< draft-azimov-sidrops-aspa-profile-00.txt		draft-azimov-sidrops-aspa-profile-01.txt >
	Network Working Group A. Azimov		Network Working Group A. Azimov
	Internet-Draft E. Uskov		Internet-Draft E. Uskov
	Intended status: Standards Track Qrator Labs		Intended status: Standards Track Qrator Labs
	Expires: December 30, 2018 R. Bush		Expires: July 10, 2019 R. Bush
	Internet Initiative Japan		Internet Initiative Japan
	K. Patel		K. Patel
	Arrcus		Arrcus
	J. Snijders		J. Snijders
	NTT		NTT
	R. Housley		R. Housley
	Vigil Security		Vigil Security
	June 28, 2018		January 6, 2019
	A Profile for Autonomous System Provider Authorization		A Profile for Autonomous System Provider Authorization
	draft-azimov-sidrops-aspa-profile-00		draft-azimov-sidrops-aspa-profile-01
	Abstract		Abstract
	This document defines a standard profile for Autonomous System		This document defines a standard profile for Autonomous System
	Provider Authorization in the Resource Public Key Infrastructure. An		Provider Authorization in the Resource Public Key Infrastructure. An
	Autonomous System Provider Authorization is a digitally signed object		Autonomous System Provider Authorization is a digitally signed object
	that provides a means of verifying that a Customer Autonomous System		that provides a means of verifying that a Customer Autonomous System
	holder has authorized a Provider Autonomous System to be its upstream		holder has authorized a Provider Autonomous System to be its upstream
	provider and for the Provider to send prefixes received from the		provider and for the Provider to send prefixes received from the
	Customer Autonomous System in all directions including providers and		Customer Autonomous System in all directions including providers and
	skipping to change at page 1, line 46 ¶		skipping to change at page 1, line 46 ¶
	capitals, as shown here.		capitals, as shown here.
	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 http://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 December 30, 2018.		This Internet-Draft will expire on July 10, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2019 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		(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
	skipping to change at page 7, line 38 ¶		skipping to change at page 7, line 38 ¶
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[IANA-AF] IANA, "Address Family Numbers",		[IANA-AF] IANA, "Address Family Numbers",
	<http://www.iana.org/numbers.html>.		<http://www.iana.org/numbers.html>.
	[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, <https://www.rfc-		DOI 10.17487/RFC2119, March 1997,
	editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP		[RFC3779] Lynn, C., Kent, S., and K. Seo, "X.509 Extensions for IP
	Addresses and AS Identifiers", RFC 3779,		Addresses and AS Identifiers", RFC 3779,
	DOI 10.17487/RFC3779, June 2004, <https://www.rfc-		DOI 10.17487/RFC3779, June 2004,
	editor.org/info/rfc3779>.		<https://www.rfc-editor.org/info/rfc3779>.
	[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70,		[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70,
	RFC 5652, DOI 10.17487/RFC5652, September 2009,		RFC 5652, DOI 10.17487/RFC5652, September 2009,
	<https://www.rfc-editor.org/info/rfc5652>.		<https://www.rfc-editor.org/info/rfc5652>.
	[RFC6485] Huston, G., "The Profile for Algorithms and Key Sizes for		[RFC6485] Huston, G., "The Profile for Algorithms and Key Sizes for
	Use in the Resource Public Key Infrastructure (RPKI)",		Use in the Resource Public Key Infrastructure (RPKI)",
	RFC 6485, DOI 10.17487/RFC6485, February 2012,		RFC 6485, DOI 10.17487/RFC6485, February 2012,
	<https://www.rfc-editor.org/info/rfc6485>.		<https://www.rfc-editor.org/info/rfc6485>.
	skipping to change at page 8, line 39 ¶		skipping to change at page 8, line 39 ¶
	[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, DOI 10.17487/RFC6480,		Secure Internet Routing", RFC 6480, DOI 10.17487/RFC6480,
	February 2012, <https://www.rfc-editor.org/info/rfc6480>.		February 2012, <https://www.rfc-editor.org/info/rfc6480>.
	Authors' Addresses		Authors' Addresses
	Alexander Azimov		Alexander Azimov
	Qrator Labs		Qrator Labs
	Email: aa@qrator.net		Email: a.e.azimov@gmail.com
	Eugene Uskov		Eugene Uskov
	Qrator Labs		Qrator Labs
	Email: eu@qrator.net		Email: eu@qrator.net
	Randy Bush		Randy Bush
	Internet Initiative Japan		Internet Initiative Japan
	Email: randy@psg.com		Email: randy@psg.com
End of changes. 10 change blocks.
	12 lines changed or deleted		12 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/