Brian,
The SCTP association still UP. We did not notice any ABORT. If there was an ABORT, SCCP connection request would n't have gone till peer node SCCP layer which is above M3UA.
Thanks
--- On Mon, 3/2/09, Brian F. G. Bidulock <[email protected]> wrote:
From: Brian F. G. Bidulock <[email protected]>
Subject: Re: query regarding ASP Identifier in ASP UP ACK .
To: [email protected]
Cc: "sigtran" <[email protected]>
Date: Monday, March 2, 2009, 8:02 AM
moharana_p,
I have no idea what special use there is for IPSP.
Because the sender of the ASP UP forms the SCTP association,
it should know the identity of the ASP to which it is sending it.
It is the receiver of the ASP UP, that accepted the SCTP
association, that may not be able to derived from a dynamically
allocated port number on the connecting peer, the ASP Id of
the sender of the ASP UP.
--brian
[email protected] wrote: (Mon, 02 Mar 2009 04:17:17)
>
> Hello,
>
> As per the rfc-4666.
>
> 3.5.2. ASP Up Acknowledgement (ASP Up Ack)
> ......
> The optional ASP Identifier parameter is specifically useful for
> IPSP
> communication. In that case, the IPSP answering the ASP Up message
> MAY include its own ASP Identifier value.
>
> Since ASP Identifier is used to identify the ASP with in an AS so in
> ASP UP ACK message ASP Identifier value should be the value that
> received in ASP UP message in stead of its own ASP Identifier value.
>
> If No then what is the role of ASP identifier in case of IPSP mode?
>
> Br,
> Padmalochan
--
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/
_______________________________________________
Sigtran mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sigtran
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.