A SIP Usage for REsource LOcation And Discovery (RELOAD)
RFC 7904

Document Type RFC - Proposed Standard (October 2016; No errata)
Last updated 2016-10-17
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Carlos Bernardos
Shepherd write-up Show (last changed 2016-02-02)
IESG IESG state RFC 7904 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                       C. Jennings
Request for Comments: 7904                                         Cisco
Category: Standards Track                                    B. Lowekamp
ISSN: 2070-1721                                                    Skype
                                                             E. Rescorla
                                                              RTFM, Inc.
                                                                S. Baset
                                                                     IBM
                                                          H. Schulzrinne
                                                     Columbia University
                                                         T. Schmidt, Ed.
                                                             HAW Hamburg
                                                            October 2016

        A SIP Usage for REsource LOcation And Discovery (RELOAD)

Abstract

   This document defines a SIP Usage for REsource LOcation And Discovery
   (RELOAD).  The SIP Usage provides the functionality of a SIP proxy or
   registrar in a fully distributed system and includes a lookup service
   for Address of Records (AORs) stored in the overlay.  It also defines
   Globally Routable User Agent URIs (GRUUs) that allow the
   registrations to map an AOR to a specific node reachable through the
   overlay.  After such initial contact of a Peer, the RELOAD AppAttach
   method is used to establish a direct connection between nodes through
   which SIP messages are exchanged.

Status of This Memo

   This is an Internet Standards Track document.

   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).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   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/rfc7904.

Jennings, et al.             Standards Track                    [Page 1]
RFC 7904                    RELOAD SIP Usage                October 2016

Copyright Notice

   Copyright (c) 2016 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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Jennings, et al.             Standards Track                    [Page 2]
RFC 7904                    RELOAD SIP Usage                October 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Registering AORs in the Overlay . . . . . . . . . . . . . . .   6
     3.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  Data Structure  . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Access Control  . . . . . . . . . . . . . . . . . . . . .   9
     3.4.  Overlay Configuration Document Extension  . . . . . . . .  10
   4.  Looking Up an AOR . . . . . . . . . . . . . . . . . . . . . .  11
     4.1.  Finding a Route to an AOR . . . . . . . . . . . . . . . .  11
     4.2.  Resolving an AOR  . . . . . . . . . . . . . . . . . . . .  12
   5.  Forming a Direct Connection . . . . . . . . . . . . . . . . .  12
     5.1.  Setting Up a Connection . . . . . . . . . . . . . . . . .  12
     5.2.  Keeping a Connection Alive  . . . . . . . . . . . . . . .  13
   6.  Using GRUUs . . . . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text