mail-vet-discuss
[Top] [All Lists]

Re: [mail-vet-discuss] Last Call: draft-kucherawy-sender-auth-header (Message Header Field for Indicating Message Authentication Status) to Proposed Standard

2008-12-02 14:59:57
At 08:33 02-12-2008, Victor Duchovni wrote:
If all untrusted headers are removed at the edge, we don't need an
"authserv-id" field at all, and the MUA's job is much easier. Presumably
"authserv-id" is there to:

The "authserv-id" field servers as an identifier.  It can be used to 
identify where the header was added within the ADMD.  For example, 
there may be two or more verifiers running on two MTAs performing 
tests.  If there is header reordering, we can still identify where 
the header was inserted.  Obviously, that depends on the format of 
the authserv-id being used.

There are several "status" header fields in use today.  Although they 
are meant for internal consumption, they do leak out.  It's quite 
common to see two different sites using the same header field name to 
convey the same type of status.  That's one more reason to build in 
some uniqueness into the header.

Regards,
-sm 

_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html 

<Prev in Thread] Current Thread [Next in Thread>