[NNTP] CAPABILITIES problem!
Scott Hollenbeck
sah at 428cobrajet.net
Mon Aug 1 23:19:50 PDT 2005
> -----Original Message-----
> From: Ned Freed [mailto:ned.freed at mrochek.com]
> Sent: Tuesday, August 02, 2005 2:10 AM
> To: Clive DW Feather
> Cc: Ned Freed; IETF NNTP mailing list
> Subject: Re: [NNTP] CAPABILITIES problem!
>
> > Ned Freed said:
> > >> Possible solutions:
> > >> (1) Relax the 12 character limit to something longer
> (where did it come
> > >> from anyway?).
> > >> (2) Relax the requirement for the label to be a keyword.
> > >> (3) Change the keyword to something shorter, like SERVER_INFO.
> > >
> > > My personal preference would be to bump the limit to 16
> or even 32 characters.
> > > 12 seems a bit short.
>
> > As I said, I'm not sure where the limit comes from in the
> first place.
>
> > But, as Russ asks, what's the formal process?
>
> IMO this can be handled during AUTH48. When the RFC Editor is
> ready you
> as author will be contacted and asked if the RFC-to-be is OK.
> You submit
> a correction then. The RFC Editor will run it past the
> relevant AD (Scott
> in this case). If Scott is OK with the change then we should
> be good to go.
Agreed. All I would add to Ned's note is that I'd like to see a proposal
confirmed by the WG before I agree with the change. Ned's suggestion to
bump the limit seems like the least intrusive document change, but I don't
know what the impact would be on implementations.
-Scott-
More information about the ietf-nntp
mailing list