Protocol Action: 'A Profile for Route Origin Authorizations (ROAs)' to Proposed Standard (draft-ietf-sidrops-rfc6482bis-09.txt)

The IESG <iesg-secretary@ietf.org> Thu, 14 December 2023 20:56 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'A Profile for Route Origin Authorizations (ROAs)' to Proposed Standard (draft-ietf-sidrops-rfc6482bis-09.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, draft-ietf-sidrops-rfc6482bis@ietf.org, morrowc@ops-netman.net, rfc-editor@rfc-editor.org, sidrops-chairs@ietf.org, sidrops@ietf.org, warren@kumari.net
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <170258738876.33548.349327225689412183@ietfa.amsl.com>
Date: Thu, 14 Dec 2023 12:56:28 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/vleSRtBcGSPGnJBOsImGFFETK9o>

The IESG has approved the following document:
- 'A Profile for Route Origin Authorizations (ROAs)'
  (draft-ietf-sidrops-rfc6482bis-09.txt) as Proposed Standard

This document is the product of the SIDR Operations Working Group.

The IESG contact persons are Warren Kumari and Robert Wilton.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rfc6482bis/




Technical Summary

   This document defines a standard profile for Route Origin
   Authorizations (ROAs).  A ROA is a digitally signed object that
   provides a means of verifying that an IP address block holder has
   authorized an Autonomous System (AS) to originate routes to one or
   more prefixes within the address block.  This document obsoletes RFC
   6482.

Working Group Summary

   It took a while to get to consensus, but it seems solid now. 

Document Quality

   While it is not really a protocol document, there are two
   linked implementations of the sorting in the document.

   The document does contain an example ROA which contains a
   non-RFC3849-compliant IP address. This seems OK to me.

Personnel

   Chris Morrow is DS. 
   Warren "Ace" Kumari is RAD!!!!

Protocol Action: 'A Profile for Route Origin Auth… The IESG