Hi, We will remove all figures in section 6 showing the different configurations of marking bits related to specific protocols. We will only mention in general that various experimentations has been done.
Regards, Massimo (and co-authors in CC) From: David Schinazi <[email protected]> Sent: venerdì 12 maggio 2023 21:05 To: Lucas Pardue <[email protected]> Cc: [email protected]; IETF IPPM WG ([email protected]) <[email protected]>; Bulgarella Fabio (Guest) <[email protected]>; Cociglio Mauro (outlook.com) <[email protected]>; [email protected]; Nilo Massimo <[email protected]> Subject: [EXT] Re: [ippm] QUIC concerns relating to draft-ietf-ippm-explicit-flow-measurements I agree with Lucas here. If the authors are in the process of writing separate drafts for how to encode this in COAP, QUIC, and TCP - then adding informational references to those drafts in an example section sounds like a good plan, but showing how to use specific bits in this draft (even in an appendix) without actually registering them will likely lead to confusion. David On Fri, May 12, 2023 at 10:25 AM Lucas Pardue <[email protected]<mailto:[email protected]>> wrote: Hi Nilo, On Fri, May 12, 2023 at 6:11 PM Nilo Massimo <[email protected]<mailto:[email protected]>> wrote: Hi, first of all thanks for the many comments received. As jointly agreed at the time with the chairs of the IPPM, QUIC and TSWG WGs, this draft is general and its purpose is to describe only the measurement methodologies in a protocol independent way. In order to describe their application to a certain protocol, it was agreed to present a specific draft in the related WG. So to give an example, with regard to the COAP protocol, this was done by submitting a draft in the CORE WG. See https://datatracker.ietf.org/doc/draft-ietf-core-coap-pm/ Therefore, with regard to the QUIC protocol, we will prepare a draft to be presented in the QUIC WG which will address the issues highlighted in this thread and details related to the possible future implementation. As for this draft https://datatracker.ietf.org/doc/draft-ietf-ippm-explicit-flow-measurements , we will write a new version of it where the section 6 will be placed in a draft appendix and renamed to Experimental Examples. In this way (we hope) it will be clear that we are talking about experiments made, and that they must not be interpreted as implementation. If the other co-authors agree, we can proceed to make a new version of the draft. Given that section 6 just seems to be a trivial presentation of how to assign bits in QUIC's 7 bit space, I don't really see what the value of talking about any specifics are. What benefit would the authors see in keeping an appendix? Cheers Lucas Gruppo TIM - Uso Interno - Tutti i diritti riservati. Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. Rispetta l'ambiente. Non stampare questa mail se non è necessario.
