Associated Channel over IPv6
draft-yang-rtgwg-ipv6-associated-channel-00

Document Type Active Internet-Draft (individual)
Authors Fan Yang  , Mach Chen  , Tianran Zhou 
Last updated 2021-02-22
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
On Agenda spring at IETF-110
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
RTGWG Working Group                                              F. Yang
Internet-Draft                                                   M. Chen
Intended status: Standards Track                                 T. Zhou
Expires: August 26, 2021                             Huawei Technologies
                                                       February 22, 2021

                      Associated Channel over IPv6
              draft-yang-rtgwg-ipv6-associated-channel-00

Abstract

   In this document, an associated channel is introduced to provide a
   control channel based on IPv6, carrying types of control and
   management messages.  By using the associated channel, messages can
   be transmitted between the network nodes to provide functions like
   path identification, OAM, protection switchover signaling, etc.,
   targeting to provide high quality SLA guarantee to service.

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

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 August 26, 2021.

Copyright Notice

   Copyright (c) 2021 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Yang, et al.             Expires August 26, 2021                [Page 1]
Internet-Draft  draft--yang-rtgwg-ipv6-associated-channel  February 2021

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Associated Channel  . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Identification of Associated Channel  . . . . . . . . . .   3
     3.2.  ACH TLV to Carry Message  . . . . . . . . . . . . . . . .   3
     3.3.  Encapsulation of ACH TLV in IPv6  . . . . . . . . . . . .   4
       3.3.1.  Encapsulated in IPv6 Destination Options Header . . .   5
       3.3.2.  Encapsulated in IPv6 Hop-by-Hop Options Header  . . .   5
       3.3.3.  Encapsulated in IPv6 Segment Routing Header . . . . .   6
       3.3.4.  Encapsulated in Payload . . . . . . . . . . . . . . .   6
     3.4.  Processing of ACH TLV . . . . . . . . . . . . . . . . . .   7
   4.  Applicability . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Path Identification . . . . . . . . . . . . . . . . . . .   7
     4.2.  OAM . . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  Assist to Protection Switchover . . . . . . . . . . . . .   7
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   IPv6 is becoming widely accepted to provide the connectivity in many
   new emerging scenarios, including Cloud Network convergence, Cloud-
   Cloud interconnection, 5G vertical industries, Internet of Things, as
   well as the legacy networks migrating towards SR over IPv6.  However,
   IP packet is locally lookup, and forwarded hop by hop without aware
   of the forwarding path.  Path segment over SRv6
   [I-D.ietf-spring-srv6-path-segment] provides a good solution to
   identify an SR path over IPv6, but can only be applicable in source
   routing paradigm.

Yang, et al.             Expires August 26, 2021                [Page 2]
Internet-Draft  draft--yang-rtgwg-ipv6-associated-channel  February 2021
Show full document text