[Netrqmts] updated network requirements draft

"kodonog@pobox.com" <kodonog@gmail.com> Tue, 09 July 2019 01:42 UTC

Return-Path: <kodonog@gmail.com>
X-Original-To: netrqmts@ietfa.amsl.com
Delivered-To: netrqmts@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF47F1200E6 for <netrqmts@ietfa.amsl.com>; Mon, 8 Jul 2019 18:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.693
X-Spam-Level:
X-Spam-Status: No, score=-0.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_PDS_FROM_2_EMAILS=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rPQM-Jdzq3Ib for <netrqmts@ietfa.amsl.com>; Mon, 8 Jul 2019 18:42:48 -0700 (PDT)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EE3B12024E for <netrqmts@ietf.org>; Mon, 8 Jul 2019 18:42:46 -0700 (PDT)
Received: by mail-qk1-x732.google.com with SMTP id d79so10578430qke.11 for <netrqmts@ietf.org>; Mon, 08 Jul 2019 18:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=Kq7oWxXRC5YnOZUvfONQoLriHxAbB3AjJmHmYwbQhfE=; b=QGaF5eBeLUNn3Fs31H7Fr7Ta6zDRjfRFPJ1DlHxu0rN9IAWTd1Ij81gBnYcdJK4eg9 33aJL66IYcb7KwGx73mAaacTKWcYXugt9AiejeOnfOdvQciYG1aXf5NIxOoZj0aogp3k Jclt/KPDnun0tlOSymSfKa4oQNFm5o8Sb7i+J2XOY4BZDjFXWQI5A++bG268IZ1lyj/6 5241qYO05SRJTD47TjtXLHucjHdO0CMxt+ttUG1a3eXSYKOiNsSyIFZlapSU2+5xMFtp qmJLm1hr85fdrzxwLVDo7nObR0vULMUq+2+FwcIKDHQIvaoAJxbytsOMQsjiMf254T1o tWRQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-transfer-encoding; bh=Kq7oWxXRC5YnOZUvfONQoLriHxAbB3AjJmHmYwbQhfE=; b=dgvLHayui/5O7nNrIRpclCxC+9sJtrLP/t8yNP6LzS/SRzUNqUOhE21EjC4KrEVzxX L/fVPpRmcHEuTQtsNWk+2qXFH2bywowvpMMNIa6IBTckxo3JNc+i4Ec88aDCzCERhtCP LRP5Mfp1KD/ZuadDtUbY/7L05u3FGKJPPPy7dvU2icJCgZyaMC5lielHbdFhaIdOzhWL BB0YNLldIqoQ9XjtnSqh6UIFroHXfHQnVjf9HzzP5EyUuk48ayNcZL9bV3XHFFGCnSVT zVYIQpcTvR00RwM5AundG/Rqxd8qKMX7SU59pc5UqnQHF0PlCX920JY/lwVUfEGC8nXP asEg==
X-Gm-Message-State: APjAAAVAzieqZKvfbOlok4QUcpb7vtk2sB13OX4HeleSYw7caWFJ8jAi ApbSKqVw8TbpybfiLdqWm3hPfw==
X-Google-Smtp-Source: APXvYqy1trzCoO0iOKG7sVS0U0QLg0C10tjEjNlbwNMpd3tXRGPqmVbTKxAQkdSnpabrLhQ+MSbICQ==
X-Received: by 2002:a05:620a:632:: with SMTP id 18mr17226572qkv.205.1562636565299; Mon, 08 Jul 2019 18:42:45 -0700 (PDT)
Received: from [192.168.1.137] (d-65-99-124-221.va.cpe.atlanticbb.net. [65.99.124.221]) by smtp.gmail.com with ESMTPSA id u71sm8658595qka.21.2019.07.08.18.42.44 for <netrqmts@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 08 Jul 2019 18:42:44 -0700 (PDT)
From: "kodonog@pobox.com" <kodonog@gmail.com>
To: netrqmts@ietf.org
Date: Mon, 08 Jul 2019 21:42:43 -0400
X-Mailer: MailMate (1.12.5r5635)
Message-ID: <0E50607A-89A1-44DB-BD78-8256D23BC5F7@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/PgyV-Hd9JH4GKToDyaq-5TZ6ue8>
Subject: [Netrqmts] updated network requirements draft
X-BeenThere: netrqmts@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Meeting Network Requirements <netrqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netrqmts/>
List-Post: <mailto:netrqmts@ietf.org>
List-Help: <mailto:netrqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netrqmts>, <mailto:netrqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jul 2019 01:42:50 -0000

Folks,

I have submitted an update (-01) to the network requirements draft (see 
pointers below). However, there is still much to be fixed and much 
missing from the draft.

I originally chose for the -00 to be the exact text developed originally 
so that there would be transparency in what was added and removed. 
(https://www.ietf.org/how/meetings/admin/meeting-network-requirements/)

In hindsight, perhaps that wasn’t the wisest choice but hey… you 
live and learn…

This document represents three sets of requirements:
1) Requirements for external connectivity providers
2) Requirements for the meeting venue
3) Requirements for the network that the IETF NOC Team builds
These are perhaps not as clearly differentiated as they should be.

Also, we have not addressed any network requirements for the hotel rooms 
in this document as the original text also did not address it.

And finally, some sections of this still haven’t received any 
substantive review. But, tomorrow is another day…

Suggestions with text are most welcome.

Karen

A new version of I-D, draft-odonoghue-netrqmts-01.txt
has been successfully submitted by Karen O'Donoghue and posted to the
IETF repository.

Name:		draft-odonoghue-netrqmts
Revision:	01
Title:		IETF Meeting Network Requirements
Document date:	2019-07-08
Group:		Individual Submission
Pages:		8
URL:            
https://www.ietf.org/internet-drafts/draft-odonoghue-netrqmts-01.txt
Status:         
https://datatracker.ietf.org/doc/draft-odonoghue-netrqmts/
Htmlized:       https://tools.ietf.org/html/draft-odonoghue-netrqmts-01
Htmlized:       
https://datatracker.ietf.org/doc/html/draft-odonoghue-netrqmts
Diff:           
https://www.ietf.org/rfcdiff?url2=draft-odonoghue-netrqmts-01

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.