[martini] gin #66 (new): Abtract and Section 1

"martini issue tracker" <trac@tools.ietf.org> Fri, 19 November 2010 06:16 UTC

Return-Path: <trac@tools.ietf.org>
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 24E343A679F for <martini@core3.amsl.com>; Thu, 18 Nov 2010 22:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, 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 CRaokBNoiLKP for <martini@core3.amsl.com>; Thu, 18 Nov 2010 22:16:33 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id A907F3A67D1 for <martini@ietf.org>; Thu, 18 Nov 2010 22:16:33 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1PJKHi-000238-FA; Thu, 18 Nov 2010 22:17:22 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "martini issue tracker" <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Fri, 19 Nov 2010 06:17:22 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/martini/trac/ticket/66
Message-ID: <067.1e63a8df94c7ce52ff8a86d2dba78964@tools.ietf.org>
X-Trac-Ticket-ID: 66
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: bernard_aboba@hotmail.com, martini@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: martini@ietf.org
Subject: [martini] gin #66 (new): Abtract and Section 1
X-BeenThere: martini@ietf.org
X-Mailman-Version: 2.1.9
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: Fri, 19 Nov 2010 06:16:36 -0000

#66: Abtract and Section 1

 Looking over the text in GIN-10,  there are two places where the
 requirements for proper functioning are addressed:

 One is the abstract:

    This document defines a mechanism by which a SIP server acting as a
    traditional Private Branch Exchange (SIP-PBX) can register with a SIP
    Service Provider (SSP) to receive phone calls for UAs designated by
    phone numbers.  In order to function properly, this mechanism relies
    on the fact that the phone numbers are fully qualified and globally
    unique.

 The other is in Section 1, whose last paragraph states:

    In recognition of the momentum that REGISTER-based approaches have
    seen in deployments, this document defines a REGISTER-based approach
    that is tailored to E.164-addressed UAs in a SIP-PBX environment.  It
    does not address registration of SIP URIs in which the user portion
    is not an E.164 number.

 As noted in the Olive document, proper functioning is not restricted to
 E.164 numbers, although the requirements are satisfied by AORs expressed
 as E.164 numbers, since they are fully qualified and globally unique.

 My suggestion would be to clarify what the actual requirement
 is, and why E.164 numbers satisfy that requirement.

 For example, the abstract could be modified as follows:

    This document defines a mechanism by which a SIP server acting as a
    traditional Private Branch Exchange (SIP-PBX) can register with a SIP
    Service Provider (SSP) to receive phone calls for UAs. In order to
    function properly, this mechanism requires that each of the AORs
    registered in bulk map to a unique set of contacts.  This requirement
 is
    satisfied by AORs representing phone numbers regardless of the domain,
    since phone numbers are fully qualified and globally unique.  This
    document therefore focuses on this use case.

 The text in Section 1 could be changed to the following:

    In recognition of the momentum that REGISTER-based approaches have
    seen in deployments, this document defines a REGISTER-based approach.
    Since E.164-addressed UAs are very common today in SIP-PBX
    environments, and since SIP URIs in which the user portion is an
    E.164 number are always globally unique regardless of the domain,
    this document focuses on registration of SIP URIs in
    which the user portion is an E.164 number.

-- 
---------------------------------------+------------------------------------
 Reporter:  bernard_aboba@…            |       Owner:            
     Type:  defect                     |      Status:  new       
 Priority:  minor                      |   Milestone:  milestone1
Component:  gin                        |     Version:  1.0       
 Severity:  Submitted WG Document      |    Keywords:            
---------------------------------------+------------------------------------

Ticket URL: <https://svn.tools.ietf.org/wg/martini/trac/ticket/66>
martini <http://tools.ietf.org/martini/>