RE: DRN and TID Label Issues - Issue #5

Brian,

I don't see any problem with the wording below.

Lincoln

-----Original Message-----
From: Brian F. G. Bidulock [mailto:[email protected]] 
Sent: Wednesday, October 11, 2006 3:54 PM
To: Haresign Lincoln
Cc: Barry Nagelberg; [email protected]
Subject: DRN and TID Label Issues - Issue #5

Lincoln,

RFC 3868 says:

4.3.4.3.  ASP Active Procedures

   ...

   An SGP or IPSP, upon reception of an ASP Active message for the first
   ASP in a Loadshare AS, MAY choose not to direct traffic to a newly
   active ASP until it determines that there are sufficient resources to
   handle the expected load (e.g., until there are "n" ASPs in state
   ASP-ACTIVE in the AS).

4.7.3.1.  TCAP traffic

   Messages not containing a destination (or "responding") TID, i.e.,
   Query, Begin, Unidirectional, are loadshared among the available
   ASPs.  Any scheme permitting a fair load distribution among the ASPs
   is allowed (e.g., round robin).

4.7.3.2.  SCCP Connection Oriented traffic

   Messages not containing a destination reference number (DRN), i.e., a
   Connection Request, MAY be loadshared among the available ASPs.

Application of the concept of "n" and DRN/TID labels is inconsistent.

--brian

--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/