Number Resources
We are responsible for global coordination of the Internet Protocol addressing systems, as well as the Autonomous System Numbers used for routing Internet traffic.
Currently there are two types of Internet Protocol (IP) addresses in active use: IP version 4 (IPv4) and IP version 6 (IPv6). IPv4 was initially deployed on 1 January 1983 and is still the most commonly used version. IPv4 addresses are 32-bit numbers often expressed as 4 octets in “dotted decimal” notation (for example, 192.0.2.53 ). Deployment of the IPv6 protocol began in 1999. IPv6 addresses are 128-bit numbers and are conventionally expressed using hexadecimal strings (for example, 2001:0db8:582:ae33::29 ).
Both IPv4 and IPv6 addresses are generally assigned in a hierarchical manner. Users are assigned IP addresses by Internet service providers (ISPs). ISPs obtain allocations of IP addresses from a local Internet registry (LIR) or National Internet Registry (NIR), or from their appropriate Regional Internet Registry (RIR):
Our primary role for IP addresses is to allocate pools of unallocated addresses to the RIRs according to their needs as described by global policy and to document protocol assignments made by the IETF . When an RIR requires more IP addresses for allocation or assignment within its region, we make an additional allocation to the RIR. We do not make allocations directly to ISPs or end users except in specific circumstances, such as allocations of multicast addresses or other protocol specific needs.
IP Address Allocations
Internet protocol version 4 (ipv4).
- IPv4 Address Space
- IPv4 Multicast Address Assignments
- IPv4 Special Purpose Address Registry
- IPv4 Recovered Address Space Registry
- Bootstrap Service Registry for IPv4 Address Space
Internet Protocol Version 6 (IPv6)
- IPv6 Address Space
- IPv6 Global Unicast Allocations
- IPv6 Parameters (Parameters described for IPv6, including header types, action codes, etc.)
- IPv6 Anycast Address Allocations
- IPv6 Multicast Address Allocations
- IPv6 Sub-TLA Assignments (DEPRECATED)
- IANA IPv6 Special Registry
- Bootstrap Service Registry for IPv6 Address Space
- Announcement of Worldwide Deployment of IPv6 (14 July 1999)
- RIR Comparative Policy Overview
Autonomous System Number Allocations
- Autonomous System Numbers
- Special-Purpose AS Number Assignments
- Bootstrap Service Registry for AS Number Space
- Internet Number Resource Request Procedure
Regional Internet Registry Creation
- Criteria for Establishment of New Regional Internet Registries (ICP-2) (4 June 2001)
- IANA Report on Recognition of LACNIC as a Regional Internet Registry (7 November 2002)
- IANA Report on Recognition of AfriNIC as a Regional Internet Registry (8 April 2005)
Technical Documentation
- RFC 4632 — Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan
- RFC 1918 — Address Allocation for Private Internets
- RFC 5737 — IPv4 Address Blocks Reserved for Documentation
- RFC 4291 — Internet Protocol Version 6 (IPv6) Addressing Architecture
- RFC 3587 — IPv6 Global Unicast Address Format
- RFC 6177 — IPv6 Address Assignment to End Sites
- RFC 6890 — Special-Purpose IP Address Registries
- RFC 7020 — The Internet Numbers Registry System
- RFC 7249 — Internet Numbers Registries
- Locally Served DNS Zones
IMAGES
COMMENTS
Note. Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first-come, first-served process, as documented in [ RFC6335 ]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User ...
RFC 7605 Recommendations for Transport Port Use August 2015 or passive-mode FTP (in which both connections are opened from the client side). 7. Considerations for Requesting Port Number Assignments Port numbers are assigned by IANA by a set of documented procedures [ RFC6335 ].
This RFC will be updated periodically, and in any case current information can be obtained from the Internet Assigned Numbers Authority (IANA). If you are developing a protocol or application that will require the use of a link, socket, port, protocol, etc., please contact the IANA to receive a number assignment.
This includes review under the "Expert Review" procedure documented in RFC 8126. User port numbers range between 1024 and 49151. If you wish to register a system port — those numbered 1023 or less — it must be done through the standardisation process of the IETF. ... Assignment of a port number does not in any way imply an endorsement of an ...
RFC 1010 - Assigned Numbers May 1987 Port Numbers PORT NUMBERS Ports are used in the TCP [36,81] to name the ends of logical connections which carry long term conversations.For the purpose of providing services to unknown callers, a service contact port is defined. This list specifies the port used by the server process as its contact port.
IANA MAY accept early assignment [RFC4020] requests (known as "early allocation" therein) from IETF working groups that reference a sufficiently stable Internet-Draft instead of a published Standards-Track RFC. o Port Number: If assignment of a port number is desired, either the port number the requester suggests for assignment or indication of ...
RFC 6335 Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry, August 2011. File formats: Status: BEST CURRENT PRACTICE Updates: RFC 2780, RFC 2782, RFC 3828, RFC 4340, RFC 4960, RFC 5595 Authors: M. Cotton
This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the ...
Note. Service names and port numbers are used to distinguish between different services that run over transport protocols such as TCP, UDP, DCCP, and SCTP. Service names are assigned on a first-come, first-served process, as documented in [ RFC6335 ]. Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User ...
This form is used to modify an existing user port number assignment in the IANA Service Name and Transport Protocol Port Number Registry. This is not an application for a new service name or port number assignment. ... For further information, see RFC 6335 and RFC 7605. Assignee. List the organization, company or individual person responsible ...
Ports 0-1023 are the Well Known Ports and are assigned by IANA. These should only be used for the assigned protocols on public networks. Ports 1024-65535 used to be called Registered Port Numbers (see rfc1700) but are now split into two areas (see rfc6335).. Ports 1024-49151 are the User Ports and are the ones to use for your own protocols.
Currently there are two types of Internet Protocol (IP) addresses in active use: IP version 4 (IPv4) and IP version 6 (IPv6). IPv4 was initially deployed on 1 January 1983 and is still the most commonly used version. IPv4 addresses are 32-bit numbers often expressed as 4 octets in "dotted decimal" notation (for example, 192.0.2.53 ).
The original requesters of a granted port number assignment can return the port number to IANA at any time if there no longer is a need for it. The port number will be de-registered and will be marked as unassigned. ... Stewart, R., "Stream Control Transmission Protocol," RFC 4960, September 2007 . Internet Assigned Numbers Authority (IANA ...
RFC 1700 Assigned Numbers October 1994 36 XTP XTP ... The service doesn't care what port it gets, remote clients will query the portmapper to ask it what port number was assigned to the service when it was started. The key is that the port was not currently in use. The only port that ONC/RPC must have is 111 its assigned port for the portmap ...
Range Operating system 49152-65535: suggested by RFC 6335 and the Internet Assigned Numbers Authority (IANA) (2 15 + 2 14 to 2 16 − 1 or C000 hex … FFFF hex) for dynamic or private ports. FreeBSD has used the IANA port range since release 4.6. Windows Vista, Windows 7, and Server 2008 use the IANA range by default.: 32768-60999: used by many Linux kernels.: 32768-65535
Well-Known Port Assignments for the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP) (RFC 8545, March 2019) ... [RFC5357] describes the detailed process of negotiating the Receiver Port number, on which the TWAMP Session-Reflector will send and receive TWAMP-Test packets; see the quoted text below ...
Assigned Numbers RFC 870 Network Numbers One commonly used notation for internet host addresses divides the 32-bit address into four 8-bit fields and specifies the value of each field as a decimal number with the fields separated by periods. This is called the "dotted decimal" notation. For example, the internet address of ISIF in dotted decimal is 010.002.000.052, or 10.2.0
This RFC will be updated periodically, and in any case current information can be obtained from Jon Postel. The assignment of numbers is also handled by Jon. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, or network number please contact Jon to receive a number assignment.
RFC 6056 Port Randomization Recommendations January 2011 issuing a socket () call). Secondly, the application binds the file descriptor to a local TCP port number (e.g., by issuing a bind () call), thus creating a TCP in the fictional CLOSED state. Thirdly, the aforementioned TCP is put in the LISTEN state (e.g., by issuing a listen () call).
dynamic port numbers (private port numbers): The dynamic port numbers (also known as the private port numbers ) are the port number s that are available for use by any application to use in communicating with any other application, using the Internet's Transmission Control Protocol ( TCP ) or the User Datagram Protocol ( UDP ). When one ...
RFC 7194 Default Port for IRC via TLS/SSL August 2014 This document does not address server links as there are no commonly accepted ports or even back-end protocols. Ports and back-end protocols are normally established in a bilateral agreement. All operators are encouraged to use strong encryption for back-end traffic, no matter if they offer IRC via TLS/SSL to end users.
RFC 7605 Recommendations for Transport Port Use August 2015 or passive-mode FTP (in which both connections are opened from the client side). 7. Considerations for Requesting Port Number Assignments Port numbers are assigned by IANA by a set of documented procedures [ RFC6335 ].
This RFC will be updated periodically, and in any case current information can be obtained from the Internet Assigned Numbers Authority (IANA). If you are developing a protocol or application that will require the use of a link, socket, port, protocol, etc., please contact the IANA to receive a number assignment.