idnits 2.17.1 draft-secretaries-good-practices-07.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 -- The document date (November 11, 2014) is 3451 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 3979 (ref. '2') (Obsoleted by RFC 8179) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group M. Vigoureux 2 Internet Draft Alcatel-Lucent 3 Intended status: Informational D. King 4 Expires: May 2015 Old Dog Consulting 5 C. Pignataro 6 Cisco Systems, Inc. 8 November 11, 2014 10 IETF Working Groups' Secretaries 11 draft-secretaries-good-practices-07 13 Abstract 15 The Working Group Secretary's role was succinctly defined in RFC 16 2418. However, this role has greatly evolved and increased both in 17 value and scope, since the writing of RFC 2418. This document thus 18 provides a compilation of good practices and general guidelines 19 regarding the fulfilment of the role. 21 This document is intended for established Working Group Secretaries, 22 individuals motivated by taking up that role, or anyone else simply 23 interested in understanding better the Working Group Secretary's 24 role. This document may also be useful for Working Group Chairs to 25 better appreciate and help develop the value of Working Group 26 Secretaries. 28 Status of this Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF), its areas, and its working groups. Note that other 35 groups may also distribute working documents as Internet-Drafts. 37 Internet-Drafts are draft documents valid for a maximum of six months 38 and may be updated, replaced, or obsoleted by other documents at any 39 time. It is inappropriate to use Internet-Drafts as reference 40 material or to cite them other than as "work in progress". 42 The list of current Internet-Drafts can be accessed at 43 http://www.ietf.org/ietf/1id-abstracts.txt 45 The list of Internet-Draft Shadow Directories can be accessed at 46 http://www.ietf.org/shadow.html 48 This Internet-Draft will expire on May 11, 2015. 50 Copyright Notice 52 Copyright (c) 2014 IETF Trust and the persons identified as the 53 document authors. All rights reserved. 55 This document is subject to BCP 78 and the IETF Trust's Legal 56 Provisions Relating to IETF Documents 57 (http://trustee.ietf.org/license-info) in effect on the date of 58 publication of this document. Please review these documents 59 carefully, as they describe your rights and restrictions with respect 60 to this document. 62 Table of Contents 64 1. Introduction...................................................2 65 2. Applicability Statement........................................3 66 3. WG Secretary's Functions and Responsibilities..................4 67 3.1. IETF Meeting Specific Tasks...............................4 68 3.1.1. Pre WG Session Phase.................................4 69 3.1.2. WG Session Phase.....................................7 70 3.1.3. Post WG Session Phase................................8 71 3.2. Continuous Tasks..........................................8 72 4. Complementary Considerations..................................10 73 5. Conclusions and Perspectives..................................11 74 6. Security Considerations.......................................12 75 7. IANA Considerations...........................................13 76 8. References....................................................13 77 8.1. Informative References...................................13 78 9. Acknowledgments...............................................13 79 Contributors' Addresses..........................................14 80 Authors' Addresses...............................................15 82 1. Introduction 84 The Working Group (WG) Secretary's role was defined as a minute taker 85 and to record WG discussions' points, and decisions (see section 6.2 86 of RFC 2418 [1]). Over time, the WG Secretary's role has greatly 87 evolved to include a number of additional delegated functions and 88 responsibilities which are critical to the smooth operation of IETF 89 WGs. This document describes these additional functions and 90 responsibilities. 92 In that context, it shall be noted that a certain number of tools and 93 means exist in support of WG operation (e.g., Session Request Tool, 94 Meeting Materials Manager, the Datatracker, Etherpad, Trac Tool, 95 Wiki). Most, if not all, of these are accessible from the WG Chairs' 96 page (https://www.ietf.org/wg/chairs-page.html). It is however 97 outside of the scope of this document to describe the use of these 98 tools and means. It shall also be noted that no specific tool exists 99 in support of certain actions and tasks that can fall under the 100 responsibility of a WG Secretary. It is expected that a WG Secretary 101 would procure the right set of tools for the job, based on 102 availability and personal preference. This might entail searching and 103 finding, or developing, tools. 105 Section 2 of this document sets out its scope of applicability. 106 Section 3 of this document gives detailed descriptive information of 107 the WG Secretary's functions, responsibilities, and good practices. 108 Section 4 provides a complementary set of information. 110 It is expected that upon publication, the content of this document 111 will be transferred to the Working Groups Chairs' wiki, or this 112 document be referenced there. 114 2. Applicability Statement 116 The WG Secretary is a resource that can be leveraged by WG Chairs, 117 and is concerned with supporting the operations of a WG to make 118 forward progress, and with assisting in managing the WG processes. WG 119 Chairs hold the responsibility for the decisions and actions taken at 120 the level of their WG. However, WG Chairs can delegate punctually or 121 durably any of their responsibilities to someone else. In essence, 122 this document therefore lists a subset of WG Chairs' functions and 123 responsibilities which can typically be delegated to a WG Secretary. 125 The framework and perimeter of action associated to the WG 126 Secretary's role, depends on the WG Secretary and the Chairs, as well 127 as on the professional relationship they establish. Therefore this 128 document does not prescribe what must be performed, but lists what 129 might be performed by a WG Secretary. Also, this list is intended to 130 be as complete as possible, but it shall not be considered as 131 exhaustive. This document is therefore not a rigid job description. 133 Also, IETF WGs differ from one another according several aspects. 134 Amongst those aspects is the "effective size" of the WG (number of 135 active participants, number of active documents, rate of WG 136 document's adoption calls and WG Last Calls, and mailing list 137 traffic). In that regard, part or even all of the guidelines provided 138 in this document might not be relevant for the successful operation 139 of smaller WGs. In those, the Chairs may not need to delegate 140 operational tasks. 142 In fact, the appointment of a WG Secretary is a matter concerning the 143 WG. As such it is fully up to the WG Chairs to decide whether or not 144 they wish to appoint a Secretary, to decide who to appoint as 145 Secretary and to decide which responsibilities to delegate to that 146 Secretary. Area Directors may nonetheless provide useful advice. 148 3. WG Secretary's Functions and Responsibilities 150 The WG Secretary supports the processes and workflows to make the WG 151 successful during its lifetime, with specific actions at the times of 152 IETF meetings. We thus classify the functions and responsibilities of 153 a WG Secretary according to IETF meeting specific tasks, and to 154 continuous tasks. The following sub-sections reflect that 155 classification. 157 3.1. IETF Meeting Specific Tasks 159 The set of tasks specific to an IETF meeting can be further sub- 160 classified into three phases: the WG session held during that meeting 161 as well as both the pre and post phases of that session. 163 3.1.1. Pre WG Session Phase 165 o Submitting a request for a WG session 167 Using the means available, the WG Secretary could submit a request 168 for a WG session at the upcoming IETF meeting. The WG Secretary 169 should coordinate with the Chairs in order to correctly formulate the 170 request, especially with regards to the number of sessions to request 171 for and their respective duration. As part of this request, care 172 should also be taken to specify precise conflicts lists (WGs and 173 individuals). Concomitantly, the WG Secretary could formulate the 174 request to have collaborative software (e.g., WebEx, Meetecho) 175 support during the WG session. It shall be noted that holding a WG 176 session is typically driven by the need for the WG to discuss some 177 topics or documents, and that the identification of this need may 178 imply having interactions with the WG before requesting a session. 180 o Calling for discussion slots 182 Working Group Chairs may organise WG sessions in different ways. As 183 part of this organisation, they may allocate all or part of the WG 184 session to people wishing to discuss their work (e.g., with the 185 objective to resolve issues and make progress). In that context, and 186 as soon as the IETF agenda for a given meeting is published, the WG 187 Secretary could send an e-mail to the WG mailing list asking the WG 188 participants to submit requests for discussion slots at the upcoming 189 WG session. Note that WG Chairs may wish that certain conditions be 190 met to accept discussion's slot requests. The call for discussion 191 slots should remind the WG of these conditions as well as how should 192 the requests be formulated, together with a deadline for sending 193 them. The call would also typically include information on when will 194 the particular WG session be held during the IETF meeting noting that 195 the IETF agenda is draft until being final. 197 o Collecting the discussion's slot requests 199 As a preliminary step to building the WG session agenda, the WG 200 Secretary could collect all the requests for discussion slots. In 201 order to be able to do so, the WG Secretary should make sure that 202 he/she is aware of the formulated requests by clearly indicating in 203 the call for discussion slots that he/she must be one of the 204 recipients of the requests. It may nevertheless happen that some 205 requests are sent to the WG Chairs only. To cover that situation, the 206 WG Secretary should coordinate with the Chairs to make sure the final 207 list of requests for discussion slots is complete. 209 o Proposing a WG session agenda 211 Based on the collected discussion's slot requests, and depending on 212 the known preferences of the WG Chairs for the typical structure of 213 their WG sessions, or on the objectives Chairs have for a particular 214 WG session, and/or on his/her personal view, the Secretary could 215 propose to the Chairs a structured agenda for the upcoming WG 216 session. Following that, the WG Secretary could work with the Chairs 217 to finalise the agenda in view of publishing a first draft agenda. 219 o Submitting the WG session agenda 220 At the deadline, or even earlier, the WG Secretary could publish the 221 draft and then final agenda for the WG session. The WG Secretary 222 could then inform the WG that the agenda has been published. When 223 doing so, the WG Secretary could ask the WG participants to verify 224 that discussion's slot requests have not been accidentally missed. 225 Also, in the case where some requests have not been granted, the WG 226 Secretary could inform the participants who requested the discussion 227 slots, of the reason(s) why they were not allocated a slot in the 228 final WG session agenda. 230 o Requesting presentations materials 232 In combination with the notification of the publication of the WG 233 session agenda, or separately, the WG Secretary could ask the 234 individuals who were granted a discussion slot to send the material 235 in support of their upcoming presentation. This request should come 236 with a deadline so as to give sufficient time to upload the materials 237 before the WG session. 239 Optionally the request could also include information on the practice 240 the WG Chairs apply if the materials fail to be delivered prior to 241 the deadline. 243 o Securing Jabber relays and minute takers 245 Supporting remote participation is very important. As such, the WG 246 Secretary could ask for one specific volunteer: a Jabber scribe, 247 responsible for acting as a gateway for remote participants, by way 248 of relaying remote questions and annotating slide numbers. Also, it 249 is crucial that discussions' points and decisions be written down. 250 The WG Secretary could make sure that minutes will be taken. The WG 251 Secretary may self-designate and/or find at least one other volunteer 252 tasked with taking notes during the WG session. Securing these two 253 roles in advance sets up for a successful meeting. 255 For the purpose of minutes taking, the WG Secretary may suggest the 256 use of the Etherpad tool (available from each WG web page at 257 https://tools.ietf.org) which enables the other WG participants to 258 also contribute, as well as provides immediate access to the minutes. 260 o Preparing the WG Status material 262 Working Groups sessions typically start with a slot allocated to the 263 Chairs during which is presented a status of the WG. The WG Secretary 264 could produce part, or the totality, of the WG status slides by 265 compiling the appropriate information. As part of this step, the WG 266 Secretary could query the authors of WG documents to know the status 267 of -and the plans they have for- their document (e.g., envisaged date 268 of readiness for WG Last Call). This, mostly if not only, applies to 269 WG documents the state of which is not evident. For example there is 270 no apparent need to query authors of a WG document which is in IESG 271 processing. 273 o Uploading the materials 275 The WG Secretary could, sufficiently ahead of time, upload the 276 presentations materials. This is useful both to the WG participants 277 wanting to have access to the materials and to the person responsible 278 for displaying the materials during the WG session. 280 3.1.2. WG Session Phase 282 o Before the WG session 284 For the WG Chairs to enjoy their lunch, cookie, coffee, tea (or any 285 other favoured drink) until the last minute, the Secretary could 286 sacrifice his/her time and enter the meeting room well in advance to 287 prepare the WG session. This might include: checking if blue sheets 288 are available, preparing the session's material to be displayed, 289 launching collaborative software environments, preparing minute 290 taking, etc. The usefulness of such preparation depends of course on 291 the WG and on the WG session. A WG session with a light agenda might 292 not require all this. On the other hand, a WG session with an 293 extremely packed agenda, and for which every minute counts, shall 294 surely benefit from such preparation. 296 The WG Secretary could also confirm the Jabber scribe assignment, as 297 well as the minute taker assignment if applicable. 299 o During the WG session 301 The WG Secretary could be responsible for displaying the material and 302 running through the slides as speakers advance through their 303 presentation. The WG Secretary could also act as the time keeper to 304 ensure there is sufficient remaining time for all discussions to 305 happen. 307 In case the WG Secretary also takes minutes, performing multiple 308 tasks in parallel might pose certain challenges but nothing 309 insurmountable. 311 o After the WG session 313 After the end of a WG session, the WG Secretary could bring the blue 314 sheets to the IETF Secretariat and socialize with the very supportive 315 and welcoming people composing it. 317 3.1.3. Post WG Session Phase 319 o Publishing the WG session minutes 321 While it is highly recommended that the minutes of a WG session be 322 published as quickly as possible, this might only be feasible after 323 the end of the week of an IETF meeting. In any case, if the WG 324 Secretary was the minute taker he/she could polish the notes taken 325 (correcting typos, or even complementing missing parts with audio 326 recordings) and send these to the Chairs for validation. 327 Alternatively, depending on the WG Chairs' preferences, the Secretary 328 could nearly immediately share with the WG the raw minutes and 329 collect corrections. 331 Once the WG Chairs agree on the written minutes, the Secretary could 332 publish these using the means available and ask the WG participants 333 to review them and inform him/her of changes that would need to be 334 performed before final publication. 336 3.2. Continuous Tasks 338 Tracking is the word dominating the tasks a WG Secretary could be 339 expected to continuously perform. 341 o Recording and tracking authors' inputs 343 At least on two occasions, the WG Secretary is in position to receive 344 inputs from authors of Internet-Drafts concerning the status and 345 plans they have for their document(s). This is during the WG session 346 preparation phase (when building the WG status material) and during 347 the WG session when authors sometimes communicate such plans. The WG 348 Secretary should record and track this information as it is valuable 349 for sketching a plan and a schedule of the actions the Chairs will 350 have to take (e.g., WG document's adoption calls, WG Last Call). 352 o Recording and tracking WG Chairs' decisions 354 Decisions are sometimes taken by WG Chairs during WG sessions. These 355 decisions often imply some follow-up actions that the WG Chairs need 356 to take. The WG Secretary could record and track the action-points 357 for the Chairs, as well as remind them of these when necessary. 359 o Tracking events 361 Between IETF meetings, a number of WG events, including WG document's 362 adoption calls, WG Last Calls, publication of new revisions of 363 Internet-Drafts, will occur. The WG Secretary could track these 364 events and report progress, or deadlines to the Chairs. For the WG 365 document's adoption calls and WG Last Calls, the WG Secretary could 366 notify the Chairs of the end of the call together with an evaluation 367 of the positions expressed on the WG mailing list in response to 368 those calls. For Internet-Drafts that require a revision before being 369 progressed further, the WG Secretary could also notify the Chairs 370 when the expected revision is published. 372 o Watching over compliance with IETF IPR rules 374 As per [2] it is important for people making IETF contributions to 375 disclose relevant IPR in a timely manner. Verification that authors 376 are in compliance with IETF IPR rules may for example be conducted 377 prior to a WG document's adoption call or WG Last Call (see [3]). The 378 WG Secretary could monitor and track responses to such verifications, 379 and chase authors and contributors where necessary. Where responses 380 are not forthcoming, the WG Secretary could notify the Chairs. 382 o Tracking of documents' issues 384 Working Groups have issue trackers to facilitate the tracking of 385 documents issues. The WG Secretary could identify the issues raised 386 in a review of a WG document or during WG discussions and record the 387 information in the issue tracker. The WG Secretary could liaise with 388 the document editor to find which issues were resolved and how they 389 were resolved and record that information. 391 o Maintaining the Datatracker and ensuring it is up to date 393 An important tool in support of WG operations is the Datatracker [4]. 394 The WG Secretary could have the responsibility of keeping the 395 Datatracker up to date so that it reflects the exact state each 396 document is effectively in. See RFC 6174 [5] for further information 397 on the states of IETF WG Documents. The WG Secretary could also make 398 sure that the replacement status of documents is correct, and apply 399 of the proper status in case it is incorrect or not indicated and 400 necessary. Note that performing actions on the Datatracker requires 401 greater privileges than those associated to the WG Secretary status; 402 see the following section for further information. 404 o Shepherding documents 406 By convention and default WG Chairs tend to be Document Shepherds. 407 This may lead to overloading the WG Chairs and they should recall 408 that they are allowed to assign anyone to be a Document Shepherd (see 409 [6]). One option is to assign the shepherding role for some documents 410 to the WG Secretary. 412 4. Complementary Considerations 414 o Empowerment 416 When appointed as WG Secretary, the concerned person shall be 417 identified as such on the WG charter page of the Datatracker. 418 Additionally, his/her e-mail address shall be added both to the WG 419 Chairs general alias (wgchairs@ietf.org) and to the specific WG 420 Chairs alias (-chairs@tools.ietf.org). Also, certain tasks 421 described herein require the use of credentials and some rights 422 associated to these. In principle, when appointed as WG Secretary, 423 the concerned person is automatically given access to both the 424 Session Request Tool and the Meeting Materials Manager. The WG Chairs 425 should nevertheless make sure all of these elements are effective as 426 they are necessary for the Secretary to perform the various tasks. 428 o Secretary versus Delegate 430 As noted in the previous section, performing actions on the 431 Datatracker requires greater privileges than those associated to the 432 WG Secretary status. Working Group Chairs have the possibility to 433 delegate part of their privileges on the Datatracker (while retaining 434 them) to anyone. As a result, the person inheriting the delegation is 435 identified as Delegate on the WG charter page of the Datatracker, and 436 benefits from an extended scope of action. It is up to the WG Chairs 437 to decide whether a Secretary should also be a Delegate or not, and 438 conversely whether a Delegate is expected to also act as a Secretary 439 or not. It is nevertheless preferable that if a Delegate is expected 440 to act as WG Secretary, he/she also be explicitly identified as such. 442 o Secretary to WG ratio 444 Although typically a WG might only have one Secretary there is no 445 reason why two Secretaries might not be appointed. This might be to 446 help transition a new WG Secretary into the role, before the previous 447 Secretary steps down, or simply to load balance the tasks across two 448 Secretaries. Reciprocally, a person may perfectly be Secretary of 449 multiple WGs. This primarily depends on his/her ability to deal with 450 the induced workload, noting nevertheless that synergies may be 451 realised in such a situation. In any case, this document does not 452 give a recommendation on what should be the appropriate value for the 453 "Secretary / WG" ratio. 455 o Further delegation 457 There are tasks that the WG Secretary might be expected to perform 458 but in fact may further delegate. Typical examples of those tasks are 459 jabber scribing and minute taking. More generally, there are 460 situations where the WG Secretary is unable to perform certain tasks 461 (absence at an IETF meeting, agenda conflict with the WG session, 462 participation to the technical discussions during the WG session, 463 ...). The WG Secretary may fall back on the Chairs for performing the 464 impacted tasks but this would defeat the purpose of the Secretary's 465 role. Therefore it is preferable that, in those situations, the WG 466 Secretary further delegates those tasks, in agreement with the 467 Chairs. 469 As a final consideration, WG Secretaries are invited to the IETF WG 470 Chairs' lunch tutorial held during IETF meetings, usually on 471 Wednesdays. The WG Secretaries are also welcome to attend, when it is 472 scheduled, the Sunday afternoon training on WG Leadership. 474 5. Conclusions and Perspectives 476 Section 3 has listed the typical functions and responsibilities of WG 477 Secretaries. The role of a given WG Secretary can range from a few of 478 these to the full spectrum of them, and even beyond. In that regard, 479 there is a number of additional WG related events for which the 480 support of the WG Secretary would be useful. Those for example 481 include planning and setting for WG interim meetings, design team 482 meetings, etc. Nevertheless, some tasks described herein apply to 483 these contexts. 485 It is essential that over time the WG Secretary and Chairs build 486 trust to facilitate an effective and productive working relationship. 487 No secret recipe was however given here on how to achieve such a 488 relationship. Nevertheless, making clear expectations from both 489 perspectives and clear communication, the higher the probability of 490 an efficient and productive relationship. In that context, while the 491 WG Secretary function can be viewed as being a support function to 492 the Chairs, it is crucial that the Chairs also provide support to the 493 Secretary as needed. 495 The WG Secretary's role is not mandatory in WGs, hence no formal 496 selection process exists and it is also difficult to identify a 497 general practice for that purpose. Reality is that WG Chairs select 498 their Secretary in different ways. Nevertheless, to become a WG 499 Secretary, the first step is to be active and involved in the WG of 500 interest as well as show willingness and have time to dedicate to 501 that function. 503 While the apparent value of a good WG Secretary might be in the 504 delegation of tasks that the Chairs are expected to manage and in the 505 smoothed operation of WGs, this role carries a second important 506 value. As the WG Secretary develops the knowledge to fulfil the above 507 functions and responsibilities, he/she will be in a position to both 508 extend the scope of his/her actions, and to be more and more involved 509 in WG operation and decision-making. The WG Secretary's role is 510 therefore an excellent means for training individuals in the art of 511 WG operation, and ideally towards the role of WG Chair. 513 6. Security Considerations 515 Delegation based on trust is not expected to introduce security 516 issues. 518 Nevertheless, while the WG Chairs may delegate a number of tasks to 519 the Secretary, they maintain the overall responsibility and 520 accountability over the WG and the decisions and actions that are 521 taken. As such, it is recommended that the WG Secretary does not 522 operate without the agreement of the Chairs, or at least without the 523 confidence that his/her choices and actions are in line with the 524 Chairs views on any given matter. 526 In the context of his/her functions, a WG Secretary will have access 527 to the Session Request Tool and to the Meeting Materials Manager. 528 This access is in principle automatically given. The WG Chairs might 529 also give the Secretary the rights to perform certain actions onto 530 the WG Datatracker. The WG Chairs should know how to revoke both the 531 latter and former privileges. 533 Also, the WG Secretary might have access to sensitive information, 534 usually only destined to the Chairs. Therefore, it is very important 535 that a WG Secretary acts with ethics, respecting the privacy of these 536 data. 538 7. IANA Considerations 540 This document does not require any action from the IANA. 542 8. References 544 8.1. Informative References 546 [1] Bradner, S., "IETF Working Group Guidelines and Procedures", 547 BCP 25, RFC 2418, September 1998. 549 [2] Bradner, S., "Intellectual Property Rights in IETF Technology", 550 BCP 79, RFC 3979, March 2005. 552 [3] Polk, T., and Saint-Andre, P., "Promoting Compliance with 553 Intellectual Property Rights (IPR) Disclosure Rules", RFC 6702, 554 August 2012. 556 [4] "The IETF Datatracker tool", Web Application: 557 https://datatracker.ietf.org/, Version 5.7.2, November 2014. 559 [5] Juskevicius, E., "Definition of IETF Working Group Document 560 States", RFC 6174, March 2011. 562 [6] Levkowetz, H., Meyer, D., Eggert, L., and Mankin, A., "Document 563 Shepherding from Working Group Last Call to Publication", RFC 564 4858, May 2007. 566 9. Acknowledgments 568 The authors thank a number of Working Group Secretaries (in 569 alphabetical order) who have contributed to the development of this 570 document: Daniele Ceccarelli, Luigi Iannone, Subramanian Moonesamy, 571 Ines Robles, and Sam Weiler. The authors also thank Scott Bradner for 572 his thorough review and useful input. The authors also thank the 573 following WG Chairs for their reviews and comments: Lou Berger, 574 Spencer Dawkins, and Hannes Tschofenig, as well as Loa Andersson for 575 also acting as Document Shepherd. Finally, the authors thank Adrian 576 Farrel, as Area Director, for sponsoring this document. 578 This document was prepared using 2-Word-v2.0.template.dot. 580 Contributors' Addresses 582 Daniele Ceccarelli 583 Ericsson 584 Via Melen 77, Genova, Italy 586 Email: daniele.ceccarelli@ericsson.com 588 Luigi Iannone 589 Telecom ParisTech 590 23, Avenue d'Italie, 75013 Paris, France 592 Email: ggx@gigix.net 594 Subramanian Moonesamy 595 76, Ylang Ylang Avenue 596 Quatre Bornes 597 Mauritius 599 Email: sm+ietf@elandsys.com 601 Ines Robles 602 Universidad Tecnologica Nacional - FRM 603 Rodriguez 273, Mendoza, Argentina 605 Email: ines.robles@gridtics.frm.utn.edu.ar 607 Samuel Weiler 608 Parsons 609 7110 Samuel Morse Drive 610 Columbia, Maryland, 21046, USA 612 Email: weiler@tislabs.com 614 Authors' Addresses 616 Martin Vigoureux 617 Alcatel-Lucent 619 Email: martin.vigoureux@alcatel-lucent.com 621 Daniel King 622 Old Dog Consulting 624 Email: daniel@olddog.co.uk 626 Carlos Pignataro 627 Cisco Systems, Inc. 628 7200-12 Kit Creek Road 629 Research Triangle Park, NC 27709, USA 631 Email: cpignata@cisco.com