< draft-psarkar-isis-node-admin-tag-01.txt		draft-psarkar-isis-node-admin-tag-02.txt >
	IS-IS for IP Internets P. Sarkar, Ed.		IS-IS for IP Internets P. Sarkar, Ed.
	Internet-Draft H. Gredler		Internet-Draft H. Gredler
	Intended status: Standards Track S. Hegde		Intended status: Standards Track S. Hegde
	Expires: August 18, 2014 H. Raghuveer		Expires: January 2, 2015 Juniper Networks, Inc.
	Juniper Networks, Inc.
	S. Litkowski		S. Litkowski
	B. Decraene		B. Decraene
	Orange		Orange
	February 14, 2014		Z. Li
			Huawei Technologies
			H. Raghuveer
			July 1, 2014
	Advertising Per-node Admin Tags in IS-IS		Advertising Per-node Admin Tags in IS-IS
	draft-psarkar-isis-node-admin-tag-01		draft-psarkar-isis-node-admin-tag-02
	Abstract		Abstract
	This document describes an extension to IS-IS protocol [ISO10589],		This document describes an extension to IS-IS protocol [ISO10589],
	[RFC1195] to add an optional operational capability, that allows		[RFC1195] to add an optional operational capability, that allows
	tagging and grouping ofthe nodes in an IS-IS domain. This allows		tagging and grouping ofthe nodes in an IS-IS domain. This allows
	simple management and easy control over route and path selection,		simple management and easy control over route and path selection,
	based on local configured policies.		based on local configured policies.
	This document describes the protocol extensions to disseminate per-		This document describes the protocol extensions to disseminate per-
	node admin-tags in IS-IS protocols.		node admin-tags in IS-IS protocols.
	Requirements Language		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].
	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 January 2, 2015.
	This Internet-Draft will expire on August 18, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Administrative Tag . . . . . . . . . . . . . . . . . . . . . . 3		2. Administrative Tag . . . . . . . . . . . . . . . . . . . . . 2
	3. TLV format . . . . . . . . . . . . . . . . . . . . . . . . . . 3		3. TLV format . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3.1. Per-node Admin Tag sub-TLV . . . . . . . . . . . . . . . . 3		3.1. Per-node Admin Tag sub-TLV . . . . . . . . . . . . . . . 3
	3.2. Ordering of tags . . . . . . . . . . . . . . . . . . . . . 4		3.2. Ordering of tags . . . . . . . . . . . . . . . . . . . . 4
	4. Applications . . . . . . . . . . . . . . . . . . . . . . . . . 4		4. Applications . . . . . . . . . . . . . . . . . . . . . . . . 5
	5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5		5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
	6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5		6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
	7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 5		7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5		8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
	8.1. Normative References . . . . . . . . . . . . . . . . . . . 5		8.1. Normative References . . . . . . . . . . . . . . . . . . 5
	8.2. Informative References . . . . . . . . . . . . . . . . . . 5		8.2. Informative References . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
	1. Introduction		1. Introduction
	This document provides mechanisms to advertise per-node		This document provides mechanisms to advertise per-node
	administrative tags in the IS-IS Link State PDU [RFC1195]. In		administrative tags in the IS-IS Link State PDU [RFC1195]. In
	certain path-selection applications like for example in traffic-		certain path-selection applications like for example in traffic-
	engineering or LFA [RFC5286] selection there is a need to tag the		engineering or LFA [RFC5286] selection there is a need to tag the
	nodes based on their roles in the network and have policies to prefer		nodes based on their roles in the network and have policies to prefer
	or prune a certain group of nodes.		or prune a certain group of nodes.
	skipping to change at page 5, line 16 ¶		skipping to change at page 5, line 20 ¶
	refinements to address those limitations. One of the proposed		refinements to address those limitations. One of the proposed
	refinements is to be able to group the nodes in IGP domain with		refinements is to be able to group the nodes in IGP domain with
	administrative tags and engineer the alternate paths based on		administrative tags and engineer the alternate paths based on
	configured policies.		configured policies.
	The proposal in this document helps provide the capability to		The proposal in this document helps provide the capability to
	advertise group tags within IS-IS protocol and perform policy based		advertise group tags within IS-IS protocol and perform policy based
	LFA selection. The policies configured on each node can then make		LFA selection. The policies configured on each node can then make
	use of these tags to prefer or prune LFAs via certain group of nodes.		use of these tags to prefer or prune LFAs via certain group of nodes.
			For a detailed list of more such applications please refer to section
			5 in [I-D.hegde-ospf-node-admin-tag].
	5. Security Considerations		5. Security Considerations
	This document does not introduce any further security issues other		This document does not introduce any further security issues other
	than those discussed in [ISO10589] and [RFC1195].		than those discussed in [ISO10589] and [RFC1195].
	6. IANA Considerations		6. IANA Considerations
	IANA maintains the registry for the Router Capability sub-TLVs.		IANA maintains the registry for the Router Capability sub-TLVs. IS-
	IS-IS Administrative Tags will require one new type code for the sub-		IS Administrative Tags will require one new type code for the sub-TLV
	TLV defined in this document.		defined in this document.
	7. Acknowledgments		7. Acknowledgments
	8. References		8. References
	8.1. Normative References		8.1. Normative References
	[ISO10589]		[ISO10589]
	"Intermediate system to Intermediate system intra-domain		"Intermediate system to Intermediate system intra-domain
	routeing information exchange protocol for use in		routeing information exchange protocol for use in
	conjunction with the protocol for providing the		conjunction with the protocol for providing the
	connectionless-mode Network Service (ISO 8473), ISO/IEC		connectionless-mode Network Service (ISO 8473), ISO/IEC
	10589:2002, Second Edition.", Nov 2002.		10589:2002, Second Edition.", Nov 2002.
	[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.
	8.2. Informative References		8.2. Informative References
			[I-D.hegde-ospf-node-admin-tag]
			Hegde, S., Raghuveer, H., Gredler, H., Shakir, R.,
			Smirnov, A., and Z. Li, "Advertising per-node
			administrative tags in OSPF", draft-hegde-ospf-node-admin-
			tag-02 (work in progress), June 2014.
	[I-D.ietf-rtgwg-lfa-manageability]		[I-D.ietf-rtgwg-lfa-manageability]
	Litkowski, S., Decraene, B., Filsfils, C., and K. Raza,		Litkowski, S., Decraene, B., Filsfils, C., and K. Raza,
	"Operational management of Loop Free Alternates",		"Operational management of Loop Free Alternates", draft-
	draft-ietf-rtgwg-lfa-manageability-00 (work in progress),		ietf-rtgwg-lfa-manageability-00 (work in progress), May
	May 2013.		2013.
	[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and		[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
	dual environments", RFC 1195, December 1990.		dual environments", RFC 1195, December 1990.
	[RFC4971] Vasseur, JP., Shen, N., and R. Aggarwal, "Intermediate		[RFC4971] Vasseur, JP., Shen, N., and R. Aggarwal, "Intermediate
	System to Intermediate System (IS-IS) Extensions for		System to Intermediate System (IS-IS) Extensions for
	Advertising Router Information", RFC 4971, July 2007.		Advertising Router Information", RFC 4971, July 2007.
	[RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast		[RFC5286] Atlas, A. and A. Zinin, "Basic Specification for IP Fast
	Reroute: Loop-Free Alternates", RFC 5286, September 2008.		Reroute: Loop-Free Alternates", RFC 5286, September 2008.
	skipping to change at page 6, line 37 ¶		skipping to change at page 7, line 4 ¶
	Email: psarkar@juniper.net		Email: psarkar@juniper.net
	Hannes Gredler		Hannes Gredler
	Juniper Networks, Inc.		Juniper Networks, Inc.
	1194 N. Mathilda Ave.		1194 N. Mathilda Ave.
	Sunnyvale, CA 94089		Sunnyvale, CA 94089
	US		US
	Email: hannes@juniper.net		Email: hannes@juniper.net
	Shraddha Hegde		Shraddha Hegde
	Juniper Networks, Inc.		Juniper Networks, Inc.
	Electra, Exora Business Park		Electra, Exora Business Park
	Bangalore, KA 560103		Bangalore, KA 560103
	India		India
	Email: shraddha@juniper.net		Email: shraddha@juniper.net
	Harish Raghuveer
	Juniper Networks, Inc.
	Electra, Exora Business Park
	Bangalore, KA 560103
	India
	Email: hraghuveer@juniper.net
	Stephane Litkowski		Stephane Litkowski
	Orange		Orange
	Email: stephane.litkowski@orange.com		Email: stephane.litkowski@orange.com
	Bruno Decraene		Bruno Decraene
	Orange		Orange
	Email: bruno.decraene@orange.com		Email: bruno.decraene@orange.com
			Li Zhenbin
			Huawei Technologies
			Huawei Bld. No.156 Beiqing Rd
			Beijing, KA 100095
			China
			Email: lizhenbin@huawei.com
			Harish Raghuveer
			Email: hraghuveer@juniper.net
End of changes. 13 change blocks.
	34 lines changed or deleted		37 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/