Subject: Re: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-01: section 3.7 comments
From: <[email-masked]>
To: <[email-masked]>, <[email-masked]>, <[email-masked]>
Date: Mon, 15 Oct 2012 16:50:44 +0200
List-Id: SIP Core Working Group <sipcore.ietf.org>

Hi Brett,
with regard to your comment:

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

I understand RFC4244bis correct that the adding of mp=1 needs only to be done when it is a redirect server which carol's end device is not.

RFC4244bis
...
8.  Redirect Server Handling of History-Info Header Fields

   A redirect server MUST follow the procedures in Section 9.1 when it
   receives a SIP Request.  A redirect server MUST follow the procedures
   in Section 9.4 when it sends a SIP Response.  When generating the
   Contact header field in a 3xx response, the redirect server MUST add
   the appropriate "mp", "np" or "rc" header field parameter to each
   Contact header field as described in Section 10.4, if applicable.
...

Best Regards

Roland