Re: [arch-d] Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11

"Murray S. Kucherawy" <superuser@gmail.com> Wed, 13 May 2020 06:58 UTC

MIME-Version: 1.0
References: <158920530782.23655.6622928751672901506@ietfa.amsl.com> <6.2.5.6.2.20200512152625.124c1588@elandnews.com> <d798d383-9bab-50f8-b6ee-dabb9cc37c2a@cs.tcd.ie> <6.2.5.6.2.20200512162358.0b239160@elandnews.com> <4548adba-834c-bfdd-36af-66b367408df8@cs.tcd.ie> <6.2.5.6.2.20200512191150.0bafa9a0@elandnews.com> <9161f68e-f51b-f97b-fc2b-372d24404209@cs.tcd.ie> <CAL0qLwZQxM+eDeZ+zFw3Gny7sy=jXi-1aUvE1B2RuO=M5CP_Sw@mail.gmail.com> <6.2.5.6.2.20200512232644.0d9328c8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20200512232644.0d9328c8@elandnews.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Tue, 12 May 2020 23:58:04 -0700
Message-ID: <CAL0qLwZkXJ+DqQqq=cwC__XsSqW4UkBkV9y0wpHhCiaajjvNhg@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: architecture-discuss@ietf.org, iab@iab.org, Barry Leiba <barryleiba@computer.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary="000000000000b6e8a305a5821a21"
Archived-At: <https://mailarchive.ietf.org/arch/msg/architecture-discuss/vg7y3X70juFjnleYIGCx0tQsLhw>
Subject: Re: [arch-d] Domain-based Message Authentication, Reporting & Conformance (dmarc) WG Virtual Meeting: 2020-06-11
Precedence: list

On Tue, May 12, 2020 at 11:35 PM S Moonesamy <sm+ietf@elandsys.com> wrote:

> >The meeting is being scheduled and operated as a typical WG interim
> >meeting, under IETF IPR rules and so forth, scheduled adjacent to a
> >M3AAWG session on the same topic.  The proximity is meant to
> >encourage participation in our forum by their members who are
> >typically fairly shy about doing so.
>
> I read
>
> https://au.news.yahoo.com/valimail-extends-email-security-standards-172300535.html
> I could not help noticing that DMARC is described as an IETF
> publication.  Is that accurate?
>

I imagine you are referencing the paragraph that starts "The IETF
previously published an informational RFC ..." and I imagine it is indeed
inaccurate.  The front page text of RFC 7489 makes it clear that it is a
"contribution to the RFC series" and that it is specifically not a
standards track document.

It does, however, say it is "Copyright (c) 2015, The IETF Trust".  The
distinction might be lost on some readers.

-MSK

Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Stephen Farrell
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Stephen Farrell
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Stephen Farrell
Re: [arch-d] Domain-based Message Authentication,… Murray S. Kucherawy
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Murray S. Kucherawy
Re: [arch-d] Domain-based Message Authentication,… Barry Leiba
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Barry Leiba
Re: [arch-d] Domain-based Message Authentication,… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Barry Leiba
[arch-d] Liaison reports (was: Domain-based Messa… S Moonesamy
Re: [arch-d] Domain-based Message Authentication,… Murray S. Kucherawy
Re: [arch-d] Liaison reports Wes Hardaker
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports Guntur Wiseno Putra
Re: [arch-d] Liaison reports Guntur Wiseno Putra
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports (was: Domain-based M… Mirja Kuehlewind
Re: [arch-d] Liaison reports (was: Domain-based M… S Moonesamy
Re: [arch-d] Liaison reports (was: Domain-based M… Bob Hinden
Re: [arch-d] Liaison reports (was: Domain-based M… Mirja Kuehlewind
Re: [arch-d] Liaison reports Alexandre Petrescu
Re: [arch-d] Liaison reports Wes Hardaker
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports Wes Hardaker
Re: [arch-d] Liaison reports S Moonesamy
Re: [arch-d] Liaison reports (was: Domain-based M… Spencer Dawkins at IETF
Re: [arch-d] Liaison reports Spencer Dawkins at IETF
Re: [arch-d] Liaison reports Mirja Kuehlewind