RFC 7530
E768630
RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 7530 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8950920 — 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 7530 Context triple: [RFC 3530, obsoletedBy, RFC 7530]
-
A.
RFC 7503
RFC 7503 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces RFC 5340 with revised specifications for the OSPFv3 routing protocol.
-
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 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
E.
RFC 7053
RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
- 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 7530 Target entity description: RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
-
A.
RFC 7503
RFC 7503 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces RFC 5340 with revised specifications for the OSPFv3 routing protocol.
-
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 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
E.
RFC 7053
RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
NFS protocol specification ⓘ Request for Comments ⓘ |
| area | Transport Area NERFINISHED ⓘ |
| category | Standards Track ⓘ |
| clarifies | NFSv4 core mechanisms ⓘ |
| defines |
NFS version 4 core protocol
ⓘ
NFSv4 COMPOUND operation framework NERFINISHED ⓘ NFSv4 OPEN and CLOSE semantics ⓘ NFSv4 attribute model ⓘ NFSv4 callback mechanisms ⓘ NFSv4 client ID and lease model ⓘ NFSv4 error codes and semantics ⓘ NFSv4 file locking via LOCK and LOCKU operations ⓘ NFSv4 security negotiation using RPCSEC_GSS ⓘ NFSv4 stateid handling ⓘ |
| definesPortUsage |
TCP
NERFINISHED
ⓘ
UDP NERFINISHED ⓘ |
| definesTransport |
RPC over TCP
ⓘ
RPC over UDP ⓘ |
| intendedUse |
Internet-wide file access
ⓘ
Network file system interoperability ⓘ |
| language | English ⓘ |
| obsoletes | RFC 3530 NERFINISHED ⓘ |
| organization | Internet Society NERFINISHED ⓘ |
| protocolFamily | NFS NERFINISHED ⓘ |
| publicationMonth | March ⓘ |
| publicationYear | 2015 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| refines | NFSv4 protocol semantics ⓘ |
| replaces | original NFS version 4 protocol definition ⓘ |
| rfcNumber | 7530 ⓘ |
| specifies |
NFSv4 client behavior
ⓘ
NFSv4 compound procedures NERFINISHED ⓘ NFSv4 error handling ⓘ NFSv4 file attributes ⓘ NFSv4 file locking model ⓘ NFSv4 namespace model ⓘ NFSv4 operations ⓘ NFSv4 security model ⓘ NFSv4 server behavior ⓘ NFSv4 state management ⓘ |
| status | Proposed Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | Network File System (NFS) Version 4 Protocol NERFINISHED ⓘ |
| updatesProtocolVersion | NFSv4 NERFINISHED ⓘ |
| workingGroup | Network File System Version 4 (nfsv4) 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 7530 Description of subject: RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.