ietf-nntp BCP for RFC977 server/RFC1036 interaction

Anne Bennett anne at alcor.concordia.ca
Mon Apr 7 10:19:22 PDT 1997


Ade Lovett  <ade at demon.net> writes:
> Trivial to change, if required:
> 
> 	NNTP-Posting-User: [<authtype> " "] <authinfo>
> 	with <authtype> implicitly meaning RFC1413-identd if missing
> 
> so,
> 
> 	NNTP-Posting-User: ade
> 	NNTP-Posting-User: rfc1413 ade
> 	NNTP-Posting-User: ssl @c=gb@ .....
> 
> would all be valid.

I'm not sure it's even worth formalizing what should be in the
NNTP-Posting-User header; after all, only the server that put it there
can really "trust" it.  As is the case for identd, as long as the
generator of the header can make sense of the information and take 
action according to it, no one else needs to know what it means.

Of course, I could always put in

   NNTP-Posting-User: concordia-hack 21298127446124

:-)



Anne.
--
Ms. Anne Bennett          anne at alcor.concordia.ca            (514) 848-7606
Computing Services,   Concordia University,   Montreal QC,   Canada H3G 1M8



More information about the ietf-nntp mailing list