Re: Last Call sender-auth-header

From: SM <sm at resistor.net>
To: ietf at ietf.org
Date: Fri, 21 Nov 2008 11:02:27 -0800
In-reply-to: <DEBF580C-6D06-49E8-A604-D531F98133C6 at mail-abuse.org>
References: <DEBF580C-6D06-49E8-A604-D531F98133C6 at mail-abuse.org>

At 20:00 20-11-2008, Douglas Otis wrote:

It is rather startling that adoption of an experimental RFC is beingpresumed by this draft. As such, those not adopting thisexperimental PRA RFC run the risk of being


There are existing implementations of these experimental RFCs.

Adoption of this draft may then require the IETF to endorseSender-ID. After all, email

As I mentioned before on the mail-vet mailing list, this header isused to convey results of DomainKeys, DKIM, SPF and Sender-IDevaluation. It is not an endorsement of a specific evaluation method.


Regards,

-sm

_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- Re: Last Call sender-auth-header
  - From: Douglas Otis

References:
- Last Call sender-auth-header
  - From: Douglas Otis

Prev by Date: [Sip] Last Call: draft-ietf-sip-session-policy-framework (A Framework for Session Initiation Protocol (SIP) Session Policies) to Proposed Standard
Next by Date: Re: Last Call sender-auth-header
Previous by thread: Last Call sender-auth-header
Next by thread: Re: Last Call sender-auth-header
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Last Call sender-auth-header

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.