idnits 2.17.1 draft-zhang-bier-bierin6-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 26, 2017) is 2368 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-10) exists of draft-ietf-bier-idr-extensions-03 == Outdated reference: A later version (-12) exists of draft-ietf-bier-mpls-encapsulation-10 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-09 == Outdated reference: A later version (-10) exists of draft-zhang-bier-babel-extensions-01 ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BIER Z. Zhang 3 Internet-Draft ZTE Corporation 4 Intended status: Standards Track A. Przygienda 5 Expires: April 29, 2018 Juniper Networks, Inc. 6 October 26, 2017 8 BIER in IPv6 9 draft-zhang-bier-bierin6-00 11 Abstract 13 BIER is a new architecture for the forwarding of multicast data 14 packets. This document defines native IPv6 encapsulation for BIER 15 hop-by-hop forwarding or BIERin6 for short. 17 Requirements Language 19 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 21 document are to be interpreted as described in RFC2119. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on April 29, 2018. 40 Copyright Notice 42 Copyright (c) 2017 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. IPv6 Header . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 3. BIER Header . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 62 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 6.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 67 1. Introduction 69 BIER [I-D.ietf-bier-architecture] is a new architecture for the 70 forwarding of multicast data packets. It provides optimal forwarding 71 through a "multicast domain' and it does not necessarily precondition 72 construction of a multicast distribution tree, nor does it require 73 intermediate nodes to maintain any per-flow state. 75 [I-D.ietf-bier-mpls-encapsulation] defines the BIER encapsulation 76 format in MPLS and non-MPLS environment that rely on MPLS labels or 77 special ethernet type support. In pure IPv6 environments a BIER 78 packet could be forwarded by means of simple IPv6 hop-by-hop 79 processing only, without any new hardware support. Ultimate hardware 80 support is obviously possible but the encapsulation is especially 81 interesting for environments like [RFC7368] where high throughput 82 multicast forwarding performance is not decisive and could be 83 initially done in slow-path or end host (assuming last-hop being IPv6 84 encapsulated). 86 This document defines native BIER IPv6 [RFC2460] encapsulation we 87 call BIERv6. This encapsulation is aligned with the format defined 88 in [I-D.ietf-bier-mpls-encapsulation] for a non-mpls version. 90 This document uses terminology defined in 91 [I-D.ietf-bier-architecture]. 93 2. IPv6 Header 95 The BIER packet itself is the payload of an IPv6 frame. The 96 destination address field in IPv6 packet MAY be the neighbor's link- 97 local or one of the loopback interface addresses of that neighbor. 98 The destination address SHOULD be the BFR-prefix advertised by IGP/ 99 BGP extensions for BIER. TTL value of 1 MUST be used on the IPv6 100 packet. 102 The source address field in IPv6 packet MAY be the loopback interface 103 address of the sending BFIR. The address SHOULD be the BFR-prefix 104 advertised in IGP/BGP extension. 106 A new next-protocol type in IPv6 Next header field of TBD indicates 107 the following BIER packet. 109 The Flow-ID in the IPv6 packet SHOULD be copied from the entropy 110 field in the BIER encapsulation. 112 3. BIER Header 114 S bit in BIER header has no significance in this environment. It 115 should be set to 1 upon transmission, but it MUST be ignored upon 116 reception. 118 TC bits in BIER header have no significance in this environment since 119 the IPv6 packet TC takes precedence on processing. It should be set 120 to zero upon transmission, but it MUST be ignored upon reception. 122 The BIFT-id is used to indicate the combination of 123 normally; it should be set to the value advertised by the next-hop 124 BFR through e.g. IGP [I-D.ietf-bier-ospf-bier-extensions], 125 [I-D.zhang-bier-babel-extensions] or BGP 126 [I-D.ietf-bier-idr-extensions] extension for BIER. 128 The remaining fields defined in BIER header MUST assume the same 129 values and be afforded same treatement as specified in 130 [I-D.ietf-bier-mpls-encapsulation]. 132 4. IANA Considerations 134 IANA is requested to set up a new type of "Next header" registry 135 value for BIERv6 in the "Assigned Internet Protocol Numbers" 136 registry. 138 5. Security Considerations 140 General IPv6 and BIER security considerations apply. 142 6. References 144 6.1. Normative References 146 [I-D.ietf-bier-architecture] 147 Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and 148 S. Aldrin, "Multicast using Bit Index Explicit 149 Replication", draft-ietf-bier-architecture-08 (work in 150 progress), September 2017. 152 [I-D.ietf-bier-idr-extensions] 153 Xu, X., Chen, M., Patel, K., Wijnands, I., and T. 154 Przygienda, "BGP Extensions for BIER", draft-ietf-bier- 155 idr-extensions-03 (work in progress), August 2017. 157 [I-D.ietf-bier-mpls-encapsulation] 158 Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., 159 Aldrin, S., and I. Meilik, "Encapsulation for Bit Index 160 Explicit Replication in MPLS and non-MPLS Networks", 161 draft-ietf-bier-mpls-encapsulation-10 (work in progress), 162 October 2017. 164 [I-D.ietf-bier-ospf-bier-extensions] 165 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 166 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPF Extensions 167 for BIER", draft-ietf-bier-ospf-bier-extensions-09 (work 168 in progress), October 2017. 170 [I-D.zhang-bier-babel-extensions] 171 Zhang, Z. and T. Przygienda, "BIER in BABEL", draft-zhang- 172 bier-babel-extensions-01 (work in progress), June 2017. 174 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 175 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 176 December 1998, . 178 6.2. Informative References 180 [RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J. 181 Weil, "IPv6 Home Networking Architecture Principles", 182 RFC 7368, DOI 10.17487/RFC7368, October 2014, 183 . 185 Authors' Addresses 187 Zheng(Sandy) Zhang 188 ZTE Corporation 190 EMail: zzhang_ietf@hotmail.com 192 Tony Przygienda 193 Juniper Networks, Inc. 195 EMail: prz@juniper.net