idnits 2.17.1 draft-iab-liaison-mgt-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 26, 2003) is 7456 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group L. Daigle 2 Internet-Draft Editor 3 Expires: May 26, 2004 Internet Architecture Board 4 IAB 5 November 26, 2003 7 IAB Processes for management of liaison relationships 8 draft-iab-liaison-mgt-00 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on May 26, 2004. 33 Copyright Notice 35 Copyright (C) The Internet Society (2003). All Rights Reserved. 37 Abstract 39 This document discusses the procedures the IAB uses to select 40 organizations to form and maintain liaison relationships with. It 41 further discusses the expectations that the IAB has of such 42 organizations and of the people assigned to manage those 43 relationships. 45 Table of Contents 47 1. Liaison Relationships and Personnel . . . . . . . . . . . . . 3 48 2. Aspects of Liaisons and Liaison Management . . . . . . . . . . 4 49 2.1 Liaison Relationships . . . . . . . . . . . . . . . . . . . . 4 50 2.2 Liaison Manager . . . . . . . . . . . . . . . . . . . . . . . 4 51 2.3 Liaison Communications . . . . . . . . . . . . . . . . . . . . 5 52 3. Summary of IETF Liaison Role Expectations . . . . . . . . . . 6 53 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 54 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 8 55 References . . . . . . . . . . . . . . . . . . . . . . . . . . 9 56 References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 57 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 10 58 Full Copyright Statement . . . . . . . . . . . . . . . . . . . 11 60 1. Liaison Relationships and Personnel 62 The IETF, as an organization, has the need to engage in joint 63 endeavors with various other formal organizations. For example, as 64 the IETF is one of many Standards Development Organizations, or SDOs. 65 Increasingly, SDOs find it necessary to communicate and coordinate 66 their activities involving Internet-related technologies, to avoid 67 overlaps and to manage interactions between their groups. They do 68 this in many ways: they send people to each other's meetings, they 69 exchange email and more formal notes call "liaison statements", and 70 they hold formal meetings. These relationships are generically 71 referred to as liaison relationships. Often, a person is designated 72 to manage a "liaison relationship"; that person is generally called 73 the "IETF liaison" to that organization. 75 The IETF has chartered the Internet Architecture Board to manage 76 liaison relationships. In its charter [2], the IAB states that 78 The IAB acts as representative of the interests of the IETF and 79 the Internet Society in technical liaison relationships with other 80 organizations concerned with standards and other technical and 81 organizational issues relevant to the world-wide Internet. 82 Liaisons are kept as informal as possible and must be of 83 demonstrable value in improving the quality of IETF 84 specifications. Individual members of the IETF are appointed as 85 liaisons to other organizations by the IAB or IESG as appropriate. 87 2. Aspects of Liaisons and Liaison Management 89 2.1 Liaison Relationships 91 A liaison relationship is set up when it is mutually agreeable and 92 needed, in the view of the other organization, the IAB, and the IETF 93 participants conducting the work. There is no set process or form 94 for this; the IETF participants and the peer organization approach 95 the IAB, and after discussion come to an agreement to form the 96 relationship. 98 The IAB's expectation in setting up the relationship is that there 99 will be a mutual exchange of views, resulting in documents developed 100 in both organizations. If the peer organization wants the IETF to 101 adopt a document, someone from that organization may propose and 102 Internet-Draft following the usual procedures, or an IETF participant 103 may do so. Such work will be accomplished in an IETF working group 104 in the usual manner, chartered and managed by the IESG according to 105 IETF procedures [1]. The peer organization often has different 106 organizational structure and different procedures than the IETF, 107 which will require some flexibility on the part of both organizations 108 to accommodate. The IAB expects that the peer organization will use 109 the relationship carefully, allowing time for the processes it 110 requests to occur and not making unreasonable demands. 112 2.2 Liaison Manager 114 As described above, most work on mutually interesting topics will be 115 carried out in the usual way within the IETF and the peer 116 organization. Therefore, most communications will be informal in 117 nature (e.g., working group, mailing list discussions, etc). 119 From time to time, it may be important for the peer organization to 120 send a more formal communication, making a request or declaring an 121 official position.To ensure that communications are smooth and the 122 results proper, the IAB requests that any such formal email or 123 liaison statement to an IETF organization, the following be copied: 124 statements@ietf.org, the appropriate working group, the IAB- 125 designated liaison manager, and the relevant area directors. The 126 email will generally be addressed to the area director, if the matter 127 is larger than a single working group, or the working group chair. 129 The function of the liaison manager, or "liaison", is to ensure that 130 communication is maintained, is productive, and is timely. He or she 131 may use any businesslike approach to that necessary, from private 132 communications to public communications, and bringing in other 133 parties as needed. If a communication from a peer organization is 134 addressed to an inappropriate party, such as being sent to the 135 working group but not copying the AD or being sent to the wrong 136 working group, the liaison manager should redirect or otherwise 137 augment the communication. 139 Since the IAB is ultimately responsible for liaison relationships, 140 anyone who has a problem with one (whether an IETF participant or a 141 person from the peer organization) should first consult the IAB's 142 designated liaison relationship manager, and if that does not result 143 in a satisfactory outcome, the IAB itself. 145 2.3 Liaison Communications 147 Communications between organizationns use a variety of formal and 148 informal channels. The stated preference of the IETF, which is 149 largely an informal organization, is to use informal channels, as 150 these have historically worked well to expedite matters. In some 151 cases, however, more formal communications are appropriate. In such 152 cases, the established procedures of many organizations use a form 153 known as a "liaison statement". Procedures for sending, managing, 154 and responding to liaison statements are discussed in draft-baker- 155 liaisons. 157 3. Summary of IETF Liaison Role Expectations 159 While the requirements will certainly vary depending on the nature of 160 the peer organization and the type of joint work being undertaken, 161 the general expectations of a liaison appointed by the IAB are as 162 follows: 164 Attend relevant meetings of the peer organization and report back 165 to the appopriate IETF organization any material updates. 167 Carry any messages from the IETF to the peer organization, when 168 specifically instructed (in this case, the message does "represent 169 the IETF"). 171 Prepare occasional updates -- e.g., to the IAB, an AD, a WG. The 172 target of these updates will generally be identified upon 173 appointment. 175 Ensure that any liaison statement addressed to the IETF reaches 176 the appropriate destination within the IETF, and work to ensure 177 that whatever relevant response from the IETF is created and sent 178 in a timely fashion. 180 4. Security Considerations 182 The security of the Internet is not threatened by these procedures. 184 5. Acknowledgements 186 This document was developed as part of a conversation regarding the 187 management of draft-baker-liaisons, and the authors of that document 188 contributed significantly to it. 190 Normative References 192 [1] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 193 9, RFC 2026, October 1996. 195 [2] Internet Architecture Board and B. Carpenter, "Charter of the 196 Internet Architecture Board (IAB)", BCP 39, RFC 2850, May 2000. 198 Informative References 200 Authors' Addresses 202 Leslie Daigle 203 Editor 205 Internet Architecture Board 206 IAB 208 EMail: iab@iab.org 210 Full Copyright Statement 212 Copyright (C) The Internet Society (2003). All Rights Reserved. 214 This document and translations of it may be copied and furnished to 215 others, and derivative works that comment on or otherwise explain it 216 or assist in its implementation may be prepared, copied, published 217 and distributed, in whole or in part, without restriction of any 218 kind, provided that the above copyright notice and this paragraph are 219 included on all such copies and derivative works. However, this 220 document itself may not be modified in any way, such as by removing 221 the copyright notice or references to the Internet Society or other 222 Internet organizations, except as needed for the purpose of 223 developing Internet standards in which case the procedures for 224 copyrights defined in the Internet Standards process must be 225 followed, or as required to translate it into languages other than 226 English. 228 The limited permissions granted above are perpetual and will not be 229 revoked by the Internet Society or its successors or assigns. 231 This document and the information contained herein is provided on an 232 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 233 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 234 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 235 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 236 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 238 Acknowledgement 240 Funding for the RFC Editor function is currently provided by the 241 Internet Society.