Proposal to invoke a 7601bis effort

--===============4383254517518172933==
Content-Type: multipart/alternative; boundary="94eb2c082cdc19aa4e055f4d5fcb"

--94eb2c082cdc19aa4e055f4d5fcb
Content-Type: text/plain; charset="UTF-8"

In the context of work that is happening in the DMARC-WG, some changes to
RFC7601 have been discussed which we think may merit a 'bis' effort to
revise 7601.

If you are interested or care, please join the DMARC WG where the detailed
discussion will be carried out.

(Apologies for the wide posting, but we wanted to reach a broad group of
potentially interested parties.)

--Kurt Andersen

--94eb2c082cdc19aa4e055f4d5fcb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">In the context of work that is happening in the DMARC-WG, =
some changes to RFC7601 have been discussed which we think may merit a &#39=
;bis&#39; effort to revise 7601.<div><br></div><div>If you are interested o=
r care, please join the DMARC WG where the detailed discussion will be carr=
ied out.</div><div><br></div><div>(Apologies for the wide posting, but we w=
anted to reach a broad group of potentially interested parties.)</div><div>=
<br></div><div>--Kurt Andersen</div></div>

--94eb2c082cdc19aa4e055f4d5fcb--


--===============4383254517518172933==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ietf-822 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-822

--===============4383254517518172933==--