idnits 2.17.1 draft-bonica-6man-seg-end-opt-04.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 (July 7, 2019) is 1755 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) == Unused Reference: 'RFC4443' is defined on line 189, but no explicit reference was found in the text == Unused Reference: 'RFC8200' is defined on line 199, but no explicit reference was found in the text == Outdated reference: A later version (-06) exists of draft-bonica-spring-srv6-plus-01 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6man R. Bonica 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track J. Halpern 5 Expires: January 8, 2020 Ericsson 6 Y. Kamite 7 NTT Communications Corporation 8 T. Niwa 9 KDDI 10 N. So 11 F. Xu 12 Reliance Jio 13 G. Chen 14 Baidu 15 Y. Zhu 16 G. Yang 17 China Telecom 18 Y. Zhou 19 ByteDance 20 July 7, 2019 22 The Per-Segment Service Instruction (PSSI) Option 23 draft-bonica-6man-seg-end-opt-04 25 Abstract 27 SRv6+ encodes Per-Segment Service Instructions (PSSI) in a new IPv6 28 option, called the PSSI Option. This document describes the PSSI 29 Option. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at https://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on January 8, 2020. 48 Copyright Notice 50 Copyright (c) 2019 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (https://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 66 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 67 3. PSSI Identifiers . . . . . . . . . . . . . . . . . . . . . . 3 68 4. Option Format . . . . . . . . . . . . . . . . . . . . . . . . 3 69 5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 70 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 71 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 72 8. Normative References . . . . . . . . . . . . . . . . . . . . 4 73 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5 75 1. Introduction 77 An SRv6+ [I-D.bonica-spring-srv6-plus] path provides unidirectional 78 connectivity from its ingress node to its egress node. While an 79 SRv6+ path can follow the least cost path from ingress to egress, it 80 can also follow any other path. 82 An SRv6+ path contains one or more segments. A segment provides 83 unidirectional connectivity from its ingress node to its egress node. 85 SRv6+ paths are programmable. They support several instruction 86 types, including Per-Segment Service Instructions (PSSI). The 87 following are examples of PSSIs: 89 o Expose a packet to a firewall policy. 91 o Expose a packet to a sampling policy. 93 PSSIs are executed at segment egress nodes and can be used to 94 implement limited service chains. However, they do not provide an 95 alternative to the Network Service Header (NSH) [RFC8300]. 97 SRv6+ encodes PSSIs in a new IPv6 option, called the PSSI Option. 98 This document describes the PSSI Option. 100 2. Requirements Language 102 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 103 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 104 "OPTIONAL" in this document are to be interpreted as described in BCP 105 14 [RFC2119] [RFC8174] when, and only when, they appear in all 106 capitals, as shown here. 108 3. PSSI Identifiers 110 PSSI Identifiers identify PSSIs. They have domain-wide significance. 111 When a controller creates a limited service chain, also allocates a 112 PSSI Identifier. It then distributes the following information to 113 each node that contributes to the limited service chain: 115 o The PSSI Identifier. 117 o The PSSI that the node should execute when it receives a packet 118 that has the PSSI Identifier encoded within it. 120 4. Option Format 122 The PSSI Option contains the following fields: 124 o Option Type: 8-bit selector. PSSI option. Value TBD by IANA. 125 (Suggested value: 0x10). See Note below. 127 o Opt Data Len - 8-bit unsigned integer. Length of the option, in 128 octets, excluding the Option Type and Option Length fields. This 129 field MUST be set to 4. 131 o PSSI identifier - (32-bit selector). Identifies a PSSI. 133 The PSSI option MAY appear in any Destination Options header, 134 regardless of whether that Destination Options header precedes a 135 Routing header or an upper-layer header. The PSSI option MUST NOT 136 appear in a Hop-by-hop Options header. 138 NOTE : The highest-order two bits of the Option Type (i.e., the "act" 139 bits) are 00. These bits specify the action taken by a destination 140 node that does not recognize the option. The required action is to 141 skip over this option and continue processing the header. 143 The third highest-order bit of the Option Type (i.e., the "chg" bit) 144 is 0. This indicates that Option Data cannot be modified along the 145 path between the packet's source and its destination. 147 5. Security Considerations 149 The PSSI option shares many security concerns with IPv6 routing 150 headers. In particular, any boundary filtering protecting a domain 151 from external routing headers should also protect against external 152 PSSI options being processed inside a domain. This occurs naturally 153 if encapsulation is used to add routing headers to a packet. If 154 external routing headers are allowed, then protections must also 155 include ensuring that any provided PSSI option is properly protected, 156 e.g. with an IPSEC AH header or other suitable means. 158 As with Routing headers, the security assumption within a domain is 159 that the domain is trusted to provide, and to avoid improperly 160 modifying, the PSSI Option. 162 6. IANA Considerations 164 IANA is requested to allocate a cod epoint from the Destination 165 Options and Hop-by-hop Options registry 166 (https://www.iana.org/assignments/ipv6-parameters/ 167 ipv6-parameters.xhtml#ipv6-parameters-2). This option is called 168 "PSSI". The "act" bits are 00 and the "chg" bit is 0. (Suggested 169 value: 0x10). 171 7. Acknowledgements 173 Thanks to Fred Baker and Shizhang Bi for their careful review of this 174 document. 176 8. Normative References 178 [I-D.bonica-spring-srv6-plus] 179 Bonica, R., Hegde, S., Kamite, Y., Alston, A., Henriques, 180 D., Halpern, J., and J. Linkova, "IPv6 Support for Segment 181 Routing: SRv6+", draft-bonica-spring-srv6-plus-01 (work in 182 progress), July 2019. 184 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 185 Requirement Levels", BCP 14, RFC 2119, 186 DOI 10.17487/RFC2119, March 1997, 187 . 189 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 190 Control Message Protocol (ICMPv6) for the Internet 191 Protocol Version 6 (IPv6) Specification", STD 89, 192 RFC 4443, DOI 10.17487/RFC4443, March 2006, 193 . 195 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 196 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 197 May 2017, . 199 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 200 (IPv6) Specification", STD 86, RFC 8200, 201 DOI 10.17487/RFC8200, July 2017, 202 . 204 [RFC8300] Quinn, P., Ed., Elzur, U., Ed., and C. Pignataro, Ed., 205 "Network Service Header (NSH)", RFC 8300, 206 DOI 10.17487/RFC8300, January 2018, 207 . 209 Authors' Addresses 211 Ron Bonica 212 Juniper Networks 213 2251 Corporate Park Drive 214 Herndon, Virginia 20171 215 USA 217 Email: rbonica@juniper.net 219 Joel Halpern 220 Ericsson 221 P. O. Box 6049 222 Leesburg, Virginia 20178 223 USA 225 Email: joel.halpern@ericsson.com 227 Yuji Kamite 228 NTT Communications Corporation 229 3-4-1 Shibaura, Minato-ku 230 Tokyo 108-8118 231 Japan 233 Email: : y.kamite@ntt.com 234 Tomonobu Niwa 235 KDDI 236 3-22-7, Yoyogi, Shibuya-ku 237 Tokyo 151-0053 238 JP 240 Email: to-niwa@kddi.com 242 Ning So 243 Reliance Jio 244 3010 Gaylord PKWY, Suite 150 245 Frisco, Texas 75034 246 USA 248 Email: Ning.So@ril.com 250 Fengman Xu 251 Reliance Jio 252 3010 Gaylord PKWY, Suite 150 253 Frisco, Texas 75034 254 USA 256 Email: Fengman.Xu@ril.com 258 Gang Chen 259 Baidu 260 No.10 Xibeiwang East Road Haidian District 261 Beijing 100193 262 P.R. China 264 Email: phdgang@gmail.com 266 Yongqing Zhu 267 China Telecom 268 109 West Zhongshan Ave, Tianhe District 269 Guangzhou 270 P.R. China 272 Email: zhuyq.gd@chinatelecom.cn 273 Guangming Yang 274 China Telecom 275 109 West Zhongshan Ave, Tianhe District 276 Guangzhou 277 P.R. China 279 Email: yanggm.gd@chinatelecom.cn 281 Yifeng Zhou 282 ByteDance 283 Building 1, AVIC Plaza, 43 N 3rd Ring W Rd Haidian District 284 Beijing 100000 285 P.R. China 287 Email: yifeng.zhou@bytedance.com