<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type>
<META content='"MSHTML 4.71.1702.0"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 solid 2px; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">
<DIV><FONT face=Arial size=2><B>-----Original Message-----</B><BR><B>From:
</B>Stan Barber <<A
href="mailto:sob@academ.com">sob@academ.com</A>><BR><B>To: </B>Nat Ballou
<<A
href="mailto:NatBa@ims.microsoft.com">NatBa@ims.microsoft.com</A>>; NNTP
Working Group <<A
href="mailto:ietf-nntp@academ.com">ietf-nntp@academ.com</A>><BR><B>Date:
</B>Thursday, September 04, 1997 8:30 AM<BR><B>Subject: </B>Re: ietf-nntp
Issues with new draft<BR><BR></DIV></FONT>Nat, <BR><BR>The x8x response
codes were always intended to be used by non-standard <BR>extensions. It
makes no sense to continue to use them for something<BR>that will now be a
standard extension. If we are going to use the x8x for<BR>authentication and
identification, we can't use them for non-standard<BR>extensions.</BLOCKQUOTE>
<DIV><FONT color=#000000 face="MS Sans Serif" size=2>I'm just concerned that
there are already clients and servers that use the </FONT></DIV>
<DIV><FONT color=#000000 face="MS Sans Serif" size=2></FONT><FONT
face="MS Sans Serif" size=2>current response codes. I understand your
reasoning, but it complicates</FONT></DIV>
<DIV><FONT face="MS Sans Serif" size=2>the transition to the new
RFC.</FONT> </DIV>
<DIV><FONT face="MS Sans Serif" size=2></FONT> </DIV>
<DIV><FONT face="MS Sans Serif" size=2>Nat</FONT></DIV></BODY></HTML>