RFC 8515 on URN Namespace for ETSI Documents

rfc-editor@rfc-editor.org Wed, 27 February 2019 04:55 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 47A21130E2E for <ietf-announce@ietfa.amsl.com>; Tue, 26 Feb 2019 20:55:30 -0800 (PST)
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 vnrjNbUQAMyD for <ietf-announce@ietfa.amsl.com>; Tue, 26 Feb 2019 20:55:28 -0800 (PST)
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 7315A130E2B for <ietf-announce@ietf.org>; Tue, 26 Feb 2019 20:55:28 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F033CB80E09; Tue, 26 Feb 2019 20:55:08 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8515 on URN Namespace for ETSI Documents
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: <20190227045508.F033CB80E09@rfc-editor.org>
Date: Tue, 26 Feb 2019 20:55:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/KYGSlhxGH1gUbxYkZs9TywtVXcE>
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: Wed, 27 Feb 2019 04:55:30 -0000

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

        
        RFC 8515

        Title:      URN Namespace for ETSI Documents 
        Author:     M. Jethanandani,
                    M.A. Reina Ortega
        Status:     Informational
        Stream:     IETF
        Date:       February 2019
        Mailbox:    mjethanandani@gmail.com, 
                    miguelangel.reinaortega@etsi.org
        Pages:      7
        Characters: 10779
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-mahesh-etsi-urn-05.txt

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

        DOI:        10.17487/RFC8515

This document describes the Namespace Identifier (NID) "etsi" for
Uniform Resource Names (URNs) used to identify resources published by
the European Telecommunications Standards Institute
(http://etsi.org).  ETSI specifies and manages resources that utilize
this URN identification model.  Management activities for these and
other resource types are handled by the manager of the ETSI Protocol
Naming and Numbering Service (PNNS).


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