< draft-ietf-ospf-routable-ip-address-00.txt		draft-ietf-ospf-routable-ip-address-02.txt >
	Network Working Group X. Xu		Network Working Group X. Xu
	Internet-Draft Huawei		Internet-Draft Huawei
	Intended status: Standards Track U. Chunduri		Intended status: Standards Track U. Chunduri
	Expires: March 29, 2015 Ericsson		Expires: October 16, 2015 Ericsson
	M. Bhatia		M. Bhatia
	Ionos Networks		Ionos Networks
	September 25, 2014		April 14, 2015
	Carrying Routable IP Addresses in OSPF RI LSA		Carrying Routable IP Addresses in OSPF RI LSA
	draft-ietf-ospf-routable-ip-address-00		draft-ietf-ospf-routable-ip-address-02
	Abstract		Abstract
	This document proposes two new TLVs within the body of the OSPF		This document proposes two new TLVs within the body of the OSPF
	Router Information (RI) Opaque LSA, called Routable IPv4 Address TLV		Router Information (RI) Opaque LSA, called Routable IPv4 Address TLV
	and Routable IPv6 Address TLV. Here the OSPF means both OSPFv2 and		and Routable IPv6 Address TLV. Here the term OSPF means both OSPFv2
	OSPFv3.		and OSPFv3.
	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 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 March 29, 2015.		This Internet-Draft will expire on October 16, 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
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. Routable IPv4 Address TLV . . . . . . . . . . . . . . . . . . 3		3. Routable IPv4 Address TLV . . . . . . . . . . . . . . . . . . . 3
	4. Routable IPv6 Address TLV . . . . . . . . . . . . . . . . . . 3		4. Routable IPv6 Address TLV . . . . . . . . . . . . . . . . . . . 4
	5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3		5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 3		7. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . 4		8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
	8.1. Normative References . . . . . . . . . . . . . . . . . . 4		8.1. Normative References . . . . . . . . . . . . . . . . . . . 5
	8.2. Informative References . . . . . . . . . . . . . . . . . 4		8.2. Informative References . . . . . . . . . . . . . . . . . . 5
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	There are several situations where it is required for OSPF routers in		There are several situations where it is required for OSPF routers in
	one area to find correlations between routable IP addresses and		one area to find correlations between routable IP addresses and
	capabilities of OSPF routers in another area. One example is the		capabilities of OSPF routers in another area. One example is the
	Entropy Label Capability (ELC) advertisement [I-D.xu-ospf-mpls-elc]		Entropy Label Capability (ELC) advertisement [I-D.xu-ospf-mpls-elc]
	across the OSPF domain. In this example, assume the ELC TLV		across the OSPF domain. In this example, assume the ELC TLV
	originated by a router in one area is propagated to another area,		originated by a router in one area is propagated to another area.
	those routers in the latter area need to find routable IP addresses		Those routers in the latter area need to find routable IP addresses
	of the router originating that ELC TLV before inserting the Entropy		of the router originating that ELC TLV before inserting the Entropy
	Label (EL) for packets going to the Label Switch Path (LSP) tunnel		Label (EL) for packets going to the Label Switch Path (LSP) tunnel
	towards one of the above routable IP addresses. Another example is		towards one of the above routable IP addresses. Another example is
	the S-BFD discriminator distribution		the S-BFD discriminator distribution
	[I-D.bhatia-ospf-sbfd-discriminator] across the OSPF domain. In this		[I-D.ietf-ospf-sbfd-discriminator] across the OSPF domain. In this
	example, assume the S-BFD Discriminator TLV originated by a router in		example, assume the S-BFD Discriminator TLV originated by a router in
	one area is propagated to another area, those routers in the latter		one area is propagated to another area. Those routers in the latter
	area need to find routable IP addresses of the router originating		area need to find routable IP addresses of the router originating
	that S-BFD Discriminator TLV so as to set up S-BDF sessions with that		that S-BFD Discriminator TLV so as to set up S-BDF sessions with that
	originating router.		originating router.
	However, in the OSPF Router Information (RI) Opaque LSA as defined in		However, in the OSPF Router Information (RI) Opaque LSA as defined in
	[RFC4970], which is used by OSPF routers to announce their		[RFC4970], which is used by OSPF routers to announce their
	capabilities, there is no such field for containing routable IP		capabilities, there is no such field for containing routable IP
	addresses of the originating router. Therefore, this document		addresses of the originating router. Therefore, this document
	propose two new TLVs within the body of OSPF RI LSA, called Routable		propose two new TLVs within the body of OSPF RI LSA, called Routable
	IPv4 Address TLV and Routable IPv6 Address TLV, which are used to		IPv4 Address TLV and Routable IPv6 Address TLV, which are used to
	carry routable IPv4 and IPv6 addresses respectively. Here the OSPF		carry routable IPv4 and IPv6 addresses respectively. Here the term
	means both OSPFv2 and OSPFv3.		OSPF means both OSPFv2 and OSPFv3.
	1.1. Requirements Language		1.1. 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", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. Terminology		2. Terminology
	This memo makes use of the terms defined in [RFC4970].		This memo makes use of the terms defined in [RFC4970].
	3. Routable IPv4 Address TLV		3. Routable IPv4 Address TLV
	A new TLV within the body of the OSPF RI Opaque LSA, called Routable		A new TLV within the body of the OSPF RI Opaque LSA, called Routable
	IPv4 Address TLV is defined to carry one or more routable IPv4		IPv4 Address TLV is defined to carry one or more routable IPv4
	addresses of the router originating the RI LSA. The Type of this TLV		addresses of the router originating the RI LSA. The Type of this TLV
	is TBD, the Length is variable (multiple of 4), and the Value field		is TBD, the Length is variable (multiple of 4), and the Value field
	contains one or more routable IPv4 addresses of the router		contains one or more routable IPv4 addresses of the router
	originating the RI LSA. This TLV is applicable to OSPFv2 and for		originating the RI LSA. This TLV is applicable to OSPFv2 and for
	IPv4 Address Families (AFs) of OSPFv3 [RFC5838] within the body of		IPv4 Address Families (AFs) of OSPFv3 [RFC5838]. The scope of the
	the corresponding RI Opaque LSA. The scope of the advertisement MUST		advertisement MUST be domain-wide as mapping between the originator
	be domain-wide.		and advertised address is required only when crossing the area
			boundaries.
	4. Routable IPv6 Address TLV		4. Routable IPv6 Address TLV
	A new TLV within the body of the OSPFv3 RI Opaque LSA, called		A new TLV within the body of the OSPFv3 RI Opaque LSA, called
	Routable IPv6 Address TLV is defined to carry one or more routable		Routable IPv6 Address TLV is defined to carry one or more routable
	IPv6 global addresses of the router originating the RI LSA. The Type		IPv6 global addresses of the router originating the RI LSA. The Type
	of this TLV is TBD, the Length is variable (multiple of 16), and the		of this TLV is TBD, the Length is variable (multiple of 16), and the
	Value field contains one or more routable IPv6 global addresses of		Value field contains one or more routable IPv6 global addresses of
	the router originating the RI LSA. This TLV is only applicable to		the router originating the RI LSA. This TLV is only applicable to
	OSPFv3. The scope of the advertisement MUST be domain-wide.		OSPFv3. The scope of the advertisement MUST be domain-wide as
			mapping between the originator and advertised address is required
			only when crossing the area boundaries.
	5. Acknowledgements		5. Acknowledgements
	Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M.		Thanks Karsten Thomann, Anton Smirnov, Joel Jaeggli, Joel M. Halpern,
	Halpern, Wes George, Les Ginsberg, Abhay Roy, Mach Chen and Acee		Wes George, Les Ginsberg, Abhay Roy, Mach Chen, Peter Psenak and Acee
	Lindem for their support and valuable comments on this draft.		Lindem for their support and valuable comments on this draft.
	6. IANA Considerations		6. IANA Considerations
	This document includes a request to IANA to allocate two TLV type		This document includes a request to IANA to allocate two TLV type
	codes for the new RI LSA TLVs proposed in this document respectively.		codes for the new TLVs proposed in Section 3 and Section 4 of this
			document from OSPF Router Information (RI) TLVs Registry defined by
			[RFC4970].
	7. Security Considerations		7. Security Considerations
	This document does not introduce any new security risk.		This document describes a mechanism for advertising routable IP
			address information through OSPF Router Information Opaque LSA and
			does not introduce any new security issues other than what is
			specified by [RFC4970].
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S.		[RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S.
	Shaffer, "Extensions to OSPF for Advertising Optional		Shaffer, "Extensions to OSPF for Advertising Optional
	Router Capabilities", RFC 4970, July 2007.		Router Capabilities", RFC 4970, July 2007.
	8.2. Informative References		8.2. Informative References
	[I-D.bhatia-ospf-sbfd-discriminator]		[I-D.ietf-ospf-sbfd-discriminator]
	Bhatia, M., Ranganath, T., Pignataro, C., and S. Aldrin,		Bhatia, M., Pignataro, C., Aldrin, S., and T. Ranganath,
	"OSPF extensions to advertise S-BFD Target Discriminator",		"OSPF extensions to advertise S-BFD Target Discriminator",
	draft-bhatia-ospf-sbfd-discriminator-00 (work in		draft-ietf-ospf-sbfd-discriminator-01 (work in progress),
	progress), May 2014.		March 2015.
	[I-D.xu-ospf-mpls-elc]		[I-D.xu-ospf-mpls-elc]
	Xu, X., Kini, S., Sivabalan, S., and C. Filsfils,		Xu, X., Kini, S., Sivabalan, S., Filsfils, C., and S.
	"Signaling Entropy Label Capability Using OSPF", draft-xu-		Litkowski, "Signaling Entropy Label Capability Using
	ospf-mpls-elc-00 (work in progress), December 2013.		OSPF", draft-xu-ospf-mpls-elc-01 (work in progress),
			October 2014.
	[RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.		[RFC5838] Lindem, A., Mirtorabi, S., Roy, A., Barnes, M., and R.
	Aggarwal, "Support of Address Families in OSPFv3", RFC		Aggarwal, "Support of Address Families in OSPFv3",
	5838, April 2010.		RFC 5838, April 2010.
	Authors' Addresses		Authors' Addresses
	Xiaohu Xu		Xiaohu Xu
	Huawei		Huawei
	Email: xuxiaohu@huawei.com		Email: xuxiaohu@huawei.com
	Uma Chunduri		Uma Chunduri
	Ericsson		Ericsson
End of changes. 23 change blocks.
	44 lines changed or deleted		53 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/