Internet-Draft submission

idnits 2.14.01 

/a/www/www6s/staging/draft-ietf-intareawg-mams-protocol-00.txt:

  Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed before draft submission.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

     No issues found here.

  Running in submission checking mode -- *not* checking nits according to
  http://www.ietf.org/id-info/checklist .
  ----------------------------------------------------------------------------


     No nits found.

INTAREA                                                      S. Kanugovi
Internet-Draft                                              S. Vasudevan
Intended status: Standards Track                                   Nokia
Expires: January 9, 2017                                     F. Baboescu
                                                                Broadcom
                                                            July 8, 2016


                  Multiple Access Management Protocol
                 draft-ietf-intareawg-mams-protocol-00

Abstract

   A communication network includes an access network element that
   delivers data to/from the user and an associated core network element
   that typically is the IP gateway having connectivity with the
   application servers.  Multiconnectivity scenarios are common where a
   device can be simultaneously connected to multiple communication
   networks based on different technology implementations and network
   architectures like Wi-Fi, LTE, DSL.  A smart combination and
   selection of access and core network paths can improve quality of
   experience that a user in a multiconnectivity scenario.  This
   document presents the problem statement and proposes solution
   principles.  It specifies the requirements and reference architecture
   for a multi access management services framework that can be used to
   flexibly select the best combination of uplink and downlink access
   and core network paths, ensuring better network efficiency and
   enhanced application performance.

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

   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 January 9, 2017.






Kanugovi, et al.         Expires January 9, 2017                [Page 1]
Internet-Draft                    MAMS                         July 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.

Table of Contents

   1.  Conventions used in this document . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Solution Principles . . . . . . . . . . . . . . . . . . . . .   4
   5.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  MAMS Reference Architecture . . . . . . . . . . . . . . . . .   6
   7.  MAMS call flow  . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   9
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Conventions used in this document

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

2.  Terminology

   "Client": The end-user device supporting connections with multiple
   access nodes, possibly over different access technologies.

   "Multiconnectivity Client": A client with multiple network
   connections.

   "Access network element": The functional element in the network that
   delivers user data packets to the client via a point-to-point access
   link like Wi-Fi airlink, LTE airlink, DSL.



Kanugovi, et al.         Expires January 9, 2017                [Page 2]