Message Header Field for Indicating Message Authentication Status
RFC 5451

Note: This ballot was opened for revision 20 and is now closed.

(Lisa Dusseault) Yes

(Ron Bonica) No Objection

Comment (2008-12-18 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
Support Dan/Peters discuss

(Ross Callon) No Objection

(Pasi Eronen) (was No Record, No Objection) No Objection

(Russ Housley) No Objection

Comment (2008-12-14 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
  In the Gen-ART Review by Suresh Krishnan, he said that one thing was
  unclear.  He wanted to know how the MUA would convey the results to
  the user.  For example, using the case C.5 from the appendix, what
  would the user actually see (Success indication, Failure indication,
  or something else)?  Is this field used more as input for filters
  rather than communicating authentication information to the user?
  How is the authenticity of the sender established?

(Cullen Jennings) No Objection

Comment (2008-12-17 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
I can not find evidence on any IETF mailing list of any consensus to publish this.

(Chris Newman) No Objection

Comment (2008-12-15 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
>    "CFWS" is as defined in section 3.2.3 of [MAIL].

I believe that should be section 3.2.2.

(Tim Polk) No Objection

(Dan Romascanu) (was Discuss) No Objection

(Mark Townsley) No Objection

(David Ward) No Objection

Magnus Westerlund No Objection