Re: So here it is one year later...

ietf-mxcomp

Re: So here it is one year later...

2005-01-28 17:04:19



On Jan 28, 2005, at 2:20 PM, wayne wrote:

The problem is not that draft-schlitt-spf-00
changed things back, but that the IETF, via the MARID WG, allowed it
to change in the first place.

This statement strikes me as particularly offensive. If the intent wasto have the IETF simply rubber-stamp SPF, making that clear up frontwould have saved us all a lot of time.


-andy

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
So here it is one year later..., Gordon Fecyk Re: So here it is one year later..., Douglas Otis Re: So here it is one year later..., Frank Ellermann Re: So here it is one year later..., Douglas Otis Re: So here it is one year later..., Frank Ellermann Re: So here it is one year later..., Douglas Otis Re: So here it is one year later..., wayne Re: So here it is one year later..., Douglas Otis Re: So here it is one year later..., wayne Re: So here it is one year later..., Andrew Newton <= Re: So here it is one year later..., wayne Re: So here it is one year later..., Andrew Newton Re: So here it is one year later..., wayne Re: So here it is one year later..., Douglas Otis Re: So here it is one year later..., Frank Ellermann Re: So here it is one year later..., Douglas Otis Re: So here it is one year later..., gmc Re: So here it is one year later..., Ian Rogers Re: So here it is one year later..., David Woodhouse Re: So here it is one year later..., K.F.J. Martens

Previous by Date:	Re: So here it is one year later..., Justin Mason
Next by Date:	RE: So here it is one year later..., Gordon Fecyk
Previous by Thread:	Re: So here it is one year later..., wayne
Next by Thread:	Re: So here it is one year later..., wayne
Indexes:	[Date] [Thread] [Top] [All Lists]