[martini] #49: NITs

"martini issue tracker" <trac@tools.ietf.org> Mon, 12 July 2010 13:26 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 C21643A6358 for <martini@core3.amsl.com>; Mon, 12 Jul 2010 06:26:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level:
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.070, 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 emjrjKm24UYa for <martini@core3.amsl.com>; Mon, 12 Jul 2010 06:26:18 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id ED4653A67A7 for <martini@ietf.org>; Mon, 12 Jul 2010 06:26:18 -0700 (PDT)
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 1OYJ1e-0003f1-OJ; Mon, 12 Jul 2010 06:26:26 -0700
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: john.elwell@siemens-enterprise.com
X-Trac-Project: martini
Date: Mon, 12 Jul 2010 13:26:26 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/49
Message-ID: <076.6b72e55767e3af8f26fa131f1691fb80@tools.ietf.org>
X-Trac-Ticket-ID: 49
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: john.elwell@siemens-enterprise.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] #49: NITs
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: Mon, 12 Jul 2010 13:26:19 -0000

#49: NITs
------------------------------------------------+---------------------------
 Reporter:  john.elwell@…                       |       Owner:            
     Type:  defect                              |      Status:  new       
 Priority:  trivial                             |   Milestone:  milestone1
Component:  gin                                 |     Version:  1.0       
 Severity:  In WG Last Call                     |    Keywords:            
------------------------------------------------+---------------------------
 Nits:
 N1. "in the same way that
    is would "
 Change "is" to "it".

 N2. "then the resulting registration
    information documents SHOULD contain an 'aor' attribute in its
    <registration/> element"
 Change "documents" to "document", or alternatively add "each" after
 "SHOULD".

 N3. "for all the potentially
    effected users"
 Change "effected" to "affected".

 N4. "The ability to learn the identity and registration state of every use
    on the PBX "
 Change "use" to "user".

 N5. "These are being defined in
    the MARTINI requirements document [8]."
 Delete "being".

 N6.  "   Further, the term "SSP" is meant as an acronym for a "SIP Service
    Provider," while "
 Move the comma outside the quotes.

 N7. Perhaps it is a matter of taste (ignore if you wish), but there are
 several places where we talk about REGISTER message or just REGISTER when
 we perhaps mean REGISTER request.

 N8. Again a mater of taste, but in several places the word "multitude" is
 used, which suggests the number is always very large. Perhaps
 "multiplicity" might be better.

 N9. "   that User Agents services by the SIP-PBX can acquire and use GRUUs
    for their own use."
 Change "services" to "serviced".

 N10. "sent the following Contact header field
    in its register"
 Change "register" to "REGISTER request".

 N11. "When the
       SSP registrar creates the first temporary GRUU for a particular
       SIP-PBX and instance ID..."
 This is the first time "instance ID" has been mentioned - should we have a
 reference to RFC 5627 at this point?

 N12. "temp-gruu-cookie = base64enc(I_i || SA)"
 We should add "where || denotes concatenation." (the same as in 7.1.2.2)

 N13: "This allows the SSP to
    designate a domain on the incoming Request URI that does not
    necessarily resolve to the SIP-PBX from when the SSP applies RFC 3263
    procedures to it."
 I think the word "from" should be deleted.

 N14: "This document registers a new SIP option tag to indicate support for
    the mechanism it defines, plus two new SIP URI parameters."
 We should also mention the new header field parameter defined in 9.3.

 N15: "more than on AOR"
 Chance "on" to "one".

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/martini/trac/ticket/49>
martini <http://tools.ietf.org/martini/>