draft-ietf-idr-aigp-09.txt		draft-ietf-idr-aigp-10.txt
	Network Working Group Pradosh Mohapatra		Network Working Group Pradosh Mohapatra
	Internet Draft Rex Fernando		Internet Draft Cumulus Networks
	Intended Status: Proposed Standard Eric C. Rosen		Intended Status: Proposed Standard
	Expires: May 27, 2013 Cisco Systems, Inc.		Expires: November 23, 2013 Rex Fernando
			Eric C. Rosen
			Cisco Systems, Inc.
	James Uttaro		James Uttaro
	ATT		ATT
	November 27, 2012		May 23, 2013
	The Accumulated IGP Metric Attribute for BGP		The Accumulated IGP Metric Attribute for BGP
	draft-ietf-idr-aigp-09.txt		draft-ietf-idr-aigp-10.txt
	Abstract		Abstract
	Routing protocols that have been designed to run within a single		Routing protocols that have been designed to run within a single
	administrative domain ("IGPs") generally do so by assigning a metric		administrative domain ("IGPs") generally do so by assigning a metric
	to each link, and then choosing as the installed path between two		to each link, and then choosing as the installed path between two
	nodes the path for which the total distance (sum of the metric of		nodes the path for which the total distance (sum of the metric of
	each link along the path) is minimized. BGP, designed to provide		each link along the path) is minimized. BGP, designed to provide
	routing over a large number of independent administrative domains		routing over a large number of independent administrative domains
	("autonomous systems"), does not make its path selection decisions		("autonomous systems"), does not make its path selection decisions
	skipping to change at page 2, line 14		skipping to change at page 2, line 18
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Copyright and License Notice		Copyright and License Notice
	Copyright (c) 2012 IETF Trust and the persons identified as the		Copyright (c) 2013 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 3, line 25		skipping to change at page 3, line 25
	3.3.3 Modifications by a Non-Originator ..................... 8		3.3.3 Modifications by a Non-Originator ..................... 8
	4 Decision Process ...................................... 10		4 Decision Process ...................................... 10
	4.1 When a Route has an AIGP Attribute .................... 10		4.1 When a Route has an AIGP Attribute .................... 10
	4.2 When the Route to the Next Hop has an AIGP attribute .. 11		4.2 When the Route to the Next Hop has an AIGP attribute .. 11
	5 Deployment Considerations ............................. 12		5 Deployment Considerations ............................. 12
	6 IANA Considerations ................................... 12		6 IANA Considerations ................................... 12
	7 Security Considerations ............................... 12		7 Security Considerations ............................... 12
	8 Acknowledgments ....................................... 12		8 Acknowledgments ....................................... 12
	9 Authors' Addresses .................................... 13		9 Authors' Addresses .................................... 13
	10 Normative References .................................. 13		10 Normative References .................................. 13
	11 Informative References ................................ 14		11 Informative References ................................ 13
	1. Specification of requirements		1. Specification of requirements
	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 [RFC2119].		document are to be interpreted as described in [RFC2119].
	2. Introduction		2. Introduction
	There are many routing protocols that have been designed to run		There are many routing protocols that have been designed to run
	skipping to change at page 13, line 14		skipping to change at page 13, line 14
	9. Authors' Addresses		9. Authors' Addresses
	Rex Fernando		Rex Fernando
	Cisco Systems, Inc.		Cisco Systems, Inc.
	170 Tasman Drive		170 Tasman Drive
	San Jose, CA 95134		San Jose, CA 95134
	Email: rex@cisco.com		Email: rex@cisco.com
	Pradosh Mohapatra		Pradosh Mohapatra
	Cisco Systems, Inc.		Cumulus Networks
	170 Tasman Drive		Email: pmohapat@cumulusnetworks.com
	San Jose, CA 95134
	Email: pmohapat@cisco.com
	Eric C. Rosen		Eric C. Rosen
	Cisco Systems, Inc.		Cisco Systems, Inc.
	1414 Massachusetts Avenue		1414 Massachusetts Avenue
	Boxborough, MA, 01719		Boxborough, MA, 01719
	Email: erosen@cisco.com		Email: erosen@cisco.com
	James Uttaro		James Uttaro
	AT&T		AT&T
	200 S. Laurel Avenue		200 S. Laurel Avenue
	skipping to change at page 14, line 9		skipping to change at page 13, line 38
	10. Normative References		10. Normative References
	[BGP], "A Border Gateway Protocol 4 (BGP-4)", Y. Rekhter, T. Li, S.		[BGP], "A Border Gateway Protocol 4 (BGP-4)", Y. Rekhter, T. Li, S.
	Hares, RFC 4271, January 2006.		Hares, RFC 4271, January 2006.
	11. Informative References		11. Informative References
	[ADDPATH] "Fast Connectivity Restoration Using BGP Add-Path", P.		[ADDPATH] "Fast Connectivity Restoration Using BGP Add-Path", P.
	Mohapatra, R. Fernando, C. Filsfils, R. Raszuk, draft-pmohapat-idr-		Mohapatra, R. Fernando, C. Filsfils, R. Raszuk, draft-pmohapat-idr-
	fast-conn-restore-02.txt, October 2011.		fast-conn-restore-03.txt, January 2013.
	[BESTEXT], "Advertisement of the Best External Route in BGP", P.		[BESTEXT], "Advertisement of the Best External Route in BGP", P.
	Marques, R. Fernando, E. Chen, P. Mohapatra, H. Gredler, draft-ietf-		Marques, R. Fernando, E. Chen, P. Mohapatra, H. Gredler, draft-ietf-
	idr-best-external-05.txt, January 2012.		idr-best-external-05.txt, January 2012.
	[RFC2119] "Key words for use in RFCs to Indicate Requirement		[RFC2119] "Key words for use in RFCs to Indicate Requirement
	Levels.", S. Bradner, March 1997.		Levels.", S. Bradner, March 1997.
End of changes. 7 change blocks.
	12 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/