Subject: [Megaco] Terminology related to TLS and DTLS; RE: TLS 1.3: Enhanced definitions of terms "TLS session" and "TLS connection"

From: "Schwarz, Albrecht (Albrecht)" <[email-masked]>
Date: Fri, 10 Oct 2014 19:32:40 +0000

fyi,
we've developed an hierarchical terminology framework for TLS and DTLS (in context of H.248 gateways, serving the termination or interworking of (D)TLS protocol).
However, the terminology isn't gateway specific, defined in a general manner, thus applicable (and fully consistent) to IETF TLS RFCs in our understanding.

Download:
AVD-4600 H.Sup.13 (Rel. 2): Terminology related to TLS and DTLS
http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/AVD-4600.zip  

Regards,

Albrecht, Jens & Juergen

PS
The formal proceeding behind AVD-4600 may be found in:
AVD-4614 Backup-material to AVD-4600: Formal description of "TLS terminology framework"
http://wftp3.itu.int/av-arch/avc-site/2013-2016/1411_Seo/AVD-4614.zip 

-----Original Message-----
From: TLS [mailto:[email-masked]] On Behalf Of Schwarz, Albrecht (Albrecht)
Sent: Mittwoch, 19. März 2014 17:10
To: [email-masked]
Subject: [TLS] TLS 1.3: Enhanced definitions of terms "TLS session" and "TLS connection"

Dear All,
like to raise a question related to the RFC 5246, Appendix B "Glossary":

Status: 
- connection:	
       A connection is a transport (in the OSI layering model definition) that provides a suitable type of service.  For TLS, such connections are peer-to-peer relationships.  The connections are transient.  Every connection is associated with one session.

- session:	
       A TLS session is an association between a client and a server. Sessions are created by the handshake protocol.  Sessions define a set of cryptographic security parameters that can be shared among multiple connections.  Sessions are used to avoid the expensive negotiation of new security parameters for each connection.

Both terms are rather high-level and silent concerning a number of key characteristics.
E.g.,
What constitutes exactly a "TLS session"? Just the 1-tuple of a "session id" or the 6-tuple of {session identifier, peer certificate, compression method, cipher spec, master secret, is resumable}" (based on clause 7/RFC 5246)?

Similar, what constitues exactly a "TLS connection"? An n-tuple based on the ConnectionState on clause 6.1/RFC 5246, just a sub-set ..., the 5-tuple of IP transport connection endpoint addresses?

What exactly is the relation between a "TLS session" and its associated "TLS connection(s)"?

Resumption of a "TLS session"? What kind of "data object (configuration)" is exactly used as starting point for the "resumption procedure"?

Such kind of questions are all leading to the baseline of good terminology. The existing Glossary could and should be improved in my understanding.

Any opinions, comments from TLS expert side?
Anyone aware of similar terminology enhancements requests in the past?

Thanks,
Albrecht

_______________________________________________
TLS mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/tls