idnits 2.17.1 draft-iab-rfc3356bis-03.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 128 has weird spacing: '... topics of mu...' -- The document date (June 11, 2012) is 4336 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '6' is defined on line 579, but no explicit reference was found in the text == Unused Reference: '9' is defined on line 591, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 594, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 599, but no explicit reference was found in the text == Unused Reference: '12' is defined on line 603, but no explicit reference was found in the text == Unused Reference: '14' is defined on line 609, but no explicit reference was found in the text == Unused Reference: '16' is defined on line 616, but no explicit reference was found in the text == Unused Reference: '17' is defined on line 619, but no explicit reference was found in the text == Unused Reference: '18' is defined on line 622, 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: 2 errors (**), 0 flaws (~~), 11 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 11, 2012 11 Internet Engineering Task Force and International 12 Telecommunication Union - Telecommunication Standardization 13 Sector Collaboration Guidelines 15 draft-iab-rfc3356bis-03 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 normally 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 Liaison Statements from the IETF to 94 ITU-T.......................................................9 95 2.5.2. Contributions and Liaison Statements from the ITU-T to 96 IETF.......................................................10 97 2.5.3. ITU-T & IETF........................................10 98 2.6. Simple Cross Referencing.................................11 99 2.7. Preliminary Work Efforts.................................11 100 2.8. Additional Items.........................................11 101 2.8.1. IETF Information that may be of use to ITU-T 102 participations.............................................11 103 2.8.2. ITU-T Information that may be useful to IETF 104 participants...............................................12 105 3. Security Considerations.......................................13 106 4. IANA Considerations...........................................13 107 5. Acknowledgements..............................................13 108 6. References....................................................13 109 6.1. Normative References.....................................13 110 6.2. Informative References...................................14 111 7. Changes since RFC3356.........................................15 112 8. Authors' Addresses............................................15 114 [The following note to be removed upon publication as an RFC] 116 Editors' Note: 118 This Informational Internet-Draft is intended for publication as an 119 RFC with the IAB stream, and is subject to the publication process 120 described in RFC 4845. 122 1. Introduction & Scope 124 This document provides guidance to aid in the understanding of 125 collaboration on standards development between the International 126 Telecommunication Union - Telecommunication Standardization Sector 127 (ITU-T) and the Internet Society (ISOC) -- Internet Engineering Task 128 Force (IETF). Early identification of topics of mutual interest 129 will allow for constructive efforts between the two organizations. 131 In the IETF, work is done in working groups (WG), mostly through 132 open, public mailing lists rather than face-to-face meetings. 133 WGs are organized into Areas, each Area being managed by two co- 134 area directors. Collectively, the area directors comprise the 135 Internet Engineering Steering Group (IESG). 137 In the ITU-T, work is defined by study questions which are 138 worked on mostly through meetings led by rapporteurs (these are 139 sometimes called "Rapporteur's Group" meetings). Questions are 140 generally grouped within working parties (WPs) led by a WP 141 chairman. Working parties report to a parent study group (SG) 142 led by a SG chairman. Work may also be conducted in ITU-T focus 143 groups (see Section 2.5) 145 To foster ongoing communication between the ITU-T and IETF, it is 146 important to identify and establish contact points within each 147 organization. Contact points may include: 149 1. ITU-T Study Group Chair and IETF Area Director 151 An IETF area director is the individual responsible for 152 overseeing a major focus of activity with a scope similar to 153 that of an ITU-T study group chairman. These positions are 154 both relatively long-term (of several years) and offer the 155 stability of contact points between the two organizations for 156 a given topic. 158 2. ITU-T Rapporteur and IETF Working Group Chair 160 An IETF working group chair is an individual who is assigned 161 to lead the work on a specific task within one particular Area 162 with a scope similar to that of an ITU-T rapporteur. These 163 positions are working positions (of a year or more) that 164 typically end when the work on a specific topic ends. 165 Collaboration here is very beneficial to ensure the actual 166 work gets done. 168 3. Other Contact Points 170 It may be beneficial to establish additional contact points 171 for specific topics of mutual interest. These contact points 172 should be established early in the work effort, and in some 173 cases the contact point identified by each organization may be 174 the same individual. In addition, the ITU-T has an additional 175 level of management, the working party chair. From time to 176 time it may be beneficial for this person to exchange views 177 with IETF working group chairs and area directors. 179 Note that the current IETF area directors and working group 180 chairs can be found in the IETF working group charters. The 181 current ITU-T study group chairmen and rapporteurs are listed on 182 the ITU-T web page. 184 2. Guidance on Collaboration 186 This section describes how the existing processes within the IETF 187 and ITU-T may be utilized to enable collaboration between the 188 organizations. 190 2.1. How to Interact on ITU-T or IETF Work Items 192 Study groups that have identified work topics that are IP- 193 related should evaluate the relationship with topics defined in 194 the IETF. Current IETF working groups and their charters (IETF 195 definition of the scope of work) are listed in the IETF archives 196 (see Section 2.8.1). 198 A study group may decide that development of a Recommendation on 199 a particular topic may benefit from collaboration with the IETF. 200 The study group should identify this collaboration in its work 201 plan (specifically in that of each Question involved), 202 describing the goal of the collaboration and its expected 203 outcome. 205 An IETF working group should also evaluate and identify areas of 206 relationship with the ITU-T and document the collaboration with 207 the ITU-T study group in its charter. 209 The following sections outline a process that can be used to 210 enable each group to be informed about the other's new work 211 items. 213 2.1.1. How the ITU-T is informed about Existing IETF Work Items 215 The responsibility is on individual study groups to review the 216 current IETF working groups to determine if there are any topics of 217 mutual interest. Working group charters and active Internet-Drafts 218 can be found on the IETF web site (http://datatracker.ietf.org/wg/). 219 If a study group identifies a common area of work, the study group 220 leadership should contact both the IETF working group chair and the 221 area director(s) responsible. This may be accompanied by a formal 222 liaison statement (see 2.3). 224 2.1.2. How the IETF is informed about Existing ITU-T Work Items 226 The IETF through its representatives will review current work of 227 various study groups from time to time. Each ITU-T study group's 228 web pages on the ITU-T web site contain its current list of 229 Questions as well as its current work programme. When an area or 230 working group identifies a common area of work, the matter is 231 referred to appropriate working group chairs and area directors, 232 where they may consider sending a liaison statement to the 233 appropriate study group. 235 2.1.3. How the ITU-T is informed about proposed new IETF work items 237 The IETF maintains a mailing list for the distribution of proposed 238 new work items among standards development organizations. Many such 239 items can be identified in proposed Birds of a Feather (BoF) 240 sessions, as well as draft charters for working groups. The IETF 241 forwards all such draft charters for all new and revised working 242 groups and Birds Of a Feather session announcements to the IETF new- 243 work mailing list. An ITU-T mailing list is subscribed to this 244 list. Leadership of study groups may subscribe to this ITU-T mailing 245 list, which is maintained by the Telecommunication Standardization 246 Bureau (TSB). Members of the SG-specific listname may include the 247 SG chairman, SG vice-chairmen, working party chairmen, concerned 248 rapporteurs, other experts designated by the SG and the SG 249 Counsellor. This will enable the SGs to monitor the new work items 250 for possible overlap or interest to their study group. It is 251 expected that this mailing list will see a few messages per month. 253 Each SG chairman, or designated representative, may provide comments 254 on these charters by responding to the IESG mailing list at 255 iesg@ietf.org clearly indicating their ITU-T position and the nature 256 of their concern. Plain-text email is preferred on the IESG mailing 257 list. 259 It should be noted that the IETF turnaround time for new working 260 group charters is two weeks. As a result, the mailing list 261 should be consistently monitored. 263 2.1.4. How the IETF is informed about ITU-T Work Items 265 The ITU-T accepts new areas of work through the creation or update 266 of Questions and these can be found on the ITU-T Study Group web 267 pages. In addition, the ITU-T work programme is documented on each 268 ITU-T study group's web page on the ITU-T web site. 270 Study groups send updates to the IETF new-work mailing list as new 271 Questions are first drafted or created, terms of reference for 272 Questions are first drafted or updated, or otherwise when there is 273 reason to believe that a particular effort might be of interest to 274 the IETF. Area directors or WG chairs should provide comments 275 through liaison statements or direct email to the relevant SG 276 chairman in cases of possible overlap or interest. 278 2.2. Representation 280 ISOC, including its standards body IETF, is a Sector Member of the 281 ITU-T. As a result, ISOC delegates are therefore afforded the same 282 rights as other ITU-T Sector Members (see 2.2.1). Conversely, ITU-T 283 delegates may participate in the work of the IETF as representatives 284 of the ITU-T (see 2.2.2). To promote collaboration it is useful to 285 facilitate communication between the organizations as further 286 described below. 288 2.2.1. IETF Recognition at ITU-T 290 Experts and representatives from the IETF that are chosen by IETF 291 leadership normally participate in ITU-T meetings as ISOC delegates. 292 The ISOC focal point will facilitate registration and verification 293 of these people, as appropriate. 295 2.2.2. ITU-T Recognition at ISOC/IETF 297 ITU-T study group chairmen can authorize one or more members to 298 attend an IETF meeting as an official ITU-T delegate speaking 299 authoritatively on behalf of the activities of the study group (or a 300 particular rapporteur group). The study group chairman sends the 301 ITU-T list of delegates by email to the working group chair, with a 302 copy to the area directors, and also to the study group. Note that, 303 according to IETF process, opinions expressed by any such delegate 304 are given equal weight with opinions expressed by any other working 305 group participant. 307 2.3. Communication outside of Meetings 309 Informal communication between contact points and experts of both 310 organizations is encouraged. However, note that formal 311 communication from an ITU-T study group, working party or rapporteur 312 group to an associated IETF contact point must be explicitly 313 approved and identified as coming from the study group, working 314 party or rapporteur group, respectively. Formal liaison statements 315 from the ITU-T to the IETF are transmitted according to the 316 procedures described in [2]. These liaison statements are placed by 317 the IETF onto a liaison statements web page at 318 https://datatracker.ietf.org/liaison/. An individual at the IETF is 319 assigned responsibility for dealing with each liaison statement that 320 is received. The name and contact information of the responsible 321 person and any applicable deadline is listed with the links to the 322 liaison statement on this web page. 324 Formal liaison statements from the IAB, the IESG, the IETF, an IETF 325 working group or Area to the ITU-T are generated, approved, and 326 transmitted according to the procedures described in [2] and [15]. 327 Formal communication is intended to allow the sharing of positions 328 between the IETF and the ITU-T outside of actual documents (as 329 described in 2.5.1). This covers such things as comments on 330 documents and requests for input. 332 2.4. Mailing Lists 334 All IETF working groups and all ITU-T study group Questions have 335 associated mailing lists. 337 In the IETF, the mailing list is the primary vehicle for discussion 338 and decision-making. It is recommended that the ITU-T experts 339 interested in particular IETF working group topics subscribe to and 340 participate in these lists. IETF WG mailing lists are open to all 341 subscribers. The IETF working group mailing list subscription and 342 archive information are noted in each working group's charter. In 343 the ITU-T, the TSB has set up formal mailing lists for Questions, 344 working parties and other topics within study groups (more detail 345 can be found on the ITU-T website). These mailing lists are 346 typically used for ITU-T correspondence, including technical 347 discussion, meeting logistics, reports, etc. Note that individual 348 subscribers to this list must be affiliated with an ITU-T member or 349 associate (at this time, there is no blanket inclusion of all IETF 350 participants as members, however, as a member, the ISOC focal point 351 can facilitate access by IETF technical experts, liaison 352 representatives, or liaison managers). IETF participants may 353 subscribe to ITU-T focus group email lists if they are from a 354 country that is a member of ITU-T. 356 2.5. Document Sharing 358 During the course of ITU-T and IETF collaboration it is important to 359 share working drafts and documents among the technical working 360 groups. Initially proposed concepts and specifications typically 361 can be circulated by email (often just repeating the concept and not 362 including the details of the specification) on both the IETF and 363 ITU-T mailing lists. In addition, working texts (or URLs) of draft 364 Recommendations, Internet-Drafts or RFCs may also be sent between 365 the organizations as described below. 367 Internet-Drafts are available on the IETF web site. The ITU-T can 368 make selected ITU-T documents at any stage of development available 369 to IETF by attaching them to a formal liaison statement. Although a 370 communication can point to a URL where a non-ASCII document (e.g., 371 Word) can be downloaded, attachments in proprietary formats to an 372 IETF mailing list are discouraged. It should also be recognized 373 that the official versions of all IETF documents are in ASCII. 375 2.5.1. Contributions and Liaison Statements from the IETF to ITU-T 377 IETF documents (e.g., Internet-Drafts) or URLs of those documents 378 are most commonly transmitted to ITU-T study groups as liaison 379 statements (see [2]), but exceptionally can be submitted to a study 380 group as a Contribution from ISOC. In order to ensure that the IETF 381 has properly authorized this, the IETF working group must agree that 382 the specific drafts are of mutual interest, that there is a benefit 383 in forwarding them to the ITU-T for review, comment and potential 384 use and that the document status is accurately represented in the 385 cover letter. Once agreed, the appropriate area directors would 386 review the working group request and give approval. The rules of 387 the IETF Trust are followed in these circumstances[3]. The 388 contributions would then be forwarded (with the noted approval) to 389 the TSB for circulation as a study group Contribution (see 2.2). 390 Note that material submitted to the ITU-T as an ISOC Contribution is 391 governed by Section 3.1.5 of Recommendation ITU-T A.1. Any such 392 contribution will be made only after receiving necessary approval of 393 owners of the work in question. In other circumstances, a liaison 394 statement may be appropriate. See RFC 5378 and Recommendation ITU-T 395 A.1 for more information.[3, 15] 397 2.5.2. Contributions and Liaison Statements from the ITU-T to IETF 399 An ITU-T study group or working party may send texts of draft new or 400 revised Recommendations, clearly indicating their status, to the 401 IETF as contributions in the form of liaison statements or Internet- 402 Drafts. Internet-Drafts are IETF temporary documents that expire 403 six months after being published. The study group or working party 404 must decide that there is a benefit in forwarding them to the IETF 405 for review, comment and potential use. Terms of reference for 406 rapporteur group meetings may authorize rapporteur groups to send 407 working documents, in the form of Internet-Drafts, to the IETF. 409 If the study group or working party elects to transmit the text as 410 an Internet-Draft, the document editor would be instructed to 411 prepare the contribution in Internet-Draft format (in ASCII and 412 optionally postscript format as per [8]) and upload it via 413 https://datatracker.ietf.org/idst/upload.cgi. Material submitted as 414 an Internet-Draft or intended for inclusion in an Internet-Draft or 415 RFC is governed by the rules set forth in RFCs 5378, 3979, and 4879. 416 [4,5] Alternatively, the study group, working party or rapporteur 417 group could attach the text to a formal liaison statement. 419 Both the rapporteur and the document editor should be identified as 420 contacts in the contribution. The document should also clearly 421 indicate the state of development in a particular ITU-T study group. 422 Note that liaison statements and their attachments sent to the IETF 423 are made publicly available on the IETF web site. 425 2.5.3. ITU-T & IETF 427 It is envisaged that the processes of 2.5.1 & 2.5.2 will often be 428 used simultaneously by both an IETF working group and an ITU-T study 429 group to collaborate on a topic of mutual interest. 431 It is also envisaged that the outcome of the collaboration will be 432 the documentation in full by one body and its referencing by the 433 other (see section 2.4 for details). That is, common or joint text 434 is discouraged because of the current differences in procedures for 435 document approval and revision. Where complementary work is being 436 undertaken in both organizations that will result in Recommendations 437 or RFCs, due allowance should be given to the differing 438 perspectives, working methods, and procedures of the two 439 organizations. That is, each organization should understand the 440 other organization's procedures and strive to respect them in the 441 collaboration. 443 2.6. Simple Cross Referencing 445 Recommendation ITU-T A.5 describes the process for including 446 references to documents of other organizations in ITU-T 447 Recommendations. Recommendation ITU-T A.5 also addresses the 448 situation where a study group or working party decides to 449 incorporate the text of another organization into the text of a 450 Recommendation, rather than referencing it. Information specific to 451 referencing IETF RFCs is found at http://itu.int/ITU-T/go/ref-ietf- 452 isoc. 454 RFC 2026 Section 6.1.1, describes the process for referencing other 455 open standards (like ITU-T Recommendations) in IETF RFCs.[7] 457 2.7. Preliminary Work Efforts 459 Both ITU-T and IETF provide mechanisms for early discussion of 460 potential new work areas prior to the official start of work in an 461 ITU-T study group or creation of an IETF working group. 463 Objectives, methods and procedures for the creation and operation of 464 ITU-T focus groups are defined in Recommendation ITU-T A.7. Focus 465 groups are frequently created in new work areas where there is a 466 need for deliverables to be produced on a specific topic within a 467 short timeframe. IETF participants who are not members or associates 468 of ITU-T may participate fully in the work of ITU-T focus groups if 469 they are from a country that is a member of ITU-T. 471 In the IETF, guidance for Birds Of a Feather (BoF) sessions is 472 provided in RFC 5434. Efforts that have not yet reached the working 473 group stage may be discussed in BOF sessions.[13] These sessions 474 typically gauge interest in pursuing creation of working groups. In 475 some cases, these discussions continue on mailing lists. 477 2.8. Additional Items 479 2.8.1. IETF Information that may be of use to ITU-T participations 481 Information on IETF procedures may be found in the documents in the 482 informative references, and URLs below. Note that RFCs do not 483 change after they are published. Rather they are either obsoleted 484 or updated by other RFCs. Such updates are tracked in the rfc- 485 index.txt file. 487 Current list and status of all IETF RFCs: 488 ftp://ftp.ietf.org/rfc/rfc-index.txt 490 Current list and description of all IETF Internet-Drafts: 491 ftp://ftp.ietf.org/internet-drafts/1id-abstracts.txt 493 Current list of IETF working groups and their Charters: (includes 494 area directors and chair contacts, mailing list information, etc.) 495 http://www.ietf.org/dyn/wg/charter.html 497 Current list of registered BOFs 498 http://trac.tools.ietf.org/bof/trac/ 500 RFC Editor pages about publishing RFCs, including available tools 501 and lots of guidance: 502 http://www.rfc-editor.org/pubprocess.html 504 Current list of liaison statements: 505 https://datatracker.ietf.org/liaison/ 507 IETF Intellectual Property Rights Policy and Notices: 508 http://www.ietf.org/ipr/ 510 The Tao of the IETF - A Novice's Guide to the Internet Engineering 511 Task Force, http://www.ietf.org/tao.html 513 2.8.2. ITU-T Information that may be useful to IETF participants 515 Information about the ITU-T can be found in the informative 516 references and at the URLs below. 518 ITU-T Main page: http://itu.int/ITU-T 520 List of all ITU-T Recommendations: 521 http://itu.int/itu-t/recommendations/index.aspx 523 ITU-T Study Group main page for Study Group NN (where NN is the 2- 524 digit SG number): 525 http://itu.int/ITU-T/studygroups/comNN/index.asp 527 Intellectual Property policies, forms and databases: 528 http://itu.int/en/ITU-T/ipr/Pages/default.aspx 530 Current list of active ITU-T focus Groups 531 http://itu.int/en/ITU-T/focusgroups/Pages/default.aspx 533 ITU-T Procedures including: 534 Resolution 1 - Rules of Procedure for ITU-T 535 Resolution 2 - Study Group responsibility and mandates 536 http://itu.int/publ/T-RES/en 538 Authors Guide for drafting ITU-T Recommendations: 539 http://itu.int/ITU-T/go/author-guide 541 Templates for contributions and liaison statements: 542 http://itu.int/ITU-T/studygroups/templates/index.html 544 3. Security Considerations 546 Documents that describe cooperation procedures, like this one 547 does, have no direct Internet security implications. 549 4. IANA Considerations 551 No new IANA considerations. 553 5. Acknowledgements 555 This document is based on the text from RFCs 2436 and 3356 and 556 benefited greatly from discussions during the January 2012 ITU-T 557 Telecommunication Standardization Advisory Group (TSAG) meeting. 559 6. References 561 6.1. Normative References 563 [1] Daigle, L, Ed. "IAB Processes for Management of IETF Liaison 564 Relationships", RFC 4052, BCP 102, April 2005. 566 [2] Trowbridge, S, Bradner, S, and Baker, F, "Procedures for 567 Handling Liaison Statements to and from the IETF", RFC 4053, 568 BCP 103, April 2005. 570 [3] Bradner, J. Ed., Contreras, J., Ed., "Rights Contributors 571 Provide to the IETF Trust", RFC 5378, BCP 78, November, 2008. 573 [4] Bradner, S., Ed., "Intellectual Property Rights in IETF 574 Technology", RFC 3979, BCP 79, March 2005. 576 [5] Narten, T., "Clarifications of the Third Party Disclosure 577 Procedure in RFC 4879", BCP 79, April 2007. 579 [6] International Telecommunication Union, "Generic procedures for 580 including references to documents of other organizations in 581 ITU-T Recommendations", Recommendation ITU-T A.5, 2008. 583 6.2. Informative References 585 [7] Bradner. S, "The Internet Standards Process -- Revision 3", 586 BCP 9, RFC 2026, October 1996. 588 [8] Postel, J. and J. Reynolds, "Instructions to RFC Authors", RFC 589 2223, October 1997. 591 [9] Brett, R., Bradner, S. and G. Parsons, "Collaboration between 592 ISOC/IETF and ITU-T", RFC 2436, October 1998. 594 [10] Fishman, G. and Bradner, S., "Internet Engineering Task Force 595 and International Telecommunication Union - Telecommunications 596 Standardization Sector Collaboration Guidelines", RFC 3356, 597 August 2002. 599 [11] Hovey, R., Bradner, S., "The Organizations involved in the 600 IETF Standards Process, October 1996", RFC 2028, October, 601 1996. 603 [12] Bradner, S., "IETF Working Group Guidelines and Procedures", 604 RFC-2418, September 1998. 606 [13] Narten, T., "Considerations for Having a Successful Birds-of- 607 a-Feather (BOF) Session", RFC 5434, February 2009. 609 [14] Alvestrand, H., "A Mission Statement for the IETF", BCP 95 610 (also RFC 3935), October 2004. 612 [15] International Telecommunications Union, "Work Methods for 613 study groups of the ITU Telecommunication Standardization 614 Sector (ITU-T)", Recommendation ITU-T A.1, 2008. 616 [16] International Telecommunications Union, "Presentation of 617 Contributions to the ITU-T", Recommendation ITU-T A.2, 2008. 619 [17] International Telecommunications Union, "Focus groups: Working 620 methods and procedures", Recommendation ITU-T A.7, 2008. 622 [18] International Telecommunications Union, "Alternative approval 623 process for new and revised ITU-T Recommendations", 624 Recommendation ITU-T A.8, 2008. 626 7. Changes since RFC3356 628 The introduction has been integrated the scope section. 630 Additional information has been added about copyright and IPR 631 issues. 633 Authorization of liaison managers and liaison representatives from 634 IETF to ITU-T are updated per current IETF procedures documented in 635 [1]. 637 Transmission of formal liaison statements between ITU-T and IETF are 638 updated per current IETF procedures documented in [2]. 640 Description is added of preliminary efforts including ITU-T focus 641 groups and IETF BOFs. ITU-T focus group participation is not limited 642 to ITU-T members. 644 Obsolete URLs in RFC3356 from both the ITU-T and IETF web sites are 645 updated, more references have been moved to the References section. 647 8. Authors' Addresses 649 Steve Trowbridge 650 Alcatel-Lucent 651 5280 Centennial Trail 652 Boulder, CO 80303-1262 USA 654 Phone: +1 720 945 6885 655 Email: steve.trowbridge@alcatel-lucent.com 656 Eliot Lear 657 Cisco Systems GmbH 658 Richtistrasse 7 659 8304 Wallisellen 660 Switzerland 662 Phone: +41 44 878 9200 663 Email: lear@cisco.com 665 Gary Fishman 666 Pearlfisher International 667 12 Chestnut Drive 668 Matawan, NJ 07747 670 Phone: +1 732 778 9572 671 Email: gryfishman@aol.com 673 Scott Bradner 674 Harvard University 675 29 Oxford St. 676 Cambridge, MA 02138 678 Phone: +1 617 495 3864 679 Email: sob@harvard.edu