RFC 5661
E209178
RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5661 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1718330 — 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 5661 Context triple: [NFS, definedIn, RFC 5661]
-
A.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
-
B.
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.
-
C.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
D.
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.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- 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 5661 Target entity description: RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
-
A.
RFC 5751
RFC 5751 is the Internet standards document that specifies the Secure/Multipurpose Internet Mail Extensions (S/MIME) protocol for secure email communication.
-
B.
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.
-
C.
RFC 6856
RFC 6856 is an Internet standards document that updates and extends the Post Office Protocol version 3 (POP3), superseding earlier specifications such as RFC 1939.
-
D.
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.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| area | Transport Area ⓘ |
| category | Standards Track ⓘ |
| defines |
NFSv4.1 data types
ⓘ
NFSv4.1 operations ⓘ NFSv4.1 parallel NFS (pNFS) framework ⓘ NFSv4.1 protocol architecture ⓘ NFSv4.1 security model ⓘ NFSv4.1 sessions mechanism ⓘ NFSv4.1 state management ⓘ XDR data types for NFSv4.1 protocol messages ⓘ access control model for NFSv4.1 ⓘ attributes model for NFSv4.1 ⓘ callback mechanisms for NFSv4.1 ⓘ client ID and lease management for NFSv4.1 ⓘ client-server interactions for NFSv4.1 ⓘ compound operations for NFSv4.1 ⓘ delegations and caching behavior for NFSv4.1 ⓘ error codes and status values for NFSv4.1 ⓘ file locking semantics for NFSv4.1 ⓘ filehandle and namespace model for NFSv4.1 ⓘ internationalization and UTF-8 filename handling for NFSv4.1 ⓘ layout types for pNFS ⓘ migration and replication mechanisms for NFSv4.1 ⓘ recovery and failover behavior for NFSv4.1 ⓘ security negotiation using RPCSEC_GSS for NFSv4.1 ⓘ session trunking and connection management for NFSv4.1 ⓘ session-based exactly-once semantics for NFSv4.1 ⓘ stateid-based state tracking for NFSv4.1 ⓘ |
| definesProtocolVersion |
NFS
ⓘ
surface form:
NFSv4.1
|
| extends |
NFS
ⓘ
surface form:
NFS version 4
|
| format | text ⓘ |
| intendedUse |
distributed file access
ⓘ
network file sharing ⓘ |
| language | English ⓘ |
| obsoletes | RFC 3530 ⓘ |
| protocolFamily | NFS ⓘ |
| publicationMonth | January ⓘ |
| publicationYear | 2010 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| RFCNumber | 5661 ⓘ |
| specifies |
NFS
ⓘ
surface form:
Network File System version 4 minor version 1
|
| status | Proposed Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| title |
NFS
ⓘ
surface form:
Network File System (NFS) Version 4 Minor Version 1 Protocol
|
| updates | RFC 3530 ⓘ |
| workingGroup |
NFS
ⓘ
surface form:
Network File System Version 4 (nfsv4)
|
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 5661 Description of subject: RFC 5661 is the Internet Engineering Task Force (IETF) standard that specifies version 4.1 of the Network File System (NFS) protocol, detailing its architecture, operations, and extensions for distributed file access.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.