Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing

[Eliot Lear <[e-mail]>]

On 04.06.21 13:50, [e-mail] wrote:
>
> Re-,
>
> It is also ours as participants, Carsten.
>
> If you really want to make sure that extension is considered by a MUD 
> implementer (and this is really about the augment thing), you can 
> consider defining version 2 of the mud module in the ol I-D. This is a 
> much more clean design to convey the message you want.
>
I don't know that we want to tell v1 implementations that they SHOULD 
NOT parse the rest of the file because of this.

Eliot

> Cheers,
>
> Med
>
> *De :*Carsten Bormann [mailto:[e-mail]]
> *Envoyé :* vendredi 4 juin 2021 12:13
> *À :* BOUCADAIR Mohamed INNOV/NET <[e-mail]>
> *Cc :* Michael Richardson <[e-mail]>; [e-mail]
> *Objet :* Re: [OPSAWG] please see draft-lear-opsawg-ol on licensing
>
> On 4. Jun 2021, at 11:34, <[e-mail] 
> <mailto:[e-mail]>> <[e-mail] 
> <mailto:[e-mail]>> wrote:
>
>     What I'm really concerned about is consistent use of the "update"
>     header.
>
> That’s the IESG’s job — above my paygrade :-)
>
> What I’m concerned is that 8520 readers find a pointer to the new 
> document.
>
> An “updated by” on the (metadata rich versions of) 8520 raises the 
> likelihood substantially.
>
> Which is more important than any concept of consistency (which we 
> won’t really have until the IESG is done with Mirja’s proposals).
>
> Grüße, Carsten
>
> _________________________________________________________________________________________________________________________
>
> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/opsawg