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

Document Type Active Internet-Draft (lsr WG)
Last updated 2018-02-28 (latest revision 2018-01-28)
Replaces draft-keyupate-ospf-ospfv2-hbit
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
OSPF                                                            K. Patel
Internet-Draft                                                    Arrcus
Intended status: Standards Track                       P. Pillay-Esnault
Expires: August 1, 2018                              Huawei Technologies
                                                             M. Bhardwaj
                                                            S. Bayraktar
                                                           Cisco Systems
                                                        January 28, 2018

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

Abstract

   OSPFv3 defines an option field for router-LSAs known as a R-bit in
   RFC5340.  If the R-bit is clear, an OSPFv3 router can participate in
   OSPF topology distribution without acting as a forwarder to forward
   the transit traffic.  In such cases, an OSPF router would only accept
   traffic intended for local delivery.  This draft defines R-bit
   functionality for OSPFv2 defined in RFC2328.

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.

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

Patel, et al.            Expires August 1, 2018                 [Page 1]
Internet-Draft                                              January 2018

   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 Compatibility  . . . . . . . . .   5
   6.  OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   10. Change Log  . . . . . . . . . . . . . . . . . . . . . . . . .   7
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     11.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     11.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

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

   This functionality is particularly useful for BGP Route Reflectors
   known as virtual Route Reflectors (vRRs) that are not in the
   forwarding path but are in central location such as data centers.
   Such Route Reflectors typically are used for route distribution and
   are not capable of forwarding data traffic.  However, they need to
   participate in the IGP routing for: 1) computing SPFs for Optimal
   Route Reflection functionality defined in
   [I-D.ietf-idr-bgp-optimal-route-reflection], and 2) resolving
   reachability for its Route Reflector Clients.

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

Patel, et al.            Expires August 1, 2018                 [Page 2]
Internet-Draft                                              January 2018

2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text