Network based Bonding solution for Hybrid Access
draft-muley-network-based-bonding-hybrid-access-01

Document Type Active Internet-Draft (individual)
Last updated 2017-02-06
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)
Internet Area WG                                          Praveen Muley
Internet Draft                                           Wim Henderickx
Intended status: Informational                                    Nokia
Expires: August 5, 2017                                      Geng Liang
                                                           China Mobile
                                                                Hans Liu
                                                             D-Link Corp
                                                          Loris Cardullo
                                                         Jonathan Newton
                                                                Vodafone
                                                            SungHoon Seo
                                                           Korea Telecom
                                                           Sagiv Draznin
                                                        Verizon Wireless
                                                         Basavaraj Patil
                                                                    AT&T
                                                       February 6, 2017

             Network based Bonding solution for Hybrid Access
            draft-muley-network-based-bonding-hybrid-access-01

Abstract

   In order to address increasing bandwidth demands, operators are
   considering bundling of multiple heterogeneous access networks
   (Hybrid access) for residential and enterprise customers. This
   document describes a solution for Hybrid access and covers the use
   case scenarios.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

Status of this Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts. The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

Muley et al.            Expires August 5, 2017                 [Page 1]
Internet-Draft      Network based Bonding solution        February 2017

   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."

   This Internet-Draft will expire on August 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. 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. Reference Architecture.........................................4
   4. Network Based Bonding Solution Overview........................5
      4.1. Separate BNG and PGW......................................5
      4.2. Integrated BNG and SGW/PGW................................6
   5. HAG Function...................................................7
      5.1. Address Assignment........................................7
         5.1.1. Separate BNG and PGW.................................7
         5.1.2. Integrated BNG and SGW/PGW...........................8
      5.2. Setup and Tunnel Management...............................9
      5.3. Traffic distribution policies............................10
      5.4. Path Management..........................................11
      5.5. Backward compatibility...................................12
   6. Applicability in Mobile networks..............................12
   7. Inter-working with MP-TCP.....................................14
   8. Security Considerations.......................................14
   9. IANA considerations...........................................15
Show full document text