RFC 9092 on Finding and Using Geofeed Data

rfc-editor@rfc-editor.org Mon, 26 July 2021 20:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 002DD3A0AEF; Mon, 26 Jul 2021 13:00:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kTJl3-0_Pa_T; Mon, 26 Jul 2021 13:00:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 951C63A0AEB; Mon, 26 Jul 2021 13:00:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 52ADCF406D5; Mon, 26 Jul 2021 13:00:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9092 on Finding and Using Geofeed Data
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, opsawg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210726200023.52ADCF406D5@rfc-editor.org>
Date: Mon, 26 Jul 2021 13:00:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2Q32Ml-sDxivvIfO8Uiimd0vjiY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jul 2021 20:00:46 -0000

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

        
        RFC 9092

        Title:      Finding and Using Geofeed Data 
        Author:     R. Bush,
                    M. Candela,
                    W. Kumari,
                    R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2021
        Mailbox:    randy@psg.com,
                    massimo@ntt.net,
                    warren@kumari.net,
                    housley@vigilsec.com
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-opsawg-finding-geofeeds-17.txt

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

        DOI:        10.17487/RFC9092

This document specifies how to augment the Routing Policy
Specification Language inetnum: class to refer specifically to
geofeed data comma-separated values (CSV) files and describes an
optional scheme that uses the Routing Public Key Infrastructure to
authenticate the geofeed data CSV files.

This document is a product of the Operations and Management Area Working Group 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
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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