Re: rfc2822bis -- adding clarifying Sender: text

ietf-822

Re: rfc2822bis -- adding clarifying Sender: text

2008-01-15 19:57:54


Pete Resnick wrote:

Does that convey the correct information?


Yes, if it is understood that you are talking
about a message modulo Resent-* header fields.
  
Any "let's add a Sender" scheme starting with 
RFC 4409 8.1 has to be aware of Resent-*.
  
IMO "let's replace Sender" schemes are broken
by design.  If you know a good place to note
that an existing Sender MUST NOT be modified
please do.

 Frank

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
rfc2822bis -- adding clarifying Sender: text, Dave Crocker Re: rfc2822bis -- adding clarifying Sender: text, ned+ietf-822 Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick Re: rfc2822bis -- adding clarifying Sender: text, Frank Ellermann <= Re: rfc2822bis -- adding clarifying Sender: text, Charles Lindsey Re: rfc2822bis -- adding clarifying Sender: text, Frank Ellermann Re: rfc2822bis -- adding clarifying Sender: text, Charles Lindsey Re: rfc2822bis -- adding clarifying Sender: text, ned+ietf-822 Re: rfc2822bis -- adding clarifying Sender: text, Dave Crocker Re: rfc2822bis -- adding clarifying Sender: text, Dave Crocker Re: rfc2822bis -- adding clarifying Sender: text, Mark Martinec Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick Re: rfc2822bis -- adding clarifying Sender: text, Nick Shelness Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick

Previous by Date:	Re: rfc2822bis: "originator of the message" and "transmitter" not defined, Pete Resnick
Next by Date:	Re: rfc2822bis -- adding clarifying Sender: text, Dave Crocker
Previous by Thread:	Re: rfc2822bis -- adding clarifying Sender: text, Pete Resnick
Next by Thread:	Re: rfc2822bis -- adding clarifying Sender: text, Charles Lindsey
Indexes:	[Date] [Thread] [Top] [All Lists]