idnits 2.17.1 draft-cheng-spring-srv6-encoding-network-sliceid-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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 4) being 64 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 5 instances of too long lines in the document, the longest one being 2 characters 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 (July 12, 2021) is 1020 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 L. Gong 3 Intended status: Standards Track China Mobile 4 Expires: January 12, 2022 Changwang. Lin 5 H3C Corporation 6 July 12, 2021 8 Encoding Network Slice Identification for SRv6 9 draft-cheng-spring-srv6-encoding-network-sliceid-00 11 Abstract 13 This document describe a method to encode network slicing identifier 14 within SRv6 domain. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on January 12, 2022. 33 Copyright Notice 35 Copyright (c) 2021 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 52 2. Slice Identifier . . . . . . . . . . . . . . . . . . . . . . 2 53 3. SLID Assignment . . . . . . . . . . . . . . . . . . . . . . . 2 54 4. Per-Slice Forwarding . . . . . . . . . . . . . . . . . . . . 3 55 5. Backward Compatibility . . . . . . . . . . . . . . . . . . . 3 56 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4 57 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 7.1. Normative References . . . . . . . . . . . . . . . . . . 4 59 7.2. Informative References . . . . . . . . . . . . . . . . . 4 60 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 62 1. Introduction 64 SRv6 Network Programming[RFC8986] enables the creation of overlays 65 with underlay optimization to be deployed in an SR domain[RFC8402]. 67 As defined in [RFC8754], all inter-domain packets are encapsulated 68 for the part of the packet journey that is within the SR domain. The 69 outer IPv6 header [RFC8200] is originated by a node of the SR domain 70 and is destined to a node of the SR domain. 72 This document describes a novelty method to encode slice identifier 73 in the outer IPv6 header of an SR domain. Unlike other proposed 74 methods before, which will bring side effects on existed functions, 75 by encoding network slicing identifier in the source IPv6 address of 76 the outer header, this method avoids the drawbacks which previous 77 proposals incur. 79 1.1. Requirements Language 81 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 82 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 83 document are to be interpreted as described in RFC 2119 [RFC2119]. 85 2. Slice Identifier 87 Slice identifier (SLID) is a 16-bit Identifier which uniquely define 88 a slicing of the network in the specified SR domain. 90 3. SLID Assignment 92 When SR domain enables network slicing, the ingress PE should reserve 93 16 least significant bits in its locater for slicing use. When a 94 packet enters the SR domain from an ingress PE, the ingress PE 95 encapsulates the packet in an outer IPv6 header and optional SRH as 96 defined in [RFC8754]. The ingress PE MAY also classify the packet 97 into a slice and set the slice identifier as follows: 99 o Set the SPI bit (SLID Presence Indicator) in the Traffic Class 100 field of the outer IPv6 header. 102 o Write this SLID in the 16 least significant bits of source address 103 of the outer IPv6 header. 105 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 106 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 107 |Version| SPI Bit | Flow Label | 108 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 109 | Payload Length | Next Header | Hop Limit | 110 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 111 | | 112 + + 113 | | 114 + Source Address + 115 | | 116 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 117 | | SLID | 118 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 119 | | 120 + + 121 | | 122 + Destination Address + 123 | | 124 + + 125 | | 126 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 128 The choice of the SPI bit from within the IPv6 Traffic Class field is 129 a domain-wide configuration and is outside the scope of this 130 document. 132 4. Per-Slice Forwarding 134 Any router within the SR domain that forwards a packet with SPI bit 135 set uses the SLID to select a slice and apply per-slice policies. 137 5. Backward Compatibility 139 PE routers that do not set the SPI bit do not enable the SLID 140 semantic of the IPv6 source address bits. Hence, SLID-aware routers 141 would not attempt to classify these packets into a slice. 143 Any router that does not process the SPI nor the SLID forwards 144 packets as usual. 146 6. Acknowledgements 148 The authors would like to thank AAAA, BBBB and CCCC for their 149 insightful feedback on this document. 151 7. References 153 7.1. Normative References 155 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 156 Requirement Levels", BCP 14, RFC 2119, 157 DOI 10.17487/RFC2119, March 1997, 158 . 160 [RFC8986] Filsfils, C., Camarillo, P., Leddy, J., Voyer, D., 161 Matsushima, S., and Z. Li, 162 Segment Routing over IPv6 (SRv6) Network Programming, 163 RFC 8986, DOI 10.17487/RFC8986, February 2021, 164 . 166 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 167 Decraene, B., Litkowski, S., and R. Shakir, "Segment 168 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 169 July 2018, . 171 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 172 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 173 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 174 . 176 7.2. Informative References 178 [RFC8200] Deering, S., and Hinden, D., "Internet Protocol, Version 6 179 (IPv6) Specification", RFC 8200, DOI 10.17487/RFC8200, 180 July 2017, . 182 Authors' Addresses 184 Weiqiang Cheng 185 China Mobile 186 Beijing 187 China 189 Email: chengweiqiang@chinamobile.com 191 Liyan Gong 192 China Mobile 193 Beijing 194 China 196 Email: gongliyan@chinamobile.com 198 Changwang Lin 199 H3C Corporation 200 Beijing 201 China 203 Email: linchangwang.04414@h3c.com