draft-ietf-sidr-rpki-rtr-rfc6810-bis-06.txt		draft-ietf-sidr-rpki-rtr-rfc6810-bis-07.txt
	Network Working Group R. Bush		Network Working Group R. Bush
	Internet-Draft Internet Initiative Japan		Internet-Draft Internet Initiative Japan
	Obsoletes: 6810 (if approved) R. Austein		Obsoletes: 6810 (if approved) R. Austein
	Intended status: Standards Track Dragon Research Labs		Intended status: Standards Track Dragon Research Labs
	Expires: April 8, 2016 October 6, 2015		Expires: September 4, 2016 March 3, 2016
	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-06		draft-ietf-sidr-rpki-rtr-rfc6810-bis-07
	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 38		skipping to change at page 1, line 38
	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 April 8, 2016.		This Internet-Draft will expire on September 4, 2016.
	Copyright Notice		Copyright Notice
	Copyright (c) 2015 IETF Trust and the persons identified as the		Copyright (c) 2016 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 16, line 42		skipping to change at page 16, line 42
	An Error Report PDU MUST NOT be sent for an Error Report PDU. If an		An Error Report PDU MUST NOT be sent for an Error Report PDU. If an
	erroneous Error Report PDU is received, the session SHOULD be		erroneous Error Report PDU is received, the session SHOULD be
	dropped.		dropped.
	If the error is associated with a PDU of excessive length, i.e., too		If the error is associated with a PDU of excessive length, i.e., too
	long to be any legal PDU other than another Error Report, or a		long to be any legal PDU other than another Error Report, or a
	possibly corrupt length, the Erroneous PDU field MAY be truncated.		possibly corrupt length, the Erroneous PDU field MAY be truncated.
	The diagnostic text is optional; if not present, the Length of Error		The diagnostic text is optional; if not present, the Length of Error
	Text field MUST be zero. If error text is present, it MUST be a		Text field MUST be zero. If error text is present, it MUST be a
	string in UTF-8 encoding (see [RFC3269]).		string in UTF-8 encoding (see [RFC3629]).
	0 8 16 24 31		0 8 16 24 31
	.-------------------------------------------.		.-------------------------------------------.
	| Protocol | PDU | |		| Protocol | PDU | |
	| Version | Type | Error Code |		| Version | Type | Error Code |
	| 1 | 10 | |		| 1 | 10 | |
	+-------------------------------------------+		+-------------------------------------------+
	| |		| |
	| Length |		| Length |
	| |		| |
	skipping to change at page 31, line 33		skipping to change at page 31, line 33
	No doubt this list is incomplete. We apologize to any contributor		No doubt this list is incomplete. We apologize to any contributor
	whose name we missed.		whose name we missed.
	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., "BGPsec Algorithms, Key Formats, & Signature		Turner, S., "BGPsec Algorithms, Key Formats, & Signature
	Formats", draft-ietf-sidr-bgpsec-algs-11 (work in		Formats", draft-ietf-sidr-bgpsec-algs-14 (work in
	progress), August 2015.		progress), November 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.
	[RFC3269] Kermode, R. and L. Vicisano, "Author Guidelines for		[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
	Reliable Multicast Transport (RMT) Building Blocks and		10646", RFC 3629, STD 63, November 2003.
	Protocol Instantiation documents", RFC 3269, April 2002.
	[RFC4252] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)		[RFC4252] Ylonen, T. and C. Lonvick, "The Secure Shell (SSH)
	Authentication Protocol", RFC 4252, January 2006.		Authentication Protocol", RFC 4252, January 2006.
	[RFC4301] Kent, S. and K. Seo, "Security Architecture for the		[RFC4301] Kent, S. and K. Seo, "Security Architecture for the
	Internet Protocol", RFC 4301, December 2005.		Internet Protocol", RFC 4301, December 2005.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an		[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
	IANA Considerations Section in RFCs", RFC 5226, BCP 26,		IANA Considerations Section in RFCs", RFC 5226, BCP 26,
	May 2008.		May 2008.
	skipping to change at page 32, line 50		skipping to change at page 32, line 47
	[RFC6811] Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R.		[RFC6811] Mohapatra, P., Scudder, J., Ward, D., Bush, R., and R.
	Austein, "BGP Prefix Origin Validation", RFC 6811, January		Austein, "BGP Prefix Origin Validation", RFC 6811, January
	2013.		2013.
	16.2. Informative References		16.2. Informative References
	[RFC1996] Vixie, P., "A Mechanism for Prompt Notification of Zone		[RFC1996] Vixie, P., "A Mechanism for Prompt Notification of Zone
	Changes (DNS NOTIFY)", RFC 1996, August 1996.		Changes (DNS NOTIFY)", RFC 1996, August 1996.
	[RFC4808] Bellovin, S., "Key Change Strategies for TCP-MD5", RFC		[RFC4808] Bellovin, S., "Key Change Strategies for TCP-MD5",
	4808, March 2007.		RFC 4808, March 2007.
	[RFC5781] Weiler, S., Ward, D., and R. Housley, "The rsync URI		[RFC5781] Weiler, S., Ward, D., and R. Housley, "The rsync URI
	Scheme", RFC 5781, February 2010.		Scheme", RFC 5781, February 2010.
	[RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support		[RFC6480] Lepinski, M. and S. Kent, "An Infrastructure to Support
	Secure Internet Routing", RFC 6480, February 2012.		Secure Internet Routing", RFC 6480, February 2012.
	[RFC6481] Huston, G., Loomans, R., and G. Michaelson, "A Profile for		[RFC6481] Huston, G., Loomans, R., and G. Michaelson, "A Profile for
	Resource Certificate Repository Structure", RFC 6481,		Resource Certificate Repository Structure", RFC 6481,
	February 2012.		February 2012.
End of changes. 8 change blocks.
	12 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/