idnits 2.17.00 (12 Aug 2021) /tmp/idnits6516/draft-tgraf-opsawg-ipfix-srv6-srh-03.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 document date (20 March 2022) is 55 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) == Missing Reference: 'RFC-to-be' is mentioned on line 274, but not defined -- Looks like a reference, but probably isn't: '0' on line 466 -- Looks like a reference, but probably isn't: '1' on line 456 -- Looks like a reference, but probably isn't: '2' on line 444 == Outdated reference: A later version (-15) exists of draft-ietf-bess-srv6-services-13 == Outdated reference: A later version (-13) exists of draft-ietf-pce-segment-routing-ipv6-12 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Graf 3 Internet-Draft Swisscom 4 Intended status: Standards Track B. Claise 5 Expires: 21 September 2022 Huawei 6 20 March 2022 8 Export of Segment Routing IPv6 Information in 9 IP Flow Information Export (IPFIX) 10 draft-tgraf-opsawg-ipfix-srv6-srh-03 12 Abstract 14 This document introduces new IP Flow Information Export (IPFIX) 15 information elements to identify the SRv6 Segment Routing Header 16 dimensions and SRv6 Control Plane Protocol that traffic is being 17 forwarded with. 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 21 September 2022. 36 Copyright Notice 38 Copyright (c) 2022 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 (https://trustee.ietf.org/ 43 license-info) in effect on the date of publication of this document. 44 Please review these documents carefully, as they describe your rights 45 and restrictions with respect to this document. Code Components 46 extracted from this document must include Revised BSD License text as 47 described in Section 4.e of the Trust Legal Provisions and are 48 provided without warranty as described in the Revised BSD License. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 53 2. IPFIX Information Elements . . . . . . . . . . . . . . . . . 2 54 3. Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 56 5. Operational Considerations . . . . . . . . . . . . . . . . . 6 57 6. Security Considerations . . . . . . . . . . . . . . . . . . . 7 58 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7 59 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 60 8.1. Normative References . . . . . . . . . . . . . . . . . . 7 61 8.2. Informative References . . . . . . . . . . . . . . . . . 8 62 Appendix A. IPFIX Encoding Example . . . . . . . . . . . . . . . 8 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 65 1. Introduction 67 A new type of Routing Extension Header called Segment Routing Header 68 (SRH) is defined by [RFC8754] which is used for applying Segment 69 Routing (SR) on the IPv6 data plane. 71 Three routing protocol extensions, OSPFv3 Extensions 72 [I-D.li-lsr-ospfv3-srv6-extensions], IS-IS Extensions 73 [I-D.ietf-lsr-isis-srv6-extensions], BGP Prefix Segment Identifiers 74 (Prefix-SIDs) [I-D.ietf-bess-srv6-services] and one Path Computation 75 Element Communication Protocol (PCEP) Extension 76 [I-D.ietf-pce-segment-routing-ipv6] have been defined to propagate 77 Segment Identifiers (SIDs) for the IPv6 data plane. 79 This document defines eight new IPFIX Information Elements (IEs) and 80 two new subregistries within the "IPFIX Information Elements" 81 registry [RFC7012], respectively for the new SRH dimensions and 82 routing protocol and PCEP extensions. 84 2. IPFIX Information Elements 86 This section defines and describes the new IPFIX IEs. 88 ipv6SRHFlags 89 8-bit flags defined in the SRH. 91 ipv6SRHTag 92 16-bit tag field defined in the SRH that marks a packet as part of 93 a class or group of packets sharing the same set of properties. 95 ipv6SRHSegment 96 128-bit IPv6 address that represents an SRv6 segment. 98 ipv6SRHSegmentBasicList 99 Ordered basicList [RFC6313] of zero or more 128-bit IPv6 addresses 100 in the SRH that represents the SRv6 segment list. The Segment 101 List is encoded starting from the active segment of the SR Policy. 103 ipv6SRHSegmentListSection 104 Exposes the SRH Segment List as defined in section 2 of [RFC8754] 105 as series of n octets. 107 ipv6SRHSegmentsLeft 108 8-bit unsigned integer defining the number of route segments 109 remaining to reach the end of the segment list. 111 ipv6SRHSection 112 Exposes the SRH and its TLV's as defined in section 2 of [RFC8754] 113 as series of n octets. 115 ipv6SRHSegmentType 116 Name of the routing protocol or PCEP extension from where the 117 active SRv6 segment has been learned from. 119 3. Use Cases 121 By using ipv6SRHSegmentBasicList(TBD4), ipv6SRHSegmentsLeft (TBD6), 122 ipv6SRHSegmentType(TBD8) and forwardingStatus(89) it is possible to 123 identify 125 * how many packets are forwarded or dropped 127 * if dropped, for which reasons, 129 * identify the control plane protocol which defined the active 130 segment, 132 * the SRv6 segment list and 134 * how many SRv6 segments are left. 136 4. IANA Considerations 138 This document requests IANA to create new IEs (see table1) and two 139 new subregistries called "IPFIX IPv6 SRH Flags" (table 2) and "IPFIX 140 IPv6 SRH Segment type" (table 3) under the "IPFIX Information 141 Elements" registry [RFC7012] available at [IANA-IPFIX] and assign the 142 following code initial points. 144 +-------+---------------------------+ 145 |Element| Name | 146 | ID | | 147 +-------+---------------------------+ 148 | TBD1 | ipv6SRHFlags | 149 | | | 150 +-------+---------------------------+ 151 | TBD2 | ipv6SRHTag | 152 | | | 153 +-------+---------------------------+ 154 | TBD3 | ipv6SRHSegment | 155 | | | 156 +-------+---------------------------+ 157 | TBD4 | ipv6SRHSegmentBasicList | 158 | | | 159 +-------+---------------------------+ 160 | TBD5 | ipv6SRHSegmentListSection | 161 | | | 162 +-------+---------------------------+ 163 | TBD6 | ipv6SRHSegmentsLeft | 164 | | | 165 +-------+---------------------------+ 166 | TBD7 | ipv6SRHSection | 167 +-------+---------------------------+ 168 | TBD8 | ipv6SRHSegmentType | 169 +-------+---------------------------+ 171 Table 1: Creates IEs in the "IPFIX Information Elements" registry 173 Note to the RFC-Editor: 175 * Please replace TBD1 - TBD12 with the values allocated by IANA 177 * Please replace the [RFC-to-be] with the RFC number assigned to 178 this document 180 4.1. ipv6SRHFlags 182 Name: ipv6SRHFlags ElementID: TBD1 Description: This Information 183 Element identifies the 8-bit flags defined in the SRH. Values for 184 this Information Element are listed in the "IPFIX IPv6 SRH Flags" 185 registry, see [IANA-IPFIX]. Initial values in the registry are 186 defined by the table below. New assignments of values will be 187 administered by IANA and are subject to Expert Review Abstract Data 188 Type: unsigned8 Data Type Semantics: flags Reference: [RFC-to-be], 189 RFC8754[RFC8126]. Experts need to check definitions of new values 190 for completeness, accuracy, and redundancy. 192 +--------+-------------------+--------------------------------------+ 193 | Value | Description | Reference | 194 +--------+-------------------+--------------------------------------+ 195 | 0-7 | Unassigned | | 196 +--------+-------------------+--------------------------------------+ 198 Table 2: "IPFIX IPv6 SRH Flags" registry 200 4.2. ipv6SRHTag 202 Name: ipv6SRHTag ElementID: TBD2 Description: This Information 203 Element identifies the 16-bit tag field defined in the SRH that marks 204 a packet as part of a class or group of packets sharing the same set 205 of properties. Abstract Data Type: unsigned16 Data Type Semantics: 206 identifier Reference: [RFC-to-be], RFC8754 208 4.3. ipv6SRHSegment 210 Name: ipv6SRHSegment ElementID: TBD3 Description: This Information 211 Element identifies the 128-bit IPv6 address that represents an SRv6 212 segment. Abstract Data Type: ipv6address Data Type Semantics: 213 default Reference: [RFC-to-be], RFC8754 215 4.4. ipv6SRHSegmentBasicList 217 Name: ipv6SRHSegmentBasicList ElementID: TBD4 Description: This 218 Information Element identifies the Ordered basicList [RFC6313] of 219 zero or more 128-bit IPv6 addresses in the SRH that represents the 220 SRv6 segment list. The Segment List is encoded starting from the 221 active segment of the SR Policy. Abstract Data Type: basicList Data 222 Type Semantics: list Reference: [RFC-to-be], RFC8754 224 4.5. ipv6SRHSegmentListSection 226 Name: ipv6SRHSegmentListSection ElementID: TBD5 Description: Exposes 227 the SRH Segment List as defined in section 2 of Abstract Data Type: 228 octetArray Data Type Semantics: default Reference: [RFC-to-be], 229 RFC8754[RFC8754] as series of n octets. 231 4.6. ipv6SRHSegmentsLeft 233 Name: ipv6SRHSegmentsLeft ElementID: TBD6 Description: This 234 Information Element identifies the 8-bit unsigned integer defining 235 the number of route segments remaining to reach the end of the 236 segment list. Abstract Data Type: unsigned8 Data Type Semantics: 237 quantity Reference: [RFC-to-be], RFC8754 239 4.7. ipv6SRHSection 241 Name: ipv6SRHSection ElementID: TBD7 Description: This Information 242 Element exposes the SRH and its TLV's as defined in s ection 2 of 243 Abstract Data Type: octetArray Data Type Semantics: default 244 Reference: [RFC-to-be], RFC8754[RFC8754] as series of n octets. 246 4.8. ipv6SRHSegmentType 248 Name: ipv6SRHSegmentType ElementID: TBD8 Description: This 249 Information Element identifies the name of the routing protocol or 250 PCEP extension from where the active SRv6 segment has been learned 251 from. Values for this Information Element are listed in the "IPFIX 252 IPv6 SRH Segment type" registry, see [IANA-IPFIX]. Initial values in 253 the registry are defined by the table below. New assignments of 254 values will be administered by IANA and are subject to Expert Review 255 Abstract Data Type: unsigned8 Data Type Semantics: identifier 256 Reference: [RFC-to-be][RFC8126]. Experts need to check definitions 257 of new values for completeness, accuracy, and redundancy. 259 +-------+--------------------+--------------------------------------+ 260 | Value | Description | Reference | 261 +-------+--------------------+--------------------------------------+ 262 | TBD9 | Unknown | [RFC-to-be] | 263 | | | | 264 +-------+--------------------+--------------------------------------+ 265 | TBD10 | Path Computation | [RFC-to-be], | 266 | | Element | draft-ietf-pce-segment-routing-ipv6 | 267 +-------+--------------------+--------------------------------------+ 268 | TB11 | OSPFv3 | [RFC-to-be], | 269 | | Segment Routing | draft-li-ospf-ospfv3-srv6-extensions | 270 +-------+--------------------+--------------------------------------+ 271 | TBD12 | IS-IS | [RFC-to-be] | 272 | | Segment Routing | draft-ietf-lsr-isis-srv6-extensions | 273 +-------+--------------------+--------------------------------------+ 274 | TBD13 | BGP Segment | [RFC-to-be], | 275 | | Routing Prefix-SID | draft-ietf-bess-srv6-services | 276 +-------+--------------------+--------------------------------------+ 278 Table 3: "IPFIX IPv6 SRH Segment type" subregistry 280 5. Operational Considerations 282 The zero or more 128-bit IPv6 addresses in the SRH [RFC8754] can be 283 exported in two different ways, with two different IPFIX IEs: 285 * ipv6SRHSegmentBasicList 286 * ipv6SRHSegmentListSection 288 The ipv6SRHSegmentBasicList encodes the SID list of IPv6 addresses 289 with a basicList, specified in the IPFIX Structured Data [RFC6313]. 290 This encoding offers the advantage to the data collection that the 291 different IPv6 addresses are already structured as a list, without 292 the need of post processing. However, this method requires some 293 extra processing on the exporter, to realize the BasicList data 294 mapping. 296 The ipv6SRHSegmentListSection, on the other hand, encodes the list of 297 IPv6 addresses as an octetArray. This doesn't impose any data flow 298 manipulation on the exporter, facilitating the immediate export. 299 However, the data collection must be able to decode the IPv6 300 addresses according the SR specifications. 302 It is not expected that an exporter would support both 303 ipv6SRHSegmentBasicList and ipv6SRHSegmentListSection at the same 304 time. 306 6. Security Considerations 308 There exists no significant extra security considerations regarding 309 the allocation of these new IPFIX IEs compared to [RFC7012]. 311 7. Acknowledgements 313 I would like to thank Pierre Francois, Yao Liu and Paolo Lucente for 314 their review and valuable comments. 316 8. References 318 8.1. Normative References 320 [RFC6313] Claise, B., Dhandapani, G., Aitken, P., and S. Yates, 321 "Export of Structured Data in IP Flow Information Export 322 (IPFIX)", RFC 6313, DOI 10.17487/RFC6313, July 2011, 323 . 325 [RFC7012] Claise, B., Ed. and B. Trammell, Ed., "Information Model 326 for IP Flow Information Export (IPFIX)", RFC 7012, 327 DOI 10.17487/RFC7012, September 2013, 328 . 330 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 331 Writing an IANA Considerations Section in RFCs", BCP 26, 332 RFC 8126, DOI 10.17487/RFC8126, June 2017, 333 . 335 8.2. Informative References 337 [I-D.ietf-bess-srv6-services] 338 Dawra, G., Filsfils, C., Talaulikar, K., Raszuk, R., 339 Decraene, B., Zhuang, S., and J. Rabadan, "SRv6 BGP based 340 Overlay Services", Work in Progress, Internet-Draft, 341 draft-ietf-bess-srv6-services-13, 19 March 2022, 342 . 345 [I-D.ietf-lsr-isis-srv6-extensions] 346 Psenak, P., Filsfils, C., Bashandy, A., Decraene, B., and 347 Z. Hu, "IS-IS Extensions to Support Segment Routing over 348 IPv6 Dataplane", Work in Progress, Internet-Draft, draft- 349 ietf-lsr-isis-srv6-extensions-18, 20 October 2021, 350 . 353 [I-D.ietf-pce-segment-routing-ipv6] 354 Li, C., Negi, M., Sivabalan, S., Koldychev, M., 355 Kaladharan, P., and Y. Zhu, "PCEP Extensions for Segment 356 Routing leveraging the IPv6 data plane", Work in Progress, 357 Internet-Draft, draft-ietf-pce-segment-routing-ipv6-12, 6 358 March 2022, . 361 [I-D.li-lsr-ospfv3-srv6-extensions] 362 Li, Z., Hu, Z., Cheng, D., Talaulikar, K., and P. Psenak, 363 "OSPFv3 Extensions for SRv6", Work in Progress, Internet- 364 Draft, draft-li-lsr-ospfv3-srv6-extensions-00, 15 January 365 2020, . 368 [IANA-IPFIX] 369 "IANA, "IP Flow Information Export (IPFIX) Entities"", 370 . 372 [RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J., 373 Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header 374 (SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020, 375 . 377 Appendix A. IPFIX Encoding Example 379 In this section an example is provided to show the encoding format 380 for the newly introduced IEs. 382 +-----+------+-----+--------+---------------------------------------| 383 | SRH | SRH | SRH | Segment| Segment List | 384 | Nr | Flags| Tag | Type | | 385 +-----+------+-----+--------+---------------------------------------+ 386 | 1 | 0 | 123 | IS-IS | 2001:db8::1, 2001:db8::2, 2001:db8::3 | 387 +-----+------+-----+--------+---------------------------------------+ 388 | 2 | 0 | 456 | IS-IS | 2001:db8::4, 2001:db8::5 | 389 +-----+------+-----+--------+---------------------------------------+ 390 | 3 | 0 | 789 | IS-IS | 2001:db8::6 | 391 +-----+------+-----+--------+---------------------------------------+ 393 Table 4: 3 observed SRH headers and their routing protocol 395 A.1. Template Record 397 0 1 2 3 398 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 399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 400 | SET ID = 2 | Length = 41 | 401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 402 | Template ID = 256 | Field Count = 4 | 403 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 404 |0| ipv6SRHFlags = TBD1 | Field Length = 1 | 405 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 406 |0| ipv6SRHTag = TBD2 | Field Length = 2 | 407 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 408 |0| ipv6SRHSegmentType = TBD8 | Field Length = 1 | 409 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 410 |0| ipv6SRHSegment = TBD3 | Field Length = 16 | 411 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 412 |0|ipv6SRHSegmentBasicList= TBD4| Field Length = 0xFFFF | 413 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 415 Table 4: Template Record Encoding Format 417 In this example, the Template ID is 256, which will be used in the 418 Data Record. The field length for ipv6SRHSegmentBasicList is 0xFFFF, 419 which means the length of this IE is variable, and the actual length 420 of this IE is indicated by the List Length field in the basicList 421 format as per [RFC6313]. 423 A.2. Data Set 425 The data set is represented as follows: 427 0 1 2 3 428 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 429 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 430 | SET ID = 256 | Length = 136 | 431 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 432 | ipv6SRHFlags | ipv6SRHTag = 123 | ipv6SRHSegment| 433 | = 0 | | Type = TBD12 | 434 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 435 | 255 | List Length = 53 |semantic= | 436 | | |ordered | 437 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 438 | ipv6SRHSegment = TBD4 | Field Length = 16 | 439 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 440 | Segment List[0] = 2001:db8::1 (16 bytes) | 441 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 442 | Segment List[1] = 2001:db8::2 (16 bytes) | 443 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 444 | Segment List[2] = 2001:db8::3 (16 bytes) | 445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 446 | ipv6SRHFlags | ipv6SRHTag = 456 | ipv6SRHSegment| 447 | = 0 | | Type = TBD12 | 448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 449 | 255 | List Length = 37 |semantic= | 450 | | |ordered | 451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 452 | ipv6SRHSegment = TBD4 | Field Length = 16 | 453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 454 | Segment List[0] = 2001:db8::4 (16 bytes) | 455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 456 | Segment List[1] = 2001:db8::5 (16 bytes) | 457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 458 | ipv6SRHFlags | ipv6SRHTag = 789 | ipv6SRHSegment| 459 | = 0 | | Type = TBD12 | 460 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 461 | 255 | List Length = 21 |semantic= | 462 | | |ordered | 463 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 464 | ipv6SRHSegment = TBD4 | Field Length = 16 | 465 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 466 | Segment List[0] = 2001:db8::6 (16 bytes) | 467 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 469 Table 5: Data Set Encoding Format 471 Authors' Addresses 472 Thomas Graf 473 Swisscom 474 Binzring 17 475 CH-8045 Zurich 476 Switzerland 477 Email: thomas.graf@swisscom.com 479 Benoit Claise 480 Huawei 481 Email: benoit.claise@huawei.com