Ruben Safir writes:
> RFCs are a record of a process.
Partially true. The process almost invariably leaves its trace in the
text, and (as in any committee work) many compromises are inexplicable
without reference to the process. But the text of an RFC is a
specification, not a narrative.
> U
On 10/23/2017 12:57 AM, Stephen J. Turnbull wrote:
> Grant Taylor via Mailman-Users writes:
>
> > RFC 6377 - DomainKeys Identified Mail (DKIM) and Mailing Lists,
> > disagrees with you. (RFC 6377 is also currently known as BCP 167.)
>
> tl;dr version: RFC 5598 (non-normative but authoritative
Grant Taylor via Mailman-Users writes:
> RFC 6377 - DomainKeys Identified Mail (DKIM) and Mailing Lists,
> disagrees with you. (RFC 6377 is also currently known as BCP 167.)
tl;dr version: RFC 5598 (non-normative but authoritative) disagrees
with you. In practice, the mailing list *decides*
