Skip to main content

A Uniform Resource Name (URN) Namespace for the Open IPTV Forum (OIPF)

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 6893.
Authors Paul Higgs , Paul Szucs
Last updated 2015-10-14 (Latest revision 2012-08-13)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Informational
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 6893 (Informational)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Barry Leiba
Send notices to (None)
IESG                                                           P. Higgs
                                                               P. Szucs
Internet Draft                                     Open IPTV Forum e.V.
Intended status: Informational                          August 13, 2012
Expires: February 2013

      A Uniform Resource Name (URN) Namespace for the Open IPTV Forum

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   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-

   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

   The list of Internet-Draft Shadow Directories can be accessed at

   This Internet-Draft will expire on February 13, 2013.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal Provisions
   Relating to IETF Documents ( in 
   effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Higgs, et al.         Expires February 13, 2013                [Page 1]
Internet-Draft                 OIPF URN                     August 2012


   This document describes a Uniform Resource Name (URN) namespace for
   the Open IPTV Forum (OIPF) for naming persistent resources defined
   within OIPF specifications. Example resources include technical
   documents and specifications, eXtensible Markup Language (XML)
   Schemas, classification schemes, XML Document Type Definitions
   (DTDs), namespaces, style sheets, media assets, and other types of
   resources produced or managed by the OIPF.

Table of Contents

   1. Introduction...................................................2
   2. URN Specification for the OIPF Namespace Identifier (NID)......3
   3. Examples.......................................................5
   4. Namespace Considerations.......................................6
   5. Community Considerations.......................................7
   6. Security Considerations........................................7
   7. IANA Considerations............................................7
   8. References.....................................................7
      8.1. Normative References......................................7
      8.2. Informative References....................................7
   9. Acknowledgments................................................8

1. Introduction

   The Open IPTV Forum (OIPF) is a pan-industry initiative with the
   purpose of producing end-to-end specifications for IPTV that will
   take the next generation of IPTV into the mass market. The Forum,
   which is fully open to participation from the communications,
   entertainment and other relevant industries, will focus on the
   development of specifications that will help streamline and
   accelerate deployments of IPTV technologies, and maximize the
   benefits of IPTV for consumers, network operators, content providers,
   service providers, consumer electronics manufacturers and home and
   network infrastructure providers.

   The main objective of the Open IPTV Forum is to produce end-to-end
   specifications for IPTV including:

   o  Architecture and interfaces

   o  Network and terminal functionality

   o  Interactive and personalized services

   o  Technology choices for all major functionalities

   o  A common UNI (User-Network Interface) for the Open Internet and
      Managed Networks

   o  Certification of equipment including end user devices and service
      provider offerings

   The end-to-end specifications support:

   o  A variety of IPTV and Internet multimedia services

   o  Managed networks and the Open Internet

   o  Integration with communication services

   o  Convergence of IPTV and multimedia services across different
      access technologies

   o  Easy integration of 3rd party content offerings

   o  Authentication and content protection

   o  Various devices in the home network

   The OIPF is basing its end-to-end IPTV specifications on relevant
   standards produced by other bodies, and collaborating with them to
   encourage convergence where appropriate, and address any shortcomings
   or gaps.

   In the creation of the end-to-end IPTV specification, some new
   resources need to be defined.

   The OIPF would like to assign unique, permanent, location-independent
   names based on URNs for some resources it produces or manages. These
   URNs will be constructed according to the URN syntax defined in

   This namespace specification is for a formal namespace to be
   registered according to the procedures set forth in [RFC3406].

2. URN Specification for the OIPF Namespace Identifier (NID)

   This section provides the information required to register a formal
   namespace according to the registration procedure defined in
   [RFC3406]. The URNs conform to the syntax defined in [RFC2141].

Higgs, et al.         Expires February 13, 2013                [Page 3]
Internet-Draft                 OIPF URN                     August 2012

   Namespace ID:


   Registration Information:

      Version: 1

      Date: 2012-08-13

   Declared registrant of the namespace:

      Name:          Dr. Nilo Mitra

      Title:         President

      Affiliation:   Open IPTV Forum

      Address:       Open IPTV Forum e.V. Secretariat,
                     650 Route des Lucioles,
                     06921 Sophia Antipolis Cedex, France.

      Phone:         +33 492 94 43 83


   Declaration of structure:

      URNs assigned by the OIPF will have the following structure based
      on the organizational structure of the resources specified in the
      OIPF IPTV Solution specifications:


      where the syntax of "<NSS>" is specified in Section 2.2 of the URN
      Syntax requirements ([RFC2141]).

      The individual URNs will be assigned by the OIPF through the
      process of development of OIPF specifications.

   Relevant ancillary documentation:


Higgs, et al.         Expires February 13, 2013                [Page 4]
Internet-Draft                 OIPF URN                     August 2012

   Identifier uniqueness considerations:

      The OIPF will establish unique identifiers as appropriate and will
      ensure that an assigned string is never reassigned.

   Identifier persistence considerations:

      The OIPF is committed to maintaining the accessibility and
      persistence of all resources that are officially assigned URNs by
      the organization. The registration tables and information will be
      published and maintained by the OIPF on its web site.

   Process of identifier assignment:

      The assignment of identifiers is fully controlled and managed by
      the OIPF.

   Process of identifier resolution:

      Not applicable; the "oipf" namespace is not listed with a
      Resolution Discovery System.

   Rules for Lexical Equivalence:

      The "<NSS>" is case-insensitive.

   Conformance with URN Syntax:

      No special considerations.

   Validation mechanism:

      None specified. URN assignment will be managed completely and
      published by the OIPF.



3. Examples

   The following examples of schemas and classification schemes are
   taken from the current OIPF Release 1 IPTV Solution specification:



Higgs, et al.         Expires February 13, 2013                [Page 5]
Internet-Draft                 OIPF URN                     August 2012




4. Namespace Considerations

   A unique formal namespace is required by the OIPF in order to specify
   how the various existing standards can be linked in order to create a
   true end-to-end ecosystem for standards-based IPTV deployments, and
   to provide the necessary system-wide resources.

   URN assignment procedures:

      The individual URNs shall be assigned through the process of
      development of OIPF specifications by the Open IPTV Forum e.v
      (OIPF). The latest information about OIPF defined specifications
      can always be found at the owner's website at

   URN resolution/delegation:

     The resolution and delegation shall be determined through the
     process of development of specifications by the Open IPTV Forum.

     Since the implementations envisaged cover a wide range of devices
     with quite different access methods and capabilities, no single
     resolution or delegation mechanism can be referenced in this

   Type of resources to be identified:

     Types of resources to be identified include XML schema definition
     files, classification schemes and identification systems defined
     and published by OIPF. These resources being identified constitute
     a metadata system to describe digital multimedia broadcast services
     or content conveyed as part of such services.

     The latest OIPF defined specifications can always be found at

Higgs, et al.         Expires February 13, 2013                [Page 6]
Internet-Draft                 OIPF URN                     August 2012

5. Community Considerations

   URNs defined by the OIPF will be used by implementers of IPTV
   systems, services, products, and applications based on the OIPF IPTV
   Solution specification. They are an essential component of the open
   IPTV ecosystem that is being facilitated by the OIPF.

6. Security Considerations

   There are no additional security considerations other than those
   normally associated with the use and resolution of URNs in general,
   which are described in [RFC1737], [RFC2141], and [RFC3406].

   This document registers a namespace for URNs.  OIPF may assign
   special meaning to certain of the characters of the Namespace
   Specific String in its specifications.  Any security consideration
   resulting from such assignment is outside the scope of this document.

7. IANA Considerations

   This document defines a URN NID registration of "oipf". IANA is
   requested to include it in the URN Namespaces registry.

8. References

8.1. Normative References

   [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for
             Uniform Resource Names", RFC 1737, December 1994.

   [RFC2141] Moats, R., "URN Syntax", RFC 2124, May 1997.

   [RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom,
             "Uniform Resource Names (URN) Namespace Definition
             Mechanisms", October 2002.

8.2. Informative References

   The following specifications are available freely at:

   [OIPF1]  Open IPTV Forum, "Release 1 Specification, Volume 1 -
             Overview", V1.1, October 2009.

Higgs, et al.         Expires February 13, 2013                [Page 7]
Internet-Draft                 OIPF URN                     August 2012

   [OIPF2]  Open IPTV Forum, "Release 1 Specification, Volume 2 - Media
             Formats", V1.1, October 2009.

   [OIPF3]  Open IPTV Forum, "Release 1 Specification, Volume 3 -
             Content Metadata", V1.1, October 2009.

   [OIPF4]  Open IPTV Forum, "Release 1 Specification, Volume 4 -
             Protocols", V1.1, October 2009.

   [OIPF5]  Open IPTV Forum, "Release 1 Specification, Volume 5 -
             Declarative Application Environment", V1.1, October 2009.

   [OIPF6]  Open IPTV Forum, "Release 1 Specification, Volume 6 -
             Procedural Application Environment", V1.1, October 2009.

   [OIPF7]  Open IPTV Forum, "Release 1 Specification, Volume 7 -
             Authentication, Content Protection and Service Protection",
             V1.1, October 2009.

9. Acknowledgments

   This document was prepared using

Higgs, et al.         Expires February 13, 2013                [Page 8]
Internet-Draft                 OIPF URN                     August 2012

Authors' Address

   Paul Higgs
   Chair, OIPF IOT Working Group
   c/o Ericsson Inc, 6 Concourse Parkway, suite 3000,
   Atlanta, GA 30328, USA

   Phone: +1-650-580-1731

   Paul Szucs
   Board Member, OIPF,
   c/o Sony Europe, Hedelfinger Str. 61,
   D-70327 Stuttgart, Germany

   Phone: +49-711-5858-583

Higgs, et al.         Expires February 13, 2013                [Page 9]