9P network protocol
E632955
The 9P network protocol is a lightweight, file-oriented protocol from the Plan 9 operating system that unifies access to files, devices, and services across local and distributed environments.
All labels observed (1)
| Label | Occurrences |
|---|---|
| 9P network protocol canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T6991589 — 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: 9P network protocol Context triple: [Plan 9 from Bell Labs, keyConcept, 9P network protocol]
-
A.
IEEE 802.19
IEEE 802.19 is an IEEE working group that develops standards and guidelines to ensure effective coexistence and interference management among wireless networks operating in shared or adjacent frequency bands.
-
B.
NPN (Next Protocol Negotiation)
NPN (Next Protocol Negotiation) is a now-deprecated TLS extension that allowed a client and server to agree on which application-layer protocol (such as SPDY or HTTP/2) to use over a secure connection.
-
C.
PULSE network
PULSE network is a major U.S. electronic funds transfer and debit payment network widely used for ATM and point-of-sale transactions.
-
D.
PDCP
PDCP (Packet Data Convergence Protocol) is a key LTE/E-UTRAN layer responsible for header compression, security (ciphering and integrity), and in-sequence delivery of user and control plane data between the radio network and the core.
-
E.
IEEE 1901
IEEE 1901 is an international standard that defines high-speed broadband communication over power lines, enabling data transmission for applications like home networking and smart grid systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: 9P network protocol Target entity description: The 9P network protocol is a lightweight, file-oriented protocol from the Plan 9 operating system that unifies access to files, devices, and services across local and distributed environments.
-
A.
IEEE 802.19
IEEE 802.19 is an IEEE working group that develops standards and guidelines to ensure effective coexistence and interference management among wireless networks operating in shared or adjacent frequency bands.
-
B.
NPN (Next Protocol Negotiation)
NPN (Next Protocol Negotiation) is a now-deprecated TLS extension that allowed a client and server to agree on which application-layer protocol (such as SPDY or HTTP/2) to use over a secure connection.
-
C.
PULSE network
PULSE network is a major U.S. electronic funds transfer and debit payment network widely used for ATM and point-of-sale transactions.
-
D.
PDCP
PDCP (Packet Data Convergence Protocol) is a key LTE/E-UTRAN layer responsible for header compression, security (ciphering and integrity), and in-sequence delivery of user and control plane data between the radio network and the core.
-
E.
IEEE 1901
IEEE 1901 is an international standard that defines high-speed broadband communication over power lines, enabling data transmission for applications like home networking and smart grid systems.
- F. None of above. chosen
Statements (55)
| Predicate | Object |
|---|---|
| instanceOf |
distributed system protocol
ⓘ
file protocol ⓘ network protocol ⓘ |
| alsoKnownAs |
9P
NERFINISHED
ⓘ
Styx NERFINISHED ⓘ |
| associatedWithOperatingSystem |
Inferno OS
NERFINISHED
ⓘ
Linux (via v9fs) NERFINISHED ⓘ Plan 9 NERFINISHED ⓘ |
| associatedWithOrganization | Bell Labs NERFINISHED ⓘ |
| canRunOver |
IL protocol
ⓘ
TCP NERFINISHED ⓘ Unix domain sockets ⓘ shared memory transports ⓘ |
| category |
Plan 9 technology
ⓘ
remote file system protocol ⓘ |
| designedBy | Bell Labs NERFINISHED ⓘ |
| designGoal |
simplicity
ⓘ
transparency between local and remote resources ⓘ uniform namespace ⓘ unify access to files, devices, and services ⓘ |
| developedFor | Plan 9 from Bell Labs NERFINISHED ⓘ |
| hasImplementation |
Inferno Styx server
ⓘ
Plan 9 kernel server NERFINISHED ⓘ v9fs Linux kernel client NERFINISHED ⓘ |
| influenced |
Inferno operating system protocol design
NERFINISHED
ⓘ
Linux v9fs file system NERFINISHED ⓘ |
| messageType |
R-message
ⓘ
T-message ⓘ |
| namespaceModel | single hierarchical namespace ⓘ |
| operatesOnAbstraction |
directory
ⓘ
file ⓘ file system namespace ⓘ |
| originCountry |
United States of America
ⓘ
surface form:
United States
|
| primaryDesigner |
Dennis Ritchie
NERFINISHED
ⓘ
Ken Thompson NERFINISHED ⓘ Rob Pike NERFINISHED ⓘ |
| releaseContext | Plan 9 operating system NERFINISHED ⓘ |
| securityModel | user-based permissions ⓘ |
| supportsFeature | per-user namespaces ⓘ |
| supportsOperation |
attach
ⓘ
clunk ⓘ create ⓘ open ⓘ read ⓘ remove ⓘ stat ⓘ walk ⓘ write ⓘ wstat ⓘ |
| transportAgnostic | true ⓘ |
| usedFor |
accessing devices as files
ⓘ
accessing services as files ⓘ remote file system access ⓘ |
| usesConcept |
fid
ⓘ
tag ⓘ |
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: 9P network protocol Description of subject: The 9P network protocol is a lightweight, file-oriented protocol from the Plan 9 operating system that unifies access to files, devices, and services across local and distributed environments.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.