draft-ietf-sidr-rpki-rtr-impl-04.txt		draft-ietf-sidr-rpki-rtr-impl-05.txt
	Network Working Group R. Bush		Network Working Group R. Bush
	Internet-Draft Internet Initiative Japan		Internet-Draft Internet Initiative Japan
	Intended status: Informational R. Austein		Intended status: Informational R. Austein
	Expires: April 18, 2014 Dragon Research Labs		Expires: June 14, 2014 Dragon Research Labs
	K. Patel		K. Patel
	Cisco Systems		Cisco Systems
	H. Gredler		H. Gredler
	Juniper Networks, Inc.		Juniper Networks, Inc.
	M. Waehlisch		M. Waehlisch
	FU Berlin		FU Berlin
	October 15, 2013		December 11, 2013
	RPKI Router Implementation Report		RPKI Router Implementation Report
	draft-ietf-sidr-rpki-rtr-impl-04		draft-ietf-sidr-rpki-rtr-impl-05
	Abstract		Abstract
	This document is an implementation report for the RPKI Router		This document is an implementation report for the RPKI Router
	protocol as defined in [RFC6810]. The editor did not verify the		protocol as defined in [RFC6810]. The editor did not verify the
	accuracy of the information provided by respondents. The respondents		accuracy of the information provided by respondents. The respondents
	are experts with the implementations they reported on, and their		are experts with the implementations they reported on, and their
	responses are considered authoritative for the implementations for		responses are considered authoritative for the implementations for
	which their responses represent. Respondents were asked to only use		which their responses represent. Respondents were asked to only use
	the YES answer if the feature had at least been tested in the lab.		the YES answer if the feature had at least been tested in the lab.
	skipping to change at page 1, line 43		skipping to change at page 1, line 43
	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 18, 2014.		This Internet-Draft will expire on June 14, 2014.
	Copyright Notice		Copyright Notice
	Copyright (c) 2013 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
	skipping to change at page 2, line 31		skipping to change at page 2, line 31
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Implementation Forms . . . . . . . . . . . . . . . . . . . . 3		2. Implementation Forms . . . . . . . . . . . . . . . . . . . . 3
	3. Protocol Data Units . . . . . . . . . . . . . . . . . . . . . 5		3. Protocol Data Units . . . . . . . . . . . . . . . . . . . . . 5
	4. Protocol Sequence . . . . . . . . . . . . . . . . . . . . . . 6		4. Protocol Sequence . . . . . . . . . . . . . . . . . . . . . . 6
	5. Protocol Transport . . . . . . . . . . . . . . . . . . . . . 6		5. Protocol Transport . . . . . . . . . . . . . . . . . . . . . 6
	6. Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . 7		6. Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . 7
	7. Incremental Updates Support . . . . . . . . . . . . . . . . . 7		7. Incremental Updates Support . . . . . . . . . . . . . . . . . 7
	8. Session ID Support . . . . . . . . . . . . . . . . . . . . . 8		8. Session ID Support . . . . . . . . . . . . . . . . . . . . . 8
	9. Incremental Session Startup Support . . . . . . . . . . . . . 8		9. Incremental Session Startup Support . . . . . . . . . . . . . 8
	10. Interoperable Implementations . . . . . . . . . . . . . . . . 9		10. Interoperable Implementations . . . . . . . . . . . . . . . . 8
	10.1. Cisco Implementation . . . . . . . . . . . . . . . . . . 9		10.1. Cisco Implementation . . . . . . . . . . . . . . . . . . 8
	10.2. Juniper Implementation . . . . . . . . . . . . . . . . . 9		10.2. Juniper Implementation . . . . . . . . . . . . . . . . . 9
	10.3. rpki.net Implementation . . . . . . . . . . . . . . . . 9		10.3. rpki.net Implementation . . . . . . . . . . . . . . . . 9
	10.4. RIPE NCC Implementation . . . . . . . . . . . . . . . . 9		10.4. RIPE NCC Implementation . . . . . . . . . . . . . . . . 9
	10.5. RTRlib Implementation . . . . . . . . . . . . . . . . . 9		10.5. RTRlib Implementation . . . . . . . . . . . . . . . . . 9
	10.6. BBN RPSTIR Implementation . . . . . . . . . . . . . . . 9		10.6. BBN RPSTIR Implementation . . . . . . . . . . . . . . . 9
	11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
	12. Security considerations . . . . . . . . . . . . . . . . . . . 10		12. Security considerations . . . . . . . . . . . . . . . . . . . 10
	13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10		13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 10
	14. Normative References . . . . . . . . . . . . . . . . . . . . 10		14. Normative References . . . . . . . . . . . . . . . . . . . . 10
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
	skipping to change at page 3, line 25		skipping to change at page 3, line 25
	2. Implementation Forms		2. Implementation Forms
	Contact and implementation information for person filling out this		Contact and implementation information for person filling out this
	form:		form:
	IOS		IOS
	Name: Keyur Patel		Name: Keyur Patel
	Email: keyupate@cisco.com		Email: keyupate@cisco.com
	Vendor: Cisco Systems, Inc.		Vendor: Cisco Systems, Inc.
	Release: IOS		Release: IOS
			Protocol Role: Client
	XR		XR
	Name: Forhad Ahmed		Name: Forhad Ahmed
	Email:foahmed@cisco.com		Email:foahmed@cisco.com
	Vendor: Cisco Systems, Inc.		Vendor: Cisco Systems, Inc.
	Release: IOS-XR		Release: IOS-XR
			Protocol Role: Client
	JUNOS		JUNOS
	Name: Hannes Gredler		Name: Hannes Gredler
	Email: hannes@juniper.net		Email: hannes@juniper.net
	Vendor: Juniper Networks, Inc.		Vendor: Juniper Networks, Inc.
	Release: JUNOS		Release: JUNOS
			Protocol Role: Client
	rpki.net		rpki.net
	Name: Rob Austein		Name: Rob Austein
	Email: sra@hactrn.net		Email: sra@hactrn.net
	Vendor: rpki.net project		Vendor: rpki.net project
	Release: http://subvert-rpki.hactrn.net/trunk/		Release: http://subvert-rpki.hactrn.net/trunk/
			Protocol Role: Client, Server
	NCC		NCC
	Name: Tim Bruijnzeels		Name: Tim Bruijnzeels
	Email: tim@ripe.net		Email: tim@ripe.net
	Vendor: RIPE NCC		Vendor: RIPE NCC
	Release: RIPE NCC validator-app 2.0.0 https://github.com/RIPE-NCC/		Release: RIPE NCC validator-app 2.0.0 https://github.com/RIPE-NCC/
	rpki-validator		rpki-validator
			Protocol Role: Server
	RTRlib		RTRlib
	Name: Fabian Holler, Matthias Waehlisch		Name: Fabian Holler, Matthias Waehlisch
	Email: waehlisch@ieee.org		Email: waehlisch@ieee.org
	Vendor: HAW Hamburg, FU Berlin, RTRlib project		Vendor: HAW Hamburg, FU Berlin, RTRlib project
	Release: RTRlib 0.2 http://rpki.realmv6.org/		Release: RTRlib 0.2 http://rpki.realmv6.org/
			Protocol Role: Client
	BBN		BBN
	Name: David Mandelberg, Andrew Chi		Name: David Mandelberg, Andrew Chi
	Email: dmandelb@bbn.com		Email: dmandelb@bbn.com
	Vendor: Raytheon/BBN Technologies		Vendor: Raytheon/BBN Technologies
	Release: RPSTIR 0.2 http://sourceforge.net/projects/rpstir/		Release: RPSTIR 0.2 http://sourceforge.net/projects/rpstir/
			Protocol Role: Server
	3. Protocol Data Units		3. Protocol Data Units
	Does the implementation support Protocol Data Units (PDUs) as		Does the implementation support Protocol Data Units (PDUs) as
	described in Section 5 of [RFC6810]?		described in Section 5 of [RFC6810]?
	P0: Serial Notify		P0: Serial Notify
	P1: Serial Query		P1: Serial Query
	skipping to change at page 6, line 4		skipping to change at page 6, line 4
	| Snd.P4 | --- | --- | --- | --- | YES | YES | --- | YES |		| Snd.P4 | --- | --- | --- | --- | YES | YES | --- | YES |
	| Rcv.P6 | YES | YES | YES | YES | --- | --- | YES | --- |		| Rcv.P6 | YES | YES | YES | YES | --- | --- | YES | --- |
	| Snd.P6 | --- | --- | --- | --- | YES | YES | --- | YES |		| Snd.P6 | --- | --- | --- | --- | YES | YES | --- | YES |
	| Rcv.P7 | YES | YES | YES | YES | --- | --- | YES | --- |		| Rcv.P7 | YES | YES | YES | YES | --- | --- | YES | --- |
	| Snd.P7 | --- | --- | --- | --- | YES | YES | --- | YES |		| Snd.P7 | --- | --- | --- | --- | YES | YES | --- | YES |
	| Rcv.P8 | YES | YES | YES | YES | --- | --- | YES | --- |		| Rcv.P8 | YES | YES | YES | YES | --- | --- | YES | --- |
	| Snd.P8 | --- | --- | --- | --- | YES | YES | --- | YES |		| Snd.P8 | --- | --- | --- | --- | YES | YES | --- | YES |
	| Rcv.P10 | YES | YES | NO~1 | YES | YES | YES | YES | YES |		| Rcv.P10 | YES | YES | NO~1 | YES | YES | YES | YES | YES |
	| Snd.P10 | YES | NO | NO | YES | YES | YES | YES | YES |		| Snd.P10 | YES | NO | NO | YES | YES | YES | YES | YES |
	+---------+------+-----+-------+--------+--------+-----+------+-----+		+---------+------+-----+-------+--------+--------+-----+------+-----+
	1) No, Error PDU gets silently ignored		Note 1: No, Error PDU gets silently ignored.
	4. Protocol Sequence		4. Protocol Sequence
	Does RPKI Router protocol implementation follow the four protocol		Does RPKI Router protocol implementation follow the four protocol
	sequences as outlined in Section 6 of [RFC6810]?		sequences as outlined in Section 6 of [RFC6810]?
	S1: Start or Restart		S1: Start or Restart
	S2: Typical Exchange		S2: Typical Exchange
	S3: Generation of Incremental Updates Sequence		S3: No Incremental Update Available
	S4: Receipt of Incremental Updates Sequence
	S5: Generation of Cache has No data Sequence		S4: Cache Has No Data Available
	+------+------+-----+-------+--------+--------+------+--------+-----+		+-----+-----+-----+-------+--------+--------+------+--------+-------+
	| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |		| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |
	| | | | | .net | .net | | | |		| | | | | .net | .net | | | |
	| | | | | clnt | srvr | | | |		| | | | | clnt | srvr | | | |
	+------+------+-----+-------+--------+--------+------+--------+-----+		+-----+-----+-----+-------+--------+--------+------+--------+-------+
	| S1 | YES | YES | YES | YES | YES | YES | YES | YES |		| S1 | YES | YES | YES | YES | YES | YES | YES | YES |
	| S2 | YES | YES | YES | YES | YES | NO~1 | YES | YES |		| S2 | YES | YES | YES | YES | YES | NO~1 | YES | YES |
	| S3 | --- | --- | --- | --- | YES | NO | --- | YES |		| S3 | YES | YES | YES | YES | YES | YES | YES | YES |
	| S4 | YES | YES | YES | YES | --- | --- | YES | --- |		| S4 | YES | YES | YES | YES | YES | YES | YES | YES~2 |
	| S5 | --- | --- | --- | --- | YES | YES | --- | YES |		+-----+-----+-----+-------+--------+--------+------+--------+-------+
	+------+------+-----+-------+--------+--------+------+--------+-----+
	1) NO, we always respond as described in 6.3 of [RFC6810]		Note 1: Does not implement Serial Query, thus Incremental Update is
			never available, so responds to Serial Query with Cache Reset as
			described in Section 6.3 of [RFC6810]
			Note 2: Sends Cache Reset in response to Serial Query when no data;
			sends Error Report PDU in response to Reset Query when no data.
	5. Protocol Transport		5. Protocol Transport
	Does RPKI Router protocol implementation support different protocol		Does RPKI Router protocol implementation support different protocol
	transport mechanism outlined in Section 7 of [RFC6810]?		transport mechanism outlined in Section 7 of [RFC6810]?
	+---------+-------+------+-------+------+------+-----+--------+-----+		+---------+-------+------+-------+------+------+-----+--------+-----+
	| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |		| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |
	| | | | | .net | .net | | | |		| | | | | .net | .net | | | |
	| | | | | clnt | srvr | | | |		| | | | | clnt | srvr | | | |
	+---------+-------+------+-------+------+------+-----+--------+-----+		+---------+-------+------+-------+------+------+-----+--------+-----+
	| SSH | NO | YES | NO | YES | YES | NO | YES | YES |		| SSH | NO | YES | NO | YES | YES | NO | YES | YES |
	| TLS | NO | NO | NO | NO | NO | NO | NO | NO |		| TLS | NO | NO | NO | NO | NO | NO | NO | NO |
	| TCP | YES | YES | YES | YES | YES | YES | YES | YES |		| TCP | YES | YES | YES | YES | YES | YES | YES | YES |
	| TCP-MD5 | NO | NO | NO | NO | NO | NO | NO | NO |		| TCP-MD5 | NO | NO | NO | NO | NO | NO | NO | NO |
	| TCP-AO | NO | NO | NO | NO | NO | NO | NO | NO |		| TCP-AO | NO | NO | NO | NO | NO | NO | NO | NO |
	skipping to change at page 7, line 14		skipping to change at page 7, line 5
	+---------+-------+------+-------+------+------+-----+--------+-----+		+---------+-------+------+-------+------+------+-----+--------+-----+
	| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |		| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |
	| | | | | .net | .net | | | |		| | | | | .net | .net | | | |
	| | | | | clnt | srvr | | | |		| | | | | clnt | srvr | | | |
	+---------+-------+------+-------+------+------+-----+--------+-----+		+---------+-------+------+-------+------+------+-----+--------+-----+
	| SSH | NO | YES | NO | YES | YES | NO | YES | YES |		| SSH | NO | YES | NO | YES | YES | NO | YES | YES |
	| TLS | NO | NO | NO | NO | NO | NO | NO | NO |		| TLS | NO | NO | NO | NO | NO | NO | NO | NO |
	| TCP | YES | YES | YES | YES | YES | YES | YES | YES |		| TCP | YES | YES | YES | YES | YES | YES | YES | YES |
	| TCP-MD5 | NO | NO | NO | NO | NO | NO | NO | NO |		| TCP-MD5 | NO | NO | NO | NO | NO | NO | NO | NO |
	| TCP-AO | NO | NO | NO | NO | NO | NO | NO | NO |		| TCP-AO | NO | NO | NO | NO | NO | NO | NO | NO |
			| IPsec | NO | NO | NO | NO | NO | NO | NO | NO |
	+---------+-------+------+-------+------+------+-----+--------+-----+		+---------+-------+------+-------+------+------+-----+--------+-----+
	6. Error Codes		6. Error Codes
	Does RPKI Router protocol implementation support different protocol		Does RPKI Router protocol implementation support different protocol
	error codes outlined in Section 10 of [RFC6810]?		error codes outlined in Section 10 of [RFC6810]?
	+-------+-------+------+-------+------+------+-------+--------+-----+		+-------+-------+------+-------+------+------+-------+--------+-----+
	| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |		| | IOS | XR | JUNOS | rpki | rpki | NCC | RTRlib | BBN |
	| | | | | .net | .net | | | |		| | | | | .net | .net | | | |
	skipping to change at page 7, line 44		skipping to change at page 7, line 36
	| Rcv.4 | YES | YES | NO | YES | YES | YES | YES | YES |		| Rcv.4 | YES | YES | NO | YES | YES | YES | YES | YES |
	| Snd.4 | YES | YES | NO | YES | YES | YES | YES | YES |		| Snd.4 | YES | YES | NO | YES | YES | YES | YES | YES |
	| Rcv.5 | YES | YES | NO | YES | YES | YES | YES | YES |		| Rcv.5 | YES | YES | NO | YES | YES | YES | YES | YES |
	| Snd.5 | YES | YES | NO | YES | YES | YES | YES | YES |		| Snd.5 | YES | YES | NO | YES | YES | YES | YES | YES |
	| Rcv.6 | --- | --- | --- | --- | YES | YES~1 | --- | YES |		| Rcv.6 | --- | --- | --- | --- | YES | YES~1 | --- | YES |
	| Snd.6 | YES | YES | NO | NO | --- | --- | YES | --- |		| Snd.6 | YES | YES | NO | NO | --- | --- | YES | --- |
	| Rcv.7 | --- | --- | --- | --- | YES | YES~1 | --- | YES |		| Rcv.7 | --- | --- | --- | --- | YES | YES~1 | --- | YES |
	| Snd.7 | YES | YES | NO | NO | --- | --- | YES | --- |		| Snd.7 | YES | YES | NO | NO | --- | --- | YES | --- |
	+-------+-------+------+-------+------+------+-------+--------+-----+		+-------+-------+------+-------+------+------+-------+--------+-----+
	1) YES, but... fatal, so connection is dropped, but cache does not		Note 1: YES, but... fatal, so connection is dropped, but cache does
	conclude it's inconsistent.		not conclude it's inconsistent.
	7. Incremental Updates Support		7. Incremental Updates Support
	Does the RPKI Router implementation support Incremental Updates as		Does the RPKI Router implementation support Incremental Updates as
	defined in Section 4 of [RFC6810]?		defined in Section 4 of [RFC6810]?
	+-----+------+-------+------------+------------+-----+--------+-----+		+-----+------+-------+------------+------------+-----+--------+-----+
	| IOS | XR | JUNOS | rpki.net | rpki.net | NCC | RTRlib | BBN |		| IOS | XR | JUNOS | rpki.net | rpki.net | NCC | RTRlib | BBN |
	| | | | clnt | srvr | | | |		| | | | clnt | srvr | | | |
	+-----+------+-------+------------+------------+-----+--------+-----+		+-----+------+-------+------------+------------+-----+--------+-----+
	| NO | NO | YES | YES | YES | NO | YES | YES |		| NO | NO | YES | YES | YES | NO | YES | YES |
	+-----+------+-------+------------+------------+-----+--------+-----+		+-----+------+-------+------------+------------+-----+--------+-----+
	8. Session ID Support		8. Session ID Support
	Session ID is used to indicate that the cache server may have		Session ID is used to indicate that the cache server may have
	skipping to change at page 8, line 29		skipping to change at page 8, line 26
	Does RPKI Router protocol implementation support Session ID		Does RPKI Router protocol implementation support Session ID
	procedures outlined in Section 5.1 of [RFC6810]?		procedures outlined in Section 5.1 of [RFC6810]?
	+-----+-----+-------+------------+------------+------+--------+-----+		+-----+-----+-------+------------+------------+------+--------+-----+
	| IOS | XR | JUNOS | rpki.net | rpki.net | NCC | RTRlib | BBN |		| IOS | XR | JUNOS | rpki.net | rpki.net | NCC | RTRlib | BBN |
	| | | | clnt | srvr | | | |		| | | | clnt | srvr | | | |
	+-----+-----+-------+------------+------------+------+--------+-----+		+-----+-----+-------+------------+------------+------+--------+-----+
	| YES | YES | YES | YES | YES | NO~1 | YES | YES |		| YES | YES | YES | YES | YES | NO~1 | YES | YES |
	+-----+-----+-------+------------+------------+------+--------+-----+		+-----+-----+-------+------------+------------+------+--------+-----+
	1) NO, using random, but will FIX		Note 1: NO, using random, but will FIX
	9. Incremental Session Startup Support		9. Incremental Session Startup Support
	Does the RPKI Router protocol implementation support Incremental		Does the RPKI Router protocol implementation support Incremental
	session startups with Serial Number and Session ID as defined in		session startups with Serial Number and Session ID as defined in
	section 5.3 of [RFC6810]?		section 5.3 of [RFC6810]?
	+------+-----+-------+------------+------------+-----+--------+-----+		+------+-----+-------+------------+------------+-----+--------+-----+
	| IOS | XR | JUNOS | rpki.net | rpki.net | NCC | RTRlib | BBN |		| IOS | XR | JUNOS | rpki.net | rpki.net | NCC | RTRlib | BBN |
	| | | | clnt | srvr | | | |		| | | | clnt | srvr | | | |
	skipping to change at page 9, line 22		skipping to change at page 9, line 14
	Cisco: The Cisco IOS and IOS-XR implementation should be		Cisco: The Cisco IOS and IOS-XR implementation should be
	interoperable with other vendor RPKI Router Protocol implementations.		interoperable with other vendor RPKI Router Protocol implementations.
	In particular we have tested our interoperability with rpki.net's		In particular we have tested our interoperability with rpki.net's
	RPKI Router implementation.		RPKI Router implementation.
	10.2. Juniper Implementation		10.2. Juniper Implementation
	Juniper: The Juniper Networks, Inc. JUNOS implementation should be		Juniper: The Juniper Networks, Inc. JUNOS implementation should be
	interoperable with other vendor RPKI Router Protocol implementations.		interoperable with other vendor RPKI Router Protocol implementations.
	In particular we have tested our interoperability with rpki.net's and		In particular we have tested our interoperability with rpki.net's and
	NCCs RPKI Router Cache implementation.		NCC's RPKI Router Cache implementation.
	10.3. rpki.net Implementation		10.3. rpki.net Implementation
	rpki.net: The rpki.net implementation should operate with other rpki-		rpki.net: The rpki.net implementation should operate with other rpki-
	rtr implementations. In particular, we have tested our rpki-rtr		rtr implementations. In particular, we have tested our rpki-rtr
	server's interoperability with Cisco IOS, Cisco IOS-XR, and Juniper.		server's interoperability with Cisco IOS, Cisco IOS-XR, and Juniper.
	10.4. RIPE NCC Implementation		10.4. RIPE NCC Implementation
	RIPE NCC: The RIPE NCC validator has been tested by us with other		RIPE NCC: The RIPE NCC validator has been tested by us with other
	skipping to change at page 9, line 51		skipping to change at page 9, line 43
	rpki.net and RIPE NCC Validator.		rpki.net and RIPE NCC Validator.
	10.6. BBN RPSTIR Implementation		10.6. BBN RPSTIR Implementation
	BBN RPSTIR: We have not yet tested with any other implementations.		BBN RPSTIR: We have not yet tested with any other implementations.
	11. IANA Considerations		11. IANA Considerations
	This document makes no request of IANA.		This document makes no request of IANA.
	Note to RFC Editor: this section may be removed on publication as an		Note to RFC Editor: The IANA has requested that this section remain
	RFC.		in the document upon publication as an RFC. This note to the RFC
			Editor, however, may be removed.
	12. Security considerations		12. Security considerations
	No new security issues are introduced to the RPKI Router protocol		No new security issues are introduced to the RPKI Router protocol
	defined in [RFC6810].		defined in [RFC6810].
	13. Acknowledgements		13. Acknowledgements
	The authors would like to thank Andrew Chi, David Mandelberg, Fabian		The authors would like to thank Andrew Chi, David Mandelberg, Fabian
	Holler, Forhad Ahmed, and Tim Bruijnzeels for their contributions to		Holler, Forhad Ahmed, and Tim Bruijnzeels for their contributions to
End of changes. 27 change blocks.
	25 lines changed or deleted		37 lines changed or added
This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/