M.Sc.

Julio Santisteban Pablo

Telnet
Ports numbers (iana.org)
DateTime
NTP



TELNET
TELNET (TErminaL NETwork) is a network protocol
used on the Internet or local area networks to
provide a bidirectional interactive communications
facility
Telnet was developed in 1969 beginning with RFC 15
Telnet is a client-server protocol, based on a reliable
connection-oriented transport. Typically this
protocol is used to establish a connection to
Transmission Control Protocol (TCP) port number
23, where a Telnet server application (telnetd) is
listening. Telnet, however, predates TCP/IP and
was originally run over Network Control Program
(NCP) protocols.
Telnet
Telnet protocol itself has been mostly superseded for
remote login, Telnet clients are still used, often
when diagnosing problems, to manually "talk" to
other services without specialized client software.
For example, it is sometimes used in debugging
network services such as SMTP, IRC, HTTP, FTP
or POP3 servers, to issue commands to a server
and examine the responses
limitations due to terminal control handshaking and
the special rules regarding \377 and \15. nc
(netcat) and PuTTy
Telnet superseded
Enterprise networks to access host applications, e.g., on IBM
Mainframes.
Administration of network elements, e.g., in commissioning,
integration and maintenance of core network elements in mobile
communication networks, and many industrial control systems.
MUD games played over the Internet, as well as talkers, MUSHes,
MUCKs, MOOes, and the resurgent BBS community.
Internet game clubs, like the Internet Chess Club, the Free Internet
Chess Server and the Internet Go server.
Embedded systems.
Mobile data collection applications where telnet runs over secure
networks
Collaboration of multiple users where the capability of session
transfer, swap, sharing, and recovery of disconnected sessions is
needed
Telnet is popular in various areas
IBM 5250 or 3270 workstation emulation is supported
via custom telnet clients, TN5250/TN3270, and IBM
servers. Clients and servers designed to pass IBM
5250 data streams over Telnet generally do support
SSL encryption, as SSH does not include 5250
emulation.
IBM 5250

http://www.iana.org/assignments/port-numbers
The port numbers are divided into three ranges: the Well Known Ports,
the Registered Ports, and the Dynamic and/or Private Ports.

The Well Known Ports are those from 0 through 1023.

DCCP Well Known ports SHOULD NOT be used without IANA registration.
The registration procedure is defined in [RFC4340], Section 19.9.

The Registered Ports are those from 1024 through 49151

DCCP Registered ports SHOULD NOT be used without IANA registration.
The registration procedure is defined in [RFC4340], Section 19.9.

The Dynamic and/or Private Ports are those from 49152 through 65535
PORT NUMBERS
The DAYTIME service is an Internet protocol defined
in 1983 in RFC 867. It is intended for testing and
measurement purposes in computer networks.

A host may connect to a server that supports the
DAYTIME protocol, on either TCP or UDP port 13.
The server then returns the current date and time
as an ASCII string with an unspecified format.

DateTime
nist1-ny.ustiming.org
time-a.nist.gov
time-b.nist.gov
nist1.aol-va.symmetricom.com


> telnet time-b.nist.gov 13
55279 10-03-24 19:50:42 50 0 0 474.0 UTC(NIST) *

Connection to host lost.
>


demo
The Network Time Protocol (NTP) is a protocol for
synchronizing the clocks of computer systems over
packet-switched, variable-latency data networks.
NTP uses UDP on port 123 as its transport layer. It
is designed particularly to resist the effects of
variable
support for features such as leap seconds
provides Coordinated Universal Time (UTC), No
information about time zones or daylight saving
time is transmitted
Simple Network Time Protocol (SNTP)
Network Time Protocol
Unix
implemented as a daemon process that runs continuously
in user space (ntpd)
Microsoft Windows
since Windows 2000 include the Windows Time
Service,[3] which has the ability to sync the computer
clock to an NTP server. However, the version in
Windows 2000 only implements Simple NTP, and
violates several aspects of the NTP version 3
standard. Beginning with Windows Server 2003
Windows Time Service cannot maintain the system
time more accurately than about a 1-2 second range
Network Time Protocol
The 64-bit timestamps used by NTP consist of a 32-
bit seconds part and a 32-bit fractional second part,
giving NTP a time scale of 2^32
The NTP timescale wraps around every 2^32
seconds (136 years). NTP uses an epoch of
January 1, 1900, so the first rollover will occur in
2036, well before the familiar UNIX Year 2038
problem.
The 64 bit second value is enough to provide
unambiguous time representation until the universe
goes dim. Indeed, 2^64 seconds is about 54
zeptoseconds, and 2^64 seconds is about 585
billion years
NTP
Stratum0: devices such as atomic (caesium,
rubidium) clocks
Stratum1: PC to clock device, PC as server
Stratum2: PC to PC, peer groups, PC as server
Stratum3: same as Stratum 2, up to 16 levels,
supports up to 256.
NTP Stratum

NTP
nist1-ny.ustiming.org
time-a.nist.gov
time-b.nist.gov
nist1.aol-va.symmetricom.com


> telnet time-b.nist.gov 123




NTP