IETF Logo Mail Archive

Re: Opsdir last call review of draft-ietf-quic-manageability-14

"Brian Trammell (IETF)" <ietf@trammell.ch> Wed, 23 March 2022 10:17 UTC

Return-Path: <ietf@trammell.ch>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D0E3A0CC7 for <quic@ietfa.amsl.com>; Wed, 23 Mar 2022 03:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trammell.ch
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 R2m2EfnRAHHU for <quic@ietfa.amsl.com>; Wed, 23 Mar 2022 03:17:09 -0700 (PDT)
Received: from smtp-8faf.mail.infomaniak.ch (smtp-8faf.mail.infomaniak.ch [83.166.143.175]) (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 5987C3A0D27 for <quic@ietf.org>; Wed, 23 Mar 2022 03:17:09 -0700 (PDT)
Received: from smtp-3-0000.mail.infomaniak.ch (unknown [10.4.36.107]) by smtp-2-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4KNkmg0RmczMqMRW; Wed, 23 Mar 2022 11:17:07 +0100 (CET)
Received: from smtpclient.apple (unknown [IPv6:2001:67c:370:128:7911:4a4b:fb57:6494]) by smtp-3-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4KNkmf3Y13zlhRVh; Wed, 23 Mar 2022 11:17:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=trammell.ch; s=20191114; t=1648030627; bh=6J6/Ai7atRzslMIAkDiKxzmjoVpYdhaX0pudAwfYMvM=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=xeHwsNYchm06wAYK2NDv3du60VSZ5+vCT2OVCO9MYWMG8z1356DScQY4JSbYFFf6u VlpLAQPqMusdYqXkStno3qliWtNHJ8KmcIlUved5Z7yqQNSzLwqIqf2pHbdOW7UFct T7uevxQfEASAjDOZ6vjjKOQqKKUfr8B/wKLYNloQ=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: Opsdir last call review of draft-ietf-quic-manageability-14
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
In-Reply-To: <2191c163-bf91-2d35-6d93-4eb594cd5fe8@redbarn.org>
Date: Wed, 23 Mar 2022 11:17:04 +0100
Cc: Paul Vixie <paul=40redbarn.org@dmarc.ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-quic-manageability.all@ietf.org" <draft-ietf-quic-manageability.all@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D781BCF-9C70-40AF-AA3F-BED0A1A6CC51@trammell.ch>
References: <CH0PR02MB7980CA04E5EADBF6D25AD8F2D3319@CH0PR02MB7980.namprd02.prod.outlook.com> <D82872C2-4C79-45AB-92F1-9F27B324ADE0@ericsson.com> <CH0PR02MB79803C4AF8ED0F28A5F81D30D3009@CH0PR02MB7980.namprd02.prod.outlook.com> <5224BCAC-B8EC-4150-B3B1-5735056BC54C@ericsson.com> <CH0PR02MB798003A25A1C96D02F1FE525D3069@CH0PR02MB7980.namprd02.prod.outlook.com> <346C0025-B1CB-4CAF-BB23-A7E09D79E9B5@ericsson.com> <DM8PR02MB7973BBE35F26700D004BF9A3D3119@DM8PR02MB7973.namprd02.prod.outlook.com> <9f8d0243-c5c8-b335-96c8-57027e7da692@redbarn.org> <DB8CC21F-2F61-4553-B1A8-837252E81DA9@trammell.ch> <2191c163-bf91-2d35-6d93-4eb594cd5fe8@redbarn.org>
To: Paul Vixie <paul@redbarn.org>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fTB63ZOm22pBuOKQDEDTevtQEcc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Mar 2022 10:17:15 -0000

Hi Paul,

Cutting a bit to try to get this to concrete actions on the document; will follow up on the other points in a subsequent message...

> On 22 Mar 2022, at 17:25, Paul Vixie <paul@redbarn.org> wrote:
> <snip>
> perhaps this wording will be if lesser concern to you:
> 
> <<Identification of QUIC traffic by on-path actors such as network operators is not reliable. Therefore a heuristic along the lines of "any unrecognizable UDP traffic could be QUIC" is the least unappealing way for a network operator to characterize their network's UDP traffic in the QUIC era.>>

 I don’t think this fits editorially with the rest of the document. However, I do see your point that “not designed to be distinguishable” is maybe not strong enough. I also note that there’s something hiding in the rest of Section 3.1 that we should maybe make more explicit: “this traffic is definitely QUIC” is probabilistically doable, but there are better heuristics on a per-application basis.

How about something like:

<<The QUIC wire image is not specifically designed to be distinguishable from other UDP traffic by a passive observer in the network. While certain QUIC applications may be heuristically identifiable on a per-application basis, there is no general method for distinguishing QUIC traffic from otherwise-unclassifiable UDP traffic on a given link. Any unrecognized UDP traffic may therefore be QUIC traffic.>>

?

Cheers,

Brian

v2.23.0 | Report a Bug | By Email