RFC 4078 on The TV-Anytime Content Reference Identifier (CRID)

rfc-editor@rfc-editor.org Mon, 23 May 2005 22:32 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLTQ-0007VY-7u; Mon, 23 May 2005 18:32:36 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DaLTN-0007Uv-Oc for ietf-announce@megatron.ietf.org; Mon, 23 May 2005 18:32:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05721 for <ietf-announce@ietf.org>; Mon, 23 May 2005 18:32:30 -0400 (EDT)
From: rfc-editor@rfc-editor.org
Received: from council.ci.sugar-land.tx.us ([] helo=mail.ci.sugar-land.tx.us) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DaLlR-0006Pr-0G for ietf-announce@ietf.org; Mon, 23 May 2005 18:51:13 -0400
Received: from svrpd14 ([]) by mail.ci.sugar-land.tx.us; Mon, 23 May 2005 17:31:42 -0500
MIME-Version: 1.0
Date: Mon, 23 May 2005 17:31:41 -0500
X-Priority: 3 (Normal)
To: ietf-announce@ietf.org, rfc-editor@rfc-editor.org
X-Mailer: GWAVA Archive Mailer
Content-Type: multipart/mixed; boundary="----=_NextPart_39c_4b00_36224683.50148e0c_.MIX"
Message-ID: <CHILKAT-MID-592f75f9-c2fd-475d-8aa9-4e943df48da2@svrpd14>
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 72dbfff5c6b8ad2b1b727c13be042129
Subject: RFC 4078 on The TV-Anytime Content Reference Identifier (CRID)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        RFC 4078

        Title:      The TV-Anytime Content Reference Identifier (CRID)
        Author(s):  N. Earnshaw, S. Aoki, A. Ashley, W. Kameyama
        Status:     Informational
        Date:       May 2005
        Mailbox:    nigel.earnshaw@rd.bbc.co.uk,
                    shig@center.jfn.co.jp, aashley@ndsuk.com,
        Pages:      10
        Characters: 21433
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-earnshaw-tv-anytime-crid-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4078.txt

The Uniform Resource Locator (URL) scheme "CRID:" has been devised to
allow references to current or future scheduled publications of
broadcast media content over television distribution platforms and
the Internet.

The initial intended application is as an embedded link within
scheduled programme description metadata that can be used by the home
user or agent to associate a programme selection with the
corresponding programme location information for subsequent automatic

This document reproduces the TV-Anytime CRID definition found in the
TV-Anytime content referencing specification, and is published as an
RFC for ease of access and registration with the Internet Assigned
Numbers Authority (IANA).

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
IETF-Announce mailing list