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

Document Type Active Internet-Draft (lsr WG)
Last updated 2018-10-03 (latest revision 2018-08-27)
Replaces draft-keyupate-ospf-ospfv2-hbit
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Yingzhen Qu
Shepherd write-up Show (last changed 2018-09-04)
IESG IESG state Publication Requested
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to Yingzhen Qu <yingzhen.ietf@gmail.com>
OSPF                                                            K. Patel
Internet-Draft                                                    Arrcus
Updates: 2328 (if approved)                            P. Pillay-Esnault
Intended status: Standards Track                     Huawei Technologies
Expires: February 28, 2019                                   M. Bhardwaj
                                                            S. Bayraktar
                                                           Cisco Systems
                                                         August 27, 2018

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

Abstract

   OSPFv3 defines an option bit for router-LSAs known as the R-bit in
   RFC5340.  If the R-bit is clear, an OSPFv3 router can participate in
   OSPF topology flooding, however it will not be used as a transit
   router.  In such cases, other routers in the OSPFv3 routing domain
   only install routes to allow local traffic delivery.  This document
   defines the H-bit functionality to prevent other OSPFv2 routers from
   using the router for transit traffic in OSPFv2 routing domains as
   described in RFC 2328.  This document updates 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 February 28, 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

Patel, et al.           Expires February 28, 2019               [Page 1]
Internet-Draft                                               August 2018

   (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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  H-bit Support . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  SPF Modifications . . . . . . . . . . . . . . . . . . . . . .   5
   5.  Auto Discovery and Backward Compatibility . . . . . . . . . .   5
   6.  OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics . . . . .   6
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

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

   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 locations such as data centers.
Show full document text