idnits 2.17.1 draft-ietf-trill-link-gk-profiles-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 (July 26, 2018) is 2101 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) ** Obsolete normative reference: RFC 5246 (Obsoleted by RFC 8446) ** Downref: Normative reference to an Informational RFC: RFC 5869 ** Obsolete normative reference: RFC 6347 (Obsoleted by RFC 9147) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Donald Eastlake 2 Intended status: Proposed Standard Dacheng Zhang 3 Huawei 4 Expires: January 25, 2019 July 26, 2018 6 Simple Group Keying Protocol TRILL Use Protfiles 7 9 Abstract 11 This document specifies use profiles for the application of the 12 simple group keying protocol (SGKP) to multi-destination TRILL 13 Extended RBridge Channel message security (RFC 7978) and TRILL over 14 IP packet security (draft-ietf-trill-over-ip). 16 Status of This Memo 18 This Internet-Draft is submitted to IETF in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Distribution of this document is unlimited. Comments should be sent 22 to the authors or the TRILL working group mailing list: 23 trill@ietf.org. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft 37 Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Table of Contents 42 1. Introduction............................................3 43 1.1 Terminology and Acronyms..............................3 45 2. DTLS: Extended RBridge Channel Group Keyed Security.....5 46 2.1 Transmission of Group Keying Messages..................5 47 2.2 Transmission of Protected Multi-destination Data.......6 49 3. TRILL Over IP Group Keyed Security......................7 50 3.1 Transmission of Group Keying Messages..................7 51 3.2 Transmission of Protected Multi-destination Data.......8 53 4. Security Considerations.................................9 55 5. IANA Considerations....................................10 56 5.1 Group Keying RBridge Channel Protocol Numbers.........10 57 5.2 Group Secured Extended RBridge Channel SType..........10 59 Normative References......................................11 60 Informative References....................................12 62 Acknowledgements..........................................13 63 Authors' Addresses........................................14 65 1. Introduction 67 This document specifies use profiles for the application of the 68 simple group keying protocol (SGKP) [SGKPrfc] to the use of DTLS 69 [RFC6347] formatted TRILL [RFC6325] [RFC7780] Extended RBridge 70 Channel message security [RFC7178] [RFC7978] and to the use of IPsec 71 formatted TRILL over IP [TRILLoverIP]. It is anticipated that there 72 will be other uses for this group keying protocol. 74 1.1 Terminology and Acronyms 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 77 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 78 document are to be interpreted as described in [RFC2119] [RFC8174] 79 when, and only when, they appear in all capitals, as shown here. 81 This document uses terminology and acronyms defined in [RFC6325] and 82 [RFC7178]. Some of these are repeated below for convenience along 83 with additional new terms and acronyms. 85 Data Label - VLAN or FGL. 87 DTLS - Datagram Transport Level Security [RFC6347]. 89 FGL - Fine Grained Label [RFC7172]. 91 GKd - A distinguished station in a group that is in charge of 92 which group keying (Section 2) is in use. 94 GKs - Stations in a group other than GKd (Section 2). 96 HKDF - Hash based Key Derivation Function [RFC5869]. 98 IS-IS - Intermediate System to Intermediate System [RFC7176]. 100 keying material - The set of a Key ID, a secret key, and a cypher 101 suite. 103 PDU - Protocol Data Unit. 105 QoS - Quality of Service. 107 RBridge - An alternative term for a TRILL switch. 109 SHA - Secure Hash Algorithm [RFC6234]. 111 TRILL - Transparent Interconnection of Lots of Links or Tunneled 112 Routing in the Link Layer. 114 TRILL switch - A device that implements the TRILL protocol 115 [RFC6325] [RFC7780], sometimes referred to as an RBridge. 117 2. DTLS: Extended RBridge Channel Group Keyed Security 119 This section specifies a profile of the simple group keying protocol 120 (SGKP) defined in [SGKPrfc]. This profile provides shared secret 121 keying to secure multi-destination Extended RBridge Channel messages 122 [RFC7978] as described in Setction 2.2. 124 For this SKGP use profile, a group is identified by TRILL Data Label 125 (VLAN or FGL [RFC7172]) and consists of the data reachable [RFC7780] 126 RBridges with interest in that Data Label. GKd is the RBridge in the 127 group that, of those group members supporting the Group Keying 128 Protocol, is the highest priority to be a TRILL distribution tree 129 root as specified in Section 4.5 of [RFC6325]. If not all members of 130 the group support the Group Keying Protocol, then there are two cases 131 of destinations for multi-destination Channel Tunnel RBridge Channel 132 messages: 134 (1) If the sender and at least two other group members support the 135 Group Keying Protocol, it SHOULD, for efficiency, send a secured 136 multi-destination RBridge Channel message to cover the group and 137 serially unicast to the group members not supporting the Group 138 Keying Protocol. 139 (2) In other cases the sender serially transmits the data to the 140 group members using pairwise security. 142 2.1 Transmission of Group Keying Messages 144 Keying messages themselves are sent as unicast Extended RBridge 145 Channel messages carrying a Group Keying protocol (see Section 5.1) 146 RBridge Channel message. Such messages MUST use DTLS Pairwise or 147 Composite (STypes 2 or 3) security [RFC7978]. 149 The Group Keying profile for this Group Keying Use Type is as 150 follows: 152 Priority of Group Keying messages for this SHOULD be 6 unless the 153 network manager chooses to use a lower priority after 154 determining that such lower priority group keying messages 155 will yield acceptable performance. Priority 7 SHOULD NOT be 156 used as it may cause interference with the establishment and 157 maintenance of adjacency. 159 Use Type = 1 161 KeyID1 Length = 2, KeyID1 is an [RFC5310] key ID. 163 CypherSuiteLng = 2, CypherSuite is the cypher suite used in 164 groupcast extended RBridge Channel data messages for the 165 corresponding KeyID2. This is a DTLS [RFC6347] cypher suite. 167 KeyID2 Length = 1, KeyID2 is the index under which a group key is 168 set. Group keys are, in effect, indexed by this KeyID2 and 169 the nickname of the GKd as used in the Ingress Nickname 170 field of the TRILL Header of Group Keying messages. 172 2.2 Transmission of Protected Multi-destination Data 174 Protected Extended RBridge Channel [RFC7978] messages are multicast 175 (M bit set to one in the TRILL Header) and set the SType field to a 176 new value TBD2 for "Group Secured" (see Section 5.2). Since there 177 could be multiple group keys distribued and enabled for use, data is 178 formatted as two bytes of Key ID followed by data formatted as TLS 179 1.2 [RFC5246] application_data using the cyphersuite and keying 180 material stored under the Key ID. Such a message on the wire looks 181 like the following: 183 +---------------------------+ 184 | Link Header | 185 +---------------------------+ 186 | TRILL Header | 187 +---------------------------+ 189 | RBridge Channel Header | 190 | snd Extension | 191 +---------------------------+ 192 | RBridge Channel Payload | 193 | +----------------------+ | 194 | | 2-byte Key ID | | 195 | +----------------------+ | 196 | | DTLS formatted | | 197 | | application data | | 198 | +----------------------+ | 199 +---------------------------+ 200 | Link Trailer | 201 +---------------------------+ 203 3. TRILL Over IP Group Keyed Security 205 This SGKP usage profile provides shared secret keying to secure TRILL 206 over IP messages [TRILLoverIP]. The keys put in place by the group 207 keying protocol are available for use as IPSEC keys. 209 For this use profile, a group is identified by an IP multicast 210 address and consists of the RBridges adjacent [RFC7177] to the sender 211 reachable with that multicast address over a TRILL over IP link. GKd 212 is the RBridge in the group that, of those group members supporting 213 the Group Keying Protocol, has the highest priority to be a TRILL 214 distribution tree root as specified in Section 4.5 of [RFC6325]. If 215 not all members of the group support the Group Keying Protocol, then 216 there are two cases for multi-destination TRILL over IP messages: 218 (1) If the sender and at least two other group members support SGKP, 219 it SHOULD, for efficiency, send a secured IPSEC message to cover 220 the group and serially unicast to the group members not 221 supporting the Group Keying Protocol. 222 (2) In other cases the sender serially transmits the data to the 223 group members using pairwise security. 225 3.1 Transmission of Group Keying Messages 227 Keying messages themselves are sent as unicast Extended RBridge 228 Channel messages carrying a Group Keying protocol (see Section 5.1) 229 RBridge Channel message. Such messages MUST use DTLS Pairwise or 230 Composite (STypes 2 or 3) security [RFC7978]. 232 The Group Keying profile for this Group Keying Use Type is as 233 follows: 235 Priority of Group Keying messages for this SHOULD be 6 unless the 236 network manager chooses to use a lower priority after 237 determining that such lower priority group keying messages 238 will yield acceptable performance. Priority 7 SHOULD NOT be 239 used as it may cause interference with the establishment and 240 maintenance of adjacency. 242 Use Type = 2 244 KeyID1 Length = 2, KeyID1 is an [RFC5310] key ID. 246 CypherSuiteLng = variable, CypherSuite is an IKEv2 crypto 247 algorithm "proposal" [RFC7296]. 249 KeyID2 Length = 4, KeyID2 is the IPsec multicast SA. It is the 250 index under which a group key is set. Group keys are indexed 251 by this KeyID2 and the nickname of the GKd as used in the 252 Ingress Nickname field of the TRILL Header of Group Keying 253 messages. 255 3.2 Transmission of Protected Multi-destination Data 257 Multi-destination TRILL over IP data packets are formatted as 258 multicast IPsec ESP tunnel mode [RFC4303] packets. The key and crpto 259 algorithms in use are indicated by the multicast SA. 261 4. Security Considerations 263 See [SGKPrfc] for Simple Group Keying Protocol security 264 considerations. 266 See [RFC7978] for Extended RBridge Channel security considerations. 268 See [RFC7457] in connection with TLS and DTLS security 269 considerations. 271 See [TRILLoverIP] for TRILL over IP secrity considerations. 273 See [RFC4303] for IPsec ESP security considerations. 275 5. IANA Considerations 277 This section gives IANA Considerations. 279 5.1 Group Keying RBridge Channel Protocol Numbers 281 IANA is requested to assign TBD1 as the TRILL RBridge Channel 282 protocol number, from the range assigned by Standards Action, for use 283 when the "Group Keying" protocol is transmitted over Extended RBridge 284 Channel messages. 286 The added RBridge Channel protocols registry entry on the TRILL 287 Parameters web page is as follows: 289 Protocol Description Reference 290 -------- -------------- ------------------ 291 TBD1 Group Keying Section 2 of [this document] 293 5.2 Group Secured Extended RBridge Channel SType 295 IANA is requested to assign TBD2 as the Group Secured SType in the 296 "Extended RBridge Channel Security Types Subregistry" on the TRILL 297 Parameters web page as follows: 299 SType Description Reference 300 ----- ------------- ---------- 301 TBD2 Group Secured Section 2.2 of [this document] 303 Normative References 305 [RFC2119] - BBradner, S., "Key words for use in RFCs to Indicate 306 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, 307 March 1997, . 309 [RFC4303] - Kent, S., "IP Encapsulating Security Payload (ESP)", RFC 310 4303, DOI 10.17487/RFC4303, December 2005, . 313 [RFC5246] - Dierks, T. and E. Rescorla, "The Transport Layer Security 314 (TLS) Protocol Version 1.2", RFC 5246, August 2008, 315 . 317 [RFC5310] - Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., 318 and M. Fanto, "IS-IS Generic Cryptographic Authentication", RFC 319 5310, DOI 10.17487/RFC5310, February 2009, . 322 [RFC5869] - Krawczyk, H. and P. Eronen, "HMAC-based Extract-and- 323 Expand Key Derivation Function (HKDF)", RFC 5869, May 2010, 324 . 326 [RFC6325] - Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A. 327 Ghanwani, "Routing Bridges (RBridges): Base Protocol 328 Specification", RFC 6325, DOI 10.17487/RFC6325, July 2011, 329 . 331 [RFC6347] - Rescorla, E. and N. Modadugu, "Datagram Transport Layer 332 Security Version 1.2", RFC 6347, January 2012, . 335 [RFC7172] - Eastlake 3rd, D., Zhang, M., Agarwal, P., Perlman, R., 336 and D. Dutt, "Transparent Interconnection of Lots of Links 337 (TRILL): Fine-Grained Labeling", RFC 7172, DOI 338 10.17487/RFC7172, May 2014, . 341 [RFC7176] - Eastlake 3rd, D., Senevirathne, T., Ghanwani, A., Dutt, 342 D., and A. Banerjee, "Transparent Interconnection of Lots of 343 Links (TRILL) Use of IS-IS", RFC 7176, May 2014, 344 . 346 [RFC7177] - Eastlake 3rd, D., Perlman, R., Ghanwani, A., Yang, H., 347 and V. Manral, "Transparent Interconnection of Lots of Links 348 (TRILL): Adjacency", RFC 7177, DOI 10.17487/RFC7177, May 2014, 349 . 351 [RFC7178] - Eastlake 3rd, D., Manral, V., Li, Y., Aldrin, S., and D. 352 Ward, "Transparent Interconnection of Lots of Links (TRILL): 354 RBridge Channel Support", RFC 7178, DOI 10.17487/RFC7178, May 355 2014, . 357 [RFC7296] - Kaufman, C., Hoffman, P., Nir, Y., Eronen, P., and T. 358 Kivinen, "Internet Key Exchange Protocol Version 2 (IKEv2)", 359 STD 79, RFC 7296, DOI 10.17487/RFC7296, October 2014, 360 . 362 [RFC7780] - Eastlake 3rd, D., Zhang, M., Perlman, R., Banerjee, A., 363 Ghanwani, A., and S. Gupta, "Transparent Interconnection of 364 Lots of Links (TRILL): Clarifications, Corrections, and 365 Updates", RFC 7780, DOI 10.17487/RFC7780, February 2016, 366 . 368 [RFC7978] - Eastlake 3rd, D., Umair, M., and Y. Li, "Transparent 369 Interconnection of Lots of Links (TRILL): RBridge Channel 370 Header Extension", RFC 7978, DOI 10.17487/RFC7978, September 371 2016, . 373 [RFC8174] - Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 374 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 375 2017, . 377 [TRILLoverIP] - M. Cullen, D. Eastlake, M. Zhang, D. Zhang, 378 "Transparent Interconnection of Lots of Links (TRILL) over IP", 379 draft-ietf-trill-over-ip, work in progress. 381 [SGKPrfc] - D. Eastlake, D. Zhang, "Simple Group Keying Protocol 382 (SGKP)", draft-ietf-trill-group-keying, work in progress. 384 Informative References 386 [RFC6234] - Eastlake 3rd, D. and T. Hansen, "US Secure Hash 387 Algorithms (SHA and SHA-based HMAC and HKDF)", RFC 6234, DOI 388 10.17487/RFC6234, May 2011, . 391 [RFC7457] - Sheffer, Y., Holz, R., and P. Saint-Andre, "Summarizing 392 Known Attacks on Transport Layer Security (TLS) and Datagram 393 TLS (DTLS)", RFC 7457, February 2015, . 396 Acknowledgements 398 The contributions of the following are hereby gratefully 399 acknowledged: 401 TBD 403 Authors' Addresses 405 Donald E. Eastlake, 3rd 406 Huawei Technologies 407 1424 Pro Shop Court 408 Davenport, FL 33896 USA 410 Phone: +1-508-333-2270 411 EMail: d3e3e3@gmail.com 413 Dacheng Zhang 414 Huawei Technologies 416 Email: dacheng.zhang@huawei.com 418 Copyright, Disclaimer, and Additional IPR Provisions 420 Copyright (c) 2018 IETF Trust and the persons identified as the 421 document authors. All rights reserved. 423 This document is subject to BCP 78 and the IETF Trust's Legal 424 Provisions Relating to IETF Documents 425 (http://trustee.ietf.org/license-info) in effect on the date of 426 publication of this document. Please review these documents 427 carefully, as they describe your rights and restrictions with respect 428 to this document. Code Components extracted from this document must 429 include Simplified BSD License text as described in Section 4.e of 430 the Trust Legal Provisions and are provided without warranty as 431 described in the Simplified BSD License. The definitive version of 432 an IETF Document is that published by, or under the auspices of, the 433 IETF. Versions of IETF Documents that are published by third parties, 434 including those that are translated into other languages, should not 435 be considered to be definitive versions of IETF Documents. The 436 definitive version of these Legal Provisions is that published by, or 437 under the auspices of, the IETF. Versions of these Legal Provisions 438 that are published by third parties, including those that are 439 translated into other languages, should not be considered to be 440 definitive versions of these Legal Provisions. For the avoidance of 441 doubt, each Contributor to the IETF Standards Process licenses each 442 Contribution that he or she makes as part of the IETF Standards 443 Process to the IETF Trust pursuant to the provisions of RFC 5378. No 444 language to the contrary, or terms, conditions or rights that differ 445 from or are inconsistent with the rights and licenses granted under 446 RFC 5378, shall have any effect and shall be null and void, whether 447 published or posted by such Contributor, or included with or in such 448 Contribution.