Operator-Assisted Relay Service Architecture (OARS)
draft-wang-rtcweb-oars-02

Document Type Active Internet-Draft (individual)
Last updated 2017-04-05
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RTCWEB Working Group                                           A.Wang
Internet Draft                                           China Telecom
                                                                  B.Liu
                                                    Huawei Technologies
                                                               J.Uberti
                                                                 Google
                                                              Peng.Ding
                                                          China Telecom
Intended status: Standard Track                           April 6, 2017
Expires: October 5, 2017

            Operator-Assisted Relay Service Architecture (OARS)
                       draft-wang-rtcweb-oars-02.txt

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79. This document may not be modified,
   and derivative works of it may not be created, and it may not be
   published except as an Internet-Draft.

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79. This document may not be modified,
   and derivative works of it may not be created, except to publish it
   as an RFC and to translate it into languages other than English.

   It is for publication as an RFC or to translate it into languages
   other than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time.  It is inappropriate to use Internet-Drafts as
   reference material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

<Wang,Liu,Uberti&Ding> Expires October 5, 2017              [Page 1]
Internet-Draft  Operator-Assisted Relay Service Architecture (OARS)
   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on October 5, 2017.

Copyright Notice

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

Abstract

    This document proposes a new relay-based NAT traversal architecture
    called OARS which could simplify the data communication process
    between two hosts that locates behind some non-BEHAVE compliant
    [RFC4787] [RFC5382] NAT devices.  The key mechanism in OARS is the
    newly defined "Couple" message which allows the Relay servers to be
    easily incorporated into existing CGN/CDN nodes which are already
    deployed within the network in a distributed manner.
Table of Contents

   1. Introduction ................................................ 3
      1.1. Motivations ............................................ 3
      1.2. Relationship with TURN.................................. 5
   2. Conventions used in this document............................ 5
   3. Solution Overview ........................................... 6
      3.1. Reference Architecture of OARS ..........................6
      3.2. Solution Rationale...................................... 7
         3.2.1. Get_RS_Token()..................................... 7
         3.2.2. Get_Optimal_Relay()................................ 7
         3.2.3. Get_Relay_Reflex()................................. 7
         3.2.4. Couple() .......................................... 7
         3.2.5. Data() ............................................ 8
   4. Detailed Example ............................................ 8
      4.1. Procedures of Communication between two IPv4 hosts.......8
      4.2. Procedures of IPv4 and IPv6 Host Communication...........9
   5. OARS Benefits .............................................. 10
   6. OARS Deployment Considerations.............................. 11
   7. Security Considerations..................................... 11
   8. IANA Considerations ........................................ 11
   9. Conclusions ................................................ 11
   10. Acknowledgements .......................................... 11
Show full document text