Re: [martini] New text for gin section 7.1.1 first paragraph

Adam Roach <adam@nostrum.com> Tue, 28 September 2010 13:24 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 40DA13A6D17 for <martini@core3.amsl.com>; Tue, 28 Sep 2010 06:24:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level:
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 FECr4VFl13P2 for <martini@core3.amsl.com>; Tue, 28 Sep 2010 06:24:50 -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 8B8043A6D0C for <martini@ietf.org>; Tue, 28 Sep 2010 06:24:49 -0700 (PDT)
Received: from hydra-3.local (ppp-70-249-149-233.dsl.rcsntx.swbell.net [70.249.149.233]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id o8SDPTLk068094 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 28 Sep 2010 08:25:29 -0500 (CDT) (envelope-from adam@nostrum.com)
Message-ID: <4CA1ECC9.4080908@nostrum.com>
Date: Tue, 28 Sep 2010 08:25:29 -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.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: "Elwell, John" <john.elwell@siemens-enterprise.com>
References: <A444A0F8084434499206E78C106220CA01C81C2B32@MCHP058A.global-ad.net> <B1771F0F1F97A8478E2F449EA19CC7C5DA1A7EB3@ESESSCMS0365.eemea.ericsson.se> <A444A0F8084434499206E78C106220CA01C81C2D93@MCHP058A.global-ad.net>
In-Reply-To: <A444A0F8084434499206E78C106220CA01C81C2D93@MCHP058A.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "martini@ietf.org" <martini@ietf.org>
Subject: Re: [martini] New text for gin section 7.1.1 first paragraph
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: Tue, 28 Sep 2010 13:24:54 -0000

  This text is fine too.

/a

On 9/28/10 04:52, Sep 28, Elwell, John wrote:
> Martien has privately indicated to me a certain lack of clarity in the proposed text. In thinking about this again, I haven't got the wording quite right. The bulk registration mechanism doesn't register UAs behind the PBX - it registers contacts for each of the AORs assigned to the PBX. What we are concerned about here is contact URIs for UAs behind the PBX. Those UAs register with the PBX, they do not register using the bulk registration mechanism. So my revised words would be as follows (only the first sentence has changed):
>
> "An SSP needs to provide a means of assigning a globally routable contact URI to a UA behind a SIP-PBX, thereby allowing other entities to address out-of-dialog requests to that UA. To achieve this, an SSP MUST support the public GRUU mechanism described in this section, unless the SSP has other means of providing globally routable contact URIs (e.g., by acting as a B2BUA and performing mapping between SIP-PBX-provided local contact URIs and SSP-provided globally routable contact URIs)."
>
> John
>
>
>> -----Original Message-----
>> From: Elwell, John
>> Sent: 28 September 2010 08:44
>> To: 'Martien Huysmans'
>> Subject: RE: New text for gin section 7.1.1 first paragraph
>>
>> Martien,
>>
>> Yes, in thinking about this again, I haven't got the wording
>> quite right. The bulk registration mechanism doesn't register
>> UAs behind the PBX - it registers contacts for each of the
>> AORs assigned to the PBX. What we are concerned about here is
>> contact URIs for UAs behind the PBX. Those UAs register with
>> the PBX, they do not register using the bulk registration
>> mechanism. So my revised words would be as follows (only the
>> first sentence has changed):
>>
>> "An SSP needs to provide a means of assigning globally
>> routable contact URIs to UAs behind a SIP-PBX, thereby
>> allowing other entities to address out-of-dialog requests to
>> those UAs. To achieve this, an SSP MUST support the public
>> GRUU mechanism described in this section, unless the SSP has
>> other means of providing globally routable contact URIs
>> (e.g., by acting as a B2BUA and performing mapping between
>> SIP-PBX-provided local contact URIs and SSP-provided globally
>> routable contact URIs)."
>>
>> John
>>
>>> -----Original Message-----
>>> From: Martien Huysmans [mailto:martien.huysmans@ericsson.com]
>>> Sent: 28 September 2010 08:13
>>> To: Elwell, John
>>> Subject: RE: New text for gin section 7.1.1 first paragraph
>>>
>>> I find this a difficult sentence to understand. Is UA the
>>> SIP-PBX or the UA behind the SIP-PBX. So I propose to add
>>> "behind a SIP-PBX".
>>>
>>> An SSP needs to provide a means of assigning globally
>>> routable contact URIs to UAs behind a SIP-PBX ...
>>>
>>> Regards Martien
>>>
>>> -----Original Message-----
>>> From: martini-bounces@ietf.org
>>> [mailto:martini-bounces@ietf.org] On Behalf Of Elwell, John
>>> Sent: Monday, September 27, 2010 9:30 PM
>>> To: martini@ietf.org
>>> Subject: [martini] New text for gin section 7.1.1 first paragraph
>>>
>>> As actioned on this evening's call, here is my proposed text:
>>>
>>> "An SSP needs to provide a means of assigning globally
>>> routable contact URIs to UAs that have been registered using
>>> the bulk registration mechanism specified in this document,
>>> thereby allowing other entities to address out-of-dialog
>>> requests to those UAs. To achieve this, an SSP MUST support
>>> the public GRUU mechanism described in this section, unless
>>> the SSP has other means of providing globally routable
>>> contact URIs (e.g., by acting as a B2BUA and performing
>>> mapping between SIP-PBX-provided local contact URIs and
>>> SSP-provided globally routable contact URIs)."
>>>
>>> John
>>> _______________________________________________
>>> martini mailing list
>>> martini@ietf.org
>>> https://www.ietf.org/mailman/listinfo/martini
>>>
> _______________________________________________
> martini mailing list
> martini@ietf.org
> https://www.ietf.org/mailman/listinfo/martini