Re: [martini] Announcement of MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"

"Elwell, John" <john.elwell@siemens-enterprise.com> Fri, 16 July 2010 17:28 UTC

Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF05A3A6AA2 for <martini@core3.amsl.com>; Fri, 16 Jul 2010 10:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level:
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.215, 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 dNFGH5pvjRNX for <martini@core3.amsl.com>; Fri, 16 Jul 2010 10:28:03 -0700 (PDT)
Received: from ms02.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 9DC653A6AA7 for <martini@ietf.org>; Fri, 16 Jul 2010 10:28:02 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms02.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-881354; Fri, 16 Jul 2010 19:28:13 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id A46CD23F0278; Fri, 16 Jul 2010 19:28:13 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Fri, 16 Jul 2010 19:28:13 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>, Bernard Aboba <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
Date: Fri, 16 Jul 2010 19:28:12 +0200
Thread-Topic: [martini] Announcement of MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"
Thread-Index: AcsdmUew8PdE1pujT9S8ZGk7hxSBuQHWgTRgAAY4SiA=
Message-ID: <A444A0F8084434499206E78C106220CAECB2FD96@MCHP058A.global-ad.net>
References: <BLU137-W10550BA232377BE7913FFE93B30@phx.gbl> <430FC6BDED356B4C8498F634416644A921187F7251@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A921187F7251@mail>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [martini] Announcement of MARTINI WG last Call on "Registration for Multiple Phone Numbers in the SIP"
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of en-mass SIP PBX registration mechanisms <martini.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/martini>
List-Post: <mailto:martini@ietf.org>
List-Help: <mailto:martini-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/martini>, <mailto:martini-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jul 2010 17:28:03 -0000

 

> -----Original Message-----
> From: martini-bounces@ietf.org 
> [mailto:martini-bounces@ietf.org] On Behalf Of Hadriel Kaplan
> Sent: 16 July 2010 16:37
> To: Bernard Aboba; martini@ietf.org
> Subject: Re: [martini] Announcement of MARTINI WG last Call 
> on "Registration for Multiple Phone Numbers in the SIP"
> 
> 
> Howdy,
> I've reviewed the latest gin draft and think it is ready for 
> consideration by the IESG, if the following changes/comments 
> are made/addressed (these will also be added in the tools database):
> 
> 1) Section 5.2 says:
>    A registrar that receives a Contact URI with both a "bnc" parameter
>    and a user portion MUST either discard the user portion and process
>    the request as if the parameter were not present or return 
> a 400 (Bad
>    Request) error in response (unless some other error code is more
>    appropriate).
> 
>    Section 5.3 says:
>    When a SIP-PBX registers with an SSP using a "bnc" contact, that
>    contact MUST NOT include a "user" parameter.  An SSP registrar that
>    receives a Contact URI with both a "bnc" parameter and a "user"
>    parameter MUST either discard the "user" parameter and process the
>    request as if the parameter were not present or return a 400 (Bad
>    Request) error in response (unless some other error code is more
>    appropriate).
> 
> I think we need to pick one and only one behavior - having 
> some Registrars accept these and others not leads to 
> inconsistent interoperability among vendor equipment.  Since 
> at some future time we may find a need for the user portion, 
> but will probably want backwards-compatibility without 
> failure at that time, I recommend for 5.2 we stipulate a 
> Registrar compliant to this draft MUST discard and ignore the 
> user portion and process the request as if the user portion 
> were not present; and for 5.3 the same for a "user" param.  
> This would also follow the mantra of strict on send, liberal 
> on receipt.
[JRE] Sounds reasonable to me.

John