IETF Meeting Network Requirements
draft-odonoghue-netrqmts-02

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      K. O'Donoghue
Internet-Draft                                             IETF NOC Team
Intended status: Informational                            R. Hinden, Ed.
Expires: May 7, 2020                                Check Point Software
                                                        November 4, 2019

                   IETF Meeting Network Requirements
                      draft-odonoghue-netrqmts-02

Abstract

   The IETF Meeting Network has become integral to the success of any
   physical IETF meeting.  Building such a network, which provides
   service to thousands of heavy users and their multitude of devices,
   spread throughout the event venue, with very little time for setup
   and testing is a challenge.  This document provides a set of
   requirements, derived from hard won experience, as an aid to anyone
   involved in designing and deploying such future networks.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on May 7, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must

O'Donoghue & Hinden        Expires May 7, 2020                  [Page 1]
Internet-Draft                     I-D                     November 2019

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements for Internet Connectivity  . . . . . . . . . . .   3
   3.  Meeting Facility Requirements . . . . . . . . . . . . . . . .   3
   4.  Internal Network Requirements . . . . . . . . . . . . . . . .   5
     4.1.  Requirements for Terminal Room or equivalent  . . . . . .   5
     4.2.  Requirements for Wireless . . . . . . . . . . . . . . . .   6
     4.3.  Requirements for Services . . . . . . . . . . . . . . . .   6
     4.4.  Network Monitoring Requirements . . . . . . . . . . . . .   7
   5.  Miscellaneous Requirements  . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   9.  Revision History [RFC Editor: Please remove]  . . . . . . . .   8
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     10.2.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The IETF Meeting Network has grown and evolved over time as has the
   IETF overall.  In addition, the way that the IETF network is built
   and provisioned has also changed.  It is time for the IETF community
   to consider the requirements of this infrastructure and its role in
   supporting the mission of the IETF.  This document is meant to help
   frame that conversation.  Additionally, this document may eventually
   be developed to be useful to others outside the IETF in specifying
   and building their own successful event networks.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

O'Donoghue & Hinden        Expires May 7, 2020                  [Page 2]
Internet-Draft                     I-D                     November 2019

2.  Requirements for Internet Connectivity

   o  A primary and backup link MUST be provided for redundancy.  If
Show full document text