It's not a vendor controlled namespace; it's an individual controlled namespace that I'm more than happy to delegate to the IESG.
The IETF has complete change control of the spec at this point -- including changing the XML namespace used by the extension if doing so would be appropriate. I trust the IESG and the RFC editor to do whatever is deemed to be appropriate. - James p.s. FUD is generally more effective when not based on generally false and easily refuted assumptions Robert Sayre wrote: > On 6/23/06, Paul Hoffman <[EMAIL PROTECTED]> wrote: >> >> The view I prefer >> is "follow RFC 2026 because no one is going to remember the logic for >> not following it after the RFC is published." Yes, I'm a bit of a >> priss about these things... > > I'm alarmed that this specification is on the standards track in a > vendor-controlled namespace. > > <http://purl.org/maint/search_user.pl.cgi?userid=^JASNELL$> > > I notice Sam Hartman raised this point in IESG discussion, but I don't > see a record of its resolutoin. What were the procedures followed, and > how can it be said that the IETF has change control here? >
