Todd Glassey wrote:
I forgot to mention that per IETF rules the AutoKEY brief is also filed as Informational Only (per the current filing) and as such cannot possibly replace a standards-track document like RFC1305 (whether its better technology or not).Chair - why is a RFC being obsoleted by an Internet-Draft?Seems to me like an impossibility. No I-D can in and of itself strip any RFC document without issuing a new RFC to replace the old one. Since an I-D is NOT a RFC this is an issue.This is a problem per se like this one... http://tools.ietf.org/html/draft-ietf-ntp-autokey-06
So we need to resolve this with a new NTP Standards Practice work-product which includes the v4 additions and the autokey security additions and the RFC needs to be re-set as "not Obsoleted" until the actual replacement work is published.
Todd
Todd Glassey _______________________________________________ Ipr-wg mailing list Ipr-wg at ietf.org https://www.ietf.org/mailman/listinfo/ipr-wg ------------------------------------------------------------------------ No virus found in this incoming message.Checked by AVG - www.avg.com Version: 8.5.409 / Virus Database: 270.13.109/2384 - Release Date: 09/20/09 06:22:00