BCP 190, RFC 8820 on URI Design and Ownership

rfc-editor@rfc-editor.org Tue, 30 June 2020 21:58 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 []) by ietfa.amsl.com (Postfix) with ESMTP id BD7EC3A089C for <ietf-announce@ietfa.amsl.com>; Tue, 30 Jun 2020 14:58:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EwZWHyiDouLK for <ietf-announce@ietfa.amsl.com>; Tue, 30 Jun 2020 14:58:53 -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 65C5E3A0895 for <ietf-announce@ietf.org>; Tue, 30 Jun 2020 14:58:53 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3A8F7F40754; Tue, 30 Jun 2020 14:58:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?QkNQIDE5MCwgUkZDIDg4MjAgb24gVVJJIERlc2lnbiBhbmQgT3duZXJzaGlw?=
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
Content-type: text/plain; charset=UTF-8
Message-Id: <20200630215834.3A8F7F40754@rfc-editor.org>
Date: Tue, 30 Jun 2020 14:58:34 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/mUPQ9uSBPj4UnLG1kKk12p76Rtc>
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: Tue, 30 Jun 2020 21:58:55 -0000

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

        BCP 190        
        RFC 8820

        Title:      URI Design and Ownership 
        Author:     M. Nottingham
        Status:     Best Current Practice
        Stream:     IETF
        Date:       June 2020
        Mailbox:    mnot@mnot.net
        Pages:      8
        Obsoletes:  RFC 7320
        Updates:    RFC 3986
        See Also:   BCP 190

        I-D Tag:    draft-nottingham-rfc7320bis-03.txt

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

        DOI:        10.17487/RFC8820

Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
extensible naming system wherein each scheme's specification may
further restrict the syntax and semantics of identifiers using that
scheme."  In other words, the structure of a URI is defined by its
scheme. While it is common for schemes to further delegate their
substructure to the URI's owner, publishing independent standards
that mandate particular forms of substructure in URIs is often

This document provides guidance on the specification of URI
substructure in standards.

This document obsoletes RFC 7320 and updates RFC 3986.

BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. 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