draft-ietf-sidr-rpki-rtr-rfc6810-bis-02.txt		draft-ietf-sidr-rpki-rtr-rfc6810-bis-03.txt
	Network Working Group R. Bush		Network Working Group R. Bush
	Internet-Draft Internet Initiative Japan		Internet-Draft Internet Initiative Japan
	Intended status: Standards Track R. Austein		Intended status: Standards Track R. Austein
	Expires: March 2, 2015 Dragon Research Labs		Expires: September 6, 2015 Dragon Research Labs
	August 29, 2014		March 5, 2015
	The Resource Public Key Infrastructure (RPKI) to Router Protocol		The Resource Public Key Infrastructure (RPKI) to Router Protocol
	draft-ietf-sidr-rpki-rtr-rfc6810-bis-02		draft-ietf-sidr-rpki-rtr-rfc6810-bis-03
	Abstract		Abstract
	In order to verifiably validate the origin Autonomous Systems and		In order to verifiably validate the origin Autonomous Systems and
	Autonomous System Paths of BGP announcements, routers need a simple		Autonomous System Paths of BGP announcements, routers need a simple
	but reliable mechanism to receive Resource Public Key Infrastructure		but reliable mechanism to receive Resource Public Key Infrastructure
	(RFC 6480) prefix origin data and router keys from a trusted cache.		(RFC 6480) prefix origin data and router keys from a trusted cache.
	This document describes a protocol to deliver validated prefix origin		This document describes a protocol to deliver validated prefix origin
	data and router keys to routers.		data and router keys to routers.
	skipping to change at page 1, line 36		skipping to change at page 1, line 36
	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 2, 2015.		This Internet-Draft will expire on September 6, 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
	skipping to change at page 28, line 38		skipping to change at page 28, line 38
	Raszuk, Andreas Reuter, Thomas C. Schmidt, John Scudder, Ruediger		Raszuk, Andreas Reuter, Thomas C. Schmidt, John Scudder, Ruediger
	Volk, Matthias Waehlisch, and David Ward. Particular thanks go to		Volk, Matthias Waehlisch, and David Ward. Particular thanks go to
	Hannes Gredler for showing us the dangers of unnecessary fields.		Hannes Gredler for showing us the dangers of unnecessary fields.
	16. References		16. References
	16.1. Normative References		16.1. Normative References
	[I-D.ietf-sidr-bgpsec-algs]		[I-D.ietf-sidr-bgpsec-algs]
	Turner, S., "BGP Algorithms, Key Formats, & Signature		Turner, S., "BGP Algorithms, Key Formats, & Signature
	Formats", draft-ietf-sidr-bgpsec-algs-08 (work in		Formats", draft-ietf-sidr-bgpsec-algs-09 (work in
	progress), July 2014.		progress), January 2015.
	[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,		[RFC1982] Elz, R. and R. Bush, "Serial Number Arithmetic", RFC 1982,
	August 1996.		August 1996.
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", RFC 2119, BCP 14, March 1997.		Requirement Levels", RFC 2119, BCP 14, March 1997.
	[RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5		[RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5
	Signature Option", RFC 2385, August 1998.		Signature Option", RFC 2385, August 1998.
End of changes. 5 change blocks.
	7 lines changed or deleted		7 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/