The IANA houses the many unique parameters and protocol values necessary for
operation of the Internet and its future development. Types of numbers
range from unique port assignments to the registration of character sets.
In the past, these numbers were documented through the RFC document series,
the last of these documents was RFC
1700, which is also now
outdated. Since that time, the assignments have been listed in this
directory as living documents, constantly updated and revised when new information
is available and new assignments are made. Please check back periodically if
you need up-to-date information from these files. Thank you.
The documents are listed alphabetically and linked from their listings below. The documents are also available on the IANA ftp server.
ACAP's usefulness comes from providing a structured storage
model for all sorts of configuration data. However, for
its potential to be achieved, it is important that the Internet
community strives for the following goals:
(1) Standardization. It is very important to
standardize dataset classes. The authors hope that ACAP
achieves the success that SNMP has seen with the definition of
numerous standards track MIBs.
(2) Community Review. In the absence of standardization,
it is important to get community review on a proposal to improve
its engineering quality. Community review is strongly recommended
prior to registration. The ACAP implementors mailing list
<ietf-acap@andrew.cmu.edu> should be used for this purpose.
(3) Registration. Registration serves a two-fold
purpose. First it prevents use of the same name for different
purposes, and second it provides a one-stop list which can be
used to locate existing extensions or dataset classes to prevent
duplicate work.
The RFC "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures" [RFC2048] establishs a list of "Access Type" names. The IANA registry of these codes is listed here.
Several protocols deal with multiple address families. The 16-bit assignments are listed here.
Ad Hoc On Demand Distance Vector (AODV) Parameters
Applicable Exchange Core (APEX) Parameters
The Address Resolution Protocol (ARP) specified in [RFC826] has several parameters. The assigned values for these parameters are listed here.
Authentication Option Name Spaces
The Autonomous System (AS) numbers are used by various routing protocols. AS numbers are allocated to the regional registries by the IANA. These registries are ARIN <hostmaster@arin.net> for the Americas, Carribbean, and Africa, RIPE-NCC <ncc@ripe.net> for Europe, and the APNIC <helpdesk@apnic.net> for the Asia Pacific region. AS Numbers can be obtained from the registry in your region. Listed below are the allocated blocks to the regional registries.
Blocks Extensible Exchange Protocol (BEEP) Parameters
The Border Gateway Protocol (BGP) has Attribute Types as listed here.
Directory includes detailed extensions for BOOTP and DHCP parameters.
The Bootstrap Protocol (BOOTP) [RFC951] describes an IP/UDP bootstrap protocol (BOOTP) which allows a diskless client machine to discover its own IP address, the address of a server host, and the name of a file to be loaded into memory and executed. The Dynamic Host Configuration Protocol (DHCP) [RFC1531] provides a framework for automatic configuration of IP hosts. The "DHCP Options and BOOTP Vendor Information Extensions" [RFC1533] describes the additions to the Bootstrap Protocol (BOOTP) which can also be used as options with the Dynamic Host Configuration Protocol (DHCP).
Directory includes detailed applications of chracter sets that are not defined in RFCs.
Information about how to register a Character Set - RFC 2978
These are the official names for character sets that may be used in the Internet and may be referred to in Internet documentation.
Character Sets Mailing List Information
Common Name Resolution Protocol (CNRP) Parameters
Common Open Policy Service (COPS) Protocol Parameters
Context labels for Internet messages
Delivery Status Notification (DSN) Types
Directory includes detailed extensions for DHCP and BOOTP parameters
Differentiated Services Field CodepointsIn the representation of distinquished names (and possibly other contexts) of the X.500 Directory system, several unique keywords may be necessary. This file is the list of keywords.
DNS Header Flags and EDNS Header Flags
DNS KEY Resource Record Protocol Octet Values
Domain Name System (DNS) Parameters
The Internet Domain Naming System (DOMAIN) includes several parameters. These are documented in [RFC1034] and [RFC1035]. The CLASS parameter is listed here.
Domain Name System (DNS) Security Algorithm Numbers
SMI Network Management Private Enterprise Codes.
Many of the networks of all classes are Ethernets (10Mb) or Experimental Ethernets (3Mb). These systems use a message "type" field in much the same way the ARPANET uses the "link" field. The following list of EtherTypes is contributed unverified information from various sources.
In the FTP Operation Over Big Address Records (FOOBAR) Protocol [RFC1639] there is a field, called "address family" or "af", to identify the lower level protocol addresses in use. This is an 8 bit field. The first 16 assignments (0-15) of the af value are exactly the same as the IP Version number. The assignment for values 16-255 are listed here.
Generalized Multi-Protocol Label Switching (GMPLS) Parameters
Global Switch Management Protocol v3 (GSMPv3) Parameters
Global Switched Telephone Network (GSTN) Extensions
Information about registering GSTN Parameters
A service is a resource provided to network clients; often provided by more than one server and potentially by more than one protocol. Service names are short alphanumeric textual strings. Service names are used in the GSSAPI [RFC2078] host-service name form, are specified as part of a SASL profile [RFC2222] and are used by Kerberos service based tickets [RFC1510].
The Hypertext Transfer Protocol (HTTP) defines some classes of parameters [RFC2068].
A complete list of registered IANA ifTypes.
IANA MALLOC MIB
IANA Tn3270eTC MIB
The registered IANA Tn3270eTC MIB.
ICMP
Parameters
The Internet Control Message Protocol (ICMP) has many messages that are identified by a "type" field.
The Internet Control Message Protocol (ICMPv6) has many messages that are identified by a "type" field [RFC1885].
Some of the networks of all classes are IEEE 802 Networks. These systems may use a Link Service Access Point (LSAP) field in much the same way the MILNET uses the "link" field. Further, there is an extension of the LSAP header called the Sub Network Access Protocol (SNAP).
Namespaces for IP over IEEE 1394
IETF Protocol Parameter Identifiers
Capability names MUST either begin with "X" or be standard or standards-track IMAP4rev1 extensions, revisions, or amendments registered with IANA. A server MUST NOT offer unregistered or non-standard capability names, unless such names are prefixed with an "X".
Integrated Services Parameters
Internet Group Management Protocol (IGMP) TYPE NUMBERS
The files in this directory document the currently assigned values for several series of numbers used in network protocol implementations.
The Internet Protocol (IP) has provision for optional header fields identified by an option type field.
Internet Printing Protocol (IPP) Registrations
Internet/XNS Protocol Mappings
Here are two tables describing the arrangement of protocol fields or type field assignments so that one could send XNS Datagrams on the MILNET or Internet Datagrams on 10Mb Ethernet, and also protocol and type fields so one could encapsulate each kind of Datagram in the other.
Internet Key Exchange (IKE) Attributes
Internet Protocol v4 Address Space
The allocation of Internet Protocol version 4 (IPv4) address space to various registries is listed here.
Internet Protocol v6:
IPv6 Parameters (Parameters desribed for IPv6, including header types, action codes, etc.)
IPv6 Anycast Address Allocations
IPv6 Multicast Address Allocations
IPv6 Router Alert Option Values
IPv4 TOS Byte and IPv6 Traffic Class Octet
In the Internet Protocol (IP) [RFC791] there is a field to identify the version of the internetwork general protocol. This field is 4 bits in size.
Internet Open Trading Protocol (IOTP) Codes
IOTP codes consist of codes that are used by the Internet Open Trading Protocol (IOTP) [RFC2801]. IOTP provides an interoperable framework for Internet commerce. It is a payment system independent of and encapsulates payment systems such as SET, Secure Channel Credit/Debit, Mondex, CyberCoin, GeldKarte, etc. The codes covered include: Authentication Algorithms; Payment Brands; Currency Codes; Delivery Methods; Packaged Content Datatypes; Related Transaction Types; Status Types; Trading Roles; Transaction Types; and Component Types.
Internet Security Association and Key Management Protocol (ISAKMP) Identifiers
Label Distribution Protocol (LDP) Name Spaces
Directory of Language Tag Applications
Layer Two Tunneling Protocol "L2TP"
These are the Official Machine Names as they appear in the Domain Name System HINFO records and the NIC Host Table. Their use is described in [RFC952].
MAIL CONTENT DISPOSITION Values and Parameters
[RFC1505] specifies an initial list of keywords for the experimental encoding header field (EHF-MAIL), and provides that additional keywords may be registered with the IANA.
Please see RFC
2506 for details on these assignments.
Media Gateway Control Protocol (MGCP) Package Registry
Media Gateway Control Protocol (MGCP) LocalConnectionOptions Sub-registry
Message Disposition Notifications (MDN) Parameters
Document includes: milnet link numbers, link assignments, logical addresses, etc.
The document "IP Mobility Support" [RFC3344] specifies some message types and extensibility fields.
Multicast Address Dynamic Client Allocation Protocol (MADCAP) Parameters
The multicast addressess are in the range 224.0.0.0 through 239.255.255.255. Current addresses are listed here.
Multicast Address-Set Claim (MASC) Protocol Parameters
RFC 2909, "The Multicast Address-Set Claim (MASC) Protocol," establishes a list of several number spaces. The IANA registry of these parameters is listed here.
Multiprotocol Label Switching Architecture (MPLS) Label Values
NHRP Packet Types
Novell SAP Numbers
For the convenience of the Internet community the IANA maintains a list of Novell Service Advertising Protocol (SAP) numbers. This list is kept up to date by contributions from the community. Please send corrections and additions to IANA@IANA.ORG.
These are the Official System Names as they appear in the Domain Name System HINFO records and the NIC Host Table. Their use is described in [RFC952].
OSI Network Service Access Point Addresses include an Authority and Format Identifier (AFI). The AFI value 35 has been assigned to the IANA [IS 8348]. Within this format a two octet Internet Code Point (ICP) field is available for assignment by the IANA. All ICP values not listed below are reserved.
Open Shortest Path First (OSPF) Signature Algorithms
The Open Shortest Path First (OSPF) protocols has a provision for authentication, and the type of authentication can me indicated by a code number. The following are the registered authentication codes.
The port numbers are divided into three ranges: the Well Known Ports, the Registered Ports, and the Dynamic and/or Private Ports. This file contains the listing of all registered port numbers.
The System (Well-Known) Ports are those from 0 through 1023.
The User (Registered) Ports are those from 1024 through 49151.
The Dynamic and/or Private Ports are those from 49152 through 65535.
The Point to Point Protocol (PPP) Data Link Layer [146,147,175] contains a 16 bit Protocol field to identify the the encapsulated protocol. The Protocol field is consistent with the ISO 3309 (HDLC) extension mechanism for Address fields. All Protocols MUST be assigned such that the least significant bit of the most significant octet equals "0", and the least significant bit of the least significant octet equals "1".
This file contains a listing of Printer MIB Interpreters Language Families.
This is the current list of PRONET 80 Type Numbers. Note: a protocol that is on this list does not necessarily mean that there is any implementation of it on ProNET.
In the Internet Protocol (IP) [DDN], [RFC791] there is a field, called Protocol, to identify the next level protocol. This is an 8 bit field.
These are the Official Protocol Names as they appear in the Domain Name System WKS records and the NIC Host Table. Their use is described in [RFC952].
One of the Internet Class A Networks is the international system of Public Data Networks. This section lists the mapping between the Internet Addresses and the Public Data Network Addresses (X.121).
The RFC "A Format for E-Mailing Bibliographic Records" [RFC1357] establishes a "publisher-ID" code. The IANA registry of these codes is listed here.
Realm Specific IP (RSIP) Parameters
Radius Types
The RFC "Remote Authentication Dial In User Service (RADIUS)" [RFC2058] defines a type code. The IANA registry of these codes is listed here.
Reliable Mutlicast Transport (RMT) FEC Encoding IDs and FEC Instance IDs
Routing Information Protocol (RIP) Types
The Routing Information Protocol (RIP) has message types. These are listed here.
RObust Header Compression (ROHC) Profile Identifiers
RFC 2207 describes a set of virtual destination ports for use with IPSEC.
RTP Payload Types: The RFC "RTP Profile for Audio and Video Conferences with Minimal Control" [RFC1890] specifies an initial set "payload types". This list mantains and extends that list.
RTP RTCP Control Packet Types: The RFC "RTP: A Transport Protocol for Real-Time Applications" [RFC1889] specifies an initial set of "control packet types" for RTCP. This list mantains and extends that list.
RTP SDES item types: The RFC "RTP: A Transport Protocol for Real-Time Applications" [RFC1889] specifies an initial set of "item types" for the RTCP SDES control packet. This list mantains and extends that list.
List of obsolete codes.
SMI Numbers (Network Management Parameters)
For the management of hosts and gateways on the Internet a data structure for the information has been defined. This data structure should be used with any of several possible management protocols, such as the "Simple Network Management Protocol" (SNMP) [RFC1157], or the "Common Management Information Protocol over TCP" (CMOT) [RFC1095].
The Simple Authentication and Security Layer (SASL) [RFC2222] is a method for adding authentication support to connection based protocols. To use this specification, a protocol includes a command for identifying and authenticating a user to a server and for optionally negotiating a security layer for subsequent protocol interactions. The command has a required argument identifying a SASL mechanism.
Server Cache Synchronization Protocol (SCSP)
The SOCKS Method is a 8-bit number used to identify the authentication method used with the SOCKS protocol [RFC1929]. These 256 values are assigned by the IANA and listed here.
The Security Parameters Index is a 32-bit number used to identify the security association of a datagram in certain security procedures [RFC1826, RFC1827]. The first 256 SPI values are assigned by the IANA and listed here.
Session Description Protocol (SDP) Parameters
Session Initiation Protocol (SIP) Parameters
For information about the SIP Parameters please see RFC 3261.
Session Initiation Protocol (SIP) Event Types Namespace
Precondition Types used with Session Initiation Protocol (SIP)
Session Initiation Protocol (SIP) Privacy header values
Registry for the Session Initiation Protocol (SIP) SRV Resource Record Service Field
Signaling User Adaptation Layer Assignments
Simple Mail Transfer Protocol (SMTP) Service Extensions
Special People Numbers Registry (SPNR)
SNMP Number SpacesStream Control Transmission Protocol (SCTP)
RFC 2960, "Stream Control Transmission Protocol (SCTP)," defines extensible lists for SCTP Chunk Types, Chunk Parameter Types, Error Causes, and Payload Protocol Identifiers. The IANA registry of these parameters is listed here.
Structured Data Exchange Format (SDXF) Parameters
Subsequence Address Family Identifier (SAFI)
RFC 2858, "Multiprotocol Extensions for BGP-4," defines attributes that contain the Subsequence Address Family Identifier (SAFI) field. The SAFI name space values are listed here.
Specification and description of Remote Procedure Call (RPC) numbers.
Service Location Protocol, Version 2 (SLPv2) Extensions
Service Location Protocol, Version 2 (SLPv2) Function IDs
The service templates in this directory conforms to RFC 2609.
Telephony Routing over IP (TRIP) Parameters
The Transmission Control Protocol (TCP) has provision for optional header fields identified by an option kind field. Options 0 and 1 are exactly one octet which is their kind field. All other options have their one octet kind field, followed by a one octet length field, followed by length-2 octets of option data.
The Telnet Protocol has a number of options that may be negotiated. These options are listed here. "Internet Official Protocol Standards" (STD 1) provides more detailed information.
These are the Official Terminal Type Names. Their use is described in [RFC930]. The maximum length of a name is 40 characters.
The RFC "Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures" [RFC2048] establishs a list of "Transfer Encoding" names. The IANA registry of these codes is listed here.
Uniform Resource Identifier (URI) Schemes
Uniform Resource Names (URN) Namespaces
Information about how to register a URN Namespace - RFC 3406
Uniform Resource Names (URN) - Informal namespace registration data
VCDIFF Secondary Compressor ID Values
Version NumbersIn the Internet Protocol (IP) [RFC791] there is a field to identify the version of the internetwork general protocol. This field is 4 bits in size.
'version' symbols used within the ISUP and QSIG
Internet applications may reference specific codecs within the WAVE and AVI registries as follows:
* video/vnd.avi; codec=XXX identifies a specific video codec (i.e., XXX) within the AVI Registry.
* audio/vnd.wave; codec=YYY identifies a specific audio codec (i.e., YYY) within the WAVE Registry.
CCITT defines the high order two bits of the first octet of call user data as follows: