idnits 2.17.1 draft-zhang-bier-bierin6-01.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 (Apr 27, 2018) is 2190 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-05 == Outdated reference: A later version (-18) exists of draft-ietf-bier-ospf-bier-extensions-17 == 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 (~~), 4 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: October 29, 2018 Juniper Networks, Inc. 6 Apr 27, 2018 8 BIER in IPv6 9 draft-zhang-bier-bierin6-01 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 October 29, 2018. 40 Copyright Notice 42 Copyright (c) 2018 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 . . . . . . . . . . . . . . . . . . . . . . . . . 2 59 3. BIER Header . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 62 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 63 6.1. Normative References . . . . . . . . . . . . . . . . . . 4 64 6.2. Informative References . . . . . . . . . . . . . . . . . 4 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 67 1. Introduction 69 BIER [RFC8279] is a new architecture for the forwarding of multicast 70 data packets. It provides optimal forwarding through a "multicast 71 domain' and it does not necessarily precondition construction of a 72 multicast distribution tree, nor does it require intermediate nodes 73 to maintain any per-flow state. 75 [RFC8296] defines the BIER encapsulation format in MPLS and non-MPLS 76 environment that rely on MPLS labels or special ethernet type 77 support. In pure IPv6 environments a BIER packet could be forwarded 78 by means of simple IPv6 hop-by-hop processing only, without any new 79 hardware support. Ultimate hardware support is obviously possible 80 but the encapsulation is especially interesting for environments like 81 [RFC7368] where high throughput multicast forwarding performance is 82 not decisive and could be initially done in slow-path or end host 83 (assuming last-hop being IPv6 encapsulated). 85 This document defines native BIER IPv6 [RFC2460] encapsulation we 86 call BIERv6. This encapsulation is aligned with the format defined 87 in [RFC8296] for a non-mpls version. 89 This document uses terminology defined in [RFC8279]. 91 2. IPv6 Header 93 The BIER packet itself is the payload of an IPv6 frame. The 94 destination address field in IPv6 packet MAY be the neighbor's link- 95 local or one of the loopback interface addresses of that neighbor. 96 The destination address SHOULD be the BFR-prefix advertised by IGP/ 97 BGP extensions for BIER. TTL value of 1 MUST be used on the IPv6 98 packet. 100 The source address field in IPv6 packet MAY be the loopback interface 101 address of the sending BFIR. The address SHOULD be the BFR-prefix 102 advertised in IGP/BGP extension. 104 A new next-protocol type in IPv6 Next header field of TBD indicates 105 the following BIER packet. 107 The Flow-ID in the IPv6 packet SHOULD be copied from the entropy 108 field in the BIER encapsulation. 110 3. BIER Header 112 S bit in BIER header has no significance in this environment. It 113 should be set to 1 upon transmission, but it MUST be ignored upon 114 reception. 116 TC bits in BIER header have no significance in this environment since 117 the IPv6 packet TC takes precedence on processing. It should be set 118 to zero upon transmission, but it MUST be ignored upon reception. 120 The BIFT-id is used to indicate the combination of 121 normally; it should be set to the value advertised by the next-hop 122 BFR through e.g. IGP [I-D.ietf-bier-ospf-bier-extensions], 123 [I-D.zhang-bier-babel-extensions] or BGP 124 [I-D.ietf-bier-idr-extensions] extension for BIER. 126 The remaining fields defined in BIER header MUST assume the same 127 values and be afforded same treatement as specified in [RFC8296]. 129 4. IANA Considerations 131 IANA is requested to set up a new type of "Next header" registry 132 value for BIERv6 in the "Assigned Internet Protocol Numbers" 133 registry. 135 5. Security Considerations 137 General IPv6 and BIER security considerations apply. 139 6. References 140 6.1. Normative References 142 [I-D.ietf-bier-idr-extensions] 143 Xu, X., Chen, M., Patel, K., Wijnands, I., and T. 144 Przygienda, "BGP Extensions for BIER", draft-ietf-bier- 145 idr-extensions-05 (work in progress), March 2018. 147 [I-D.ietf-bier-ospf-bier-extensions] 148 Psenak, P., Kumar, N., Wijnands, I., Dolganow, A., 149 Przygienda, T., Zhang, Z., and S. Aldrin, "OSPFv2 150 Extensions for BIER", draft-ietf-bier-ospf-bier- 151 extensions-17 (work in progress), April 2018. 153 [I-D.zhang-bier-babel-extensions] 154 Zhang, Z. and T. Przygienda, "BIER in BABEL", draft-zhang- 155 bier-babel-extensions-01 (work in progress), June 2017. 157 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 158 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 159 December 1998, . 161 6.2. Informative References 163 [RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J. 164 Weil, "IPv6 Home Networking Architecture Principles", 165 RFC 7368, DOI 10.17487/RFC7368, October 2014, 166 . 168 [RFC8279] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 169 Przygienda, T., and S. Aldrin, "Multicast Using Bit Index 170 Explicit Replication (BIER)", RFC 8279, 171 DOI 10.17487/RFC8279, November 2017, 172 . 174 [RFC8296] Wijnands, IJ., Ed., Rosen, E., Ed., Dolganow, A., 175 Tantsura, J., Aldrin, S., and I. Meilik, "Encapsulation 176 for Bit Index Explicit Replication (BIER) in MPLS and Non- 177 MPLS Networks", RFC 8296, DOI 10.17487/RFC8296, January 178 2018, . 180 Authors' Addresses 182 Zheng(Sandy) Zhang 183 ZTE Corporation 185 EMail: zzhang_ietf@hotmail.com 186 Tony Przygienda 187 Juniper Networks, Inc. 189 EMail: prz@juniper.net