< draft-ietf-ospf-ospfv2-hbit-02.txt		draft-ietf-ospf-ospfv2-hbit-03.txt >
	OSPF K. Patel		OSPF K. Patel
	Internet-Draft Arrcus		Internet-Draft Arrcus
	Intended status: Standards Track P. Pillay-Esnault		Intended status: Standards Track P. Pillay-Esnault
	Expires: October 12, 2017 Huawei Technologies		Expires: December 16, 2017 Huawei Technologies
	M. Bhardwaj		M. Bhardwaj
	S. Bayraktar		S. Bayraktar
	Cisco Systems		Cisco Systems
	April 10, 2017		June 14, 2017
	H-bit Support for OSPFv2		H-bit Support for OSPFv2
	draft-ietf-ospf-ospfv2-hbit-02		draft-ietf-ospf-ospfv2-hbit-03
	Abstract		Abstract
	OSPFv3 defines an option field for router-LSAs known as a R-bit in		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		RFC5340. If the R-bit is clear, an OSPFv3 router can participate in
	OSPF topology distribution without acting as a forwarder to forward		OSPF topology distribution without acting as a forwarder to forward
	the transit traffic. In such cases, an OSPF router would only accept		the transit traffic. In such cases, an OSPF router would only accept
	traffic intended for local delivery. This draft defines R-bit		traffic intended for local delivery. This draft defines R-bit
	functionality for OSPFv2 defined in RFC2328.		functionality for OSPFv2 defined in RFC2328.
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	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 http://datatracker.ietf.org/drafts/current/.		Drafts is at http://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 October 12, 2017.		This Internet-Draft will expire on December 16, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://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
	skipping to change at page 6, line 18 ¶		skipping to change at page 6, line 18 ¶
	OSPF area support this functionality.		OSPF area support this functionality.
	Implementations are encouraged to provide a knob to manually override		Implementations are encouraged to provide a knob to manually override
	enforcement of the H-bit functionality in partial deployment		enforcement of the H-bit functionality in partial deployment
	scenarios for cases where the topology guarantees that the router		scenarios for cases where the topology guarantees that the router
	supporting the H-bit will not cause routing loops.		supporting the H-bit will not cause routing loops.
	6. OSPF AS-External-LSAs/NSSA LSAs with Type 2 Metrics		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		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 an more		a Type-2 metric, the advertised Type-2 metric is taken as more
	significant than the OSPF intra-area or inter-area path. Hence,		significant than the OSPF intra-area or inter-area path. Hence,
	advertising the links with MaxLinkMetric as specified in [RFC6987]		advertising the links with MaxLinkMetric as specified in [RFC6987]
	does not discourage transit traffic when calculating AS external or		does not discourage transit traffic when calculating AS external or
	NSSA routes. Consequently, OSPF routers implementing [RFC6987] or		NSSA routes. Consequently, OSPF routers implementing [RFC6987] or
	this specification should advertise a Type-2 metric of LSInfinity for		this specification should advertise a Type-2 metric of LSInfinity for
	any self-originated AS-External-LSAs or NSSA-LSAs in situations when		any self-originated AS-External-LSAs or NSSA-LSAs in situations when
	the OSPF router is acting as a stub router [RFC6987] or implementing		the OSPF router is acting as a stub router [RFC6987] or implementing
	this specification.		this specification.
	7. IANA Considerations		7. IANA Considerations
End of changes. 5 change blocks.
	5 lines changed or deleted		5 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/