IETF Logo Mail Archive

Re: [tsvwg] design assumptions - draft-ietf-udp-options

Joe Touch <touch@strayalpha.com> Wed, 17 July 2019 19:03 UTC

Return-Path: <touch@strayalpha.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 471A0120873 for <tsvwg@ietfa.amsl.com>; Wed, 17 Jul 2019 12:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level:
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=strayalpha.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 lyby8_j7Xtqi for <tsvwg@ietfa.amsl.com>; Wed, 17 Jul 2019 12:02:59 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 ED77A120026 for <tsvwg@ietf.org>; Wed, 17 Jul 2019 12:02:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=QWoZcDgy5K0Sci+d0+qx6OtYc3VpUShYT1CpVHUblwE=; b=FYcuFrV0rDFiYersQKjqVS1hu FvjDyIUPpv1xrwPQIdvInRVFdeexK67PNFSrAQcjAd11Jmd4ulPOzAIGYnIu4fLybfltpNb9PTzXA sXq1AoBDGtByYHKaFqxJo9A5n8aXN+hZUcP5eSehXAV9u9gWs+MlZaMmq+ZB0c4DE2KdckVFNYJ/P ZHEIkpgvn5In1oNoaQ8TXNjnleXqpV8HkhERm+pCroEdLScKbyuQCio2JoNFwaPVH9TvBVpCDtxFb bbEEEW8eX/cAPVP2BIEPvbl6EFKb2dHTtXu4awEgAU1TDJu8wITgVz2u5uzQ4i+bbOfb2RmwoYdvU wqadUHDtg==;
Received: from [38.64.80.138] (port=58302 helo=[172.21.27.119]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1hnpCX-003XPx-CX; Wed, 17 Jul 2019 15:02:58 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
X-Mailer: iPhone Mail (16F203)
In-Reply-To: <CACL_3VGS8-3susS-qm3oDD3=fwT6QmRa4_hgceJKhqjz3n+H5Q@mail.gmail.com>
Date: Wed, 17 Jul 2019 12:02:53 -0700
Cc: "Black, David" <David.Black@dell.com>, tsvwg <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <390A2B45-8981-42B5-A758-74B59BD7A6B4@strayalpha.com>
References: <CAPDqMeq9GjEQKukH1pZOTdE50e_rc3U6gpdxT-5qrS5phD0RGw@mail.gmail.com> <646D45AD-D79B-4BD2-A084-7DA97CE2C415@strayalpha.com> <7EC37B50-45D5-4CF1-B113-205E55BF244E@strayalpha.com> <CALx6S34s7L7xo+26bt5Cdaqi4Es5Aci42GHk1WNKzugr5st-Gw@mail.gmail.com> <B525BF50-EFCC-44A5-A604-6CDDA914A1CB@strayalpha.com> <CAPDqMep3R6z9PRKkHyOvrh6sV9n5Sc0B++-zVz0FYJCwE6swrQ@mail.gmail.com> <E42A2AE2-F499-465E-BDE6-5EFC0AB20042@strayalpha.com> <CE03DB3D7B45C245BCA0D24327794936306138E9@MX307CL04.corp.emc.com> <CAPDqMeoyNb7vQTdqxLpZpnKb9S7QKeDJNLyQJBmq95yXhB+xfQ@mail.gmail.com> <7D365770-64FE-40BC-901D-B4D7DF6B484B@strayalpha.com> <20190713182554.GB39770@clarinet.employees.org> <CALx6S36mH2M6SYnRSecWXa7k_d1u8O43+CXE-=KqeO0x2e5+qw@mail.gmail.com> <82FF6486-FABF-4D2C-B5E2-178779C720A4@strayalpha.com> <30c17e9c174f6b0da3ecc6b503a8cb17@strayalpha.com> <CACL_3VGs7j+y5vFNT3OL9OKX8ue4rv-Cxi467KR-vbhnMdx86g@mail.gmail.com> <2f71a292f924a9b8de4227c4bbc2f809@strayalpha.com> <0ce46e21249f0dc55310b192d382f50a@ strayalpha.com> <CALx6S36gaMqNRo_hYKr45T_vTkUB-vRrYRYJz2_KgvejNsJtLQ@mail.gmail.com> <efbf65646a0e0d2535dc5726b34f3472@strayalpha.com> <CALx6S37sZxmGQJq5mxDiF88NeUjj2HMRnQG5KyZA_4ujrLJkqg@mail.gmail.com> <079d7d849d0e6260497a6c0ed37595a2@strayalpha.com> <CALx6S37wOkz0436CmevOjSe=VwAxKstSR9Jc66PUmXwUKK4vBw@mail.gmail.com> <075C3166-DF88-4160-8E6C-1C32511F4D46@strayalpha.com> <811C4C35-48D8-4382-A4B4-784FAC1B9F1D@strayalpha.com> <CE03DB3D7B45C245BCA0D2432779493630620745@MX307CL04.corp.emc.com> <80BB381B-9B2F-4ACF-9F3A-27E7B8B10AC2@strayalpha.com> <CE03DB3D7B45C245BCA0D24327794936306212A0@MX307CL04.corp.emc.com> <CACL_3VGS8-3susS-qm3oDD3=fwT6QmRa4_hgceJKhqjz3n+H5Q@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/6uwPjqqG4n0X485iHBUy3tztae4>
Subject: Re: [tsvwg] design assumptions - draft-ietf-udp-options
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 Jul 2019 19:03:00 -0000


> On Jul 17, 2019, at 11:20 AM, C. M. Heard <heard@pobox.com> wrote:
> 
> 9 - any option that affects the handling of payload data must share fate with that payload data, by all receivers (legacy or otherwise)
> 
> The clarification to #3 that I would like to see is whether "required" means:
> (a) "required for any conforming implementation to support" or
> (b) "required by the receiver in every packet"
> 
> I ask because the term is used both ways in draft-ietf-tsvwg-udp-options-07.

The confirming implementations support the core options as listed. We can’t add to that list on the fly. 

Required by receivers ought to be decided by receivers, as is the case for the only current UDP choice (CS=0)

> Either way, I think everything on the list is achievable.

I don’t see how unless the user data is presented twice / once for legacy and a different way for option-aware. 

And that ought to be another design goal to avoid. 

Joe

v2.23.0 | Report a Bug | By Email