idnits 2.17.1 draft-iab-rfc3356bis-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 3 instances of too long lines in the document, the longest one being 84 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 126 has weird spacing: '... topics of mu...' -- The document date (June 4, 2012) is 4337 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '6' is defined on line 575, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 581, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 587, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 590, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 595, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 599, but no explicit reference was found in the text == Unused Reference: '13' is defined on line 602, but no explicit reference was found in the text == Unused Reference: '14' is defined on line 605, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 612, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 615, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 618, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3979 (ref. '4') (Obsoleted by RFC 8179) ** Obsolete normative reference: RFC 4879 (ref. '5') (Obsoleted by RFC 8179) -- Obsolete informational reference (is this intentional?): RFC 2223 (ref. '8') (Obsoleted by RFC 7322) -- Obsolete informational reference (is this intentional?): RFC 2436 (ref. '9') (Obsoleted by RFC 3356) -- Obsolete informational reference (is this intentional?): RFC 3356 (ref. '10') (Obsoleted by RFC 6756) -- Obsolete informational reference (is this intentional?): RFC 2028 (ref. '11') (Obsoleted by RFC 9281) Summary: 3 errors (**), 0 flaws (~~), 13 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Architecture Board (IAB) S. Trowbridge, Ed. 2 Internet-Draft Alcatel-Lucent 3 Obsoletes: 3356 E. Lear, Ed. 4 Intended status: Informational Cisco Systems 5 G. Fishman, Ed. 6 Pearlfisher International 7 S. Bradner, Ed. 8 Harvard University 9 Expires: December 4, 2012 June 4, 2012 11 Internet Engineering Task Force and International 12 Telecommunication Union - Telecommunication Standardization 13 Sector Collaboration Guidelines 15 draft-iab-rfc3356bis-02 17 Abstract 19 This document provides guidance to aid in the understanding of 20 collaboration on standards development between the International 21 Telecommunication Union -- Telecommunication Standardization 22 Sector (ITU-T) and the Internet Society (ISOC) -- Internet 23 Engineering Task Force (IETF). It is an update of and obsoletes 24 RFC 3356. The updates reflect changes in the IETF and ITU-T 25 since RFC 3356 was written. The bulk of this document is common 26 text with ITU-T A Series Supplement 3. 28 Note: This was approved by ITU-T TSAG on xx July 2012 as a 29 Supplement to the ITU-T A-Series of Recommendations (will be 30 numbered as A-Series Supplement 3). 32 Status of this Memo 34 This Internet-Draft is submitted to IETF in full conformance 35 with the provisions of BCP 78 and BCP 79. 37 Internet-Drafts are working documents of the Internet 38 Engineering Task Force (IETF), its areas, and its working 39 groups. Note that other groups may also distribute working 40 documents as Internet-Drafts. 42 Internet-Drafts are draft documents valid for a maximum of six 43 months and may be updated, replaced, or obsoleted by other 44 documents at any time. It is inappropriate to use Internet- 45 Drafts as reference material or to cite them other than as "work 46 in progress". 48 The list of current Internet-Drafts can be accessed at 49 http://www.ietf.org/ietf/1id-abstracts.txt. 51 The list of Internet-Draft Shadow Directories can be accessed at 52 http://www.ietf.org/shadow.html. 54 This Internet-Draft will expire on July 9, 2012. 56 Copyright Notice 58 Copyright (c) 2012 IETF Trust and the persons identified as the 59 document authors. All rights reserved. 61 This document is subject to BCP 78 and the IETF Trust's Legal 62 Provisions Relating to IETF Documents 63 (http://trustee.ietf.org/license-info) in effect on the date of 64 publication of this document. Please review these documents 65 carefully, as they describe your rights and restrictions with 66 respect to this document. Code Components extracted from this 67 document must include Simplified BSD License text as described 68 in Section 4.e of the Trust Legal Provisions and are provided 69 without warranty as described in the Simplified BSD License. 71 Table of Contents 73 1. Introduction & Scope...........................................4 74 2. Guidance on Collaboration......................................5 75 2.1. How to Interact on ITU-T or IETF Work Items...............5 76 2.1.1. How the ITU-T is informed about Existing IETF Work 77 Items.......................................................6 78 2.1.2. How the IETF is informed about Existing ITU-T Work 79 Items.......................................................6 80 2.1.3. How the ITU-T is informed about proposed new IETF work 81 items.......................................................6 82 2.1.4. How the IETF is informed about ITU-T Work Items......7 83 2.2. Representation............................................7 84 2.2.1. IETF Recognition at ITU-T............................7 85 Experts and representatives from the IETF that are chosen by 86 IETF leadership may participate in ITU-T meetings as ISOC 87 delegates. The ISOC focal point will facilitate registration 88 and verification of these people, as appropriate............7 89 2.2.2. ITU-T Recognition at ISOC/IETF.......................7 90 2.3. Communication outside of Meetings.........................8 91 2.4. Mailing Lists.............................................8 92 2.5. Document Sharing..........................................9 93 2.5.1. Contributions and Liaisons from the IETF to ITU-T....9 94 2.5.2. Conributions and liaisons form the ITU-T to IETF....10 95 2.5.3. ITU-T & IETF........................................10 96 2.6. Simple Cross Referencing.................................11 97 2.7. Preliminary Work Efforts.................................11 98 2.8. Additional Items.........................................11 99 2.8.1. IETF Information that may be of use to ITU-T 100 participations.............................................11 101 2.8.2. ITU-T Information that may be useful to IETF 102 participants...............................................12 103 3. Security Considerations.......................................13 104 4. IANA Considerations...........................................13 105 5. Acknowledgements..............................................13 106 6. References....................................................13 107 6.1. Normative References.....................................13 108 6.2. Informative References...................................14 109 7. Changes since RFC3356.........................................15 110 8. Authors' Addresses............................................15 112 [The following note to be removed upon publication as an RFC] 114 Editors' Note: 116 This Informational Internet-Draft is intended for publication as an 117 RFC with the IAB stream, and is subject to the publication process 118 described in RFC 4845. 120 1. Introduction & Scope 122 This document provides guidance to aid in the understanding of 123 collaboration on standards development between the International 124 Telecommunication Union - Telecommunication Standardization Sector 125 (ITU-T) and the Internet Society (ISOC) -- Internet Engineering Task 126 Force (IETF). Early identification of topics of mutual interest 127 will allow for constructive efforts between the two organizations. 129 In the IETF, work is done in Working Groups (WG), mostly through 130 open, public mailing lists rather than face-to-face meetings. 131 WGs are organized into Areas, each Area being managed by two co- 132 Area Directors. Collectively, the Area Directors comprise the 133 Internet Engineering Steering Group (IESG). 135 In the ITU-T, work is defined by study Questions which are 136 worked on mostly through meetings led by rapporteurs (these are 137 sometimes called "Rapporteur's Group meetings). Questions are 138 generally grouped within Working Parties (WPs) led by a WP 139 chairman. Working Parties report to a parent Study Group led by 140 a SG chairman. Work may also be conducted in ITU-T focus groups 141 (see Section 2.5) 143 To foster ongoing communication between the ITU-T and IETF, it is 144 important to identify and establish contact points within each 145 organization. Contact points may include: 147 1. ITU-T Study Group Chair and IETF Area Director 149 An IETF Area Director is the individual responsible for 150 overseeing a major focus of activity with a scope similar to 151 that of an ITU-T study group chairman. These positions are 152 both relatively long-term (of several years) and offer the 153 stability of contact points between the two organizations for 154 a given topic. 156 2. ITU-T Rapporteur and IETF Working Group Chair 158 An IETF Working Group Chair is an individual who is assigned 159 to lead the work on a specific task within one particular Area 160 with a scope similar to that of an ITU-T rapporteur. These 161 positions are working positions (of a year or more) that 162 typically end when the work on a specific topic ends. 163 Collaboration here is very beneficial to ensure the actual 164 work gets done. 166 3. Other Contact Points 168 It may be beneficial to establish additional contact points 169 for specific topics of mutual interest. These contact points 170 should be established early in the work effort, and in some 171 cases the contact point identified by each organization may be 172 the same individual. In addition, the ITU-T has an additional 173 level of management, the working party chair. From time to 174 time it may be beneficial for this person to exchange views 175 with IETF Working Group Chairs and Area Directors. 177 Note that the current IETF Area Directors and Working Group 178 Chairs can be found in the IETF Working Group charters. The 179 current ITU-T study group chairmen and rapporteurs are listed on 180 the ITU-T web page. 182 2. Guidance on Collaboration 184 This section describes how the existing processes within the IETF 185 and ITU-T may be utilized to enable collaboration between the 186 organizations. 188 2.1. How to Interact on ITU-T or IETF Work Items 190 Study groups that have identified work topics that are IP- 191 related should evaluate the relationship with topics defined in 192 the IETF. Current IETF Working Groups and their charters (IETF 193 definition of the scope of work) are listed in the IETF archives 194 (see Section 2.8.1). 196 A study group may decide that development of a Recommendation on 197 a particular topic may benefit from collaboration with the IETF. 198 The study group should identify this collaboration in its work 199 plan (specifically in that of each Question involved), 200 describing the goal of the collaboration and its expected 201 outcome. 203 An IETF Working Group should also evaluate and identify areas of 204 relationship with the ITU-T and document the collaboration with 205 the ITU-T study group in its charter. 207 The following sections outline a process that can be used to 208 enable each group to be informed about the other's new work 209 items. 211 2.1.1. How the ITU-T is informed about Existing IETF Work Items 213 The responsibility is on individual study groups to review the 214 current IETF Working Groups to determine if there are any topics of 215 mutual interest. Should a study group believe that there is an 216 opportunity for collaboration on a topic of mutual interest, it 217 should contact both the IETF Working Group Chair and the Area 218 Director(s) responsible. This may be accompanied by a formal liaison 219 statement (see 3.2.4). 221 2.1.2. How the IETF is informed about Existing ITU-T Work Items 223 The IETF through its representatives will review current work of 224 various study groups from time to time. Each ITU-T study group's 225 web pages on the ITU-T web site contain its current list of 226 Questions as well as its current work programme. When a common area 227 of work is identified, the matter is referred to appropriate Working 228 Group chairs and Area Directors, where they may consider sending a 229 liaison statement to the appropriate study group. 231 2.1.3. How the ITU-T is informed about proposed new IETF work items 233 The IETF maintains a mailing list for the distribution of proposed 234 new work items among standards development organizations. Many such 235 items can be identified in proposed Birds of a Feather (BoF) 236 sessions, as well as draft charters for working groups. The IETF 237 forwards all such draft charters for all new and revised Working 238 Groups and Birds Of a Feather session announcements to the IETF 239 NewWork mailing list. An ITU-T mailing list is subscribed to this 240 list. Leadership of study groups may subscribe to this ITU-T mailing 241 list, which is maintained by the Telecommunication Standardization 242 Bureau (TSB). Members of the SG-specific listname may include the 243 SG chairman, SG vice-chairmen, working party chairmen, concerned 244 rapporteurs, other experts designated by the SG and the SG 245 Counsellor. This will enable the SGs to monitor the new work items 246 for possible overlap or interest to their study group. It is 247 expected that this mailing list will see a few messages per month. 249 Each SG chairman, or designated representative, may provide comments 250 on these charters by responding to the IESG mailing list at 251 iesg@ietf.org clearly indicating their ITU-T position and the nature 252 of their concern. Plain-text email is preferred on the IESG mailing 253 list. 255 It should be noted that the IETF turnaround time for new Working 256 Group charters is two weeks. As a result, the mailing list 257 should be consistently monitored. 259 2.1.4. How the IETF is informed about ITU-T Work Items 261 The ITU-T accepts new areas of work through the creation or update 262 of Questions and these can be found on the ITU-T Study Group web 263 pages. In addition, the ITU-T work programme is documented on each 264 ITU-T study group's web page on the ITU-T web site. 266 Study groups should send updates to the IETF NewWork mailing list as 267 new Questions are contemplated or created, terms of reference for 268 Questions are contemplated or updated, or otherwise when there is 269 reason to believe that a particular effort might be of interest to 270 the IETF. Area Directors or WG Chairs should provide comments 271 through liaison statements or direct email to the relevant SG 272 chairman in cases of possible overlap or interest. 274 2.2. Representation 276 ISOC, including its standards body IETF, is a Sector Member of the 277 ITU-T. As a result, ISOC delegates are therefore afforded the same 278 rights as other ITU-T Sector Members (see 2.2.1). Conversely, ITU-T 279 delegates may participate in the work of the IETF as representatives 280 of the ITU-T (see 2.2.2). To promote collaboration it is useful to 281 facilitate communication between the organizations as further 282 described below. 284 2.2.1. IETF Recognition at ITU-T 286 Experts and representatives from the IETF that are chosen by IETF 287 leadership normally participate in ITU-T meetings as ISOC delegates. 288 The ISOC focal point will facilitate registration and verification 289 of these people, as appropriate. 291 2.2.2. ITU-T Recognition at ISOC/IETF 293 ITU-T study group Chairmen can authorize one or more members to 294 attend an IETF meeting as an official ITU-T delegate speaking 295 authoritatively on behalf of the activities of the study group (or a 296 particular rapporteur group). The study group chairman sends the 297 ITU-T list of delegates by email to the Working Group chair, with a 298 copy to the Area Directors, and also to the study group. Note that, 299 according to IETF process, opinions expressed by any such delegate 300 are given equal weight with opinions expressed by any other working 301 group participant. 303 2.3. Communication outside of Meetings 305 Informal communication between contact points and experts of both 306 organizations is encouraged. However, note that formal 307 communication from an ITU-T study group, working party or rapporteur 308 group to an associated IETF contact point must be explicitly 309 approved and identified as coming from the study group, working 310 party or rapporteur group, respectively. Formal liaison statements 311 from the ITU-T to the IETF are transmitted according to the 312 procedures described in [2]. These liaison statements are placed by 313 the IETF onto a liaison statements web page at 314 https://datatracker.ietf.org/liaison/. An individual at the IETF is 315 assigned responsibility for dealing with each liaison statement that 316 is received. The name and contact information of the responsible 317 person and any applicable deadline is listed with the links to the 318 liaison statement on this web page. 320 Formal liaison statements from the IAB, the IETF, an IETF Working 321 Group or Area to the ITU-T are generated, approved, and transmitted 322 according to the procedures described in [2] and [15]. Formal 323 communication is intended to allow the sharing of positions between 324 the IETF and the ITU-T outside of actual documents (as described in 325 2.5.1). This covers such things as comments on documents and 326 requests for input. 328 2.4. Mailing Lists 330 All IETF Working Groups and all ITU-T study group Questions have 331 associated mailing lists. 333 In the IETF, the mailing list is the primary vehicle for discussion 334 and decision-making. It is recommended that the ITU-T experts 335 interested in particular IETF Working Group topics subscribe to and 336 participate in these lists. IETF WG mailing lists are open to all 337 subscribers. The IETF Working Group mailing list subscription and 338 archive information are noted in each Working Group's charter. In 339 the ITU-T, the TSB has set up formal mailing lists for Questions, 340 working parties and other topics within study groups (more detail 341 can be found on the ITU-T website). These mailing lists are 342 typically used for ITU-T correspondence, including technical 343 discussion, meeting logistics, reports, etc. Note that individual 344 subscribers to this list must be affiliated with an ITU-T member or 345 associate (at this time, there is no blanket inclusion of all IETF 346 participants as members, however, as a member, the ISOC focal point 347 can facilitate access by IETF technical experts, liaison 348 representatives, or liaison managers). IETF participants may 349 subscribe to ITU-T focus group email lists if they are from a 350 country that is a member of ITU-T. 352 2.5. Document Sharing 354 During the course of ITU-T and IETF collaboration it is important to 355 share working drafts and documents among the technical working 356 groups. Initially proposed concepts and specifications typically 357 can be circulated by email (often just repeating the concept and not 358 including the details of the specification) on both the IETF and 359 ITU-T mailing lists. In addition, working texts (or URLs) of draft 360 Recommendations, Internet-Drafts or RFCs may also be sent between 361 the organizations as described below. 363 Internet-Drafts are available on the IETF web site. The ITU-T can 364 make selected ITU-T documents at any stage of development available 365 to IETF by attaching them to a formal liaison statement. Although a 366 communication can point to a URL where a non-ASCII document (e.g., 367 Word) can be downloaded, attachments in proprietary formats to an 368 IETF mailing list are discouraged. It should also be recognized 369 that the official version of all IETF documents are in ASCII. 371 2.5.1. Contributions and Liaison Statements from the IETF to ITU-T 373 IETF documents (e.g., Internet-Drafts) or URLs of those documents 374 are most commonly transmitted to ITU-T study groups as liaison 375 statements (see [2]), but exceptionally can be submitted to a study 376 group as a Contribution from ISOC. In order to ensure that the IETF 377 has properly authorized this, the IETF Working Group must agree that 378 the specific drafts are of mutual interest, that there is a benefit 379 in forwarding them to the ITU-T for review, comment and potential 380 use and that the document status is accurately represented in the 381 cover letter. Once agreed, the appropriate Area Directors would 382 review the Working Group request and give approval. The rules of 383 the IETF Trust are followed in these circumstances[3]. The 384 contributions would then be forwarded (with the noted approval) to 385 the TSB for circulation as a study group Contribution (see 2.2). 386 Note that material submitted to the ITU-T as an ISOC Contribution is 387 governed by Section 3.1.5 of Recommendation ITU-T A.1. Any such 388 contribution will be made only after receiving necessary approval of 389 owners of the work in question. In other circumstances, a liaison 390 statement may be appropriate. See RFC5378 and Recommendation ITU-T 391 A.1 for more information. 393 2.5.2. Contributions and Liaison Statements from the ITU-T to IETF 395 An ITU-T study group or working party may send texts of draft new or 396 revised Recommendations, clearly indicating their status, to the 397 IETF as contributions in the form of liaison statements or Internet- 398 Drafts. Internet-Drafts are IETF temporary documents that expire 399 six months after being published. The study group or working party 400 must decide that there is a benefit in forwarding them to the IETF 401 for review, comment and potential use. Terms of reference for 402 rapporteur group meetings may authorize rapporteur groups to send 403 working documents, in the form of Internet-Drafts, to the IETF. 405 If the study group or working party elects to transmit the text as 406 an Internet-Draft, the document editor would be instructed to 407 prepare the contribution in Internet-Draft format (in ASCII and 408 optionally postscript format as per [8]) and upload it via 409 https://datatracker.ietf.org/idst/upload.cgi. Material submitted as 410 an Internet-Draft or intended for inclusion in an Internet-Draft or 411 RFC is governed by the rules set forth in RFCs 5378, 3979, and 4879. 412 [3,4,5] Alternatively, the study group, working party or rapporteur 413 group could attach the text to a formal liaison statement. 415 Both the rapporteur and the document editor should be identified as 416 contacts in the contribution. The document should also clearly 417 indicate the state of development in a particular ITU-T study group. 418 Note that liaison statements and their attachments sent to the IETF 419 are made publicly available on the IETF web site. 421 2.5.3. ITU-T & IETF 423 It is envisaged that the processes of 2.5.1 & 2.5.2 will often be 424 used simultaneously by both an IETF Working Group and an ITU-T study 425 group to collaborate on a topic of mutual interest. 427 It is also envisaged that the outcome of the collaboration will be 428 the documentation in full by one body and its referencing by the 429 other (see section 2.4 for details). That is, common or joint text 430 is discouraged because of the current differences in procedures for 431 document approval and revision. Where complementary work is being 432 undertaken in both organizations that will result in Recommendations 433 or RFCs, due allowance should be given to the differing 434 perspectives, working methods, and procedures of the two 435 organizations. That is, each organization should understand the 436 other organization's procedures and strive to respect them in the 437 collaboration. 439 2.6. Simple Cross Referencing 441 Recommendation ITU-T A.5 describes the process for including 442 references to documents of other organizations in ITU-T 443 Recommendations. Recommendation ITU-T A.5 also addresses the sit uation where a study group 444 or working party decides to incorporate the text of another organization into the text of a 445 Recommendation, rather than referencing it . Information specific to referencing 446 IETF RFCs is found at http:// itu.int/dms_pub/itu- 447 t/oth/3E/01/T3E010000010001MSWE.doc. 449 RFC 2026, specifically section 6.1.1, describes the process for 450 referencing other open standards (like ITU-T Recommendations) in 451 IETF RFCs. 453 2.7. Preliminary Work Efforts 455 Both ITU-T and IETF provide mechanisms for early discussion of 456 potential new work areas prior to the official start of work in an 457 ITU-T study group or creation of an IETF Working Group. 459 Objectives, methods and procedures for the creation and operation of 460 ITU-T focus groups are defined in Recommendation ITU-T A.7. Focus 461 groups are frequently created in new work areas where there is a 462 need for deliverables to be produced on a specific topic within a 463 short timeframe. IETF participants who are not members or associates 464 of ITU-T may participate fully in the work of ITU-T focus groups if 465 they are from a country that is a member of ITU-T. 467 In the IETF, guidance for Birds Of a Feather (BoF) sessions is 468 provided in RFC 5434. Efforts that have not yet reached the Working 469 Group stage may be discussed in BOF sessions. These sessions 470 typically gauge interest in pursuing creation of Working Groups. In 471 some cases, these discussions continue on mailing lists. 473 2.8. Additional Items 475 2.8.1. IETF Information that may be of use to ITU-T participations 477 Information on IETF procedures may be found in the documents in the 478 informative references, and URLs below. Note that RFCs do not 479 change after they are published. Rather they are either obsoleted 480 or updated by other RFCs. Such updates are tracked in the rfc- 481 index.txt file. 483 Current list and status of all IETF RFCs: 484 ftp://ftp.ietf.org/rfc/rfc-index.txt 486 Current list and description of all IETF Internet-Drafts: 487 ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt 489 Current list of IETF Working Groups and their Charters: (includes 490 Area Directors and Chair contacts, Mailing list information, etc.) 491 http://www.ietf.org/dyn/wg/charter.html 493 Current list of registered BOFs 494 http://trac.tools.ietf.org/bof/trac/ 496 RFC Editor pages about publishing RFCs, including available tools 497 and lots of guidance: 498 http://www.rfc-editor.org/pubprocess.html 500 Current list of liaison statements: 501 https://datatracker.ietf.org/liaison/ 503 IETF Intellectual Property Rights Policy and Notices: 504 http://www.ietf.org/ipr/ 506 The Tao of the IETF - A Novice's Guide to the Internet Engineering 507 Task Force, http://www.ietf.org/tao.html 509 2.8.2. ITU-T Information that may be useful to IETF participants 511 Information about the ITU-T can be found in the informative 512 references and at the URLs below. 514 ITU-T Main page: http://itu.int/ITU-T 516 List of all ITU-T Recommendations: 517 http://itu.int/itu-t/recommendations/index.aspx 519 ITU-T Study Group main page for Study Group NN (where NN is the 2- 520 digit SG number): 521 http://itu.int/ITU-T/studygroups/comNN/index.asp 523 Intellectual Property policies, forms and databases: 524 http://itu.int/en/ITU-T/ipr/Pages/default.aspx 526 Current list of active ITU-T focus Groups 527 http://itu.int/en/ITU-T/focusgroups/Pages/default.aspx 529 ITU-T Procedures including: 530 Resolution 1 - Rules of Procedure for ITU-T 531 Resolution 2 - Study Group responsibility and mandates 532 http://itu.int/publ/T-RES/en 534 Authors Guide for drafting ITU-T Recommendations: 535 http://itu.int/dms_pub/itu-t/oth/0A/0F/T0A0F0000040003MSWE.docx 537 Templates for contributions and liaison statements: 538 http://itu.int/ITU-T/studygroups/templates/index.html 540 3. Security Considerations 542 Documents that describe cooperation procedures, like this one 543 does, have no direct Internet security implications. 545 4. IANA Considerations 547 No new IANA considerations. 549 5. Acknowledgements 551 This document is based on the text from RFCs 2436 and 3356 and 552 benefited greatly from discussions during the January 2012 ITU-T 553 Telecommunication Standardization Advisory Group (TSAG) meeting. 555 6. References 557 6.1. Normative References 559 [1] Daigle, L, Ed. "IAB Processes for Management of IETF Liaison 560 Relationships", RFC 4052, BCP 102, April 2005. 562 [2] Trowbridge, S, Bradner, S, and Baker, F, "Procedures for 563 Handling Liaison Statements to and from the IETF", RFC 4053, 564 BCP 103, April 2005. 566 [3] Bradner, J. Ed., Contreras, J., Ed., "Rights Contributors 567 Provide to the IETF Trust", RFC-5378, BCP 78, November, 2008. 569 [4] Bradner, S., Ed., "Intellectual Property Rights in IETF 570 Technology", RFC 3979, BCP 79, March 2005. 572 [5] Narten, T., "Clarifications of the Third Party Disclosure 573 Procedure in RFC 4879", BCP 79, April 2007. 575 [6] International Telecommunication Union, "Generic procedures for 576 including references to documents of other organizations in 577 ITU-T Recommendations", Recommendation ITU-T A.5, 2008. 579 6.2. Informative References 581 [7] Bradner. S, "The Internet Standards Process -- Revision 3", 582 BCP 9, RFC 2026, October 1996. 584 [8] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 585 2223, October 1997. 587 [9] Brett, R., Bradner, S. and G. Parsons, "Collaboration between 588 ISOC/IETF and ITU-T", RFC 2436, October 1998. 590 [10] Fishman, G. and Bradner, S., "Internet Engineering Task Force 591 and International Telecommunication Union - Telecommunications 592 Standardization Sector Collaboration Guidelines", RFC 3356, 593 August 2002. 595 [11] Hovey, R., Bradner, S., "The Organizations involved in the 596 IETF Standards Process, October 1996", RFC 2028, October, 597 1996. 599 [12] Bradner, S., "IETF Working Group Guidelines and Procedures", 600 RFC-2418, September 1998. 602 [13] Narten, T., "Considerations for Having a Successful Birds-of- 603 a-Feather (BOF) Session", RFC-5434, February 2009. 605 [14] Alvestrand, H., "A Mission Statement for the IETF", BCP-95 606 (also RFC-3935), October 2004. 608 [15] International Telecommunications Union, "Work Methods for 609 study groups of the ITU Telecommunication Standardization 610 Sector (ITU-T)", Recommendation ITU-T A.1, 2008. 612 [16] International Telecommunications Union, "Presentation of 613 Contributions to the ITU-T", Recommendation ITU-T A.2, 2008. 615 [17] International Telecommunications Union, "Focus groups: Working 616 methods and procedures", Recommendation ITU-T A.7, 2008. 618 [18] International Telecommunications Union, "Alternative approval 619 process for new and revised ITU-T Recommendations", 620 Recommendation ITU-T A.8, 2008. 622 7. Changes since RFC3356 624 The introduction has been integrated the scope section. 626 Additional information has been added about copyright and IPR 627 issues. 629 Authorization of liaison managers and liaison representatives from 630 IETF to ITU-T are updated per current IETF procedures documented in 631 [1]. 633 Transmission of formal liaison statements between ITU-T and IETF are 634 updated per current IETF procedures documented in [2]. 636 Description is added of preliminary efforts including ITU-T focus 637 groups and IETF BOFs. ITU-T focus group participation is not limited 638 to ITU-T members. 640 Obsolete URLs in RFC3356 from both the ITU-T and IETF web sites are 641 updated, more references have been moved to the References section. 643 8. Authors' Addresses 645 Steve Trowbridge 646 Alcatel-Lucent 647 5280 Centennial Trail 648 Boulder, CO 80303-1262 USA 650 Phone: +1 720 945 6885 651 Email: steve.trowbridge@alcatel-lucent.com 652 Eliot Lear 653 Cisco Systems GmbH 654 Richtistrasse 7 655 8304 Wallisellen 656 Switzerland 658 Phone: +41 44 878 9200 659 Email: lear@cisco.com 661 Gary Fishman 662 Pearlfisher International 663 12 Chestnut Drive 664 Matawan, NJ 07747 666 Phone: +1 732 778 9572 667 Email: gryfishman@aol.com 669 Scott Bradner 670 Harvard University 671 29 Oxford St. 672 Cambridge, MA 02138 674 Phone: +1 617 495 3864 675 Email: sob@harvard.edu