Diff: draft-ietf-ospf-prefix-link-attr-09.txt - draft-ietf-ospf-prefix-link-attr-10.txt

	< draft-ietf-ospf-prefix-link-attr-09.txt	draft-ietf-ospf-prefix-link-attr-10.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: February 6, 2016 Juniper Networks, Inc.	Expires: February 12, 2016 Juniper Networks, Inc.
	R. Shakir	R. Shakir
	Individual Contributor	Individual Contributor
	W. Henderickx	W. Henderickx
	Alcatel-Lucent	Alcatel-Lucent
	J. Tantsura	J. Tantsura
	Ericsson	Ericsson
	A. Lindem	A. Lindem
	Cisco Systems	Cisco Systems

	August 5, 2015	August 11, 2015

	OSPFv2 Prefix/Link Attribute Advertisement	OSPFv2 Prefix/Link Attribute Advertisement

	draft-ietf-ospf-prefix-link-attr-09.txt	draft-ietf-ospf-prefix-link-attr-10.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 February 6, 2016.	This Internet-Draft will expire on February 12, 2016.

	Copyright Notice	Copyright Notice

	Copyright (c) 2015 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

	skipping to change at page 6, line 34 ¶	skipping to change at page 6, line 34 ¶

	5 - AS External	5 - AS External

	7 - NSSA External	7 - NSSA External

	These route types correspond directly to the OSPFv2 LSAs types as	These route types correspond directly to the OSPFv2 LSAs types as
	defined in http://www.iana.org/assignments/ospfv2-parameters/	defined in http://www.iana.org/assignments/ospfv2-parameters/
	ospfv2-parameters.xhtml#ospfv2-parameters-5.	ospfv2-parameters.xhtml#ospfv2-parameters-5.

	Prefix Length	Prefix Length

	Length in of the prefix in bits.	Length in 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. OSPFv3 [OSPFV3] is used for OSPF	value is 0 for IPv4 unicast. OSPFv3 [OSPFV3] is used for OSPF
	advertisement of IPv6 prefixes so this address family is not	advertisement of IPv6 prefixes so this address family is not
	applicable. The inclusion of address family in this TLV allows	applicable. The inclusion of address family in this TLV allows
	for future extension.	for future extension.

	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 \|N \| \| \| \| \| \| \|	\|A\|N\| \| \| \| \| \| \|
	+--+--+--+--+--+--+--+--+	+-+-+-+-+-+-+-+-+

	where:	where:

	A-Flag: Attach flag. An Area Border Router (ABR) generating an	A-Flag: Attach flag. An Area Border Router (ABR) generating an
	Extended Prefix TLV for inter-area prefix that is locally	Extended Prefix TLV for inter-area prefix that is locally
	connected or attached in other connected area SHOULD set this	connected or attached in other connected area SHOULD set this
	flag.	flag.

	N-Flag: Set when the prefix identifies the advertising router	N-Flag: Set when the prefix identifies the advertising router
	i.e., the prefix is a host prefix advertising a globally	i.e., the prefix is a host prefix advertising a globally
	reachable address typically associated with a loopback address.	reachable address typically associated with a loopback address.
	The advertising router MAY choose to NOT set this flag even	The advertising router MAY choose to NOT set this flag even
	when the above conditions are met. If the flag is set and the	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	prefix length is NOT a host prefix then the flag MUST be
	ignored. The flag is preserved when the OSPFv2 Extended Prefix	ignored. The flag is preserved when the OSPFv2 Extended Prefix
	Opaque LSA is propagated between areas.	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 a 32-bit value. The default route is
	padded with zeroed bits as necessary. This encoding consumes
	((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.

	If this TLV is advertised multiple times for the same prefix in	If this TLV is advertised multiple times for the same prefix in
	different OSPFv2 Extended Prefix Opaque LSAs originated by the same	different OSPFv2 Extended Prefix Opaque LSAs originated by the same
	OSPF router, the OSPF advertising router is re-originating Extended	OSPF router, the OSPF advertising router is re-originating Extended

	skipping to change at page 10, line 27 ¶	skipping to change at page 10, line 27 ¶
	ascending order of Instance to minimize the disruption.	ascending order of Instance to minimize the disruption.

	This document creates a registry for OSPF Extended Link sub-TLVs in	This document creates a registry for OSPF Extended Link sub-TLVs in
	Section 7.	Section 7.

	4. Backward Compatibility	4. Backward Compatibility

	Since opaque OSPFv2 LSAs are optional and backward compatible	Since opaque OSPFv2 LSAs are optional and backward compatible
	[OPAQUE], the extensions described herein are fully backward	[OPAQUE], the extensions described herein are fully backward
	compatible. However, future OSPFv2 extensions utilizing these	compatible. However, future OSPFv2 extensions utilizing these

	extensions must address backward compatibility of the corresponding	extensions MUST address backward compatibility of the corresponding
	functionality.	functionality.

	5. Implementation Status	5. Implementation Status

	Note to RFC Editor: this section may be removed on publication as an	Note to RFC Editor: this section may be removed on publication as an
	RFC.	RFC.

	This section records the status of known implementations of the	This section records the status of known implementations of the
	protocol defined by this specification at the time of posting of this	protocol defined by this specification at the time of posting of this
	Internet-Draft, and is based on a proposal described in RFC 6982.	Internet-Draft, and is based on a proposal described in RFC 6982.

	skipping to change at page 14, line 21 ¶	skipping to change at page 14, line 21 ¶
	Thanks to Tony Przygienda for his review and comments.	Thanks to Tony Przygienda for his review and comments.

	Thanks to Wim Henderickx, Greg Harkins, Peter Psenak, Eric Wu,	Thanks to Wim Henderickx, Greg Harkins, Peter Psenak, Eric Wu,
	Shraddha Hegde, and Csaba Mate for their responses to the	Shraddha Hegde, and Csaba Mate for their responses to the
	implementation survey.	implementation survey.

	Thanks to Alia Atlas for AD review and comments.	Thanks to Alia Atlas for AD review and comments.

	Thanks to Tom Petch for review and comments.	Thanks to Tom Petch for review and comments.


		Thanks to Carlos Pignataro for Operations Directorate Review and
		Comments.

	9. References	9. References

	9.1. Normative References	9.1. Normative References

	[OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The	[OPAQUE] Berger, L., Bryskin, I., Zinin, A., and R. Coltun, "The
	OSPF Opaque LSA Option", RFC 5250, July 2008.	OSPF Opaque LSA Option", RFC 5250, July 2008.

	[OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.	[OSPFV2] Moy, J., "OSPF Version 2", RFC 2328, April 1998.

	[RFC-KEYWORDS]	[RFC-KEYWORDS]

End of changes. 9 change blocks.
	13 lines changed or deleted	14 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/