[no subject]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



Requiring the IETF to update all RFCs which extend RFC BBBB would be 
a huge job (as a long-time participant in IETF, I'm sure you're aware
how much work is required to update even one word in an RFC), and
especially if confusion is unlikely, unnecessary.

However, if you have a suggestion about text we could add to TLS 1.2,
that could be considered by IESG (however, note that this document
is on telechat agenda already this Thursday).

(Some other SDOs have document numbering/reference schemes which
avoid some parts of this problem (e.g. allowing reference either
to a specific version of some other spec, or the latest version);
but lacking this ability doesn't seem to result in big problems
in practice.)

Best regards,
Pasi

> -----Original Message-----
> From: ext Simon Josefsson [mailto:simon at josefsson.org] 
> Sent: 03 March, 2008 16:31
> To: Eronen Pasi (Nokia-NRC/Helsinki)
> Cc: mark at redphonesecurity.com; tls at ietf.org
> Subject: Re: Last Call: draft-ietf-tls-rfc4346-bis (The 
> Transport Layer Security (TLS) Protocol Version 1.2) to 
> Proposed Standard
> 
> TLS versioning and IETF update/obsolete-versioning has different
> semantics.  RFC 4680 updates RFC 4346, i.e. TLS 1.1.  If RFC 4346 is
> obsoleted by RFC 4346bis (TLS 1.2), then RFC 4680 will not
> automatically update RFC 4346bis.  My interpretation is that RFC
> 4680 will have to be revised to update RFC 4346bis, in order to
> apply to TLS 1.2, if you follow the IETF update/obsolete-versioning
> semantics.
> 
> I think Mark has a point here.  IETF-versioning doesn't handle
> version-independent feature, unless such behaviour is explicitly
> documented (which it isn't, as far as I can tell, in this case).
> 
> However, I think the solution here is to (once RFC 4346bis is
> published) revise RFC 4680 to update RFC 4346bis, if there is a need
> from the community to use RFC 4680 with TLS 1.2, rather than
> changing the TLS 1.2 specification.
> 
> /Simon
<snip>
_______________________________________________
TLS mailing list
TLS at ietf.org
https://www.ietf.org/mailman/listinfo/tls



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.