[martini] Minor comments on temp-gruus in gin-07

"Elwell, John" <john.elwell@siemens-enterprise.com> Mon, 27 September 2010 16:06 UTC

Return-Path: <john.elwell@siemens-enterprise.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 2510A3A6D7B for <martini@core3.amsl.com>; Mon, 27 Sep 2010 09:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.634
X-Spam-Level:
X-Spam-Status: No, score=-102.634 tagged_above=-999 required=5 tests=[AWL=-0.035, 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 hNF06tx2wHb7 for <martini@core3.amsl.com>; Mon, 27 Sep 2010 09:06:50 -0700 (PDT)
Received: from ms04.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 4D7DE3A6D6B for <martini@ietf.org>; Mon, 27 Sep 2010 09:06:49 -0700 (PDT)
Received: from senmx12-mx ([62.134.46.10] [62.134.46.10]) by ms04.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-1641825 for martini@ietf.org; Mon, 27 Sep 2010 18:07:28 +0200
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx12-mx (Server) with ESMTP id 8842723F028E for <martini@ietf.org>; Mon, 27 Sep 2010 18:07:28 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 27 Sep 2010 18:07:28 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "martini@ietf.org" <martini@ietf.org>
Date: Mon, 27 Sep 2010 18:07:26 +0200
Thread-Topic: Minor comments on temp-gruus in gin-07
Thread-Index: ActeXhQbCKbxnlYDR4y2WQ0gDfG1Rg==
Message-ID: <A444A0F8084434499206E78C106220CA01C81C2A34@MCHP058A.global-ad.net>
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
Subject: [martini] Minor comments on temp-gruus in gin-07
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, 27 Sep 2010 16:06:53 -0000

1. In 7.1.2:
"The SIP-PBX MUST be able to construct a temp-gruu in a way that the
   SSP can decode."
In 05, it used to be "must". I think this is only intended to be an informative statement, as part of the justification why we need to standardize a mechanism. I don't think this section is placing requirements on the SIP-PBX - that should be the job of 7.1.2.2. I think "must" (or "needs to") is correct.

2. In 7.1.2.2:
"SIP-  
       PBXes that implement temporary GRUUs MUST generate a new temp-gruu  
       according to the procedures in this section for every registration  
       refresh. "
It is unclear, but I think this is intended to apply to temp gruus that the SIP-PBX provides to its registering UAs, and applies to initial registrations and registration refreshes by to those UAs (as opposed to registration refreshes with the SP). Just to make it more explicit, how about:
"SIP-  
       PBXes that implement temporary GRUUs MUST generate a new temp-gruu  
       according to the procedures in this section for every registration  
       or registration refresh from GRUU-supporting UAs attached to the SIP-PBX. "

John