RFC 3995
E745324
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 3995 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8611099 — 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.
Target entity: RFC 3995 Context triple: [Internet Printing Protocol, hasRFC, RFC 3995]
-
A.
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.
-
B.
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.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
E.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: RFC 3995 Target entity description: 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.
-
A.
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.
-
B.
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.
-
C.
RFC 3947
RFC 3947 is an IETF standard that specifies how to detect and negotiate IPsec NAT Traversal (NAT-T) using IKE.
-
D.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
E.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard-track document
ⓘ
Request for Comments ⓘ |
| abbreviation | IPP: Event Notifications NERFINISHED ⓘ |
| appliesTo |
IPP clients
ⓘ
IPP print services ⓘ IPP printers ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
Cancel-Subscription operation
ⓘ
Create-Job-Subscriptions operation NERFINISHED ⓘ Create-Printer-Subscriptions operation NERFINISHED ⓘ Get-Notifications operation ⓘ IPP Event Notifications NERFINISHED ⓘ IPP notification attributes ⓘ IPP notification delivery methods framework NERFINISHED ⓘ IPP notification model NERFINISHED ⓘ IPP subscription objects ⓘ IPP subscription operations ⓘ Internet Printing Protocol Event Notifications extension NERFINISHED ⓘ Renew-Subscription operation ⓘ notification events for print jobs ⓘ notification events for printers ⓘ notification recipient concept ⓘ |
| extends |
IPP/1.1
NERFINISHED
ⓘ
Internet Printing Protocol/1.1 NERFINISHED ⓘ |
| focusesOn |
asynchronous alert messages from printers
ⓘ
asynchronous printer status notifications ⓘ event notification framework for IPP ⓘ |
| intendedAudience |
IPP client implementers
ⓘ
print server implementers ⓘ printer manufacturers ⓘ |
| language | English ⓘ |
| networkProtocol | Application-layer protocol specification ⓘ |
| obsoletedBy | None ⓘ |
| obsoletes | None ⓘ |
| partOfSeries | Request for Comments NERFINISHED ⓘ |
| protocolFamily | Internet Printing Protocol NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
IPP printer state and job state monitoring
ⓘ
RFC 2910 NERFINISHED ⓘ RFC 2911 NERFINISHED ⓘ |
| rfcNumber | 3995 ⓘ |
| standardsBody | Internet Engineering Task Force NERFINISHED ⓘ |
| status | Proposed Standard ⓘ |
| title | Internet Printing Protocol (IPP): Event Notifications NERFINISHED ⓘ |
| useCase |
notifying clients of job completion
ⓘ
notifying clients of job state changes ⓘ notifying clients of printer configuration changes ⓘ notifying clients of printer errors ⓘ |
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.
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.
Subject: RFC 3995 Description of subject: 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.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.