On 4/21/2011 12:18 AM, Behcet Sarikaya wrote: > Hi, > It seems like I-D submission for a revised draft (after expiration) encounters > so many new hurdles: > > 1. Version number. Submission page complains about the version number even > though it is correct. This seems to be because the system keeps the expiration > message in html format as the new version to be submitted. > > Is there a way to get around this? Don't let I-Ds expire? > > 2. RFC XML has changed. It seem like > xml.resource.org has a new xml compiler. I had a lot of trouble in compiling my > existing xml files. Hmm. I'm not experiencing any problems, either with the on-line or the host based tools. Are you sure that your XML was valid before? > I am OK with improving RFC XML but why not keep upward > compatibility? > > Regards, > > Behcet > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf > >
begin:vcard fn:Glen Zorn n:Zorn;Glen org:Network Zen adr:;;;Seattle;WA;;USA email;internet:gwz@xxxxxxxxxxx tel;cell:+66 87 040 4617 note:PGP Key Fingerprint: DAD3 F5D3 ACE6 4195 9C5C 2EE1 6E17 B5F6 5953 B45F version:2.1 end:vcard
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf