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