Re: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-01: section 3.7 comments

[Brett Tate <[e-mail]>]

Hi Roland,

Based upon the following RFC 3261 definition of Redirect Server, Bob's client is a redirect server.  Thus the parameter must be added.  And if not added by the Redirect Server, F4 is non compliant to the following draft-ietf-sipcore-rfc4244bis section 10.4 MUST NOT.

RFC 3261 section 6:

"Redirect Server: A redirect server is a user agent server that
 generates 3xx responses to requests it receives, directing the
 client to contact an alternate set of URIs."

Draft-ietf-sipcore-rfc4244bis-10 section 10.4:

"If the Contact header field
 does not contain an "rc" or "mp" header field parameter, then the SIP
 entity MUST NOT include an "rc" or "mp" header field parameter in the
 hi-target-param in the hi-entry when the request is retargeted to a
 contact URI received in a 3xx response."


> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]]
> Sent: Monday, October 15, 2012 10:51 AM
> To: Brett Tate; [e-mail]; draft-ietf-sipcore-rfc4244bis-
> [e-mail]
> Subject: AW: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-01:
> section 3.7 comments
> 
> 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