Re: [tsvwg] path forward on L4S issue #16
"Holland, Jake" <jholland@akamai.com> Wed, 17 June 2020 21:12 UTC
Return-Path: <jholland@akamai.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 1C6993A0C85
for <tsvwg@ietfa.amsl.com>; Wed, 17 Jun 2020 14:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=akamai.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 3gb4ux3ZhPwi for <tsvwg@ietfa.amsl.com>;
Wed, 17 Jun 2020 14:12:23 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com
[IPv6:2620:100:9005:57f::1])
(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 D79AF3A0C8B
for <tsvwg@ietf.org>; Wed, 17 Jun 2020 14:12:22 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1])
by m0050102.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id
05HL5vgo002572; Wed, 17 Jun 2020 22:12:13 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com;
h=from : to : cc :
subject : date : message-id : references : in-reply-to : content-type :
content-id : content-transfer-encoding : mime-version; s=jan2016.eng;
bh=+dIqGW/VSrGTLUuix2gwWJ6UNAh1oULJMaSusCTRX7Q=;
b=oN7/T9XfhrhBe4FKIgBn+90fbbZgl5hD5eAL0ylQyLONMw6k9ekRAD6i5Fwy4G+1Z4DF
Rn1D9U7L2uxgLQ6XXnym6ufCbOoLzBaAxK2CRnV1lbTm2PJcDMSsWWudDnlPS1rAv9pO
KDpwHX9AUpAm+IyoPXJ1LLcrpEzBmMYii6ZI2q7UHbEukJyonfI6+VtIWs2uN7TQr6/0
93h+fNNIBtc0LxhvUcV+0X9wLR4U7cXxGSh95G4RamNfOIzXp4i0GP4qecvR3OW2Eu9u
f03V+GgZkWCkTH02lZC9DcNSvTMPWIVcUvjhr/bijf1jxfz32VwfkjSR9bzD0Vwfwv4c QQ==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]
(may be forged))
by m0050102.ppops.net-00190b01. with ESMTP id 31qqyfjvsf-1
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT);
Wed, 17 Jun 2020 22:12:13 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1])
by prod-mail-ppoint2.akamai.com (8.16.0.42/8.16.0.42) with SMTP id
05HL0fgN023729; Wed, 17 Jun 2020 17:12:12 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33])
by prod-mail-ppoint2.akamai.com with ESMTP id 31qjm1220n-1
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT);
Wed, 17 Jun 2020 17:12:12 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) by
usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP
Server (TLS) id 15.0.1497.2; Wed, 17 Jun 2020 17:12:11 -0400
Received: from usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) by
usma1ex-dag1mb6.msg.corp.akamai.com ([172.27.123.65]) with mapi id
15.00.1497.006; Wed, 17 Jun 2020 17:12:12 -0400
From: "Holland, Jake" <jholland@akamai.com>
To: Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org>,
"Rodney W. Grimes" <ietf@gndrsh.dnsmgr.net>, Jonathan Morton
<chromatix99@gmail.com>, Sebastian Moeller <moeller0@gmx.de>
CC: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "tsvwg@ietf.org"
<tsvwg@ietf.org>
Thread-Topic: [tsvwg] path forward on L4S issue #16
Thread-Index: AQHWPmflxF+ga8lui0+JiOujX3WmVqjQmKyAgAAGX4CAAATUAIAAF0yAgAAq6wCAAAwWgIAAuTMAgAAS/QCAAAv+gIAASXuAgAAREQCAB7ORgIADQc6AgAAK5ACAAAWgAIAAI86A///aPYA=
Date: Wed, 17 Jun 2020 21:12:12 +0000
Message-ID: <7B7C1BEC-9DBB-410E-BDFB-3337E071CA86@akamai.com>
References: <2DC5C89B-C979-4354-98D7-BBDBC78A42B1@gmail.com>
<202006171419.05HEJClG085550@gndrsh.dnsmgr.net>
<HE1PR0701MB287641121218FC0AA72F56B0C29A0@HE1PR0701MB2876.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0701MB287641121218FC0AA72F56B0C29A0@HE1PR0701MB2876.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.37.20051002
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.86.187]
Content-Type: text/plain; charset="utf-8"
Content-ID: <27A7FCA8EBA7ED4F899F17AD926B0276@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687
definitions=2020-06-17_11:2020-06-17,
2020-06-17 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
bulkscore=0 suspectscore=0
phishscore=0 mlxlogscore=687 adultscore=0 mlxscore=0 malwarescore=0
classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2004280000
definitions=main-2006170155
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.216, 18.0.687
definitions=2020-06-17_11:2020-06-17,
2020-06-17 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=662
impostorscore=0
suspectscore=0 priorityscore=1501 bulkscore=0 clxscore=1015 spamscore=0
lowpriorityscore=0 adultscore=0 mlxscore=0 cotscore=-2147483648
phishscore=0 malwarescore=0 classifier=spam adjust=0 reason=mlx
scancount=1 engine=8.12.0-2004280000 definitions=main-2006170158
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/1mphXvpLTXioL6oJOO7LA6k7aBk>
Subject: Re: [tsvwg] path forward on L4S issue #16
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>,
<mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>,
<mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 21:12:34 -0000
Hi Ingemar, One clarification: On 6/17/20, 9:27 AM, "Ingemar Johansson S" <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org> wrote: > So far I see only one firm evidence that RFC3168 AQMs are deployed and > enabled and these are related to the OpenWrt project, manifested in a few > upgradeable devices (and some not upgradeable) that can be bought in retail > stores. The rest is unconfirmed. If you're referring to the observations I sent, they are not linked to OpenWRT. I was looking at Akamai production traffic that saw ECE marks while delivering content to end users. Although many of the marking devices were likely CPE devices deployed by individual end users, there's reason to believe that several ISPs (what looks like a growing number) have some kind of managed deployment that has a much greater prevalence within their ASN than can be easily explained by individual users installing a custom CPE. I don't have any information on whether the marking devices inside these wider deployments within specific ASNs are predominantly CPE devices or whether they're one of the many routers or access devices that support CE-marking that they have now chosen to enable, after historically running it disabled. (This is not implausible, because the amount of traffic that will respond to the marks has changed substantially in the last few years.) HTH. Best regards, Jake
- [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Black, David
- [tsvwg] FW: path forward on L4S issue #16 Black, David
- Re: [tsvwg] FW: path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] FW: path forward on L4S issue #16 Steven Blake
- [tsvwg] Options for improving L4S safety alex.burr@ealdwulf.org.uk
- Re: [tsvwg] Options for improving L4S safety Jonathan Morton
- Re: [tsvwg] FW: path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Rodney W. Grimes
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Rodney W. Grimes
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Spencer Dawkins at IETF
- Re: [tsvwg] path forward on L4S issue #16 Holland, Jake
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Rodney W. Grimes
- Re: [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Black, David
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Paul Vixie
- Re: [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Holland, Jake
- Re: [tsvwg] path forward on L4S issue #16 Ingemar Johansson S
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Jonathan Morton
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller
- Re: [tsvwg] path forward on L4S issue #16 Holland, Jake
- Re: [tsvwg] path forward on L4S issue #16 Rodney W. Grimes
- Re: [tsvwg] path forward on L4S issue #16 Ruediger.Geib
- Re: [tsvwg] path forward on L4S issue #16 Scharf, Michael
- Re: [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Martin Duke
- Re: [tsvwg] path forward on L4S issue #16 Holland, Jake
- Re: [tsvwg] path forward on L4S issue #16 Rodney W. Grimes
- Re: [tsvwg] path forward on L4S issue #16 Wesley Eddy
- Re: [tsvwg] path forward on L4S issue #16 Sebastian Moeller