IETF Logo Mail Archive

Re: [sipcore] Summary: number of location headers

"Thomson, Martin" <Martin.Thomson@andrew.com> Wed, 10 November 2010 01:53 UTC

Return-Path: <Martin.Thomson@andrew.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B09483A6A15 for <sipcore@core3.amsl.com>; Tue, 9 Nov 2010 17:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.56
X-Spam-Level:
X-Spam-Status: No, score=-3.56 tagged_above=-999 required=5 tests=[AWL=-0.961, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUvrfJ8pkTfa for <sipcore@core3.amsl.com>; Tue, 9 Nov 2010 17:53:27 -0800 (PST)
Received: from csmailgw2.commscope.com (csmailgw2.commscope.com [198.135.207.242]) by core3.amsl.com (Postfix) with ESMTP id BA5743A69D3 for <sipcore@ietf.org>; Tue, 9 Nov 2010 17:53:27 -0800 (PST)
Received: from [10.86.20.103] ([10.86.20.103]:62566 "EHLO ACDCE7HC2.commscope.com") by csmailgw2.commscope.com with ESMTP id S488538Ab0KJBxw (ORCPT <rfc822; sipcore@ietf.org>); Tue, 9 Nov 2010 19:53:52 -0600
Received: from SISPE7HC1.commscope.com (10.97.4.12) by ACDCE7HC2.commscope.com (10.86.20.103) with Microsoft SMTP Server (TLS) id 8.1.436.0; Tue, 9 Nov 2010 19:53:17 -0600
Received: from SISPE7MB1.commscope.com ([fe80::9d82:a492:85e3:a293]) by SISPE7HC1.commscope.com ([fe80::8a9:4724:f6bb:3cdf%10]) with mapi; Wed, 10 Nov 2010 09:53:12 +0800
From: "Thomson, Martin" <Martin.Thomson@andrew.com>
To: "Elwell, John" <john.elwell@siemens-enterprise.com>, SIPCORE Chairs <sipcore-chairs@tools.ietf.org>, "SIPCORE (Session Initiation Protocol Core) WG" <sipcore@ietf.org>
Date: Wed, 10 Nov 2010 09:53:09 +0800
Thread-Topic: [sipcore] Summary: number of location headers
Thread-Index: Act/7fuf6bscUKp/QZ6eF+3pdklD4wAis/BAAABBELA=
Message-ID: <8B0A9FCBB9832F43971E38010638454F03F33652A1@SISPE7MB1.commscope.com>
References: <4CD90FFC.40502@nostrum.com> <A444A0F8084434499206E78C106220CA023587F124@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA023587F124@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BCN: Meridius 1000 Version 3.4 on csmailgw2.commscope.com
X-BCN-Sender: Martin.Thomson@andrew.com
Subject: Re: [sipcore] Summary: number of location headers
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 10 Nov 2010 01:53:28 -0000

That's sensible.

On 2010-11-10 at 09:46:46, Elwell, John wrote:
> I think we have to make provision for >1, and limiting it to 2 probably
> doesn't make sense. However, the warnings must include the fact that
> anyone inserting an additional location and then getting back a 424 has
> no way of knowing whether the 424 applies to the location it inserted
> or a location already present.
> 
> John
> 
> > -----Original Message-----
> > From: sipcore-bounces@ietf.org
> > [mailto:sipcore-bounces@ietf.org] On Behalf Of Adam Roach -
> > SIPCORE Chair
> > Sent: 09 November 2010 09:10
> > To: SIPCORE (Session Initiation Protocol Core) WG
> > Subject: [sipcore] Summary: number of location headers
> >
> > [as chair]
> >
> > I just wanted to summarize where it looks like the discussion
> > ended up
> > on whether we constrain the number of location header fields in a SIP
> > message. From my review of the discussion, I believe that four people
> > have weighed in on the topic to voice support for an
> > arbitrary number of
> > location headers (albeit with a implementation warning that
> > doing so is
> > not advisable):
> >
> > Martin Thompson:
> > http://www.ietf.org/mail-archive/web/sipcore/current/msg03576.html
> > Richard Barnes:
> > http://www.ietf.org/mail-archive/web/sipcore/current/msg03580.html
> > Keith Drage:
> > http://www.ietf.org/mail-archive/web/sipcore/current/msg03600.html
> > Hannu Hietalahti:
> > http://www.ietf.org/mail-archive/web/sipcore/current/msg03619.html
> >
> > And two people have agreed to go along with that direction, with
> > expressed reservations:
> >
> > Jon Peterson:
> > http://www.ietf.org/mail-archive/web/sipcore/current/msg03601.html
> > James Polk:
> > http://www.ietf.org/mail-archive/web/sipcore/current/msg03603.html
> >
> > If any other working group participants have comments on this topic,
> > they are encouraged to make them quickly. Lacking any further
> > input, the
> > authors will be instructed to revise the document to allow an
> > arbitrary
> > number of location header fields, with an accompanying warning that
> > doing so is not recommended.
> >
> > /a
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
> >
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore

v2.23.0 | Report a Bug | By Email