Re-, Please see inline.
Cheers, Med > -----Message d'origine----- > De : Michael Richardson <[email protected]> > Envoyé : lundi 6 mai 2024 12:18 > À : BOUCADAIR Mohamed INNOV/NET <[email protected]>; > [email protected] > Objet : Re: [OPSAWG] advancing PCAP drafts > > > {please ignore unicast message I sent thirty seconds ago} > > [email protected] wrote: > > I think that it would be useful to have a new column to > easily tag the > > status of an assignment. Deprecated ones can be marked as > such using > > that new column, instead of having this in the description. > > okay, I couldn't quite understand this from the diff, but in > principal I have no problem with that. [Med] Actually, I didn't make that change in the PR as I wanted to discuss it first here. As you are Ok with it, so please update the table accordingly. Thanks. > > > For the DE guidance, I'm afraid that the first part of your > text is redundant with what is already in 8126, especially this > part: > > > For the Specification Required policy, review and approval > by a > > designated expert (see Section 5) is required, and the > values and > > their meanings must be documented in a permanent and > readily > > available public specification, in sufficient detail so > that > > interoperability between independent implementations is > possible. > > So, a reason why I wrote that slight redundant text is so that > the engineer who is trying to get their marketing person to put > the document out in a sane place, would have a single place to > point to. [Med] Yeah. I think the text in 8126 is well enough. > But, if the WG feels that redundant, I can go with that. > > -- > Michael Richardson <[email protected]>, Sandelman Software > Works > -= IPv6 IoT consulting =- *I*LIKE*TRAINS* ____________________________________________________________________________________________________________ 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. _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
