IETF Logo Mail Archive

Re: [Netrqmts] IETF 105 Minutes

"Livingood, Jason" <Jason_Livingood@comcast.com> Wed, 31 July 2019 13:13 UTC

Return-Path: <Jason_Livingood@comcast.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 8DDB8120018 for <netrqmts@ietfa.amsl.com>; Wed, 31 Jul 2019 06:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcast.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 2_SZerHnyPsN for <netrqmts@ietfa.amsl.com>; Wed, 31 Jul 2019 06:12:58 -0700 (PDT)
Received: from copdcmhout02.cable.comcast.com (copdcmhout02.cable.comcast.com [96.114.158.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFBDF120121 for <netrqmts@ietf.org>; Wed, 31 Jul 2019 06:12:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190412; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1564578777; x=2428492377; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=qBpZbZ1zRaqWFBkbi60zKTTWAGrfkFe7dLGY7Bk8Vo4=; b=WCvqBg3EpsaCmZjfQodGlrTjpEV6DWPNr8y6usl9D+edgbdLXKXN0+a+NWSTlLSL HxLfXw5EejYId01KIL5rMJByxh7BiNpCleYXfk5Lut21yjQ0zUeIMYIcwF+i6eYx CfTjReYyi4Dsw9LUc5nxhxpvNyaMNCCiPf5huAydgh046FaHduSAQ1GhL8t0kEiY DBO/RDrgwu24pRES2tmfhW4+/Sl4KgguXC7YgpiRV7AyJrP8+SwDtP8EXbCIj1tL xezV/9MqmG6+NZdOf9NBQnXnYuuOgrT5PTTJU3LMzNNdc9l1ke1Sk7H5aT68UW4f vv839Pket8PmwZy5fZCCSw==;
X-AuditID: 60729ed4-227ff700000013e0-8c-5d4193d92143
Received: from COPDCEXC38.cable.comcast.com (copdcmhoutvip.cable.comcast.com [96.114.156.147]) (using TLS with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by copdcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id D2.35.05088.9D3914D5; Wed, 31 Jul 2019 07:12:57 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC38.cable.comcast.com (147.191.125.137) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Wed, 31 Jul 2019 09:12:56 -0400
Received: from COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94]) by COPDCEXC37.cable.comcast.com ([fe80::3aea:a7ff:fe36:8a94%15]) with mapi id 15.01.1713.008; Wed, 31 Jul 2019 09:12:56 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Toerless Eckert <tte@cs.fau.de>
CC: "netrqmts@ietf.org" <netrqmts@ietf.org>
Thread-Topic: [Netrqmts] IETF 105 Minutes
Thread-Index: AQHVRvONAYazPAoYaE2SZCvNTzAtR6bjzLqAgAASDICAAB0WgIAAuZGA
Date: Wed, 31 Jul 2019 13:12:56 +0000
Message-ID: <822E4995-72BB-4680-88B4-FBB2DC17B60A@cable.comcast.com>
References: <DF3803B7-C05B-4A31-B873-73A86B1416CE@vigilsec.com> <19915.1564514403@localhost> <20190730202439.zl6gjvzasxofvej2@faui48f.informatik.uni-erlangen.de> <27837.1564524525@localhost>
In-Reply-To: <27837.1564524525@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1b.0.190715
x-originating-ip: [68.87.29.9]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E164C1E5FFFF4A4284B7738C772A70F7@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrIKsWRmVeSWpSXmKPExsWSUDRnsu7NyY6xBn9+CFn0HOpntzj3Zzur xbnrv5kdmD1mbnzL6LFkyU8mj5Y5e5gDmKMaGG1KMopSE0tcUtNS84pT7bgUMIBNUmpaflGq a2JRTmVQak5qInZlIJUpqTmZZalF+liN0cdqTkIXU8b0NYuZCvpYK67u+cHSwPiHpYuRk0NC wETi1f7dbF2MXBxCAkeYJDacWMIMkhASaGGS+HpWAyJxmlHibu9WVpAEm4CZxN2FV8CKRAQC JVZv38UOYjMLaEtc2H6bDcQWFtCQaF8ygxGiRlNi4pZFUPVuEj++nACrZxFQlbjcdByohoOD V8BFYv7rPIi9Rxgldm3VB7E5gVoXTugEW8soICbx/dQaJohV4hK3nsxngnhAQGLJnvPMELao xMvH/8DqRQX0Jb6c2wT1pJzEsp93mEFWMQPNXL9LH2KMlcTDl21sELaixJTuh2CX8QoISpyc +QSqVVzi8JEdrBMYJWch2TwLYdIsJJNmIZk0C8mkBYysqxj5LM30DA1N9AxNLfSMDI02MYIT 0rwrOxgvT/c4xCjAwajEw1vX5xgrxJpYVlyZe4hRgoNZSYR3sbh9rBBvSmJlVWpRfnxRaU5q 8SFGaQ4WJXHevL06sUIC6YklqdmpqQWpRTBZJg5OqQbG/od68oa7HFueHF5pFGUscz3O9/YK A+9tHoGXprF/sS8x2Z3gFJL6+Jaib4gZ67FfARbvTsekCf/7GWwuLhFstNub/S3btveh10/O 6hebYhC7kUlMISdZi+n85NbneotXsNZ4FoUefOU2Mds7OihtqX06Rx23kXfBjygvxznlgTHl lhme35RYijMSDbWYi4oTASDB/HhEAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/netrqmts/7RQSoy8Nb8F8GrkcnxiW-L0SsPI>
Subject: Re: [Netrqmts] IETF 105 Minutes
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: Wed, 31 Jul 2019 13:13:01 -0000

On 7/30/19, 6:09 PM, "Netrqmts on behalf of Michael Richardson" <netrqmts-bounces@ietf.org on behalf of mcr+ietf@sandelman.ca> wrote:

>    We used to see those people, they were in the terminal room re-installing
    windows 98.   

It's not really for us to decide or judge IMO. I'd suggest we simply include a question in this area to gauge user preferences at the IETF and let their responses guide what sorts of network features & types are offered. 

Jason

v2.23.0 | Report a Bug | By Email