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

Adam Roach <adam@nostrum.com> Mon, 19 July 2010 23:21 UTC

Return-Path: <adam@nostrum.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 D57A43A695D for <martini@core3.amsl.com>; Mon, 19 Jul 2010 16:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.671
X-Spam-Level:
X-Spam-Status: No, score=-2.671 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, SPF_PASS=-0.001]
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 2+4e2w84L-lH for <martini@core3.amsl.com>; Mon, 19 Jul 2010 16:21:51 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id A8A8E3A6947 for <martini@ietf.org>; Mon, 19 Jul 2010 16:21:50 -0700 (PDT)
Received: from dn3-228.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o6JNLvR5024043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jul 2010 18:21:57 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4C44DE51.2030305@nostrum.com>
Date: Mon, 19 Jul 2010 18:22:57 -0500
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.4) Gecko/20100608 Thunderbird/3.1
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <BLU137-W10550BA232377BE7913FFE93B30@phx.gbl> <430FC6BDED356B4C8498F634416644A921187F7251@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A921187F7251@mail>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: Bernard Aboba <bernard_aboba@hotmail.com>, "martini@ietf.org" <martini@ietf.org>
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: Mon, 19 Jul 2010 23:21:51 -0000

  On 7/16/10 10:37 AM, Hadriel Kaplan wrote:
> 5) Section 7.2.1 says:
>     In particular, the "bnc" parameter is forbidden from appearing in the
>     body of a reg-event notify.
>
> Something about that statement rings warning bells in my head.  I don't know what that something is, but it seems wrong to me. :)  Are we absolutely sure this is a normative statement we want, forever?

The logic here is that subscribers to the event package won't 
necessarily know about the GIN extension. If you send them a "bnc" URI, 
they're going to have no clue that it's not just a normal URI.

Now, I don't think this prohibition is a "forever" thing. There's 
certainly nothing that says that another extension (say, VERMOUTH) is 
prohibited from overriding this prohibition with another behavior -- so 
long as the subscriber indicates that it would know what to do with a 
"bnc" URI.

Would the following change address your concern?


    In particular, the "bnc" parameter is forbidden from appearing in the
    body of a reg-event notify unless the subscriber has indicated
    knowledge of the semantics of the "bnc" parameter. The means
    for indicating this support are out of scope of this document.


/a