Segment Routing Traffic Engineering Leveraging Existing IPv6 Interface Addresses
draft-dukes-6man-sr-te-intf-address-00

Document Type Active Internet-Draft (individual)
Last updated 2020-06-12
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized (tools) 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)
6MAN                                                       D. Dukes, Ed.
Internet-Draft                                          C. Filsfils, Ed.
Intended status: Informational                             Cisco Systems
Expires: December 14, 2020                                 June 12, 2020

 Segment Routing Traffic Engineering Leveraging Existing IPv6 Interface
                               Addresses
                 draft-dukes-6man-sr-te-intf-address-00

Abstract

   This document illustrates how an operator may re-use an existing IPv6
   address allocation within its domain to deliver SR-based Traffic
   Engineering service.

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 December 14, 2020.

Copyright Notice

   Copyright (c) 2020 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.

Dukes & Filsfils        Expires December 14, 2020               [Page 1]
Internet-Draft  SR TE Leveraging Existing IPv6 Addresses       June 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Reference Topology  . . . . . . . . . . . . . . . . . . . . .   2
   3.  Address Allocation  . . . . . . . . . . . . . . . . . . . . .   3
   4.  SID Bound To Existing Interface Address . . . . . . . . . . .   3
   5.  Life Of A Packet  . . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Inter SR Domain . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  Intra SR Domain . . . . . . . . . . . . . . . . . . . . .   4
   6.  Upper-Layer Header Processing . . . . . . . . . . . . . . . .   5
     6.1.  ICMPv6 Echo Request and Reply . . . . . . . . . . . . . .   5
     6.2.  ICMPv6 Echo Request via an SR Policy  . . . . . . . . . .   6
     6.3.  SSH Session Initiation  . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   9.  Ecosystem . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   This document illustrates how an operator may re-use an existing IPv6
   address allocation within its domain to deliver SR-based Traffic
   Engineering service by describing:

   o  A reference topology with IPv6 address allocation.

   o  Binding a SID behavior to existing IPv6 addresses.

   o  The life of a packet forwarded via an SR policy.

   o  Upper-layer header processing for a SID bound to an existing IPv6
      address.

   The illustrations cover traffic engineering (TE) SR policy between
   two border routers of the domain and two hosts of the domain.

2.  Reference Topology

   The reference topology is the same as Section 6.2 of [RFC8754].

Dukes & Filsfils        Expires December 14, 2020               [Page 2]
Internet-Draft  SR TE Leveraging Existing IPv6 Addresses       June 2020

              + * * * * * * * * * * * * * * * * * * * * +
              *         [8]                [9]          *
                         |                  |
              *          |                  |           *
      [1]----[3]--------[5]----------------[6]---------[4]---[2]
              *          |                  |           *
                         |                  |
              *          |                  |           *
                         +--------[7]-------+
              *                                         *
              + * * * * * * *  SR domain  * * * * * * * +
Show full document text