[martini] #48: Appendix A

"martini issue tracker" <trac@tools.ietf.org> Thu, 08 July 2010 07:25 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: martini@core3.amsl.com
Delivered-To: martini@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id A2AB53A67E9 for <martini@core3.amsl.com>; Thu, 8 Jul 2010 00:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.502
X-Spam-Status: No, score=-102.502 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id ZxXm-sbEWppJ for <martini@core3.amsl.com>; Thu, 8 Jul 2010 00:25:45 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 8FE683A67B1 for <martini@ietf.org>; Thu, 8 Jul 2010 00:25:45 -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 1OWlUS-0001J0-NC; Thu, 08 Jul 2010 00:25:48 -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: adam@nostrum.com, bernard_aboba@hotmail.com
X-Trac-Project: martini
Date: Thu, 08 Jul 2010 07:25:48 -0000
X-URL: http://tools.ietf.org/martini/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/martini/trac/ticket/48
Message-ID: <067.5a22eadd4a3556222a2df4553fbf9f93@tools.ietf.org>
X-Trac-Ticket-ID: 48
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: adam@nostrum.com, 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] #48: Appendix A
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: Thu, 08 Jul 2010 07:25:46 -0000

#48: Appendix A
 Reporter:  bernard_aboba@…            |       Owner:  adam@…          
     Type:  defect                     |      Status:  new             
 Priority:  major                      |   Milestone:  milestone1      
Component:  gin                        |     Version:  1.0             
 Severity:  In WG Last Call            |    Keywords:                  
 Since Appendix A was added the requirements document has changed. The
 changes include:

 New text for REQs 4, 5, 10, 14, 15:

    REQ4 - The mechanism MUST allow UAs attached to a SIP-PBX to register
    with the SIP-PBX for AORs based on assigned telephone numbers, in
    order to receive requests targeted at those telephone numbers,
    without needing to involve the SSP in the registration process.

    REQ5 - The mechanism MUST allow a SIP-PBX to handle requests
    originating at its own UAs and targeted at its assigned telephone
    numbers, without routing those requests to the SSP.

    REQ10 - The mechanism MUST work in the presence of a sequence of
    intermediate SIP entities on the SIP-PBX-to-SSP interface (i.e.,
    between the SIP-PBX and the SSP's domain proxy), where those
    intermediate SIP entities indicated during registration a need to be
    on the path of inbound requests to the SIP-PBX.

    REQ14 - The mechanism MUST be able to operate over a transport that
    provides end-to-end integrity protection and confidentiality between
    the SIP-PBX and the SSP, e.g., using TLS as specified in [RFC3261].

    REQ15 - The mechanism MUST support authentication of the SIP-PBX by
    the SSP and vice versa, e.g., using SIP digest authentication plus
    TLS server authentication as specified in [RFC3261].

 The Requirement 17 presently referenced in Appendix A has been deleted.
 Requirement 18 is now Requirement 17:

    REQ17 - The mechanism MUST work over any existing transport specified
    for SIP, including UDP.

 DES4 has been deleted.

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