Re: Mandatory/optional RC in ACTIVE/INACTIVE ACK
"Saurabh Jain" <[email protected]>
| Newsgroups | gmane.ietf.sigtran |
|---|---|
| Message-ID | <[email protected]> |
Hello Ilie, I believe your point is valid. In ASP Active Ack Message, the Routing Key IE should have been Optional. In ASP Active and ASP Inactive, absence of RC, would imply that ASP Active is meant for all AS served by the ASP. Section 4.3.4.3 : * In the case where an ASP Active message does not contain a Routing Context parameter, * * the receiver must know, via configuration data, which Application Server(s) the ASP is a member. * Similarly in ASP Active Ack and ASP Inactive Ack, absence of RC should imply that Acknowledgement is meant for all AS served by ASP. (NOTE: Peer SUA always has the option o sending individual acknowledgements for each RC) Section 4.3.4.3 : * The Routing Context parameter "MUST" be included in the ASP Active Ack message(s) "if" the* * received ASP Active message contained any Routing Contexts. In ACTIVE and INACTIVE, RC is optional,* * would imply that ASP Active is meant for all AS served by the ASP.* Thus, in case ASP Active didn't contain RC, then MUST clause doesn't apply. Regards Saurabh Jain Flextronics Software Systems On 9/22/06, Ilie Glib <[email protected]> wrote: > > Hello Folks > > SUA RFC requires RC in ACTIVE ACK message, while the RC in ACTIVE is > optional. Perhaps, this is OK, but the RC in INACTIVE ACK is optional. > > What is the reason for that difference. > > Thank you in advance > > -- > Ilie > > _______________________________________________ > Sigtran mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/sigtran > _______________________________________________ Sigtran mailing list [email protected] https://www1.ietf.org/mailman/listinfo/sigtran