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

"Richard Shockey" <richard@shockey.us> Tue, 28 September 2010 14:59 UTC

Return-Path: <richard@shockey.us>
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 78A923A6D16 for <martini@core3.amsl.com>; Tue, 28 Sep 2010 07:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.24
X-Spam-Level:
X-Spam-Status: No, score=-102.24 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 p5vLgkAa-Lce for <martini@core3.amsl.com>; Tue, 28 Sep 2010 07:59:02 -0700 (PDT)
Received: from oproxy3-pub.bluehost.com (oproxy3-pub.bluehost.com [69.89.21.8]) by core3.amsl.com (Postfix) with SMTP id EED313A6CA8 for <martini@ietf.org>; Tue, 28 Sep 2010 07:59:01 -0700 (PDT)
Received: (qmail 13399 invoked by uid 0); 28 Sep 2010 14:59:43 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy3.bluehost.com with SMTP; 28 Sep 2010 14:59:43 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=shockey.us; h=Received:From:To:References:In-Reply-To:Subject:Date:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:Thread-Index:Content-Language:X-Identified-User; b=LkH4k8ORgMfiberkkrpVumf5gXw+JErCQEqFG62+R2JZ7Am2f1CFr0B3icj6b/UtT65SDQJ4qB6Yy0WzaGycO4HEjwaoaMm7zyGMkAXCxZGQUht5kPG+GepQ/Ur2q834;
Received: from pool-173-79-200-247.washdc.fios.verizon.net ([173.79.200.247] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.69) (envelope-from <richard@shockey.us>) id 1P0beg-0008Hu-Op; Tue, 28 Sep 2010 08:59:43 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Adam Roach'" <adam@nostrum.com>, <martini@ietf.org>
References: <A444A0F8084434499206E78C106220CA01C81C2B32@MCHP058A.global-ad.net> <B1771F0F1F97A8478E2F449EA19CC7C5DA1A7EB3@ESESSCMS0365.eemea.ericsson.se> <A444A0F8084434499206E78C106220CA01C81C2D93@MCHP058A.global-ad.net> <4CA1ECC9.4080908@nostrum.com>
In-Reply-To: <4CA1ECC9.4080908@nostrum.com>
Date: Tue, 28 Sep 2010 10:59:40 -0400
Message-ID: <019901cb5f1d$c7c296e0$5747c4a0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActfEKRAEvC9rW+PRh2XYSKGMCGP7AADOM2Q
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 173.79.200.247 authed with richard@shockey.us}
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 14:59:03 -0000

+1 though I would have preferred SHOULD. 

My principal concern has been deployment. I would roughly guess it will take
2 years or more for this to make the rounds.

-----Original Message-----
From: martini-bounces@ietf.org [mailto:martini-bounces@ietf.org] On Behalf
Of Adam Roach
Sent: Tuesday, September 28, 2010 9:25 AM
To: Elwell, John
Cc: martini@ietf.org
Subject: Re: [martini] New text for gin section 7.1.1 first paragraph

  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

_______________________________________________
martini mailing list
martini@ietf.org
https://www.ietf.org/mailman/listinfo/martini