[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 draft-ietf-sfc-nsh-broadband-allocation

Service Function Chaining                                        W. Meng
Internet-Draft                                                   C. Wang
Intended status: Standards Track                         ZTE Corporation
Expires: November 11, 2016                                  May 10, 2016


                     NSH Context Header - Broadband
               draft-meng-sfc-nsh-broadband-allocation-01

Abstract

   This document provides a recommended allocation of the mandatory
   fixed context headers for a Network Service Header (NSH) within the
   broadband service provider network context.

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 November 11, 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.





Meng & Wang             Expires November 11, 2016               [Page 1]


Internet-Draft       NSH Context Header - Broadband             May 2016


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Convention and Terminology . . . . . . . . . . . . . . . . . .  4
   3.  Network Service Header (NSH) Context Headers . . . . . . . . .  5
   4.  Recommended Broadband Context Allocation . . . . . . . . . . .  6
   5.  Broadband Allocation Specifics . . . . . . . . . . . . . . . .  7
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
   7.  Normative References . . . . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10









































Meng & Wang             Expires November 11, 2016               [Page 2]


Internet-Draft       NSH Context Header - Broadband             May 2016


1.  Introduction

   The objective of SFC is trying to unload services from nodes in
   traditional network and deal with such services through service
   function chains.

   As increasingly large number of customers, The possibility of
   deployment SFC in broadband network seems emergency.  And this
   document is aimed to provides a recommended allocation of the
   mandatory fixed context headers for a Network Service Header (NSH) in
   broadband network.








































Meng & Wang             Expires November 11, 2016               [Page 3]


Internet-Draft       NSH Context Header - Broadband             May 2016


2.  Convention and Terminology

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

   The terms about SFC are defined in [I-D.ietf-sfc-problem-statement].












































Meng & Wang             Expires November 11, 2016               [Page 4]


Internet-Draft       NSH Context Header - Broadband             May 2016


3.  Network Service Header (NSH) Context Headers

   In Service Function Chaining, the Network Service Header is composed
   of a 4-byte base header (BH1), a 4-byte service path header (SH1) and
   four mandatory 4-byte context headers (CH1-CH4).

   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |Ver|O|C|R|R|R|R|R|R|   Length  | MD Type = 0x01| Next Protocol | BH1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |          Service Path ID                      | Service Index | SH1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Mandatory Context Header 1                     | CH1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Mandatory Context Header 2                     | CH2
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Mandatory Context Header 3                     | CH3
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                Mandatory Context Header 4                     | CH4
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

              Figure 1: Network Service Header - MD Type 0x01





























Meng & Wang             Expires November 11, 2016               [Page 5]


Internet-Draft       NSH Context Header - Broadband             May 2016


4.  Recommended Broadband Context Allocation

   The following context header allocation provides information to
   support service function chaining in a broadband service provider
   network.

   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Source Node ID         |    Source Interface ID          |CH1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                  User ID/Accouting ID                         | CH2
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               vlan ID               |       reserved          | CH3
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           reserved                            | CH4
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

                Figure 2: NSH Broadband Context Allocation

































Meng & Wang             Expires November 11, 2016               [Page 6]


Internet-Draft       NSH Context Header - Broadband             May 2016


5.  Broadband Allocation Specifics

   Source Node ID: An identifier indicating the source device where the
   original traffic initially entered the Service Function Chain.  This
   identifier is unique within an SFC-enabled domain.

   Source Interface ID: An identifier indicating the source interface
   where the original traffic initially entered the Service Function
   Chain.  This identifier is scoped within the context of the Source
   Node ID.

   User ID: The user ID indicates the user who access to the broadband
   network.  It is unique in administrative domain.

   Vlan ID : Together with Source Node ID and Source Interface ID, they
   indicate the access point of the user accessing.



































Meng & Wang             Expires November 11, 2016               [Page 7]


Internet-Draft       NSH Context Header - Broadband             May 2016


6.  IANA Considerations

   This memo includes no request to IANA.
















































Meng & Wang             Expires November 11, 2016               [Page 8]


Internet-Draft       NSH Context Header - Broadband             May 2016


7.  Normative References

   [I-D.ietf-sfc-nsh]
              Quinn, P. and U. Elzur, "Network Service Header",
              draft-ietf-sfc-nsh-04 (work in progress), March 2016.

   [I-D.ietf-sfc-problem-statement]
              Quinn, P. and T. Nadeau, "Service Function Chaining
              Problem Statement", draft-ietf-sfc-problem-statement-13
              (work in progress), February 2015.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
              RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC2865]  Rigney, C., Willens, S., Rubens, A., and W. Simpson,
              "Remote Authentication Dial In User Service (RADIUS)",
              RFC 2865, DOI 10.17487/RFC2865, June 2000,
              <http://www.rfc-editor.org/info/rfc2865>.

   [RFC7498]  Quinn, P., Ed. and T. Nadeau, Ed., "Problem Statement for
              Service Function Chaining", RFC 7498, DOI 10.17487/
              RFC7498, April 2015,
              <http://www.rfc-editor.org/info/rfc7498>.


























Meng & Wang             Expires November 11, 2016               [Page 9]


Internet-Draft       NSH Context Header - Broadband             May 2016


Authors' Addresses

   Wei Meng
   ZTE Corporation
   No.50 Software Avenue, Yuhuatai District
   Nanjing
   China

   Email: meng.wei2@zte.com.cn,vally.meng@gmail.com


   Cui Wang
   ZTE Corporation
   No.50 Software Avenue, Yuhuatai District
   Nanjing
   China

   Email: wang.cui1@zte.com.cn

































Meng & Wang             Expires November 11, 2016              [Page 10]


Html markup produced by rfcmarkup 1.127, available from https://tools.ietf.org/tools/rfcmarkup/