Re: [tsvwg] (transport) RE: Advance notice on request to poll TSVWG for adoption of draft-kaippallimalil-tsvwg-media-hdr-wireless-03

"C. M. Heard" <heard@pobox.com> Tue, 31 October 2023 15:10 UTC

Return-Path: <heard@pobox.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 9FFC3C16F41E for <tsvwg@ietfa.amsl.com>; Tue, 31 Oct 2023 08:10:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.806
X-Spam-Level:
X-Spam-Status: No, score=-2.806 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhK8EHcdsg7E for <tsvwg@ietfa.amsl.com>; Tue, 31 Oct 2023 08:10:55 -0700 (PDT)
Received: from pb-smtp21.pobox.com (pb-smtp21.pobox.com [173.228.157.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED70CC1705E7 for <tsvwg@ietf.org>; Tue, 31 Oct 2023 08:10:45 -0700 (PDT)
Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 0ECC91B49A for <tsvwg@ietf.org>; Tue, 31 Oct 2023 11:10:45 -0400 (EDT) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=WcrokE0PR4TtUJXKwlPgX90/Vf2HMCAS DWIzkmA1Snc=; b=SvV482yQMOOLUs/50NgSf3ILjahJh8gX+wGhlJS69seukECq 1Epl28zQOYMFeCWvRuYKZCwY2y6yp+jvpagqmFHE1UzV+XUk5/NIh21r/sMJZNCr gUq0gsTPxndoOyswDCh/RMWewLps3usV0cc7ka1KbVFTTwkat6M0+b721EM=
Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 06E521B498 for <tsvwg@ietf.org>; Tue, 31 Oct 2023 11:10:44 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-ed1-f49.google.com (unknown [209.85.208.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id D19D61B496 for <tsvwg@ietf.org>; Tue, 31 Oct 2023 11:10:40 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-ed1-f49.google.com with SMTP id 4fb4d7f45d1cf-5406c099cebso9034156a12.2 for <tsvwg@ietf.org>; Tue, 31 Oct 2023 08:10:40 -0700 (PDT)
X-Gm-Message-State: AOJu0YxeiNCxoTGosQUy1WnesFfqca6NkfkjWAxggWppUpXgzxhbc5o3 yOES3mR76qR5w5OhVuUVnH+MaYGYthiZYUaViCQ=
X-Google-Smtp-Source: AGHT+IERBh05VQ1wx3o5SBn3Xvl81g+QIWT8FmByR+l0G4P80zdam9CzI90ASk4ozv8+CZal2w2vC7jPGoFMXNVUQ6M=
X-Received: by 2002:a17:906:da87:b0:9c5:7a7:3752 with SMTP id xh7-20020a170906da8700b009c507a73752mr11927696ejb.26.1698765038638; Tue, 31 Oct 2023 08:10:38 -0700 (PDT)
MIME-Version: 1.0
References: <CAKKJt-cr7e5pUR=zxaO35Tjn2d=oM-xBvpdyGop+xaLOG-_U9g@mail.gmail.com> <CALx6S34__pK8tTM08fzTAxx=_dAM4MsEwH1-RL7eXGrCdtnR1Q@mail.gmail.com> <7E9754EA-9A11-49F6-A3F2-3F5E630CEBA6@strayalpha.com> <SN4PR13MB5311CF46AF56025360252C3AE8DCA@SN4PR13MB5311.namprd13.prod.outlook.com> <CALx6S378sTLPzis3=qB07OvojjbCTV8St21-31_oZzsUNZ-5vA@mail.gmail.com> <3D728108-E440-4625-BC4F-F1D134C1BD63@gmx.de> <CALx6S36G3s6UjfLXoxdotGoJaaQgXDhBCTVJi=j8=NhQQDUMWw@mail.gmail.com> <CACL_3VFvjNXGWh3jUg7b21z6f8uWQr8aKe_Lok+gqt-_jy1XKg@mail.gmail.com> <SN4PR13MB5311ADF5015B050B3595C121E8A0A@SN4PR13MB5311.namprd13.prod.outlook.com>
In-Reply-To: <SN4PR13MB5311ADF5015B050B3595C121E8A0A@SN4PR13MB5311.namprd13.prod.outlook.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Tue, 31 Oct 2023 08:10:24 -0700
X-Gmail-Original-Message-ID: <CACL_3VHNm9R2X3b8cCX5sScZtPS=Md6KXic4-TpOU8Qqkg1QMg@mail.gmail.com>
Message-ID: <CACL_3VHNm9R2X3b8cCX5sScZtPS=Md6KXic4-TpOU8Qqkg1QMg@mail.gmail.com>
To: Kaippallimalil John <john.kaippallimalil@futurewei.com>
Cc: Sri Gundavelli <sgundave@cisco.com>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Tom Herbert <tom@herbertland.com>, Sebastian Moeller <moeller0@gmx.de>, Joe Touch <touch@strayalpha.com>, TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000af5e300609048e47"
X-Pobox-Relay-ID: A7AF684C-77FF-11EE-BE52-A19503B9AAD1-06080547!pb-smtp21.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/ls8sEAzFULpQ8zszecV80IeQYjw>
Subject: Re: [tsvwg] (transport) RE: Advance notice on request to poll TSVWG for adoption of draft-kaippallimalil-tsvwg-media-hdr-wireless-03
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 31 Oct 2023 15:10:59 -0000

On Tue, Oct 31, 2023 at 7:20 AM Kaippallimalil John <
john.kaippallimalil@futurewei.com> wrote:

> Hi,
>
> Thanks for this feedback. Much of it has been factored into the proposed
> revision to use MED in outer packet UDP option for now.
>
> Further responses tagged with [JK]:
>
> > But the big elephant in the room is that draft-ietf-tsvwg-udp-options
> > exclusively defines TRANSPORT options designed to be consumed by
> > endpoints, not NETWORK options designed to be inspected by routers or
> > other middleboxes. If draft-kaippallimalil-tsvwg-media-hdr-wireless-03
> > is to be adopted as a basis for future work, then in my opinion one of
> the
> > adoption questions should be whether the WG would be willing to make this
> > change of direction to draft-ietf-tsvwg-udp-options.
> >
> > The rather lengthy previous discussion pretty much left this last point
> up in
> > the air, but I came away with the conclusion that trying to fix
> > IPv6 HbH options is probably the better alternative in the long run.
>
>         [JK] The authors discussed this and related notes from Alex with
> the various trade-offs of each of the transports.
> For this draft, MED in outer UDP packet option from server (Provider-A) to
> wireless node (Provider-B) is sufficient.
> The only potential drawback may be that the option at the end of the
> packet may affect performance, or may not depending on the implementation.
>

If there is no inspection by middleboxes, just generation/consumption by
tunnel endpoints, then the usage of UDP Options would be as intended in the
current specification, and the elephant will have quietly exited the room.

The possibility still exists to use per-fragment options to address the
performance issues, as those are currently in the UDP Options spec. If that
is seen as desirable or useful, and if it would predominantly be used with
atomic fragments, it may be possible to add a 3rd FRAG option format for
this purpose (it would have utility in more general situations).

Mike Heard