draft-ietf-sidr-slurm-05.txt   draft-ietf-sidr-slurm-06.txt 
SIDR D. Ma SIDR D. Ma
Internet-Draft ZDNS Internet-Draft ZDNS
Intended status: Standards Track D. Mandelberg Intended status: Standards Track D. Mandelberg
Expires: August 9, 2018 Unaffiliated Expires: August 10, 2018 Unaffiliated
T. Bruijnzeels T. Bruijnzeels
RIPE NCC RIPE NCC
February 5, 2018 February 6, 2018
Simplified Local internet nUmber Resource Management with the RPKI Simplified Local internet nUmber Resource Management with the RPKI
draft-ietf-sidr-slurm-05 draft-ietf-sidr-slurm-06
Abstract Abstract
The Resource Public Key Infrastructure (RPKI) is a global The Resource Public Key Infrastructure (RPKI) is a global
authorization infrastructure that allows the holder of Internet authorization infrastructure that allows the holder of Internet
Number Resources (INRs) to make verifiable statements about those Number Resources (INRs) to make verifiable statements about those
resources. Network operators, e.g., Internet Service Providers resources. Network operators, e.g., Internet Service Providers
(ISPs), can use the RPKI to validate BGP route origination (ISPs), can use the RPKI to validate BGP route origination
assertions. In the future, ISPs also will be able to use the RPKI to assertions. In the future, ISPs also will be able to use the RPKI to
validate the path of a BGP route. However, ISPs may want to validate the path of a BGP route. However, ISPs may want to
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 August 9, 2018. This Internet-Draft will expire on August 10, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://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
skipping to change at page 4, line 37 skipping to change at page 4, line 37
| SLURM +---> SLURM +---> rpki-rtr +---> BGP Speakers| | SLURM +---> SLURM +---> rpki-rtr +---> BGP Speakers|
| Filters | | Assertions | | | | | | Filters | | Assertions | | | | |
+--------------+ +------------+ +----------+ +-------------+ +--------------+ +------------+ +----------+ +-------------+
Figure 1: SLURM's Position in the Relying Party Stack Figure 1: SLURM's Position in the Relying Party Stack
3. SLURM File and Mechanisms 3. SLURM File and Mechanisms
3.1. Use of JSON 3.1. Use of JSON
This document describes responses in the JSON [RFC7159]format. JSON This document describes responses in the JSON [RFC8259]format. JSON
members that are not defined here MUST NOT be used in SLURM Files. members that are not defined here MUST NOT be used in SLURM Files.
Relying Parties MUST consider any deviations from the specification Relying Parties MUST consider any deviations from the specification
an error. Future additions to the specifications in this document an error. Future additions to the specifications in this document
MUST use an incremented value for the "slurmVersion" member. MUST use an incremented value for the "slurmVersion" member.
3.2. SLURM File Overview 3.2. SLURM File Overview
A SLURM file consists of: A SLURM file consists of:
o A SLURM Version indication that MUST be 1 o A SLURM Version indication that MUST be 1
skipping to change at page 15, line 33 skipping to change at page 15, line 33
[RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and [RFC6598] Weil, J., Kuarsingh, V., Donley, C., Liljenstolpe, C., and
M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address M. Azinger, "IANA-Reserved IPv4 Prefix for Shared Address
Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April Space", BCP 153, RFC 6598, DOI 10.17487/RFC6598, April
2012, <https://www.rfc-editor.org/info/rfc6598>. 2012, <https://www.rfc-editor.org/info/rfc6598>.
[RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for [RFC6996] Mitchell, J., "Autonomous System (AS) Reservation for
Private Use", BCP 6, RFC 6996, DOI 10.17487/RFC6996, July Private Use", BCP 6, RFC 6996, DOI 10.17487/RFC6996, July
2013, <https://www.rfc-editor.org/info/rfc6996>. 2013, <https://www.rfc-editor.org/info/rfc6996>.
[RFC8211] Kent, S. and D. Ma, "Adverse Actions by a Certification
Authority (CA) or Repository Manager in the Resource
Public Key Infrastructure (RPKI)", RFC 8211,
DOI 10.17487/RFC8211, September 2017,
<https://www.rfc-editor.org/info/rfc8211>.
8.2. Normative References 8.2. Normative References
[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, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data
Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006, Encodings", RFC 4648, DOI 10.17487/RFC4648, October 2006,
<https://www.rfc-editor.org/info/rfc4648>. <https://www.rfc-editor.org/info/rfc4648>.
skipping to change at page 16, line 10 skipping to change at page 16, line 20
[RFC6810] Bush, R. and R. Austein, "The Resource Public Key [RFC6810] Bush, R. and R. Austein, "The Resource Public Key
Infrastructure (RPKI) to Router Protocol", RFC 6810, Infrastructure (RPKI) to Router Protocol", RFC 6810,
DOI 10.17487/RFC6810, January 2013, DOI 10.17487/RFC6810, January 2013,
<https://www.rfc-editor.org/info/rfc6810>. <https://www.rfc-editor.org/info/rfc6810>.
[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, Austein, "BGP Prefix Origin Validation", RFC 6811,
DOI 10.17487/RFC6811, January 2013, DOI 10.17487/RFC6811, January 2013,
<https://www.rfc-editor.org/info/rfc6811>. <https://www.rfc-editor.org/info/rfc6811>.
[RFC7159] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Interchange Format", RFC 7159, DOI 10.17487/RFC7159, March
2014, <https://www.rfc-editor.org/info/rfc7159>.
[RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol [RFC8205] Lepinski, M., Ed. and K. Sriram, Ed., "BGPsec Protocol
Specification", RFC 8205, DOI 10.17487/RFC8205, September Specification", RFC 8205, DOI 10.17487/RFC8205, September
2017, <https://www.rfc-editor.org/info/rfc8205>. 2017, <https://www.rfc-editor.org/info/rfc8205>.
[RFC8208] Turner, S. and O. Borchert, "BGPsec Algorithms, Key [RFC8208] Turner, S. and O. Borchert, "BGPsec Algorithms, Key
Formats, and Signature Formats", RFC 8208, Formats, and Signature Formats", RFC 8208,
DOI 10.17487/RFC8208, September 2017, DOI 10.17487/RFC8208, September 2017,
<https://www.rfc-editor.org/info/rfc8208>. <https://www.rfc-editor.org/info/rfc8208>.
[RFC8209] Reynolds, M., Turner, S., and S. Kent, "A Profile for [RFC8209] Reynolds, M., Turner, S., and S. Kent, "A Profile for
BGPsec Router Certificates, Certificate Revocation Lists, BGPsec Router Certificates, Certificate Revocation Lists,
and Certification Requests", RFC 8209, and Certification Requests", RFC 8209,
DOI 10.17487/RFC8209, September 2017, DOI 10.17487/RFC8209, September 2017,
<https://www.rfc-editor.org/info/rfc8209>. <https://www.rfc-editor.org/info/rfc8209>.
[RFC8210] Bush, R. and R. Austein, "The Resource Public Key [RFC8210] Bush, R. and R. Austein, "The Resource Public Key
Infrastructure (RPKI) to Router Protocol, Version 1", Infrastructure (RPKI) to Router Protocol, Version 1",
RFC 8210, DOI 10.17487/RFC8210, September 2017, RFC 8210, DOI 10.17487/RFC8210, September 2017,
<https://www.rfc-editor.org/info/rfc8210>. <https://www.rfc-editor.org/info/rfc8210>.
[RFC8211] Kent, S. and D. Ma, "Adverse Actions by a Certification [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data
Authority (CA) or Repository Manager in the Resource Interchange Format", STD 90, RFC 8259,
Public Key Infrastructure (RPKI)", RFC 8211, DOI 10.17487/RFC8259, December 2017,
DOI 10.17487/RFC8211, September 2017, <https://www.rfc-editor.org/info/rfc8259>.
<https://www.rfc-editor.org/info/rfc8211>.
Authors' Addresses Authors' Addresses
Di Ma Di Ma
ZDNS ZDNS
4 South 4th St. Zhongguancun 4 South 4th St. Zhongguancun
Haidian, Beijing 100190 Haidian, Beijing 100190
China China
Email: madi@zdns.cn Email: madi@zdns.cn
David Mandelberg David Mandelberg
Unaffiliated Unaffiliated
Email: david@mandelberg.org Email: david@mandelberg.org
URI: https://david.mandelberg.org URI: https://david.mandelberg.org
Tim Bruijnzeels Tim Bruijnzeels
RIPE NCC RIPE NCC
Stationsplein 11 Stationsplein 11
Amsterdam 1012 AB Amsterdam 1012 AB
 End of changes. 10 change blocks. 
15 lines changed or deleted 16 lines changed or added

This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/