Re: [TLS] Last Call: draft-ietf-tls-rfc4346-bis (The TransportLayer Security (TLS) Protocol Version 1.2) to Proposed Standard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TLS] Last Call: draft-ietf-tls-rfc4346-bis (The TransportLayer Security (TLS) Protocol Version 1.2) to Proposed Standard
Simon,
The relationship between updates/obsoletes/references is not (as far
as I know) clearly defined anywhere, but in practice, there is rarely
any confusion.
Suppose that someone is implementing RFC AAAA, an optional extension
to a base protocol specified in RFC BBBB, and finds that the base
protocol specification has been updated after RFC AAAA was published
(i.e., RFC BBBB has been obsoleted by RFC CCCC). The implementor
should know whether his/her implementation implements BBBB or CCCC,
and if it's the latter, usually is able to easily tell whether the
extension works with the new version or not.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.