BCP 183, RFC 6963 on A Uniform Resource Name (URN) Namespace for Examples
rfc-editor@rfc-editor.org Fri, 24 May 2013 19: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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA72611E80C5 for <ietf-announce@ietfa.amsl.com>; Fri, 24 May 2013 12:58:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level:
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0GxM60m0H087 for <ietf-announce@ietfa.amsl.com>; Fri, 24 May 2013 12:58:35 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 45BDC21F9416 for <ietf-announce@ietf.org>; Fri, 24 May 2013 12:58:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BD9C762102; Fri, 24 May 2013 12:57:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 183, RFC 6963 on A Uniform Resource Name (URN) Namespace for Examples
From: rfc-editor@rfc-editor.org
Message-Id: <20130524195753.BD9C762102@rfc-editor.org>
Date: Fri, 24 May 2013 12:57:53 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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, 24 May 2013 19:58:35 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 183
RFC 6963
Title: A Uniform Resource Name (URN)
Namespace for Examples
Author: P. Saint-Andre
Status: Best Current Practice
Stream: IETF
Date: May 2013
Mailbox: psaintan@cisco.com
Pages: 7
Characters: 11749
See Also: BCP 183
I-D Tag: draft-saintandre-urn-example-05.txt
URL: http://www.rfc-editor.org/rfc/rfc6963.txt
This document defines a Uniform Resource Name (URN) namespace
identifier enabling the generation of URNs that are appropriate for
use in documentation and in URN-related testing and experimentation.
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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
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