[martini] RFC 6140 on Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)

rfc-editor@rfc-editor.org Thu, 03 March 2011 18:03 UTC

Return-Path: <wwwrun@rfc-editor.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 602003A69ED; Thu, 3 Mar 2011 10:03:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.107
X-Spam-Status: No, score=-102.107 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, 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 hBI0lzuH4RCo; Thu, 3 Mar 2011 10:03:46 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id B487628C103; Thu, 3 Mar 2011 10:03:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F0273E0742; Thu, 3 Mar 2011 10:04:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110303180451.F0273E0742@rfc-editor.org>
Date: Thu, 3 Mar 2011 10:04:51 -0800 (PST)
Cc: martini@ietf.org, rfc-editor@rfc-editor.org
Subject: [martini] RFC 6140 on Registration for Multiple Phone Numbers in the Session Initiation Protocol (SIP)
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: Thu, 03 Mar 2011 18:03:47 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6140

        Title:      Registration for Multiple Phone Numbers 
                    in the Session Initiation Protocol (SIP) 
        Author:     A.B. Roach
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2011
        Mailbox:    adam@nostrum.com
        Pages:      35
        Characters: 79372
        Updates:    RFC3680

        I-D Tag:    draft-ietf-martini-gin-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6140.txt

This document defines a mechanism by which a Session Initiation
Protocol (SIP) server acting as a traditional Private Branch Exchange
(PBX) can register with a SIP Service Provider (SSP) to receive phone
calls for SIP User Agents (UAs).  In order to function properly, this
mechanism requires that each of the Addresses of Record (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.  [STANDARDS-TRACK]

This document is a product of the Multiple AoR reachabiliTy InformatioN Indication Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC