ForCES architecture CUSP applicability
draft-haleplidis-bcause-forces-gap-analysis-01

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized 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 Engineering Task Force                            E. Haleplidis
Internet-Draft
Intended status: Informational                             J. Hadi Salim
Expires: May 7, 2020                                   Mojatatu Networks
                                                        November 4, 2019

                 ForCES architecture CUSP applicability
             draft-haleplidis-bcause-forces-gap-analysis-01

Abstract

   This document provides a gap-analysis on how the ForCES architecture
   meets the requirements for CUSP.  In addition it provides a ForCES
   XML model that implements the current proposed CUSP information
   model.

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 https://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 May 7, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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.

Haleplidis & Hadi Salim    Expires May 7, 2020                  [Page 1]
Internet-Draft               ForCES For CUSP               November 2019

Table of Contents

   1.  Terminology and Conventions . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  ForCES overview . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  ForCES protocol . . . . . . . . . . . . . . . . . . . . .   4
     3.2.  ForCES Model  . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Meeting CUSP requirements . . . . . . . . . . . . . . . . . .   8
     4.1.  Transmit information tables . . . . . . . . . . . . . . .   8
     4.2.  Message Priority  . . . . . . . . . . . . . . . . . . . .   9
     4.3.  Reliability . . . . . . . . . . . . . . . . . . . . . . .   9
     4.4.  Support for secure communication  . . . . . . . . . . . .  10
     4.5.  Version negotiation . . . . . . . . . . . . . . . . . . .  10
     4.6.  Capability Exchange . . . . . . . . . . . . . . . . . . .  10
     4.7.  CP primary/backup capability  . . . . . . . . . . . . . .  11
     4.8.  Event Notification  . . . . . . . . . . . . . . . . . . .  11
     4.9.  Query Statistics  . . . . . . . . . . . . . . . . . . . .  12
     4.10. Beyond the CUSP requirements  . . . . . . . . . . . . . .  12
   5.  Control and user plane information models . . . . . . . . . .  12
     5.1.  Information model for the Control Plane . . . . . . . . .  12
       5.1.1.  User related information  . . . . . . . . . . . . . .  12
       5.1.2.  Interface related information . . . . . . . . . . . .  18
       5.1.3.  Device related information  . . . . . . . . . . . . .  19
     5.2.  Information model for User Plane  . . . . . . . . . . . .  21
   6.  ForCES XML model for CUSP info model  . . . . . . . . . . . .  25
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  38
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  38
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  38
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  38
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  38
     10.2.  Informative References . . . . . . . . . . . . . . . . .  39
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  40

1.  Terminology and Conventions

1.1.  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 [RFC2119].

1.2.  Definitions

   This document reiterates the terminology defined by the ForCES
   architecture in various documents for the sake of clarity.

Haleplidis & Hadi Salim    Expires May 7, 2020                  [Page 2]
Show full document text