Remote Hub Status and Definition
draft-elkins-ietf-remote-hubs-00

Document Type Expired Internet-Draft (individual)
Last updated 2016-09-10 (latest revision 2016-03-09)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-elkins-ietf-remote-hubs-00.txt

Abstract

Remote IETF hubs seem to be springing up organically in quite a few regions. There appear to be regional differences in how hubs are organized. Latin America has quite a few remote hubs as does India. The two regions are different in how they arose, where they meet, and what they do. Thus, creating a template for a remote hub may not work because hubs may be very different across cultures and of very different sizes. Lastly, this document discusses how IETF "central" can assist with remote hubs.

Authors

Nalini Elkins (nalini.elkins@insidethestack.com)
Alvaro Retana (aretana@cisco.com)
Anand Raje (anand@rabt.in)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)