OSPF                                                            K. Patel
Internet-Draft                                                    Arrcus
Intended status: Standards Track                       P. Pillay-Esnault
Expires: August 1, 2018 February 2, 2019                            Huawei Technologies
                                                             M. Bhardwaj
                                                            S. Bayraktar
                                                           Cisco Systems
                                                        January 28,
                                                          August 1, 2018

                        H-bit Support for OSPFv2
                     draft-ietf-ospf-ospfv2-hbit-04
                     draft-ietf-ospf-ospfv2-hbit-05

Abstract

   OSPFv3 defines an option field bit for router-LSAs known as a the R-bit in
   RFC5340.  If the R-bit is clear, an OSPFv3 router can participate in
   OSPF topology distribution without acting flooding, however it will not used as a forwarder to forward
   the transit traffic. router.
   In such cases, an OSPF router would other routers in the OSPFv3 routing domain only accept
   traffic intended for
   install routes to allow local traffic delivery.  This draft defines R-bit
   the H-bit functionality to prevent other OSPFv2 routers from using
   the router for transit traffic in OSPFv2 defined routing domains as described
   in RFC2328. RFC 2328.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   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 August 1, 2018. February 2, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  H-bit Support . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  SPF Modifications . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Auto Discovery and Backwards Backward Compatibility . . . . . . . . . .   5
   6.  OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   10. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   11.
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7   8

1.  Introduction

   OSPFv3 [RFC5340] defines an option field bit for router-LSAs known as a the
   R-bit.  If the R-bit is clear, an OSPF OSPFv3 router can participate in
   OSPFv3 topology distribution flooding without acting as a forwarder to forward
   the transit traffic. router.  In such
   cases, an OSPF router would other routers in the OSPFv3 routing domain only accept
   traffic intended install routes
   used for local delivery. traffic.

   This functionality is particularly useful for BGP Route Reflectors Reflectors,
   known as virtual Route Reflectors (vRRs) (vRRs), that are not in the
   forwarding path but are in central location locations such as data centers.
   Such Route Reflectors typically are used for route distribution and
   are not capable of forwarding data transit traffic.  However, they need to
   participate in
   learn the IGP routing OSPF topology for: 1) computing SPFs

   1.  SPF computation for Optimal Route Reflection functionality as
       defined in
   [I-D.ietf-idr-bgp-optimal-route-reflection], and 2) resolving
   reachability [I-D.ietf-idr-bgp-optimal-route-reflection]

   2.  Reachability resolution for its Route Reflector Clients.

   This draft defines the R-bit functionality equivalent for OSPFv2
   defined in [RFC2328] by introducing a new Router LSA router-LSA bit known as a the
   "H-bit".

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when when, they appear in all upper case.  They may also appear in lower or
   mixed case
   capitals, as English words, without any normative meaning. shown here.

3.  H-bit Support

   This draft document defines a new Router-LSA router-LSA bit known as a the Host Bit or a
   the H-bit.  The  An OSPFv2 router advertising a router-LSA with the H-bit
   set indicates to other OSPFv2 routers in the OSPFv2's capability of acting area supporting the
   functionality that it MUST NOT be used as a transit router.  When set, the OSPFv2 router indicates that the
   transit capability is disabled.  The bit
   value usage of the H-bit is reversed as opposed to from the R-bit value defined in OSPFv3
   [RFC5340] to support backward compatibility.  The modified OSPFv2 Router LSA
   router-LSA format is
   defined as: is:

        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
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |            LS age             |     Options   |       1       |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                        Link State ID                          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     Advertising Router                        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                     LS sequence number                        |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |         LS checksum           |             length            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |H|0|0|N|W|V|E|B|        0      |            # links            |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          Link ID                              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         Link Data                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Type      |     # TOS     |            metric             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                              ...                              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |      TOS      |        0      |          TOS  metric          |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                          Link ID                              |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                         Link Data                             |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |                              ...                              |

      bit H
          When set, an OSPFv2 router is a non-transit router and is
          incapable of acting as a forwarder. forwarding transit traffic.

   When the H-bit is set, an OSPFv2 router is a non-transit router and is
   incapable of acting as a forwarder.
   should not be used to forward transit traffic.  In this mode, the
   other OSPFv2 routers in the area SHOULD NOT use the originating
   OSPFv2 router for the transit traffic, but they will MAY use the OSPFv2 router for data
   local traffic destined to that OSPFv2 router.

   An OSPFv2 router originating a
   Router LSA router-LSA with the H-bit set SHOULD
   advertise all its LINKS non-local router links with MAX
   Link a link cost of
   MaxLinkMetric as defined in Section 3 of [RFC6987].  This is to
   increase the applicability of the H-bit in to partial deployments where
   it is the responsibility of the operator to ensure that OSPFv2
   routers not supporting the H-bit does do not
   result in install routes causing
   routing loops.

   When the H-bit is set, IPv4 prefixes associated with local interfaces
   in other areas MAY be advertised in summary LSAs.  Non-local IPv4
   prefixes, e.g., those advertised by other routers and installed
   during the SPF computation, MAY be advertised in summary-LSAs if
   configured by policy.  Likewise, when the H-bit is set, only IPv4
   prefixes associated with local interfaces MAY be advertised in AS-external AS-
   external LSAs.  Non-local IPv4 prefixes, e.g., those exported from
   other routing protocols, MUST NOT be advertised in AS-external-LSAs.
   Finally, when the H-bit is set, an
   ABR Area Border Router (ABR) MUST
   advertise a consistent H-bit setting in its self-originated
   router-LSAs router-
   LSAs for all attached areas.

4.  SPF Modifications

   The SPF calculation described in section 16.1 [RFC2328] will be
   modified to assure ensure that the routers originating router-LSAs with the
   H-bit set will not be used for transit traffic.  Step 2 is modified
   as follows:

                2) Call the vertex just added to the
                   tree vertex V.  Examine the LSA
                   associated with vertex V.  This is
                   a lookup in the Area A's link state
                   database based on the Vertex ID. If
                   this is a router-LSA, and the H-bit
                   of the router-LSA is set, and
                   vertex V is not the root, then the
                   router should not be used for transit
                   and step (3) should be executed
                   immediately. If this is a router-LSA,
                   and bit V of the router-LSA (see
                   Section A.4.2) is set, set Area A's
                   TransitCapability to TRUE. In any case,
                   each link described by the LSA gives
                   the cost to an adjacent vertex.  For
                   each described link, (say it joins
                   vertex V to vertex W):

5.  Auto Discovery and Backwards Backward Compatibility

   To avoid the possibility of any routing loops due to partial
   deployments,
   deployment, this draft document defines a new OSPF Router Functional
   Capability Router-Information LSA
   functional capability bit known as a the Host Support Capability.  The value of this
   capability is a bit value to be assigned by IANA from OSPF Router
   Functional Capability Bits registry [RFC7770] .

   The capability.

   Auto Discovery via announcement of the Host Support Functional
   Capability ensures that the H-bit functionality and its associated
   SPF changes SHOULD only take effect if all the routers in a given
   OSPF area support this functionality.

   Implementations are encouraged to provide a knob configuration parameter
   to manually override enforcement of the H-bit functionality in
   partial deployment
   scenarios for cases deployments where the topology guarantees that the router OSPFv2 routers
   not supporting the H-bit will do not cause compute routes resulting in routing
   loops.  More precisely, the advertisement of MaxLinkMetric for the
   router's non-local links will prevent OSPFv2 routers not supporting
   the H-bit from attempting to use it for transit traffic.

6.  OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics

   When calculating the path to an OSPF AS-External-LSA or NSSA-LSA with
   a Type-2 metric, the advertised Type-2 metric is taken as more
   significant than the OSPF intra-area or inter-area path.  Hence,
   advertising the links with MaxLinkMetric as specified in [RFC6987]
   does not discourage transit traffic when calculating AS external or
   NSSA routes.  Consequently, OSPF routers implementing [RFC6987] or
   this specification should advertise a Type-2 metric of LSInfinity for
   any self-originated AS-External-LSAs or NSSA-LSAs in situations when
   the OSPF router is acting as a stub router [RFC6987] or implementing
   this specification.

7.  IANA Considerations

   This draft defines a new Router LSA bit known as a H-bit.  This draft
   requests

   IANA is requested to 1) Create a new create the OSPF Router LSA bits Router-LSA bit registry and 2)
   assign a H-bit code type from with the newly allocated OSPF
   following assignments:

        Value   Description                                 Reference
        0x01    Area Border Router LSA bit
   registry. (B-bit)                  [RFC2328]
        0x02    AS Boundary Router (E-bit)                  [RFC2328]
        0x04    Virtual Link Endpoint (V-bit)               [RFC2328]
        0x08    Historic (W-bit)                            [RFC1584]
        0x10    Unconditional NSSA Translator (Nt-bit)      [RFC3101]
        0x20    Unassigned
        0x40    Unassigned
        0x80    Host (H-bit)                            This draft Document

   This document also defines a new Router Functional Capability
   [RFC7770] known as a the Host Support Functional Capability.  This draft
   document requests IANA to allocate the value of this capability from
   the Router Functional Capability Bits TLV.

8.  Security Considerations

   This document introduces no new security considerations above and beyond those
   already specified in [RFC2328] [RFC6987], [RFC2328], and [RFC5340].

9.  Acknowledgements

   The authors would like to acknowledge Hasmit Grover for discovery of
   the limitation in [RFC6987], Acee Lindem, Abhay Roy, David Ward,
   Burjiz Pithawala and Michael Barnes for their comments.

10.  Change Log

   Initial Version:  April 23 2015

11.  References

11.1.

10.1.  Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <https://www.rfc-editor.org/info/rfc2119>.

   [RFC2328]  Moy, J., "OSPF Version 2", STD 54, RFC 2328,
              DOI 10.17487/RFC2328, April 1998,
              <https://www.rfc-editor.org/info/rfc2328>.

   [RFC3101]  Murphy, P., "The OSPF Not-So-Stubby Area (NSSA) Option",
              RFC 3101, DOI 10.17487/RFC3101, January 2003,
              <https://www.rfc-editor.org/info/rfc3101>.

   [RFC5340]  Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF
              for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
              <https://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, <https://www.rfc-editor.org/info/rfc7770>.

11.2.

   [RFC8174]  Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
              2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
              May 2017, <https://www.rfc-editor.org/info/rfc8174>.

10.2.  Informative References

   [I-D.ietf-idr-bgp-optimal-route-reflection]
              Raszuk, R., Cassar, C., Aman, E., Decraene, B., Litkowski,
              S., and K.
              Wang, "BGP Optimal Route Reflection (BGP-ORR)",
              draft-ietf-idr-bgp-optimal-route-reflection-13 draft-
              ietf-idr-bgp-optimal-route-reflection-16 (work in
              progress), January 2017. April 2018.

   [RFC1584]  Moy, J., "Multicast Extensions to OSPF", RFC 1584,
              DOI 10.17487/RFC1584, March 1994,
              <https://www.rfc-editor.org/info/rfc1584>.

   [RFC6987]  Retana, A., Nguyen, L., Zinin, A., White, R., and D.
              McPherson, "OSPF Stub Router Advertisement", RFC 6987,
              DOI 10.17487/RFC6987, September 2013,
              <https://www.rfc-editor.org/info/rfc6987>.

Authors' Addresses

   Keyur Patel
   Arrcus

   Email: keyur@arrcus.com

   Padma Pillay-Esnault
   Huawei Technologies
   2330 Central Expressway
   Santa Clara,  CA 95050
   USA

   Email: padma@huawei.com

   Manish Bhardwaj
   Cisco Systems
   170 W. Tasman Drive
   San Jose,  CA 95134
   USA

   Email: manbhard@cisco.com

   Serpil Bayraktar
   Cisco Systems
   170 W. Tasman Drive
   San Jose,  CA 95134
   USA

   Email: serpil@cisco.com