Subject: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-01: section 3.6 comments

From: Brett Tate <[email-masked]>
Date: Fri, 12 Oct 2012 16:18:23 +0000

The following are some WGLC comments concerning draft-ietf-sipcore-rfc4244bis-callflows-01 section 3.6.

1) All of the requests must include Max-Forwards to be RFC 3261 compliant.

2) Figure is missing an ACK for 302; consider it optional to also include the ACK message details.

3) For draft-ietf-sipcore-rfc4244bis compliance, F1 appears to need a History-Info.

4) If I understand draft-ietf-sipcore-rfc4244bis correctly, F3 needs mp=1 added to the Contact.

5) F1 and F6 are missing SIP/2.0

This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, or by sending an email to [email-masked], and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it.