RFC 7528

RFC 7528: A Uniform Resource Name (URN) Namespace for the Hybrid Broadcast Broadband TV (HbbTV) Association 🎀

okay so the title block first 💅 This one is from the IETF (Internet Engineering Task Force) and it was published in April 2015 📅. It's an Informational doc, so it's not a standards-track spec 🧚. The authors are Paul Higgs and Jonathan Piesing, both from the HbbTV Association 🫶. The ISSN is 2070-1721. The title block doesn't list anything this RFC obsoletes or updates, so it's standing alone 🌈

---

Abstract ✨

so this doc describes a Uniform Resource Name (URN) namespace for the Hybrid Broadcast Broadband TV (HbbTV) Association 📺 The whole point is giving persistent names to resources defined in HbbTV specs 🔥 Those resources are things like technical docs and specifications, Extensible Markup Language (XML) Schemas, classification schemes, XML Document Type Definitions (DTDs), namespaces, style sheets, media assets, and other stuff HbbTV makes or manages 💖

Status of This Memo 🌸

this one is giving "informational only" 🎀 It is not an Internet Standards Track specification, it's just published for information purposes.

This document is a product of the Internet Engineering Task Force (IETF) 🦋 It represents the consensus of the IETF community and got public review, then the Internet Engineering Steering Group (IESG) approved it for publication ✨ Not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 5741 for that 🙈

For info on the current status, any errata, and how to give feedback, go to http://www.rfc-editor.org/info/rfc7528.

Copyright Notice 💜

Copyright (c) 2015 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 they were in effect when it was published. Please read those carefully, bestie, because they explain your rights and restrictions for this document 📜 Any Code Components pulled out of this document must include Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come without warranty, as the Simplified BSD License describes 💀

Table of Contents 🗺️

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

---

1. Introduction 🌸

okay so HbbTV (Hybrid Broadcast Broadband TV) is a new industry standard, and it's giving open and business-neutral 📺 It smoothly mashes together TV services delivered over broadcast with services delivered over broadband, and it also opens the door to Internet-only services for people using connected TVs and set-top boxes 🌈 The founding members of the HbbTV consortium, plus a big group of supporters, built the HbbTV specification together to make a global standard for hybrid entertainment services 🔥 Version 1.2.1 of that spec was published by ETSI as ETSI TS 102 796 [HbbTV12] in November 2012 🎀

The HbbTV spec is built on existing standards and web tech, including the Open IPTV Forum (OIPF), the Consumer Electronics Association (CEA), Digital Video Broadcasting (DVB), and the World Wide Web Consortium (W3C) 💖 It gives you the features and functionality you need for feature-rich broadcast and Internet services ✨ Because it uses standard Internet tech, app development is fast 🧚 It sets minimum requirements so devices are simpler to build, while still leaving room for differentiation, which keeps the investment manufacturers need to make compliant devices pretty low 💅 The HbbTV Association is a pan-European initiative that wants to offer an alternative to proprietary tech and give broadcasters an open platform for delivering value-added on-demand services to end consumers 🫶

HbbTV has a huge range of supporters across the broadcaster and consumer electronics industries 🦋

HbbTV wants to assign unique, permanent, location-independent names based on URNs to some of the resources it produces or manages 🔥 These URNs will be built according to the URN syntax defined in [RFC2141] 💜 This namespace spec is for a formal namespace that will be registered following the procedures in [RFC3406] 🌸

2. URN Specification for the HbbTV Namespace Identifier (NID) 🦋

this section has everything you need to register a formal namespace under the procedure in [RFC3406] ✨ The URNs follow the syntax in [RFC2141] 💅

Namespace ID:

• "hbbtv"

Registration Information:

• Version: 1
• Date: 2014-08-07

Declared registrant of the namespace:

• Name: Mr. Peter Macavock
• Title: Administrator
• Affiliation: HbbTV Association
• Address: L'Ancienne-Route 17A, CH-1218 Grand-Saconnex, Switzerland
• Phone: + 41 22 717 27 14
• Email: info@hbbtv.org

Declaration of structure:

HbbTV's URNs will have this structure, based on the organizational structure of the resources in the HbbTV specs 🧚

urn:hbbtv:<NSS>

The syntax of "<NSS>" is specified in Section 2.2 of the URN Syntax requirements [RFC2141] 💖 Individual URNs get assigned by HbbTV through the process of developing the HbbTV specs 🌈

Relevant ancillary documentation:

• None. 🙈

Identifier uniqueness considerations:

HbbTV will set up unique identifiers as appropriate and will make sure an assigned string is never reassigned 🔒

Identifier persistence considerations:

HbbTV 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 HbbTV on its web site 🌸

Process of identifier assignment:

The assignment of identifiers is fully controlled and managed by HbbTV 👑

Process of identifier resolution:

Not applicable. The "hbbtv" 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 HbbTV 🎀

Scope:

Global 🌍

3. Examples 🧚

The following example of schemas and classification schemes comes from the current HbbTV spec [HbbTV12] 🔥

urn:hbbtv:dash:profile:isoff-live:2012

These examples of schemas and classification schemes are under consideration for a future version of the HbbTV spec that's still in development 🌈

urn:hbbtv:sync:timeline:ebu-tt-d

urn:hbbtv:config:oitf:oitfCapabilities:2014-1

4. Namespace Considerations 💖

HbbTV needs a unique formal namespace so it can specify how the various existing standards link up, which creates a true end-to-end ecosystem for standards-based IPTV deployments and provides the system-wide resources it needs ✨

URN assignment procedures:

The individual URNs shall be assigned through the process of developing HbbTV specs by the Hybrid Broadcast Broadband TV Association 🫶 The latest info on HbbTV-defined specs can always be found on the owner's website at

<https://hbbtv.org/pages/about_hbbtv/specification.php>

URN resolution/delegation:

Resolution and delegation shall be determined through the process of developing specs by the HbbTV Association 🦋

Because the implementations envisaged cover a wide range of devices with quite different access methods and capabilities, this document can't reference a single resolution or delegation mechanism 🙈

Type of resources to be identified:

The types of resources to be identified include XML schema definition files, classification schemes, and identification systems that HbbTV defines and publishes 📚 Together, these resources make up a metadata system that describes digital multimedia broadcast services, or content carried as part of those services 📺

The latest HbbTV-defined specs can always be found at

<https://hbbtv.org/pages/about_hbbtv/specification.php>

5. Community Considerations 🫶

URNs defined by HbbTV will be used by implementers building hybrid broadcast/broadband systems, services, products, and apps based on the HbbTV spec 🌸 They're an essential part of the open ecosystem HbbTV is making happen ✨

HbbTV specs are developed through a consensus-based process by member organizations that represent most parts of the digital television ecosystem 💖 You can find the full member list at

<http://hbbtv.org/pages/hbbtv_association/members.php>

6. Security Considerations 💀

⚠️ This section is serious, bestie. Read it all.

There are no 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. HbbTV may give special meaning to certain characters of the Namespace Specific String (NSS) in its specs 😱 Any security consideration that comes from that kind of assignment is outside the scope of this document 🙈

7. IANA Considerations 🧚

This document defines a URN NID registration of "hbbtv" 🎀 IANA has added it to the "Uniform Resource Names (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,
           <http://www.rfc-editor.org/info/rfc1737>.

[RFC2141]  Moats, R., "URN Syntax", RFC 2141, May 1997,
           <http://www.rfc-editor.org/info/rfc2141>.

[RFC3406]  Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
           "Uniform Resource Names (URN) Namespace Definition
           Mechanisms", BCP 66, RFC 3406, October 2002,
           <http://www.rfc-editor.org/info/rfc3406>.

8.2. Informative References

[HbbTV12]  ETSI, "Hybrid Broadcast Broadband TV", ETSI TS 102 796
           v1.2.1, November 2012.

Authors' Addresses 🌷

Paul Higgs
HbbTV Association
c/o Ericsson Inc, 6 Concourse Parkway, suite 400
Atlanta, GA  30328
United States

Phone: +1-650-580-1731
EMail: paul.higgs@ericsson.com


Jonathan Piesing
HbbTV Association
c/o TP Vision Belgium - Innovation Site Europe,
Technologiepark-Zwijnaarde 19,
9052 Gent
Belgium

Phone: +32 484 430 060
EMail: jon.piesing@tpvision.com