Just to clarify this point. The text in the introduction where the authors retained change control was a leftover from the original draft that was intended to go informational.
We simply forgot to remove this when we changed the scope to informational. This is fixed in version 03 of the draft. Stefan Santesson Program Manager, Standards Liaison Windows Security -----Original Message----- From: Russ Housley [mailto:[EMAIL PROTECTED] Sent: den 19 februari 2006 23:22 To: Bill Fenner; Steven M. Bellovin Cc: [email protected]; [EMAIL PROTECTED]; [email protected] Subject: [TLS] Re: Last Call: 'TLS User Mapping Extension' to Proposed Standard I misunderstood the original question. I'll get it fixed or withdraw the Last Call. Russ At 12:38 AM 2/19/2006, Bill Fenner wrote: > >Can we have a Proposed Standard > >without the IETF having change control? > >No. RFC3978 says, in section 5.2 where it describes the derivative >works limitation that's present in draft-santesson-tls-ume, "These >notices may not be used with any standards-track document". > > Bill _______________________________________________ TLS mailing list [EMAIL PROTECTED] https://www1.ietf.org/mailman/listinfo/tls _______________________________________________ Ietf mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ietf
