Re: [Add] meeting hum: should the IETF take up this work?

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

Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B407A12063F for <add@ietfa.amsl.com>; Wed, 31 Jul 2019 10:29:17 -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 sY56U8FHMRLS for <add@ietfa.amsl.com>; Wed, 31 Jul 2019 10:29:16 -0700 (PDT)
Received: from copdcmhout01.cable.comcast.com (copdcmhout01.cable.comcast.com [162.150.44.71]) (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 0CE9312060B for <add@ietf.org>; Wed, 31 Jul 2019 10:29:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=comcast.com; s=20190412; c=relaxed/simple; q=dns/txt; i=@comcast.com; t=1564594134; x=2428507734; 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=dcKDHCtgGDOurlwqpH35QQPC/yB893U7a4jSpHaWRpQ=; b=vZPJxkRcFjVLaI1WgR94rwc4HAS0wGYDxiUbt+melphIy+Xnfk8lyHdGBjJ7jhY0 9J7kRdQUv6xuw0wZBWbeXW3hfc/1bOWsh7cvj5kDl1106E53yF0qVcUuhMYaS3Kl +cFZtK6JxlEfCR8XsaxpSpuFKW4gY11HlLu0Lpvxh1GkHf/T/TzAt9G4S0MEBkM1 eMqtabnwM/8bUJEFnV50EHZeXQpTJPycG1QXYP03WIgOJvPitAHAPGRxuVUbEKa4 /HUSp0Ng/jNvREnrtZuAAf8/ujLF06dBunnmnuYkq6Vd6PEACFlT2YJOjQoGe4t3 m47UDGxKTFEK4fKVVsdbMA==;
X-AuditID: a2962c47-a9fff7000002e144-51-5d41cfd68cf0
Received: from COPDCEXC40.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 copdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 44.D7.57668.6DFC14D5; Wed, 31 Jul 2019 11:28:54 -0600 (MDT)
Received: from COPDCEXC37.cable.comcast.com (147.191.125.136) by COPDCEXC40.cable.comcast.com (147.191.125.139) 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 13:29:08 -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 13:29:08 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "add@ietf.org" <add@ietf.org>
Thread-Topic: [Add] meeting hum: should the IETF take up this work?
Thread-Index: AQHVR8V1WrgBv7BM8EegWWPMEALeFA==
Date: Wed, 31 Jul 2019 17:29:08 +0000
Message-ID: <745AC544-A6E0-45E4-A571-4EF2A47F77CA@cable.comcast.com>
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: [96.114.156.8]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E199C406495C7145B306537CD68543D8@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJIsWRmVeSWpSXmKPExsWSUDRnsu61846xBiubJCz+n17H5sDosWTJ T6YAxqgGRpuSjKLUxBKX1LTUvOJUOy4FDGCTlJqWX5TqmliUUxmUmpOaiF0ZSGVKak5mWWqR PlZj9LGak9DFlLFixVXWgnvMFT13LzA1MF5g7mLk5JAQMJHY++cPWxcjF4eQwBEmiV/7djND OC1MEo8ev2GHcE4zShx8+4sFpIVNwEzi7sIrYO0iAooSjRvvMILYwgJOEkvvL2aHiDtLPN76 CSjOAWTrSXQdzQQJswioSiw6fRSslVfAReL1zG9MIDajgJjE91NrwGxmAXGJW0/mM0FcJyCx ZM95qEtFJV4+/scKYosK6Et8ObeJBSKuILF9/zYWkFXMApoS63fpQ4yxknh86iYzhK0oMaX7 ITvEWkGJkzOfQLWKSxw+soN1AqPYLCSbZyFMmoVk0iwkk2YhmbSAkXUVI6+hmZGeoamBnomJ nrnhJkZgglg0Tcd9B+OH87GHGAU4GJV4eI+ecowVYk0sK67MPcQowcGsJMK7WNw+Vog3JbGy KrUoP76oNCe1+BCjNAeLkjjv4ckasUIC6YklqdmpqQWpRTBZJg5OqQZG2XOM1W0qtt6rwvdf Scz1Vay6d3/fly3piVOLgr06ZVpFXzFlaffqdRjWf9j2PkPLX/dKj0xeF/dRxVvuDSfVtHR7 vmaYzo7ItTUP9xd+avyj7NvHZ0rvf9u+Ng5ettum/NYGs/PR1w2v7hAKDbmfeeNr6uc1945z 1BovbAnKXrb4l+sD7yYlluKMREMt5qLiRAABgB+nDAMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/22bHppdMcJPXxLerwBW0udpJwxs>
Subject: Re: [Add] meeting hum: should the IETF take up this work?
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jul 2019 17:29:25 -0000

From: Eric Rescorla <ekr@rtfm.com>
> This seems to be assuming a number of facts about how ISPs behave that are not in evidence.

ISPs, like browsers and search portals, do not all have the same business models, practices, and cultures. Just as the Firefox browser is very different from Google Chrome, then so too is ISP-1 from ISP-2.