Re: [tsvwg] draft-ietf-udp-options issues from IETF 104

Tom Herbert <tom@herbertland.com> Sun, 21 July 2019 02:27 UTC

Return-Path: <tom@herbertland.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 5173312007C for <tsvwg@ietfa.amsl.com>; Sat, 20 Jul 2019 19:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 rOwD8H57NXqR for <tsvwg@ietfa.amsl.com>; Sat, 20 Jul 2019 19:27:47 -0700 (PDT)
Received: from mail-ed1-x541.google.com (mail-ed1-x541.google.com [IPv6:2a00:1450:4864:20::541]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76F4A12006A for <tsvwg@ietf.org>; Sat, 20 Jul 2019 19:27:47 -0700 (PDT)
Received: by mail-ed1-x541.google.com with SMTP id s49so2888956edb.1 for <tsvwg@ietf.org>; Sat, 20 Jul 2019 19:27:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fMPgc8xSlLK4uSQUvolMq3/ajCHtGE/+jpgxt2T0z0g=; b=bLKaIdGL7QsSIfvE8DxeW/Z7x5kjwx0ks7MaqeN4+n5ifusFkKa1ty+qGq8DTWw09D GzM52j+1hnwtaYcZMN0R5fAJlKyZX05wG/Vz57e0QuIXESqHx8DrznuAQlY1Vl6D37d0 b/t1ktu6BcaqhkmqXAk1FZh0lgzXj/pyUOUAwvppTKn6eT+pevB4rRwpK7ORG26100La 8j7i8Od2XcWkkG80q22BP+JCsQaeDDMBc8apWEYs7ropQwSqGlb1kGKXeP4IS2MEq1nC UCvUJaTpOanAt1NS9EIYe/2sg5agVumgA+/NBzk/1cGNJUyEbSbNin/Xy5HjUMfl/Jok whAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fMPgc8xSlLK4uSQUvolMq3/ajCHtGE/+jpgxt2T0z0g=; b=qchsQDaA5e4Nll080OMuiMuDQNNEpYuGNXQWMMBNjioQ2PN3jMRzhCgLyCEundEHg3 Y+7jJmeqSUMTQaKrEMli0aZiTx4ob/buRQ2bon0YWF2KC0LXliE1SqMZhXHZ/3n3LDhx bkCKMBQSWH1YCnYqsjt9gGkvJsi3RMYM1S8SGnoiFsLq90T+Ox8m4yv290iUI1iETKoT D7zOKMgcjTWmS5yLvnpD65H7u4kPAi/CagRXLV0DSgle3PZeM/j9Lw6uoy3YPWoSYDnk bsy3cZQUel2g5cVXvYGoaZY0aItHaKqLqKMKRn4hXayZ32FmmOvyEZQqMrJB90B6h0vM Yx/A==
X-Gm-Message-State: APjAAAXEy/0PI9+GP+uCo053WKtziV9IEhqFQMwjdPpJ3TeFLeDVWXLR FqCIUS/4CmrzOErdWdspYtpI69GKDp5hhniIhtU=
X-Google-Smtp-Source: APXvYqw6T32uUFLTbXgiqFrRtK4NCuRvUAH6M0nc05QvUht1KNzwQNE8gIW4izHQWnaQcXjah9WbKVjLQwNrc9/QtDY=
X-Received: by 2002:a17:906:5806:: with SMTP id m6mr47560510ejq.80.1563676065813; Sat, 20 Jul 2019 19:27:45 -0700 (PDT)
MIME-Version: 1.0
References: <CACL_3VGL2irCkZeEcP+9HLBHqtqaMPZM66youUsatzosUu=Aew@mail.gmail.com> <A07EA390-1A3A-4AE9-AFD7-2F22CD4B0E31@strayalpha.com> <CALx6S34oOza3Z4Ymjsp+HLXnSTOKwh+SAQO8mt=a-1AbTTB0GQ@mail.gmail.com> <177233bb33272ce3b64298a005254724@strayalpha.com> <CALx6S36ZBa4Bioj=0KYn7wcFi08VeAg8sHUHLRNGURsrUN673w@mail.gmail.com> <5D30B36D.80409@erg.abdn.ac.uk> <CALx6S37EauLMyeksHJ3iPNjKwLTv5qti_Hf0a2QTdzZoDrarrw@mail.gmail.com> <F1092EE4-16DC-4292-903E-F54A447E6A8D@strayalpha.com> <CALx6S340gCTQiA85iVXwnbA8nU8=nvWnGq7q3jzuG7SuVHv=ag@mail.gmail.com> <DE387BB9-BA9D-447E-9767-FD0428B7F1D7@strayalpha.com> <20190720215636.GA66376@clarinet.employees.org> <CACL_3VGbd_91cP2jrOigRc=rt3bOoarmbNqG5ma+iSgf0ABDtw@mail.gmail.com> <CE03DB3D7B45C245BCA0D243277949363062AB13@MX307CL04.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949363062AB13@MX307CL04.corp.emc.com>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 20 Jul 2019 19:27:34 -0700
Message-ID: <CALx6S35hgRzgnhKOC6SzFjqfaWGpqD4=wKH5AV1DqH0Q3eHeDQ@mail.gmail.com>
To: "Black, David" <David.Black@dell.com>
Cc: "C. M. Heard" <heard@pobox.com>, Derek Fawcus <dfawcus+lists-tsvwg@employees.org>, tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/L8-F4bXsSzZNMkcmh8L-0b7ng54>
Subject: Re: [tsvwg] draft-ietf-udp-options issues from IETF 104
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: Sun, 21 Jul 2019 02:27:49 -0000

On Sat, Jul 20, 2019 at 6:50 PM Black, David <David.Black@dell.com> wrote:
>
> Still as an individual ...
>
> > What I was actually advocating was that in the presence of any option marked
> > "drop if unknown" there MUST NOT be any legacy data, i.e, such options
> > could not appear in the trailer format. All payload would have to be in the
> > surplus area (which requires the header format). In that case, "drop the
> > packet" and "drop the surplus" would amount to the same thing.
>
> That would "freeze" LITE - if we ever found anything problematic with LITE and wanted to replace it with LITE2, that replacement would be prohibited by such a requirement.
>
David,

This is why having a version number, variant number, or the like in
the surplus area header is so critical.

Tom

> NB: *replace* is crucial in this context - this is not about trying to use both LITE and LITE2 in the same packet.
>
> Thanks, --David
>
> > -----Original Message-----
> > From: tsvwg <tsvwg-bounces@ietf.org> On Behalf Of C. M. Heard
> > Sent: Saturday, July 20, 2019 8:51 PM
> > To: Derek Fawcus
> > Cc: tsvwg
> > Subject: Re: [tsvwg] draft-ietf-udp-options issues from IETF 104
> >
> >
> > [EXTERNAL EMAIL]
> >
> > On Sat, Jul 20, 2019 at 2:56 PM Derek Fawcus wrote:
> > > I suspect we should interpret "drop the packet" here for options marked
> > > as "drop if not known" to actually mean "discard the surplus".
> > >
> > > i.e. if a non-legacy receiver in processing the surplus finds such an
> > > option, it then switches to operating in legacy mode for that packet.
> >
> > I do not agree.
> >
> > > Which means that like the legacy receiver, it will either see a zero length
> > > UDP packet (if UDP payload length was zero) or see whatever legacy UDP data
> > > was passed in the non-surplus area.
> >
> > What I was actually advocating was that in the presence of any option marked
> > "drop if unknown" there MUST NOT be any legacy data, i.e, such options
> > could not appear in the trailer format. All payload would have to be in the
> > surplus area (which requires the header format). In that case, "drop the
> > packet" and "drop the surplus" would amount to the same thing.
> >
> > Mike
>