Internet Engineering Task Force (IETF) C. PignataroInternet-DraftRequest for Comments: 7884 CiscoIntended status:Category: Standards Track M. BhatiaExpires: October 31, 2016ISSN: 2070-1721 Ionos Networks S. Aldrin Huawei Technologies T. Ranganath NokiaApril 29,July 2016 OSPF Extensions to Advertise Seamless Bidirectional Forwarding Detection (S-BFD) Target Discriminatorsdraft-ietf-ospf-sbfd-discriminator-06Abstract This document defines a new OSPF Router Information (RI) TLV that allows OSPF routers to flood the Seamless Bidirectional Forwarding Detection (S-BFD)discriminatorDiscriminator values associated with a target network identifier. This mechanism is applicable to both OSPFv2 and OSPFv3.Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].Status of This Memo ThisInternet-Draftissubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsan Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved fora maximumpublication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 ofsix monthsRFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on October 31, 2016.http://www.rfc-editor.org/info/rfc7884. Copyright Notice Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . 2....................................................3 1.1. RelationshipBetweenbetween OSPF and S-BFD. . . . . . . . . . . 3........................3 2. Implementation. . . . . . . . . . . . . . . . . . . . . . . 3..................................................3 2.1. S-BFD Discriminator TLV. . . . . . . . . . . . . . . . . 3....................................4 2.2. Flooding Scope. . . . . . . . . . . . . . . . . . . . . 4.............................................4 3. Backward Compatibility. . . . . . . . . . . . . . . . . . . 5..........................................5 4. Security Considerations. . . . . . . . . . . . . . . . . . . 5.........................................5 5. IANA Considerations. . . . . . . . . . . . . . . . . . . . . 5.............................................6 6.Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 7.References. . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1.......................................................6 6.1. Normative References. . . . . . . . . . . . . . . . . . 6 7.2........................................6 6.2. Informative References. . . . . . . . . . . . . . . . . 6.....................................6 Acknowledgements ...................................................7 Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . 6.................................................7 1. Introduction Seamless Bidirectional Forwarding Detection (S-BFD), specified in[I-D.ietf-bfd-seamless-base],[RFC7880], is a simplified mechanism for usingBidirectional Forwarding Detection (BFD)BFD with many negotiations eliminated. This is achieved by usingfour-octet4-octet discriminators, unique within an administrative domain, to identify theNetwork Targets.network targets. These S-BFDdiscriminatorsDiscriminators can be advertised by the IGPs, and this document concerns itself with OSPF. Specifically, this document defines a new TLV (named the S-BFD Discriminator TLV) to be carried within the OSPF Router Information (RI) Link State Advertisement (LSA)([RFC7770]).[RFC7770]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. 1.1. RelationshipBetweenbetween OSPF and S-BFD Thisdocument, implicitly,document implicitly defines a relationship between OSPF and S-BFD. S-BFD assigns one or more discriminators to each S-BFD reflector node. OSPF, in turn, learns about these fromS-BFD,S-BFD and floods them in the newly defined TLV. After this information is flooded, it is stored in all the OSPF nodes such that S-BFD initiators can map out target nodes to targetdiscriminators,discriminators and can therefore construct the S-BFD probe. When multiple S-BFDdiscriminatorsDiscriminators are advertised, how a given discriminator is mapped to a specific use case is out of scope for this document. 2. Implementation This extension makes use of the Router Information (RI) Opaque LSA, defined in[RFC7770] ,[RFC7770], for both OSPFv2 [RFC2328] and OSPFv3[RFC5340],[RFC5340] by defining a new OSPF Router Information (RI) TLV: the S-BFD Discriminator TLV. The S-BFD Discriminator TLV is OPTIONAL. Upon receipt of the TLV, a router may decide to install the S-BFDdiscriminatorDiscriminator in the BFDTarget Identifier Table.target identifier table. In the presence of multiple instances of theOSPF/OSPFv3 RIOSPFv2/OSPFv3 Router Information LSA, the S-BFDdiscriminatorsDiscriminators for an OSPF router are the union of all discriminators advertised in all instances of the S-BFD Discriminator TLV (see Section 2.1) in all advertised non-MaxAge OSPFRIRouter Information LSAs. 2.1. S-BFD Discriminator TLV The format of the S-BFD Discriminator TLV is as follows: 0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator 1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator 2 (Optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator n (Optional) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type - S-BFD Discriminator TLV Type(TBD [to be filled in by IANA])(11) Length -TotalThis field represents the total length of the discriminator(s) thatappearappears in the Value field, in octets. Each discriminator is 4 octets, so the Length is4four times the number of discriminators included in the TLV. There is no optional padding for this field. Discriminator(s) - The Value field of theTVLTLV includes the S-BFD network targetdiscriminatorDiscriminator value or values. Routers that do not recognize the S-BFD Discriminator TLV Type will ignore the TLV[RFC7770],[RFC7770] and therefore will not learn S-BFDdiscriminatorsDiscriminators via OSPF. 2.2. Flooding Scope The S-BFD Discriminator TLV is advertised within OSPFv2 Router Information LSAs (Opaque type of 4 and Opaque ID of 0) or OSPFv3 Router Information LSAs (function code of 12), which are defined in [RFC7770]. As such, elements of this procedure are inherited from those defined in [RFC7770].In OSPFv2, theThe flooding scope is controlled by theopaqueOpaque LSA type (as defined in [RFC5250])andinOSPFv3,OSPFv2 and by the S1/S2 bits (as defined in[RFC5340]).[RFC5340]) in OSPFv3. If the flooding scope is area local, then the S-BFD Discriminator TLV MUST be carried within an OSPFv2 type 10router informationRouter Information LSA or an OSPFV3 Router Information LSA with the S1 bit set and the S2 bit clear. If the flooding scope is the entire IGP domain, then the S-BFD Discriminator TLV MUST be carried within an OSPFv2 type 11 Router Information LSA or OSPFv3 Router Information LSA with the S1 bit clear and the S2 bit set. When the S-BFDReflectorreflector is deactivated, the OSPF speaker advertisingthisa particular S-BFDdiscriminatorDiscriminator MUST originate a new Router Information LSA that no longer includes the corresponding S-BFD Discriminator TLV, provided there are other TLVs in the LSA. If there are no other TLVs in the LSA, it MUST either send an empty Router Information LSA or purge it by prematurelyageingaging it. For intra-area reachability, the S-BFD Discriminator TLV information regarding a specific target identifier is only considered current anduseableusable when the router advertisingthisthat information is itself reachable via OSPF calculated paths in the same area of the LSA in which the S-BFD Discriminator TLV appears. In the case ofdomain- widedomain-wide flooding, i.e., where the originator is sitting in a remote area, the mechanism described insectionSection 5 of [RFC5250] should be used. Although the S-BFDdiscriminatorsDiscriminators may change when enabling the S-BFD functionality or via an explicit configuration event, such changes are expected to occur very rarely. Sucha changechanges intheinformation will require that the S-BFD Discriminator TLV in OSPFtobe advertised. A change in information in the S-BFD Discriminator TLV MUST NOT trigger any SPFcomputationcomputations at a receiving router. 3. Backward Compatibility The S-BFD Discriminator TLV defined in this document does not introduce any interoperability issues. A router not supporting the S-BFD Discriminator TLV will just silently ignore theTLVTLV, as specified in [RFC7770]. 4. Security Considerations This document defines OSPF extensions to distribute the S-BFDdiscriminatorDiscriminator within an administrative domain.HenceHence, the security oftheS-BFDdiscriminatorDiscriminator distribution relies on the security of OSPF. OSPF provides no encryption mechanism for protecting the privacy of LSAs and, in particular, the privacy of the S-BFDdiscriminatorDiscriminator advertisement information.This howeverHowever, this is not aconcernconcern, as there isn't any need to hide thediscriminatorDiscriminator value that can be used to reach theReflectors.reflectors. 5. IANA Considerations IANA has defined a registry for TLVs carried in the Router Information LSA defined in [RFC7770]. IANAneeds to assignhas assigned a new TLV codepoint (11) for the S-BFD Discriminator TLVcarried withinin the "OSPF Router InformationLSA.(RI) TLVs" registry. Value TLV Name Reference ----- -------- ----------TBD11 S-BFD(this document)RFC 7884 Discriminator 6.Acknowledgements The authors would like to thank Nobo Akiya, Les Ginsberg, Mach Chen and Peter Psenak for insightful comments and useful suggestions. 7.References7.1.6.1. Normative References[I-D.ietf-bfd-seamless-base] Akiya, N., Pignataro, C., Ward, D., Bhatia, M., and J. Networks, "Seamless Bidirectional Forwarding Detection (S-BFD)", draft-ietf-bfd-seamless-base-09 (work in progress), April 2016.[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>. [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, DOI 10.17487/RFC2328, April 1998, <http://www.rfc-editor.org/info/rfc2328>. [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, <http://www.rfc-editor.org/info/rfc5340>. [RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and S. Shaffer, "Extensions to OSPF for Advertising Optional Router Capabilities", RFC 7770, DOI 10.17487/RFC7770, February 2016, <http://www.rfc-editor.org/info/rfc7770>.7.2.[RFC7880] Pignataro, C., Ward, D., Akiya, N., Bhatia, M., and S. Pallagatti, "Seamless Bidirectional Forwarding Detection (S-BFD)", RFC 7880, DOI 10.17487/RFC7880, July 2016, <http://www.rfc-editor.org/info/rfc7880>. 6.2. Informative References [RFC5250] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The OSPF Opaque LSA Option", RFC 5250, DOI 10.17487/RFC5250, July 2008, <http://www.rfc-editor.org/info/rfc5250>. Acknowledgements The authors would like to thank Nobo Akiya, Les Ginsberg, Mach Chen, and Peter Psenak for insightful comments and useful suggestions. Authors' Addresses Carlos Pignataro Cisco Systems, Inc. Email: cpignata@cisco.com Manav Bhatia Ionos Networks Email: manav@ionosnetworks.com Sam Aldrin Huawei Technologies Email: aldrin.ietf@gmail.com Trilok Ranganath Nokia Email: trilok.ranganatha@nokia.com