RFC 866

E197375

RFC 866 is an early Internet standard that specifies the "Daytime Protocol," a simple service for returning the current date and time over a network connection.

Try in SPARQL Jump to: Surface forms Statements Referenced by

All labels observed (1)

Label Occurrences
RFC 866 canonical 1

Statements (45)

Predicate Object
instanceOf Internet standard
Request for Comments
accessMethod Publicly available via RFC repositories
category Network protocol specification
connectionDirection Client initiates connection to server
connectionModel Client-server
dataFormat ASCII text
definesService Daytime service
describes Daytime Protocol
documentSeries RFCs
surface form: RFC series
intendedClients Any host capable of opening TCP or UDP connections
language English
medium Text document
networkLayer Application layer
obsoletedBy More modern time synchronization protocols
operatesOver IP networks
the internet
surface form: Internet
organizationContext IETF community
surface form: Internet Engineering community
originalPurpose Provide a simple daytime service for testing and demonstration
outputCharacteristic Implementation-dependent date and time format
portAssignmentAuthority IANA
portType Well-known port
protocolName Daytime Protocol
publicationMonth May
publicationYear 1983
relatedTo RFC 867
Time Protocol
responseContent Current date
Current time
responseTermination Server closes connection after sending time
responseTrigger Server sends time upon connection
scope Simple time reporting, not time synchronization
securityConsideration No authentication or encryption defined
serviceFunction Return current date and time as human-readable text
standardType Informational protocol specification
status Historic
tcpPort 13
terminology Daytime client
Daytime server
title Daytime Protocol
transportProtocol Transmission Control Protocol
surface form: TCP

UDP
udpPort 13
useCase Providing simple time-of-day information
Testing and debugging network connectivity

Referenced by (1)

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

RFC 854 relatedRFC RFC 866