Re: Intent to revive "expires" header from draft-ietf-mailext-new-fields-15
Hector Santos <[email protected]>
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Organization | Santronics Software, Inc |
| Message-ID | <[email protected]> |
[email protected] wrote: > >> > When you get down to it this is really about being able to manage >> > ever-increasing amounts of email a litte more easily. If we try and >> take it >> > further than that we'll lose focus and likely derail the entire >> proposal. > >> I guess I'm with Bill on this. My main issue with an 'expires' header is >> that it will mean many things to many people. > > Then we'll just have to agree to disagree. I thought the definition Keith > provided was just about right in nailing down the semantics for the field. > I think anything tighter will prevent its use and anything looser will > be so amorphous that we won't get any traction. > > Ned Well, it shouldn't be called "Expires" then. Call it something else. I like "Color-me-Gray-Date:" <g> Calling it expires or anything close to it, and intentionally ignoring the complete picture, IMV, will make it highly probable it will be used not as it was intended. Especially when it is get mixed in with other 2822 expiration concepts - DKIM. -- HLS