idnits 2.17.1 draft-mule-ietf-cablelabs-collaboration-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 415. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 426. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 433. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 439. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 13, 2006) is 6398 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Obsolete informational reference (is this intentional?): RFC 3978 (Obsoleted by RFC 5378) -- Obsolete informational reference (is this intentional?): RFC 3979 (Obsoleted by RFC 8179) Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group J-F. Mule 3 Internet-Draft CableLabs 4 Expires: April 16, 2007 W. Townsley 5 Cisco Systems 6 October 13, 2006 8 CableLabs - IETF Standardization Collaboration 9 draft-mule-ietf-cablelabs-collaboration-02.txt 11 Status of this Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on April 16, 2007. 36 Copyright Notice 38 Copyright (C) The Internet Society (2006). 40 Abstract 42 This document describes the collaboration between the Cable 43 Television Laboratories, Inc. (CableLabs) and the Internet 44 Engineering Task Force (IETF). 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. Basis of Collaboration . . . . . . . . . . . . . . . . . . . . 5 50 3. Document Sharing . . . . . . . . . . . . . . . . . . . . . . . 6 51 4. Participation in the IETF Process . . . . . . . . . . . . . . 7 52 5. Designated Liaisons . . . . . . . . . . . . . . . . . . . . . 8 53 6. Formal Liaison Statements . . . . . . . . . . . . . . . . . . 10 54 7. Contributions . . . . . . . . . . . . . . . . . . . . . . . . 11 55 8. Terms of Agreement . . . . . . . . . . . . . . . . . . . . . . 12 56 8.1. Limitation of Liability . . . . . . . . . . . . . . . . . 12 57 8.2. General . . . . . . . . . . . . . . . . . . . . . . . . . 12 58 9. Security Considerations . . . . . . . . . . . . . . . . . . . 13 59 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 60 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 15 61 12. Common Work Areas . . . . . . . . . . . . . . . . . . . . . . 16 62 13. Informative References . . . . . . . . . . . . . . . . . . . . 17 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 18 64 Intellectual Property and Copyright Statements . . . . . . . . . . 19 66 1. Introduction 68 This document contains a set of principles and guidelines that serves 69 as the basis for establishing a cooperation framework between the 70 Cable Television Laboratories, Inc. and the Internet Engineering Task 71 Force (IETF). This cooperation is intended to secure timely 72 development of technical specifications that facilitate maximum 73 interoperability with existing Internet systems, devices, and 74 protocols. 76 CableLabs is a non-profit research and development consortium that is 77 dedicated to pursuing new cable telecommunications technologies and 78 to helping its cable operator members integrate those technical 79 advancements into their business objectives. Within CableLabs, 80 specification activities are organized into projects like CableHome, 81 DOCSIS, PacketCable and OpenCable and technical work is conducted in 82 focus teams. Product vendors, manufacturers and cable operator 83 members are invited to join the focus teams which create technical 84 specifications. From time to time, CableLabs submits technical 85 requirements or requirement specifications to IETF in order to seek 86 expert reviews and solicit comments to create solutions that foster 87 product interoperability beyond cable. CableLabs' submissions may 88 for example include use cases, protocol requirements, draft MIB 89 modules, and proposed solutions for comments such as new DHCP 90 options. CableLabs also references IETF Request For Comments in its 91 specifications. The list of CableLabs projects and specifications 92 available publicly can be found at the CableLabs web site, 93 http://www.cablelabs.com. 95 Within the IETF, activities are undertaken within a framework of 96 Areas, with specific activities being undertaken by working groups 97 that are chartered within each Area. Working group output is 98 reviewed by the Internet Engineering Steering Group (IESG) and 99 published by the RFC-Editor. IETF activities are based on a 100 principle of open contribution and participation by any interested 101 party. Details on the Internet Standards Process followed by IETF 102 can be found in [RFC2026]. Information on IETF working groups, 103 current work item drafts, meeting schedules, and mailing lists are 104 published on the IETF web site, http://www.ietf.org. 106 The IETF and CableLabs are cooperating with a mutual desire to 107 support the integrity of specifications developed by each body. 108 CableLabs does not develop standards other than through its 109 participation with Standards Defining Organizations (SDOs) like the 110 IETF. 112 The preferred approach is that CableLabs uses the IETF specifications 113 unchanged, if feasible, and communicates requirements for change to 114 the IETF, as needed. The parties intend to work together in an 115 effort to avoid duplication of work. 117 Within the framework of this collaboration, each organization will 118 operate according to its own rules and procedures, including rules 119 governing Intellectual Property Rights (IPR), specification 120 elaboration, approval, and maintenance. 122 2. Basis of Collaboration 124 In the further development of CableLabs specifications, the benefit 125 of adopting IETF specifications has been identified. Although this 126 document recognizes the importance of interoperability of the 127 CableLabs specifications with the existing Internet and hence the use 128 of IETF standards, CableLabs recognizes that additions or 129 modifications might be needed in order to make the IETF 130 specifications meet the needs of CableLabs. In such cases, 131 CableLabs, directly, or via one of the vendor participants or 132 individuals working on a CableLabs specification will take its 133 concerns directly to the appropriate IETF working groups for 134 resolution. When no appropriate working group can be found or it is 135 not known where to direct the communication, or in the case of 136 resolution of consequent matters, the issue will be raised through 137 the CableLabs designated liaison to the IETF. 139 The IETF may also need to ask questions of CableLabs in order to 140 refine its understanding of CableLabs requirements or may wish to 141 offer guidance to CableLabs on the effective use of IETF 142 specifications. Where possible, these communications will occur in 143 the context of a discussion between CableLabs and an IETF working 144 group. In the event that a working group level discussion is deemed 145 inappropriate for the desired communication, the matter will be 146 raised through the IETF's designated liaison to CableLabs. 148 3. Document Sharing 150 Both CableLabs and the IETF encourage the sharing of specification 151 documents and draft requirements that are of mutual interest. 153 All IETF documents are publicly available from the IETF web site, and 154 discussion of documents is hosted on open mailing lists. 156 CableLabs documents intended for public consumption include CableLabs 157 Technical Reports and CableLabs Specifications that are in ISSUED 158 status. They are published for open access on CableLabs' web site, 159 http://www.cablelabs.com, or 160 http://www.cablelabs.com/specifications/archives/. 162 It is expected that CableLabs will share relevant information with 163 IETF participants via IETF Contributions as described in [RFC3978] 164 and without requiring a non-disclosure agreement. 166 CableLabs and the IETF will work to update and exchange, when 167 appropriate and on a regular basis, a list of dependencies between 168 each organization's specifications and work in progress. 170 4. Participation in the IETF Process 172 The Internet Standards Process is described in [RFC2026]. 173 Participation in the IETF process is completely open. This allows 174 CableLabs, its members and any CableLabs vendor contributor to 175 participate to whatever extent CableLabs considers appropriate in 176 IETF meetings and mailing list discussions to assist the IETF in 177 refining its understanding of CableLabs requirements and in meeting 178 requirements that the IETF deems appropriate. This close working 179 relationship also offers an excellent opportunity for CableLabs to 180 receive informal guidance from IETF on CableLabs use of IETF 181 specifications. 183 The vast majority of technical discussions and decision making within 184 the IETF is undertaken by using open mailing lists. It is 185 recommended that interested individuals subscribe to and participate 186 on these lists. 188 The IETF liaison is not responsible for notifying CableLabs of new 189 work to be undertaken by the IETF. The designated CableLabs liaison 190 should subscribe to IETF lists announcing the creation or 191 rechartering of IETF working groups (ietf-announce) and the lists 192 announcing new work (new-work). 194 5. Designated Liaisons 196 When the informal working group level of interaction is insufficient, 197 matters can be raised through a liaison channel. CableLabs and the 198 IETF shall each establish liaison functions for communication with 199 the other organization and shall appoint one or more individuals to 200 those functions. 202 5.1. IETF Liaison to CableLabs 204 The preferred way for organizations to work with IETF is through the 205 working groups. However, IETF has a limited number of individual 206 liaison roles with other organizations when conditions warrant the 207 appointment of a specific person. 209 The Internet Architecture Board (IAB) shall appoint a specific person 210 to serve as the CableLabs Liaison. The role of the IETF's CableLabs 211 Liaison is to act as an initial contact point in IETF for 212 administrative aspects of this collaboration that cannot easily be 213 handled in other ways (e.g., at a technical level by interactions 214 with IETF Working Groups or Area Directors). It is agreed that the 215 role does not carry the expectation of attendance at CableLabs 216 meetings or participation in CableLabs specification development 217 processes, and it is anticipated that all liaison efforts assigned to 218 this individual will be carried out by electronic mail. It is 219 understood that the liaison does not have the ability to make 220 exceptions to, or special provisions for, IETF policies and 221 procedures. 223 It is expected that the individual appointed to this role would: 225 o be informed by CableLabs, when appropriate, of CableLabs 226 activities within the IETF, including new work proposals, and be 227 able to report those using appropriate channels within the IETF, 229 o convey liaisons statements from CableLabs to the IETF, and be 230 responsible for shepherding CableLabs communication to the 231 relevant parts of the IETF, 233 o report to CableLabs on progress with IETF consideration of 234 CableLabs liaison statements, and 236 o be able to raise issues with CableLabs technical leadership as 237 well as the IAB members and IETF Area Directors, as required. 239 CableLabs meetings are normally only open to delegates from CableLabs 240 members or those manufacturers who have signed the appropriate 241 agreements to participate in CableLabs projects or meetings. 243 5.2. CableLabs Liaison to IETF 245 CableLabs shall establish an IETF liaison to be the initial contact 246 point in CableLabs for matters pertaining to the CableLabs- IETF 247 cooperation. The CableLabs-IETF liaison function, therefore, is 248 expected to work with the concerned IETF and CableLabs projects and 249 focus teams and to support the interaction between CableLabs and the 250 IETF. 252 6. Formal Liaison Statements 254 Whenever possible, and as the preferred primary method of 255 communication and coordination of activity, communication at the 256 working group level is strongly encouraged. 258 When deemed necessary, formal communication between CableLabs and 259 IETF is also permitted. These communications are to be recorded in 260 the form of Liaison Statements, and the IETF will use the CableLabs 261 liaison role to convey these statements between the IETF and 262 CableLabs. All liaison statements made by the IETF or directed to 263 the IETF shall be published by the IETF as public documents. All 264 liaison statements made by the IETF will comply with the IETF IPR 265 policy as documented in [RFC3978], [RFC3979] and any updates. 267 7. Contributions 269 CableLabs members or entities working on CableLabs' projects may make 270 contributions to the IETF in their capacity as IETF participants, 271 under the IETF's IPR policy, as documented in [RFC3978] and 272 [RFC3979]. 274 IETF participants whose companies are CableLabs members or have 275 signed the appropriate agreements with CableLabs may also make 276 contributions to CableLabs' projects and specifications. 278 CableLabs mailing lists are not open to the general public. It is 279 recommended that work of mutual interest be discussed on the relevant 280 IETF mailing lists. 282 The IETF and CableLabs will not co-develop any documents or material. 284 8. Terms of Agreement 286 8.1. Limitation of Liability 288 Neither the IETF or CableLabs makes any representations with respect 289 to and does not warrant the accuracy of any information or any 290 document. Without limiting the foregoing, each party agrees to 291 accept the terms of and reproduce any warranty disclaimers or 292 limitations of liability that are included in any reproduction of 293 published material made available to it under this cooperation 294 framework. 296 8.2. General 298 The following general terms of agreement apply: 300 o Neither CableLabs nor the IETF acquires any intellectual or 301 industrial property rights under this cooperation framework or 302 through any disclosure. No license to any patent, trademark, 303 copyright, or other proprietary right is granted here. 305 o There is no obligation for either CableLabs or the IETF to 306 incorporate the materials presented by the other party. 308 o This cooperation framework and the relationship between the IETF 309 and CableLabs does not constitute a partnership, joint venture, 310 agency, or contract of employment between the IETF and CableLabs. 312 9. Security Considerations 314 This document does not directly affect the security of the Internet. 316 10. IANA Considerations 318 This section provides some guidelines for IANA to consider when 319 adding references to a CableLabs specification in its registries. 321 CableLabs maintains current and archived specification repositories. 322 When a specification is updated, a copy of the previous version is 323 moved to the archived repository to provide a stable reference. 325 IANA should add a pointer to both the current and archive 326 specification repositories when referencing a CableLabs 327 specification, for example: 329 o For a DOCSIS or cable modem related specification, consider adding 330 a reference to both http://www.cablemodem.com/specifications/ and 331 http://www.cablelabs.com/specifications/archives/ ; 333 o For a PacketCable specification, consider adding a reference to 334 both http://www.packetcable.com/specifications/ and 335 http://www.cablelabs.com/specifications/archives/ 337 11. Acknowledgments 339 The authors wish to thank the following individuals for their 340 comments and contributions: Ralph Brown, Brian Carpenter, Leslie 341 Daigle, Ralph Droms, Alain Durand, Simon Krauss, Thomas Narten, Dan 342 Romascanu, 344 It is also acknowledged that this document is inspired from [RFC3113] 345 and [RFC3131]. 347 This document was produced using the xml2rfc tool (RFC2629). 349 12. Common Work Areas 351 This section may be removed from future versions of this document. 352 It is provided here to give some background information on the areas 353 that may be common to both CableLabs and the IETF. 355 At the time of this writing, IETF working groups which are of 356 particular interest to CableLabs include: 358 dhcwg, kerberos, ipcdn, sip, sipping, simple, speermint, iptel, 359 behave, avt, mmusic, aaa, geopriv, disman, msec, enum, ecrit, ipv6, 360 mip6, netconf, isms, bridge, entmib, magma, v6ops, dnsext, ipsec, 361 l2vpn, zeroconf, l2tpext, tls. 363 13. Informative References 365 [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 366 3", BCP 9, RFC 2026, October 1996. 368 [RFC3113] Rosenbrock, K., Sanmugam, R., Bradner, S., and J. Klensin, 369 "3GPP-IETF Standardization Collaboration", RFC 3113, 370 June 2001. 372 [RFC3131] Bradner, S., Calhoun, P., Cuschieri, H., Dennett, S., 373 Flynn, G., Lipford, M., and M. McPheters, "3GPP2-IETF 374 Standardization Collaboration", RFC 3131, June 2001. 376 [RFC3978] Bradner, S., "IETF Rights in Contributions", BCP 78, 377 RFC 3978, March 2005. 379 [RFC3979] Bradner, S., "Intellectual Property Rights in IETF 380 Technology", BCP 79, RFC 3979, March 2005. 382 Authors' Addresses 384 Jean-Francois Mule 385 CableLabs 386 858 Coal Creek Circle 387 Louisville, CO 80027 388 USA 390 Email: jf.mule@cablelabs.com 392 W. Mark Townsley 393 Cisco Systems 394 7025 Kit Creek Road 395 PO Box 14987 396 Research Triangle Park, NC 27709 397 USA 399 Email: mark@townsley.net 401 Full Copyright Statement 403 Copyright (C) The Internet Society (2006). 405 This document is subject to the rights, licenses and restrictions 406 contained in BCP 78, and except as set forth therein, the authors 407 retain all their rights. 409 This document and the information contained herein are provided on an 410 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 411 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 412 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 413 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 414 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 415 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 417 Intellectual Property 419 The IETF takes no position regarding the validity or scope of any 420 Intellectual Property Rights or other rights that might be claimed to 421 pertain to the implementation or use of the technology described in 422 this document or the extent to which any license under such rights 423 might or might not be available; nor does it represent that it has 424 made any independent effort to identify any such rights. Information 425 on the procedures with respect to rights in RFC documents can be 426 found in BCP 78 and BCP 79. 428 Copies of IPR disclosures made to the IETF Secretariat and any 429 assurances of licenses to be made available, or the result of an 430 attempt made to obtain a general license or permission for the use of 431 such proprietary rights by implementers or users of this 432 specification can be obtained from the IETF on-line IPR repository at 433 http://www.ietf.org/ipr. 435 The IETF invites any interested party to bring to its attention any 436 copyrights, patents or patent applications, or other proprietary 437 rights that may cover technology that may be required to implement 438 this standard. Please address the information to the IETF at 439 ietf-ipr@ietf.org. 441 Acknowledgment 443 Funding for the RFC Editor function is currently provided by the 444 Internet Society.