< draft-ietf-ospf-prefix-link-attr-02.txt		draft-ietf-ospf-prefix-link-attr-03.txt >
	Network Working Group P. Psenak		Network Working Group P. Psenak
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track H. Gredler		Intended status: Standards Track H. Gredler
	Expires: June 18, 2015 Juniper Networks, Inc.		Expires: August 5, 2015 Juniper Networks, Inc.
	R. Shakir		R. Shakir
	British Telcom		British Telcom
	W. Henderickx		W. Henderickx
	Alcatel-Lucent		Alcatel-Lucent
	J. Tantsura		J. Tantsura
	Ericsson		Ericsson
	A. Lindem		A. Lindem
	Cisco Systems		Cisco Systems
	December 15, 2014		February 1, 2015
	OSPFv2 Prefix/Link Attribute Advertisement		OSPFv2 Prefix/Link Attribute Advertisement
	draft-ietf-ospf-prefix-link-attr-02.txt		draft-ietf-ospf-prefix-link-attr-03.txt
	Abstract		Abstract
	OSPFv2 requires functional extension beyond what can readily be done		OSPFv2 requires functional extension beyond what can readily be done
	with the fixed-format Link State Advertisements (LSAs) as described		with the fixed-format Link State Advertisements (LSAs) as described
	in RFC 2328. This document defines OSPF opaque LSAs based on Type-		in RFC 2328. This document defines OSPF opaque LSAs based on Type-
	Length-Value (TLV) tuples that can be used to associate additional		Length-Value (TLV) tuples that can be used to associate additional
	attributes with prefixes or links. Dependent on the application,		attributes with prefixes or links. Dependent on the application,
	these prefixes and links may or not be advertised in the fixed-format		these prefixes and links may or not be advertised in the fixed-format
	LSAs. The OSPF opaque LSAs are optional and fully backward		LSAs. The OSPF opaque LSAs are optional and fully backward
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	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 June 18, 2015.		This Internet-Draft will expire on August 5, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2015 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
	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
	skipping to change at page 6, line 40 ¶		skipping to change at page 6, line 40 ¶
	Length in of the prefix in bits.		Length in of the prefix in bits.
	AF		AF
	Address family for the prefix. Currently, the only supported		Address family for the prefix. Currently, the only supported
	value is 0 for IPv4 unicast.		value is 0 for IPv4 unicast.
	Flags: 1 octet field. The following flags are defined:		Flags: 1 octet field. The following flags are defined:
	0 1 2 3 4 5 6 7		0 1 2 3 4 5 6 7
	+--+--+--+--+--+--+--+--+		+--+--+--+--+--+--+--+--+
	|A | | | | | | | |		|A |N | | | | | | |
	+--+--+--+--+--+--+--+--+		+--+--+--+--+--+--+--+--+
	where:		where:
	A-Flag: Attach flag. An ABR generating Extended Prefix TLV for		A-Flag: Attach flag. An ABR generating Extended Prefix TLV for
	inter-area prefix that is locally connected or attached in		inter-area prefix that is locally connected or attached in
	other connected area SHOULD set this flag.		other connected area SHOULD set this flag.
			N-Flag: Set when the prefix identifies the advertising router
			i.e., the prefix is a host prefix advertising a globally
			reachable address typically associated with a loopback address.
			The advertising router MAY choose to NOT set this flag even
			when the above conditions are met. If the flag is set and the
			prefix length is NOT a host prefix then the flag MUST be
			ignored. The flag is preserved when OSPFv2 Extended Prefix
			Opaque LSA is propagated between areas.
	Address Prefix		Address Prefix
	The prefix itself encoded as an even multiple of 32-bit words,		The prefix itself encoded as an even multiple of 32-bit words,
	padded with zeroed bits as necessary. This encoding consumes		padded with zeroed bits as necessary. This encoding consumes
	((PrefixLength + 31) / 32) 32-bit words. The default route is		((PrefixLength + 31) / 32) 32-bit words. The default route is
	represented by a prefix of length 0.		represented by a prefix of length 0.
	If this TLV is advertised multiple times for the same prefix in the		If this TLV is advertised multiple times for the same prefix in the
	same OSPFv2 Extended Prefix Opaque LSA, only the first instance is		same OSPFv2 Extended Prefix Opaque LSA, only the first instance is
	used by receiving OSPFv2 Routers. This situation SHOULD be logged as		used by receiving OSPFv2 Routers. This situation SHOULD be logged as
	an error.		an error.
End of changes. 7 change blocks.
	6 lines changed or deleted		16 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/