RE: Recommendation for SUA modifications
"Haresign Lincoln" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <849535E338E99741B7F7413F73253EDB02544921@us-nj-mail1.comverse.com> |
Brian, That's your definition. The RFC says otherwise. An ASP can congest according to the RFC and according to practical matters in networks. We need a mechanism to support ASP congestion. The RFC has specified one. A minor change to the RFC allows the cases that the current RFC has not covered. And it has no impact on existing SGs since the handling of an SCON is optional. Regards, Lincoln -----Original Message----- From: Brian F. G. Bidulock [mailto:[email protected]] Sent: Friday, October 14, 2005 8:28 AM To: Haresign Lincoln Cc: Valerie Gastaud; [email protected]; [email protected]; [email protected] Subject: Re: [Sigtran] Recommendation for SUA modifications Lincoln, The congestion level only applies to a single point code. SCCP maintains a independent congestion level for each point code. --brian Haresign Lincoln wrote: (Fri, 14 Oct 2005 08:19:02) > Valerie, > > I think this is a good solution. Using the RC also addresses the > scenario of the ASP supporting multiple point codes (not something > that we do, but the RFC supports it). Since the current SCON message > doesn't indicate that multiple point codes can be specified in the > SCON, the RC parameter would handle this scenario also. > > Regards, > Lincoln > -- Brian F. G. Bidulock [email protected] http://www.openss7.org/ ______________________________________________________________________ This email message has been scanned by PineApp Mail-Secure and has been found clean.