< draft-idr-bgp-route-refresh-options-02.txt		draft-idr-bgp-route-refresh-options-03.txt >
	Network Working Group K. Patel		Network Working Group K. Patel
	Internet-Draft A. Vyavaharkar		Internet-Draft Arrcus, Inc
	Intended status: Standards Track N. Fazlollahi		Intended status: Standards Track A. Vyavaharkar
	Expires: September 7, 2017 Cisco Systems		Expires: March 1, 2018 Cisco Systems
			N. Fazlollahi
	A. Przygienda		A. Przygienda
	Juniper Networks		Juniper Networks
	March 06, 2017		August 28, 2017
	Extension to BGP's Route Refresh Message		Extension to BGP's Route Refresh Message
	draft-idr-bgp-route-refresh-options-02		draft-idr-bgp-route-refresh-options-03
	Abstract		Abstract
	[RFC2918] defines a route refresh capability to be exchanged between		[RFC2918] defines a route refresh capability to be exchanged between
	BGP speakers. BGP speakers that support this capability are		BGP speakers. BGP speakers that support this capability are
	advertising that they can resend the entire BGP Adj-RIB-Out on		advertising that they can resend the entire BGP Adj-RIB-Out on
	receipt of a refresh request. By supporting this capability, BGP		receipt of a refresh request. By supporting this capability, BGP
	speakers are more flexible in applying any inbound routing policy		speakers are more flexible in applying any inbound routing policy
	changes as they no longer have to store received routes in their		changes as they no longer have to store received routes in their
	unchanged form or reset the session when an inbound routing policy		unchanged form or reset the session when an inbound routing policy
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 6 ¶
	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 September 7, 2017.
			This Internet-Draft will expire on March 1, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 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 2, line 39 ¶		skipping to change at page 2, line 42 ¶
	not be created outside the IETF Standards Process, except to format		not be created outside the IETF Standards Process, except to format
	it for publication as an RFC or to translate it into languages other		it for publication as an RFC or to translate it into languages other
	than English.		than English.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
	1.1. Use Case Examples . . . . . . . . . . . . . . . . . . . . 3		1.1. Use Case Examples . . . . . . . . . . . . . . . . . . . . 3
	2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4		2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
	3. Route Refresh Options Capability . . . . . . . . . . . . . . 4		3. Route Refresh Options Capability . . . . . . . . . . . . . . 4
	4. Route Refresh Sub-Types . . . . . . . . . . . . . . . . . . . 4		4. Route Refresh Sub-Types . . . . . . . . . . . . . . . . . . . 5
	5. Route Refresh Option format . . . . . . . . . . . . . . . . . 5		5. Route Refresh Option format . . . . . . . . . . . . . . . . . 5
	6. Route Refresh Option Length . . . . . . . . . . . . . . . . . 6		6. Route Refresh Option Length . . . . . . . . . . . . . . . . . 6
	7. Route Refresh ID . . . . . . . . . . . . . . . . . . . . . . 6		7. Route Refresh ID . . . . . . . . . . . . . . . . . . . . . . 6
	8. Route Refresh Option Flags . . . . . . . . . . . . . . . . . 7		8. Route Refresh Option Flags . . . . . . . . . . . . . . . . . 7
	9. Route Refresh Options . . . . . . . . . . . . . . . . . . . . 8		9. Route Refresh Options . . . . . . . . . . . . . . . . . . . . 8
	10. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 9		10. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	11. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 11		11. Error Handling . . . . . . . . . . . . . . . . . . . . . . . 11
	12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12		12. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
	13. Security Considerations . . . . . . . . . . . . . . . . . . . 12		13. Security Considerations . . . . . . . . . . . . . . . . . . . 12
	14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12		14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
	skipping to change at page 12, line 42 ¶		skipping to change at page 12, line 46 ¶
	The authors would like to thank Anant Utgikar for initial discussions		The authors would like to thank Anant Utgikar for initial discussions
	resulting in this work. John Scudder and Jeff Hass provided further		resulting in this work. John Scudder and Jeff Hass provided further
	comments.		comments.
	15. References		15. References
	15.1. Normative References		15.1. Normative References
	[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,		[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
	DOI 10.17487/RFC1982, August 1996,		DOI 10.17487/RFC1982, August 1996, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc1982>.		editor.org/info/rfc1982>.
	[RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918,		[RFC2918] Chen, E., "Route Refresh Capability for BGP-4", RFC 2918,
	DOI 10.17487/RFC2918, September 2000,		DOI 10.17487/RFC2918, September 2000, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc2918>.		editor.org/info/rfc2918>.
	[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,		[RFC4684] Marques, P., Bonica, R., Fang, L., Martini, L., Raszuk,
	R., Patel, K., and J. Guichard, "Constrained Route		R., Patel, K., and J. Guichard, "Constrained Route
	Distribution for Border Gateway Protocol/MultiProtocol		Distribution for Border Gateway Protocol/MultiProtocol
	Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual		Label Switching (BGP/MPLS) Internet Protocol (IP) Virtual
	Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,		Private Networks (VPNs)", RFC 4684, DOI 10.17487/RFC4684,
	November 2006, <http://www.rfc-editor.org/info/rfc4684>.		November 2006, <https://www.rfc-editor.org/info/rfc4684>.
	[RFC5291] Chen, E. and Y. Rekhter, "Outbound Route Filtering		[RFC5291] Chen, E. and Y. Rekhter, "Outbound Route Filtering
	Capability for BGP-4", RFC 5291, DOI 10.17487/RFC5291,		Capability for BGP-4", RFC 5291, DOI 10.17487/RFC5291,
	August 2008, <http://www.rfc-editor.org/info/rfc5291>.		August 2008, <https://www.rfc-editor.org/info/rfc5291>.
	[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement		[RFC5492] Scudder, J. and R. Chandra, "Capabilities Advertisement
	with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February		with BGP-4", RFC 5492, DOI 10.17487/RFC5492, February
	2009, <http://www.rfc-editor.org/info/rfc5492>.		2009, <https://www.rfc-editor.org/info/rfc5492>.
	[RFC7313] Patel, K., Chen, E., and B. Venkatachalapathy, "Enhanced		[RFC7313] Patel, K., Chen, E., and B. Venkatachalapathy, "Enhanced
	Route Refresh Capability for BGP-4", RFC 7313,		Route Refresh Capability for BGP-4", RFC 7313,
	DOI 10.17487/RFC7313, July 2014,		DOI 10.17487/RFC7313, July 2014, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc7313>.		editor.org/info/rfc7313>.
	[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.		[RFC7606] Chen, E., Ed., Scudder, J., Ed., Mohapatra, P., and K.
	Patel, "Revised Error Handling for BGP UPDATE Messages",		Patel, "Revised Error Handling for BGP UPDATE Messages",
	RFC 7606, DOI 10.17487/RFC7606, August 2015,		RFC 7606, DOI 10.17487/RFC7606, August 2015,
	<http://www.rfc-editor.org/info/rfc7606>.		<https://www.rfc-editor.org/info/rfc7606>.
	15.2. Information References		15.2. Information 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,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc2119>.		editor.org/info/rfc2119>.
	[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A		[RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A
	Border Gateway Protocol 4 (BGP-4)", RFC 4271,		Border Gateway Protocol 4 (BGP-4)", RFC 4271,
	DOI 10.17487/RFC4271, January 2006,		DOI 10.17487/RFC4271, January 2006, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc4271>.		editor.org/info/rfc4271>.
	[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,		[RFC7432] Sajassi, A., Ed., Aggarwal, R., Bitar, N., Isaac, A.,
	Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based		Uttaro, J., Drake, J., and W. Henderickx, "BGP MPLS-Based
	Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February		Ethernet VPN", RFC 7432, DOI 10.17487/RFC7432, February
	2015, <http://www.rfc-editor.org/info/rfc7432>.		2015, <https://www.rfc-editor.org/info/rfc7432>.
	[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and		[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
	S. Ray, "North-Bound Distribution of Link-State and		S. Ray, "North-Bound Distribution of Link-State and
	Traffic Engineering (TE) Information Using BGP", RFC 7752,		Traffic Engineering (TE) Information Using BGP", RFC 7752,
	DOI 10.17487/RFC7752, March 2016,		DOI 10.17487/RFC7752, March 2016, <https://www.rfc-
	<http://www.rfc-editor.org/info/rfc7752>.		editor.org/info/rfc7752>.
	[Wikipedia]		[Wikipedia]
	Wikipedia, "https://en.wikipedia.org/wiki/		Wikipedia, "https://en.wikipedia.org/wiki/
	Serial_number_arithmetic", 2016.		Serial_number_arithmetic", 2016.
	Appendix A. Sequence Number Binary Arithmetic		Appendix A. Sequence Number Binary Arithmetic
	The only reasonably reference to a cleaner than [RFC1982] sequence		The only reasonably reference to a cleaner than [RFC1982] sequence
	number solution is given in [Wikipedia]. It basically converts the		number solution is given in [Wikipedia]. It basically converts the
	problem into two complement's arithmetic. Assuming a straight two		problem into two complement's arithmetic. Assuming a straight two
	skipping to change at page 15, line 8 ¶		skipping to change at page 15, line 8 ¶
	2 < < = > > > ? <		2 < < = > > > ? <
	3 < < < = > > > ?		3 < < < = > > > ?
	4 ? < < < = > > >		4 ? < < < = > > >
	5 > ? < < < = > >		5 > ? < < < = > >
	6 > > ? < < < = >		6 > > ? < < < = >
	7 > > > ? < < < =		7 > > > ? < < < =
	Authors' Addresses		Authors' Addresses
	Keyur Patel		Keyur Patel
	Cisco Systems		Arrcus, Inc
	821 Alder Drive
	Milpitas, CA 95035
	USA		USA
	Email: keyupate@cisco.com		Email: keyur@arrcus.com
	Aamod Vyavaharkar		Aamod Vyavaharkar
	Cisco Systems		Cisco Systems
	821 Alder Drive		821 Alder Drive
	Milpitas, CA 95035		Milpitas, CA 95035
	USA		USA
	Email: avyavaha@cisco.com		Email: avyavaha@cisco.com
	Niloofar Fazlollahi		Niloofar Fazlollahi
	Cisco Systems
	821 Alder Drive
	Milpitas, CA 95035
	USA		USA
	Email: nifazlol@cisco.com		Email: Niloofar_fazlollahi@yahoo.com
	Tony Przygienda		Tony Przygienda
	Juniper Networks		Juniper Networks
	1194 N. Mathilda Ave		1194 N. Mathilda Ave
	Sunnyvale, CA 94089		Sunnyvale, CA 94089
	USA		USA
	Email: prz@juniper.net		Email: prz@juniper.net
End of changes. 20 change blocks.
	32 lines changed or deleted		30 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/