Re: SG view of the ASP
"Brian F. G. Bidulock" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Organization | http://www.openss7.org/ |
| Message-ID | <[email protected]> |
Barry,
Barry Nagelberg wrote: (Fri, 10 Feb 2006 11:40:53)
>
> I suggest the following text for this param:
>
> <snip>
> ASP Identifier: 32-bit unsigned integer
>
> The optional ASP Identifier parameter contains a unique value that
> is locally significant among the ASPs that support an AS.
>
> This parameter identifies the physical ASP that is using this SCTP
ASPs are not necessarily "physical". In fact, the ASPs that the ASP
Identifier was also intended to distinguish are simply processes on
the same host (i.e, SCTP transport endpoint).
> association, in the case where an ASP is using more than one
> association to communicate with the SG.
>
> The SGP should save the ASP Identifier to be used, if necessary,
> with the Notify message (see Section 3.8.2).
> <snip>
>
I would prefer that the note from RFC 3331 and RFC 3868 be added instead
of your text.
Your text has two prolems as I see it: it is not required that an ASP
provide an ASP Identifier when it forms more than one SCTP association
with an SG. An ASP only needs to provide an ASP Identifier in two
situations:
1) when other ASPs in the AS wish to receive identification of a failed
ASP with the NTFY("ASP Failure") or identification of a overriding
ASP with the NTFY("Alternate ASP Active"); and,
2) when the SGP cannot otherwise distinguish between connecting ASPs
(e.g. when ASP are using dynamically allocated port numbers from
the same host.)
IMO your proposed text does not clarify either situation.
--brian
--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/