nntp-extensions Renaming the SEARCH extensions

[Brian Hernacki]

Nat Ballou wrote:
> Clients aren't likely to include search support until
> we get a little further with the search. Also, getting a
> syntax error against the Netscape server when you
> use the 'SEARCH' extension name does not seem
> like a big deal to me - probably as good as any other
> error you can give until Netscape provides an
> implementation of the search draft.
> 
> So, I'd prefer to leave the draft with 'SEARCH' as
> the extension name.  Given the current rate of progress
> on RFC977bis, I think Netscape will have plenty
> of time to update their implementation.

It's not a matter of releasing a up-to-spec client or server. It's a
matter of deployed clients and servers. Just because new software is
available doesn't mean people will upgrade to it... nor should we force
them to. 

If we leave it as SEARCH we're going to see a lot of breakage. It's
seems a pretty simple thing to do to solve interoperability problems and
I can't see any downside to it.


> P.S. - if you also want developers to hit against a
> Netscape implementation but have problems with
> release dates, how about putting up a early version
> of the Netscape server on the Netscape Internet
> site that does support the search draft?  Microsoft
> will probably do this in the next month or so ...

We already do.

--brian
Opinions are mine, not Netscape's