NANC 279

SOA Resynchronization for Large Ranges

Origination Date :04/16/1999

Originator:MCI

Description:

A problem exists for re-syncing the SOA for large ranges, because the SV time stamp that the NPAC users for re-syncs is the same for large ranges.

For example, if all the TNs in the range contain the same time stamp (e.g., 17 minutes and 20 seconds after 3p, 15:17:20), and the number of TNs in the range exceeds the tunable allowed for queries, the SOA cannot re-sync since the NPAC, for any time range, will respond with an error for maximum TN query reached.

Final Resolution:

May LNPAWG (Baltimore), this is an issue that needs more thought.  Leave on open issue for now, and let SPs discuss internally, and provide more information next month.

June LNPAWG (San Ramon), discussed this change order in conjunction with NANC 285.  Need to add to the text that this is a query functionality issue, and not just a resync issue.  Since this is related to 285, MCI is O.K. with closing out this change order, and moving the requested functionality into 285.  Move to cancel-pending category.

Related Release:

N/A

Status: Closed