Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-14.txt

[[e-mail]]

Hi Joe,

Thanks for this update.


I see that your suggestion to tag REQ/RES as required was already implemented in -14. I support maintaining that change. With this change, I consider that the point currently discussed in the dplpmtud-03 thread is closed. Still, some tweaks are needed to the dplpmtud I-D to sync with udp-options-14.

Joe, please find below a nit and a change:

(1)


OLD: 7*      6         Response (RESP)

NEW: 7*      6         Response (RES)



(2) Please add an explicit pointer to the section where fragmentation is discussed in dplpmtud:



OLD:

   Note also that the FRAG option is

   not used when sending DPLPMTUD probes to determine a PLPMTU [Fa22<https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-14#ref-Fa22>].



NEW:

   Note also that the FRAG option is

   not used when sending DPLPMTUD probes to determine a PLPMTU (Section 4.1<https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-dplpmtud#section-4.1> of [Fa22<https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-14#ref-Fa22>]).



Thank you.

Cheers,
Med

De : tsvwg <[e-mail]> De la part de [e-mail]
Envoyé : mercredi 2 mars 2022 06:39
À : TSVWG <[e-mail]>
Objet : Re: [tsvwg] I-D Action: draft-ietf-tsvwg-udp-options-14.txt

PS - note that I’m also suggesting that REQ/RES be included in the required options, otherwise we won’t get PLPMTUD off the ground.

And ACS was renamed to APC (alternate payload checksum), to avoid confusion with OCS (which is a checksum on the options area).

Again, LOTS of changes.

Note also that this is one of my first uses of an alternate publication pipeline, using Word -> PDF -> text directly on a Mac, without use of a PC and a “text only” printer. So if there are any errant spaces (e.g., in the middle of words), please ignore (and it would be helpful to let me know).

Joe

—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com<http://www.strayalpha.com>


On Mar 1, 2022, at 9:35 PM, [e-mail]<mailto:[e-mail]> wrote:

Hi, all,

LOTS of changes. Mostly as discussed in past IETF reports, focusing on:
- moving OCS to a required field
- moving UNSAFE options to a simper, reserved subset of the kind range

I also did a full deep pass for clarity through the first 7 sections.

I *tried* to keep up with the >100 messages and update suggestions, but won’t pretend I caught them all. Any omissions are my fault; please let me know if you notice any I missed.

Joe
—
Dr. Joe Touch, temporal epistemologist
www.strayalpha.com<http://www.strayalpha.com/>


On Mar 1, 2022, at 9:31 PM, [e-mail]<mailto:[e-mail]> wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transport Area Working Group WG of the IETF.

       Title           : Transport Options for UDP
       Author          : Joe Touch
             Filename        : draft-ietf-tsvwg-udp-options-14.txt
             Pages           : 39
             Date            : 2022-03-01

Abstract:
  Transport protocols are extended through the use of transport header
  options. This document extends UDP by indicating the location,
  syntax, and semantics for UDP transport layer options.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-udp-options/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-udp-options-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-udp-options-14


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts




_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.