RFC 3996
E746695
RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3996 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8611100 — 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 3996 Context triple: [Internet Printing Protocol, hasRFC, RFC 3996]
-
A.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3629
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
- 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 3996 Target entity description: RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
-
A.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
B.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
C.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
D.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
E.
RFC 3629
RFC 3629 is the Internet standard that defines the UTF-8 character encoding for representing Unicode/ISO/IEC 10646 characters in a byte-oriented format.
- F. None of above. chosen
Statements (32)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| abbreviation | IPP: The 'ipp' URI Scheme NERFINISHED ⓘ |
| area | Applications Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
ipp URI scheme
ⓘ
semantics of ipp URIs ⓘ syntax of ipp URIs ⓘ use of ipp URIs to identify IPP printers ⓘ use of ipp URIs to identify print jobs ⓘ |
| focusesOn | extensions and clarifications for IPP ⓘ |
| intendedUse | identification of IPP resources ⓘ |
| language | English ⓘ |
| obsoletes | RFC 3510 NERFINISHED ⓘ |
| protocolFamily | Application layer ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor NERFINISHED ⓘ |
| relatedProtocol | Internet Printing Protocol NERFINISHED ⓘ |
| relatedRFC |
RFC 2910
NERFINISHED
ⓘ
RFC 2911 NERFINISHED ⓘ RFC 3510 NERFINISHED ⓘ |
| standardizes |
ipp URI scheme for print jobs
ⓘ
ipp URI scheme for printers ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Internet Printing Protocol (IPP): The 'ipp' URI Scheme NERFINISHED ⓘ |
| updates | Internet Printing Protocol NERFINISHED ⓘ |
| uses |
HTTP-based transport
ⓘ
Uniform Resource Identifier syntax ⓘ |
| workingGroup | Internet Printing Protocol Working Group NERFINISHED ⓘ |
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 3996 Description of subject: RFC 3996 is an Internet Engineering Task Force (IETF) specification that defines extensions and clarifications for the Internet Printing Protocol (IPP).
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.