idnits 2.17.1 draft-cheng-spring-srv6-encoding-network-sliceid-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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 4) being 69 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 9 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 24, 2021) is 909 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) No issues found here. Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 SPRING WG W. Cheng 2 Internet-Draft China Mobile 3 Intended status: Standards Track C. Filsfils 4 Expires: April 24, 2022 Cisco Systems 5 Changwang. Lin 6 H3C Corporation 7 L. Gong 8 China Mobile 9 October 24, 2021 11 Encoding Network Slice Identification for SRv6 12 draft-cheng-spring-srv6-encoding-network-sliceid-01 14 Abstract 16 This document describe a method to encode network slicing identifier 17 within SRv6 domain. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at https://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on April 24, 2022. 36 Copyright Notice 38 Copyright (c) 2021 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (https://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 55 2. Slice Identifier . . . . . . . . . . . . . . . . . . . . . . 2 56 3. SLID Assignment . . . . . . . . . . . . . . . . . . . . . . . 2 57 4. Per-Slice Forwarding . . . . . . . . . . . . . . . . . . . . 3 58 5. Backward Compatibility . . . . . . . . . . . . . . . . . . . 3 59 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 60 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 62 7.2. Informative References . . . . . . . . . . . . . . . . . 4 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 65 1. Introduction 67 SRv6 Network Programming[RFC8986] enables the creation of overlays 68 with underlay optimization to be deployed in an SR domain[RFC8402]. 70 As defined in [RFC8754], all inter-domain packets are encapsulated 71 for the part of the packet journey that is within the SR domain. The 72 outer IPv6 header [RFC8200] is originated by a node of the SR domain 73 and is destined to a node of the SR domain. 75 This document describes a novel method to encode slice identifier 76 in the outer IPv6 header of an SR domain. Unlike other proposed 77 methods before, which will bring side effects on existed functions, 78 by encoding network slicing identifier in the source IPv6 address of 79 the outer header, this method avoids the drawbacks which previous 80 proposals incur. 82 1.1. Requirements Language 84 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 85 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 86 document are to be interpreted as described in RFC 2119 [RFC2119]. 88 2. Slice Identifier 90 Slice identifier (SLID) is a 16-bit Identifier which uniquely defines 91 a slicing of the network in the specified SR domain. 93 3. SLID Assignment 95 When SR domain enables network slicing, the ingress PE should reserve 96 16 least significant bits in its locater for slicing use. When a 97 packet enters the SR domain from an ingress PE, the ingress PE 98 encapsulates the packet in an outer IPv6 header and optional SRH as 99 defined in [RFC8754]. The ingress PE MAY also classify the packet 100 into a slice and set the slice identifier as follows: 102 o Set the SPI bit (SLID Presence Indicator) in the Traffic Class 103 field of the outer IPv6 header. 105 o Write this SLID in the 16 least significant bits of source address 106 of the outer IPv6 header. 108 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 109 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 110 |Version| SPI Bit | Flow Label | 111 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 112 | Payload Length | Next Header | Hop Limit | 113 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 114 | | 115 + + 116 | | 117 + Source Address + 118 | | 119 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 120 | | SLID | 121 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 122 | | 123 + + 124 | | 125 + Destination Address + 126 | | 127 + + 128 | | 129 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 131 The choice of the SPI bit from within the IPv6 Traffic Class field is 132 a domain-wide configuration and is outside the scope of this 133 document. 135 4. Per-Slice Forwarding 137 Any router within the SR domain that forwards a packet with SPI bit 138 set uses the SLID to select a slice and apply per-slice policies. 140 5. Backward Compatibility 142 PE routers that do not set the SPI bit do not enable the SLID 143 semantic of the IPv6 source address bits. Hence, SLID-aware routers 144 would not attempt to classify these packets into a slice. 146 Any router that does not process the SPI nor the SLID forwards 147 packets as usual. 149 6. Acknowledgements 151 The authors would like to thank AAAA, BBBB and CCCC for their 152 insightful feedback on this document. 154 7. References 156 7.1. Normative References 158 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 159 Requirement Levels", BCP 14, RFC 2119, 160 DOI 10.17487/RFC2119, March 1997, 161 . 163 [RFC8986] Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 164 Matsushima, S., and Z. Li, 165 Segment Routing over IPv6 (SRv6) Network Programming, 166 RFC 8986, DOI 10.17487/RFC8986, February 2021, 167 . 169 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 170 Decraene, B., Litkowski, S., and R. Shakir, "Segment 171 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 172 July 2018, . 174 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 175 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 176 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 177 . 179 7.2. Informative References 181 [RFC8200] Deering, S., and Hinden, D., "Internet Protocol, Version 6 182 (IPv6) Specification", RFC 8200, DOI 10.17487/RFC8200, 183 July 2017, . 185 Authors' Addresses 187 Weiqiang Cheng 188 China Mobile 189 Beijing 190 China 192 Email: chengweiqiang@chinamobile.com 194 Clarence Filsfils 195 Cisco Systems, Inc. 196 Belgium 198 Email: cf@cisco.com 200 Changwang Lin 201 H3C Corporation 202 Beijing 203 China 205 Email: linchangwang.04414@h3c.com 207 Liyan Gong 208 China Mobile 209 Beijing 210 China 212 Email: gongliyan@chinamobile.com