Draft:  draft-ietf-sipping-service-examples-10.txt
Reviewer: nagesh kumar [bvnkumar@gmail.com]
Review Date: Thursday 6/22/2006 3:46 AM
Review Deadline: 7/01/2006
Status: WGLC 
Sections: 2.7, 2.8 and 2.9 

Summary: 

=====
 
2.7 
 
F3 - Here proxy sends 181 when it is forwarding the call. However, proxy shall not generate any response by itself as per RFC 3261 - P110.
"Since a proxy may not insert a tag into the To header field of a 1xx response to a request that did not contain one, it cannot issue
non-100 provisional responses on its own. "
 
F4 - the t= line in the forwardede SDP shall be identical to what is received. ( 0 is missing).
 
F13 - the 1st Via header bracnch parameter shall be identical to what is sent in F12. (Currently, "1" is missing in the end for the latter.)
 
 
2.8
 
F6 - Here proxy sends 181 when it is forwarding the call. However, proxy shall not generate any response by itself as per RFC 3261 - P110.
"Since a proxy may not insert a tag into the To header field of a 1xx response to a request that did not contain one, it cannot issue
non-100 provisional responses on its own. "
 
2.9
 
F10 - Here proxy sends 181 when it is forwarding the call. However, proxy shall not generate any response by itself as per RFC 3261 - P110.
"Since a proxy may not insert a tag into the To header field of a 1xx response to a request that did not contain one, it cannot issue
non-100 provisional responses on its own. "

F7 - To tag in the CANCEL shall be the same as that of 180 Ringing in F5.
 
F15 - the via branch of this message shall match with the second Via header's branch parameter in F14.  
 
General
 
All the other message call-flows have Allow header included in INVITEs and responses. This shall be repeated for sections 2.7, 2.8 and 2.9 too.