[rfc-dist] RFC 8458 on Using National Bibliography Numbers as Uniform Resource Names

rfc-editor@rfc-editor.org Sat, 13 October 2018 00:48 UTC

Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F19130EBA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 12 Oct 2018 17:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 5LvFyp5_Sj_S for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 12 Oct 2018 17:48:48 -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 99E33130E99 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 12 Oct 2018 17:48:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7E92DB81797; Fri, 12 Oct 2018 17:48:26 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id E1EF9B81797; Fri, 12 Oct 2018 17:48:24 -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
Message-Id: <20181013004824.E1EF9B81797@rfc-editor.org>
Date: Fri, 12 Oct 2018 17:48:24 -0700
Subject: [rfc-dist] RFC 8458 on Using National Bibliography Numbers as Uniform Resource Names
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8458

        Title:      Using National Bibliography Numbers as 
                    Uniform Resource Names 
        Author:     J. Hakala
        Status:     Informational
        Stream:     IETF
        Date:       October 2018
        Mailbox:    juha.hakala@helsinki.fi
        Pages:      18
        Characters: 41283
        Obsoletes:  RFC 3188

        I-D Tag:    draft-hakala-urn-nbn-rfc3188bis-02.txt

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

        DOI:        10.17487/RFC8458

National Bibliography Numbers (NBNs) are used by national libraries
and other organizations in order to identify resources in their
collections.  NBNs are usually applied to resources that are not
catered for by established (standard) identifier systems such as
International Standard Book Number (ISBN).

A Uniform Resource Name (URN) namespace for NBNs was established in
2001 in RFC 3188.  Since then, a number of European national
libraries have implemented URN:NBN-based systems.

This document replaces RFC 3188 and defines how NBNs can be supported
within the updated URN framework.  A revised namespace registration
(version 4) compliant to RFC 8141 is included.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org