DOCSLIB.ORG

Nmap TCP Ports (Scanned Using -F)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Nmap TCP Ports (scanned using -F) Port Service 7 Echo Protocol 9 Discard Protocol, SCTP 13 Daytime Protocol 21 File Transfer Protocol (FTP) 22 Secure Shell (scp, sftp) 23 Telnet 25 Simple Mail Transfer Protocol (SMTP) 26 AltaVista Firewall97, W32.Netsky 37 Time Protocol 53 Domain Name System (DNS) 79 Finger Protocol 80 Hypertext Transfer Protocol (HTTP) 81 TorPark onion routing 88 Kerberos 106 3COM-TSMUX, Eudora PW changer, Mac OS X Server (Password), poppassd 110 Post Office Protocol, version 3 (POP3) 111 Open Network Computing Remote Procedure Call (ONC RPC, aka Sun RPC) 113 Ident (Authentication for IRC), Authentication Service (auth) 119 Network News Transfer Protocol (NNTP) 135 DCE Endpoint Resolution, Microsoft EPMAP (Endpoint Mapper) 139 NetBIOS Session Service 143 Internet Message Access Protocol (IMAP) 144 Universal Management Architecture, NewS window system 179 Border Gateway Protocol (BGP) 199 SMUX, SNMP Unix Multiplexer 389 Lightweight Directory Access Protocol (LDAP) 427 Service Location Protocol (SLP) 443 Hypertext Transfer Protocol over TLS/SSL (HTTPS) 444 Simple Network Paging Protocol (SNPP) 445 Microsoft-DS (Directory Services) Active Directory, Windows Shares, SMB 465 Authenticated SMTP over TLS/SSL (SMTPS) 513 rlogin 514 Remote Shell 515 Line Printer Daemon (LPD) 543 klogin (Kerberos login) 544 kshell (Kerberos remote shell) 548 Apple Filing Protocol (AFP) over TCP 554 Real Time Streaming Protocol (RTSP) 587 Email Message Submission (SMTP) 631 Internet Printing Protocol (IPP) 646 Label Distribution Protocol (LDP) - used in MPLS 873 rsync File Synchronization Protocol 990 FTPS Protocol (control), FTP over TLS/SSL 993 Internet Message Access Protocol over TLS/SSL (IMAPS) 995 Post Office Protocol 3 over TLS/SSL (POP3S) 1025 Network Blackjack, NFS or ISS or Teradata, Windows RPC, Threats and Trojans 1026 Calendar Access Protocol, Microsoft DCOM, Windows RPC, Trojans 1027 icq instant messenger, Threats and Trojans 1028 Trojans 1029 Microsoft DCOM services 1110 Start Web Admin Server (webadmstart), Client Status Info (nfsd-keepalive), EasyBits, Threats 1433 Microsoft SQL Server (MSSQL) 1720 H.323 Call Signaling 1723 Point-to-Point Tunneling Protocol (PPTP) 1755 Microsoft Media Services (MMS, ms-streaming) 1900 Simple Service Discovery Protocl (SSDP), discovery of UPnP 2000 Cisco Skinny Client Control Protocol (SCCP) 2001 dc, wizard (curry), CAPTAN Test Stand System, Threats and Trojans 2049 Network File System (NFS) 2121 SCIENTIA-SSDB (scientia-ssdb), FTP proxy 2717 PN REQUESTER (pn-requester), KnowShowGo P2P 3000 Cloud9 IDE, Ruby on Rails, Meteor, Resilio Sync 3128 Squid caching web proxy 3306 MySQL database system 3389 Microsoft Terminal Server (RDP) aka Windows Based Terminal (WBT) 3986 GTP' 3GPP GSM/UMTS CDR logging protocol 4899 Radmin (radmin-port, radmin), W32.Rahack 5000 UPnP, Vtun VPN, Synology Management Console, Flask, Heroku, League of Legends 5009 Microsoft Windows Filesystem (winfs), AirPort Admin Utility 5051 ita-agent Symantec Intruder Alert 5060 Session Initiation Protocol (SIP) 5101 Talarian_TCP (talarian-tcp) 5190 AOL Instant Messenger 5357 Web Services for Devices (WSDAPI) 5432 PostgreSQL 5631 pcANYWHEREdata (Symantec) 5666 NRPE (Nagios) 5800 VNC Remote Frame Buffer over HTTP, ProjectWise Server 5900 Remote Frame Buffer protocol (RFB), Virtual Network Computing (VNC) RFB protocol 6000 X11 (X Window System) 6001 X11 6646 McAfee Network Agent 7070 Real Time Streaming Protocol (RTSP) 8000 SHOUTcast, Icecast, and iTunes Radio 8008 Alternative HTTP, IBM HTTP Server, iCal 8009 Apache Jserv (ajp13) 8080 Alternative HTTP, Apache Tomcat, Atlassian JIRA 8081 BlackICE ICEcap (blackice), Web Service, iTunes Radio Streams (irdmi), Sun Proxy 8443 SQ Soft Plesk, Apache Tomcat SSL, Promise WebPAM SSL, iCal over SSL 8888 Freenet web UI 9100 PDL Data Stream 9999 Urchin Web Analytics 10000 Network Data Management Protocol, BackupExec, Webmin 32768 Filenet TMS (filenet-tms), Hacker's Paradise (hackersparadise) 49152 Certificate Management over CMS 49153 Certificate Management over CMS 49154 Certificate Management over CMS 49155 Certificate Management over CMS 49156 Certificate Management over CMS 49157 Certificate Management over CMS.
Recommended publications
  • Towards Web-Based Delta Synchronization for Cloud Storage Services

    Towards Web-Based Delta Synchronization for Cloud Storage Services

    Towards Web-based Delta Synchronization for Cloud Storage Services He Xiao Zhenhua Li ∗ Ennan Zhai Tianyin Xu Tsinghua University Tsinghua University Yale University UIUC Yang Li Yunhao Liu Quanlu Zhang Yao Liu Tsinghua University Tsinghua University Microsoft Research SUNY Binghamton Abstract savings in the presence of users’ file edits [29, 39, 40]. Delta synchronization (sync) is crucial for network-level Unfortunately, today delta sync is only available for efficiency of cloud storage services. Practical delta sync PC clients and mobile apps, but not for the web—the most pervasive and OS-independent access method [37]. techniques are, however, only available for PC clients 0 and mobile apps, but not web browsers—the most per- After a file f is edited into a new version f by users, vasive and OS-independent access method. To under- Dropbox’s PC client will apply delta sync to automati- stand the obstacles of web-based delta sync, we imple- cally upload only the altered bits to the cloud; in contrast, Dropbox’s web interface requires users to manually up- ment a delta sync solution, WebRsync, using state-of- 0 1 the-art web techniques based on rsync, the de facto delta load the entire content of f to the cloud. This gap sig- sync protocol for PC clients. Our measurements show nificantly affects web-based user experiences in terms of that WebRsync severely suffers from the inefficiency of both sync speed and traffic cost. JavaScript execution inside web browsers, thus leading Web is a fairly popular access method for cloud stor- to frequent stagnation and even hanging.
  • Cheat Sheet – Common Ports (PDF)

    Cheat Sheet – Common Ports (PDF)

    COMMON PORTS packetlife.net TCP/UDP Port Numbers 7 Echo 554 RTSP 2745 Bagle.H 6891-6901 Windows Live 19 Chargen 546-547 DHCPv6 2967 Symantec AV 6970 Quicktime 20-21 FTP 560 rmonitor 3050 Interbase DB 7212 GhostSurf 22 SSH/SCP 563 NNTP over SSL 3074 XBOX Live 7648-7649 CU-SeeMe 23 Telnet 587 SMTP 3124 HTTP Proxy 8000 Internet Radio 25 SMTP 591 FileMaker 3127 MyDoom 8080 HTTP Proxy 42 WINS Replication 593 Microsoft DCOM 3128 HTTP Proxy 8086-8087 Kaspersky AV 43 WHOIS 631 Internet Printing 3222 GLBP 8118 Privoxy 49 TACACS 636 LDAP over SSL 3260 iSCSI Target 8200 VMware Server 53 DNS 639 MSDP (PIM) 3306 MySQL 8500 Adobe ColdFusion 67-68 DHCP/BOOTP 646 LDP (MPLS) 3389 Terminal Server 8767 TeamSpeak 69 TFTP 691 MS Exchange 3689 iTunes 8866 Bagle.B 70 Gopher 860 iSCSI 3690 Subversion 9100 HP JetDirect 79 Finger 873 rsync 3724 World of Warcraft 9101-9103 Bacula 80 HTTP 902 VMware Server 3784-3785 Ventrilo 9119 MXit 88 Kerberos 989-990 FTP over SSL 4333 mSQL 9800 WebDAV 102 MS Exchange 993 IMAP4 over SSL 4444 Blaster 9898 Dabber 110 POP3 995 POP3 over SSL 4664 Google Desktop 9988 Rbot/Spybot 113 Ident 1025 Microsoft RPC 4672 eMule 9999 Urchin 119 NNTP (Usenet) 1026-1029 Windows Messenger 4899 Radmin 10000 Webmin 123 NTP 1080 SOCKS Proxy 5000 UPnP 10000 BackupExec 135 Microsoft RPC 1080 MyDoom 5001 Slingbox 10113-10116 NetIQ 137-139 NetBIOS 1194 OpenVPN 5001 iperf 11371 OpenPGP 143 IMAP4 1214 Kazaa 5004-5005 RTP 12035-12036 Second Life 161-162 SNMP 1241 Nessus 5050 Yahoo! Messenger 12345 NetBus 177 XDMCP 1311 Dell OpenManage 5060 SIP 13720-13721
  • 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 - 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.
  • List of NMAP Scripts Use with the Nmap –Script Option

    List of NMAP Scripts Use with the Nmap –Script Option

    List of NMAP Scripts Use with the nmap –script option Retrieves information from a listening acarsd daemon. Acarsd decodes ACARS (Aircraft Communication Addressing and Reporting System) data in real time. The information retrieved acarsd-info by this script includes the daemon version, API version, administrator e-mail address and listening frequency. Shows extra information about IPv6 addresses, such as address-info embedded MAC or IPv4 addresses when available. Performs password guessing against Apple Filing Protocol afp-brute (AFP). Attempts to get useful information about files from AFP afp-ls volumes. The output is intended to resemble the output of ls. Detects the Mac OS X AFP directory traversal vulnerability, afp-path-vuln CVE-2010-0533. Shows AFP server information. This information includes the server's hostname, IPv4 and IPv6 addresses, and hardware type afp-serverinfo (for example Macmini or MacBookPro). Shows AFP shares and ACLs. afp-showmount Retrieves the authentication scheme and realm of an AJP service ajp-auth (Apache JServ Protocol) that requires authentication. Performs brute force passwords auditing against the Apache JServ protocol. The Apache JServ Protocol is commonly used by ajp-brute web servers to communicate with back-end Java application server containers. Performs a HEAD or GET request against either the root directory or any optional directory of an Apache JServ Protocol ajp-headers server and returns the server response headers. Discovers which options are supported by the AJP (Apache JServ Protocol) server by sending an OPTIONS request and lists ajp-methods potentially risky methods. ajp-request Requests a URI over the Apache JServ Protocol and displays the result (or stores it in a file).
  • 17 Basic Networking Clients

    17 Basic Networking Clients

    Certification Basic Networking Clients UNIT 17 Basic Networking Clients 1 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc. UNIT 16: Objectives ? Learn basic network commands ? Learn how to communicate securely with remote hosts ? Understand the use of rsync and wget 2 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc. UNIT 17: Agenda ? ssh / scp / telnet ? lftp ? links ? mutt ? rsync / wget ? ping / traceroute / host 3 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc. ssh: Secure Shell ? Public-key encryption technology replacement for various unsecure services ? Allows secure access to remote systems · $ ssh joe@barney -or- · $ ssh -l joe barney joe@barney's password: · $ ssh barney ls /tmp 4 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc. scp: Secure copy ? Secure replacement for rcp ? Layered on top of ssh · $ scp source destination ? Remote files can be specified using: · user@host:/path/to/file · -r option enables recursion · -p preserves times and permissions · -C compresses datastream 5 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc. telnet and the “r” services ? Insecure protocols ? telnet: Login names and passwords pass over the network in clear text ? “r” services (rsh, rlogin, rcp): generally insecure authentication mechanism ? telnet client can be used to connect to services running on arbitrary ports ? Example: testing your mail server: $ telnet localhost 25 6 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc. lftp ? Versatile command-line FTP client ? Anonymous or real-user sessions $ lftp ftp.cdrom.com $ lftp -u joe ftp.myserver.com ? Automated transfers with lftpget 7 Rev RH033-RHEL3-1 Copyright © 2003 Red Hat, Inc.
  • The Nmap Project

    The Nmap Project

    Insecure.Org The Nmap Project Fotis Hantzis aka ithilgore sock-raw.org FOSSCOMM 2016 Insecure.Org whoami • Exploiting TCP and the Persist Timer Infiniteness (Phrack #66) • Abusing Network Protocols (stealthy portscanning through XMPP exploitation) • Nmap developer, Ncrack author • Startup ventures @ithilgore Insecure.Org http://phrack.org/issues/51/11.html#article Insecure.Org Ndiff NSE Npcap Zenmap Insecure.Org Trinity uses Nmap in Matrix Reloaded Insecure.Org CIA using Zenmap in Bourne Ultimatum Insecure.Org Die Hard 4 Insecure.Org And many more: http://nmap.org/movies Elysium Insecure.Org > 1000 students $5.000 stipends 3 – 4 months ~ 150 open source organizations Insecure.Org Past Nmap GSoC Accomplishments o Nping – generic packet crafting tool o Ncat – the modern netcat o Npcap – packet sniffing library (WPF) o Ncrack – network auth cracking tool o NSE – Nmap Scripting Engine o Zenmap – GUI for Nmap o Ndiff – diff for network scans Insecure.Org http://nmap.org/ncrack High speed network authentication cracking tool Insecure.Org Ncrack’s Main Features o Intelligent Core Engine o Service Recognition through Nmap (-oN, -oX) o Fine-grained timing control (cl, CL, to, cd, at, T1-T5) o Built-in username/password lists o Session stop/resume o Modular architecture o Nsock based (asynchronous) Insecure.Org Ncrack modules o SSH – custom opensshlib based on OpenSSH o RDP – extremely hard protocol by MS SMB o • Telnet o SIP • FTP • HTTP (basic/digest) • PostgreSQL • MySQL Contributions • VNC • POP3 • Redis Insecure.Org New Ncrack 0.5 release
  • Automotive Ethernet: the Definitive Guide

    Automotive Ethernet: the Definitive Guide

    Automotive Ethernet: The Definitive Guide Charles M. Kozierok Colt Correa Robert B. Boatright Jeffrey Quesnelle Illustrated by Charles M. Kozierok, Betsy Timmer, Matt Holden, Colt Correa & Kyle Irving Cover by Betsy Timmer Designed by Matt Holden Automotive Ethernet: The Definitive Guide. Copyright © 2014 Intrepid Control Systems. All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and publisher. Printed in the USA. ISBN-10: 0-9905388-0-X ISBN-13: 978-0-9905388-0-6 For information on distribution or bulk sales, contact Intrepid Control Systems at (586) 731-7950. You can purchase the paperback or electronic version of this book at www.intrepidcs.com or on Amazon. We’d love to hear your feedback about this book—email us at [email protected]. Product and company names mentioned in this book may be the trademarks of their respective owners. Rather than use a trademark symbol with every occurence of a trademarked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The information in this book is distributed on an “As Is” basis, without warranty. While every precaution has been taken in the preparation of this book, neither the authors nor Intrepid Control Systems shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in this book.
  • Pragma Systems & Stay-Linked™: Remote SSH Connectivity Done Right

    Pragma Systems & Stay-Linked™: Remote SSH Connectivity Done Right

    WHITE PAPER Pragma Systems & Stay‐Linked™: Remote SSH Connectivity Done Right This paper is designed to serve as a primer for upgrading – or choosing and implementing – a highly effective, secure SSH connectivity solution. This document provides an overview of key regulatory and market developments driving the need to make remote computing systems more secure; takes a look at the origins of SSH and the factors that have led to its becoming the enterprise security protocol of choice; outlines key components of an optimal SSH‐based security approach; and, then, examines the market’s most trusted, effective, end‐to‐end, server and client SSH security solution, offered in partnership by Pragma Systems and Stay‐Linked. Pragma Systems & Stay‐Linked™: Remote SSH Connectivity Done Right Contents Executive Summary ............................................................................................................................................. 3 Takin’ it to the streets ......................................................................................................................................... 3 Clearly, it’s time to leave clear text behind ........................................................................................................ 4 Regulatory rundown ........................................................................................................................................... 4 Gaga for gadgets ................................................................................................................................................
  • Edition with Romkey, April 16, 1986 (PDF)

    Edition with Romkey, April 16, 1986 (PDF)

    PC/IP User's Guide MASSACHUSETTS INSTITUTE OF TECHNOLOGY Laboratory For Computer Science Network programs based on the DoD Internet Protocol for the mM Personal Computer PC/~ release or March, 1986; document updated Aprill4, 1986 by: Jerome H. Saltzer John L. Romkey .• Copyright 1984, 1985, 1986 by the Massachusetts Institute or Technology Permission to use, copy, modlt'y, and distribute these programs and their documentation ror any purpose and without ree ls hereby granted, provided that this copyright and permission notice appear on all copies and supporting documentation, the name or M.I.T. not be used in advertising or publlclty pertalnlng to dlstrlbutlon or the programs without written prior permission, and notice be glven in supporting documentation that copying and distribution ls by permlsslon or M.I.T. M.I.T. makes no representations about the suitablllty or this software for any purpose. It is provided "as ls" without express or Implied warranty. - ii - CREDITS The PC/IP packages are bullt on the work of many people in the TCP/IP community, both at M.I.T. and elsewhere. Following are some of the people who directly helped in the creation of the packages. Network environment-John L. Romkey Terminal emulator and customizer-David A. Bridgham Inltlal TFTP-Kari D. Wright Inltlal telnet-Louls J. Konopelskl Teinet model-David D. Clark Tasking package-Larry W. Allen Development system-Christopher J. Terman Development environment-Wayne C. Gramlich Administrative Assistant-Muriel Webber October 3, 1985. This document is in cover .mss - iii- - iv Table of Contents 1. Overview of PC/IP network programs 1 1.1.
  • List of TCP and UDP Port Numbers from Wikipedia, the Free Encyclopedia

    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.
  • Implementing TCP/IP

    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.
  • Network Time Protocol (Version 2) Specification and Implementation

    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.