idnits 2.17.1 draft-kameyama-tv-anytime-urn-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3667, Section 5.1 on line 13. -- Found old boilerplate from RFC 3978, Section 5.5 on line 186. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 192), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 36. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement -- however, there's a paragraph with a matching beginning. Boilerplate error? ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document seems to lack an RFC 3979 Section 5, para. 1 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 2 IPR Disclosure Acknowledgement. ** The document seems to lack an RFC 3979 Section 5, para. 3 IPR Disclosure Invitation. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The "Author's Address" (or "Authors' Addresses") section title is misspelled. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 6, 2005) is 7048 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 13 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group W. Kameyama 2 Internet-Draft GITS, Waseda University 3 Expires: July 5, 2005 January 6, 2005 5 A URN Namespace for the TV-Anytime Forum 6 draft-kameyama-tv-anytime-urn-02.txt 8 Status of this Memo 10 By submitting this Internet-Draft, I certify that any applicable 11 patent or other IPR claims of which I am aware have been disclosed, 12 or will be disclosed, and any of which I become aware will be 13 disclosed, in accordance with RFC 3668. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/1id-abstracts.html 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html 32 This Internet-Draft expires on July 5, 2005. 34 Copyright Notice 36 Copyright (C) The Internet Society (2005). All Rights Reserved. 38 Abstract 40 This document describes a Uniform Resource Name (URN) namespace that 41 is engineered by the TV-Anytime Forum for naming persistent resources 42 published by the TV-Anytime Forum including the TV-Anytime Forum 43 Standards, XML (Extensible Markup Language) Document Type 44 Definitions, XML Schemas, Namespaces, and other documents. 46 1. Introduction 48 The TV-Anytime Forum produces many kinds of documents: 49 specifications, working documents, schemas, etc. that currently being 50 considered for adoption by many standardization bodies such as ETSI 51 (European Telecommunication Standardization Institute), DVB (Digital 52 Video Broadcasting), ARIB (Association of Radio Industries and 53 Businesses) and ATSC (Advance Television Systems Committee). 55 The TV-Anytime Forum wishes to provide global, distributed, 56 persistent, location-independent names for these resources. 58 2. Specification Template 60 Namespace ID: 62 "tva" requested. 64 Registration information: 66 Registration Version Number: 1 67 Registration Date: 2005-1-6 69 Declared registrant of the namespace: 71 Name: Wataru KAMEYAMA 72 Title: Vice Chairman and Secretary, The TV-Anytime Forum 73 Affiliation: Graduate School of Global Information 74 and Telecommunication Studies, Waseda University 75 Address: 1011 Okuboyama, Nishi-tomida, Honjo-shi, Saitama 76 367-0035, JAPAN 77 Phone: +81 495 24 6052 78 Email: wataru@waseda.jp 80 Declaration of structure: 82 The Namespace Specific String (NSS) of all URNs assigned by the 83 TV-Anytime Forum will have the following hierarchical structure: 85 urn:tva:{category}:{string} 87 where the "category" is a US-ASCII string that conforms to URN 88 syntax requirements ([RFC2141]), and "{string}" is a string that 89 confirms to URN syntax requirements ([RFC2141]). 91 Relevant ancillary documentation: 93 The TV-Anytime Forum specifications have been publicly available 94 at all stages during their development from 95 "ftp://tva:tva@ftp.bbc.co.uk/Specifications/". The final 96 specifications are also available as formal ETSI (European 97 Telecommunication Standardization Institute) technical 98 specification documents, ETSI TS 102 822 series. 100 Identifier uniqueness considerations: 102 The TV-Anytime Forum shall establish unique identifiers as 103 appropriate. 105 Uniqueness is guaranteed as long as the assigned "{category}" is 106 never reassigned for another categories. The TV-Anytime Forum is 107 responsible for this. 109 Identifier persistence considerations: 111 The TV-Anytime Forum is committed to maintaining the accessibility 112 and persistence of all resources that are officially assigned URNs 113 by the organization. Persistence of identifiers is dependent upon 114 suitable delegation at the level of "category"s, and persistence 115 of category assignment. 117 Process of identifier assignment: 119 All the assignments of identifiers are fully controlled and 120 managed by the TV-Anytime Forum. 122 Process of identifier resolution: 124 The namespace is not listed with an RDS; this is not relevant. 126 Rules for Lexical Equivalence: 128 The "{category}" is case-insensitive. Thus, the portion of the 129 URN: 131 urn:tva:{category}: 133 is case-insensitive for matches. The remainder of the identifier 134 shall be considered case-sensitive, and so URNs are only lexically 135 equivalent if they are also lexically identical in the remaining 136 {string} field. 138 Conformance with URN Syntax: 140 No special considerations. 142 Validation mechanism: 144 Validation shall be done by a syntax grammar corresponding to each 145 "{category}". 147 Scope: 149 Global. 151 3. Examples 153 The following examples are not guaranteed to be real. They are 154 provided for pedagogical reasons only. 156 urn:tva:metadata:2002 157 urn:tva:metadata:cs:IntentionCS:2002 158 urn:tva:metadata:cs:ActionTypeCS:2002 159 urn:tva:rmp:tvax 161 4. Security Considerations 163 There are no additional security considerations other than those 164 normally associated with the use and resolution of URNs in general. 166 References 168 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997 170 Author Address 172 Wataru KAMEYAMA 173 GITS, Waseda University 174 1011 Okuboyama, Nishi-tomida, Honjo-shi, Saitama, 367-0035, JAPAN 175 Phone: +81 495 24 6052 176 Email: wataru@waseda.jp 178 Disclaimer of Validity 180 This document and the information contained herein are provided on an 181 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 182 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 183 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 184 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 185 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 186 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 188 Copyright Statement 190 Copyright (C) The Internet Society (2005). This document is subject 191 to the rights, licenses and restrictions contained in BCP 78, and 192 except as set forth therein, the authors retain all their rights.