Re: [Netrqmts] New Version Notification for draft-odonoghue-netrqmts-02.txt

"Joe Clarke (jclarke)" <jclarke@cisco.com> Sat, 23 November 2019 03:40 UTC

Return-Path: <jclarke@cisco.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 B7EF71201E4 for <netrqmts@ietfa.amsl.com>; Fri, 22 Nov 2019 19:40:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=eN6Azqqo; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=D8yl3DsQ
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 H7zvVnmnSWKC for <netrqmts@ietfa.amsl.com>; Fri, 22 Nov 2019 19:40:26 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C09E12010F for <netrqmts@ietf.org>; Fri, 22 Nov 2019 19:40:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4640; q=dns/txt; s=iport; t=1574480426; x=1575690026; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zI4Xz4bqnqc3oW0X6CnY7f9wsKMQ+ERUCqj2s1Ohrk4=; b=eN6AzqqoeBvZWUkbVa7BJd3Ob9o2DJD4ASm3ySTjmRbGvJ3GCsinv0Sf 36LcoQFhNiFlwJ7ONYeGNgNwF9s2KWun6KJGPoiezkDCAxB9UUm2T0t0+ Wpl1GBwc+q9n+6jgcl9yjEU0a+gTtkgcUnospwJeuwWi14SXzdLVUigqt Y=;
IronPort-PHdr: =?us-ascii?q?9a23=3AmoAA/BBBvrN1d29U/3ezUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qs13kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMfkuHw?= =?us-ascii?q?QAld1QmgUhBMCfDkiuLvXuZjY5EexJVURu+DewNk0GUMs=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ApAACBqdhd/5JdJa1lGgEBAQEBAQE?= =?us-ascii?q?BAQMBAQEBEQEBAQICAQEBAYFtAgEBAQELAYFKUAWBRCAECyoKhCCDRgOKbYJ?= =?us-ascii?q?fmAGCUgNUCQEBAQwBAS0CAQGEQAIXghMkNwYOAgMNAQEEAQEBAgEFBG2FNwy?= =?us-ascii?q?FUQEBAQECARIREQwBATUCAQQLAgEIDgQGAgImAgICMBUCDgIEDgUigwCCRwM?= =?us-ascii?q?OIAGjXQKBOIhgdYEygn4BAQWFGxiCFwmBDigBjBUagUA/gTgfgkw+hCUBAR6?= =?us-ascii?q?DEDKCLI1agjyFbJdEbgqCK4hqgxKJVBuCPpdaqFQCBAIEBQIOAQEFgWgjgVh?= =?us-ascii?q?wFWUBgkFQERSGSAwXg1CKU3SBKI1sgSIBgQ4BAQ?=
X-IronPort-AV: E=Sophos;i="5.69,232,1571702400"; d="scan'208";a="369487625"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Nov 2019 03:40:25 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id xAN3ePUK006134 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 23 Nov 2019 03:40:25 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 22 Nov 2019 21:40:24 -0600
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 22 Nov 2019 21:40:24 -0600
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 22 Nov 2019 21:40:24 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Vt8d58e2zdsDtldT/vAllL0K7ExYbEgu6viZ2Edhqv6aDjWNEEfoxZvVPN1eQbAeM/K87MBLVtaCavtI7hWw0yN17HjqJ62ZP3O1F0hPIiI7v7+yAD+jalumFHx2l078pXGQ1T2hEStDwfZiEXGxc10IaN24YOHuh8wQIaLP12z92BkxLMyfdcSyrnG4o/TJ2mz7ZsfvrLdIYQu1feYI5YNSF3U6KdCZNobX4Y2c0Am7bVMwWnkow5Rn4EnsLFjTC17eaTcBLv9Qtlcdj0m86v1M+sRUiGC4zgN3TlwU9hiE8k73BatZIpnAbbOqdJxBAOYtlzei7ed0KVmxBVgpxg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zI4Xz4bqnqc3oW0X6CnY7f9wsKMQ+ERUCqj2s1Ohrk4=; b=P1AGOns9CN3M9w4tNH5CqSdDk7aD/PMfx8mdH2oIHf9gopKE6MRAIpwb2XqFaTSNoV9UASQO8J5zlatrmZLfWyqSc4Gu4Q+7j9quzYI33IlOgwb6pZzhkGe5w4xjRW3MY5Seq5FVQUyiiwIoZ/vm6z6YLxiXmXynp8aLE2iFZOkgWuy0TUZUGjA2WWdeFW0svkPvWEEXQlokgfFx/JtnKlwgM5ion3IDzpCIdeBgwi2zOBIUTVKddTG27eL0GtSyx8wjnutgzRo/KVWWtKfCjFPsnl3FwPjUe792GfglDI0H79SchAku91wsep0K1kmsSZOeCej8AibxtOfIbjPUPA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zI4Xz4bqnqc3oW0X6CnY7f9wsKMQ+ERUCqj2s1Ohrk4=; b=D8yl3DsQSYTEaYMFepceT+6RLwOffUXuLbKHki1Cg+Kf1sS0oAVHMNwER5Z/WmxgOIqn0jFCQBPp0Z5rVsHZ1hbHgok0cVwa2KQV6AYFClp0h0R43oK8hKCissev0OrOj4RM1nXz9PMtMkpDnbnYzGjEp+Q1IwAcf/EgbJI8mWg=
Received: from BN6PR11MB1667.namprd11.prod.outlook.com (10.172.23.12) by BN6PR11MB2051.namprd11.prod.outlook.com (10.173.32.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2474.16; Sat, 23 Nov 2019 03:40:23 +0000
Received: from BN6PR11MB1667.namprd11.prod.outlook.com ([fe80::499:8548:e967:458e]) by BN6PR11MB1667.namprd11.prod.outlook.com ([fe80::499:8548:e967:458e%12]) with mapi id 15.20.2474.019; Sat, 23 Nov 2019 03:40:23 +0000
From: "Joe Clarke (jclarke)" <jclarke@cisco.com>
To: Tim Wattenberg <mail@timwattenberg.de>
CC: "netrqmts@ietf.org" <netrqmts@ietf.org>, "Livingood, Jason" <Jason_Livingood@comcast.com>, Bob Hinden <bob.hinden@gmail.com>, "Karen O'Donoghue" <odonoghue@isoc.org>
Thread-Topic: [Netrqmts] New Version Notification for draft-odonoghue-netrqmts-02.txt
Thread-Index: AQHVoOuUEVbsEyQCDUmuB7ee4rgMxqeWojkAgAF7ZoA=
Date: Sat, 23 Nov 2019 03:40:23 +0000
Message-ID: <BB1A54F9-FF57-4ABC-BDFB-FC28528EA419@cisco.com>
References: <157290772945.13855.16351216204560466911.idtracker@ietfa.amsl.com> <55AACF28-576A-42E4-8FD7-E082482AF43B@gmail.com> <B53C5F5D-0C2E-4395-A778-967948D4DB4D@cable.comcast.com> <08D065C1-16EE-4CC0-8941-FD92B5EA167E@cisco.com> <6E2A34C0-4D2C-415A-9D14-52AA1AAE4982@timwattenberg.de>
In-Reply-To: <6E2A34C0-4D2C-415A-9D14-52AA1AAE4982@timwattenberg.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=jclarke@cisco.com;
x-originating-ip: [70.231.19.155]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 13e6d03c-700c-42de-40dc-08d76fc6df27
x-ms-traffictypediagnostic: BN6PR11MB2051:
x-microsoft-antispam-prvs: <BN6PR11MB2051A99AABE37EBF7E99D452B8480@BN6PR11MB2051.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0230B09AC4
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(346002)(376002)(136003)(366004)(396003)(189003)(199004)(51914003)(71190400001)(36756003)(8676002)(6486002)(229853002)(4326008)(305945005)(86362001)(76176011)(99286004)(14444005)(7736002)(53546011)(6506007)(5660300002)(1250700005)(54906003)(6512007)(256004)(6916009)(316002)(6246003)(102836004)(6436002)(3846002)(26005)(71200400001)(11346002)(6116002)(2616005)(66066001)(478600001)(186003)(33656002)(64756008)(81166006)(91956017)(8936002)(76116006)(66476007)(66556008)(81156014)(66946007)(66446008)(446003)(14454004)(25786009)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR11MB2051; H:BN6PR11MB1667.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Hi9jgO330RIwyOWG+4iCCvsLyPjAuBUR3e8GIy39JPQhHfZ3tC6vktdoTBNBVCCH4e3WHAKK4B9WuWVtBLVo8+PfRoNqPqk5dSMbTc7yLa83SbJ6jT1bB8flKBnwiW5AeFaUt9RqMhFE1Yg7p8sGGhKIH7NDihMKs2ipePuHHi861sdzdDipdVH1Br+9OlE7RO4zVgdiXsnLs+lVhTg6Zu5tALZa6UQhg86Kmla7Ir9rGLtyokpHMicb6gKQ077XqJMN48uKNHYXnc131DhFdrgMk9d39yw32uL0j9p0Qdk7VJjghbP+uJjvBhIwafdCaUdEKnEbgW/0g7YYZfR0tzFxWS6BC7uuTvmfwZdS9PbbLreAdU0oaUpd6MFeyUj+i9Jfjxd4FPZKpVuHB1yycbAGjgWrPqt3SXQ+Dj9WtA/7i0Rx4xw6Qj1GLhM6FTH5
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <E76BF3E7FA724C42ACBEC85D142D369A@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 13e6d03c-700c-42de-40dc-08d76fc6df27
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Nov 2019 03:40:23.2924 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rWfo0DUe75igVLq/SgDTshgxNPFDdQNDXgKS+xPJVxnSW3Bc2vlSaLMkwDT8Kh/oao5S7Cj1ynWYB3RBUAAhyQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR11MB2051
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/xHj0bqeBhyDygzXrzwJ4j9fIvYA>
Subject: Re: [Netrqmts] New Version Notification for draft-odonoghue-netrqmts-02.txt
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: Sat, 23 Nov 2019 03:40:29 -0000


> On Nov 22, 2019, at 00:02, Tim Wattenberg <mail@timwattenberg.de> wrote:
> 
> Joe, thanks for responding. Some comments below.
> 
>> Am 22.11.2019 um 12:16 schrieb Joe Clarke (jclarke) <jclarke@cisco.com>om>:
>> 
>> First, with respect to logging/DPI/packet captures, we should not have a hard and fast rule on this.  We _do_ do some packet capturing and DPI sometimes when we’re trying to troubleshoot certain issues.  We _always_ log PII as the meeting goes on (like IPs and MACs).  What we don’t do is retain this data beyond its useful lifetime and definitely not beyond the meeting time (without some anonymization).
>> 
>> What we can state is that any and all PII must be destroyed or randomized and not transported off in its unanonymized form from the meeting venue.
> 
> Personally, that’s perfectly fine with me. With my comments I didn’t meant to oppose any hurdles against running a reliable and functional network (as this is what we ultimately need).
> But I think there is value in specifying just *what* is done (something along your lines)  – like a "privacy policy".
> Let it be just as documentation for whom it is important (for personal or whatever reasons).

That makes sense.  I guess many would assume you’d have to do these things to diagnose network problems, but it’s best to be up front, especially with the fact that we do our best to destroy PII after its usefulness ends.

> 
>> As to more on the doc, I think in some places we are too specific.  For example, in Section 4.3, we talk about providing VMs for remote participation and DHCPv4 and v6.  Today we use VMs for Meetecho, but we may not always do that.  I don’t think DHCPv4 is going anywhere, but again, it’s what we do today.  In general, we need to provide compute infrastructure to support remote participation, and we need to provide a way to scalable address client hosts and provide name resolution.  For example, we may drop DHCPv6 at some point as RDNSS is fairly well-supported in RAs.
>> 
>> Likewise, in Section 4, getting into separate VLANs for wired/wireless seems too specific.  Today we do that, but we may not as we evolve the network.  Changing VLAN architecture should not be user-impacting, and thus I don’t think we need to explicitly call it out in the requirements doc.
> 
> I tend to agree with you here. However, I also remember the BoF in Montreal where there actually *was* a detailed discussion around specific services.
> In the end, it’s somehow a matter of taste if people like to have a very strict requirements document, or rather something more general.
> (As said, personally I lean towards the latter – at least for a start.)

We wanted to provide _all the things_ in YUL.  But some of what we do, we do today because it makes sense and it’s entirely internally facing (meaning users aren’t aware).  We would like the flexibility to evolve in those areas as needed.  I’d rather the requirements doc focus more on  the user experience, only touching on engineering matters where it helps inform specific elements or that experience (such as explicitly stating single redundancy is required to ensure optimum uptime).

> 
> I’m sitting in the last Friday session, so:
> Thanks to the NOC for yet another meeting!

You’re very welcome.  We love our jobs :-).  Thanks for the shout-out.

Joe