idnits 2.17.1 draft-ietf-isis-sbfd-discriminator-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 seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 14, 2014) is 3474 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'IS-IS' ** Obsolete normative reference: RFC 4971 (Obsoleted by RFC 7981) == Outdated reference: A later version (-11) exists of draft-ietf-bfd-seamless-base-03 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Networking Working Group L. Ginsberg 3 Internet-Draft N. Akiya 4 Intended status: Standards Track Cisco Systems 5 Expires: April 17, 2015 M. Chen 6 Huawei 7 October 14, 2014 9 Advertising S-BFD Discriminators in IS-IS 10 draft-ietf-isis-sbfd-discriminator-01.txt 12 Abstract 14 This document defines a means of advertising one or more S-BFD 15 Discriminators using the IS-IS Router Capability TLV. 17 Requirements Language 19 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 21 document are to be interpreted as described in RFC 2119 [RFC2119]. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on April 17, 2015. 40 Copyright Notice 42 Copyright (c) 2014 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 This document may contain material from IETF Documents or IETF 56 Contributions published or made publicly available before November 57 10, 2008. The person(s) controlling the copyright in some of this 58 material may not have granted the IETF Trust the right to allow 59 modifications of such material outside the IETF Standards Process. 60 Without obtaining an adequate license from the person(s) controlling 61 the copyright in such materials, this document may not be modified 62 outside the IETF Standards Process, and derivative works of it may 63 not be created outside the IETF Standards Process, except to format 64 it for publication as an RFC or to translate it into languages other 65 than English. 67 Table of Contents 69 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 70 2. Encoding Format . . . . . . . . . . . . . . . . . . . . . . 2 71 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 72 4. Security Considerations . . . . . . . . . . . . . . . . . . . 3 73 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 74 6. Normative References . . . . . . . . . . . . . . . . . . . . 4 75 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 77 1. Introduction 79 [S-BFD] defines a simplified mechanism to use Bidirectional 80 Forwarding Detection (BFD)[RFC5880]. This mechanism depends on 81 network nodes knowing the BFD discriminators which each node in the 82 network has reserved for this purpose. Use of the Intermediate 83 System to Intermediate System (IS-IS)[IS-IS] protocol is one possible 84 means of advertising these discriminators. 86 2. Encoding Format 88 The IS-IS Router CAPABILITY TLV as defined in [RFC4971] will be used 89 to advertise S-BFD discriminators. A new sub-TLV is defined as 90 described below. S-BFD Discriminators sub-TLVs are formatted as 91 specified in [RFC5305]. 93 No. of octets 94 +-----------------------------+ 95 | Type (to be assigned by | 1 96 | IANA - suggested value 19) | 97 +-----------------------------+ 98 | Length (multiple of 4) | 1 99 +-----------------------------+ 100 | Discriminator Value(s) | 4/Discriminator 101 : : 102 +-----------------------------+ 104 Inclusion of the S-BFD Discriminators sub-TLV in a Router Capability 105 TLV is optional. Multiple S-BFD Discriminators sub-TLVs MAY be 106 advertised by an IS. When multiple S-BFD discriminators are 107 advertised how a given discriminator is mapped to a specific use case 108 is out of scope for this document. 110 S-BFD discriminator advertisements MAY be flooded within an area or 111 throughout the domain using the procedures specified in [RFC4971]. 112 The appropriate flooding scope depends on the intended use of S-BFD. 113 If S-BFD use will be exclusively within a Level-1 area then area 114 scope is appropriate. If S-BFD usage will span different L1 areas 115 then domain scope is appropriate. 117 3. IANA Considerations 119 This document requires the definition of a new sub-TLV in the Sub- 120 TLVs for TLV 242 registry. The value written below is a suggested 121 value subject to assignment by IANA. 123 Value Description 124 ---- --------------------- 125 19 S-BFD Discriminators 127 4. Security Considerations 129 Security concerns for IS-IS are addressed in [IS-IS], [RFC5304], and 130 [RFC5310]. Introduction of the S-BFD Discriminators sub-TLV 131 introduces no new security risks for IS-IS. 133 Advertisement of the S-BFD discriminators does make it possible for 134 attackers to initiate S-BFD sessions using the advertised 135 information. The vulnerabilities this poses and how to mitigate them 136 are discussed in the Security Considerations section of [S-BFD]. 138 5. Acknowledgements 140 The authors wish to thank Sam Aldrin, Manav Bhatia, and Carlos 141 Pignataro for input essential to defining the needed functionality. 143 6. Normative References 145 [IS-IS] "Intermediate system to Intermediate system intra-domain 146 routeing information exchange protocol for use in 147 conjunction with the protocol for providing the 148 connectionless-mode Network Service (ISO 8473), ISO/IEC 149 10589:2002, Second Edition.", Nov 2002. 151 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 152 Requirement Levels", BCP 14, RFC 2119, March 1997. 154 [RFC4971] Vasseur, JP., Shen, N., and R. Aggarwal, "Intermediate 155 System to Intermediate System (IS-IS) Extensions for 156 Advertising Router Information", RFC 4971, July 2007. 158 [RFC5304] Li, T. and R. Atkinson, "IS-IS Cryptographic 159 Authentication", RFC 5304, October 2008. 161 [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic 162 Engineering", RFC 5305, October 2008. 164 [RFC5310] Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., 165 and M. Fanto, "IS-IS Generic Cryptographic 166 Authentication", RFC 5310, February 2009. 168 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 169 (BFD)", RFC 5880, June 2010. 171 [S-BFD] "Seamless Bidirectional Forwarding Detection (S-BFD), 172 draft-ietf-bfd-seamless-base-03(work in progress)", August 173 2014. 175 Authors' Addresses 177 Les Ginsberg 178 Cisco Systems 179 510 McCarthy Blvd. 180 Milpitas, CA 95035 181 USA 183 Email: ginsberg@cisco.com 184 Nobo Akiya 185 Cisco Systems 187 Email: nobo@cisco.com 189 Mach(Guoyi) Chen 190 Huawei 192 Email: mach.chen@huawei.com