[sidr] RFC 8416 on Simplified Local Internet Number Resource Management with the RPKI (SLURM)

rfc-editor@rfc-editor.org Wed, 08 August 2018 00:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 49448130DC4; Tue, 7 Aug 2018 17:33:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Un9pmi32s1Kv; Tue, 7 Aug 2018 17:33:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CA3B130DC0; Tue, 7 Aug 2018 17:33:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9C4BBB81879; Tue, 7 Aug 2018 17:32:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sidr@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20180808003256.9C4BBB81879@rfc-editor.org>
Date: Tue, 7 Aug 2018 17:32:56 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/0TJdSS8cJRg9NlvCbEOn5r16m4Q>
Subject: [sidr] =?utf-8?q?RFC_8416_on_Simplified_Local_Internet_Number_Re?= =?utf-8?q?source_Management_with_the_RPKI_=28SLURM=29?=
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidr/>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Aug 2018 00:33:02 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8416

        Title:      Simplified Local Internet Number Resource 
                    Management with the RPKI (SLURM) 
        Author:     D. Ma, 
                    D. Mandelberg,
                    T. Bruijnzeels
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2018
        Mailbox:    madi@zdns.cn, 
        Pages:      17
        Characters: 34613
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidr-slurm-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8416

        DOI:        10.17487/RFC8416

The Resource Public Key Infrastructure (RPKI) is a global
authorization infrastructure that allows the holder of Internet
Number Resources (INRs) to make verifiable statements about those
resources.  Network operators, e.g., Internet Service Providers
(ISPs), can use the RPKI to validate BGP route origin assertions.
ISPs can also use the RPKI to validate the path of a BGP route.
However, ISPs may want to establish a local view of exceptions to the
RPKI data in the form of local filters and additions.  The mechanisms
described in this document provide a simple way to enable INR holders
to establish a local, customized view of the RPKI, overriding global
RPKI repository data as needed.

This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC