Flow Aware IPv6 Segment Routing
draft-vandevelde-spring-flow-aware-v6transport-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-09
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)
SPRING Working Group                                G. Van de Velde, Ed.
Internet-Draft                                                     Nokia
Intended status: Standards Track                        G. Fioccola, Ed.
Expires: September 10, 2017                               Telecom Italia
                                                                P. Muley
                                                                   Nokia
                                                           March 9, 2017

                    Flow Aware IPv6 Segment Routing
           draft-vandevelde-spring-flow-aware-v6transport-00

Abstract

   Flow-Aware transport of Pseudowires over an MPLS Packet Switched
   Network (RFC6391) introduces an ECMP use-case, making assumption that
   the payload of a pseudowire comprises of a number of distinct flows.
   RFC6391 provides a mechanism for fine flow granularity beyond the
   individual pseudowire, helping better flow granularity for ECMP
   purpose.  To identify the granular pseudowire flows the concept of
   MPLS Flow Label is introduced.  Furthermore RFC6391 defines the
   required LDP protocol extensions to exchange the MPLS Flow Label
   between LDP speakers.

   Another method to exchange MPLS flow labels is found in draft-ietf-
   bess-fat-pw-bgp.  Draft-ietf-bess-fat-pw-bgp defines extensions
   required to synchronise flow label state between PEs using BGP-based
   signalling procedures.  This draft assumes MPLS is the transport
   technology used.

   This draft extends the applicability of draft-ietf-bess-fat-pw-bgp
   and uses the BGP derived flow label for IPv6 Segment Routing
   transport.  The PE responsible for imposing the IPv6 Segment Routing
   top level header will in addition to an IPv6 header AND the IPv6
   Source Routing header ALSO impose the BGP derived Flow Label as the
   IPv6 outer header flow Label.  This functionality will provide fine
   ECMP granularity of IPv6 Segment routing enabled pseudowire transport
   services.

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

Van de Velde, et al.   Expires September 10, 2017               [Page 1]
Internet-Draft       Flow Aware IPv6 Segment Routing          March 2017

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 September 10, 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.  Operation . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation and Use Case . . . . . . . . . . . . . . . . . . .   4
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

Van de Velde, et al.   Expires September 10, 2017               [Page 2]
Internet-Draft       Flow Aware IPv6 Segment Routing          March 2017
Show full document text