WG, was RE: Services messages in RFC 3730

Edward Lewis <[email protected]>
Newsgroups gmane.ietf.provreg
Message-ID <a0620070dbf22a2041c5d@[192.168.1.100]>
At 14:53 -0400 8/12/05, Hollenbeck, Scott wrote:
>>  -----Original Message-----
>>  From: Edward Lewis [mailto:[email protected]]
>>  Sent: Friday, August 12, 2005 2:20 PM
>>  To: Hollenbeck, Scott
>>  Cc: Michael Young; [email protected]
>>  Subject: RE: [ietf-provreg] Services messages in RFC 3730
>
>[snip]
>
>>  >c. It's common IETF practice to add new features via extensions once
>>  >proposed standards are published.  Extension development is usually a
>>  >good reason to spin up a new working group.
>>
>>  On a tangent - do you mean to say that extensions ought to cause a
>>  new WG?  Up to now some extensions haven't been discussed in a (new)
>>  WG.
>
>What I'm saying is that it's not uncommon for a new group to form around
>the idea of adding new features to an established protocol without
>changing the established protocol.  The imapext working group, for
>example.  There generally has to be a lot of common ground among the
>implementing community to have this be successful.  In our case, it
>could mean that multiple people would want to work on the same
>extension(s), maybe due to an ICANN requirement or some other similar
>need that brings people together.
>
>It's also quite acceptable for someone to just write their own extension
>draft and push it through the standards process.  This is probably a
>better option if the extension has limited appeal.

What I expressed to someone after the CENTR meeting was that (for a 
particular extension) was that they could collect a group of CENTR 
members, hammer out a draft (DRAFT!, not specification, not RFC) and 
then bring that to the IETF.  In other words, it doesn't always have 
to start in the IETF - although having the IETF last call, and this 
list, as a significant "open discussion" of the work.
-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis                                                +1-571-434-5468
NeuStar

If you knew what I was thinking, you'd understand what I was saying.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.