On Monday, July 14, 2003, at 10:28 AM, Mark Crispin wrote:
On Mon, 14 Jul 2003, Chris Newman wrote:
RFC 1734 (POP3 AUTH) has a normative reference to RFC 1731. Until it
is
revised, we can not move RFC 1731 to historic.
And it looks like RFC 1939 has a normative reference to RFC 1731.
As do 2192
On Mon, 14 Jul 2003, Mark Crispin wrote:
> On Mon, 14 Jul 2003, Chris Newman wrote:
> > RFC 1734 (POP3 AUTH) has a normative reference to RFC 1731. Until it is
> > revised, we can not move RFC 1731 to historic.
> And it looks like RFC 1939 has a normative reference to RFC 1731.
On Mon, 14 Jul 2003, Chris Newman wrote:
> RFC 1734 (POP3 AUTH) has a normative reference to RFC 1731. Until it is
> revised, we can not move RFC 1731 to historic.
And it looks like RFC 1939 has a normative reference to RFC 1731.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerg
RFC 1734 (POP3 AUTH) has a normative reference to RFC 1731. Until it is
revised, we can not move RFC 1731 to historic.
- Chris
begin quotation by Eric A. Hall on 2003/7/11 11:52 -0500:
> Just noticed a trivial loose-end, but one which should be fixed.
> Specifically, RFC 1731 is
Just noticed a trivial loose-end, but one which should be fixed.
Specifically, RFC 1731 isn't formally deprecated nor was it obsoleted by
RFC . However, since RFC 3501 explicitly references now, 1731
should probably be snipped out of the standards-track document set by some
kind of admini
