Encapsulating Non-MPLS-BIER in UDP
draft-xu-bier-non-mpls-encap-over-udp-03

Document Type Active Internet-Draft (individual)
Last updated 2018-07-21
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Network Working Group                                              X. Xu
Internet-Draft                                              Alibaba Inc.
Intended status: Standards Track                             G. Shepherd
Expires: January 21, 2019                                          Cisco
                                                           July 20, 2018

                   Encapsulating Non-MPLS-BIER in UDP
                draft-xu-bier-non-mpls-encap-over-udp-03

Abstract

   Bit Index Explicit Replication (BIER) is a new multicast forwarding
   paradigm which doesn't require an explicit tree-building protocol nor
   intermediate routers to maintain any multicast state.  BIER has two
   types of encapsulation formats: one is MPLS-BIER encapsulation, the
   other is non-MPLS-BIER encapsulation.  This document proposes a
   mechanism of encapsulating non-MPLS-BIER packets over UDP tunnels.

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 January 21, 2019.

Copyright Notice

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

Xu & Shepherd           Expires January 21, 2019                [Page 1]
Internet-Draft     Encapsulating Non-MPLS-BIER in UDP          July 2018

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Encapsulation in UDP  . . . . . . . . . . . . . . . . . . . .   3
   4.  Processing Procedures . . . . . . . . . . . . . . . . . . . .   4
   5.  Congestion Considerations . . . . . . . . . . . . . . . . . .   5
   6.  Applicability Statements  . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   6
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   Bit Index Explicit Replication (BIER) [RFC8279] is a new multicast
   forwarding paradigm which doesn't require an explicit tree-building
   protocol nor intermediate routers to maintain any multicast state.
   As described in Section 6.9 of [RFC8279], a BFR may need to tunnel a
   BIER packet over a certain kind of tunnel, e.g., UDP tunnel.

   [RFC8296] defines two types of BIER encapsulation formats: one is
   MPLS-BIER encapsulation, the other is non-MPLS-BIER encapsulation.
   MPLS-BIER packets can be transported over UDP tunnels by using the
   MPLS-in-UDP encapsulation as described in [RFC7510] . This document
   proposes a mechanism of encapsulating non-MPLS-BIER packets over UDP
   tunnels.

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

2.  Terminology

   This memo makes use of the terms defined in [RFC8279]and [RFC8296].

Xu & Shepherd           Expires January 21, 2019                [Page 2]
Internet-Draft     Encapsulating Non-MPLS-BIER in UDP          July 2018

3.  Encapsulation in UDP

   Non-MPLS-BIER-in-UDP encapsulation format is shown as follows:

        0                   1                   2                   3
        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
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Show full document text