RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Appeal: Publication of draft-lyon-senderid-core-01 inconflictwith referenced draft-schlitt-spf-classic-02



> Behalf Of wayne
> > At some point there is a boundary between infrastructure the sender 
> > has control of and where he does not. That boundary is very clearly 
> > defined in my universe but even if it was ambiguous it would still 
> > exist.
> 
> The problem is that for different identities, this "boundary" 
> is different.  In particular, the boundaries between the SPF 
> identities (2821.MAILFROM and 2821.HELO) are different than 
> SenderID (PRA).

The identities are completely irrelevant.

The only relevant boundary is between what the sender controls and what
they do not. All that any sender, forwarder or any other mail injector
can ever be expected to do is to define the boundaries of the systems
they control.

Once that boundary is defined the definition is fair game for any party
to use to interpret it to meet their operational needs.

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




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

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