< draft-ietf-idr-eag-distribution-12.txt		draft-ietf-idr-eag-distribution-13.txt >
	IDR Working Group Z. Wang		IDR Working Group Z. Wang
	Internet-Draft Q. Wu		Internet-Draft Q. Wu
	Intended status: Standards Track Huawei		Intended status: Standards Track Huawei
	Expires: November 18, 2020 J. Tantsura		Expires: May 19, 2021 J. Tantsura
	Apstra, Inc.		Apstra, Inc.
	K. Talaulikar		K. Talaulikar
	Cisco Systems		Cisco Systems
	May 17, 2020		November 15, 2020
	Distribution of Traffic Engineering Extended Admin Groups using BGP-LS		Distribution of Traffic Engineering Extended Admin Groups using BGP-LS
	draft-ietf-idr-eag-distribution-12		draft-ietf-idr-eag-distribution-13
	Abstract		Abstract
	Administrative groups (commonly referred to as "colors" or "link		Administrative groups are link attributes (commonly referred to as
	colors") are link attributes that are advertised by link state		"colors" or "link colors") advertised by link state protocols (e.g.
	protocols like IS-IS (Intermediate System to Intermediate System) and		ISIS or OSPF) and used for traffic engineering. These administrative
	OSPF (Open Shortest Path First) and used for traffic engineering.		groups were initially defined as 32 bit masks. As network usage
	These administrative groups have initially been defined as a fixed-		grew, these 32 bit masks were found to constrain traffic engineering.
	length 32-bit bitmask. As networks grew and more use-cases were		Therefore, link state protocols (ISIS, OSPF) were expanded to
	introduced, the 32-bit length was found to be constraining and hence		advertise a variable length administrative group.
	extended administrative groups were introduced in the link state
	protocols. The 32-bit administrative groups are already advertised
	as link attributes in BGP-LS (Border Gateway Protocol Link-State).
	This document defines extensions to BGP-LS for advertisement of the
	extended administrative groups.
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 November 18, 2020.		This Internet-Draft will expire on May 19, 2021.
	Copyright Notice		Copyright Notice
	Copyright (c) 2020 IETF Trust and the persons identified as the		Copyright (c) 2020 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
	2. Advertising Extended Administrative Groups in BGP-LS . . . . 3		2. Advertising Extended Administrative Groups in BGP-LS . . . . 3
	3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4		3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 4		4. Security Considerations . . . . . . . . . . . . . . . . . . . 4
	5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4		5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 4
	6. Normative References . . . . . . . . . . . . . . . . . . . . 4		6. Normative References . . . . . . . . . . . . . . . . . . . . 4
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
	1. Introduction		1. Introduction
	Administrative groups (commonly referred to as "colors" or "link		Administrative groups (commonly referred to as "colors" or "link
	skipping to change at page 3, line 44 ¶		skipping to change at page 3, line 36 ¶
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Extended Administrative Groups (variable) //		| Extended Administrative Groups (variable) //
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 1: Extended Administrative Groups TLV Format		Figure 1: Extended Administrative Groups TLV Format
	Where:		Where:
	o Type: 1173		o Type: 1173
	o Length: variable (MUST be multiple of 4); represents the total		o Length: variable length which represents the total length of the
	length of the value field in octets.		value field. The length value must MUST be multiple of 4. If the
			length is not a multiple of 4, the TLV must be considered
			malformed.
	o Value : one or more sets of 32-bit bitmasks that indicate the		o Value: one or more sets of 32-bit bitmasks that indicate the
	administrative groups (colors) that are enable on the link when		administrative groups (colors) that are enable on the link when
	those specific bits are set.		those specific bits are set.
	The EAG TLV is an optional TLV. The existing AG TLV 108 and the EAG		The EAG TLV is an optional TLV. The existing AG TLV 108 and the EAG
	TLV defined in this document MAY be advertised together. The		TLV defined in this document MAY be advertised together. The
	semantics of the EAG and the backward compatibility aspects of EAG		semantics of the EAG and the backward compatibility aspects of EAG
	with respect to the AG are handled as described in the Backward		with respect to the AG are handled as described in the Backward
	Compatibility section of [RFC7308].		Compatibility section of [RFC7308].
	3. IANA Considerations		3. IANA Considerations
	skipping to change at page 4, line 26 ¶		skipping to change at page 4, line 23 ¶
	| Code Point | Description | IS-IS TLV/Sub-TLV |		| Code Point | Description | IS-IS TLV/Sub-TLV |
	+------------+-------------------------------+-------------------+		+------------+-------------------------------+-------------------+
	| 1173 | Extended Administrative Group | 22/14 |		| 1173 | Extended Administrative Group | 22/14 |
	+------------+-------------------------------+-------------------+		+------------+-------------------------------+-------------------+
	4. Security Considerations		4. Security Considerations
	The extensions in this document advertise same administrative group		The extensions in this document advertise same administrative group
	information specified via [RFC7752] but as a larger/extended value		information specified via [RFC7752] but as a larger/extended value
	and hence does not introduce security issues beyond those discussed		and hence does not introduce security issues beyond those discussed
	in [RFC7752].		in [RFC7752] and [I-D.ietf-idr-rfc7752bis] .
	5. Acknowledgments		5. Acknowledgments
	The authors gratefully acknowledge the review by Eric Osborne and Les		The authors gratefully acknowledge the review by Eric Osborne and Les
	Ginsberg.		Ginsberg.
	6. Normative References		6. Normative References
			[I-D.ietf-idr-rfc7752bis]
			Talaulikar, K., "Distribution of Link-State and Traffic
			Engineering Information Using BGP", draft-ietf-idr-
			rfc7752bis-04 (work in progress), September 2020.
	[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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering		[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
	(TE) Extensions to OSPF Version 2", RFC 3630,		(TE) Extensions to OSPF Version 2", RFC 3630,
	DOI 10.17487/RFC3630, September 2003,		DOI 10.17487/RFC3630, September 2003,
	<https://www.rfc-editor.org/info/rfc3630>.		<https://www.rfc-editor.org/info/rfc3630>.
End of changes. 10 change blocks.
	21 lines changed or deleted		23 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/