< draft-madi-sidrops-rush-05.txt		draft-madi-sidrops-rush-06.txt >
	SIDROPS D. Ma		SIDROPS D. Ma
	Internet-Draft ZDNS		Internet-Draft ZDNS
	Intended status: Standards Track H. Yan		Intended status: Standards Track H. Yan
	Expires: 11 May 2022 CNCERT		Expires: 10 November 2022 CNCERT
	M. Aelmans		M. Aelmans
	Juniper Networks		Juniper Networks
	7 November 2021		9 May 2022
	RPKI validated cache Update in SLURM over HTTPs (RUSH)		RPKI validated cache Update in SLURM over HTTPs (RUSH)
	draft-madi-sidrops-rush-05		draft-madi-sidrops-rush-06
	Abstract		Abstract
	This document defines a method for transferring RPKI validated cache		This document defines a method for transferring RPKI validated cache
	update information in JSON object format over HTTPs.		update information in JSON object format over HTTPs.
	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.
	skipping to change at page 1, line 34 ¶		skipping to change at page 1, line 34 ¶
	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 https://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 11 May 2022.		This Internet-Draft will expire on 10 November 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Simplified BSD License text		extracted from this document must include Revised BSD License text as
	as described in Section 4.e of the Trust Legal Provisions and are		described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Simplified BSD License.		provided without warranty as described in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
	3. RUSH Usecase . . . . . . . . . . . . . . . . . . . . . . . . 3		3. RUSH Usecase . . . . . . . . . . . . . . . . . . . . . . . . 3
	4. RUSH Operations . . . . . . . . . . . . . . . . . . . . . . . 3		4. RUSH Operations . . . . . . . . . . . . . . . . . . . . . . . 3
	4.1. Use of SLURM . . . . . . . . . . . . . . . . . . . . . . 3		4.1. Use of SLURM . . . . . . . . . . . . . . . . . . . . . . 3
	4.2. Use of HTTPs as Transport . . . . . . . . . . . . . . . . 4		4.2. Use of HTTPs as Transport . . . . . . . . . . . . . . . . 4
	4.3. RUSH Example . . . . . . . . . . . . . . . . . . . . . . 4		4.3. RUSH Example . . . . . . . . . . . . . . . . . . . . . . 4
	skipping to change at page 6, line 9 ¶		skipping to change at page 6, line 9 ¶
	Encoding considerations: This is a JSON object.		Encoding considerations: This is a JSON object.
	Security considerations: N/A		Security considerations: N/A
	Interoperability considerations: [RFC8416]		Interoperability considerations: [RFC8416]
	Published specification:		Published specification:
	Applications that use this media type:		Applications that use this media type:
	Systems that want to exchange RPKI cache data update information in		Systems that want to exchange RPKI cache data update information in
	SLURM file format [RFC8416] over HTTP.		SLURM file format [RFC8416] over HTTPs.
	Person&email address to contact for further information: Di Ma		Person&email address to contact for further information: Di Ma
	<madi@zdns.cn>		<madi@zdns.cn>
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: N/A		Restrictions on usage: N/A
	Author: Di Ma <madi@zdns.cn>		Author: Di Ma <madi@zdns.cn>
End of changes. 7 change blocks.
	9 lines changed or deleted		9 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/