Browse Prior Art Database

Requirements for Multiple Address of Record (AOR) Reachability Information in the Session Initiation Protocol (SIP) (RFC5947)

IP.com Disclosure Number: IPCOM000199700D
Original Publication Date: 2010-Sep-01
Included in the Prior Art Database: 2010-Sep-15
Document File: 26 page(s) / 30K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Elwell: AUTHOR [+2]

Abstract

The Session Initiation Protocol (SIP) [RFC3261], together with its extensions, supports multiple means of obtaining the connection information necessary to deliver out-of-dialog SIP requests to their intended targets. When a SIP proxy needs to send a request to a target address of record (AOR) within its domain, it can use a location service to obtain the registered Contact Universal Resource Identifiers (URIs), together with any associated path information [RFC3327], and build a route set to reach each target user agent (UA). The SIP REGISTER method can be used to register Contact URIs and path information. SIP-outbound [RFC5626] enhances this mechanism to cater to UAs behind Network Address Translators (NATs) and firewalls. When an entity needs to send a request to a target for which it is not authoritative, the entity can follow [RFC3263] procedures for using the Domain Name System (DNS) to obtain the next- hop connection information.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                         J. Elwell Request for Comments: 5947             Siemens Enterprise Communications Category: Informational                                        H. Kaplan ISSN: 2070-1721                                              Acme Packet                                                           September 2010

      Requirements for Multiple Address of Record (AOR) Reachability           Information in the Session Initiation Protocol (SIP)

Abstract

   This document states requirements for a standardized SIP registration    mechanism for multiple addresses of record (AORs), the mechanism    being suitable for deployment by SIP service providers on a large    scale in support of small to medium sized Private Branch Exchanges    (PBXs).  The requirements are for a solution that can, as a minimum,    support AORs based on E.164 numbers.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc5947.

Elwell & Kaplan               Informational                     [Page 1]
 RFC 5947            Multiple AOR reachability in SIP      September 2010

 Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3

   2. Terminology .....................................................3

   3. Problem Statement ...............................................4

 ...