idnits 2.17.1 draft-elkins-ietf-remote-hubs-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 2970 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 N. Elkins 3 Inside Products 4 A. Retana 5 Cisco 6 A. Raje 7 ISOC 8 Intended Status: Informational 9 Expires: September 10, 2016 March 9, 2016 11 Remote Hub Status and Definition 12 draft-elkins-ietf-remote-hubs-00 14 Abstract 16 Remote IETF hubs seem to be springing up organically in quite a few 17 regions. There appear to be regional differences in how hubs are 18 organized. Latin America has quite a few remote hubs as does India. 19 The two regions are different in how they arose, where they meet, and 20 what they do. 22 Thus, creating a template for a remote hub may not work because hubs 23 may be very different across cultures and of very different sizes. 25 Lastly, this document discusses how IETF "central" can assist with 26 remote hubs. 28 Table of Contents 30 1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 31 2 Definition and goals . . . . . . . . . . . . . . . . . . . . . . 4 32 2.1 What is a remote hub? . . . . . . . . . . . . . . . . . . . 4 33 2.2 Goals for remote hubs . . . . . . . . . . . . . . . . . . . 4 34 2.3 Advantages of remote hubs . . . . . . . . . . . . . . . . . 5 35 2.4 Drawbacks of remote hubs . . . . . . . . . . . . . . . . . . 5 36 2.5 Questions about remote hubs . . . . . . . . . . . . . . . . 6 37 3 Remote hubs by region . . . . . . . . . . . . . . . . . . . . . 6 38 3.1 Remote hubs in Latin America . . . . . . . . . . . . . . . . 6 39 3.2 Remote hubs in India . . . . . . . . . . . . . . . . . . . . 7 40 4 IETF central support of remote hubs . . . . . . . . . . . . . . 7 41 4.1 Web site . . . . . . . . . . . . . . . . . . . . . . . . . . 7 42 4.2 Email lists . . . . . . . . . . . . . . . . . . . . . . . . 7 43 4.3 Regional hosts . . . . . . . . . . . . . . . . . . . . . . . 7 44 5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7 45 6 Security Considerations . . . . . . . . . . . . . . . . . . . . 7 46 7 References . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 47 7.1 Normative References . . . . . . . . . . . . . . . . . . . . 7 48 8 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7 49 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8 51 Status of this Memo 53 This Internet-Draft is submitted to IETF in full conformance with the 54 provisions of BCP 78 and BCP 79. 56 Internet-Drafts are working documents of the Internet Engineering 57 Task Force (IETF), its areas, and its working groups. Note that 58 other groups may also distribute working documents as 59 Internet-Drafts. 61 Internet-Drafts are draft documents valid for a maximum of six months 62 and may be updated, replaced, or obsoleted by other documents at any 63 time. It is inappropriate to use Internet-Drafts as reference 64 material or to cite them other than as "work in progress." 66 The list of current Internet-Drafts can be accessed at 67 http://www.ietf.org/1id-abstracts.html 69 The list of Internet-Draft Shadow Directories can be accessed at 70 http://www.ietf.org/shadow.html 72 Copyright and License Notice 74 Copyright (c) 2016 IETF Trust and the persons identified as the 75 document authors. All rights reserved. 77 IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 78 3: This document is subject to BCP 78 and the IETF Trust's Legal 79 Provisions Relating to IETF Documents 80 (http://trustee.ietf.org/license-info) in effect on the date of 81 publication of this document. Please review these documents 82 carefully, as they describe your rights and restrictions with respect 83 to this document. Code Components extracted from this document must 84 include Simplified BSD License text as described in Section 4.e of 85 the Trust Legal Provisions and are provided without warranty as 86 described in the Simplified BSD License. 88 1 Background 90 Remote IETF hubs seem to be springing up organically in quite a few 91 regions. There appear to be regional differences in how hubs are 92 organized. Latin America has quite a few remote hubs as does India. 93 The two regions are different in how they arose, where they meet, and 94 what they do. 96 Thus, creating a template for a remote hub may not work because hubs 97 may be very different across cultures and of very different sizes. 99 Lastly, this document discusses how IETF "central" can assist with 100 remote hubs. 102 2 Definition and goals 104 2.1 What is a remote hub? 106 A remote hub can be anything where more than one person gathers to 107 listen / participate in IETF sessions. It can be as simple as 108 someone's living room to major hubs with 7 rooms, telepresence and 109 many people in each. Such large remote hubs do not actually exist at 110 this point - but they could in the future. 112 It is NOT necessarily an entire set of IETF sessions viewed in real 113 time. A remote hub for a full IETF meeting may not be practical. A 114 remote hub for a working group or a few sessions may work better, at 115 least in the beginning. 117 The hubs should be self-sustaining and organize themselves -- that 118 is, not necessarily driven by a central group. 120 2.2 Goals for remote hubs 122 1. People who regularly attend IETF cannot always do so because of 123 financial constraints. Remote hubs can be one solution. 125 2. People who WANT to be involved in IETF and have some level of 126 support (ex. in Latin America, India, etc) with an ongoing group who 127 can help prepare for the WG session(s). These people would attend 128 actual IETF meetings, if they could afford it, but they can't - so 129 they go to a remote hub. 131 3. There are many valuable people in the academic world who could 132 participate and are doing potentially relevant work but do not know 133 much about IETF. Here, support and an ongoing group first needs to 134 be built who can help prepare for the WG session(s). These people 135 down the road may want to attend actual IETF meetings, but to start, 136 may want to go to a remote hub. 138 This actually applies to the start-up community as well. One of the 139 authors of this document was contacted by a Silicon Valley developer 140 doing sensor development. In the future, he wanted to be involved in 141 the ROLL Working Group. He could not afford to attend live. This 142 is a common situation for many in the start-up world. They are doing 143 innovative work and would bring implementation knowledge and 144 creativity to the IETF but often cannot afford to attend IETF 145 meetings in person. If there were an option to be involved in a 146 remote hub in Silicon Valley, it is likely that quite a few people 147 would take advantage of that. 149 2.3 Advantages of remote hubs 151 1.Not everyone can come to the meetings. Provide that experience. 153 2. A remote hub can help to create local communities. Building 154 related communities may be a very important benefit. 156 3. Remote hubs may increase participation. This is a very important 157 benefit. 159 4. There may be topics of local interest. 161 5. The remote hub can continue to work outside of the IETF meetings. 163 6. A remote hub should be a better experience than attending remotely 164 alone. Provides a group of interested individuals or community 165 with opportunities for networking. 167 2.4 Drawbacks of remote hubs 169 1. What if the quality of the network connection is poor? If I have 170 important work to do, I may just attend from home where I can better 171 control the connection. 173 2. What if others do not want to attend the same sessions that I do? 175 3. This is logistically a complicated deal. Need space or 176 conference room for the hub. 178 4. Time zone can be quite challenging 180 2.5 Questions about remote hubs 182 1. What if interest in a given hub spans many tracks?? Especially if 183 simultaneous session demand exists. Between 5-7 rooms may be needed 184 to cover various areas. Should there be a hub and "Spoke" arrangement 185 for different rooms/interests? 187 2. Will people travel within their country (air and hotel) as a 188 "cheaper' alternative to traveling internationally? 190 3. Why would people travel domestically any significant distance, 191 rather than just set up another remote location? 193 4. How far should we expect someone to travel to a remote hub? 194 Should staying overnight be assumed viable? 196 5. Would someone travel to the remote hub for just one session? May 197 need to schedule so that everyone at that hub would attend two or 198 three consecutive sessions to make the travel worthwhile. 200 6. Scheduling across time zones could be an issue, especially if 201 time zone of meeting is Asia. Can remote hubs use recordings and 202 watch together to address time zone differences. 204 7. Can remote hubs be a viable alternative for ACTIVE participants? 205 What about a chair or director? 207 8. Does IETF sponsor any remote hubs? 209 9. Can remote hubs approach the experience of attending the 210 meetings? 212 10. Is there a cost to participate in a IETF meeting at a remote hub? 213 Physical meeting attendees pay $800, will remote hub attendees have 214 any expenses? 216 11. Are there any costs involved in running a remote hub? 218 12. Is any training or certification needed to be a hub? 220 3 Remote hubs by region 222 3.1 Remote hubs in Latin America 224 Latin America has many remote hubs and plans for many more. They are 225 organic and may be quite small with only a few individuals interested 226 in a particular topic. The first remote hub was in the Hawaii IETF 227 with 50 people attending from hubs. In Dallas IETF, there were 100 228 - 200 people and 20 hubs. 230 They haven't spent any money at all. Many don't even have a 231 projector. Just a PC. Having 3-4 people discussing is more 232 interesting than attending a meeting by themselves. 234 3.2 Remote hubs in India 236 India has 23 hubs and over 500 members participating remotely at 237 large universities as a part of the Indian IETF Capacity Building 238 (IICB) program. The web site www.IICB.org has been set up with more 239 information on this. 241 4 IETF central support of remote hubs 243 4.1 Web site 245 Web pages to get information out about remote hubs and what they are 246 covering, schedules and other details/logistics. 248 4.2 Email lists 250 Potentially providing emails lists. 252 4.3 Regional hosts 254 Maybe regional hosts are needed. 256 5 IANA Considerations 258 There are no IANA considerations. 260 6 Security Considerations 262 There are no security considerations. 264 7 References 266 7.1 Normative References 268 8 Acknowledgments 270 The authors would like to thank Christian O'Flaherty and Simon Pietro 271 Romano for their comments and assistance. 273 Authors' Addresses 275 Nalini Elkins 276 Inside Products, Inc. 277 Carmel Valley, CA 93924 278 USA 279 Phone: +1 831 659 8360 280 Email: nalini.elkins@insidethestack.com 282 Alvaro Retana 283 Cisco Systems, Inc. 284 7025 Kit Creek Rd. 285 Research Triangle Park, NC 27709 286 USA 287 EMail: aretana@cisco.com 289 Anand Raje 290 ISOC Kolkata 291 Indian IETF Capacity Building (IICB) program 292 Kolkata, India 293 EMail:anand@rabt.in