RFC 7972 on Entertainment Identifier Registry (EIDR) URN Namespace Definition

rfc-editor@rfc-editor.org Fri, 09 September 2016 05:10 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 361BF12B114 for <ietf-announce@ietfa.amsl.com>; Thu, 8 Sep 2016 22:10:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.13
X-Spam-Level:
X-Spam-Status: No, score=-104.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.508, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 1GLs1nC4rdeS for <ietf-announce@ietfa.amsl.com>; Thu, 8 Sep 2016 22:10:25 -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 831C712B0FC for <ietf-announce@ietf.org>; Thu, 8 Sep 2016 22:10:25 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 735A9B80CD6; Thu, 8 Sep 2016 22:10:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7972 on Entertainment Identifier Registry (EIDR) URN Namespace Definition
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160909051025.735A9B80CD6@rfc-editor.org>
Date: Thu, 08 Sep 2016 22:10:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-l17FJb6DgGSjiJB3X98TXKnh10>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: <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, 09 Sep 2016 05:10:27 -0000

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

        
        RFC 7972

        Title:      Entertainment Identifier Registry (EIDR) URN 
                    Namespace Definition 
        Author:     P. Lemieux
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    pal@sandflow.com
        Pages:      10
        Characters: 17603
        Obsoletes:  RFC 7302

        I-D Tag:    draft-pal-eidr-urn-2016-03.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7972

Entertainment Identifier Registry (EIDR) Identifiers are used for the
globally unique identification of motion picture and television
content.  This document defines the formal Uniform Resource Name
(URN) Namespace Identifier (NID) for EIDR Identifiers.

This document obsoletes RFC 7302.



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