Re: [martini] WGLC comments on draft-ietf-martini-gin

Adam Roach <adam@nostrum.com> Mon, 19 July 2010 19:02 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 F21263A6B5A for <martini@core3.amsl.com>; Mon, 19 Jul 2010 12:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[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 k0rqzI4zx82x for <martini@core3.amsl.com>; Mon, 19 Jul 2010 12:02:05 -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 2090A3A6B6A for <martini@ietf.org>; Mon, 19 Jul 2010 12:01:49 -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 o6JJ22w3002915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 19 Jul 2010 14:02:03 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4C44A163.5020801@nostrum.com>
Date: Mon, 19 Jul 2010 14:02:59 -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: Alan Johnston <alan.b.johnston@gmail.com>
References: <4C449E38.2060200@gmail.com>
In-Reply-To: <4C449E38.2060200@gmail.com>
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: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] WGLC comments on draft-ietf-martini-gin
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 19:02:06 -0000

  On 7/19/10 1:49 PM, Alan Johnston wrote:
> I have reviewed the document and believe it is ready to progress with no
> technical issues.  A few minor issues are noted below that could be
> addressed to improve the document, but aren't worth entering into the
> tracker.
>
> - Alan -
>
> Section 5.1:
>
> The first time the bnc parameter is introduced, it might be worth
> explaining it stands for Bulk Number Contact - the first time I read it
> I thought it stood for Bayonet Neill-Concelman...

Good point.

> Section 5.1:
>
> There are a couple of "must"s that probably are "MUST"s.

That's correct -- these are in the tracker.

> Section 5.2:
>
> There is some justification why the SIP-PBX MUST support Path, but none
> is given here why the Registrar MUST support it.  Is it for the same reason?

Yes. Unless the registrar supports it, including support in the PBX 
isn't particularly useful.

> Section 5.2:
>
> While the SIP-PBX MUST include Proxy-Require:gin, it is possible a
> registration might arrive at a Registrar with a bnc but no
> Proxy-Require:gin.  Should we define the correct behavior of the
> Registrar for this case?

How would that happen?

/a