A terminology nit, but it's going to come up in the future so I'd like to
put it out there early before we have a big re-editing job to do:
On Wed, Mar 26, 2025 at 1:23 AM Wei Chuang <weihaw=
40google....@dmarc.ietf.org> wrote:
> This is a strawman description for the DKIM2 header signing. I know that
> Richard is writing a draft for this, but as draft writing is heavyweight
> and before going too deep down a particular path, I think there is benefit
> to put some sort of concept out early for community feedback. In the
> IETF-122 discussion we heard from Bron that there is an implicit list of
> headers that always will be signed, and that the headers will be
> oversigned. There is also a DKIM2-Signature "h=" to specify extra headers
> to be signed not covered by the implicit list as mentioned in
> draft-gondwana-dkim2-header. Bron also mentioned that subsequent
> DKIM2-Signatures extra headers "h=" cover prior DKIM2-Signatures "h="
> headers i.e. must be a superset. [...]
>
In an email message, everything before the first blank line is the
"header". There's exactly one header in a message. When you say
"headers", then, you must be talking about multiple messages.
The header is made up of one or more "header fields". There can be lots
of those, but there's always at least one ("From", which is required).
See Section 2.1 of RFC 5322 (and its successor says the same thing). This
mirrors the official terminology describing how HTTP replies are formed.
-MSK
_______________________________________________
Ietf-dkim mailing list -- ietf-dkim@ietf.org
To unsubscribe send an email to ietf-dkim-le...@ietf.org
