[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Request to advance rfc4214(bis) to standards-track through ADsponsorship
- To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
- Subject: Re: Request to advance rfc4214(bis) to standards-track through ADsponsorship
- From: David Meyer <dmm@1-4-5.net>
- Date: Fri, 30 Mar 2007 08:59:22 -0800
- Cc: Ron Bonica <rbonica@juniper.net>, Mark Townsley <townsley@cisco.com>, dromasca@avaya.com, Jari Arkko <jari.arkko@piuha.net>, Lindqvist Erik Kurt <kurtis@kurtis.pp.se>, Fred Baker <fred@cisco.com>, David Ward <dward@cisco.com>, "Durand, Alain" <Alain_Durand@cable.comcast.com>, Bob Hinden <bob.hinden@nokia.com>, brian@innovationslab.net, tgleeson@cisco.com, dthaler@microsoft.com, mohitt@microsoft.com, v6ops@ops.ietf.org
- In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A101774863@XCH-NW-7V2.nw.nos.boeing.com>
- References: <EF2F0EC839870F43A6637360BC12ABD4018E3765@PACDCEXCMB05.cable.comcast.com> <39C363776A4E8C4A94691D2BD9D1C9A10177484C@XCH-NW-7V2.nw.nos.boeing.com> <460BFB6D.2000309@juniper.net> <39C363776A4E8C4A94691D2BD9D1C9A101774850@XCH-NW-7V2.nw.nos.boeing.com> <460C0B46.10405@juniper.net> <39C363776A4E8C4A94691D2BD9D1C9A101774854@XCH-NW-7V2.nw.nos.boeing.com> <20070329212331.GA12948@1-4-5.net> <39C363776A4E8C4A94691D2BD9D1C9A10177485E@XCH-NW-7V2.nw.nos.boeing.com> <20070330160709.GA29724@1-4-5.net> <39C363776A4E8C4A94691D2BD9D1C9A101774863@XCH-NW-7V2.nw.nos.boeing.com>
- User-agent: Mutt/1.4.1i
On Fri, Mar 30, 2007 at 09:36:19AM -0700, Templin, Fred L wrote:
> > Either PS means something, in which
> > case there is no rush, or it doesn't (in which case there
> > is also no rush).
>
> I can't say more about my customer or their use case, but
> from my vantage point I have to respectfully disagree.
While I understand that there and will continue to be
proprietary use cases, but such use cases seem a
particularly opaque reason for rushing to PS status
(especially given the somewhat dubious value of the PS
designation itself).
Not to put to fine a point on it, but IMO the IETF needs
more transparency (at every level), not less.
--dmm
Attachment:
pgpobccJDU1sh.pgp
Description: PGP signature