RFC 6763
E736564
RFC 6763 is the Internet standard that defines DNS-Based Service Discovery (DNS-SD), a mechanism for discovering network services using DNS queries.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 6763 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T8471108 — 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: RFC 6763 Context triple: [Bonjour, implementsStandard, RFC 6763]
-
A.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
B.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- 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: RFC 6763 Target entity description: RFC 6763 is the Internet standard that defines DNS-Based Service Discovery (DNS-SD), a mechanism for discovering network services using DNS queries.
-
A.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
B.
RFC 6437
RFC 6437 is an Internet Engineering Task Force (IETF) specification that originally defined the IPv6 flow label behavior and usage before being superseded by RFC 8999.
-
C.
RFC 6176
RFC 6176 is an Internet Engineering Task Force (IETF) standard that formally disallows the use of the obsolete and insecure SSL 2.0 protocol in TLS implementations.
-
D.
RFC 6156
RFC 6156 is an Internet standard that extends the TURN protocol to support IPv6 and NAT traversal for IPv6/IPv4 environments.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbreviation |
DNS-SD
ⓘ
linked to:
DNS Service Discovery
|
| appliesTo |
local area networks
ⓘ
wide area networks ⓘ |
| area | Internet Area ⓘ |
| category | Standards Track ⓘ |
| defines |
DNS-Based Service Discovery
ⓘ
linked to:
DNS Service Discovery
TXT record key/value attribute conventions ⓘ conventions for service instance naming in DNS ⓘ rules for human-readable service instance names ⓘ rules for internationalization of service instance names ⓘ service discovery browsing via PTR queries on service type names ⓘ service discovery in local multicast DNS environments ⓘ service instance enumeration and selection rules ⓘ service instance enumeration via DNS queries ⓘ service instance names of the form <Instance>.<Service>.<Domain> ⓘ service subtype mechanism ⓘ service type names of the form _service._proto ⓘ use of SRV records for service discovery ⓘ use of TXT records for service metadata ⓘ |
| enables | zero-configuration service discovery ⓘ |
| focusesOn | service discovery rather than hostname resolution ⓘ |
| language | English ⓘ |
| obsoletes | RFC 2782 (for service discovery usage only) ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo | RFC 6762 ⓘ |
| RFCNumber | 6763 ⓘ |
| specifies |
backward compatibility with existing DNS infrastructure
ⓘ
multicast DNS-based service discovery usage ⓘ unicast DNS-based service discovery ⓘ |
| standardizes | mechanism for discovering network services using DNS queries ⓘ |
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
DNS-Based Service Discovery
ⓘ
linked to:
DNS Service Discovery
|
| usedBy |
Apple Bonjour
ⓘ
Avahi ⓘ various networked devices and applications for service discovery ⓘ |
| uses |
A resource records
ⓘ
AAAA resource records ⓘ DNS ⓘ
linked to:
Domain Name System
PTR resource records ⓘ SRV resource records ⓘ TXT resource records ⓘ |
| workingGroup |
DNSEXT
ⓘ
linked to:
dnsop
|
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: RFC 6763 Description of subject: RFC 6763 is the Internet standard that defines DNS-Based Service Discovery (DNS-SD), a mechanism for discovering network services using DNS queries.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.