RFC 6893

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

📅 published March 2013, from ietf

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

Hiii bestie 🎀 this is RFC 6893, from the Internet Engineering Task Force (IETF), and it's written by P. Higgs and P. Szucs from the Open IPTV Forum e.V. It's Informational (so it's published for info, not as a standards-track spec 🙈), it's dated March 2013, and its ISSN is 2070-1721 ✨. It doesn't obsolete or update any other RFCs, since the header doesn't list any.

Abstract 🌸

Okay so this doc sets up a URN namespace for the Open IPTV Forum (OIPF) 🦋 The point is naming persistent resources that get defined in OIPF specs. Think technical docs, XML schemas, classification schemes, XML DTDs, namespaces, style sheets, media assets, and other stuff the OIPF makes or manages. It's giving organized library energy 📚✨

Status of This Memo 💅

This doc is not an Internet Standards Track spec, it's just here for info purposes 💜

It's still an IETF product, though! It represents the consensus of the IETF community, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG). Not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 5741 if you're curious 🧚

For the current status, errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc6893 🔥

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

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as in effect on the publication date. Please read these carefully, because they spell out your rights and restrictions for this doc 🫶 Any Code Components pulled from this document must include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come without warranty, as described in that same license 🍓

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 ........................................6
6. Security Considerations .........................................7
7. IANA Considerations .............................................7
8. Normative References ............................................7

1. Introduction ✨

The Open IPTV Forum (OIPF) is a pan-industry initiative 👑 Its whole goal is making end-to-end specs for IPTV that take the next generation of IPTV into the mass market. The Forum is fully open to anyone in communications, entertainment, and other relevant industries 🎀 It's focused on specs that help streamline and speed up IPTV deployments, and that maximize the benefits for consumers, network operators, content providers, service providers, consumer electronics makers, and home and network infrastructure providers. Main character energy, honestly 💅

The main objective is producing end-to-end IPTV specs that include:

  • Architecture and interfaces
  • Network and terminal functionality
  • Interactive and personalized services
  • Technology choices for all major functionalities
  • A common UNI (User-Network Interface) for the Open Internet and Managed Networks
  • Certification of equipment, including end user devices and service provider offerings

These end-to-end specs support:

  • A variety of IPTV and Internet multimedia services
  • Managed networks and the Open Internet
  • Integration with communication services
  • Convergence of IPTV and multimedia services across different access technologies
  • Easy integration of third-party content offerings
  • Authentication and content protection
  • Various devices in the home network

The OIPF builds its end-to-end IPTV specs on relevant standards from other bodies 🦋 It's also working with them to encourage convergence where it makes sense, and to address any shortcomings or gaps. Collab era 🫶

When creating the end-to-end IPTV spec, some new resources needed to be defined 🌸

The OIPF wants to give unique, permanent, location-independent names, based on URNs, to some of the resources it makes or manages 💖 These URNs are built using the URN syntax defined in [RFC2141].

This namespace spec is meant to be a formal namespace, registered according to the procedures in [RFC3406] 🧚

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

This section has all the info you need to register a formal namespace under the registration procedure in [RFC3406] 🍓 The URNs follow the syntax in [RFC2141].

Namespace ID: "oipf"

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
Email:         contact@oipf.tv

Declaration of structure:

URNs assigned by the OIPF follow this structure, based on how the resources in the OIPF IPTV Solution specs are organized:

urn:oipf:<NSS>

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

The OIPF assigns the individual URNs as it develops its OIPF specs 💜

Relevant ancillary documentation: None. Nothing extra, just vibes 🙈

Identifier uniqueness considerations: The OIPF will set up unique identifiers as appropriate, and it will make sure an assigned string is never reassigned 🔒

Identifier persistence considerations: The OIPF is committed to keeping every resource that officially gets a URN from the organization accessible and persistent ✨ The registration tables and info will be published and maintained by the OIPF on its website.

Process of identifier assignment: The OIPF fully controls and manages assignment of identifiers 👑

Process of identifier resolution: Not applicable 💀 The "oipf" namespace isn't 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. The OIPF manages URN assignment completely and publishes it 🧚

Scope: Global 🌍

3. Examples 🎀

Here are some examples of schemas and classification schemes, taken from the current OIPF Release 1 IPTV Solution spec:

urn:oipf:device:ig:1

urn:oipf:config:oitf:oitfCapabilities:2009

urn:oipf:iptv:IPTVProfile:2008

urn:oipf:cs:AVMediaFormatCS:2008

urn:oipf:cs:ApplicationTypeCS:2009

4. Namespace Considerations 🦋

A unique formal namespace is required by the OIPF so that various existing standards can be linked up to make 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 developing OIPF specs, by the Open IPTV Forum (OIPF) e.V. 🌸 The latest info on OIPF-defined specs is always at the owner's website:

<http://www.oipf.tv/specifications>

URN resolution/delegation: Resolution and delegation shall be determined through the process of developing specs by the Open IPTV Forum. The implementations envisaged cover a wide range of devices with quite different access methods and capabilities, so no single resolution or delegation mechanism can be referenced in this document 🔥

Types of resources to be identified: These include XML schema definition files, classification schemes, and identification systems defined and published by the OIPF. Together, these resources make up a metadata system for describing digital multimedia broadcast services, or the content carried as part of those services 🧚 The latest OIPF-defined specs are always at:

<http://www.oipf.tv/specifications>

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 spec ✨ They're an essential part of the open IPTV ecosystem the OIPF is helping to build 🌈

6. Security Considerations 🙈

⚠️ Read this one carefully, bestie. There are no additional security considerations beyond the ones that normally come with using and resolving URNs in general. Those are described in [RFC1737], [RFC2141], and [RFC3406].

This document registers a namespace for URNs. The OIPF may give special meaning to certain characters of the Namespace Specific String (NSS) in its specs. Any security considerations from that kind of assignment are outside the scope of this document 💀

7. IANA Considerations 🌸

This document defines a URN NID registration of "oipf". IANA has included it in the "Uniform Resource Names (URN) Namespaces" registry with a value of 47 🎀

8. Normative References 📚

  • [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
  • [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
  • [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.

Authors' Addresses 💜

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
EMail: paul.higgs@ericsson.com


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

Phone: +49-711-5858-583
EMail: paul.szucs@eu.sony.com
📦 where this page comes from