IETF Logo Mail Archive

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

<R.Jesske@telekom.de> Mon, 15 October 2012 14:50 UTC

Return-Path: <R.Jesske@telekom.de>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9BB121F86AB for <sipcore@ietfa.amsl.com>; Mon, 15 Oct 2012 07:50:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJ5MbaGmyLJB for <sipcore@ietfa.amsl.com>; Mon, 15 Oct 2012 07:50:48 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id 34E0421F86A5 for <sipcore@ietf.org>; Mon, 15 Oct 2012 07:50:48 -0700 (PDT)
Received: from he113445.emea1.cds.t-internal.com ([10.134.93.105]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 15 Oct 2012 16:50:46 +0200
Received: from HE111648.emea1.cds.t-internal.com ([10.134.93.17]) by HE113445.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 15 Oct 2012 16:50:45 +0200
From: R.Jesske@telekom.de
To: brett@broadsoft.com, sipcore@ietf.org, draft-ietf-sipcore-rfc4244bis-callflows@tools.ietf.org
Date: Mon, 15 Oct 2012 16:50:44 +0200
Thread-Topic: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-01: section 3.7 comments
Thread-Index: Ac2ollYDzsmluaajQh6TumzWBMajQgCTYEGw
Message-ID: <580BEA5E3B99744AB1F5BFF5E9A3C67D1545048117@HE111648.emea1.cds.t-internal.com>
References: <576A8B541C219D4E9CEB1DF8C19C7B88016B08@MBX06.citservers.local>
In-Reply-To: <576A8B541C219D4E9CEB1DF8C19C7B88016B08@MBX06.citservers.local>
Accept-Language: de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sipcore] draft-ietf-sipcore-rfc4244bis-callflows-01: section 3.7 comments
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 14:50:52 -0000

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

v2.46.0 | Report a Bug | By Email | System Status