Document: draft-earnshaw-tv-anytime-crid-01.txt Reviewer: Spencer Dawkins Date: 31 augusti 2004 For Informational RFC, I am using this criteria from the Telechat agenda: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" I'm not entirely sure this scheme actually fits into an area of "Internet engineering" - it describes resources that may or may not be accessed over the Internet, and the resource's "location" may or may not be resolved via DNS. The specification is readable, but describes a meta-scheme (since CRIDs may resolve into groups of CRIDs), so it's pretty loose. As one example - please understand that URL registrations are NOT my area (or anything LIKE my area) - I'm wondering if Character encoding considerations: TV-Anytime does not specify the character encoding scheme to be adopted by each implementation is suffient? If the purpose of this specification is to say "IANA, please register scheme CRID and point to these specifications from TV-Anytime, and when CRID authorities have to point to each other's CRIDs, we'll fight this out ourselves", it meets that purpose :-) Spencer