RFC 783

E45563

RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (1)

Label Occurrences
RFC 783 canonical 2

Statements (48)

Predicate Object
instanceOf Internet standard specification
Request for Comments
area Applications
authentication none
author Noel Chiappa
category Standards Track
checksum relies on UDP checksum
connectionType lockstep stop-and-wait
definesAcknowledgementMechanism per-block ACK
definesDefaultBlockSize 512 bytes
definesDirection client-initiated transfer
definesEndOfFileCondition DATA packet with less than 512 bytes
definesErrorHandling ERROR packet with error code and message
definesFileNameEncoding netascii for text files
definesMessageType ACK
DATA
ERROR
RRQ
WRQ
definesOperation read request
write request
definesProtocol TFTP
surface form: Trivial File Transfer Protocol
definesTransferMode mail
netascii
octet
intendedEnvironment simple, low-overhead file transfer
language English
month June
networkLayerIndependence true
obsoletedBy RFC 1350
obsoletes RFC 764
RFC 768
pageCount 18
portNumber 69
protocolScope Trivial file transfer
protocolType File transfer protocol
publishedBy Internet Activities Board
Internet Engineering Task Force
publishedInSeries RFC series
reliabilityMechanism retransmission on timeout
securityFeatures none
shortName TFTP specification
status Historic
title TFTP
surface form: The TFTP Protocol (Revision 2)
transportProtocol UDP
useCase bootstrap and diskless workstation loading
simple file transfer in local networks
year 1981

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 783
Description of subject: RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.

Referenced by (2)

Full triples — surface form annotated when it differs from this entity's canonical label.

TFTP originalRfc RFC 783
RFC 1350 obsoletes RFC 783