[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 RFC 4246

                                                               M. Dolan
Internet Draft                                                      TBT
Expires: October 2005                                    April 25, 2005



                     ISAN URN Definition
                 draft-dolan-urn-isan-01.txt


Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
        http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
        http://www.ietf.org/shadow.html

   This Internet-Draft will expire on October 25, 2005.

Copyright Notice

      Copyright (C) The Internet Society (2005).  All Rights Reserved.

Abstract

   The International Standard Audiovisual Number (ISAN) is a standard
   numbering system for the unique and international identification of
   audiovisual works. This document is the definition of the formal
   Uniform Resource Name (URN) Namespace Identifier (NID) for ISAN.

Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC-2119.










Dolan                  Expires October 25, 2005                [Page 1]

Internet-Draft           ISAN URN Definition                 April 2005




Table of Contents


   1. URN Namespace Definition Template..............................2
      1.1. Namespace ID:.............................................2
      1.2. Registration Information:.................................2
      1.3. Declared registrant of the namespace:.....................2
      1.4. Declaration of structure:.................................3
   The identifier structure is as follows:...........................3
      1.5. Relevant ancillary documentation:.........................3
      1.6. Identifier uniqueness considerations:.....................3
      1.7. Identifier persistence considerations:....................3
      1.8. Process of identifier assignment:.........................3
      1.9. Process for identifier resolution:........................3
      1.10. Rules for Lexical Equivalence:...........................3
      1.11. Conformance with URN Syntax:.............................3
      1.12. Validation mechanism:....................................4
      1.13. Scope: Global............................................4
   2. Formal Syntax..................................................4
   3. Security Considerations........................................4
   4. Namespace Considerations.......................................4
   5. Community Considerations.......................................4
   6. IANA Considerations............................................5
   7. References.....................................................5
      7.1. Normative References......................................5
      7.2. Informative References....................................5
   Author's Addresses................................................5
   Intellectual Property Statement...................................5
   Disclaimer of Validity............................................6
   Copyright Statement...............................................6
   Acknowledgment....................................................6

1. URN Namespace Definition Template

   The following template is provided in accordance with [RFC3406].

1.1. Namespace ID:

   ISAN

1.2. Registration Information:

   Version: 1

   Date: 2004 11 22

1.3. Declared registrant of the namespace:

   Name:    ISAN International Agency
   Address: 26 rue de St Jean, CH-1203 Geneva û Switzerland

   Contact: Mr. Patrick Attallah, Managing Director





Dolan                  Expires October 25, 2005                [Page 2]

Internet-Draft           ISAN URN Definition                 April 2005


1.4. Declaration of structure:

   The identifier structure is as follows:

      URN:ISAN:<ISAN-NSS>

   Where ISAN-NSS is conformant to URN syntax requirements defined in
   [RFC2141] and is further constrained by [ISO15706] and in this
   document.  There are two forms, one with the version extension and
   one without.  The formal BNF is defined in section 2 below.  Examples
   of the two forms are:

      URN:ISAN:0123-1230-3210-2310-1

      URN:ISAN:1881-66C7-3420-6541-9-9F3A-0245-U

1.5. Relevant ancillary documentation:

   ISAN, its syntax, uses and its processes are defined in [ISO15706].

1.6. Identifier uniqueness considerations:

   Uniqueness is guaranteed by the ISAN International Agency that issues
   the numbers.  Numbers are not re-assigned.

1.7. Identifier persistence considerations:

   Persistence is guaranteed by ISO Registration Authority processes and
   contracts with the ISAN International Agency.

1.8. Process of identifier assignment:

   The details of the assignment process are defined from time to time
   by the ISAN International Agency.  However, in general, any approved
   entity can request an ISAN number by providing the required metadata
   information and paying the registration fee. The ISAN International
   Agency may delegate to regional or market-based Registration Agencies
   for portions of the registration process.

1.9. Process for identifier resolution:

   ISAN numbers are resolved by a direct or indirect lookup with the
   ISAN International Agency.  At this writing, a non-commercial, manual
   system is available online at http://www.isan.org.  The resolution
   procedures may be modified from time to time by the ISAN
   International Agency.

1.10. Rules for Lexical Equivalence:

   The ISAN-NSS is unique by the nature of the ISAN International
   AgencyÆs number management.  The ISAN-NSS is case-insensitive.  Upper
   and lower case characters are treated as identical.

1.11. Conformance with URN Syntax:

   No special considerations. The syntax is fully conformant with
   [RFC2141].



Dolan                  Expires October 25, 2005                [Page 3]

Internet-Draft           ISAN URN Definition                 April 2005


1.12. Validation mechanism:

   The check digits provide syntax integrity. Lookup is via online and
   offline services provided by the ISAN International Agency.

1.13. Scope: Global.

2. Formal Syntax

   The following syntax specification uses the augmented Backus-Naur
   Form (BNF) and elements defined in the URN Syntax [RFC2141]. This
   syntax here is derived from the syntax definition in [ISO15706],
   constrained to prohibit the space character as a separator.

      <ISAN-NSS>     ::= <root> <episode> [version]

      <root>         ::= 3*(<hexnum> "-")

      <episode>      ::= <hexnum> "-" <check>

      <version>      ::= 2*("-" <hexnum>) "-" <check>

      <hexnum>       ::= 4*(<hex>)

      <check>        ::= <upper> | <lower> | <number>

   Note that <hex>, <upper>, <lower> and <number> are defined in
   [RFC2141].

3. Security Considerations

   This document only defines the syntax and resolution authority for
   the ISAN numbers. Details of the resolution process and the security
   of the assignment and resolution system processes are defined
   external to this document by the ISAN International Agency and thus
   outside the scope of this document.

4. Namespace Considerations
   ISAN is an external numbering system managed by an external agency
   established by ISO. While URN namespaces may exist for which any
   generic numbering system can be encoded, there is currently no direct
   encoding for ISAN. An example of such a namespace is the MPEG-21
   system.

   ISAN numbers are reserved for use in identifying audiovisual works
   for which there is a moving visual component, or components related
   to such a work (e.g. subtitling track).

5. Community Considerations

   The primary registrants for ISAN numbers are the producers and
   studios of audiovisual works (movies and television shows). While the
   system is not constrained to "major" works (any bona fide entity can
   register any work), the primary benefits of its use come from works
   that are widely distributed. The users of the ISAN system range from
   the studios themselves to film and video archives and libraries,
   rights administrators, program guide services, and audience


Dolan                  Expires October 25, 2005                [Page 4]

Internet-Draft           ISAN URN Definition                 April 2005


   measurement services. Its potential for use in the Internet community
   is as an identifier for streaming media.

6. IANA Considerations

   This document defines a URN NID registration that is to be entered
   into the IANA registry of URN NIDs. It specifically requests the NID,
   "ISAN".

7. References

7.1. Normative References

   [RFC2141] IETF RFC 2141, URN Syntax, May 1997

   [ISO15706] ISO 15706, Information and documentation - International
   Standard Audiovisual Number (ISAN)

7.2. Informative References

   [RFC3406] IETF RFC 3406, Uniform Resource Names (URN) Namespace
   Definition Mechanisms, October 2002.

Author's Addresses

   Michael Dolan
   TBT
   PO Box 190, Del Mar, CA 92014 USA

   Email: md.1@tbt.com

Intellectual Property Statement
   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.  By submitting this Internet-Draft, I certify that
   any applicable patent or other IPR claims of which I am aware have
   been disclosed, and any of which I become aware will be disclosed, in
   accordance with RFC 3668.



Dolan                  Expires October 25, 2005                [Page 5]

Internet-Draft           ISAN URN Definition                 April 2005


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.





















Dolan                  Expires October 25, 2005                [Page 6]


Html markup produced by rfcmarkup 1.108, available from http://tools.ietf.org/tools/rfcmarkup/