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

Hadriel Kaplan <HKaplan@acmepacket.com> Tue, 28 September 2010 17:39 UTC

Return-Path: <HKaplan@acmepacket.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 25A6C3A6D6C for <martini@core3.amsl.com>; Tue, 28 Sep 2010 10:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.476
X-Spam-Level:
X-Spam-Status: No, score=-2.476 tagged_above=-999 required=5 tests=[AWL=0.123, 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 nfKL7+LEzA46 for <martini@core3.amsl.com>; Tue, 28 Sep 2010 10:39:32 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 5FC863A6AF3 for <martini@ietf.org>; Tue, 28 Sep 2010 10:39:29 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 28 Sep 2010 13:40:09 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Tue, 28 Sep 2010 13:40:08 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Brian Lindsay <brian.lindsay@genband.com>
Date: Tue, 28 Sep 2010 13:40:06 -0400
Thread-Topic: [martini] New text for gin section 7.1.1 first paragraph
Thread-Index: ActfNDDT2mxJ8royS7CLjlfnc08okg==
Message-ID: <A15A7CEA-BEAB-4C1B-8630-4AB7E3724F67@acmepacket.com>
References: <A444A0F8084434499206E78C106220CA01C81C2B32@MCHP058A.global-ad.net> <B1771F0F1F97A8478E2F449EA19CC7C5DA1A7EB3@ESESSCMS0365.eemea.ericsson.se> <A444A0F8084434499206E78C106220CA01C81C2D93@MCHP058A.global-ad.net> <F1A0ED6425368141998E077AC43334E425B8D6F6@gbplmail02.genband.com>
In-Reply-To: <F1A0ED6425368141998E077AC43334E425B8D6F6@gbplmail02.genband.com>
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
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 17:39:34 -0000

Brian,
does it really matter?  I mean John's current proposed text is basically a get-out-of-jail card.  The "unless..." clause is an untestable, abstract condition; and anyone who doesn't want to handle GRUUs doesn't have to.  As a vendor you don't have to, and as an SSP you don't have to.  So what's there to argue about?

-hadriel

On Sep 28, 2010, at 12:34 PM, Brian Lindsay wrote:

> Hi John/all,
> 
>   Whether support for routing of out-of-dialog requests to a contact is required should depend on the service offering of the SSP. For example, SSP support for an out-of-dialog REFER to a contact URI shouldn't be considered mandatory as discussed previously. As such, I think the text proposed should be conditional based on whether such services are supported by the SSP across it's interfaces.
> 
>   Here is some alternate proposed text:
> 
> 
> "Some services may require that entities, outside the SIP PBX, be able to send out-of-dialog requests to a UA behind a SIP-PBX, using a globally routable contact URI. If an SSP supports such services across the SSP interfaces, the 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. In such a case the lifetime of the mapping may depend on the services supported by the SSP)." 
> 
>