Hi All, 
 
I guess these are the typo error found in the rfc-3261. 
 
Can these be fixed ? 
1. 
A stateless proxy does not contain a client or server transaction.
   The transaction exists between the UA or stateful proxy on one side,
   and the UA or stateful proxy on the other side.  As far as SIP
   transactions are concerned, stateless proxies are effectively
   transparent.  The purpose of the client transaction is to receive a
   request from the element in which the client is embedded (call this
   element the "Transaction User" or TU; it can be a UA or a stateful
   proxy), and reliably deliver the request to a server transaction.
 
 
 
Rosenberg, et. al.          Standards Track                   [Page 123]
 
RFC 3261            SIP: Session Initiation Protocol           June 2002
 
 
   The client transaction is also responsible for receiving responses
   and delivering them to the TU, filtering out any response
   retransmissions or disallowed responses (such as a response to ACK).
   Additionally, in the case of an INVITE request, the client
   transaction is responsible for generating the ACK request for any
>>   final response accepting a 2xx response.
 
          The last sentence should have been mentioned as EXCEPTING 2xx
response instead of accepting 2xx response.
 
2. 
   If the INVITE request whose response is being acknowledged had Route
   header fields, those header fields MUST appear in the ACK.  This is
   to ensure that the ACK can be routed properly through any downstream
   stateless proxies.
 
[ABN] I feel Route header in ACK (for 300-699)  would be more meaningful
for stateful proxies rather than stateless proxies..
 
 
Best Regards,
Nataraju A.B. Kodiak Networks  Ind Pvt Ltd
"Be a student not a follower"
 
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to