TLS Working Group
E184134
The TLS Working Group is an IETF group responsible for developing and maintaining the Transport Layer Security (TLS) protocol and related technologies that secure communications over computer networks.
All labels observed (4)
| Label | Occurrences |
|---|---|
| IETF TLS Working Group | 5 |
| TLS Working Group canonical | 4 |
| TLS WG | 1 |
| Transport Layer Security Working Group | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1632112 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TLS Working Group Context triple: [IETF QUIC Working Group, coordinatesWith, TLS Working Group]
-
A.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
C.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
D.
Internet Engineering Steering Group
The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
-
E.
IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: TLS Working Group Target entity description: The TLS Working Group is an IETF group responsible for developing and maintaining the Transport Layer Security (TLS) protocol and related technologies that secure communications over computer networks.
-
A.
HTTP Working Group
The HTTP Working Group is an IETF standards body responsible for developing and maintaining the Hypertext Transfer Protocol and related web communication specifications.
-
B.
IETF working groups
IETF working groups are collaborative teams of experts within the Internet Engineering Task Force that develop and standardize technical specifications and protocols for the Internet.
-
C.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
-
D.
Internet Engineering Steering Group
The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
-
E.
IETF QUIC Working Group
The IETF QUIC Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the QUIC transport protocol and related technologies used by modern web protocols like HTTP/3.
- F. None of above. chosen
Statements (61)
| Predicate | Object |
|---|---|
| instanceOf |
IETF working group
ⓘ
standards development working group ⓘ |
| abbreviation |
TLS Working Group
self-linksurface differs
ⓘ
surface form:
TLS WG
|
| appliesTo |
IoT protocols using DTLS
ⓘ
VPN technologies using TLS ⓘ email transport security ⓘ real-time media over DTLS ⓘ web traffic security ⓘ |
| area |
IETF Areas
ⓘ
surface form:
Security Area of the IETF
|
| communicationChannel | public mailing list ⓘ |
| goal |
ensure wide interoperability of TLS and DTLS
ⓘ
maintain and improve the security of TLS and DTLS ⓘ standardize protocols for securing transport-layer communications ⓘ |
| meetsAt | IETF meetings ⓘ |
| name |
TLS Working Group
self-linksurface differs
ⓘ
surface form:
Transport Layer Security Working Group
|
| partOf | Internet Engineering Task Force ⓘ |
| produces |
Internet-Drafts
ⓘ
RFCs ⓘ |
| responsibleFor |
DTLS 1.0
ⓘ
DTLS ⓘ
surface form:
DTLS 1.2
DTLS 1.3 ⓘ DTLS ⓘ
surface form:
Datagram Transport Layer Security protocol
TLS 0-RTT mechanisms ⓘ TLS 1.0 ⓘ TLS 1.1 ⓘ TLS 1.2 ⓘ RFC 8446 ⓘ
surface form:
TLS 1.3
TLS 1.3 0-RTT anti-replay mechanisms ⓘ TLS 1.3 cipher suite registry ⓘ TLS 1.3 downgrade protection mechanisms ⓘ TLS 1.3 extension registry ⓘ TLS ALPN extension ⓘ TLS PSK mechanisms ⓘ Server Name Indication extension ⓘ
surface form:
TLS SNI extension
TLS alerts ⓘ TLS certificate-based authentication ⓘ TLS ciphersuites ⓘ TLS compression removal ⓘ TLS export keying material mechanisms ⓘ TLS extensions ⓘ TLS handshake protocol ⓘ TLS heartbeat extension (later deprecated) ⓘ TLS key schedule design ⓘ TLS key update mechanisms ⓘ TLS ⓘ
surface form:
TLS record layer
TLS renegotiation fixes ⓘ TLS session resumption mechanisms ⓘ TLS session tickets ⓘ TLS version negotiation mechanisms ⓘ TLS ⓘ
surface form:
Transport Layer Security protocol
|
| scope |
cryptographic mechanisms for transport security
ⓘ
definition of TLS and DTLS extensions ⓘ development of new TLS and DTLS versions ⓘ interoperability of TLS implementations ⓘ maintenance of existing TLS and DTLS specifications ⓘ security analysis of TLS and DTLS ⓘ security of transport protocols ⓘ |
| technologyDomain |
cryptographic protocols
ⓘ
network security ⓘ transport-layer protocols ⓘ |
| usesProcess | IETF consensus process ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: TLS Working Group Description of subject: The TLS Working Group is an IETF group responsible for developing and maintaining the Transport Layer Security (TLS) protocol and related technologies that secure communications over computer networks.
Referenced by (11)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
IETF TLS Working Group
this entity surface form:
IETF TLS Working Group
this entity surface form:
IETF TLS Working Group
this entity surface form:
Transport Layer Security Working Group
this entity surface form:
TLS WG
this entity surface form:
IETF TLS Working Group
this entity surface form:
IETF TLS Working Group