draft-ietf-ospf-ospfv2-hbit-05.txt   draft-ietf-ospf-ospfv2-hbit-06.txt 
OSPF K. Patel OSPF K. Patel
Internet-Draft Arrcus Internet-Draft Arrcus
Intended status: Standards Track P. Pillay-Esnault Updates: 2328 (if approved) P. Pillay-Esnault
Expires: February 2, 2019 Huawei Technologies Intended status: Standards Track Huawei Technologies
M. Bhardwaj Expires: February 28, 2019 M. Bhardwaj
S. Bayraktar S. Bayraktar
Cisco Systems Cisco Systems
August 1, 2018 August 27, 2018
H-bit Support for OSPFv2 H-bit Support for OSPFv2
draft-ietf-ospf-ospfv2-hbit-05 draft-ietf-ospf-ospfv2-hbit-06
Abstract Abstract
OSPFv3 defines an option bit for router-LSAs known as the R-bit in 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 RFC5340. If the R-bit is clear, an OSPFv3 router can participate in
OSPF topology flooding, however it will not used as a transit router. OSPF topology flooding, however it will not be used as a transit
In such cases, other routers in the OSPFv3 routing domain only router. In such cases, other routers in the OSPFv3 routing domain
install routes to allow local traffic delivery. This draft defines only install routes to allow local traffic delivery. This document
the H-bit functionality to prevent other OSPFv2 routers from using defines the H-bit functionality to prevent other OSPFv2 routers from
the router for transit traffic in OSPFv2 routing domains as described using the router for transit traffic in OSPFv2 routing domains as
in RFC 2328. described in RFC 2328. This document updates RFC 2328.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 2, 2019. This Internet-Draft will expire on February 28, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. 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 Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. H-bit Support . . . . . . . . . . . . . . . . . . . . . . . . 3 3. H-bit Support . . . . . . . . . . . . . . . . . . . . . . . . 3
4. SPF Modifications . . . . . . . . . . . . . . . . . . . . . . 5 4. SPF Modifications . . . . . . . . . . . . . . . . . . . . . . 5
5. Auto Discovery and Backward Compatibility . . . . . . . . . . 5 5. Auto Discovery and Backward Compatibility . . . . . . . . . . 5
6. OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics . . . . . 6 6. OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics . . . . . 6
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 7 8. Security Considerations . . . . . . . . . . . . . . . . . . . 7
skipping to change at page 2, line 48 skipping to change at page 3, line 12
forwarding path but are in central locations such as data centers. forwarding path but are in central locations such as data centers.
Such Route Reflectors typically are used for route distribution and Such Route Reflectors typically are used for route distribution and
are not capable of forwarding transit traffic. However, they need to are not capable of forwarding transit traffic. However, they need to
learn the OSPF topology for: learn the OSPF topology for:
1. SPF computation for Optimal Route Reflection functionality as 1. SPF computation for Optimal Route Reflection functionality as
defined in [I-D.ietf-idr-bgp-optimal-route-reflection] defined in [I-D.ietf-idr-bgp-optimal-route-reflection]
2. Reachability resolution for its Route Reflector Clients. 2. Reachability resolution for its Route Reflector Clients.
This draft defines the R-bit functionality equivalent for OSPFv2 This document defines the R-bit functionality equivalent for OSPFv2
defined in [RFC2328] by introducing a new router-LSA bit known as the defined in [RFC2328] by introducing a new router-LSA bit known as the
"H-bit". "H-bit". This document updates appendix A.4.2 of RFC 2328.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. H-bit Support 3. H-bit Support
 End of changes. 8 change blocks. 
14 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/