DOCSLIB.ORG

The Network Time Protocol David L

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The Network Time Protocol David L 1482 IEEE TRANSACTIONS ON COMMUNICATIONS, VOL. 39, NO. 10, OCTOBER 1991 Internet Time Synchronization: The Network Time Protocol David L. Mills, Member, IEEE Abstruct- This paper describes the network time protocol a similar number of gateways. In this paper the capitalized (NTP),which is designed to distribute time information in a large, Internet refers to this particular system, while the uncapitalized diverse internet system operating at speeds from mundane to internet refers to any generic system of multiple networks lightwave. It uses a symmetric architecture in which a distributed subnet of time servers operating in a self-organizing, hierarchical interconnected by gateways. While the Internet backbone configuration synchronizes local clocks within the subnet and networks and gateways are carefully engineered for good to national time standards via wire, radio, or calibrated atomic service, operating speeds, and service reliability vary consid- clock. The servers can also redistribute time information within erably throughout the system. This places severe demands a network via local routing algorithms and time daemons. on NTP, which must deliver accurate and reliable time in This paper also discusses the architecture, protocol and algo- rithms, which were developed over several years of implementa- spite of component failures, service disruptions and possibly tion refinement and resulted in the designation of NTP as an mis-engineered implementations. Internet Standard protocol. The NTP synchronization system, In the remainder of this introductory Section I, issues in which has been in regular operation in the Internet for the the requirements, approaches, and comparisons with previ- last several years, is described along with performance data ous work are discussed. The architecture of the NTP syn- which shows that timekeeping accuracy throughout most portions of the Internet can be ordinarily maintained to within a few chronization system, including the primary reference sources milliseconds, even in cases of failure or disruption of clocks, time and distribution mechanisms, is described in Section 11. An servers or networks. overview of the NTP protocol and modes of operation is given in Section 111. Section IV describes the algorithms used to im- prove the accuracy of measurements made over Internet paths I. INTRODUCTION and to select the best from among a set of available clocks CCURA", reliable time is necessary for financial and for synchronization. Section V describes a local-clock design Alegal transactions, transportation and distribution systems based on a type of phase-lock loop and capable of long-term and many other applications involving widely distributed accuracies to the order of a few milliseconds. The international resources. How do hosts in a large, dispersed networking com- NTP synchronization system of time servers now operating munity know what time it is? How accurate are their clocks? In in the Internet is described and its performance assessed in a recent survey involving 94 260 hosts of the Internet system, Section VI. Section VI1 discusses further development and 20 758 provided local time using three time-transfer protocols issues for future research. This paper itself is an updated and [24]. About half of the replies had errors greater than 2 min, condensed version of [23]. while 10% had errors greater than 4 h. A few had errors over two weeks. Most local clocks are set by eyeball-and- A. Definitions wristwatch to within a minute or two and rarely checked after In this paper, the stability of a clock is how well it can that. Many of these are maintained by some sort of battery- maintain a constant frequency, the accuracy is how well its backed clock-calendar device using a room-temperature quartz time compares to national standards and the precision is how oscillator that may drift as much as a second per day and precisely time can be resolved in a particular timekeeping can go for weeks between manual corrections. For many system. The offset of two clocks is the time difference between applications, especially distributed internet applications, much them, while the skew is the frequency difference between them. greater accuracy and reliability is required. The reliability of a timekeeping system is the fraction of the This paper presents an overview of the architecture, protocol time it can be kept operating and connected in the network and algorithms of the network time protocol (NTP) used (without respect to stability and accuracy). Local clocks are in the Internet system to synchronize clocks and coordinate maintained at designated time servers, which are timekeeping time distribution. The Internet consists of over 100000 hosts systems belonging to a synchronization subnet, in which each on over 1500 packet-switching networks interconnected by server measures the offsets between its local clock and the clocks of its neighbor servers or peers in the subnet. In this Paper approved by the Editor for Network Protocols of the IEEE Communi- paper to synchronizefrequency means to adjust the clocks in cations Society. Manuscript received February 10, 1989; revised January 29, 1990 and July 18, 1990. This work was supported in part by the Defense the subnet to run at the same frequency, to synchronize time Advanced Research Projects Agency under Contract N00140-87-C-8901 and means to set them to agree at a particular epoch with respect by the National Science Foundation under Grant NCR-89-13623. to coordinated universal time (UTC), as provided by national The author is with the Department of Electrical Engineering, University of Delaware, Newark, DE 19716. standards, and to synchronize clocks means to synchronize IEEE Log Number 9101515. them in both frequency and time. 009&6778/91$01.00 0 1991 IEEE MILLS: INTERNET TIME SYNCHRONIZATION 1483 B. Performance Requirements radio services with a UTC timecode modulation which can Internet transmission paths can have wide variation in delay be decoded by suitable receivers. One approach to time and reliability due to traffic load, route selection, and facil- synchronization is to provide timecode receivers at every ity outages. Stable frequency synchronization requires stable site where required. However, these receivers are specialized, local-clock oscillators and multiple offset comparisons over moderately expensive and subject to occasional gross errors relatively long periods of time, while reliable time synchro- due to propagation and equipment failures. A comprehensive nization requires carefully engineered selection algorithms and summary of radio synchronization techniques can be found in the use of redundant resources and diverse transmission paths. [41. For instance, while only a few offset comparisons are usually The U.S. National Institute of Standards and Technology adequate to determine local time in the Internet to within a (NIST) (formerly National Bureau of Standards), recently few tens of milliseconds, dozens of measurements over some announced a computer time service available to the general days are required to reliably stabilize frequency to a few public by means of a standard telephone modem [26]. The milliseconds per day. Thus, the performance requirements of service is intended for use by personal workstations to set an intemet-based time synchronization system are particularly clock-calendars, for example, but would not be suitable for a demanding. A basic set of requirements must include the large population of clients calling on a frequent, regular basis following. without further redistribution. 1) The primary reference source(s) must be synchronized to In principle, it is possible to use special network facilities national standards by wire, radio, or calibrated atomic clock. designed for time synchronization, such as timecode rebroad- The time servers must deliver continuous local time based casts on a dedicated FM or TV subcarrier or cable system. on UTC, even when leap seconds are inserted in the UTC For many years AT&T has synchronized digital switching timescale. equipment to the basic synchronization reference frequency 2) The time servers must provide accurate and precise time, (BSRF), which consists of a master oscillator synchronized to even with relatively large delay variations on the transmission UTC and a network of dedicated 2048-kHz links embedded in paths. This requires careful design of the filtering and com- the transmission plant. AT&T and other carriers are planning bining algorithms, as well as an extremely stable local-clock to use the global positioning system and the LORAN-C radio oscillator and synchronization mechanism. navigation system to synchronize switches in various areas 3) The synchronization subnet must be reliable and sur- of the country. However, neither of these methods would be vivable, even under unstable network conditions and where economically viable for widespread deployment in a large, connectivity may be lost for periods up to days. This requires diverse internet system. redundant time servers and diverse transmission paths, as well Current network clock synchronization techniques have as a dynamically reconfigurable subnet architecture. evolved from both linear systems and Byzantine agreement 4) The synchronization protocol must operate continuously methodologies. Linear methods for digital telephone network and provide update information at rates sufficient to compen- synchronization are summarized in [ 161, while Byzantine sate for the expected wander of the room-temperature
Load more

Recommended publications
  • List of TCP and UDP Port Numbers - Wikipedia, the Free Encyclopedia 6/12/11 3:20 PM
    List of TCP and UDP port numbers - Wikipedia, the free encyclopedia 6/12/11 3:20 PM List of TCP and UDP port numbers From Wikipedia, the free encyclopedia (Redirected from TCP and UDP port numbers) This is a list of Internet socket port numbers used by protocols of the Transport Layer of the Internet Protocol Suite for the establishment of host-to-host communications. Originally, these port numbers were used by the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP), but are used also for the Stream Control Transmission Protocol (SCTP), and the Datagram Congestion Control Protocol (DCCP). SCTP and DCCP services usually use a port number that matches the service of the corresponding TCP or UDP implementation if they exist. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses.[1] However, many unofficial uses of both well-known and registered port numbers occur in practice. Contents 1 Table legend 2 Well-known ports: 0–1023 3 Registered ports: 1024–49151 4 Dynamic, private or ephemeral ports: 49152–65535 5 See also 6 References 7 External links Table legend Color coding of table entries Official Port/application combination is registered with IANA Unofficial Port/application combination is not registered with IANA Conflict Port is in use for multiple applications (may be official or unofficial) Well-known ports: 0–1023 The port numbers in the range from 0 to 1023 are the well-known ports. They are used by system processes that provide widely-used types of network services.
    [Show full text]
  • List of TCP and UDP Port Numbers from Wikipedia, the Free Encyclopedia
    List of TCP and UDP port numbers From Wikipedia, the free encyclopedia This is a list of Internet socket port numbers used by protocols of the transport layer of the Internet Protocol Suite for the establishment of host-to-host connectivity. Originally, port numbers were used by the Network Control Program (NCP) in the ARPANET for which two ports were required for half- duplex transmission. Later, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) needed only one port for full- duplex, bidirectional traffic. The even-numbered ports were not used, and this resulted in some even numbers in the well-known port number /etc/services, a service name range being unassigned. The Stream Control Transmission Protocol database file on Unix-like operating (SCTP) and the Datagram Congestion Control Protocol (DCCP) also systems.[1][2][3][4] use port numbers. They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses.[5] However, many unofficial uses of both well-known and registered port numbers occur in practice. Contents 1 Table legend 2 Well-known ports 3 Registered ports 4 Dynamic, private or ephemeral ports 5 See also 6 References 7 External links Table legend Official: Port is registered with IANA for the application.[5] Unofficial: Port is not registered with IANA for the application. Multiple use: Multiple applications are known to use this port. Well-known ports The port numbers in the range from 0 to 1023 are the well-known ports or system ports.[6] They are used by system processes that provide widely used types of network services.
    [Show full text]
  • Implementing TCP/IP
    4620-1 ch03.f.qc 10/28/99 11:56 AM Page 59 Chapter 3 Implementing TCP/IP In This Chapter ᮣ Defining TCP/IP ᮣ Microsoft’s implementation of TCP/IP ᮣ A detailed analysis of TCP ᮣ A detailed analysis of IP ᮣ Windows Sockets: a definition and the application ᮣ Three parts of Internet addressing: the IP address, subnet mask, and default gateway ᮣ Windows 2000 Server basic routing ave you ever wondered what the payoff was from years of US military Hexpenditures? Was it $200 wrenches and other doodads publicly highlighted by former Senator William Proxmire and his “Golden Fleece” awards? No, two of the great payoffs from the huge military buildup that have spanned generations are Transmission Control Protocol/Internet Protocol (TCP/IP) and the Internet itself. Not only has TCP/IP become a de facto standard for internetworking, it is also the default protocol for Windows 2000 Server. As I prepared this chapter, I promised myself that I wouldn’t drone on about the history of the Internet, Request for Comments (RFCs), and other historical hooey that has been covered in far too many books. In fact, I make two assumptions: First, that you are not a newbie — you know the definition of TCP/IP and have other thicker and more technical resources dedicated specifically to TCP/IP. And second, that perhaps like me, you have trouble sitting still when the going gets boring; if the presentation of TCP/IP (which can be very dry) isn’t exciting, you will drift away and miss the finer points about TCP/IP that are important to catch.
    [Show full text]
  • Network Time Protocol (Version 2) Specification and Implementation
    Network Working Group David L. Mills Request for Comments: 1119 University of Delaware Obsoletes: RFC-1059, RFC-958 September 1989 Network Time Protocol (Version 2) Specification and Implementation Status of this Memo This document describes the Network Time Protocol (NTP), specifies its formal structure and summarizes information useful for its implementation. NTP provides the mechanisms to synchronize time and coordinate time distribution in a large, diverse internet operating at rates from mundane to lightwave. It uses a returnable-time design in which a distributed subnet of time servers operating in a self-organizing, hierarchical-master-slave configuration synchronizes local clocks within the subnet and to national time standards via wire or radio. The servers can also redistribute reference time via local routing algorithms and time daemons. This is an Internet Standard Recommended Protocol. Distribution of this memo is unlimited. Keywords: network clock synchronization, standard time distribution, fault-tolerant architecture, maximum-likelihood estimation, disciplined oscillator, internet protocol, formal specification. Mills Page i RFC-1119 Network Time Protocol September 1989 Table of Contents 1. Introduction . 1 1.1. Related Technology . 2 2. System Architecture . 3 2.1. Implementation Model . 4 2.2. Network Configurations . 5 2.3. The NTP Timescale . 7 2.4. The NTP Calendar . 8 2.5. Time and Frequency Dissemination . 10 3. Network Time Protocol . 11 3.1. Data Formats . 11 3.2. State Variables and Parameters . 12 3.2.1. Common Variables . 12 3.2.2. System Variables . 14 3.2.3. Peer Variables . 16 3.2.4. Packet Variables . 17 3.2.5. Clock Filter Variables . 17 3.2.6.
    [Show full text]
  • List of TCP and UDP Port Numbers - Wikipedia, the Free Encyclopedia 08/31/2007 04:24 PM
    List of TCP and UDP port numbers - Wikipedia, the free encyclopedia 08/31/2007 04:24 PM List of TCP and UDP port numbers From Wikipedia, the free encyclopedia (Redirected from TCP and UDP port numbers) TCP and UDP are transport protocols used for communication between computers. The IANA is responsible for assigning port numbers to specific uses. Contents 1 Ranges 2 Port lists 2.1 Ports 0 to 1023 2.2 Ports 1024 to 49151 2.3 Ports 49152 to 65535 2.4 Multi cast Adresses 3 References 4 External links Ranges The port numbers are divided into three ranges. The Well Known Ports are those in the range 0–1023. On Unix-like operating systems, opening a port in this range to receive incoming connections requires administrative privileges or possessing of CAP_NET_BIND_SERVICE capability. The Registered Ports are those in the range 1024–49151. The Dynamic and/or Private Ports are those in the range 49152–65535. These ports are not used by any defined application. IANA does not enforce this; it is simply a set of recommended uses. Sometimes ports may be used for different applications or protocols than their official IANA designation. This misuse may, for example, be by a Trojan horse, or alternatively be by a commonly used program that didn't get an IANA registered port or port range. Port lists The tables below indicate a status with the following colors and tags: Official if the application and port combination is in the IANA list of port assignments (http://www.iana.org/assignments/port-numbers) ; Unofficial if the application and port combination is not in the IANA list of port assignments; and Conflict if the port is being used commonly for two applications or protocols.
    [Show full text]
  • TCP/IP Explained
    TCP/IP Explained PHILIP MILLER DIGITAL PRESS Boston Oxford Johannesburg Melbourne New Delhi Singapore Table of Contents Preface xvii Chapter 1 - Introduction 1 1.1 What is TCP/IP? 1 1.1.1 A Brief History of TCP/IP 2 1.1.2 The Internet Protocol Suite 3 1.2 The Internet 5 1.2.1 The Growth of the Internet 6 1.3 Summary 9 Chapter 2 - Standardization 11 2.1 The Internet Architecture Board 11 2.1.1 The Internet Engineering Task Force 12 2.1.2 The Internet Research Task Force 13 2.2 Internet Protocol Standards 13 2.2.1 Protocol States 14 2.2.2 Protocol Status 16 2.2.3 The Request For Comments (RFC) 16 2.3 Internet Protocol Architecture 17 2.3.1 The Open Systems Interconnection (OSI) Model 18 2.3.2 The OSI Model and LANs 20 2.3.3 The Internet Protocol Suite Model 23 2.4 A Comparison of Major Architectures 25 2.5 Summary 26 Chapter 3 - An Overview of Network Technologies and Relay Systems 27 3.1 Ethernet and IEEE 802.3 27 3.1.1 802.3 Specifications 27 3.1.2 Ethernet/802.3 Frame Structure 30 3.1.3 Ethernet/802.3 Operation 32 3.2 Token Ring 33 3.2.1 802.5 Specifications 34 3.2.2 802.5 Frame Structure 36 3.2.3 802.5 Operation 38 3.3 Fibre Distributed Data Interface (FDDI) 39 3.3.1 FDDI Specifications 41 3.3.2 FDDI Frame Structure 42 3.3.3 FDDI Operation 43 3.4 Relay Systems 43 3.4.1 Repeaters 44 3.4.2 Bridges 45 3.5 WAN Links 50 3.6 Summary 51 Chapter 4 - Internet Addressing 53 4.1 The Need for an Addressing Scheme 53 4.2 Internet Addressing 54 4.2.1 Dotted Decimal Notation 55 4.2.2 Identifying IP Addresses and Rules 56 4.2.3 Choosing the Right Addressing
    [Show full text]
  • Port Ranges Traffic Analysis
    Simon Owens Port Ranges • Ports 0 to 1023 are Well-Known Ports. • Ports 1024 to 49151 are Registered Ports (often registered by a software developer to designate a particular port for their application) • Ports 49152 to 65535 are Public Ports. Traffic Analysis - Wireshark Configure Name Resolution 1. Make a new profile 2. Make a “hosts” file with format “ip hostname” 3. Place that “hosts” file in the ~/.config/wireshark/configprofilename/ folder 4. open pcap file, select your configuration profile, and ensure “view>>name resolution>>resolve network/transport address names” is checked Configure Ports 1. Go to “Edit>>preferences>>columns” and add src and dst ports to the display Figuring out what multi-cast goes too 1. Fill out “hosts” and “services” file if you can 2. Click on various multi-cast products – generally the parameters will identify what the application is with a version or the company that made it. Query for Common Ports • tcp.dstport >= 0 and tcp.dstport <= 10000 || tftp || dns Saving off filters to make capture smaller 1. Apply a filter 2. Click “File>> Export Specified Packets” then save them to a file Search for Strings • Edit >> find packet Extracting files • file >> export objects Find Hashes • net-creds.py file.pcap Changing Parameters in the Packets Simon Owens • Port Scan Netdiscover -r <ip-range> make sure you know everything on network IP=insert mkdir $IP Masscan: • masscan -p0-65535 $IP --banners -oG $IP/masscan_$IP.grep Nmap: • Nmap -sV -T4 $IP -oN $IP/normalNmap.txt • nmap -v -sS -T4 -A --script=vuln --host-timeout 336h -p 0-65535 $IP -oA $IP/TCPscan_$IP • nmap -v -sU -T4 -A --script=vuln --host-timeout 336h -p 0-65535 $IP -oA $IP/UDPscan_$IP General Services: • 9/tcp - Discard o Discard Protocol - https://www.exploit-db.com/exploits/19555 The Discard Protocol is a service in the Internet Protocol Suite defined in RFC 863.
    [Show full text]
  • LANTIME M300: NTP Server in 1U Case for Server Rackmount
    Meinberg Radio Clocks Lange Wand 9 31812 Bad Pyrmont, Germany Phone: +49 (5281) 9309-0 Fax: +49 (5281) 9309-30 https://www.meinberg.de [email protected] LANTIME M300: NTP Server in 1U Case for Server Rackmount [1] The Meinberg LANTIME M300 time server provides accurate time to networks of any size. It synchronizes all NTP- or SNTP-compatible systems. The M300 time server uses as a reference time source either any compatible external or built-in Meinberg reference clock (Stratum 1 mode) or up to 7 NTP servers (Stratum 2 mode). Key Features - Selectable Reference Time Sources: * [2]GPS: Satellite receiver for the Global Positioning System * [3]GLN: Combined GPS/GLONASS satellite receiver (L1 frequency band), can also be used for mobile applications * [4]PZF: DCF77 correlation receiver for middle europe * [5]MSF: Long wave receiver for Great Britain * [6]WWVB: Long wave receiver for the US time signal * [7]TCR: Time code receiver for IRIG A/B, AFNOR or IEEE1344 codes * [8]MRS: (GPS, PPS, 10MHz, NTP): Multi Reference Source - several reference sources, adjustable following priority of signal * [9]RDT: (external PPS or NTP): Time Server without internal receiver module - Synchronization of NTP and SNTP compatible clients - Web based status and configuration interface [10](Demo) and console based graphical configuration utility - Supported net protocols: IPv4, IPv6, NTP, (S)NTP, DAYTIME, DHCP, HTTP, HTTPS, FTP, SFTP, SSH, SCP, SYSLOG, SNMP, TIME, TELNET - Alert-Notification system of status change by Email, WinMail, SNMP or an external connected
    [Show full text]
  • Siteplayer Telnet User's Manual
    RS232 to Ethernet Protocol Converter User’s Manual Version 1.11 2-Oct-06 (For SitePlayer Telnet Software Version 1.4ahu and above) *POE version depicted © 2004-2006 Netmedia Inc. All Rights Reserved. 10940 N Stallard Place Tucson, AZ 85737 520.544.4567 NetMedia, Inc. 10940 N. Stallard Place Tucson, Arizona 85737 TEL: (520) 544-4567 FAX: (520) 544-0800 PURCHASE TERMS AND CONDITIONS The laws of the State of Arizona shall govern PURCHASE TERMS AND CONDITIONS. LIMITED WARRANTY: NETMEDIA MAKES NO WARRANTIES OTHER THAN THOSE CONTAINED HEREIN AND NETMEDIA EXPRESSLY DISCLAIMS ANY AND ALL IMPLIED WARRANTIES, INCLUDING ANY WARRANTY OF FITNESS FOR A PARTICU- LAR PURPOSE OR OF MERCHANTABILITY. The foregoing limited warranty shall not apply unless Buyer has paid for in full the NetMedia products. Elec- tronic updates to the NetMedia SitePlayer User’s Manual and NetMedia SitePlayer software are available free to Registered Buyer upon request for a one (1) year period from the invoice date. NOTICE NetMedia, Inc. reserves the right to make improvements in the software product described in this manual as well as the manual itself at any time and without notice. DISCLAIMER OF ALL WARRANTIES AND LIABILITY NETMEDIA, INC. MAKES NO WARRANTIES, EITHER EXPRESSED OR IMPLIED, WITH RESPECT TO THIS MANUAL OR WITH RESPECT TO THE SOFTWARE DESCRIBED IN THIS MANUAL, ITS QUALITY, PERFORMANCE, MER- CHANTABILITY, OR FITNESS FOR ANY PARTICULAR PURPOSE. NETMEDIA, INC. SOFTWARE IS SOLD OR LI- CENSED “AS IS”. IN NO EVENT SHALL NETMEDIA, INC. BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAM- AGES RESULTING FROM ANY DEFECT IN THE SOFTWARE.
    [Show full text]
  • LANTIME M100: NTP Time Server with Internal Reference Clock for DIN Rail Installations
    Meinberg Radio Clocks Lange Wand 9 31812 Bad Pyrmont, Germany Phone: +49 (5281) 9309-0 Fax: +49 (5281) 9309-30 https://www.meinbergglobal.com [email protected] LANTIME M100: NTP Time Server with internal Reference Clock for DIN Rail Installations LANTIME M100 time servers can be installed to provide accurate time to small and medium sized computer networks. This entry level time server synchronizes all systems either NTP- or SNTP-compatible utilizing a built-in Meinberg radio clock as its primary reference time source. A stable and precise oscillator is capable of bridging interferences or a temporary loss of reception. Its compact form factor offers an ideal solution to network time synchronization needs in industrial and power generation/distribution networks. Key Features - Selectable Reference Sources: GPS: Satellite receiver for the Global Positioning System GNS: Combined GPS/GLONASS/Galileo/BeiDou satellite receiver (L1 frequency band), can also be used for mobile applications PZF: DCF77 correlation receiver for middle europe - Synchronization of NTP and SNTP compatible clients - Web-based status and configuration interface (Demo) and console-based graphical configuration utility - Supported net protocols: IPv4, IPv6, NTP, (S)NTP, DAYTIME, DHCP, HTTP, HTTPS, FTP, SFTP, SSH, SCP, SYSLOG, SNMP, TIME, TELNET - USB Port for installing firmware updates, locking frontpanel menu access and backup/restore of configuration and log files - Meinberg GPS Antenna/Converter Unit connected with up to 300m of standard coaxial cable RG58 rev 2017.0405.1416 Page 1/4 lantime-m100 Description Three LEDs (green/red) indicate the status of the three main components: Reference Time (e.g. GPS), Time Synchronization Service (NTP) and Network (Link status).
    [Show full text]
  • Results Are As of Mar - 26 - 2002
    Results are as of Mar - 26 - 2002 ======================================================================== STANDARDS ORDERED BY STD ======================================================================== Mnemonic Title RFC# STD# ------------------------------------------------------------------------ --------- Internet Official Protocol Standards 3000 1* -------- [Reserved for Assigned Numbers. See RFC 1700 and R 2 FC 3232.] -------- Requirements for Internet Hosts - Communication 1122 3 Layers -------- Requirements for Internet Hosts - Application 1123 3 and Support -------- [Reserved for Router Requirements. See RFC 1812.] 4 IP Internet Protocol 791 5 ICMP Internet Control Message Protocol 792 5 --------- Broadcasting Internet Datagrams 919 5 --------- Broadcasting Internet datagrams in the presence 922 5 of subnets -------- Internet Standard Subnetting Procedure 950 5 IGMP Host extensions for IP multicasting 1112 5 UDP User Datagram Protocol 768 6 TCP Transmission Control Protocol 793 7 TELNET Telnet Protocol Specification 854 8 TELNET Telnet Option Specifications 855 8 FTP File Transfer Protocol 959 9 SMTP Simple Mail Transfer Protocol 821 10 SMTP-SIZE SMTP Service Extension for Message Size Declaration 1870 10 MAIL Standard for the format of ARPA Internet text 822 11 messages -------- [Reserved for Network Time Protocol (NTP). See RFC 12 1305.] DOMAIN Domain names - concepts and facilities 1034 13 DOMAIN Domain names - implementation and specification 1035 13 -------- [Was Mail Routing and the Domain System. Now Histo 14 ric.] SNMP
    [Show full text]
  • List of TCP and UDP Port Numbers - Wikipedia, Th
    List of TCP and UDP port numbers - Wikipedia, th... https://en.wikipedia.org/wiki/List_of_TCP_and_U... List of TCP and UDP port numbers From Wikipedia, the free encyclopedia This is a list of Internet socket port numbers used by protocols of the transport layer of the Internet Protocol Suite for the establishment of host-to-host connectivity. Originally, port numbers were used by the Network Control Program (NCP) in the ARPANET for which two ports were required for half-duplex transmission. Later, the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) needed only one port for full-duplex, bidirectional traffic. The even-numbered ports were not used, and this resulted in some even numbers in the well-known port number range being unassigned. The Stream Control Transmission Protocol (SCTP) and the Datagram Congestion Control Protocol (DCCP) also use port numbers. They usually use port numbers that match the services of the corresponding TCP or UDP implementation, if they exist. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses.[1] However, many unofficial uses of both well-known and registered port numbers occur in practice. Contents 1 Table legend 2 Well-known ports 3 Registered ports 4 Dynamic, private or ephemeral ports 5 See also 6 References 7 External links Table legend Official: Port is registered with IANA for the application.[1] Unofficial: Port is not registered with IANA for the application. Multiple use: Multiple applications are known to use this port. Well-known ports The port numbers in the range from 0 to 1023 are the well-known ports or system ports.[2] They are used by system processes that provide widely used types of network services.
    [Show full text]