idnits 2.17.1 draft-dolan-urn-isan-01.txt: -(152): Line appears to be too long, but this could be caused by non-ascii characters in UTF-8 encoding 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 282. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 256. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 263. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 272. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 288), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 35. ** 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 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: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 5 longer pages, the longest (page 3) being 64 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (April 25, 2005) is 6913 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ISO15706' -- Obsolete informational reference (is this intentional?): RFC 3406 (Obsoleted by RFC 8141) Summary: 7 errors (**), 0 flaws (~~), 5 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 M. Dolan 2 Internet Draft TBT 3 Expires: October 2005 April 25, 2005 5 ISAN URN Definition 6 draft-dolan-urn-isan-01.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 and any of which I become aware will be disclosed, in accordance with 13 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 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html 31 This Internet-Draft will expire on October 25, 2005. 33 Copyright Notice 35 Copyright (C) The Internet Society (2005). All Rights Reserved. 37 Abstract 39 The International Standard Audiovisual Number (ISAN) is a standard 40 numbering system for the unique and international identification of 41 audiovisual works. This document is the definition of the formal 42 Uniform Resource Name (URN) Namespace Identifier (NID) for ISAN. 44 Conventions used in this document 46 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 47 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 48 document are to be interpreted as described in RFC-2119. 50 Table of Contents 52 1. URN Namespace Definition Template..............................2 53 1.1. Namespace ID:.............................................2 54 1.2. Registration Information:.................................2 55 1.3. Declared registrant of the namespace:.....................2 56 1.4. Declaration of structure:.................................3 57 The identifier structure is as follows:...........................3 58 1.5. Relevant ancillary documentation:.........................3 59 1.6. Identifier uniqueness considerations:.....................3 60 1.7. Identifier persistence considerations:....................3 61 1.8. Process of identifier assignment:.........................3 62 1.9. Process for identifier resolution:........................3 63 1.10. Rules for Lexical Equivalence:...........................3 64 1.11. Conformance with URN Syntax:.............................3 65 1.12. Validation mechanism:....................................4 66 1.13. Scope: Global............................................4 67 2. Formal Syntax..................................................4 68 3. Security Considerations........................................4 69 4. Namespace Considerations.......................................4 70 5. Community Considerations.......................................4 71 6. IANA Considerations............................................5 72 7. References.....................................................5 73 7.1. Normative References......................................5 74 7.2. Informative References....................................5 75 Author's Addresses................................................5 76 Intellectual Property Statement...................................5 77 Disclaimer of Validity............................................6 78 Copyright Statement...............................................6 79 Acknowledgment....................................................6 81 1. URN Namespace Definition Template 83 The following template is provided in accordance with [RFC3406]. 85 1.1. Namespace ID: 87 ISAN 89 1.2. Registration Information: 91 Version: 1 93 Date: 2004 11 22 95 1.3. Declared registrant of the namespace: 97 Name: ISAN International Agency 98 Address: 26 rue de St Jean, CH-1203 Geneva � Switzerland 100 Contact: Mr. Patrick Attallah, Managing Director 102 1.4. Declaration of structure: 104 The identifier structure is as follows: 106 URN:ISAN: 108 Where ISAN-NSS is conformant to URN syntax requirements defined in 109 [RFC2141] and is further constrained by [ISO15706] and in this 110 document. There are two forms, one with the version extension and 111 one without. The formal BNF is defined in section 2 below. Examples 112 of the two forms are: 114 URN:ISAN:0123-1230-3210-2310-1 116 URN:ISAN:1881-66C7-3420-6541-9-9F3A-0245-U 118 1.5. Relevant ancillary documentation: 120 ISAN, its syntax, uses and its processes are defined in [ISO15706]. 122 1.6. Identifier uniqueness considerations: 124 Uniqueness is guaranteed by the ISAN International Agency that issues 125 the numbers. Numbers are not re-assigned. 127 1.7. Identifier persistence considerations: 129 Persistence is guaranteed by ISO Registration Authority processes and 130 contracts with the ISAN International Agency. 132 1.8. Process of identifier assignment: 134 The details of the assignment process are defined from time to time 135 by the ISAN International Agency. However, in general, any approved 136 entity can request an ISAN number by providing the required metadata 137 information and paying the registration fee. The ISAN International 138 Agency may delegate to regional or market-based Registration Agencies 139 for portions of the registration process. 141 1.9. Process for identifier resolution: 143 ISAN numbers are resolved by a direct or indirect lookup with the 144 ISAN International Agency. At this writing, a non-commercial, manual 145 system is available online at http://www.isan.org. The resolution 146 procedures may be modified from time to time by the ISAN 147 International Agency. 149 1.10. Rules for Lexical Equivalence: 151 The ISAN-NSS is unique by the nature of the ISAN International 152 Agency�s number management. The ISAN-NSS is case-insensitive. Upper 153 and lower case characters are treated as identical. 155 1.11. Conformance with URN Syntax: 157 No special considerations. The syntax is fully conformant with 158 [RFC2141]. 160 1.12. Validation mechanism: 162 The check digits provide syntax integrity. Lookup is via online and 163 offline services provided by the ISAN International Agency. 165 1.13. Scope: Global. 167 2. Formal Syntax 169 The following syntax specification uses the augmented Backus-Naur 170 Form (BNF) and elements defined in the URN Syntax [RFC2141]. This 171 syntax here is derived from the syntax definition in [ISO15706], 172 constrained to prohibit the space character as a separator. 174 ::= [version] 176 ::= 3*( "-") 178 ::= "-" 180 ::= 2*("-" ) "-" 182 ::= 4*() 184 ::= | | 186 Note that , , and are defined in 187 [RFC2141]. 189 3. Security Considerations 191 This document only defines the syntax and resolution authority for 192 the ISAN numbers. Details of the resolution process and the security 193 of the assignment and resolution system processes are defined 194 external to this document by the ISAN International Agency and thus 195 outside the scope of this document. 197 4. Namespace Considerations 198 ISAN is an external numbering system managed by an external agency 199 established by ISO. While URN namespaces may exist for which any 200 generic numbering system can be encoded, there is currently no direct 201 encoding for ISAN. An example of such a namespace is the MPEG-21 202 system. 204 ISAN numbers are reserved for use in identifying audiovisual works 205 for which there is a moving visual component, or components related 206 to such a work (e.g. subtitling track). 208 5. Community Considerations 210 The primary registrants for ISAN numbers are the producers and 211 studios of audiovisual works (movies and television shows). While the 212 system is not constrained to "major" works (any bona fide entity can 213 register any work), the primary benefits of its use come from works 214 that are widely distributed. The users of the ISAN system range from 215 the studios themselves to film and video archives and libraries, 216 rights administrators, program guide services, and audience 217 measurement services. Its potential for use in the Internet community 218 is as an identifier for streaming media. 220 6. IANA Considerations 222 This document defines a URN NID registration that is to be entered 223 into the IANA registry of URN NIDs. It specifically requests the NID, 224 "ISAN". 226 7. References 228 7.1. Normative References 230 [RFC2141] IETF RFC 2141, URN Syntax, May 1997 232 [ISO15706] ISO 15706, Information and documentation - International 233 Standard Audiovisual Number (ISAN) 235 7.2. Informative References 237 [RFC3406] IETF RFC 3406, Uniform Resource Names (URN) Namespace 238 Definition Mechanisms, October 2002. 240 Author's Addresses 242 Michael Dolan 243 TBT 244 PO Box 190, Del Mar, CA 92014 USA 246 Email: md.1@tbt.com 248 Intellectual Property Statement 249 The IETF takes no position regarding the validity or scope of any 250 Intellectual Property Rights or other rights that might be claimed to 251 pertain to the implementation or use of the technology described in 252 this document or the extent to which any license under such rights 253 might or might not be available; nor does it represent that it has 254 made any independent effort to identify any such rights. Information 255 on the procedures with respect to rights in RFC documents can be 256 found in BCP 78 and BCP 79. 258 Copies of IPR disclosures made to the IETF Secretariat and any 259 assurances of licenses to be made available, or the result of an 260 attempt made to obtain a general license or permission for the use of 261 such proprietary rights by implementers or users of this 262 specification can be obtained from the IETF on-line IPR repository at 263 http://www.ietf.org/ipr. 265 The IETF invites any interested party to bring to its attention any 266 copyrights, patents or patent applications, or other proprietary 267 rights that may cover technology that may be required to implement 268 this standard. Please address the information to the IETF at 269 ietf-ipr@ietf.org. By submitting this Internet-Draft, I certify that 270 any applicable patent or other IPR claims of which I am aware have 271 been disclosed, and any of which I become aware will be disclosed, in 272 accordance with RFC 3668. 274 Disclaimer of Validity 276 This document and the information contained herein are provided on an 277 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 278 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 279 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 280 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 281 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 282 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 284 Copyright Statement 286 Copyright (C) The Internet Society (2005). This document is subject 287 to the rights, licenses and restrictions contained in BCP 78, and 288 except as set forth therein, the authors retain all their rights. 290 Acknowledgment 292 Funding for the RFC Editor function is currently provided by the 293 Internet Society.