RFC 8254 on Uniform Resource Name (URN) Namespace Registration Transition

rfc-editor@rfc-editor.org Fri, 20 October 2017 23:46 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 4DBE4132A1A; Fri, 20 Oct 2017 16:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id FSPqyFDV2gvu; Fri, 20 Oct 2017 16:46:55 -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 AE4C5132193; Fri, 20 Oct 2017 16:46:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EEC75B81050; Fri, 20 Oct 2017 16:46:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8254 on Uniform Resource Name (URN) Namespace Registration Transition
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, urn@ietf.org
Message-Id: <20171020234630.EEC75B81050@rfc-editor.org>
Date: Fri, 20 Oct 2017 16:46:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/JXgvOxvi-VMsU3J3E5a7-aoKlBM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 20 Oct 2017 23:46:57 -0000

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

        RFC 8254

        Title:      Uniform Resource Name (URN) Namespace 
                    Registration Transition 
        Author:     J. Klensin, 
                    J. Hakala
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2017
        Mailbox:    john-ietf@jck.com, 
        Pages:      9
        Characters: 18618
        Obsoletes:  RFC 3044, RFC 3187

        I-D Tag:    draft-ietf-urnbis-ns-reg-transition-08.txt

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

        DOI:        10.17487/RFC8254

The original registration procedure for formal Uniform Resource Name
(URN) namespaces required IETF Consensus.  That requirement
discouraged some registrations and increased the risk for problems
that could occur as a result.  The requirements have now been changed
by RFC 8141, which adopts a different model, focusing on encouraging
registration and publication of information for all appropriate
namespaces.  This document clarifies the status of relevant older
RFCs and confirms and documents advice to IANA about selected
existing registrations.  This document also obsoletes RFCs 3044 and
3187 and moves them to Historic status.  These RFCs describe the ISSN
and ISBN namespaces, which are now outdated because the descriptions
reside in registration templates.

This document is a product of the Uniform Resource Names, Revised 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