idnits 2.17.00 (12 Aug 2021) /tmp/idnits50568/draft-oflaherty-ietf-remote-hubs-lac-00.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 (March 9, 2016) is 2257 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT C. OFlaherty 3 ISOC 4 A. Retana 5 Cisco 6 C. Martinez 7 LACNIC 8 N. Elkins 9 Inside Products 10 S. P. Romano 11 University of Napoli 12 Intended Status: Informational 13 Expires: September 10, 2016 March 9, 2016 15 Remote Hubs in Latin America 16 draft-oflaherty-ietf-remote-hubs-lac-00 18 Abstract 20 This document describes experiences and lessons learnt organizing 21 remote sessions for working group meetings in Latin America. The main 22 objective is to engage people in the IETF through small and informal 23 meetings with people that share common interests. 25 At the same time, remote participation for those already active in 26 the IETF is more attractive and they help with IETF outreach sharing 27 their experiences with newcomers. 29 The local meetings are called remote IETF Working Group Hubs. 31 Table of Contents 33 1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 34 2 Definition and goals . . . . . . . . . . . . . . . . . . . . . . 4 35 2.1 What is a remote hub? . . . . . . . . . . . . . . . . . . . 4 36 2.2 What they are not . . . . . . . . . . . . . . . . . . . . . 4 37 3 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . 4 38 3.1 How to organize a remote hub . . . . . . . . . . . . . . . . 5 39 3.1.1 Location: . . . . . . . . . . . . . . . . . . . . . . . 5 40 3.1.1 Organizer: . . . . . . . . . . . . . . . . . . . . . . . 5 41 3.1.2 Internet access . . . . . . . . . . . . . . . . . . . . 5 42 3.1.3 Software Tools . . . . . . . . . . . . . . . . . . . . . 5 43 3.1.4 Projector or screen . . . . . . . . . . . . . . . . . . 6 44 3.1.5 Audio . . . . . . . . . . . . . . . . . . . . . . . . . 6 45 3.1.6 Microphone . . . . . . . . . . . . . . . . . . . . . . . 6 46 3.2 Planning for a remote hub . . . . . . . . . . . . . . . . . 7 47 4 Use of IETF name / brand . . . . . . . . . . . . . . . . . . . . 7 48 5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 49 6 Security Considerations . . . . . . . . . . . . . . . . . . . . 7 50 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 51 7.1 Normative References . . . . . . . . . . . . . . . . . . . . 7 52 8 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 53 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 55 Status of this Memo 57 This Internet-Draft is submitted to IETF in full conformance with the 58 provisions of BCP 78 and BCP 79. 60 Internet-Drafts are working documents of the Internet Engineering 61 Task Force (IETF), its areas, and its working groups. Note that 62 other groups may also distribute working documents as 63 Internet-Drafts. 65 Internet-Drafts are draft documents valid for a maximum of six months 66 and may be updated, replaced, or obsoleted by other documents at any 67 time. It is inappropriate to use Internet-Drafts as reference 68 material or to cite them other than as "work in progress." 70 The list of current Internet-Drafts can be accessed at 71 http://www.ietf.org/1id-abstracts.html 73 The list of Internet-Draft Shadow Directories can be accessed at 74 http://www.ietf.org/shadow.html 76 Copyright and License Notice 78 Copyright (c) 2016 IETF Trust and the persons identified as the 79 document authors. All rights reserved. 81 IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 82 3: This document is subject to BCP 78 and the IETF Trust's Legal 83 Provisions Relating to IETF Documents 84 (http://trustee.ietf.org/license-info) in effect on the date of 85 publication of this document. Please review these documents 86 carefully, as they describe your rights and restrictions with respect 87 to this document. Code Components extracted from this document must 88 include Simplified BSD License text as described in Section 4.e of 89 the Trust Legal Provisions and are provided without warranty as 90 described in the Simplified BSD License. 92 1 Background 94 IETF Remote Hubs are remote meetings for a working group session 95 where a small group of people that share their interest and knowledge 96 on a specific topic, meet locally to make their remote participation 97 more attractive. This document is how this has been implemented in 98 Latin America. 100 There are groups of people at Universities or Companies that share 101 their interest in certain Working Group or follow the same mailing 102 lists but are not yet engaged in discussions and usually have never 103 participated in a meeting. In most cases that lack of appropriate 104 involvement or their daily responsibilities discourage them for being 105 remote participants. IETF WG Remote hubs are local meetings for the 106 working group they're following, where people can experience remote 107 participation accompanied. The objective is to experience something 108 closer to a real working group session, following the presentations 109 and discussing issues locally and in their own language. 111 2 Definition and goals 113 2.1 What is a remote hub? 115 In Latin America, IETF WG Remote hubs are informal and small 116 gatherings (usually less than 15 participants), using the standard 117 IETF tools for remote participants, organized for a specific working 118 group session (2-4 hours), usually during an IETF meeting. 120 Remote hubs can be public and open for anyone to attend or closed 121 just for some invited participants. 123 2.2 What they are not 125 Remote IETF WG Hubs are not remote IETF events were people can show 126 up without invitation or attend for networking purposes. They usually 127 do not provide food nor beverages or goodies. There's no exhibition, 128 no social event (not even cookies). 130 The IETF WG remote hubs are not streaming the IETF meeting live 131 during the whole day. 133 3 Organization 135 Remote hubs can be public (open invitation) or closed to invited 136 people. It is up to the organizer the format and how to invite 137 participants. 139 IETF Remote Hubs are not as complex to organize as other remote hubs 140 such as ICANN's or IGF. The amount of people participating in an IETF 141 WG remote hub is usually limited to those that are currently 142 following that working group mailing list. The average attendance is 143 between 5 and 10 participants. 145 3.1 How to organize a remote hub 147 In order to organize a remote hub you will need: 149 3.1.1 Location: 151 The usual locations are meeting rooms when they're organized by 152 companies or classrooms when they're organized by universities. The 153 working group sessions can last up to four hours so it's desirable to 154 have seats available for the participants. 156 3.1.1 Organizer: 158 Individuals are usually the champions for IETF WG remote hubs. 159 Someone currently active in a working group is usuarlly the main 160 conviener. 162 Any organization can host a remote Hub. Companies and Universities 163 were the most common locations, but there were also remote IETF WG 164 hubs organized at IXPs (Internet Exchange Points), ccTLDs (country 165 code top level domain organizations) and RIR (Regional Internet 166 Registry) 168 3.1.2 Internet access 170 The bandwidth required is less than 1Mbps for a decent quality for 171 both audio and video. 173 3.1.3 Software Tools 175 The preferred remote participation tool is Meetecho. It includes 176 useful features for remote participants such as a virtual mike queue. 177 The updated instructions for using Meetecho are located in the remote 178 participants section in the meeting web page. As an example, for 179 IETF-94: http://www.ietf.org/meeting/94/remote- 180 participation.html#Meetecho. 182 Since IETF91 in Honolulu, all sessions are supported by Meetecho. A 183 synchronized view of the official jabber room, the slides being 184 presented and an audio/video feed from the physical meeting room is 185 made available for each Meetecho virtual room. 187 Remote participants can: 189 1. View presentations and speakers in real-time; 190 2. Use the Jabber room to make comments or ask questions; 191 3. Join a virtual queue to interactively make comments or ask 192 questions over the in-room audio system. 194 All audio/video functionality in Meetecho is WebRTC based, which 195 means that, while alternative, non-interactive options are provided, 196 a WebRTC compliant web browser (currently, either Chrome or Firefox 197 or Opera) is needed for active (i.e., interactive) participation. 198 That said, a WebRTC compliant browser is sometimes not enough, as the 199 client network may employ filters or firewalls that might affect a 200 successful WebRTC connectivity. Hence, in order to check whether or 201 not the client is able to make use of WebRTC for the purpose, a 202 simple self-test web application (directly reachable from the IETF 203 remote participation web site) is provided. The self-test site will 204 attempt to start an echo test that will try and capture client's 205 audio and video, and bounce them back: if the client can see herself 206 in both boxes and hear herself back, it means that everything is 207 fine. If not, the Meetecho team has to be notified in order to fix 208 things prior to the session's start time (so to avoid disrupting the 209 natural flow of the meeting). 211 3.1.4 Projector or screen 213 When the hub has no more than five participants there's no need to 214 use a projector. A computer screen will be enough to follow the 215 slides and video from the meeting. When more people are expected in 216 the IETF WG remote hub, you will need a bigger room and a projector 217 is usually required to se the remote slides properly. 219 3.1.5 Audio 221 The audio could be less than optimal so the computer audio is not 222 enough. Additional speakers are always recommended. 224 3.1.6 Microphone 226 Be prepared to ask questions from your Hub. A microphone will be 227 useful to improve the sound quality from your meeting room. Be 228 prepared to mute your speakers if echo is experienced. When the 229 meeting room is big, a wireless microphone will be better. 231 3.2 Planning for a remote hub 233 1. Wait for the IETF agenda to be published 235 2. Look for an available meeting room at the time slot when your 236 Working Group meets 238 3. Notify the IETF about your remote hub if you want it included in 239 the public remote IETF WG Hubs list 241 4. Invite participants (include your name, date, time, location and 242 Working Group name) 244 5. Test Meetecho before the Working Group session (see above for 245 details about the self-test facility provided by Meetecho) 247 6. Use jabber to notify the jabber scribe when your remote hub is 248 online 250 4 Use of IETF name / brand 252 Even though the IETF supports and encourages the organization of 253 remote hubs, they're not official IETF activities. If you plan to 254 host a remote hub, and you plan to publicly announce it to your 255 community, please be careful not to use the IETF name or logo without 256 authorization. In order to be complaint with current copyright 257 requirements, please notify the appropriate people at IETF before 258 doing any announcements. 260 5 IANA Considerations 262 There are no IANA considerations. 264 6 Security Considerations 266 There are no security considerations. 268 7 References 270 7.1 Normative References 272 8 Acknowledgments 274 The authors would like to thank Juliao Braga for his contributions 275 and assistance on the IETF WG Remote Hubs in Latin America. 277 Authors' Addresses 279 Christian O'Flaherty 280 ISOC 281 Rambla Republica de Mexico 6125 282 Montevideo 283 Uruguay 284 EMail: oflaherty@isoc.org 286 Alvaro Retana 287 Cisco Systems, Inc. 288 7025 Kit Creek Rd. 289 Research Triangle Park, NC 27709 290 USA 291 EMail: aretana@cisco.com 293 Carlos Martinez 294 LACNIC 295 Rambla Republica de Mexico 6125 296 Montevideo 297 Uruguay 298 EMail: carlos@lacnic.net 300 Nalini Elkins 301 Inside Products, Inc. 302 36A Upper Circle 303 Carmel Valley, CA 93924 304 United States 305 Phone: +1 831 659 8360 306 Email: nalini.elkins@insidethestack.com 307 http://www.insidethestack.com 309 Simon Pietro Romano 310 University of Napoli 311 Via Claudio 21 312 Napoli 80125 313 Italy 314 EMail: spromano@unina.it