Hi Barry

Thanks for confirming that both status change and I-D are options that will be 
considered by the WG.

In my mind, the part that suggests this was more an RFC was this one: 

"This iteration of the DMARC working group is chartered for the sole purpose of 
completing this task,
sending it to the ** IESG for publication as an Informational item**."

Cheers,
Med

> -----Message d'origine-----
> De : Barry Leiba <[email protected]>
> Envoyé : mardi 31 mars 2026 15:03
> À : BOUCADAIR Mohamed INNOV/NET <[email protected]>
> Cc : The IESG <[email protected]>; [email protected];
> [email protected]
> Objet : Re: Mohamed Boucadair's No Objection on charter-ietf-
> dmarc-03-00: (with COMMENT)
> 
> 
> > CURRENT:
> >   Accordingly, DMARC is being rechartered to publish a document
> that moves RFC
> >   8617 to historical/obsolete status, including prose describing
> the history
> >   and current status of the work.
> 
> > ## Publishing a document allows for more elaborated
> considerations to
> > document the reasoning and ** lack of operational impacts ** for
> this
> > specific case. I don’t know if that work already started, but if
> the
> > prose is condense enough, proceeding with a “status change” may
> be
> > more appropriate. Maybe better to leave the decision about
> whether to
> > proceed with a new document or a status change open in the
> charter.
> 
> I'll note two things here:
> 
> 1. We're likely to have more text and more involved discussion
> than is appropriate for a status-change document, so we're almost
> certain to want an RFC here.
> 
> 2. The current text says "publish a document", not "publish an
> RFC".
> A status-change document *is* a document.  So we are not limiting
> anything here in that regard.
> 
> Barry, DMARC chair
____________________________________________________________________________________________________________
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.
_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to