RFC 4965

CableLabs - IETF Standardization Collaboration

📅 published September 2007, from ietf

RFC 4965: CableLabs - IETF Standardization Collaboration 🎀

Okay bestie, this one is the official paperwork for how CableLabs and the IETF team up. It was written by J-F. Mule of CableLabs and W. Townsley of Cisco Systems, published in September 2007 in the Network Working Group, and it's Informational, so it's not a standard 💅. The header doesn't list it as obsoleting or updating any other RFC, so it's a clean slate ✨.

Status of This Memo 🌸

This memo gives information to the Internet community. It does not specify an Internet standard of any kind, and distribution is unlimited 🫶.

Abstract 🦋

This document is about the collaboration and liaison relationship between the Internet Engineering Task Force (IETF) and Cable Television Laboratories, Inc. (CableLabs). It's giving partnership energy 💜.

Table of Contents 📋

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.  Basis of Collaboration  . . . . . . . . . . . . . . . . . . . . 3
3.  Document Sharing  . . . . . . . . . . . . . . . . . . . . . . . 3
4.  Participation in the IETF Process . . . . . . . . . . . . . . . 4
5.  Designated Liaison Managers and Responsibilities  . . . . . . . 4
6.  Formal Liaison Statements . . . . . . . . . . . . . . . . . . . 6
7.  Contributions . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
11. Common Work Areas . . . . . . . . . . . . . . . . . . . . . . . 7
12. Informative References  . . . . . . . . . . . . . . . . . . . . 8

1. Introduction ✨

So this doc is basically a set of principles and guidelines that sets up the liaison relationship between Cable Television Laboratories, Inc. and the IETF 🎀. The whole point is to lock in timely development of technical specs that play nicely with existing Internet systems, devices, and protocols, so everything is maximally interoperable 🫶.

Okay, a little CableLabs background, because it's lowkey iconic. CableLabs is a non-profit R&D consortium obsessed with new cable telecom tech, and it helps its cable operator members fold those advances into their business goals 💼. Inside CableLabs, specs are organized into projects like DOCSIS(r), PacketCable(tm), and OpenCable(tm), and the actual technical work happens in focus teams 🛠️. Product vendors, manufacturers, and cable operator members are all invited to join those focus teams 🙌. Every so often, people from the focus teams send CableLabs technical requirements or requirement specs over to the IETF, to get expert reviews, collect comments, and build solutions that make products interoperate beyond cable 🌈. Those submissions can include things like use cases, protocol requirements, draft MIB modules, and proposed solutions such as new DHCP options 🧚. CableLabs also references IETF and Request For Comments work in its own specs 📚. You can find the public list of CableLabs projects and specs on the CableLabs Web site, http://www.cablelabs.com.

Now the IETF side 🦋. Work happens within Areas, and specific activities are done by working groups chartered inside each Area 🗂️. The Internet Engineering Steering Group (IESG) reviews working group output, and the RFC Editor publishes it 📤. Everything runs on open contribution, so any interested party can join in 🌸. The Internet Standards Process that the IETF follows is described in [RFC2026]. Info on IETF working groups, current work item drafts, meeting schedules, and mailing lists is on the IETF Web site, http://www.ietf.org 💻.

The IETF and CableLabs are forming this liaison relationship because they both want to protect the integrity of the specs each body develops 💖. CableLabs doesn't develop standards except through its participation in Standards Defining Organizations (SDOs) like the IETF 🫶.

The preferred approach is for CableLabs to use IETF specifications unchanged, when that's feasible, and to send any requests for changes to the IETF when they're needed 🔁. Both parties plan to work together so they don't duplicate effort 🤝.

Within this liaison relationship, each organization keeps operating under its own rules and procedures ✨. That includes its own rules on Intellectual Property Rights (IPR), specification elaboration, approval, and maintenance 📜.

2. Basis of Collaboration 💅

When CableLabs is building its specs, it has spotted the benefit of adopting IETF specifications 👀. CableLabs recognizes that interoperating with the existing Internet, and therefore using IETF standards, really matters 🌐. Still, it knows that additions or modifications might be needed so the IETF specs meet CableLabs' needs 🔧. In those cases, a CableLabs individual or a vendor participant working on a CableLabs specification may take their concerns straight to the appropriate IETF working groups for resolution 🎯. If no appropriate working group can be found, or it's not known where to send the communication, or the issue is about resolving consequent matters, the issue goes through the CableLabs designated liaison manager to the IETF liaison manager 📬.

The IETF may also need to ask CableLabs questions to better understand CableLabs requirements, or it may want to offer guidance on using IETF specifications effectively 🧠. Where possible, these conversations happen as part of a discussion between CableLabs and an IETF working group 🗣️. If a working-group-level discussion isn't the right fit for what needs saying, the matter goes through the IETF's designated liaison manager to CableLabs 💌.

3. Document Sharing 📂

Both CableLabs and the IETF are big fans of sharing specification documents and draft requirements that they both care about 💕.

All IETF documents are publicly available on the IETF Web site, and discussion of documents happens on open mailing lists 📣.

CableLabs documents meant for public consumption include CableLabs Technical Reports and CableLabs Specifications that are in an approved and published status 📑. These documents carry the CableLabs ISSUED status and are published for open access on CableLabs' Web site, http://www.cablelabs.com, or at http://www.cablelabs.com/specifications/archives/ 🌟.

For the IETF to make any reference (informative or normative), the document must be in an approved and published state, and publicly available 🔍. CableLabs is expected to share relevant information with IETF participants through individual IETF Contributions, as described in [RFC3978], and it doesn't need a non-disclosure agreement for that 🫶.

CableLabs and the IETF will also work to update and exchange, when appropriate and on a regular basis, a list of dependencies between each organization's specifications and work in progress 🔄.

4. Participation in the IETF Process 🙋‍♀️

The Internet Standards Process is described in [RFC2026]. Participation in the IETF process is open to anyone willing to contribute 💖. That obviously includes individuals who also represent CableLabs or otherwise contribute to CableLabs specifications 🎀. These people can freely join IETF mailing list discussions, submit and review Internet Drafts, and attend IETF meetings 🧚. That helps the IETF better understand CableLabs requirements, and it gives CableLabs a chance to get informal guidance on using IETF specifications 🌸. Most of the technical discussion and decision making in the IETF happens on open mailing lists, so interested folks should subscribe and participate there 📬.

5. Designated Liaison Managers and Responsibilities 👑

When the informal working-group-level interaction isn't enough, matters can be raised through a liaison channel 🔗. CableLabs and the IETF shall each set up liaison functions for communicating with the other organization, and each shall appoint one individual to act as a liaison manager, as described in [RFC4052] and [RFC4053] 🫶.

Formal communications from CableLabs are started by the designated CableLabs liaison manager, who sends a liaison statement to the IETF liaison manager. These must follow the procedures described in [RFC4053] ✉️. The role of the IETF liaison manager is defined in [RFC4052] and [RFC4691] 📋. The IETF liaison manager isn't responsible for telling CableLabs about new work the IETF is taking on. Instead, the designated CableLabs liaison manager or their delegates should subscribe to the IETF lists that announce the creation or rechartering of IETF working groups (ietf-announce), and the lists that announce new work (new-work) 📣🔔.

5.1. IETF Liaison Manager to CableLabs 💌

The preferred way for organizations to work with the IETF is through the working groups 🛠️. The IETF has only a limited number of liaison relationships and liaison managers with other organizations, and a specific person is appointed only when conditions warrant it 🎯.

The Internet Architecture Board (IAB) shall appoint a specific person to serve as the IETF liaison manager to CableLabs 🧚. The role and responsibilities of that IETF liaison manager are described below. In particular, the designated liaison manager is expected to act as an initial contact point in the IETF for administrative aspects of this collaboration that can't easily be handled in other ways. For example, technical-level interactions with IETF Working Groups or Area Directors are handled elsewhere 🗂️. It's agreed that the role doesn't carry an expectation of attending CableLabs meetings or taking part in CableLabs specification development processes, and all liaison efforts for this person are expected to be carried out by electronic mail 📧. The IETF liaison manager also does not have the ability to make exceptions to, or special provisions for, IETF policies and procedures 🙅‍♀️.

The person appointed to the liaison manager role is expected to do the following 💅:

  • perform all tasks as defined in [RFC4052] and [RFC4691],
  • be informed by CableLabs, when appropriate, of CableLabs activities within the IETF, including new work proposals, and be able to report those through appropriate IETF channels,
  • convey liaison statements from the IETF to CableLabs as described in [RFC4053], and be responsible for shepherding CableLabs communication to the relevant parts of the IETF,
  • be able to raise issues with CableLabs technical leadership, as well as the IAB members and IETF Area Directors, as required.

Last thing, and it's a bit of a gatekeeping moment 🚪: CableLabs meetings are normally only open to delegates from CableLabs members, or from manufacturers who have signed the appropriate agreements to participate in CableLabs projects or meetings 🔐.

(part 2 next, bestie 🧚💜)

5.2. CableLabs Liaison Manager to IETF ✨

CableLabs SHALL set up an IETF liaison function and name one person to be the CableLabs liaison manager to IETF 💼 for all the stuff about CableLabs and IETF working together. That person is expected to work with the relevant IETF and CableLabs projects and focus teams, and to keep the conversation flowing between the two groups 🫶.

6. Formal Liaison Statements 📜

Okay, the main vibe here is that communication at the working group level is strongly encouraged 🌸. It's the preferred primary method for coordinating activity, so whenever it's possible, that's the move 💅.

Formal communication between CableLabs and IETF is also allowed when it's actually needed 🎀. These exchanges get written up as Liaison Statements, and the IETF uses the CableLabs liaison manager to pass those statements between the IETF and CableLabs 🦋. The procedure for handling incoming liaison statements defined in [RFC4053] MUST be followed by both the liaison manager named by the IETF and the liaison manager designated by CableLabs 🔥.

Here's the important bit 👑: every liaison statement made by the IETF, or sent to the IETF, SHALL be published by the IETF as a public document 🌈. And all liaison statements made by the IETF will follow the IETF IPR policy as written in [RFC3978], [RFC3979], [RFC4748], [RFC4371], and any updates ✨.

7. Contributions 🧚

People working on CableLabs' projects who want to contribute to the IETF can do so as IETF participants 🙋‍♀️. Those contributions fall under the IETF's IPR policy, as documented in [RFC3978] and [RFC3979] 📚.

IETF participants whose companies are CableLabs members, or who have signed the right agreements with CableLabs, can also contribute to CableLabs' projects and specifications 💜.

Quick heads up 🙈: CableLabs mailing lists are not open to the general public. It is RECOMMENDED that work of mutual interest be discussed on the relevant IETF mailing lists instead 📬.

And finally, the IETF and CableLabs will not co-develop any documents or material 🚫. Separate kitchens, bestie 🍓.

8. Security Considerations 🔒

This document does not directly affect the security of the Internet. Honestly, low-drama section, and I'm here for it 😌✨.

9. IANA Considerations 🌷

This section gives IANA some guidelines to think about when adding references to a CableLabs specification in its registries 📋. CableLabs keeps a specification repository with a stable URL for each published document under http://www.cablelabs.com/specifications/. A stable document URL follows this format: http://www.cablelabs.com/specifications/CableLabs_docname.pdf, where CableLabs_docname is the CableLabs document name 🦋.

IANA is requested to use the above document URL format when referencing CableLabs specifications in its registries 💖.

10. Acknowledgments 🫶

The authors want to thank the following people for their comments and contributions: Ralph Brown, Brian Carpenter, Leslie Daigle, Ralph Droms, Alain Durand, Simon Krauss, Thomas Narten, Dan Romascanu, and Dave Oran 🌟. Iconic squad, all of you 👑.

It's also acknowledged that this document is inspired by [RFC3113] and [RFC3131] 🌈.

This document was produced using the xml2rfc tool (RFC2629) 🛠️💅.

11. Common Work Areas 🌸

This section MAY be removed from future versions of this document 🙃. It's here to give some background on the areas that may be common to both CableLabs and the IETF 🔍.

At the time of writing, IETF working groups of particular interest to CableLabs include:

DHCWG, KERBEROS, IPCDN, SIP, SIPPING, SIMPLE, SPEERMINT, IPTEL, BEHAVE, AVT, MMUSIC, AAA, GEOPRIV, DISMAN, MSEC, ENUM, ECRIT, IPV6, MIP6, NETCONF, ISMS, BRIDGE, ENTMIB, MAGMA, V6OPS, DNSEXT, IPSEC, L2VPN, ZEROCONF, L2TPEXT, and TLS 🧚✨.

12. Informative References 📚

[RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
           3", BCP 9, RFC 2026, October 1996.

[RFC3113]  Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin,
           "3GPP-IETF Standardization Collaboration", RFC 3113,
           June 2001.

[RFC3131]  Bradner, S., Calhoun, P., Cuschieri, H., Dennett, S.,
           Flynn, G., Lipford, M., and M. McPheters, "3GPP2-IETF
           Standardization Collaboration", RFC 3131, June 2001.

[RFC3978]  Bradner, S., "IETF Rights in Contributions", BCP 78,
           RFC 3978, March 2005.

[RFC3979]  Bradner, S., "Intellectual Property Rights in IETF
           Technology", BCP 79, RFC 3979, March 2005.

[RFC4052]  Daigle, L. and Internet Architecture Board, "IAB Processes
           for Management of IETF Liaison Relationships", BCP 102,
           RFC 4052, April 2005.

[RFC4053]  Trowbridge, S., Bradner, S., and F. Baker, "Procedures for
           Handling Liaison Statements to and from the IETF",
           BCP 103, RFC 4053, April 2005.

[RFC4371]  Carpenter, B. and L. Lynch, "BCP 101 Update for IPR
           Trust", BCP 101, RFC 4371, January 2006.

[RFC4691]  Andersson, L., "Guidelines for Acting as an IETF Liaison
           to Another Organization", RFC 4691, October 2006.

[RFC4748]  Bradner, S., "RFC 3978 Update to Recognize the IETF
           Trust", BCP 78, RFC 4748, October 2006.

Authors' Addresses 💌

Jean-Francois Mule
CableLabs
858 Coal Creek Circle
Louisville, CO  80027
USA

EMail: jf.mule@cablelabs.com


W. Mark Townsley
Cisco Systems
7025 Kit Creek Road
PO Box 14987
Research Triangle Park, NC  27709
USA

EMail: mark@townsley.net

Copyright (C) The IETF Trust (2007) 💜. Here's the legal bit, verbatim so nothing gets lost in translation:

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.

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, THE IETF TRUST 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.

Intellectual Property 🦋

Here's the IP section, also verbatim 🫶:

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.
📦 where this page comes from