RFC 8010
E745326
RFC 8010 is an IETF specification that defines the Internet Printing Protocol (IPP) model and semantics for network printing.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8010 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8611102 — 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 8010 Context triple: [Internet Printing Protocol, hasRFC, RFC 8010]
-
A.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
B.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
C.
RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
D.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
-
E.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
- 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 8010 Target entity description: RFC 8010 is an IETF specification that defines the Internet Printing Protocol (IPP) model and semantics for network printing.
-
A.
RFC 6410
RFC 6410 is an Internet Engineering Task Force (IETF) document that streamlines and updates the process for advancing technical specifications to Internet Standard status within the Internet Standards Process.
-
B.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
C.
RFC 8551
RFC 8551 is the Internet standards document that specifies the current version of S/MIME, a protocol for secure, encrypted, and signed email communication.
-
D.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
-
E.
RFC 8729
RFC 8729 is an Internet Engineering Task Force (IETF) document that defines the principles and procedures for managing and publishing documents in the IETF Stream of the RFC Series.
- F. None of above. chosen
Statements (55)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments ⓘ |
| area | Applications and Real-Time Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
IPP attributes
ⓘ
IPP encoding rules ⓘ IPP object model NERFINISHED ⓘ IPP operations ⓘ Internet Printing Protocol model NERFINISHED ⓘ Internet Printing Protocol semantics NERFINISHED ⓘ job, printer, and document objects in IPP ⓘ network printing model ⓘ |
| focusesOn | network printing ⓘ |
| isPartOf | IPP standards ⓘ |
| obsoletes |
RFC 2911
NERFINISHED
ⓘ
RFC 3380 NERFINISHED ⓘ RFC 3381 NERFINISHED ⓘ RFC 3382 NERFINISHED ⓘ RFC 3383 NERFINISHED ⓘ RFC 3384 NERFINISHED ⓘ RFC 3385 NERFINISHED ⓘ RFC 3386 NERFINISHED ⓘ RFC 3387 NERFINISHED ⓘ RFC 3388 NERFINISHED ⓘ RFC 3389 NERFINISHED ⓘ RFC 3390 NERFINISHED ⓘ RFC 3391 NERFINISHED ⓘ RFC 3392 NERFINISHED ⓘ RFC 3393 NERFINISHED ⓘ RFC 3394 NERFINISHED ⓘ RFC 3395 NERFINISHED ⓘ RFC 3396 NERFINISHED ⓘ RFC 3397 NERFINISHED ⓘ RFC 3398 NERFINISHED ⓘ RFC 3399 NERFINISHED ⓘ RFC 3400 NERFINISHED ⓘ RFC 3401 ⓘ RFC 3402 NERFINISHED ⓘ RFC 3403 NERFINISHED ⓘ RFC 3404 NERFINISHED ⓘ RFC 3405 NERFINISHED ⓘ RFC 3406 NERFINISHED ⓘ RFC 3407 NERFINISHED ⓘ RFC 3408 ⓘ RFC 3409 ⓘ RFC 3410 NERFINISHED ⓘ |
| protocolVersion | Internet Printing Protocol/1.1 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| standardizes | client-printer interactions in IPP ⓘ |
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Internet Printing Protocol/1.1: Model and Semantics NERFINISHED ⓘ |
| updatesSpecificationOf | Internet Printing Protocol NERFINISHED ⓘ |
| 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 8010 Description of subject: RFC 8010 is an IETF specification that defines the Internet Printing Protocol (IPP) model and semantics for network printing.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.