RFC 8881
E768631
RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 8881 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8950921 — 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 8881 Context triple: [RFC 3530, obsoletedBy, RFC 8881]
-
A.
RFC 8011
RFC 8011 is the IETF specification that defines the core model, semantics, and operations of the Internet Printing Protocol (IPP) used for network printing.
-
B.
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.
-
C.
RFC 6081
RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
-
D.
RFC 7888
RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
-
E.
RFC 7158
RFC 7158 is an IETF specification that updates and clarifies the JSON (JavaScript Object Notation) data interchange format previously defined in RFC 4627.
- 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 8881 Target entity description: RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
-
A.
RFC 8011
RFC 8011 is the IETF specification that defines the core model, semantics, and operations of the Internet Printing Protocol (IPP) used for network printing.
-
B.
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.
-
C.
RFC 7481
RFC 7481 is an IETF standards document that specifies the security services and requirements for the Registration Data Access Protocol (RDAP).
-
D.
RFC 6081
RFC 6081 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces the original Teredo IPv6 transition mechanism specification to improve IPv6 connectivity across IPv4 networks with NAT.
-
E.
RFC 7888
RFC 7888 is an Internet Engineering Task Force (IETF) standards document that refines and updates email-related protocols originally defined in RFC 6856.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
NFS specification ⓘ Request for Comments ⓘ |
| abbreviation | NFSv4.1 specification ⓘ |
| area |
Applications and Real-Time Area
NERFINISHED
ⓘ
Transport Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| defines |
NFSv4.1 COMPOUND procedures
NERFINISHED
ⓘ
NFSv4.1 XDR data types ⓘ NFSv4.1 attribute model ⓘ NFSv4.1 attributes ⓘ NFSv4.1 backchannel NERFINISHED ⓘ NFSv4.1 callback mechanisms ⓘ NFSv4.1 callback programs ⓘ NFSv4.1 callback state ⓘ NFSv4.1 client ID management ⓘ NFSv4.1 client recovery procedures ⓘ NFSv4.1 client-server interactions ⓘ NFSv4.1 data types ⓘ NFSv4.1 error codes ⓘ NFSv4.1 error handling ⓘ NFSv4.1 file access semantics ⓘ NFSv4.1 file locking semantics ⓘ NFSv4.1 internationalization considerations NERFINISHED ⓘ NFSv4.1 layout types ⓘ NFSv4.1 lease management ⓘ NFSv4.1 locking model ⓘ NFSv4.1 migration and replication behavior ⓘ NFSv4.1 multi-server namespace behavior ⓘ NFSv4.1 operation encodings ⓘ NFSv4.1 operations ⓘ NFSv4.1 pNFS framework ⓘ NFSv4.1 security mechanisms ⓘ NFSv4.1 security negotiation ⓘ NFSv4.1 session establishment ⓘ NFSv4.1 session trunking ⓘ NFSv4.1 sessions ⓘ NFSv4.1 slot management ⓘ NFSv4.1 state model ⓘ |
| obsoletes | RFC 5661 NERFINISHED ⓘ |
| protocolFamily | NFS NERFINISHED ⓘ |
| protocolVersion | 4.1 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| replaces | original NFSv4 specification ⓘ |
| specifiesProtocol |
NFSv4.1
NERFINISHED
ⓘ
Network File System version 4.1 NERFINISHED ⓘ |
| status | Internet Standard NERFINISHED ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title | Network File System (NFS) Version 4 Minor Version 1 Protocol NERFINISHED ⓘ |
| updates | NFS version 4 protocol specification 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 8881 Description of subject: RFC 8881 is the Internet Engineering Task Force (IETF) standard that specifies the Network File System (NFS) version 4.1 protocol, updating and replacing the original NFSv4 specification.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.