 IANA Allocation Guidelines for TCP and UDP Port Numbers draft-cotton-tsvwg-iana-ports-00Status of this memo. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress.” The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt . The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html . This Internet-Draft will expire on August 21, 2008. This document defines the IANA guidelines for registering new port number values for use with the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). It provides clear processes for the TCP and UDP port number registries, important for their long-term management. It updates RFC2780 by replacing Sections 8 and 9.1 of that RFC. Table of Contents1. Introduction 2. Terminology 3. Stewardship Principles for the Port Number Space 4. Allocation Procedures for the Port Number Space 4.1. Common Procedures 4.2. Well Known (System) Ports 4.3. Registered (User) Ports 4.4. Dynamic (Private) Ports 5. Supplemental Procedures for the Port Number Space 5.1. Port Number De-Registration 5.2. Port Number Re-Use 5.3. Port Number Revocation 6. Security Considerations 7. IANA Considerations 8. Acknowledgments 9. References 9.1. Normative References 9.2. Informative References Appendix A. Open Issues § Authors' Addresses § Intellectual Property and Copyright Statements 1. IntroductionThe Transmission Control Protocol (TCP) [RFC0793] ( Postel, J., “Transmission Control Protocol,” September 1981. ) and the User Datagram Protocol (UDP) [RFC0768] ( Postel, J., “User Datagram Protocol,” August 1980. ) have enjoyed a remarkable success over the decades as the two most widely used transport protocols on the Internet. They have introduced the concept of ports as logical entities that end system applications bind their transport sessions to. Ports are identified by 16-bit numbers, and the combination of source and destination port numbers together with the IP addresses communicating end systems uniquely identifies a session of a given transport protocol. Newer transport protocols, such as the Stream Control Transmission Protocol (SCTP) [RFC4960] ( Stewart, R., “Stream Control Transmission Protocol,” September 2007. ) and the Datagram Congestion Control Protocol (DCCP) [RFC4342] ( Floyd, S., Kohler, E., and J. Padhye, “Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC),” March 2006. ) have adopted the concept of ports for their communication sessions and use port numbers in the same way as TCP and UDP. Port numbers are the original and most widely used means for application and service identification on the Internet. Designers of applications and application-level protocols may apply to the Internet Assigned Numbers Authority (IANA) for a registered port number for a specific application, and may after successful registration assume that no other application will use that port number for its communication sessions. It is important to note that ownership of registered port numbers remains with IANA. For many years, the allocation and registration of new port number values for use with TCP and UDP have had less than clear guidelines. Information about the registration procedures for the port namespace existed in three locations: the forms for requesting port number registrations on the IANA web site [SYSFORM] ( Internet Assigned Numbers Authority (IANA), “Application for System (Well Known) Port Number,” . ) [USRFORM] ( Internet Assigned Numbers Authority (IANA), “Application for User (Registered) Port Number,” . ) , an introductory text section in the file listing the port number registrations themselves [REGISTRY] ( Internet Assigned Numbers Authority (IANA), “Port Numbers,” . ) , and two brief sections of [RFC2780] ( Bradner, S. and V. Paxson, “IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers,” March 2000. ) . This document aggregates this scattered information into a single reference and at the same time clarifies the guidelines for the management of the TCP and UDP port number space. It gives more detailed guidance to prospective requesters of TCP and UDP ports than the existing documentation, and it streamlines the IANA procedures for the management of the port number space, so that management requests can complete in a timely manner. A key factor of this streamlining is to establish identical registration procedures for transport protocol ports, independent of a specific transport protocol. This document brings the IANA procedures for TCP and UDP in line with those already in effect for SCTP and DCCP, resulting in a single process that requesters and IANA follow for all port number requests for all transport protocols. A second purpose of this document is to describe the principles that guide the IETF and IANA in their role as the long-term joint stewards of the port number space. TCP and UDP have been a remarkable success over the last decades. Thousands of applications and application-level protocols have registered ports for their use, and there is every reason to believe that this trend will continue into the future. It is hence extremely important that management of the port number space follow principles that ensure its long-term usefulness as a shared resource. Section 3 ( Stewardship Principles for the Port Number Space ) discusses these principles in detail. TCP and UDP use 16-bit namespaces for their port number registries, as do SCTP and DCCP. These ports registries are subdivided into three port number ranges, and Section 4 ( Allocation Procedures for the Port Number Space ) describes the IANA procedures for each range in detail:
When this document was being written, approximately 76% of the Well Known Ports for TCP and UDP were assigned, as was a significant fraction of the Registered Ports. (Dynamic Ports are not available for assignment through IANA.) In addition to detailing the IANA procedures for the initial assignment of port numbers, this document also specifies supplemental procedures that until now have been handled in an ad hoc manner. These include procedures to de-register a port number that is no longer in use, to re-use a port number allocated for one application that is no longer in use for another application, and procedure by which IANA can unilaterally revoke a prior port number registration. Section 5 ( Supplemental Procedures for the Port Number Space ) discusses the specifics of these procedures. Finally, this document also addresses two technical issues with ports registry that are tangential to long-term stewardship. First, it clarifies that a method for the early allocation of TCP and UDP ports for IETF working group documents is available, in line with [RFC4020] ( Kompella, K. and A. Zinin, “Early IANA Allocation of Standards Track Code Points,” February 2005. ) . Second, it discusses how the use of the symbolic names for assigned ports (the "keyword" field in [REGISTRY] ( Internet Assigned Numbers Authority (IANA), “Port Numbers,” . ) ) for Service Resource Records (SRV RRs) in the Domain Name System (DNS) [RFC2782] ( Gulbrandsen, A., Vixie, P., and L. Esibov, “A DNS RR for specifying the location of services (DNS SRV),” February 2000. ) relates to the use of SRV RRs for applications without an assigned port. This document updates [RFC2780] ( Bradner, S. and V. Paxson, “IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers,” March 2000. ) by replacing Sections 8 and 9.1 of that RFC. Note that [I‑D.arkko‑rfc2780‑proto‑update] ( Arkko, J. and S. Bradner, “IANA Allocation Guidelines for the Protocol Field,” January 2008. ) updates a different subset of the IANA allocation guidelines originally given in [RFC2780] ( Bradner, S. and V. Paxson, “IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers,” March 2000. ) (specifically, the policies on the namespace of the IP protocol number and IPv6 next header). 2. TerminologyThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14, RFC 2119 [RFC2119] ( Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997. ) . 3. Stewardship Principles for the Port Number SpaceThe overriding principle that governs the IANA and IETF procedures governing the management of the port number registry for the different transport protocols is conservation. The port number registry is one of the basic resources of the Internet and requires careful management. Exhaustion is likely to require fundamental changes to Internet communication, which is undesirable. At the same time, it is of great benefit to all Internet applications to request and receive port number allocations from IANA for their communication needs. This means that although IANA should require and verify that applicants for port numbers document their intended use to a degree that lets a technical expert review the desired allocation, this process must not appear to be an insurmountable burden. Otherwise, there is the danger that application designers turn to using ports in an undocumented fashion, which is harmful to Internet communications as a whole. Clearly stated and motivated procedures support this goal. It is important to note that different IANA procedures apply to different ranges of the port number registry. Section 4 ( Allocation Procedures for the Port Number Space ) discusses the details of these procedures; this section outlines the rationale for these differences:
Several other practices stem from the conservation principle that guides management of the port numbers registry. First, with the approval of this document, IANA will begin assigning protocol numbers only for those transport protocols explicitly included in the registration request. This ends the long-standing practice of automatically assigning a port number to an application for both TCP and a UDP, even if the request is only for one of these transport protocols. The new allocation procedure conserves resources by only allocating a port number to an application for those transport protocols (TCP, UDP, SCTP and/or DCCP) it actually uses. The port number will be marked as reserved - instead of assigned - in the port number registries of the other transport protocols. When applications start supporting the use of some of those additional transport protocols, they must request IANA to convert the reservation to an assignment. An application must not assume that it can use a port number assigned to it for use with one transport protocol with another transport protocol without a registration with IANA. Second, IANA will continue its long-standing practice of refusing allocations for applications that request the assignments of multiple port numbers. Registered port numbers are application identifiers, and extremely few applications require multiple identifiers. For applications that do require a registered port number in the first place, the vast majority of them can operate without restrictions using a single registered port number. Such applications can often simply use several ports taken on-demand from the Dynamic Ports range, or they can use a demultiplexing field that is part of their packet payload. Third, conservation for the port numbers registry is improved by procedures that allow previously allocated port numbers to become unassigned, either through de-registration or revocation, and by a procedure that lets application designers transfer an unused port number to a new application. Section 5 ( Supplemental Procedures for the Port Number Space ) describes these procedures, which so far were undocumented. 4. Allocation Procedures for the Port Number Space4.1. common procedures. All registration requests for a TCP and/or UDP ports must contain the following pieces of information: Registration Contact: Name and email address of the contact for the registration. This is mandatory. Additional address information may be provided. For registrations done through IETF-published RFCs, one or more technical contact persons shall be provided. In addition, in this case the registration ownership will belong to the IETF and not the technical contact persons. Transport Protocol: Which transport protocol(s) is the registration request for, TCP, UDP or both? Broadcast or Multicast: If multicast or broadcast is used with the registered port, a description of this usage is required. Port Name: The long name (description) of the port. It should avoid all but the most well known acronyms. Service Name: This short name for the port number is used in the service name registry for DNS SRV RRs and has a 14-character maximum length. It must not conflict with already-allocated names in the service name registry [TBD]. Note that a particular application or service should be able to operate using only one well known or registered port. For applications or services that offer multiple functions, it is usually possible to use one port number for a multiplexing or rendezvous service. That is, the client always initiates the use of a service by contacting the rendezvous port number with a message that indicates which function is needed. The rendezvous service then either (A) creates (forks, spawns) a process to perform that function and passes the connection to it; or (B) dynamically selects a (high-numbered) port and starts a process to listen on that port number and then sends a message back to the client telling it to contact the new process on that port number. When a registration for only TCP or UDP is approved, the port number for the other transport protocol will remain unassigned but is marked as reserved. However, IANA SHOULD NOT assign that port number to any other application or service until no port numbers exist in the request range that are u for both protocols. The current registration owner of a port number MAY register the same port number for other transport protocols when needed. 4.2. Well Known (System) PortsThe Well Known Ports are assigned by IANA and cover the range 0-1023. On many systems, they can only be used by system (or root) processes or by programs executed by privileged users. Registration requests for a Well Known port number MUST follow the "IETF Review" policy of [I‑D.narten‑iana‑considerations‑rfc2434bis] ( Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” March 2008. ) . Registrations for a port number in this range MUST document why a port number in the Registered Ports range will not fulfill the application needs. Registrations requesting more than a single port number for a single application in this space SHOULD be denied. Because of the special nature of port numbers in the Well Known range on several platforms, [RFC4727] ( Fenner, B., “Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers,” November 2006. ) has registered two port numbers in this range (1021 and 1022) for temporary, experimental use. Use of these two port numbers must comply to the guidelines set out in [RFC3692] ( Narten, T., “Assigning Experimental and Testing Numbers Considered Useful,” January 2004. ) , most importantly, they are not intended to be used in general deployments or be enabled by default in products or other general releases. The other restrictions as defined in [RFC3692] ( Narten, T., “Assigning Experimental and Testing Numbers Considered Useful,” January 2004. ) apply as well. 4.3. Registered (User) PortsThe Registered Ports are assigned by IANA and on most systems can be used by ordinary user processes or programs executed by ordinary users. The Registered Ports are in the range 1024-49151. This port number range is the main range for any application or service requiring a known and stable port number across all hosts. Before requesting a registration, requesters should carefully consider if a rendezvous mechanism, such as DNS SRV RRs, together with the use of port numbers in the Dynamic Ports range can satisfy the application requirements. It is expected that primarily rendezvous or look-up services or applications and services that must operate in environments where such services are unavailable will need to use registered ports. Registration requests for a Registered Port number MUST follow the "Expert Review" policy of [I‑D.narten‑iana‑considerations‑rfc2434bis] ( Narten, T. and H. Alvestrand, “Guidelines for Writing an IANA Considerations Section in RFCs,” March 2008. ) . Registration requests for more than a single port number for a single application are NOT RECOMMENDED and MUST come with an extremely strong justification when brought forward. 4.4. Dynamic (Private) PortsThe Dynamic Ports range from 49152-65535. These ports cannot be registered through IANA or by any other means. IANA SHALL refuse all such registration requests. Private ports are usable by any application in a dynamic fashion. Usage of private ports for server type applications or services are possible through the use of rendezvous or location look-up mechanisms, e.g., the DNS. Applications acquire a particular dynamic port number on an end system and register the port number of the contact port for that service with a rendezvous or look-up service. It is RECOMMENDED that application that are capable of using such mechanisms utilize them, in order to minimize consumption of the finite port number space. 5. Supplemental Procedures for the Port Number Space5.1. port number de-registration. 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. IANA will not assign port numbers that have been de-registered until all other available port numbers in the specific range have been assigned. Before proceeding with a de-registration, IANA needs to confirm that the port number is actually no longer in use. 5.2. Port Number Re-UseIf the original requesters of a granted port number assignment no longer have a need for the registered number, but would like to re-use it for a different application, they can submit a request to IANA to do so. Logically, port number re-use is to be thought of as a de-registration followed by an immediate re-registration of the same port number for a new application. Consequently, the information that needs to be provided about the proposed new use of the port number is identical to what would need to be provided for a new port number allocation for the specific ports range. IANA needs to carefully review such requests before approving them. In some instances, the Expert Reviewer will determine that the application that the port number was assigned to has found usage beyond the original requester, or that there is a concern that it may have such users. This determination MUST be made quickly. A community call concerning revocation of a port number (see below) MAY be considered, if a broader use of the port number is suspected. 5.3. Port Number RevocationOften, it will be clear that a specific port number is no longer in use and that IANA can de-register it and mark it as unassigned. But at other times, it may be unclear whether a given assigned port number is still in use somewhere in the Internet. In those cases, despite the requester's wish to de-register, IANA must consider the consequences that de-registering the port number. With the help of their IESG-appointed Expert Reviewer, IANA SHALL formulate a request to the IESG to issue a four-week community call concerning the pending port number revocation. The IESG and IANA, with the Expert Reviewer's support, SHALL determine promptly after the end of the community call whether de-registration should proceed and then communicate their decision to the community 6. Security ConsiderationsThe IANA guidelines described in this document do not change the security properties of either TCP or UDP. Assignment of a port number does not in any way imply an endorsement of an application or product, and the fact that network traffic is flowing to or from a registered port number does not mean that it is "good" traffic. Firewall and system administrators should choose how to configure their systems based on their knowledge of the traffic in question, not whether there is a port number registered or not. 7. IANA ConsiderationsThis document obsoletes Sections 8 and 9.1 of [RFC2780] ( Bradner, S. and V. Paxson, “IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers,” March 2000. ) . Upon approval of this document, IANA is requested to adopt the procedures described herein. Values in the UDP Source and Destination Field may be assigned Values in the TCP Source and Destination Field may be assigned Upon approval of this document or sooner, the IESG SHALL appoint a TCP/UDP Ports Expert Reviewer to work with IANA in support of the port registry and to uphold the principles described in this document. The Expert Reviewer will provide rapid advice to IANA as to whether to grant a port number assignment, including whether requests for more than one transport are merited. IANA MAY ask the TCP/UDP Expert Reviewer to co-review an SCTP or DCCP request if it also asks for a TCP or UDP port. The Expert Reviewer SHALL support IANA in the analysis for determining when a request to re-purpose a port number or de-assign it requires a community call on port number revocation. 8. AcknowledgmentsLars Eggert is partly funded by [TRILOGY] ( , “Trilogy Project,” . ) , a research project supported by the European Commission under its Seventh Framework Program. 9. References9.1. normative references.
9.2. Informative References
Appendix A. Open IssuesThis document is an initial version submitted for discussion at IETF-71 in Philadelphia, PA, USA. Expect nearly all sections of this document to see significant revisions in the near future. Nothing in here is final. Authors' Addresses
Full Copyright StatementCopyright © The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual PropertyThe IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr . The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at [email protected] . We’re fighting to restore access to 500,000+ books in court this week. Join us! Internet Archive Audio
Search the history of over 866 billion web pages on the Internet. Mobile Apps
Browser ExtensionsArchive-it subscription.
Save Page NowCapture a web page as it appears now for use as a trusted citation in the future. Please enter a valid web address
Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number RegistryBookreader item preview, share or embed this item, flag this item for.
plus-circle Add Review comment ReviewsDownload options, in collections. Uploaded by GoodieHicks on January 24, 2023 SIMILAR ITEMS (based on metadata)
Collectives™ on Stack OverflowFind centralized, trusted content and collaborate around the technologies you use most. Q&A for work Connect and share knowledge within a single location that is structured and easy to search. Get early access and see previews of new features. Assigning TCP/IP Ports for In-House Application UseI've written a WCF Service hosted by a Windows Service and it needs to listen on a known TCP/IP port. From what range can I safely allocate a port for use within my organization? That port will be embedded in the config files for the service and the clients that are consuming the service. 
6 Answers 6Ports 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. Ports 49152-65535 are the Dynamic ports and should not be prescribed to a protocol. The User Ports can be used for any protocol, but there are a finite number, so your use will clash with someone elses use on some network somewhere. IANA keep a record of registered port numbers (0-49151). If your protocol will be used on public networks then you need to look into registering it with IANA. If you are only using it within your own network then pick a port within this area (1024-49151) and check that port against the IANA register to make sure it isn't used by a protocol that could be used on your network. For private use it is probably better to pick a number that is assigned to a protocol you know won't be used than to choose one that is unassigned and so may be assigned in the future. Don't use a port number within the Dynamic range. These ports are assigned by the operating system, dynamically and somewhat randomly. If you open a client connection (using bind() with port=0) you will be assigned an unused port from the dynamic range. There is no way to guarantee that a port in this range will always be free for your protocol. 
Pick a port number from 49152 through 65535. IANA publishes a list of currently assigned ports. http://www.iana.org/assignments/port-numbers The Dynamic and/or Private Ports are those from 49152 through 65535. This is the range from where you SHOULD pick a port for your in-house applications. Of course any port belonging to one of the unassigned ranges on the published list can be used. But be aware that by picking a port number from those unassigned ranges there is no guarantee whatsoever that the port you choose will not be a reserved port in the future. UNASSIGNED PORT NUMBERS SHOULD NOT BE USED. THE IANA WILL ASSIGN THE NUMBER FOR THE PORT AFTER YOUR APPLICATION HAS BEEN APPROVED. And make sure that the port number you pick is configurable as you stated: That port will be embedded in the config files for the service and the clients that are consuming the service. This will avoid headaches in case some other 3rd party you-cannot-touch software is using your port number. If that happens you just go ahead and change it on the configuration file and it just works. 
Short answer: Avoid anything up to and including 1023, or over 49152, and test the chosen port against services on your network. If you've taken the reasonable precautions that it appears you have (putting the port number in a config file), it shouldn't be an enormous disruption if you later discover a conflict. But (so that I can add something to the other suggestions that have popped up while I've been typing) make sure that you make it easy to change! If it's in config files, make it obvious. Document it, and point it out in troubleshooting. It's the sort of thing that could go wrong, so make it easy to debug if it needs changing. 
In addition to the other suggestions about picking a common application port, I'd suggest that you make the port configurable within your application. Hard-coded port numbers are a bad idea, particularly if you later find a port conflict with another application and need to change yours.  As a note remember to check those port by netstat /a /n to see if its using by other application or not. I find out vista used the 49152 .... for some application level reason. Basically, because most of the system level listener does not implement port sharing its much safe to use the those ports which are not used at all.  Here is a good list of common application ports . Make your own choice in an empty slot. Maybe you should also scan your network for any in-house special application. Typically high numbers port are available and I would suggest them but they could be blocked by firewalls. 
Your AnswerReminder: Answers generated by artificial intelligence tools are not allowed on Stack Overflow. Learn more Sign up or log inPost as a guest. Required, but never shown By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy . Not the answer you're looking for? Browse other questions tagged tcp or ask your own question .
Hot Network Questions
Stack Exchange NetworkStack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers. Q&A for work Connect and share knowledge within a single location that is structured and easy to search. Where is the documentation that states TCP and UDP source port should be over 1024 and random?I am having a hard time to find where it is documented that the source port should be random and in the range 1024-65535. In which RFC is this documented? Edit: First reference for privileged ports is in RFC2623 It seems that this is depending more on the TCP/IP implementation and it is a de-facto standard. IANA is assigning the port numbers (RFC1700) 
3 Answers 3You are probably looking for RFC 6056 - Recommendations for Transport-Protocol Port Randomization ("Best Current Practice"). Technically there is no requirement that the ephemeral port be >1024 or random (you could build a system that always initiates connections from port 12 because you like the number 12), it's just not "normal" to do so (and an awful idea for a bunch of reasons, some of which are described in that RFC). 
The RFC 6335 is explaining this: Ports in the Dynamic Ports range (49152-65535) have been specifically set aside for local and dynamic use and cannot be assigned through IANA. Application software may simply use any dynamic port that is available on the local host, without any sort of assignment. On the other hand, application software MUST NOT assume that a specific port number in the Dynamic Ports range will always be available for communication at all times, and a port number in that range hence MUST NOT be used as a service identifier. The reserved ports: Ports in the User Ports range (1024-49151) are available for assignment through IANA, and MAY be used as service identifiers upon successful assignment. Ports in the System Ports range (0-1023) are also available for assignment through IANA. Because the System Ports range is both the smallest and the most densely assigned, the requirements for new assignments are more strict than those for the User Ports range, and will only be granted under the "IETF Review" or "IESG Approval" procedures RFC5226 . The introduction explains the confusion: For many years, the assignment of new service names and port number values for use with the Transmission Control Protocol (TCP) [RFC0793] and the User Datagram Protocol (UDP) [RFC0768] has had less than clear guidelines. It seems that Windows XP is not following RFC6335, but Solaris 10 does. What voretaq7 said along with this but being pedantic there is a technical requirement. Historically daemons/servers in *nix are running on ports < 1024 (calling them system ports) thus in order to avoid conflict, source ports (User ports) are > 1024 (or to be precise 1024 - 49151) However that is not always the case as you say and it depends on the implementation. All in all the above link gives a list of RFC's but probably the most specific one is RFC5226 which describes the "Expert Review" process of IANA. 
You must log in to answer this question.Not the answer you're looking for browse other questions tagged tcpip udp rfc ..
Hot Network Questions
Not logged inPage actions.
Network Working Group J. Reynolds Request for Comments: 1700 J. Postel STD: 2 ISI Obsoletes RFCs: 1340, 1060, 1010, 990, 960, October 1994 943, 923, 900, 870, 820, 790, 776, 770, 762, 758,755, 750, 739, 604, 503, 433, 349 Obsoletes IENs: 127, 117, 93 Category: Standards Track Status of this Memo This memo is a status report on the parameters (i.e., numbers and keywords) used in protocols in the Internet community. Distribution of this memo is unlimited. This RFC is a snapshot of the ongoing process of the assignment of protocol parameters for the Internet protocol suite. To make the current information readily available the assignments are kept up-to- date in a set of online text files. This RFC has been assembled by catinating these files together with a minimum of formatting "glue". The authors appologize for the somewhat rougher formatting and style than is typical of most RFCs. We expect that various readers will notice specific items that should be corrected. Please send any specific corrections via email to < [email protected] >. INTRODUCTION The files in this directory document the currently assigned values for several series of numbers used in network protocol implementations. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols. The IANA is chartered by the Internet Society (ISOC) and the Federal Network Council (FNC) to act as the clearinghouse to assign and coordinate the use of numerous Internet protocol parameters. The Internet protocol suite, as defined by the Internet Engineering Task Force (IETF) and its steering group (the IESG), contains numerous parameters, such as internet addresses, domain names, autonomous system numbers (used in some routing protocols), protocol numbers, port numbers, management information base object identifiers, including private enterprise numbers, and many others. The common use of the Internet protocols by the Internet community requires that the particular values used in these parameter fields be assigned uniquely. It is the task of the IANA to make those unique assignments as requested and to maintain a registry of the currently assigned values. Requests for parameter assignments (protocols, ports, etc.) should be sent to < [email protected] >. Requests for SNMP network management private enterprise number assignments should be sent to < [email protected] >. The IANA is located at and operated by the Information Sciences Institute (ISI) of the University of Southern California (USC). 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. Most of the protocols are documented in the RFC series of notes. Some of the items listed are undocumented. Further information on protocols can be found in the memo, "Internet Official Protocol Standards" ( STD 1 ). Data Notations The convention in the documentation of Internet Protocols is to express numbers in decimal and to picture data in "big-endian" order [COHEN]. That is, fields are described left to right, with the most significant octet on the left and the least significant octet on the right. The order of transmission of the header and data described in this document is resolved to the octet level. Whenever a diagram shows a group of octets, the order of transmission of those octets is the normal order in which they are read in English. For example, in the following diagram the octets are transmitted in the order they are numbered. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 1 | 2 | 3 | 4 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 5 | 6 | 7 | 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 9 | 10 | 11 | 12 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Whenever an octet represents a numeric quantity the left most bit in the diagram is the high order or most significant bit. That is, the bit labeled 0 is the most significant bit. For example, the following diagram represents the value 170 (decimal). Similarly, whenever a multi-octet field represents a numeric quantity the left most bit of the whole field is the most significant bit. When a multi-octet quantity is transmitted the most significant octet is transmitted first. Special Addresses There are five classes of IP addresses: Class A through Class E. Of these, Classes A, B, and C are used for unicast addresses, Class D is used for multicast addresses, and Class E addresses are reserved for future use. With the advent of classless addressing [CIDR1, CIDR2], the network-number part of an address may be of any length, and the whole notion of address classes becomes less important. There are certain special cases for IP addresses. These special cases can be concisely summarized using the earlier notation for an IP address: if we also use the notation "-1" to mean the field contains all 1 bits. Some common special cases are as follows: [COHEN] Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer [CIDR1] Fuller, V., T. Li, J. Yu, and K. Varadhan, "Classless [CIDR2] Rekhter, Y., and T. Li, "An Architecture for IP Address URL = ftp://ftp.isi.edu/in-notes/iana/assignments/introduction VERSION NUMBERS 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. Assigned Internet Version Numbers Decimal Keyword Version References ------- ------- ---------- 10-14 Unassigned [JBP] 15 Reserved [JBP] RFC791 Postel, J., ed., "Internet Protocol - DARPA Internet Program RFC1190 Topolcic, C., Editor, "Experimental Internet Stream [JPB] Jon Postel < [email protected] > [JWF] Jim Forgie < [email protected] > [RH6] Robert Hinden < [email protected] > [RXU] Robert Ullmann < [email protected] > [PXF] Paul Francis < [email protected] > [RXC] Ross Callon < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/version-numbers PROTOCOL NUMBERS 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. Assigned Internet Protocol Numbers Decimal Keyword Protocol References ------- -------- ---------- 100 GMTP GMTP [RXB5] 101-254 Unassigned [JBP] [CFTP] Forsdick, H., "CFTP", Network Message, Bolt Beranek and [CISCO] Cisco Systems, "Gateway Server Reference Manual", Manual [DDN] Feinler, E., Editor, "DDN Protocol Handbook", Network [DGP] M/A-COM Government Systems, "Dissimilar Gateway Protocol [ETHERNET] "The Ethernet, A Local Area Network: Data Link Layer and [IEN90] Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90, [IEN119] Forgie, J., "ST - A Proposed Internet Stream Protocol", [IEN158] Haverty, J., "XNET Formats for Internet Protocol Version 4", [MFENET] Shuttleworth, B., "A Documentary of MFENet, a National [PUP] Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An [SPRITE] Welch, B., "The Sprite Remote Procedure Call System", RFC741 Cohen, D., "Specifications for the Network Voice Protocol", RFC768 Postel, J., "User Datagram Protocol", STD 6 , RFC 768 , RFC791 Postel, J., "Internet Protocol - DARPA Internet Program RFC792 Postel, J., "Internet Control Message Protocol - DARPA RFC793 Postel, J., "Transmission Control Protocol - DARPA RFC823 Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway", RFC869 Hinden, R., "A Host Monitoring Protocol", RFC 869 , RFC888 Seamonson, L., and E. Rosen, "STUB" Exterior Gateway RFC905 International Standards Organization, "ISO Transport Protocol RFC908 Velten, D., R. Hinden, and J. Sax, "Reliable Data Protocol", RFC938 Miller, T., "Internet Reliable Transaction Protocol", RFC 938 , RFC969 Clark, D., M. Lambert, and L. Zhang, "NETBLT: A Bulk Data RFC1112 Deering, S., "Host Extensions for IP Multicasting", RFC1241 Woodburn, W., and D. Mills, " A Scheme for an Internet RFC1583 Moy, J., "The OSPF Specification", RFC 1583 , Proteon, [BCH2] Barry Howard < [email protected] > [BK29] Brian Kantor < [email protected] > [BN7] <mystery contact> [BWB6] Barry Boehm < [email protected] > [BXH] Brian Horn <---none---> [BXW] Bruce Willins <---none---> [DDC1] David Clark < [email protected] > [DLM1] David Mills < [email protected] > [DRC3] Dave Cheriton < [email protected] > [DXE1] Deborah Estrin < [email protected] > [DXF] Dirk Fromhein < [email protected] > [DXM2] David Mittnacht <---none---> [DXP2] Dave Presotto < [email protected] [David Johnson] <mystery contact> [GAL5] Guillermo A. Loyola < [email protected] > [GLENN] K. Robert Glenn < [email protected] > [GXC] Greg Chesson < [email protected] > [GXS] Guenther Schreiner < [email protected] > [GXT1] Gene Tsudik < [email protected] > [HCF2] Harry Forsdick < [email protected] > [HWB] Hans-Werner Braun < [email protected] > [HXH] Howard Hart < [email protected] > [JBP] Jon Postel < [email protected] > [JC120] <mystery contact> [JFH2] Jack Haverty < [email protected] > [JI6] John Ioannidis < [email protected] > [JTM4] John Moy < [email protected] > [JXS] Jim Stevens < [email protected] > [KATZ] Dave Katz < [email protected] > [MB] Mike Brescia < [email protected] > [MBG] Michael Greenwald < [email protected] > [ML109] Mike Little < [email protected] > [MTR] Marshall T. Rose < [email protected] > [MXS1] Martha Steenstrup < [email protected] > [NC3] J. Noel Chiappa < [email protected] > [PK] Peter Kirstein < [email protected] > [PXL1] Paul Liu <---none---> [RTB3] Bob Braden < [email protected] > [RC77] <mystery contact> [RWS4] Robert W. Scheifler < [email protected] > [RXB3] Robert Woodburn < [email protected] > [RXH1] Russ Housley < [email protected] > [SAF3] Stuart A. Friedberg < [email protected] > [SC3] Steve Casner < [email protected] [SGC] Steve Chipman < [email protected] > [SHB] Steven Blumenthal < [email protected] > [Sue Hares] Sue Hares < [email protected] > [SXA] Susie Armstrong < [email protected] > [SXD] Steve Deering < [email protected] > [Tony Li] Tony Li < [email protected] > [TXM] Trudy Miller < [email protected] > [VXD] Victor Dafoulas <---none---> [WM3] William Melohn < [email protected] > [WXC] Wesley Craig < [email protected] > [ZSU] Zaw-Sing Su < [email protected] .> URL = ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers WELL KNOWN PORT NUMBERS The Well Known Ports are controlled and assigned by the IANA and on most systems can only be used by system (or root) processes or by programs executed by privileged users. Ports are used in the TCP RFC793 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. The contact port is sometimes called the "well-known port". To the extent possible, these same port assignments are used with the UDP RFC768 . The assigned ports use a small portion of the possible port numbers. For many years the assigned ports were in the range 0-255. Recently, the range for assigned ports managed by the IANA has been expanded to the range 0-1023. Port Assignments: Keyword Decimal Description References ------- ----------- ----------
tcpmux 1/tcp TCP Port Service Multiplexer tcpmux 1/udp TCP Port Service Multiplexer
compressnet 2/tcp Management Utility compressnet 2/udp Management Utility compressnet 3/tcp Compression Process compressnet 3/udp Compression Process
rje 5/tcp Remote Job Entry rje 5/udp Remote Job Entry
echo 7/tcp Echo echo 7/udp Echo
discard 9/tcp Discard discard 9/udp Discard
systat 11/tcp Active Users systat 11/udp Active Users
daytime 13/tcp Daytime daytime 13/udp Daytime
qotd 17/tcp Quote of the Day qotd 17/udp Quote of the Day msp 18/tcp Message Send Protocol msp 18/udp Message Send Protocol
chargen 19/tcp Character Generator chargen 19/udp Character Generator ftp-data 20/tcp File Transfer [Default Data] ftp-data 20/udp File Transfer [Default Data] ftp 21/tcp File Transfer [Control] ftp 21/udp File Transfer [Control]
telnet 23/tcp Telnet telnet 23/udp Telnet
smtp 25/tcp Simple Mail Transfer smtp 25/udp Simple Mail Transfer
nsw-fe 27/tcp NSW User System FE nsw-fe 27/udp NSW User System FE
msg-icp 29/tcp MSG ICP msg-icp 29/udp MSG ICP
msg-auth 31/tcp MSG Authentication msg-auth 31/udp MSG Authentication
dsp 33/tcp Display Support Protocol dsp 33/udp Display Support Protocol
time 37/tcp Time time 37/udp Time rap 38/tcp Route Access Protocol rap 38/udp Route Access Protocol
rlp 39/tcp Resource Location Protocol rlp 39/udp Resource Location Protocol
graphics 41/tcp Graphics graphics 41/udp Graphics nameserver 42/tcp Host Name Server nameserver 42/udp Host Name Server nicname 43/tcp Who Is nicname 43/udp Who Is mpm-flags 44/tcp MPM FLAGS Protocol mpm-flags 44/udp MPM FLAGS Protocol mpm 45/tcp Message Processing Module [recv] mpm 45/udp Message Processing Module [recv] mpm-snd 46/tcp MPM [default send] mpm-snd 46/udp MPM [default send] ni-ftp 47/tcp NI FTP ni-ftp 47/udp NI FTP
auditd 48/tcp Digital Audit Daemon auditd 48/udp Digital Audit Daemon
login 49/tcp Login Host Protocol login 49/udp Login Host Protocol
re-mail-ck 50/tcp Remote Mail Checking Protocol re-mail-ck 50/udp Remote Mail Checking Protocol
la-maint 51/tcp IMP Logical Address Maintenance la-maint 51/udp IMP Logical Address Maintenance
xns-time 52/tcp XNS Time Protocol xns-time 52/udp XNS Time Protocol
domain 53/tcp Domain Name Server domain 53/udp Domain Name Server
xns-ch 54/tcp XNS Clearinghouse xns-ch 54/udp XNS Clearinghouse isi-gl 55/tcp ISI Graphics Language isi-gl 55/udp ISI Graphics Language xns-auth 56/tcp XNS Authentication xns-auth 56/udp XNS Authentication xns-mail 58/tcp XNS Mail xns-mail 58/udp XNS Mail ni-mail 61/tcp NI MAIL ni-mail 61/udp NI MAIL acas 62/tcp ACA Services acas 62/udp ACA Services
covia 64/tcp Communications Integrator (CI) covia 64/udp Communications Integrator (CI)
< [email protected] > tacacs-ds 65/tcp TACACS-Database Service tacacs-ds 65/udp TACACS-Database Service
sql*net 66/tcp Oracle SQL*NET sql*net 66/udp Oracle SQL*NET
bootps 67/tcp Bootstrap Protocol Server bootps 67/udp Bootstrap Protocol Server bootpc 68/tcp Bootstrap Protocol Client bootpc 68/udp Bootstrap Protocol Client
tftp 69/tcp Trivial File Transfer tftp 69/udp Trivial File Transfer
gopher 70/tcp Gopher gopher 70/udp Gopher
netrjs-1 71/tcp Remote Job Service netrjs-1 71/udp Remote Job Service netrjs-2 72/tcp Remote Job Service netrjs-2 72/udp Remote Job Service netrjs-3 73/tcp Remote Job Service netrjs-3 73/udp Remote Job Service netrjs-4 74/tcp Remote Job Service netrjs-4 74/udp Remote Job Service
deos 76/tcp Distributed External Object Store deos 76/udp Distributed External Object Store vettcp 78/tcp vettcp vettcp 78/udp vettcp
finger 79/tcp Finger finger 79/udp Finger
www-http 80/tcp World Wide Web HTTP www-http 80/udp World Wide Web HTTP
hosts2-ns 81/tcp HOSTS2 Name Server hosts2-ns 81/udp HOSTS2 Name Server
xfer 82/tcp XFER Utility xfer 82/udp XFER Utility
mit-ml-dev 83/tcp MIT ML Device mit-ml-dev 83/udp MIT ML Device
ctf 84/tcp Common Trace Facility ctf 84/udp Common Trace Facility
mit-ml-dev 85/tcp MIT ML Device mit-ml-dev 85/udp MIT ML Device mfcobol 86/tcp Micro Focus Cobol mfcobol 86/udp Micro Focus Cobol
kerberos 88/tcp Kerberos kerberos 88/udp Kerberos
su-mit-tg 89/tcp SU/MIT Telnet Gateway su-mit-tg 89/udp SU/MIT Telnet Gateway
dnsix 90/tcp DNSIX Securit Attribute Token Map dnsix 90/udp DNSIX Securit Attribute Token Map
mit-dov 91/tcp MIT Dover Spooler mit-dov 91/udp MIT Dover Spooler
npp 92/tcp Network Printing Protocol npp 92/udp Network Printing Protocol
dcp 93/tcp Device Control Protocol dcp 93/udp Device Control Protocol
objcall 94/tcp Tivoli Object Dispatcher objcall 94/udp Tivoli Object Dispatcher
supdup 95/tcp SUPDUP supdup 95/udp SUPDUP dixie 96/tcp DIXIE Protocol Specification dixie 96/udp DIXIE Protocol Specification
swift-rvf 97/tcp Swift Remote Vitural File Protocol swift-rvf 97/udp Swift Remote Vitural File Protocol
tacnews 98/tcp TAC News tacnews 98/udp TAC News metagram 99/tcp Metagram Relay metagram 99/udp Metagram Relay
newacct 100/tcp [unauthorized use] hostname 101/tcp NIC Host Name Server hostname 101/udp NIC Host Name Server iso-tsap 102/tcp ISO-TSAP iso-tsap 102/udp ISO-TSAP
gppitnp 103/tcp Genesis Point-to-Point Trans Net gppitnp 103/udp Genesis Point-to-Point Trans Net acr-nema 104/tcp ACR-NEMA Digital Imag. & Comm. 300 acr-nema 104/udp ACR-NEMA Digital Imag. & Comm. 300
csnet-ns 105/tcp Mailbox Name Nameserver csnet-ns 105/udp Mailbox Name Nameserver
3com-tsmux 106/tcp 3COM-TSMUX 3com-tsmux 106/udp 3COM-TSMUX
rtelnet 107/tcp Remote Telnet Service rtelnet 107/udp Remote Telnet Service snagas 108/tcp SNA Gateway Access Server snagas 108/udp SNA Gateway Access Server
pop2 109/tcp Post Office Protocol - Version 2 pop2 109/udp Post Office Protocol - Version 2
pop3 110/tcp Post Office Protocol - Version 3 pop3 110/udp Post Office Protocol - Version 3 sunrpc 111/tcp SUN Remote Procedure Call sunrpc 111/udp SUN Remote Procedure Call
mcidas 112/tcp McIDAS Data Transmission Protocol mcidas 112/udp McIDAS Data Transmission Protocol
auth 113/tcp Authentication Service auth 113/udp Authentication Service
audionews 114/tcp Audio News Multicast audionews 114/udp Audio News Multicast
sftp 115/tcp Simple File Transfer Protocol sftp 115/udp Simple File Transfer Protocol ansanotify 116/tcp ANSA REX Notify ansanotify 116/udp ANSA REX Notify
uucp-path 117/tcp UUCP Path Service uucp-path 117/udp UUCP Path Service sqlserv 118/tcp SQL Services sqlserv 118/udp SQL Services
nntp 119/tcp Network News Transfer Protocol nntp 119/udp Network News Transfer Protocol
cfdptkt 120/tcp CFDPTKT cfdptkt 120/udp CFDPTKT
erpc 121/tcp Encore Expedited Remote Pro.Call erpc 121/udp Encore Expedited Remote Pro.Call
smakynet 122/tcp SMAKYNET smakynet 122/udp SMAKYNET
ntp 123/tcp Network Time Protocol ntp 123/udp Network Time Protocol
ansatrader 124/tcp ANSA REX Trader ansatrader 124/udp ANSA REX Trader locus-map 125/tcp Locus PC-Interface Net Map Ser locus-map 125/udp Locus PC-Interface Net Map Ser
unitary 126/tcp Unisys Unitary Login unitary 126/udp Unisys Unitary Login locus-con 127/tcp Locus PC-Interface Conn Server locus-con 127/udp Locus PC-Interface Conn Server gss-xlicen 128/tcp GSS X License Verification gss-xlicen 128/udp GSS X License Verification
pwdgen 129/tcp Password Generator Protocol pwdgen 129/udp Password Generator Protocol
cisco-fna 130/tcp cisco FNATIVE cisco-fna 130/udp cisco FNATIVE cisco-tna 131/tcp cisco TNATIVE cisco-tna 131/udp cisco TNATIVE cisco-sys 132/tcp cisco SYSMAINT cisco-sys 132/udp cisco SYSMAINT statsrv 133/tcp Statistics Service statsrv 133/udp Statistics Service ingres-net 134/tcp INGRES-NET Service ingres-net 134/udp INGRES-NET Service
loc-srv 135/tcp Location Service loc-srv 135/udp Location Service
profile 136/tcp PROFILE Naming System profile 136/udp PROFILE Naming System
netbios-ns 137/tcp NETBIOS Name Service netbios-ns 137/udp NETBIOS Name Service netbios-dgm 138/tcp NETBIOS Datagram Service netbios-dgm 138/udp NETBIOS Datagram Service netbios-ssn 139/tcp NETBIOS Session Service netbios-ssn 139/udp NETBIOS Session Service emfis-data 140/tcp EMFIS Data Service emfis-data 140/udp EMFIS Data Service emfis-cntl 141/tcp EMFIS Control Service emfis-cntl 141/udp EMFIS Control Service
bl-idm 142/tcp Britton-Lee IDM bl-idm 142/udp Britton-Lee IDM
imap2 143/tcp Interim Mail Access Protocol v2 imap2 143/udp Interim Mail Access Protocol v2 news 144/tcp NewS news 144/udp NewS
uaac 145/tcp UAAC Protocol uaac 145/udp UAAC Protocol
iso-tp0 146/tcp ISO-IP0 iso-tp0 146/udp ISO-IP0 iso-ip 147/tcp ISO-IP iso-ip 147/udp ISO-IP cronus 148/tcp CRONUS-SUPPORT cronus 148/udp CRONUS-SUPPORT
aed-512 149/tcp AED 512 Emulation Service aed-512 149/udp AED 512 Emulation Service
sql-net 150/tcp SQL-NET sql-net 150/udp SQL-NET
hems 151/tcp HEMS hems 151/udp HEMS
bftp 152/tcp Background File Transfer Program bftp 152/udp Background File Transfer Program
sgmp 153/tcp SGMP sgmp 153/udp SGMP
netsc-prod 154/tcp NETSC netsc-prod 154/udp NETSC netsc-dev 155/tcp NETSC netsc-dev 155/udp NETSC
sqlsrv 156/tcp SQL Service sqlsrv 156/udp SQL Service
knet-cmp 157/tcp KNET/VM Command/Message Protocol knet-cmp 157/udp KNET/VM Command/Message Protocol
pcmail-srv 158/tcp PCMail Server pcmail-srv 158/udp PCMail Server
nss-routing 159/tcp NSS-Routing nss-routing 159/udp NSS-Routing
sgmp-traps 160/tcp SGMP-TRAPS sgmp-traps 160/udp SGMP-TRAPS snmp 161/tcp SNMP snmp 161/udp SNMP snmptrap 162/tcp SNMPTRAP snmptrap 162/udp SNMPTRAP cmip-man 163/tcp CMIP/TCP Manager cmip-man 163/udp CMIP/TCP Manager cmip-agent 164/tcp CMIP/TCP Agent smip-agent 164/udp CMIP/TCP Agent
xns-courier 165/tcp Xerox xns-courier 165/udp Xerox
s-net 166/tcp Sirius Systems s-net 166/udp Sirius Systems
namp 167/tcp NAMP namp 167/udp NAMP rsvd 168/tcp RSVD rsvd 168/udp RSVD
send 169/tcp SEND send 169/udp SEND
print-srv 170/tcp Network PostScript print-srv 170/udp Network PostScript
multiplex 171/tcp Network Innovations Multiplex multiplex 171/udp Network Innovations Multiplex cl/1 172/tcp Network Innovations CL/1 cl/1 172/udp Network Innovations CL/1
xyplex-mux 173/tcp Xyplex xyplex-mux 173/udp Xyplex
mailq 174/tcp MAILQ mailq 174/udp MAILQ
vmnet 175/tcp VMNET vmnet 175/udp VMNET genrad-mux 176/tcp GENRAD-MUX genrad-mux 176/udp GENRAD-MUX
xdmcp 177/tcp X Display Manager Control Protocol xdmcp 177/udp X Display Manager Control Protocol
nextstep 178/tcp NextStep Window Server NextStep 178/udp NextStep Window Server
bgp 179/tcp Border Gateway Protocol bgp 179/udp Border Gateway Protocol
ris 180/tcp Intergraph ris 180/udp Intergraph
unify 181/tcp Unify unify 181/udp Unify
audit 182/tcp Unisys Audit SITP audit 182/udp Unisys Audit SITP
ocbinder 183/tcp OCBinder ocbinder 183/udp OCBinder ocserver 184/tcp OCServer ocserver 184/udp OCServer
remote-kis 185/tcp Remote-KIS remote-kis 185/udp Remote-KIS kis 186/tcp KIS Protocol kis 186/udp KIS Protocol
aci 187/tcp Application Communication Interface aci 187/udp Application Communication Interface
mumps 188/tcp Plus Five's MUMPS mumps 188/udp Plus Five's MUMPS
qft 189/tcp Queued File Transport qft 189/udp Queued File Transport
gacp 190/tcp Gateway Access Control Protocol cacp 190/udp Gateway Access Control Protocol
prospero 191/tcp Prospero Directory Service prospero 191/udp Prospero Directory Service osu-nms 192/tcp OSU Network Monitoring System osu-nms 192/udp OSU Network Monitoring System
srmp 193/tcp Spider Remote Monitoring Protocol srmp 193/udp Spider Remote Monitoring Protocol
irc 194/tcp Internet Relay Chat Protocol irc 194/udp Internet Relay Chat Protocol
dn6-nlm-aud 195/tcp DNSIX Network Level Module Audit dn6-nlm-aud 195/udp DNSIX Network Level Module Audit dn6-smm-red 196/tcp DNSIX Session Mgt Module Audit Redir dn6-smm-red 196/udp DNSIX Session Mgt Module Audit Redir
dls 197/tcp Directory Location Service dls 197/udp Directory Location Service dls-mon 198/tcp Directory Location Service Monitor dls-mon 198/udp Directory Location Service Monitor
smux 199/tcp SMUX smux 199/udp SMUX src 200/tcp IBM System Resource Controller src 200/udp IBM System Resource Controller
at-rtmp 201/tcp AppleTalk Routing Maintenance at-rtmp 201/udp AppleTalk Routing Maintenance at-nbp 202/tcp AppleTalk Name Binding at-nbp 202/udp AppleTalk Name Binding at-3 203/tcp AppleTalk Unused at-3 203/udp AppleTalk Unused at-echo 204/tcp AppleTalk Echo at-echo 204/udp AppleTalk Echo at-5 205/tcp AppleTalk Unused at-5 205/udp AppleTalk Unused at-zis 206/tcp AppleTalk Zone Information at-zis 206/udp AppleTalk Zone Information at-7 207/tcp AppleTalk Unused at-7 207/udp AppleTalk Unused at-8 208/tcp AppleTalk Unused at-8 208/udp AppleTalk Unused
tam 209/tcp Trivial Authenticated Mail Protocol tam 209/udp Trivial Authenticated Mail Protocol
z39.50 210/tcp ANSI Z39.50 z39.50 210/udp ANSI Z39.50
914c/g 211/tcp Texas Instruments 914C/G Terminal 914c/g 211/udp Texas Instruments 914C/G Terminal
anet 212/tcp ATEXSSTR anet 212/udp ATEXSSTR
ipx 213/tcp IPX ipx 213/udp IPX
vmpwscs 214/tcp VM PWSCS vmpwscs 214/udp VM PWSCS
softpc 215/tcp Insignia Solutions softpc 215/udp Insignia Solutions
atls 216/tcp Access Technology License Server atls 216/udp Access Technology License Server
dbase 217/tcp dBASE Unix dbase 217/udp dBASE Unix mpp 218/tcp Netix Message Posting Protocol mpp 218/udp Netix Message Posting Protocol
uarps 219/tcp Unisys ARPs uarps 219/udp Unisys ARPs
imap3 220/tcp Interactive Mail Access Protocol v3 imap3 220/udp Interactive Mail Access Protocol v3
fln-spx 221/tcp Berkeley rlogind with SPX auth fln-spx 221/udp Berkeley rlogind with SPX auth rsh-spx 222/tcp Berkeley rshd with SPX auth rsh-spx 222/udp Berkeley rshd with SPX auth cdc 223/tcp Certificate Distribution Center cdc 223/udp Certificate Distribution Center
sur-meas 243/tcp Survey Measurement sur-meas 243/udp Survey Measurement
link 245/tcp LINK link 245/udp LINK dsp3270 246/tcp Display Systems Protocol dsp3270 246/udp Display Systems Protocol
pdap 344/tcp Prospero Data Access Protocol pdap 344/udp Prospero Data Access Protocol pawserv 345/tcp Perf Analysis Workbench pawserv 345/udp Perf Analysis Workbench zserv 346/tcp Zebra server zserv 346/udp Zebra server fatserv 347/tcp Fatmen Server fatserv 347/udp Fatmen Server csi-sgwp 348/tcp Cabletron Management Protocol csi-sgwp 348/udp Cabletron Management Protocol
clearcase 371/tcp Clearcase clearcase 371/udp Clearcase
ulistserv 372/tcp Unix Listserv ulistserv 372/udp Unix Listserv
legent-1 373/tcp Legent Corporation legent-1 373/udp Legent Corporation legent-2 374/tcp Legent Corporation legent-2 374/udp Legent Corporation
hassle 375/tcp Hassle hassle 375/udp Hassle
nip 376/tcp Amiga Envoy Network Inquiry Proto nip 376/udp Amiga Envoy Network Inquiry Proto
tnETOS 377/tcp NEC Corporation tnETOS 377/udp NEC Corporation dsETOS 378/tcp NEC Corporation dsETOS 378/udp NEC Corporation
is99c 379/tcp TIA/EIA/IS-99 modem client is99c 379/udp TIA/EIA/IS-99 modem client is99s 380/tcp TIA/EIA/IS-99 modem server is99s 380/udp TIA/EIA/IS-99 modem server
hp-collector 381/tcp hp performance data collector hp-collector 381/udp hp performance data collector hp-managed-node 382/tcp hp performance data managed node hp-managed-node 382/udp hp performance data managed node hp-alarm-mgr 383/tcp hp performance data alarm manager hp-alarm-mgr 383/udp hp performance data alarm manager
arns 384/tcp A Remote Network Server System arns 384/udp A Remote Network Server System
ibm-app 385/tcp IBM Application ibm-app 385/tcp IBM Application
asa 386/tcp ASA Message Router Object Def. asa 386/udp ASA Message Router Object Def.
aurp 387/tcp Appletalk Update-Based Routing Pro. aurp 387/udp Appletalk Update-Based Routing Pro.
unidata-ldm 388/tcp Unidata LDM Version 4 unidata-ldm 388/udp Unidata LDM Version 4 ldap 389/tcp Lightweight Directory Access Protocol ldap 389/udp Lightweight Directory Access Protocol uis 390/tcp UIS uis 390/udp UIS
synotics-relay 391/tcp SynOptics SNMP Relay Port synotics-relay 391/udp SynOptics SNMP Relay Port synotics-broker 392/tcp SynOptics Port Broker Port synotics-broker 392/udp SynOptics Port Broker Port
dis 393/tcp Data Interpretation System dis 393/udp Data Interpretation System
embl-ndt 394/tcp EMBL Nucleic Data Transfer embl-ndt 394/udp EMBL Nucleic Data Transfer
netcp 395/tcp NETscout Control Protocol netcp 395/udp NETscout Control Protocol
netware-ip 396/tcp Novell Netware over IP netware-ip 396/udp Novell Netware over IP mptn 397/tcp Multi Protocol Trans. Net. mptn 397/udp Multi Protocol Trans. Net.
kryptolan 398/tcp Kryptolan kryptolan 398/udp Kryptolan
work-sol 400/tcp Workstation Solutions work-sol 400/udp Workstation Solutions
ups 401/tcp Uninterruptible Power Supply ups 401/udp Uninterruptible Power Supply
genie 402/tcp Genie Protocol genie 402/udp Genie Protocol
decap 403/tcp decap decap 403/udp decap nced 404/tcp nced nced 404/udp nced ncld 405/tcp ncld ncld 405/udp ncld
imsp 406/tcp Interactive Mail Support Protocol imsp 406/udp Interactive Mail Support Protocol
timbuktu 407/tcp Timbuktu timbuktu 407/udp Timbuktu
prm-sm 408/tcp Prospero Resource Manager Sys. Man. prm-sm 408/udp Prospero Resource Manager Sys. Man. prm-nm 409/tcp Prospero Resource Manager Node Man. prm-nm 409/udp Prospero Resource Manager Node Man. decladebug 410/tcp DECLadebug Remote Debug Protocol decladebug 410/udp DECLadebug Remote Debug Protocol
rmt 411/tcp Remote MT Protocol rmt 411/udp Remote MT Protocol
synoptics-trap 412/tcp Trap Convention Port synoptics-trap 412/udp Trap Convention Port smsp 413/tcp SMSP smsp 413/udp SMSP infoseek 414/tcp InfoSeek infoseek 414/udp InfoSeek
bnet 415/tcp BNet bnet 415/udp BNet
silverplatter 416/tcp Silverplatter silverplatter 416/udp Silverplatter
onmux 417/tcp Onmux onmux 417/udp Onmux
hyper-g 418/tcp Hyper-G hyper-g 418/udp Hyper-G
ariel1 419/tcp Ariel ariel1 419/udp Ariel
smpte 420/tcp SMPTE smpte 420/udp SMPTE
ariel2 421/tcp Ariel ariel2 421/udp Ariel ariel3 422/tcp Ariel ariel3 422/udp Ariel opc-job-start 423/tcp IBM Operations Planning and Control Start opc-job-start 423/udp IBM Operations Planning and Control Start opc-job-track 424/tcp IBM Operations Planning and Control Track opc-job-track 424/udp IBM Operations Planning and Control Track
icad-el 425/tcp ICAD icad-el 425/udp ICAD
smartsdp 426/tcp smartsdp smartsdp 426/udp smartsdp
svrloc 427/tcp Server Location svrloc 427/udp Server Location ocs_cmu 428/tcp OCS_CMU ocs_cmu 428/udp OCS_CMU ocs_amu 429/tcp OCS_AMU ocs_amu 429/udp OCS_AMU
utmpsd 430/tcp UTMPSD utmpsd 430/udp UTMPSD utmpcd 431/tcp UTMPCD utmpcd 431/udp UTMPCD iasd 432/tcp IASD iasd 432/udp IASD
nnsp 433/tcp NNSP nnsp 433/udp NNSP
mobileip-agent 434/tcp MobileIP-Agent mobileip-agent 434/udp MobileIP-Agent mobilip-mn 435/tcp MobilIP-MN mobilip-mn 435/udp MobilIP-MN dna-cml 436/tcp DNA-CML dna-cml 436/udp DNA-CML
comscm 437/tcp comscm comscm 437/udp comscm
dsfgw 438/tcp dsfgw dsfgw 438/udp dsfgw
dasp 439/tcp dasp Thomas Obermair dasp 439/udp dasp [email protected]
sgcp 440/tcp sgcp sgcp 440/udp sgcp decvms-sysmgt 441/tcp decvms-sysmgt decvms-sysmgt 441/udp decvms-sysmgt
cvc_hostd 442/tcp cvc_hostd cvc_hostd 442/udp cvc_hostd
https 443/tcp https MCom https 443/udp https MCom
snpp 444/tcp Simple Network Paging Protocol snpp 444/udp Simple Network Paging Protocol microsoft-ds 445/tcp Microsoft-DS microsoft-ds 445/udp Microsoft-DS
ddm-rdb 446/tcp DDM-RDB ddm-rdb 446/udp DDM-RDB ddm-dfm 447/tcp DDM-RFM ddm-dfm 447/udp DDM-RFM ddm-byte 448/tcp DDM-BYTE ddm-byte 448/udp DDM-BYTE
as-servermap 449/tcp AS Server Mapper as-servermap 449/udp AS Server Mapper
tserver 450/tcp TServer tserver 450/udp TServer
exec 512/tcp remote process execution;
biff 512/udp used by mail system to notify users
login 513/tcp remote login a la telnet;
who 513/udp maintains data bases showing who's
cmd 514/tcp like exec, but automatic
syslog 514/udp printer 515/tcp spooler printer 515/udp spooler
talk 517/tcp like tenex link, but across
talk 517/udp like tenex link, but across ntalk 518/tcp ntalk 518/udp utime 519/tcp unixtime utime 519/udp unixtime efs 520/tcp extended file name server router 520/udp local routing process (on site);
timed 525/tcp timeserver timed 525/udp timeserver tempo 526/tcp newdate tempo 526/udp newdate
courier 530/tcp rpc courier 530/udp rpc conference 531/tcp chat conference 531/udp chat netnews 532/tcp readnews netnews 532/udp readnews netwall 533/tcp for emergency broadcasts netwall 533/udp for emergency broadcasts
apertus-ldp 539/tcp Apertus Technologies Load Determination apertus-ldp 539/udp Apertus Technologies Load Determination uucp 540/tcp uucpd uucp 540/udp uucpd uucp-rlogin 541/tcp uucp-rlogin Stuart Lynne uucp-rlogin 541/udp uucp-rlogin [email protected]
klogin 543/tcp klogin 543/udp kshell 544/tcp krcmd kshell 544/udp krcmd
new-rwho 550/tcp new-who new-rwho 550/udp new-who
dsf 555/tcp dsf 555/udp remotefs 556/tcp rfs server remotefs 556/udp rfs server
rmonitor 560/tcp rmonitord rmonitor 560/udp rmonitord monitor 561/tcp monitor 561/udp chshell 562/tcp chcmd chshell 562/udp chcmd
9pfs 564/tcp plan 9 file service 9pfs 564/udp plan 9 file service whoami 565/tcp whoami whoami 565/udp whoami
meter 570/tcp demon meter 570/udp demon meter 571/tcp udemon meter 571/udp udemon
ipcserver 600/tcp Sun IPC server ipcserver 600/udp Sun IPC server nqs 607/tcp nqs nqs 607/udp nqs urm 606/tcp Cray Unified Resource Manager urm 606/udp Cray Unified Resource Manager
sift-uft 608/tcp Sender-Initiated/Unsolicited File Transfer sift-uft 608/udp Sender-Initiated/Unsolicited File Transfer
npmp-trap 609/tcp npmp-trap npmp-trap 609/udp npmp-trap npmp-local 610/tcp npmp-local npmp-local 610/udp npmp-local npmp-gui 611/tcp npmp-gui npmp-gui 611/udp npmp-gui
ginad 634/tcp ginad ginad 634/udp ginad
mdqs 666/tcp mdqs 666/udp doom 666/tcp doom Id Software doom 666/tcp doom Id Software elcsd 704/tcp errlog copy/server daemon elcsd 704/udp errlog copy/server daemon entrustmanager 709/tcp EntrustManager entrustmanager 709/udp EntrustManager
netviewdm1 729/tcp IBM NetView DM/6000 Server/Client netviewdm1 729/udp IBM NetView DM/6000 Server/Client netviewdm2 730/tcp IBM NetView DM/6000 send/tcp netviewdm2 730/udp IBM NetView DM/6000 send/tcp netviewdm3 731/tcp IBM NetView DM/6000 receive/tcp netviewdm3 731/udp IBM NetView DM/6000 receive/tcp
netgw 741/tcp netGW netgw 741/udp netGW netrcs 742/tcp Network based Rev. Cont. Sys. netrcs 742/udp Network based Rev. Cont. Sys.
flexlm 744/tcp Flexible License Manager flexlm 744/udp Flexible License Manager
fujitsu-dev 747/tcp Fujitsu Device Control fujitsu-dev 747/udp Fujitsu Device Control ris-cm 748/tcp Russell Info Sci Calendar Manager ris-cm 748/udp Russell Info Sci Calendar Manager kerberos-adm 749/tcp kerberos administration kerberos-adm 749/udp kerberos administration rfile 750/tcp loadav 750/udp pump 751/tcp pump 751/udp qrh 752/tcp qrh 752/udp rrh 753/tcp rrh 753/udp tell 754/tcp send tell 754/udp send nlogin 758/tcp nlogin 758/udp con 759/tcp con 759/udp ns 760/tcp ns 760/udp rxe 761/tcp rxe 761/udp quotad 762/tcp quotad 762/udp cycleserv 763/tcp cycleserv 763/udp omserv 764/tcp omserv 764/udp webster 765/tcp webster 765/udp phonebook 767/tcp phone phonebook 767/udp phone vid 769/tcp vid 769/udp cadlock 770/tcp cadlock 770/udp rtip 771/tcp rtip 771/udp cycleserv2 772/tcp cycleserv2 772/udp submit 773/tcp notify 773/udp rpasswd 774/tcp acmaint_dbd 774/udp entomb 775/tcp acmaint_transd 775/udp wpages 776/tcp wpages 776/udp wpgs 780/tcp wpgs 780/udp concert 786/tcp Concert concert 786/udp Concert
mdbs_daemon 800/tcp mdbs_daemon 800/udp device 801/tcp device 801/udp xtreelic 996/tcp Central Point Software xtreelic 996/udp Central Point Software
maitrd 997/tcp maitrd 997/udp busboy 998/tcp puparp 998/udp garcon 999/tcp applix 999/udp Applix ac puprouter 999/tcp puprouter 999/udp cadlock 1000/tcp ock 1000/udp
REGISTERED PORT NUMBERS The Registered Ports are not controlled by the IANA and on most systems can be used by ordinary user processes or programs executed by ordinary users. Ports are used in the TCP RFC793 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. While the IANA can not control uses of these ports it does register or list uses of these ports as a convienence to the community. The Registered Ports are in the range 1024-65535. blackjack 1025/tcp network blackjack blackjack 1025/udp network blackjack iad1 1030/tcp BBN IAD iad1 1030/udp BBN IAD iad2 1031/tcp BBN IAD iad2 1031/udp BBN IAD iad3 1032/tcp BBN IAD iad3 1032/udp BBN IAD instl_boots 1067/tcp Installation Bootstrap Proto. Serv. instl_boots 1067/udp Installation Bootstrap Proto. Serv. instl_bootc 1068/tcp Installation Bootstrap Proto. Cli. instl_bootc 1068/udp Installation Bootstrap Proto. Cli.
socks 1080/tcp Socks socks 1080/udp Socks
ansoft-lm-1 1083/tcp Anasoft License Manager ansoft-lm-1 1083/udp Anasoft License Manager ansoft-lm-2 1084/tcp Anasoft License Manager ansoft-lm-2 1084/udp Anasoft License Manager nfa 1155/tcp Network File Access nfa 1155/udp Network File Access
nerv 1222/tcp SNI R&D network nerv 1222/udp SNI R&D network
hermes 1248/tcp hermes 1248/udp alta-ana-lm 1346/tcp Alta Analytics License Manager alta-ana-lm 1346/udp Alta Analytics License Manager bbn-mmc 1347/tcp multi media conferencing bbn-mmc 1347/udp multi media conferencing bbn-mmx 1348/tcp multi media conferencing bbn-mmx 1348/udp multi media conferencing sbook 1349/tcp Registration Network Protocol sbook 1349/udp Registration Network Protocol editbench 1350/tcp Registration Network Protocol editbench 1350/udp Registration Network Protocol
equationbuilder 1351/tcp Digital Tool Works (MIT) equationbuilder 1351/udp Digital Tool Works (MIT)
lotusnote 1352/tcp Lotus Note lotusnote 1352/udp Lotus Note
relief 1353/tcp Relief Consulting relief 1353/udp Relief Consulting
rightbrain 1354/tcp RightBrain Software rightbrain 1354/udp RightBrain Software
intuitive edge 1355/tcp Intuitive Edge intuitive edge 1355/udp Intuitive Edge
cuillamartin 1356/tcp CuillaMartin Company cuillamartin 1356/udp CuillaMartin Company pegboard 1357/tcp Electronic PegBoard pegboard 1357/udp Electronic PegBoard
connlcli 1358/tcp CONNLCLI connlcli 1358/udp CONNLCLI ftsrv 1359/tcp FTSRV ftsrv 1359/udp FTSRV
mimer 1360/tcp MIMER mimer 1360/udp MIMER
linx 1361/tcp LinX linx 1361/udp LinX
timeflies 1362/tcp TimeFlies timeflies 1362/udp TimeFlies
ndm-requester 1363/tcp Network DataMover Requester ndm-requester 1363/udp Network DataMover Requester ndm-server 1364/tcp Network DataMover Server ndm-server 1364/udp Network DataMover Server
adapt-sna 1365/tcp Network Software Associates adapt-sna 1365/udp Network Software Associates
netware-csp 1366/tcp Novell NetWare Comm Service Platform netware-csp 1366/udp Novell NetWare Comm Service Platform
dcs 1367/tcp DCS dcs 1367/udp DCS
screencast 1368/tcp ScreenCast screencast 1368/udp ScreenCast
gv-us 1369/tcp GlobalView to Unix Shell gv-us 1369/udp GlobalView to Unix Shell us-gv 1370/tcp Unix Shell to GlobalView us-gv 1370/udp Unix Shell to GlobalView
fc-cli 1371/tcp Fujitsu Config Protocol fc-cli 1371/udp Fujitsu Config Protocol fc-ser 1372/tcp Fujitsu Config Protocol fc-ser 1372/udp Fujitsu Config Protocol
chromagrafx 1373/tcp Chromagrafx chromagrafx 1373/udp Chromagrafx
molly 1374/tcp EPI Software Systems molly 1374/udp EPI Software Systems
bytex 1375/tcp Bytex bytex 1375/udp Bytex
ibm-pps 1376/tcp IBM Person to Person Software ibm-pps 1376/udp IBM Person to Person Software
cichlid 1377/tcp Cichlid License Manager cichlid 1377/udp Cichlid License Manager
elan 1378/tcp Elan License Manager elan 1378/udp Elan License Manager
dbreporter 1379/tcp Integrity Solutions dbreporter 1379/udp Integrity Solutions
telesis-licman 1380/tcp Telesis Network License Manager telesis-licman 1380/udp Telesis Network License Manager
apple-licman 1381/tcp Apple Network License Manager apple-licman 1381/udp Apple Network License Manager
udt_os 1382/tcp udt_os 1382/udp gwha 1383/tcp GW Hannaway Network License Manager gwha 1383/udp GW Hannaway Network License Manager
os-licman 1384/tcp Objective Solutions License Manager os-licman 1384/udp Objective Solutions License Manager
atex_elmd 1385/tcp Atex Publishing License Manager atex_elmd 1385/udp Atex Publishing License Manager
checksum 1386/tcp CheckSum License Manager checksum 1386/udp CheckSum License Manager
cadsi-lm 1387/tcp Computer Aided Design Software Inc LM cadsi-lm 1387/udp Computer Aided Design Software Inc LM
objective-dbc 1388/tcp Objective Solutions DataBase Cache objective-dbc 1388/udp Objective Solutions DataBase Cache
iclpv-dm 1389/tcp Document Manager iclpv-dm 1389/udp Document Manager iclpv-sc 1390/tcp Storage Controller iclpv-sc 1390/udp Storage Controller iclpv-sas 1391/tcp Storage Access Server iclpv-sas 1391/udp Storage Access Server iclpv-pm 1392/tcp Print Manager iclpv-pm 1392/udp Print Manager iclpv-nls 1393/tcp Network Log Server iclpv-nls 1393/udp Network Log Server iclpv-nlc 1394/tcp Network Log Client iclpv-nlc 1394/udp Network Log Client iclpv-wsm 1395/tcp PC Workstation Manager software iclpv-wsm 1395/udp PC Workstation Manager software
dvl-activemail 1396/tcp DVL Active Mail dvl-activemail 1396/udp DVL Active Mail audio-activmail 1397/tcp Audio Active Mail audio-activmail 1397/udp Audio Active Mail video-activmail 1398/tcp Video Active Mail video-activmail 1398/udp Video Active Mail
cadkey-licman 1399/tcp Cadkey License Manager cadkey-licman 1399/udp Cadkey License Manager cadkey-tablet 1400/tcp Cadkey Tablet Daemon cadkey-tablet 1400/udp Cadkey Tablet Daemon
goldleaf-licman 1401/tcp Goldleaf License Manager goldleaf-licman 1401/udp Goldleaf License Manager
prm-sm-np 1402/tcp Prospero Resource Manager prm-sm-np 1402/udp Prospero Resource Manager prm-nm-np 1403/tcp Prospero Resource Manager prm-nm-np 1403/udp Prospero Resource Manager igi-lm 1404/tcp Infinite Graphics License Manager igi-lm 1404/udp Infinite Graphics License Manager ibm-res 1405/tcp IBM Remote Execution Starter ibm-res 1405/udp IBM Remote Execution Starter netlabs-lm 1406/tcp NetLabs License Manager netlabs-lm 1406/udp NetLabs License Manager dbsa-lm 1407/tcp DBSA License Manager dbsa-lm 1407/udp DBSA License Manager
sophia-lm 1408/tcp Sophia License Manager sophia-lm 1408/udp Sophia License Manager
here-lm 1409/tcp Here License Manager here-lm 1409/udp Here License Manager
hiq 1410/tcp HiQ License Manager hiq 1410/udp HiQ License Manager
af 1411/tcp AudioFile af 1411/udp AudioFile
innosys 1412/tcp InnoSys innosys 1412/udp InnoSys innosys-acl 1413/tcp Innosys-ACL innosys-acl 1413/udp Innosys-ACL
ibm-mqseries 1414/tcp IBM MQSeries ibm-mqseries 1414/udp IBM MQSeries
dbstar 1415/tcp DBStar dbstar 1415/udp DBStar
novell-lu6.2 1416/tcp Novell LU6.2 novell-lu6.2 1416/udp Novell LU6.2
timbuktu-srv1 1417/tcp Timbuktu Service 1 Port timbuktu-srv1 1417/tcp Timbuktu Service 1 Port timbuktu-srv2 1418/tcp Timbuktu Service 2 Port timbuktu-srv2 1418/udp Timbuktu Service 2 Port timbuktu-srv3 1419/tcp Timbuktu Service 3 Port timbuktu-srv3 1419/udp Timbuktu Service 3 Port timbuktu-srv4 1420/tcp Timbuktu Service 4 Port timbuktu-srv4 1420/udp Timbuktu Service 4 Port gandalf-lm 1421/tcp Gandalf License Manager gandalf-lm 1421/udp Gandalf License Manager
autodesk-lm 1422/tcp Autodesk License Manager autodesk-lm 1422/udp Autodesk License Manager
essbase 1423/tcp Essbase Arbor Software essbase 1423/udp Essbase Arbor Software hybrid 1424/tcp Hybrid Encryption Protocol hybrid 1424/udp Hybrid Encryption Protocol
zion-lm 1425/tcp Zion Software License Manager zion-lm 1425/udp Zion Software License Manager
sas-1 1426/tcp Satellite-data Acquisition System 1 sas-1 1426/udp Satellite-data Acquisition System 1
mloadd 1427/tcp mloadd monitoring tool mloadd 1427/udp mloadd monitoring tool informatik-lm 1428/tcp Informatik License Manager informatik-lm 1428/udp Informatik License Manager
nms 1429/tcp Hypercom NMS nms 1429/udp Hypercom NMS tpdu 1430/tcp Hypercom TPDU tpdu 1430/udp Hypercom TPDU
rgtp 1431/tcp Reverse Gosip Transport rgtp 1431/udp Reverse Gosip Transport blueberry-lm 1432/tcp Blueberry Software License Manager blueberry-lm 1432/udp Blueberry Software License Manager
ms-sql-s 1433/tcp Microsoft-SQL-Server ms-sql-s 1433/udp Microsoft-SQL-Server ms-sql-m 1434/tcp Microsoft-SQL-Monitor ms-sql-m 1434/udp Microsoft-SQL-Monitor
ibm-cics 1435/tcp IBM CISC ibm-cics 1435/udp IBM CISC
sas-2 1436/tcp Satellite-data Acquisition System 2 sas-2 1436/udp Satellite-data Acquisition System 2 tabula 1437/tcp Tabula tabula 1437/udp Tabula
eicon-server 1438/tcp Eicon Security Agent/Server eicon-server 1438/udp Eicon Security Agent/Server eicon-x25 1439/tcp Eicon X25/SNA Gateway eicon-x25 1439/udp Eicon X25/SNA Gateway eicon-slp 1440/tcp Eicon Service Location Protocol eicon-slp 1440/udp Eicon Service Location Protocol
cadis-1 1441/tcp Cadis License Management cadis-1 1441/udp Cadis License Management cadis-2 1442/tcp Cadis License Management cadis-2 1442/udp Cadis License Management
ies-lm 1443/tcp Integrated Engineering Software ies-lm 1443/udp Integrated Engineering Software
marcam-lm 1444/tcp Marcam License Management marcam-lm 1444/udp Marcam License Management
proxima-lm 1445/tcp Proxima License Manager proxima-lm 1445/udp Proxima License Manager ora-lm 1446/tcp Optical Research Associates License Manager ora-lm 1446/udp Optical Research Associates License Manager apri-lm 1447/tcp Applied Parallel Research LM apri-lm 1447/udp Applied Parallel Research LM
oc-lm 1448/tcp OpenConnect License Manager oc-lm 1448/udp OpenConnect License Manager
peport 1449/tcp PEport peport 1449/udp PEport
dwf 1450/tcp Tandem Distributed Workbench Facility dwf 1450/udp Tandem Distributed Workbench Facility
infoman 1451/tcp IBM Information Management infoman 1451/udp IBM Information Management
gtegsc-lm 1452/tcp GTE Government Systems License Man gtegsc-lm 1452/udp GTE Government Systems License Man
genie-lm 1453/tcp Genie License Manager genie-lm 1453/udp Genie License Manager
interhdl_elmd 1454/tcp interHDL License Manager interhdl_elmd 1454/tcp interHDL License Manager
esl-lm 1455/tcp ESL License Manager esl-lm 1455/udp ESL License Manager
dca 1456/tcp DCA dca 1456/udp DCA
valisys-lm 1457/tcp Valisys License Manager valisys-lm 1457/udp Valisys License Manager
nrcabq-lm 1458/tcp Nichols Research Corp. nrcabq-lm 1458/udp Nichols Research Corp.
proshare1 1459/tcp Proshare Notebook Application proshare1 1459/udp Proshare Notebook Application proshare2 1460/tcp Proshare Notebook Application proshare2 1460/udp Proshare Notebook Application
ibm_wrless_lan 1461/tcp IBM Wireless LAN ibm_wrless_lan 1461/udp IBM Wireless LAN world-lm 1462/tcp World License Manager world-lm 1462/udp World License Manager
nucleus 1463/tcp Nucleus nucleus 1463/udp Nucleus
msl_lmd 1464/tcp MSL License Manager msl_lmd 1464/udp MSL License Manager
pipes 1465/tcp Pipes Platform pipes 1465/udp Pipes Platform [email protected]
oceansoft-lm 1466/tcp Ocean Software License Manager oceansoft-lm 1466/udp Ocean Software License Manager
csdmbase 1467/tcp CSDMBASE csdmbase 1467/udp CSDMBASE csdm 1468/tcp CSDM csdm 1468/udp CSDM
aal-lm 1469/tcp Active Analysis Limited License Manager aal-lm 1469/udp Active Analysis Limited License Manager
uaiact 1470/tcp Universal Analytics uaiact 1470/udp Universal Analytics
csdmbase 1471/tcp csdmbase csdmbase 1471/udp csdmbase csdm 1472/tcp csdm csdm 1472/udp csdm openmath 1473/tcp OpenMath openmath 1473/udp OpenMath
telefinder 1474/tcp Telefinder telefinder 1474/udp Telefinder
taligent-lm 1475/tcp Taligent License Manager taligent-lm 1475/udp Taligent License Manager
clvm-cfg 1476/tcp clvm-cfg clvm-cfg 1476/udp clvm-cfg
ms-sna-server 1477/tcp ms-sna-server ms-sna-server 1477/udp ms-sna-server ms-sna-base 1478/tcp ms-sna-base ms-sna-base 1478/udp ms-sna-base
dberegister 1479/tcp dberegister dberegister 1479/udp dberegister
pacerforum 1480/tcp PacerForum pacerforum 1480/udp PacerForum
airs 1481/tcp AIRS airs 1481/udp AIRS
miteksys-lm 1482/tcp Miteksys License Manager miteksys-lm 1482/udp Miteksys License Manager
afs 1483/tcp AFS License Manager afs 1483/udp AFS License Manager
confluent 1484/tcp Confluent License Manager confluent 1484/udp Confluent License Manager
lansource 1485/tcp LANSource lansource 1485/udp LANSource
nms_topo_serv 1486/tcp nms_topo_serv nms_topo_serv 1486/udp nms_topo_serv
localinfosrvr 1487/tcp LocalInfoSrvr localinfosrvr 1487/udp LocalInfoSrvr
docstor 1488/tcp DocStor docstor 1488/udp DocStor
dmdocbroker 1489/tcp dmdocbroker dmdocbroker 1489/udp dmdocbroker
insitu-conf 1490/tcp insitu-conf insitu-conf 1490/udp insitu-conf
anynetgateway 1491/tcp anynetgateway anynetgateway 1491/udp anynetgateway
stone-design-1 1492/tcp stone-design-1 stone-design-1 1492/udp stone-design-1
netmap_lm 1493/tcp netmap_lm netmap_lm 1493/udp netmap_lm
ica 1494/tcp ica ica 1494/udp ica
cvc 1495/tcp cvc cvc 1495/udp cvc liberty-lm 1496/tcp liberty-lm liberty-lm 1496/udp liberty-lm
rfx-lm 1497/tcp rfx-lm rfx-lm 1497/udp rfx-lm
watcom-sql 1498/tcp Watcom-SQL watcom-sql 1498/udp Watcom-SQL
fhc 1499/tcp Federico Heinz Consultora fhc 1499/udp Federico Heinz Consultora
vlsi-lm 1500/tcp VLSI License Manager vlsi-lm 1500/udp VLSI License Manager
sas-3 1501/tcp Satellite-data Acquisition System 3 sas-3 1501/udp Satellite-data Acquisition System 3 shivadiscovery 1502/tcp Shiva shivadiscovery 1502/udp Shiva
imtc-mcs 1503/tcp Databeam imtc-mcs 1503/udp Databeam
evb-elm 1504/tcp EVB Software Engineering License Manager evb-elm 1504/udp EVB Software Engineering License Manager
funkproxy 1505/tcp Funk Software, Inc. funkproxy 1505/udp Funk Software, Inc.
ingreslock 1524/tcp ingres ingreslock 1524/udp ingres orasrv 1525/tcp oracle orasrv 1525/udp oracle prospero-np 1525/tcp Prospero Directory Service non-priv prospero-np 1525/udp Prospero Directory Service non-priv pdap-np 1526/tcp Prospero Data Access Prot non-priv pdap-np 1526/udp Prospero Data Access Prot non-priv tlisrv 1527/tcp oracle tlisrv 1527/udp oracle coauthor 1529/tcp oracle coauthor 1529/udp oracle issd 1600/tcp issd 1600/udp nkd 1650/tcp nkd 1650/udp proshareaudio 1651/tcp proshare conf audio proshareaudio 1651/udp proshare conf audio prosharevideo 1652/tcp proshare conf video prosharevideo 1652/udp proshare conf video prosharedata 1653/tcp proshare conf data prosharedata 1653/udp proshare conf data prosharerequest 1654/tcp proshare conf request prosharerequest 1654/udp proshare conf request prosharenotify 1655/tcp proshare conf notify prosharenotify 1655/udp proshare conf notify netview-aix-1 1661/tcp netview-aix-1 netview-aix-1 1661/udp netview-aix-1 netview-aix-2 1662/tcp netview-aix-2 netview-aix-2 1662/udp netview-aix-2 netview-aix-3 1663/tcp netview-aix-3 netview-aix-3 1663/udp netview-aix-3 netview-aix-4 1664/tcp netview-aix-4 netview-aix-4 1664/udp netview-aix-4 netview-aix-5 1665/tcp netview-aix-5 netview-aix-5 1665/udp netview-aix-5 netview-aix-6 1666/tcp netview-aix-6 netview-aix-6 1666/udp netview-aix-6
licensedaemon 1986/tcp cisco license management licensedaemon 1986/udp cisco license management tr-rsrb-p1 1987/tcp cisco RSRB Priority 1 port tr-rsrb-p1 1987/udp cisco RSRB Priority 1 port tr-rsrb-p2 1988/tcp cisco RSRB Priority 2 port tr-rsrb-p2 1988/udp cisco RSRB Priority 2 port tr-rsrb-p3 1989/tcp cisco RSRB Priority 3 port tr-rsrb-p3 1989/udp cisco RSRB Priority 3 port
mshnet 1989/tcp MHSnet system mshnet 1989/udp MHSnet system
stun-p1 1990/tcp cisco STUN Priority 1 port stun-p1 1990/udp cisco STUN Priority 1 port stun-p2 1991/tcp cisco STUN Priority 2 port stun-p2 1991/udp cisco STUN Priority 2 port stun-p3 1992/tcp cisco STUN Priority 3 port stun-p3 1992/udp cisco STUN Priority 3 port ipsendmsg 1992/tcp IPsendmsg ipsendmsg 1992/udp IPsendmsg snmp-tcp-port 1993/tcp cisco SNMP TCP port snmp-tcp-port 1993/udp cisco SNMP TCP port stun-port 1994/tcp cisco serial tunnel port stun-port 1994/udp cisco serial tunnel port perf-port 1995/tcp cisco perf port perf-port 1995/udp cisco perf port tr-rsrb-port 1996/tcp cisco Remote SRB port tr-rsrb-port 1996/udp cisco Remote SRB port gdp-port 1997/tcp cisco Gateway Discovery Protocol gdp-port 1997/udp cisco Gateway Discovery Protocol x25-svc-port 1998/tcp cisco X.25 service (XOT) x25-svc-port 1998/udp cisco X.25 service (XOT) tcp-id-port 1999/tcp cisco identification port tcp-id-port 1999/udp cisco identification port callbook 2000/tcp callbook 2000/udp dc 2001/tcp wizard 2001/udp curry globe 2002/tcp globe 2002/udp mailbox 2004/tcp emce 2004/udp CCWS mm conf berknet 2005/tcp oracle 2005/udp invokator 2006/tcp raid-cc 2006/udp raid dectalk 2007/tcp raid-am 2007/udp conf 2008/tcp terminaldb 2008/udp news 2009/tcp whosockami 2009/udp search 2010/tcp pipe_server 2010/udp raid-cc 2011/tcp raid servserv 2011/udp ttyinfo 2012/tcp raid-ac 2012/udp raid-am 2013/tcp raid-cd 2013/udp troff 2014/tcp raid-sf 2014/udp cypress 2015/tcp raid-cs 2015/udp bootserver 2016/tcp bootserver 2016/udp cypress-stat 2017/tcp bootclient 2017/udp terminaldb 2018/tcp rellpack 2018/udp whosockami 2019/tcp about 2019/udp xinupageserver 2020/tcp xinupageserver 2020/udp servexec 2021/tcp xinuexpansion1 2021/udp down 2022/tcp xinuexpansion2 2022/udp xinuexpansion3 2023/tcp xinuexpansion3 2023/udp xinuexpansion4 2024/tcp xinuexpansion4 2024/udp ellpack 2025/tcp xribs 2025/udp scrabble 2026/tcp scrabble 2026/udp shadowserver 2027/tcp shadowserver 2027/udp submitserver 2028/tcp submitserver 2028/udp device2 2030/tcp device2 2030/udp blackboard 2032/tcp blackboard 2032/udp glogger 2033/tcp glogger 2033/udp scoremgr 2034/tcp scoremgr 2034/udp imsldoc 2035/tcp imsldoc 2035/udp objectmanager 2038/tcp objectmanager 2038/udp lam 2040/tcp lam 2040/udp interbase 2041/tcp interbase 2041/udp isis 2042/tcp isis 2042/udp isis-bcast 2043/tcp isis-bcast 2043/udp rimsl 2044/tcp rimsl 2044/udp cdfunc 2045/tcp cdfunc 2045/udp sdfunc 2046/tcp sdfunc 2046/udp dls 2047/tcp dls 2047/udp dls-monitor 2048/tcp dls-monitor 2048/udp shilp 2049/tcp shilp 2049/udp dlsrpn 2065/tcp Data Link Switch Read Port Number dlsrpn 2065/udp Data Link Switch Read Port Number dlswpn 2067/tcp Data Link Switch Write Port Number dlswpn 2067/udp Data Link Switch Write Port Number ats 2201/tcp Advanced Training System Program ats 2201/udp Advanced Training System Program rtsserv 2500/tcp Resource Tracking system server rtsserv 2500/udp Resource Tracking system server rtsclient 2501/tcp Resource Tracking system client rtsclient 2501/udp Resource Tracking system client
hp-3000-telnet 2564/tcp HP 3000 NS/VT block mode telnet www-dev 2784/tcp world wide web - development www-dev 2784/udp world wide web - development NSWS 3049/tcp NSWS 3049/udp ccmail 3264/tcp cc:mail/lotus ccmail 3264/udp cc:mail/lotus dec-notes 3333/tcp DEC Notes dec-notes 3333/udp DEC Notes
mapper-nodemgr 3984/tcp MAPPER network node manager mapper-nodemgr 3984/udp MAPPER network node manager mapper-mapethd 3985/tcp MAPPER TCP/IP server mapper-mapethd 3985/udp MAPPER TCP/IP server mapper-ws_ethd 3986/tcp MAPPER workstation server mapper-ws_ethd 3986/udp MAPPER workstation server
bmap 3421/tcp Bull Apprise portmapper bmap 3421/udp Bull Apprise portmapper
udt_os 3900/tcp Unidata UDT OS udt_os 3900/udp Unidata UDT OS nuts_dem 4132/tcp NUTS Daemon nuts_dem 4132/udp NUTS Daemon nuts_bootp 4133/tcp NUTS Bootp Server nuts_bootp 4133/udp NUTS Bootp Server
unicall 4343/tcp UNICALL unicall 4343/udp UNICALL krb524 4444/tcp KRB524 krb524 4444/udp KRB524 rfa 4672/tcp remote file access server rfa 4672/udp remote file access server commplex-main 5000/tcp commplex-main 5000/udp commplex-link 5001/tcp commplex-link 5001/udp rfe 5002/tcp radio free ethernet rfe 5002/udp radio free ethernet telelpathstart 5010/tcp TelepathStart telelpathstart 5010/udp TelepathStart telelpathattack 5011/tcp TelepathAttack telelpathattack 5011/udp TelepathAttack
mmcc 5050/tcp multimedia conference control tool mmcc 5050/udp multimedia conference control tool rmonitor_secure 5145/tcp rmonitor_secure 5145/udp aol 5190/tcp America-Online aol 5190/udp America-Online
padl2sim 5236/tcp padl2sim 5236/udp hacl-hb 5300/tcp # HA cluster heartbeat hacl-hb 5300/udp # HA cluster heartbeat hacl-gs 5301/tcp # HA cluster general services hacl-gs 5301/udp # HA cluster general services hacl-cfg 5302/tcp # HA cluster configuration hacl-cfg 5302/udp # HA cluster configuration hacl-probe 5303/tcp # HA cluster probing hacl-probe 5303/udp # HA cluster probing hacl-local 5304/tcp hacl-local 5304/udp hacl-test 5305/tcp hacl-test 5305/udp x11 6000-6063/tcp X Window System x11 6000-6063/udp X Window System
sub-process 6111/tcp HP SoftBench Sub-Process Control sub-process 6111/udp HP SoftBench Sub-Process Control meta-corp 6141/tcp Meta Corporation License Manager meta-corp 6141/udp Meta Corporation License Manager
aspentec-lm 6142/tcp Aspen Technology License Manager aspentec-lm 6142/udp Aspen Technology License Manager
watershed-lm 6143/tcp Watershed License Manager watershed-lm 6143/udp Watershed License Manager statsci1-lm 6144/tcp StatSci License Manager - 1 statsci1-lm 6144/udp StatSci License Manager - 1 statsci2-lm 6145/tcp StatSci License Manager - 2 statsci2-lm 6145/udp StatSci License Manager - 2
lonewolf-lm 6146/tcp Lone Wolf Systems License Manager lonewolf-lm 6146/udp Lone Wolf Systems License Manager
montage-lm 6147/tcp Montage License Manager montage-lm 6147/udp Montage License Manager
xdsxdm 6558/udp xdsxdm 6558/tcp afs3-fileserver 7000/tcp file server itself afs3-fileserver 7000/udp file server itself afs3-callback 7001/tcp callbacks to cache managers afs3-callback 7001/udp callbacks to cache managers afs3-prserver 7002/tcp users & groups database afs3-prserver 7002/udp users & groups database afs3-vlserver 7003/tcp volume location database afs3-vlserver 7003/udp volume location database afs3-kaserver 7004/tcp AFS/Kerberos authentication service afs3-kaserver 7004/udp AFS/Kerberos authentication service afs3-volser 7005/tcp volume managment server afs3-volser 7005/udp volume managment server afs3-errors 7006/tcp error interpretation service afs3-errors 7006/udp error interpretation service afs3-bos 7007/tcp basic overseer process afs3-bos 7007/udp basic overseer process afs3-update 7008/tcp server-to-server updater afs3-update 7008/udp server-to-server updater afs3-rmtsys 7009/tcp remote cache manager service afs3-rmtsys 7009/udp remote cache manager service ups-onlinet 7010/tcp onlinet uninterruptable power supplies ups-onlinet 7010/udp onlinet uninterruptable power supplies
font-service 7100/tcp X Font Service font-service 7100/udp X Font Service fodms 7200/tcp FODMS FLIP fodms 7200/udp FODMS FLIP
man 9535/tcp man 9535/udp isode-dua 17007/tcp isode-dua 17007/udp RFC793 Postel, J., ed., "Transmission Control Protocol - DARPA URL = ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers INTERNET MULTICAST ADDRESSES Host Extensions for IP Multicasting RFC1112 specifies the extensions required of a host implementation of the Internet Protocol (IP) to support multicasting. Current addresses are listed below. 224.0.0.0 Base Address (Reserved) [RFC1112,JBP] 224.0.0.1 All Systems on this Subnet [RFC1112,JBP] 224.0.0.2 All Routers on this Subnet [JBP] 224.0.0.3 Unassigned [JBP] 224.0.0.4 DVMRP Routers [RFC1075,JBP] 224.0.0.5 OSPFIGP OSPFIGP All Routers [RFC1583,JXM1] 224.0.0.6 OSPFIGP OSPFIGP Designated Routers [RFC1583,JXM1] 224.0.0.7 ST Routers [RFC1190,KS14] 224.0.0.8 ST Hosts [RFC1190,KS14] 224.0.0.9 RIP2 Routers [GSM11] 224.0.0.10 IGRP Routers [Dino Farinacci] 224.0.0.11 Mobile-Agents [Bill Simpson] 224.0.0.12-224.0.0.255 Unassigned [JBP] 224.0.1.0 VMTP Managers Group [RFC1045,DRC3] 224.0.1.1 NTP Network Time Protocol [RFC1119,DLM1] 224.0.1.2 SGI-Dogfight [AXC] 224.0.1.3 Rwhod [SXD] 224.0.1.4 VNP [DRC3] 224.0.1.5 Artificial Horizons - Aviator [BXF] 224.0.1.6 NSS - Name Service Server [BXS2] 224.0.1.7 AUDIONEWS - Audio News Multicast [MXF2] 224.0.1.8 SUN NIS+ Information Service [CXM3] 224.0.1.9 MTP Multicast Transport Protocol [SXA] 224.0.1.10 IETF-1-LOW-AUDIO [SC3] 224.0.1.11 IETF-1-AUDIO [SC3] 224.0.1.12 IETF-1-VIDEO [SC3] 224.0.1.13 IETF-2-LOW-AUDIO [SC3] 224.0.1.14 IETF-2-AUDIO [SC3] 224.0.1.15 IETF-2-VIDEO [SC3] 224.0.1.16 MUSIC-SERVICE [Guido van Rossum] 224.0.1.17 SEANET-TELEMETRY [Andrew Maffei] 224.0.1.18 SEANET-IMAGE [Andrew Maffei] 224.0.1.19 MLOADD [Braden] 224.0.1.20 any private experiment [JBP] 224.0.1.21 DVMRP on MOSPF [John Moy] 224.0.1.22 SVRLOC < [email protected] > 224.0.1.23 XINGTV < [email protected] > 224.0.1.24 microsoft-ds < [email protected] > 224.0.1.25 nbc-pro < [email protected] > 224.0.1.26 nbc-pfn < [email protected] > 224.0.1.27-224.0.1.255 Unassigned [JBP] 224.0.2.1 "rwho" Group (BSD) (unofficial) [JBP] 224.0.2.2 SUN RPC PMAPPROC_CALLIT [BXE1] 224.0.3.000-224.0.3.255 RFE Generic Service [DXS3] 224.0.4.000-224.0.4.255 RFE Individual Conferences [DXS3] 224.0.5.000-224.0.5.127 CDPD Groups [Bob Brenner] 224.0.5.128-224.0.5.255 Unassigned [IANA] 224.0.6.000-224.0.6.127 Cornell ISIS Project [Tim Clark] 224.0.6.128-224.0.6.255 Unassigned [IANA] 224.1.0.0-224.1.255.255 ST Multicast Groups [RFC1190,KS14] 224.2.0.0-224.2.255.255 Multimedia Conference Calls [SC3] 224.252.0.0-224.255.255.255 DIS transient groups [Joel Snyder] 232.0.0.0-232.255.255.255 VMTP transient groups [RFC1045,DRC3] These addresses are listed in the Domain Name Service under MCAST.NET and 224.IN-ADDR.ARPA. Note that when used on an Ethernet or IEEE 802 network, the 23 low-order bits of the IP Multicast address are placed in the low-order 23 bits of the Ethernet or IEEE 802 net multicast address 1.0.94.0.0.0. See the next section on "IANA ETHERNET ADDRESS BLOCK". RFC1045 Cheriton, D., "VMTP: Versatile Message Transaction RFC1075 Waitzman, D., C. Partridge, and S. Deering "Distance Vector RFC1119 Mills, D., "Network Time Protocol (Version 1), Specification [AXC] Andrew Cherenson < [email protected] > [Bob Brenner] [Braden] Bob Braden < [email protected] [BXE1] Brendan Eic < [email protected] > [BXF] Bruce Factor < [email protected] > [BXS2] Bill Schilit < [email protected] > [CXM3] Chuck McManis < [email protected] > [Tim Clark] [DXS3] Daniel Steinber < [email protected] > [Dino Farinacci] [GSM11] Gary S. Malkin < [email protected] > [IANA] IANA < [email protected] > [JXM1] Jim Miner < [email protected] > [KS14] <mystery contact> [Andrew Maffei] [John Moy] John Moy < [email protected] > [MXF2] Martin Forssen < [email protected] > [Guido van Rossum] [SC3] Steve Casner < [email protected] > [Joel Snyder] URL = ftp://ftp.isi.edu/in-notes/iana/assignments/multicast-addresses SUN RPC NUMBERS To obtain SUN Remote Procedure Call (RPC) numbers send an e-mail request to " [email protected] ". The RPC port management service ('portmap' in SunOS versions less than
and 'rpcbind' in SunOS versions greater than 5.0) "registers" theIP port number that is allocated to a particular service when that service is created. It does not allocate ports on behalf of those services. For an exact specification of the semantics refer to the source code of svcudp_create() and svctcp_create() in the archives. In short however is that these interfaces, and svc_tli_create their Transport Independent RPC equivalent, take either a user specified port number or RPC_ANY (-1) which effectively means "I don't care." In the "I don't care" case the create code simply calls socket(2) or t_open(3n) which allocates an IP port based on the rules: Port numbers count up sequentially. Can a port that is "assigned" can be used when the assignee's service is not present? Say port 501 is assigned to the "jeans" service. On a machine that does not have the "jeans" service, nor has any clients that might be expecting to use it, is port 501 available for other uses? Any dynamic allocation process, like the portmapper, that chooses the next unused port might allocate port 501 dynamically to a process that asked for a "I don't care" port. So any dynamic allocation scheme may pick an unused port that happened to correspond to a port number that had been "assigned" but was currently unused. While it might be desirable, it is impossible to guarantee that any unused port, even though officially assigned to a service, is not picked by a dynamic allocator since such an assignment might occur long after the delivery of the system into a site that doesn't watch for the latest list. There is the restriction that only "superuser" on BSD derived systems such as SunOS can bind to a port number that is less than 1024. So programs have used this information in the past to identify whether or not the service they were talking to was started by the superuser on the remote system. Making this assumption is dangerous because not all system enforce this restriction. Sun RPC services use ports that are currently unused. If someone noted that an RPC service was using port 781, it would be just as happy using port 891, or 951. 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 service. The most common complaint comes when people put a new service on their system. When they configure their systems they put the new service configuration commands at the end of their system startup scripts. During startup, several network services may be started. Those services that are ONC/RPC based just pick the next available port, those that have pre-assigned ports bind to their pre-assigned port. Clearly the correct sequence is to have all services that need a particular port to be started first (or if they are "latent" services that are started by inetd, to have inetd started). Finally, the RPC services should be started as they will be assigned unused ports. (In the BSD networking code (which we use) the algorithm for picking ports is in the file in_pcb.c, function in_pcbbind().) Services should be started in this order: a) Services that will "run" continuously and have an assigned b) inetd - which will automatically create sockets for those c) RPC services - which will automatically pick unused ports and The include file /usr/include/netinet/in.h defines a constant IPPORT_RESERVED to be 1024. The relevant text is:
Portmap does not allocate ports, the kernel allocates ports. The code that does this is part of nearly every UNIX system in the world (and since the BSD code is 'free' it is often the same code). RPC services ask the kernel to allocate them a port by calling the "bind()" system call. The parameter they pass is "INADDR_ANY" which means "allocate me any IP port you want". The kernel does that by looking at all of the ports that are currently in use and picking one that is not currently used. The number picked is either less that 1024 if the process is privledged, or greater than 1024 if the process is not privledged. After the kernel has allocated a port, the service registers this allocation with portmap. The portmapper is merely a registry of previously allocated ports. Note "allocated" here is being used in the sense that they are used by an open socket, not assigned a well known name. The role of /etc/services is to provide an idea to people who are looking at network traffic as to where a packet may have originated from or is headed to. For services like finger that have assigned ports, they can just hard code the port they want into their executable. (it isn't like it will change, and if they read it from /etc/services and someone had mistyped the port number it won't interoperate with clients anyway!) It is not practical to read the /etc/services file into the kernel to prevent it from giving out port numbers that are "pre-assigned", nor is it generally desirable since with the correct ordering of startup it is completely unneccesary. Editors Note: This information was supplied by Chuck McManis of Sun. URL = ftp://ftp.isi.edu/in-notes/iana/assignments/sun-rpc-numbers IP OPTION NUMBERS The Internet Protocol (IP) has provision for optional header fields identified by an option type field. Options 0 and 1 are exactly one octet which is their type field. All other options have their one octet type field, followed by a one octet length field, followed by length-2 octets of option data. The option type field is sub-divided into a one bit copied flag, a two bit class field, and a five bit option number. These taken together form an eight bit value for the option type field. IP options are commonly refered to by this value. Copy Class Number Value Name Reference ----- ------ ----- ------------------------------- --------- 0 0 0 0 EOOL - End of Options List [RFC791,JBP] 0 0 1 1 NOP - No Operation [RFC791,JBP] 1 0 2 130 SEC - Security RFC1108 1 0 3 131 LSR - Loose Source Route [RFC791,JBP] 0 2 4 68 TS - Time Stamp [RFC791,JBP] 1 0 5 133 E-SEC - Extended Security RFC1108 1 0 6 134 CIPSO - Commercial Security [???] 0 0 7 7 RR - Record Route [RFC791,JBP] 1 0 8 136 SID - Stream ID [RFC791,JBP] 1 0 9 137 SSR - Strict Source Route [RFC791,JBP] 0 0 10 10 ZSU - Experimental Measurement [ZSu] 0 0 11 11 MTUP - MTU Probe RFC1191 0 0 12 12 MTUR - MTU Reply RFC1191 1 2 13 205 FINN - Experimental Flow Control [Finn] 1 0 14 142 VISA - Expermental Access Control [Estrin] 0 0 15 15 ENCODE - ??? [VerSteeg] 1 0 16 144 IMITD - IMI Traffic Descriptor [Lee] 1 0 17 145 EIP - ??? RFC1358 0 2 18 82 TR - Traceroute RFC1393 1 0 19 147 ADDEXT - Address Extension [Ullmann IPv7] IP TIME TO LIVE PARAMETER The current recommended default time to live (TTL) for the Internet Protocol (IP) [45,105] is 64. IP TOS PARAMETERS This documents the default Type-of-Service values that are currently recommended for the most important Internet protocols. TOS Value Description Reference -------------------------- --------- The TOS value is used to indicate "better". Only one TOS value or property can be requested in any one IP datagram. Generally, protocols which are involved in direct interaction with a human should select low delay, while data transfers which may involve large blocks of data are need high throughput. Finally, high reliability is most important for datagram-based Internet management functions. Application protocols not included in these tables should be able to make appropriate choice of low delay (8 decimal, 1000 binary) or high throughput (4 decimal, 0100 binary). The following are recommended values for TOS: Protocol TOS Value TELNET (1) 1000 (minimize delay) TFTP 1000 (minimize delay) Domain Name Service NNTP 0001 (minimize monetary cost) Any IGP 0010 (maximize reliability) SNMP 0010 (maximize reliability) (1) Includes all interactive user protocols (e.g., rlogin). (2) Includes all bulk data transfer protocols (e.g., rcp). (3) If the implementation does not support changing the TOS during the lifetime of the connection, then the recommended TOS on opening the connection is the default TOS (0000). (4) Although ICMP request messages are normally sent with the default TOS, there are sometimes good reasons why they would be sent with some other TOS value. An ICMP response always uses the same TOS value as was used in the corresponding ICMP request message. An application may (at the request of the user) substitute 0001 (minimize monetary cost) for any of the above values. RFC1108 Kent, S., "U.S. Department of Defense Security Options for RFC1191 Mogul, J., and S. Deering, "Path MTU Discovery", RFC 1191 , RFC1349 Almquist, P., "Type of Service in the Internet Protocol RFC1358 Chapin, L., Chair, "Charter of the Internet Architecture RFC1393 Malkin, G., "Traceroute Using an IP Option", RFC 1393 , RFC1455 Eastlake, D., "Physical Link Security Type of Service", [Ullmann IPv7] [Estrin] Deborah Estrin < [email protected] > [Finn] Greg Finn < [email protected] > [Ullmann] Robert Ullmann < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/ip-parameters ICMP TYPE NUMBERS The Internet Control Message Protocol (ICMP) has many messages that are identified by a "type" field. Type Name Reference ------------------------- --------- Many of these ICMP types have a "code" field. Here we list the types again with their assigned code fields. RFC792 Postel, J., "Internet Control Message Protocol", STD 5 , RFC950 Mogul, J., and J. Postel, "Internet Standard Subnetting RFC1256 Deering, S., Editor, "ICMP Router Discovery Messages", RFC RFC1475 Ullmann, R., "TP/IX: The Next Internet", RFC 1475 , Process [David Johnson] [Bill Simpson] < [email protected] > September, 1994. [ZSu] Zaw-Sing Su < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/icmp-parameters TCP OPTION NUMBERS 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. Kind Length Meaning Reference ------ ------------------------------- --------- TCP ALTERNATE CHECKSUM NUMBERS Number Description Reference ------------------------------- ---------- 0 TCP Checksum [RFC-1146] 1 8-bit Fletchers's algorithm [RFC-1146] 2 16-bit Fletchers's algorithm [RFC-1146] 3 Redundant Checksum Avoidance [Kay] [KAY] Kay, J. and Pasquale, J., "Measurement, Analysis, and RFC793 Postel, J., "Transmission Control Protocol - DARPA Internet RFC1323 Jacobson, V., Braden, R., and D. Borman, "TCP Extensions for RFC1072 Jacobson, V., and R. Braden, "TCP Extensions for Long-Delay RFC1693 ????? RFC1146 Zweig, J., and C. Partridge, "TCP Alternate Checksum [Braden] Bob Braden < [email protected] > [Knowles] Stev Knowles < [email protected] > [Kay] J. Kay < [email protected] > [Subbu & Monroe] <mystery contact> URL = ftp://ftp.isi.edu/in-notes/iana/assignments/tcp-parameters TELNET OPTIONS 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. Options Name References ----------------------- ---------- 0 Binary Transmission [RFC856,JBP] 1 Echo [RFC857,JBP] 2 Reconnection [NIC50005,JBP] 3 Suppress Go Ahead [RFC858,JBP] 4 Approx Message Size Negotiation [ETHERNET,JBP] 5 Status [RFC859,JBP] 6 Timing Mark [RFC860,JBP] 7 Remote Controlled Trans and Echo [RFC726,JBP] 8 Output Line Width [NIC50005,JBP] 9 Output Page Size [NIC50005,JBP] Telnet Authentication Types In RFC1409 , a list of authentication types is introduced. Additions to the list are registerd by the IANA and documented here. Type Description Reference [NIC50005] DDN Protocol Handbook, "Telnet Reconnection Option", RFC652 Crocker, D., "Telnet Output Carriage-Return Disposition RFC653 Crocker, D., "Telnet Output Horizontal Tabstops Option", RFC654 Crocker, D., "Telnet Output Horizontal Tab Disposition RFC655 Crocker, D., "Telnet Output Formfeed Disposition Option", RFC656 Crocker, D., "Telnet Output Vertical Tabstops Option", RFC657 Crocker, D., "Telnet Output Vertical Tab Disposition Option", RFC658 Crocker, D., "Telnet Output Linefeed Disposition", RFC 658 , RFC698 Tovar, "Telnet Extended ASCII Option", RFC 698 , Stanford RFC726 Postel, J. and D. Crocker, "Remote Controlled Transmission RFC727 Crispin, M., "Telnet Logout Option", RFC 727 , Stanford RFC734 Crispin, M., "SUPDUP Protocol", RFC 734 , Stanford, RFC735 Crocker, D. and R. Gumpertz, "Revised Telnet Byte Marco RFC736 Crispin, M., "Telnet SUPDUP Option", Stanford University-AI, RFC749 Greenberg, B., "Telnet SUPDUP-OUTPUT Option", RFC 749 , RFC779 Killian, E., "Telnet Send-Location Option", RFC 779 , RFC856 Postel, J. and J. Reynolds, "Telnet Binary Transmission", RFC857 Postel, J. and J. Reynolds, "Telnet Echo Option", STD 28 , RFC RFC858 Postel, J. and J. Reynolds, "Telnet Suppress Go Ahead RFC859 Postel, J. and J. Reynolds, "Telnet Status Option", STD 30 , RFC860 Postel, J. and J. Reynolds, "Telnet Timing Mark Option", RFC861 Postel, J. and J. Reynolds, "Telnet Extended Options - List RFC885 Postel, J., "Telnet End of Record Option", RFC 885 , RFC927 Anderson, B., "TACACS User Identification Telnet Option", RFC933 Silverman, S., "Output Marking Telnet Option", RFC 933 , RFC946 Nedved, R., "Telnet Terminal Location Number Option", [RDC1041] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041 , RFC1043 Yasuda, A., and T. Thompson, "TELNET Data Entry Terminal RFC1053 Levy, S., and T. Jacobson, "Telnet X.3 PAD Option", RFC1073 Waitzman, D., "Telnet Window Size Option", RFC 1073 , RFC1079 Hedrick, C., "Telnet Terminal Speed Option", RFC 1079 , RFC1091 VanBokkelen, J., "Telnet Terminal Type Option", RFC1096 Marcy, G., "Telnet X Display Location Option", RFC 1096 , RFC1184 Borman, D., Editor, "Telnet Linemode Option", RFC1372 Hedrick, C., and D. Borman, "Telnet Remote Flow Control RFC1408 Borman, D., Editor, "Telnet Environment Option", RFC 1408 , RFC1409 Borman, D., Editor, "Telnet Authentication Option", RFC RFC1572 Alexander, S., Editor, "Telnet Environment Option", RFC1572, RFC1647 Kelly, B., "TN3270 Enhancements", RFC1647, Auburn [BA4] Brian Anderson < [email protected] > [CLH3] Charles Hedrick < [email protected] > [DB14] Dave Borman < [email protected] > [DW183] David Waitzman < [email protected] > [EAK4] Earl Kill < [email protected] > [GM23] Glenn Marcy < [email protected] > [MRC] Mark Crispin < [email protected] > [MS56] Marvin Solomon < [email protected] > [RN6] Rudy Nedved <Rudy.Nedved@CMU-CS-A.> [Schoch] Steven Schoch < [email protected] > [SL70] Stuart Levy < [email protected] > [SXS] Steve Silverman < [email protected] > [YXR] Yakov Rekhter < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/telnet-options DOMAIN NAME SYSTEM PARAMETERS The Internet Domain Naming System (DOMAIN) includes several parameters. These are documented in RFC1034 and RFC1035 . The CLASS parameter is listed here. The per CLASS parameters are defined in separate RFCs as indicated. Domain System Parameters: Decimal Name References ---- ---------- 65535 Reserved [PM1] In the Internet (IN) class the following TYPEs and QTYPEs are defined: TYPE value and meaning A 1 a host address RFC1035 NS 2 an authoritative name server RFC1035 MD 3 a mail destination (Obsolete - use MX) RFC1035 MF 4 a mail forwarder (Obsolete - use MX) RFC1035 CNAME 5 the canonical name for an alias RFC1035 SOA 6 marks the start of a zone of authority RFC1035 MB 7 a mailbox domain name (EXPERIMENTAL) RFC1035 MG 8 a mail group member (EXPERIMENTAL) RFC1035 MR 9 a mail rename domain name (EXPERIMENTAL) RFC1035 NULL 10 a null RR (EXPERIMENTAL) RFC1035 WKS 11 a well known service description RFC1035 PTR 12 a domain name pointer RFC1035 HINFO 13 host information RFC1035 MINFO 14 mailbox or mail list information RFC1035 MX 15 mail exchange RFC1035 TXT 16 text strings RFC1035 RP 17 for Responsible Person RFC1183 AFSDB 18 for AFS Data Base location RFC1183 X25 19 for X.25 PSDN address RFC1183 ISDN 20 for ISDN address RFC1183 RT 21 for Route Through RFC1183 NSAP 22 for NSAP address, NSAP style A record RFC1348 NSAP-PTR 23 for domain name pointer, NSAP style RFC1348 SIG 24 for security signature [Donald Eastlake] KEY 25 for security key [Donald Eastlake] PX 26 X.400 mail mapping information RFC1664 GPOS 27 Geographical Position [Craig Farrell] AAAA 28 IP6 Address [Susan Thomson] AXFR 252 transfer of an entire zone RFC1035 MAILB 253 mailbox-related RRs (MB, MG or MR) RFC1035 MAILA 254 mail agent RRs (Obsolete - see MX) RFC1035
RFC1034 Mockapetris, P., "Domain Names - Concepts and RFC1035 Mockapetris, P., "Domain Names - Implementation and RFC1183 Everhart, C., Mamakos, L., Ullmann, R., and P. Mockapetris, RFC1348 Manning, B., "DNS NSAP RRs", RFC 1348 , Rice University, RFC1664 Allocchio, C., Bonito, A., Cole, B., Giordano, S., and R. [Susan Thomson] Susan Thomson < [email protected] > [PM1] Paul Mockapetris < [email protected] > [Donald Eastlake] Donald E. Eastlake, III < [email protected] > [Craig Farrell] URL = ftp://ftp.isi.edu/in-notes/iana/assignments/dns-parameters MAIL ENCODING HEADER FIELD KEYWORDS 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. Keyword Description Reference _______ ___________ ____________ EDIFACT EDIFACT format RFC1505 EDI-X12 EDI X12 format [ANSI-X12] EVFU FORTRAN format RFC1505 FS File System format RFC1505 Hex Hex binary format RFC1505 LZJU90 LZJU90 format RFC1505 LZW LZW format RFC1505 Message Encapsulated Message RFC822 PEM, PEM-Clear Privacy Enhanced Mail RFC1421 PGP Pretty Good Privacy RFC1505 Postscript Postscript format [POSTSCRIPT] Shar Shell Archive format RFC1505 Signature Signature RFC1505 Tar Tar format RFC1505 Text Text [IS-10646] uuencode uuencode format RFC1505 URL external URL-reference RFC1505 MAIL ENCRYPTION TYPES RFC822 specifies that Encryption Types for mail may be assigned. There are currently no RFC 822 encryption types assigned. Please use instead the Mail Privacy procedures defined in [RFC1421, RFC1422, RFC1423]. ESMTP MAIL KEYWORDS RFC1651 specifies that extension to SMTP can be identified with keywords. Keywords Description Reference -------------------------------- --------- SEND Send as mail RFC821 SOML Send as mail or terminal RFC821 SAML Send as mail and terminal RFC821 EXPN Expand the mailing list RFC821 HELP Supply helpful information RFC821 TURN Turn the operation around RFC821 8BITMIME Use 8-bit data RFC1652 SIZE Message size declaration RFC1653 VERB Verbose [Eric Allman] ONEX One message transaction only [Eric Allman] MAIL EXTENSION TYPES The Simple Mail Transfer Protocol RFC821 specifies a set of commands or services for mail transfer. A general procedure for extending the set of services is defined in RFC1651 . The set of service extensions is listed here. Service Ext EHLO Keyword Parameters Verb Reference ------------ ---------- ---------- --------- Send SEND none SEND RFC821 Send or Mail SOML none SOML RFC821 Send and Mail SAML none SAML RFC821 Expand EXPN none EXPN RFC821 Help HELP none HELP RFC821 Turn TURN none TURN RFC821 8 Bit MIME 8BITMIME none none RFC1652 Size SIZE number none RFC1653 MAIL SYSTEM NAMES In some places, an identification of other mail systems is used. One of these is in "The COSINE and Internet X.500 Schema" (section 9.3.18) RFC1274 . The mail system names listed here are used as the legal values in that schema under the "otherMailbox" attribute "mailboxType" type (which must be a PrintableString). Another place is in "Mapping between X.400(1988) / ISO 10021 and RFC 822" (section 4.2.2) RFC1327 . The names listed here are used as the legal values in that schema under the "std-or-address" attribute "registered-dd-type" type (which must be a "key-string"). Note that key-string = <a-z, A-Z, 0-9, and "-" >. Mail System Name Description Reference ------------------------------- --------- mcimail MCI Mail MAIL TRANSMISSION TYPES The Simple Mail Transfer Protocol RFC821 and the Standard for the Format of ARPA Internet Text Messages RFC822 specify that a set of "Received" lines will be prepended to the headers of electronic mail messages as they are transported through the Internet. These received line may optionally include either or both a "via" phrase and/or a "with" phrase. The legal values for the phrases are listed here. The via phrase is intended to indicate the link or physical medium over which the message was transferred. The with phrase is intended to indicate the protocol or logical process that was used to transfer the message. VIA link types Description Reference ---------------------------- --------- UUCP Unix-to-Unix Copy Program [???] WITH protocol types Description Reference SMTP Simple Mail Transfer Protocol RFC821 ESMTP SMTP with Service Extensions RFC1651 [POSTSCRIPT] Adobe Systems Inc., "PostScript Langpuage Reference Manual", 2nd Edition, 2nd Printing, January 1991. RFC821 Postel, J., "Simple Mail Transfer Protocol", STD 10 , RFC 821 , RFC822 Crocker, D., "Standard for the Format of ARPA-Internet Text RFC1274 Barker, P., and S. Kille, "The COSINE and Internet X.500 RFC1327 Hardcastle-Kille, S., "Mapping between X.400(1988) / ISO RFC1421 Linn, J., "Privacy Enhancement for Internet Electronic RFC1422 Kent, S., "Privacy Enhancement for Internet RFC1423 Balenson, D., "Privacy Enhancement for Internet Electronic RFC1505 Costanzo, A., Robinson, D., and R. Ullmann, "Encoding Header RFC1651 Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. RFC1652 Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. RFC1653 Klensin, J., Freed, N., and K. Moore, "SMTP Service [Eric Allman] URL = ftp://ftp.isi.edu/in-notes/iana/assignments/mail-parameters 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). BOOTP Vendor Extensions and DHCP Options are listed below: Tag Name Data Length Meaning --- ---- ----------- ------- 10 Impress Server N N/4 Impress Server addresses 11 RLP Server N N/4 RLP Server addresses 12 Hostname N Hostname string 13 Boot File Size 2 Size of boot file in 512 byte 14 Merit Dump File Client to dump and name 15 Domain Name N The DNS domain name of the 16 Swap Server N Swap Server addeess 17 Root Path N Path name for root disk 18 Extension File N Path name for more BOOTP info 19 Forward On/Off 1 Enable/Disable IP Forwarding 20 SrcRte On/Off 1 Enable/Disable Source Routing 21 Policy Filter N Routing Policy Filters 22 Max DG Assembly 2 Max Datagram Reassembly Size 23 Default IP TTL 1 Default IP Time to Live 24 MTU Timeout 4 Path MTU Aging Timeout 25 MTU Plateau N Path MTU Plateau Table 26 MTU Interface 2 Interface MTU Size 27 MTU Subnet 1 All Subnets are Local 28 Broadcast Address 4 Broadcast Address 29 Mask Discovery 1 Perform Mask Discovery 30 Mask Supplier 1 Provide Mask to Others 31 Router Discovery 1 Perform Router Discovery 32 Router Request 4 Router Solicitation Address 33 Static Route N Static Routing Table 34 Trailers 1 Trailer Encapsulation 35 ARP Timeout 4 ARP Cache Timeout 36 Ethernet 1 Ethernet Encapsulation 37 Default TCP TTL 1 Default TCP Time to Live 38 Keepalive Time 4 TCP Keepalive Interval 39 Keepalive Data 1 TCP Keepalive Garbage 40 NIS Domain N NIS Domain Name 41 NIS Servers N NIS Server Addresses 42 NTP Servers N NTP Server Addresses 43 Vendor Specific N Vendor Specific Information 44 NETBIOS Name Srv N NETBIOS Name Servers 45 NETBIOS Dist Srv N NETBIOS Datagram Distribution 46 NETBIOS Note Type 1 NETBIOS Note Type 47 NETBIOS Scope N NETBIOS Scope 48 X Window Font N X Window Font Server 49 X Window Manmager N X Window Display Manager 50 Address Request 4 Requested IP Address 51 Address Time 4 IP Address Lease Time 52 Overload 1 Overloaf "sname" or "file" 53 DHCP Msg Type 1 DHCP Message Type 54 DHCP Server Id 4 DHCP Server Identification 55 Parameter List N Parameter Request List 56 DHCP Message N DHCP Error Message 57 DHCP Max Msg Size 2 DHCP Maximum Message Size 58 Renewal Time 4 DHCP Renewal (T1) Time 59 Rebinding Time 4 DHCP Rebinding (T2) Time 60 Class Id N Class Identifier 61 Client Id N Client Identifier 62 Netware/IP Domain N Netware/IP Domain Name 63 Netware/IP Option N Netware/IP sub Options 64-127 Unassigned 128-154 Reserved 255 End 0 None RFC951 Croft, B., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)", RFC1531 Droms, R., "Dynamic Host Configuration Protocol", Bucknell RFC1533 Alexander, S., and R. Droms, "DHCP Options and BOOTP Vendor URL = ftp://ftp.isi.edu/in-notes/iana/assignments/bootp-and-dhcp- parameters ADDRESS FAMILY NUMBERS Several protocols deal with multiple address families. The 16-bit assignments are listed here. ---------------------------------------------------- --------- URL = ftp://ftp.isi.edu/in-notes/iana/assignments/address-family-numbers FOOBAR AF NUMBERS 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. Assigned FOOBAR Address Families Decimal Keyword Address Family References ------- -------------- ---------- 17-254 Unassigned 255 Reserved RFC1639 Piscitello, D., "FTP Operation Over Big Address Records URL = ftp://ftp.isi.edu/in-notes/iana/assignments/foobar-af-numbers DIRECTORY SYSTEM NAMES In the representation of distinquished names (and possibly other contexts) of the X.500 Directory system, several unique keywords may be necessary. For example, in the string representation of distinguished names RFC1485 . Keyword Attribute (X.520 keys) --------------------------------- RFC1485 Hardcastle-Kille, S., "A String Representation of URL = ftp://ftp.isi.edu/in-notes/iana/assignments/directory-system-names PUBLISHER IDENTIFICATION CODE The RFC "A Format for E-Mailing Bibliographic Records" RFC1357 establishs a "publisher-ID" code. The IANA registry of these codes is listed here. Code Publisher Reference ------------------------------------------------------- --------- DUMMY for testing only RFC1357 TEST for testing only RFC1357 ISI Information Sciences Institute [JBP] UMCS University of Manchester Computer Science Department [TXC] RFC1357 Cohen, D., Editor, "A Format for E-mailing Bibliographic [TXC] Tim Clement < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/publisher-id OSPF AUTHENTICATION CODES The Open Shotrest 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. Code Authentication Method Reference --------------------- --------- 0 No Authentication RFC1583 1 Simple Password Authentication RFC1583 2-65535 Reserved RFC1583 Moy, J., "OSPF Version 2", RFC 1583 , Proteon, Inc., March RFC1584 Moy, J., "Multicast Extensions to OSPF", RFC 1584 , Proteon, RFC1585 Moy, J., "MOSPF: Analysis and Experience", RFC 1585 , RFC1586 deSouza, O., and M. Rodrigues, "Guidelines for Running OSPF RFC1587 Coltun, R., and V. Fuller, "The OSPF NSSA Option", RFC 1587 , URL = ftp://ftp.isi.edu/in-notes/iana/assignments/ospf-authentication- codes MEDIA TYPES RFC1521 specifies that Content Types, Content Subtypes, Character Sets, Access Types, and Conversion values for MIME mail will be assigned and listed by the IANA. Content Types and Subtypes Type Subtype Description Reference ------- ----------- --------- text plain [RFC1521,NSB] multipart mixed [RFC1521,NSB] message rfc822 [RFC1521,NSB] application octet-stream [RFC1521,NSB] image jpeg [RFC1521,NSB] audio basic [RFC1521,NSB] video mpeg [RFC1521,NSB] The "media-types" directory contains a subdirectory for each content type and each of those directories contains a file for each content subtype. URL = ftp://ftp.isi.edu/in-notes/iana/assignments/media-types Character Sets All of the character sets listed the section on Character Sets are registered for use with MIME as MIME Character Sets. The correspondance between the few character sets listed in the MIME specification RFC1521 and the list in that section are: ----------- --------- US-ASCII see ANSI_X3.4-1968 below [RFC1521,NSB] ISO-8859-1 see ISO_8859-1:1987 below [RFC1521,NSB] ISO-8859-2 see ISO_8859-2:1987 below [RFC1521,NSB] ISO-8859-3 see ISO_8859-3:1988 below [RFC1521,NSB] ISO-8859-4 see ISO_8859-4:1988 below [RFC1521,NSB] ISO-8859-5 see ISO_8859-5:1988 below [RFC1521,NSB] ISO-8859-6 see ISO_8859-6:1987 below [RFC1521,NSB] ISO-8859-7 see ISO_8859-7:1987 below [RFC1521,NSB] ISO-8859-8 see ISO_8859-8:1988 below [RFC1521,NSB] ISO-8859-9 see ISO_8859-9:1989 below [RFC1521,NSB] Access Types FTP [RFC1521,NSB] ANON-FTP [RFC1521,NSB] TFTP [RFC1521,NSB] AFS [RFC1521,NSB] LOCAL-FILE [RFC1521,NSB] MAIL-SERVER [RFC1521,NSB] Conversion Values Conversion values or Content Transfer Encodings. 7BIT [RFC1521,NSB] 8BIT [RFC1521,NSB] BASE64 [RFC1521,NSB] BINARY [RFC1521,NSB] QUOTED-PRINTABLE [RFC1521,NSB] MIME / X.400 MAPPING TABLES MIME to X.400 Table X.400 to MIME Table [MacMime] Work in Progress. RFC1036 Horton, M., and R. Adams, "Standard for Interchange of RFC1494 Alvestrand, H., and S. Thompson, "Equivalences between 1988 RFC1521 Borenstien, N., and N. Freed, "MIME (Multipurpose Internet [Larry Campbell] [Dave Crocker] Dave Crocker < [email protected] > [Terry Crowley] [NSB] Nathaniel Borenstein < [email protected] > [MTR] Marshall Rose < [email protected] > [Paul Lindner] [PXF] Patrik Faltstrom < [email protected] > [Ehud Shapiro] [Henry Spencer] URL = ftp://ftp.isi.edu/in-notes/iana/assignments/media-types/media- types CHARACTER SETS These are the official names for character sets that may be used in the Internet and may be referred to in Internet documentation. These names are expressed in ANSI_X3.4-1968 which is commonly called US-ASCII or simply ASCII. The character set most commonly use in the Internet and used especially in protocol standards is US-ASCII, this is strongly encouraged. The use of the name US-ASCII is also encouraged. The character set names may be up to 40 characters taken from the printable characters of US-ASCII. However, no distinction is made between use of upper and lower case letters. Character Set Reference Name: ANSI_X3.4-1968 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-6 Alias: ANSI_X3.4-1986 Alias: ISO_646.irv:1991 Alias: ASCII Alias: ISO646-US Alias: US-ASCII Alias: us Alias: IBM367 Alias: cp367 Name: ISO-10646-UCS-2 Source: the 2-octet Basic Multilingual Plane, aka Unicode Name: ISO-10646-UCS-4 Source: the full code space. (same comment about byte order, Name: ISO-10646-UTF-1 Source: Universal Transfer Format (1), this is the multibyte Name: ISO_646.basic:1983 [RFC1345,KXS2] Source: ECMA registry Alias: ref Name: INVARIANT [RFC1345,KXS2] Name: ISO_646.irv:1983 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-2 Alias: irv Name: BS_4730 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-4 Alias: ISO646-GB Alias: gb Alias: uk Name: NATS-SEFI [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-8-1 Name: NATS-SEFI-ADD [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-8-2 Name: NATS-DANO [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-9-1 Name: NATS-DANO-ADD [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-9-2 Name: SEN_850200_B [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-10 Alias: FI Alias: ISO646-FI Alias: ISO646-SE Alias: se Name: SEN_850200_C [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-11 Alias: ISO646-SE2 Alias: se2 Name: KS_C_5601-1987 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-149 Alias: KS_C_5601-1989 Alias: KSC_5601 Alias: korean Name: ISO-2022-KR [RFC1557,Choi] Source: RFC-1557 (see also KS_C_5601-1987) Name: EUC-KR [RFC1557,Choi] Source: RFC-1557 (see also KS_C_5861-1992) Name: ISO-2022-JP [RFC1468,Murai] Source: RFC-1468 Name: ISO-2022-JP-2 [RFC1554,Ohta] Source: RFC-1554 Name: JIS_C6220-1969-jp [RFC1345,KXS2] Source: ECMA registry Alias: JIS_C6220-1969 Alias: iso-ir-13 Alias: katakana Alias: x0201-7 Name: JIS_C6220-1969-ro [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-14 Alias: jp Alias: ISO646-JP Name: IT [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-15 Alias: ISO646-IT Name: PT [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-16 Alias: ISO646-PT Name: ES [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-17 Alias: ISO646-ES Name: greek7-old [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-18 Name: latin-greek [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-19 Name: DIN_66003 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-21 Alias: de Alias: ISO646-DE Name: NF_Z_62-010_(1973) [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-25 Alias: ISO646-FR1 Name: Latin-greek-1 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-27 Name: ISO_5427 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-37 Name: JIS_C6226-1978 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-42 Name: BS_viewdata [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-47 Name: INIS [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-49 Name: INIS-8 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-50 Name: INIS-cyrillic [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-51 Name: ISO_5427:1981 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-54 Name: ISO_5428:1980 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-55 Name: GB_1988-80 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-57 Alias: cn Alias: ISO646-CN Name: GB_2312-80 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-58 Alias: chinese Name: NS_4551-1 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-60 Alias: ISO646-NO Alias: no Name: NS_4551-2 [RFC1345,KXS2] Source: ECMA registry Alias: ISO646-NO2 Alias: iso-ir-61 Alias: no2 Name: NF_Z_62-010 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-69 Alias: ISO646-FR Alias: fr Name: videotex-suppl [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-70 Name: PT2 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-84 Alias: ISO646-PT2 Name: ES2 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-85 Alias: ISO646-ES2 Name: MSZ_7795.3 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-86 Alias: ISO646-HU Alias: hu Name: JIS_C6226-1983 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-87 Alias: x0208 Alias: JIS_X0208-1983 Name: greek7 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-88 Name: ASMO_449 [RFC1345,KXS2] Source: ECMA registry Alias: ISO_9036 Alias: arabic7 Alias: iso-ir-89 Name: iso-ir-90 [RFC1345,KXS2] Source: ECMA registry Name: JIS_C6229-1984-a [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-91 Alias: jp-ocr-a Name: JIS_C6229-1984-b [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-92 Alias: ISO646-JP-OCR-B Alias: jp-ocr-b Name: JIS_C6229-1984-b-add [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-93 Alias: jp-ocr-b-add Name: JIS_C6229-1984-hand [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-94 Alias: jp-ocr-hand Name: JIS_C6229-1984-hand-add [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-95 Alias: jp-ocr-hand-add Name: JIS_C6229-1984-kana [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-96 Name: ISO_2033-1983 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-98 Alias: e13b Name: ANSI_X3.110-1983 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-99 Alias: CSA_T500-1983 Alias: NAPLPS Name: ISO_8859-1:1987 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-100 Alias: ISO_8859-1 Alias: ISO-8859-1 Alias: latin1 Alias: l1 Alias: IBM819 Alias: CP819 Name: ISO_8859-2:1987 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-101 Alias: ISO_8859-2 Alias: ISO-8859-2 Alias: latin2 Alias: l2 Name: T.61-7bit [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-102 Name: T.61-8bit [RFC1345,KXS2] Alias: T.61 Source: ECMA registry Alias: iso-ir-103 Name: ISO_8859-3:1988 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-109 Alias: ISO_8859-3 Alias: ISO-8859-3 Alias: latin3 Name: ISO_8859-4:1988 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-110 Alias: ISO_8859-4 Alias: ISO-8859-4 Alias: latin4 Alias: l4 Name: ECMA-cyrillic [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-111 Name: CSA_Z243.4-1985-1 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-121 Alias: ISO646-CA Alias: csa7-1 Alias: ca Name: CSA_Z243.4-1985-2 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-122 Alias: ISO646-CA2 Alias: csa7-2 Name: CSA_Z243.4-1985-gr [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-123 Name: ISO_8859-6:1987 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-127 Alias: ISO_8859-6 Alias: ISO-8859-6 Alias: ECMA-114 Alias: ASMO-708 Alias: arabic Name: ISO_8859-6-E [RFC1556,IANA] Source: RFC-1556 Name: ISO_8859-6-I [RFC1556,IANA] Source: RFC-1556 Name: ISO_8859-7:1987 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-126 Alias: ISO_8859-7 Alias: ISO-8859-7 Alias: ELOT_928 Alias: ECMA-118 Alias: greek Alias: greek8 Name: T.101-G2 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-128 Name: ISO_8859-8:1988 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-138 Alias: ISO_8859-8 Alias: ISO-8859-8 Alias: hebrew Name: ISO_8859-8-E [RFC1556,Nussbacher] Source: RFC-1556 Name: ISO_8859-8-I [RFC1556,Nussbacher] Source: RFC-1556 Name: CSN_369103 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-139 Name: JUS_I.B1.002 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-141 Alias: ISO646-YU Alias: js Alias: yu Name: ISO_6937-2-add [RFC1345,KXS2] Source: ECMA registry and ISO 6937-2:1983 Alias: iso-ir-142 Name: IEC_P27-1 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-143 Name: ISO_8859-5:1988 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-144 Alias: ISO_8859-5 Alias: ISO-8859-5 Alias: cyrillic Name: JUS_I.B1.003-serb [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-146 Alias: serbian Name: JUS_I.B1.003-mac [RFC1345,KXS2] Source: ECMA registry Alias: macedonian Alias: iso-ir-147 Name: ISO_8859-9:1989 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-148 Alias: ISO_8859-9 Alias: ISO-8859-9 Alias: latin5 Alias: l5 Name: greek-ccitt [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-150 Name: NC_NC00-10:81 [RFC1345,KXS2] Source: ECMA registry Alias: cuba Alias: iso-ir-151 Alias: ISO646-CU Name: ISO_6937-2-25 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-152 Name: GOST_19768-74 [RFC1345,KXS2] Source: ECMA registry Alias: ST_SEV_358-88 Alias: iso-ir-153 Name: ISO_8859-supp [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-154 Alias: latin1-2-5 Name: ISO_10367-box [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-155 Name: latin6 [RFC1345,KXS2] Source: ECMA registry Alias: iso-ir-157 Alias: l6 Name: latin-lap [RFC1345,KXS2] Source: ECMA registry Alias: lap Alias: iso-ir-158 Name: JIS_X0212-1990 [RFC1345,KXS2] Source: ECMA registry Alias: x0212 Alias: iso-ir-159 Name: DS_2089 [RFC1345,KXS2] Source: Danish Standard, DS 2089, February 1974 Alias: DS2089 Alias: ISO646-DK Alias: dk Name: us-dk [RFC1345,KXS2] Name: dk-us [RFC1345,KXS2] Name: JIS_X0201 [RFC1345,KXS2] Alias: X0201 Name: KSC5636 [RFC1345,KXS2] Alias: ISO646-KR Name: DEC-MCS [RFC1345,KXS2] Source: VAX/VMS User's Manual, Name: hp-roman8 [RFC1345,KXS2] Source: LaserJet IIP Printer User's Manual, Alias: roman8 Alias: r8 Name: macintosh [RFC1345,KXS2] Source: The Unicode Standard ver1.0, ISBN 0-201-56788-1, Oct 1991 Alias: mac Name: IBM037 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp037 Alias: ebcdic-cp-us Alias: ebcdic-cp-ca Alias: ebcdic-cp-wt Alias: ebcdic-cp-nl Name: IBM038 [RFC1345,KXS2] Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990 Alias: EBCDIC-INT Alias: cp038 Name: IBM273 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP273 Name: IBM274 [RFC1345,KXS2] Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990 Alias: EBCDIC-BE Alias: CP274 Name: IBM275 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: EBCDIC-BR Alias: cp275 Name: IBM277 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: EBCDIC-CP-DK Alias: EBCDIC-CP-NO Name: IBM278 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP278 Alias: ebcdic-cp-fi Alias: ebcdic-cp-se Name: IBM280 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP280 Alias: ebcdic-cp-it Name: IBM281 [RFC1345,KXS2] Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990 Alias: EBCDIC-JP-E Alias: cp281 Name: IBM284 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP284 Alias: ebcdic-cp-es Name: IBM285 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP285 Alias: ebcdic-cp-gb Name: IBM290 [RFC1345,KXS2] Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990 Alias: cp290 Alias: EBCDIC-JP-kana Name: IBM297 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp297 Alias: ebcdic-cp-fr Name: IBM420 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990, Alias: cp420 Alias: ebcdic-cp-ar1 Name: IBM423 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp423 Alias: ebcdic-cp-gr Name: IBM424 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp424 Alias: ebcdic-cp-he Name: IBM437 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp437 Alias: 437 Name: IBM500 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP500 Alias: ebcdic-cp-be Alias: ebcdic-cp-ch Name: IBM850 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp850 Name: IBM851 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp851 Alias: 851 Name: IBM852 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp852 Alias: 852 Name: IBM855 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp855 Alias: 855 Name: IBM857 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp857 Alias: 857 Name: IBM860 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp860 Alias: 860 Name: IBM861 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp861 Alias: 861 Alias: cp-is Name: IBM862 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp862 Alias: 862 Name: IBM863 [RFC1345,KXS2] Source: IBM Keyboard layouts and code pages, PN 07G4586 June 1991 Alias: cp863 Alias: 863 Name: IBM864 [RFC1345,KXS2] Source: IBM Keyboard layouts and code pages, PN 07G4586 June 1991 Alias: cp864 Name: IBM865 [RFC1345,KXS2] Source: IBM DOS 3.3 Ref (Abridged), 94X9575 (Feb 1987) Alias: cp865 Alias: 865 Name: IBM868 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP868 Alias: cp-ar Name: IBM869 [RFC1345,KXS2] Source: IBM Keyboard layouts and code pages, PN 07G4586 June 1991 Alias: cp869 Alias: 869 Alias: cp-gr Name: IBM870 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP870 Alias: ebcdic-cp-roece Alias: ebcdic-cp-yu Name: IBM871 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP871 Alias: ebcdic-cp-is Name: IBM880 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp880 Alias: EBCDIC-Cyrillic Name: IBM891 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp891 Name: IBM903 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp903 Name: IBM904 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: cp904 Alias: 904 Name: IBM905 [RFC1345,KXS2] Source: IBM 3174 Character Set Ref, GA27-3831-02, March 1990 Alias: CP905 Alias: ebcdic-cp-tr Name: IBM918 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP918 Alias: ebcdic-cp-ar2 Name: IBM1026 [RFC1345,KXS2] Source: IBM NLS RM Vol2 SE09-8002-01, March 1990 Alias: CP1026 Name: EBCDIC-AT-DE [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-AT-DE-A [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-CA-FR [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-DK-NO [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-DK-NO-A [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-FI-SE [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-FI-SE-A [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-FR [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-IT [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-PT [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-ES [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-ES-A [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-ES-S [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-UK [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: EBCDIC-US [RFC1345,KXS2] Source: IBM 3270 Char Set Ref Ch 10, GA27-2837-9, April 1987 Name: UNKNOWN-8BIT RFC1428 Name: MNEMONIC [RFC1345,KXS2] Source: RFC 1345 , also known as "mnemonic+ascii+38" Name: MNEM [RFC1345,KXS2] Source: RFC 1345 , also known as "mnemonic+ascii+8200" Name: VISCII RFC1456 Source: RFC 1456 Name: VIQR RFC1456 Source: RFC 1456 Name: KOI8-R RFC1489 Source: RFC 1489 , based on GOST-19768-74, ISO-6937/8, Name: UNICODE-1-1 RFC1641 Source: RFC 1641 Name: UNICODE-1-1-UTF-7 RFC1642 Source: RFC 1642 RFC1345 Simonsen, K., "Character Mnemonics & Character Sets", RFC1428 Vaudreuil, G., "Transition of Internet Mail from RFC1456 Vietnamese Standardization Working Group, "Conventions for RFC1468 Murai, J., Crispin, M., and E. van der Poel, "Japanese RFC1489 Chernov, A., "Registration of a Cyrillic Character Set", RFC1554 Ohta, M., and K. Handa, "ISO-2022-JP-2: Multilingual RFC1556 Nussbacher, H., "Handling of Bi-directional Texts in MIME", RFC1557 Choi, U., Chon, K., and H. Park, "Korean Character Encoding RFC1641 Goldsmith, D., and M. Davis, "Using Unicode with MIME", RFC1642 Goldsmith, D., and M. Davis, "UTF-7", RFC1642, Taligent, [KXS2] Keld Simonsen < [email protected] > [Choi] Uhhyung Choi < [email protected] > [Murai] Jun Murai < [email protected] > [Ohta] Masataka Ohta < [email protected] > [Nussbacher] Hank Nussbacher < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets 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 data structure is the "Structure and Indentification of Management Information for TCP/IP-based Internets" (SMI) RFC1155 , and the "Management Information Base for Network Management of TCP/IP-based Internets" (MIB-II) RFC1213 . The SMI includes the provision for panrameters or codes to indicate experimental or private data structures. These parameter assignments are listed here. The older "Simple Gateway Monitoring Protocol" (SGMP) RFC1028 also defined a data structure. The parameter assignments used with SGMP are included here for historical completeness. The network management object identifiers are under the iso (1), org (3), dod (6), internet (1), or 1.3.6.1, branch of the name space. The major branches are: 1.3.6.1.1 directory 1.3.6.1.2 mgmt 1.3.6.1.2.1 mib-2 1.3.6.1.2.1.2.2.1.3 ifType 1.3.6.1.2.1.10 transmission 1.3.6.1.2.1.10.23 transmission.ppp 1.3.6.1.2.1.27 application 1.3.6.1.2.1.28 mta 1.3.6.1.3 experimental 1.3.6.1.4 private 1.3.6.1.4.1 enterprise 1.3.6.1.5 security 1.3.6.1.6 SNMPv2 1.3.6.1.7 mail SMI Network Management Directory Codes: Prefix: iso.org.dod.internet.directory (1.3.6.1.1.) Decimal Name Description References ---- ----------- ---------- SMI Network Management MGMT Codes: Prefix: iso.org.dod.internet.mgmt (1.3.6.1.2.) Prefix: iso.org.dod.internet.mgmt.mib-2 (1.3.6.1.2.1) -- [RFC1229,RFC1239,KZM] Prefix: iso.org.dod.internet.mgmt.mib-2.interface (1.3.6.1.2.1.2) (1.3.6.1.2.1.2.2.1.3) ifType definitions Decimal Name Description ---- ----------- -- [RFC1230,RFC1239,KZM] -- [RFC1231,RFC1239,KZM] Prefix: iso.org.dod.internet.mgmt.mib-2.transmission (1.3.6.1.2.1.10) (1.3.6.1.2.1.10.23) Prefix: iso.org.dod.internet.mgmt.mib-2.application (1.3.6.1.2.1.27) (1.3.6.1.2.1.27.2.1.3) assocApplicationProtocol OBJECT-TYPE (1.3.6.1.2.1.27.3) (1.3.6.1.2.1.27.4) -- OIDs of the form {applTCPProtoID port} are intended to be used -- for TCP-based protocols that don't have OIDs assigned by other -- means. {applUDPProtoID port} serves the same purpose for -- UDP-based protocols. In either case 'port' corresponds to -- the primary port number being used by the protocol. For example, -- assuming no other OID is assigned for SMTP, an OID of -- {applTCPProtoID 25} could be used, since SMTP is a TCP-based -- protocol that uses port 25 as its primary port. Prefix: iso.org.dod.internet.mgmt.mib-2.mta (1.3.6.1.2.1.28) (1.3.6.1.2.1.28.2.1.24) mtaGroupMailProtocol OBJECT-TYPE SMI Network Management Experimental Codes: Prefix: iso.org.dod.internet.experimental (1.3.6.1.3.)
SMI Private Codes: Prefix: iso.org.dod.internet.private (1.3.6.1.4) SMI Private Enterprise Codes: Prefix: iso.org.dod.internet.private.enterprise (1.3.6.1.4.1) See the file "enterprise-numbers". SMI Security Codes: Prefix: iso.org.dod.internet.security (1.3.6.1.5) SMI SNMPv2 Codes: Prefix: iso.org.dod.internet.snmpv2 (1.3.6.1.6) SMI mail Codes: Prefix: iso.org.dod.internet.mail (1.3.6.1.7) [1] Miller, S.P., B.C. Neuman, J.I. Schiller, and J.H. Saltzer, [2] Kohl, J., and B.C. Neuman, "The Kerberos Network RFC1028 Davin, J., J. Case, M. Fedor, and M. Schoffstall, "A Simple RFC1095 Warrier, U., and L. Besaw, "The Common Management RFC1155 Rose, M., and K. McCloghrie, "Structure and Identification RFC1157 Case, J., M. Fedor, M. Schoffstall, and J. Davin, RFC1213 McCloghrie, K., and M. Rose, "Management Information Base RFC1229 McCloghrie, K., Editor, "Extensions to the Generic-Interface RFC1230 McCloghrie, K., and R. Fox, "IEEE 802.4 Token Bus MIB", RFC1231 McCloghrie, K., Fox, R., and E. Decker, "IEEE 802.5 Token RFC1239 Reynolds, J., "Reassignment of Experimental MIBs to RFC1243 Waldbusser, S., Editor, "AppleTalk Management Information RFC1253 Baker, F., and R. Coltun, "OSPF Version 2 Management RFC1271 Waldbusser, S., "Remote Network Monitoring Management RFC1284 Cook, J., Editor, "Definitions of Managed Objects RFC1285 Case, J., "FDDI Management Information Base", RFC 1285 , RFC1286 Decker, E., Langille, P., Rijsinghani, A., and K. RFC1304 Cox, T., and K. Tesnik, Editors, "Definitions of Managed RFC1315 Brown, C., Baker, F., and C. Carvalho, "Management RFC1353 McCloghrie, K., Davin, J., and J. Galvin, "Definitions of RFC1381 Throop, D., and F. Baker, "SNMP MIB Extension for X.25 RFC1382 Throop, D., Editor, "SNMP MIB Extension for the X.25 Packet RFC1389 Malkin, G., and F. Baker, "RIP Version 2 MIB Extension", RFC RFC1406 Baker, F., and J. Watt, Editors, "Definitions of Managed RFC1407 Cox, T., and K. Tesink, "Definitions of Managed Objects RFC1414 St. Johns, M., and M. Rose, "Identification MIB", RFC 1414 , RFC1461 Throop, D., "SNMP MIB extension for Multiprotocol RFC1471 Kastenholz, F., "The Definitions of Managed Objects for RFC1472 Kastenholz, F., "The Definitions of Managed Objects for RFC1473 Kastenholz, F., "The Definitions of Managed Objects for RFC1474 Kastenholz, F., "The Definitions of Managed Objects for RFC1514 Grillo, P., and S. Waldbusser, "Host Resources MIB", RFC RFC1515 McMaster, D., McCloghrie, K., and S. Roberts, "Definitions RFC1516 McMaster, D., and K. McCloghrie, "Definitions of Managed RFC1559 Saperia, J., "DECnet Phase IV MIB Extensions", RFC 1559 , RFC1565 Kille, S., WG Chair, and N. Freed, Editor, "Network Services RFC1566 Kille, S., WG Chair, and N. Freed, Editor, "Mail Monitoring RFC1567 Mansfield, G., and S. Kille, "X.500 Directory Monitoring RFC1573 McCloghrie, K., and F. Kastenholz, "Evolution of the RFC1595 Brown, T., and K. Tesink, Editors, "Definitions of Managed RFC1596 Brown, T., Editor, Definitions of Managed Objects for Frame RFC1611 Austein, R., and J. Saperia, "DNS Server MIB Extensions", RFC1628 Case, J., Editor, "UPS Management Information Base", RFC RFC1650 Kastenholz, F., "Definitions of Managed Objects for RFC1657 Willis, S., Burruss, J., and J. Chu, Editor, "Definitions of RFC1658 Stewart, B., "Definitions of Managed Objects for Character RFC1659 Stewart, B., "Definitions of Managed Objects for RS-232-like RFC1660 Stewart, B., "Definitions of Managed Objects for RFC1665 Kielczewski, Z., Kostick, D., and K. Shih, Editors, RFC1694 Brown, T., and K. Tesink, Editors, "Definitions of Managed RFC1695 Ahmed, M., and K. Tesink, Editors, "Definitions of Managed RFC1696 Barnes, J., Brown, L., Royston, R., and S. Waldbusser, RFC1697 Brower, D., Editor, Purvy, B., RDBMSMIB Working Group Chair, [Rob Austein] [BCN] B. Clifford Neuman < [email protected] > [BS221] Bob Stewart < [email protected] > [CXB] Caralyn Brown <cbrown% [email protected] > [CXD] Chuck Davin < [email protected] > [CXG] Chris Gunner < [email protected] > [Dean Throop] [DXM5] Donna McMaster < [email protected] > [DXP1] David Perkins < [email protected] > [EXD] Eric Decker < [email protected] > [FB77] Fred Baker < [email protected] > [GS2] Greg Satz < [email protected] > [JDC20] Jeffrey Case < [email protected] > [JKR1] Joyce K. Reynolds < [email protected] > [JXC] John Cook < [email protected] > [JXG1] Jim Greuel <jimg% [email protected] > [JXS2] Jon Saperia < [email protected] > [Jeff Hilgeman] [Johannsen] [KZM] Keith McCloghrie < [email protected] > [LS8] Louis Steinberg < [email protected] > [MXA1] Masuma Ahmed < [email protected] > [RAW44] Robert A. Woodburn < [email protected] > [JXC4] John Chu < [email protected] > [Ned Freed] [Deirdre Kostick] [Joel Gyllenskog] Joel Gyllenskog < [email protected] > [Robert Purvey] Robert Purvey < [email protected] > [RXF] Richard Fox < [email protected] > [Jon Saperia] Jon Saperia < [email protected] > [SW159] Steven Willis < [email protected] > [SXW] Steve Waldbusser < [email protected] > [TXB] Tracy Brown < [email protected] > [TXK] Teemu Kurki < [email protected] > [Hartmut Wittig] URL = ftp://ftp.isi.edu/in-notes/iana/assignments/smi-numbers PRIVATE ENTERPRISE NUMBERS SMI Network Management Private Enterprise Codes: This file is 1000 Internet Assigned Numbers Authority [email protected] 1001 PECO Energy Co. Rick Rioboli [email protected] 1002 United Parcel Service Steve Pollini [email protected] 1003 Storage Dimensions, Inc. Michael Torhan [email protected] 1004 ITV Technologies, Inc. Jacob Chen [email protected] 1005 TCPSI Victor San Jose [email protected] 1006 Promptus Communications, Inc. Paul Fredette (401) 683-6100 1007 Norman Data Defense Systems 1008 Pilot Network Services, Inc. Rob Carrade [email protected] 1009 Integrated Systems Solutions Corporation 1010 SISRO Kamp Alexandre [email protected] 1011 NetVantage Kevin Bailey [email protected] 1012 Marconi S.p.A. Giuseppe Grasso [email protected] 1013 SURECOM Mike S. T. Hsieh +886.25.92232 1014 Royal Hong Kong Jockey Club 1015 Gupta Howard Cohen [email protected] 1016 Tone Software Corporation Neil P. Harkins (714) 991-9460 1017 Opus Telecom Pace Willisson [email protected] 1018 Cogsys Ltd. Niall Teasdale [email protected] 1019 Komatsu, Ltd. Akifumi Katsushima +81 463.22.84.30 1020 ROI Systems, Inc Michael Wong (801) 942-1752 1021 Lightning Instrumentation SA Mike O'Dowd [email protected] 1022 TimeStep Corp. Stephane Lacelle [email protected] 1023 INTELSAT Ivan Giron [email protected] 1024 Network Research Corporation Japan, Ltd. 1025 Relational Development, Inc. Steven Smith [email protected] 1026 Emerald Systems, Corp. Robert A. Evans Jr. (619) 673-2161 x5120 1027 Mitel, Corp. Tom Quan [email protected] 1028 Software AG Peter Cohen [email protected] 1029 MillenNet, Inc. Manh Do (510) 770-9390 1030 NK-EXA Corp. Ken'ichi Hayami [email protected] 1031 BMC Software Chris Sharp [email protected] 1032 StarFire Enterprises, Inc. Lew Gaiter [email protected] 1033 Hybrid Networks, Inc. Doug Muirhead [email protected] 1034 Quantum Software GmbH Thomas Omerzu [email protected] 1035 Openvision Technologies Limited 1036 Healthcare Communications, Inc. (HCI) 1037 SAIT Systems Hai Dotu +3223.7053.11 1038 SAT Mleczko Alain +33.1.4077.1156 1039 CompuSci Inc., Bob Berry [email protected] 1040 Aim Technology Ganesh Rajappan [email protected] 1041 CIESIN Kalpesh Unadkat [email protected] 1042 Systems & Technologies International 1043 Israeli Electric Company (IEC) Yoram Harlev [email protected] 1044 Phoenix Wireless Group, Inc. 1045 SWL Bill Kight wkightgrci.com (410) 290.7245 1046 nCUBE Greg Thompson [email protected] 1047 Cerner, Corp. Dennis Avondet (816) 221.1024 X2432 1048 Andersen Consulting Mark Lindberg [email protected] 1049 Lincoln Telephone Company Bob Morrill [email protected] 1050 Acer Jay Tao [email protected] 1051 Cedros Juergen Haakert +49.2241.9701.80 1052 AirAccess Ido Ophir [email protected] 1053 Expersoft Corporation David Curtis [email protected] 1054 Eskom Sanjay Lakhani [email protected] 1055 SBE, Inc. Vimal Vaidya [email protected] 1056 EBS, Inc. Emre Gundogan [email protected] 1057 American Computer and Electronics, Corp. 1058 Syndesis Limited Wil Macaulay [email protected] 1059 Isis Distributed Systems, Inc. Ken Chapman [email protected] 1060 Priority Call Management Greg Schumacher [email protected] 1061 Koelsch & Altmann GmbH 1062 WIPRO INFOTECH LTD. Chandrashekar Kapse [email protected] 1063 Controlware Uli Blatz [email protected] 1064 Mosaic Software W.van Biljon [email protected] 1065 Canon Information Systems 1066 AmericaOnline Andrew R. Scholnick [email protected] 1067 Whitetree Network Technologies, Inc. 1068 Xetron Corp. Dave Alverson [email protected] 1069 Target Concepts, Inc. Bill Price [email protected] 1070 DMH Software Yigal Hochberg [email protected] 1071 Innosoft International, Inc. Jeff Allison [email protected] 1072 Controlware GmbH Uli Blatz [email protected] 1073 Telecommunications Industry Association (TIA) 1074 Boole & Babbage Rami Rubin [email protected] 1075 System Engineering Support, Ltd. Vince Taylor +44 454.614.638 1076 SURFnet Ton Verschuren [email protected] 1077 OpenConnect Systems, Inc. Mark Rensmeyer [email protected] 1078 PDTS (Process Data Technology and Systems) 1079 Cornet, Inc. Nat Kumar (703) 658-3400 1080 NetStar, Inc. John K. Renwick [email protected] 1081 Semaphore Communications, Corp. Jimmy Soetarman (408) 980-7766 1082 Casio Computer Co., Ltd. Shouzo Ohdate [email protected] 1083 CSIR Frikkie Strecker [email protected] 1084 APOGEE Communications Olivier Caleff [email protected] 1085 Information Management Company Michael D. Liss [email protected] 1086 Wordlink, Inc. Mike Aleckson (314) 878-1422 1087 PEER Avinash S. Rao [email protected] 1088 Telstra Corp. Michael Scollay [email protected] 1089 Net X, Inc. Sridhar Kodela [email protected] 1090 PNC PLC Gordon Tees +44 716.061.200 To request an assignment of an Enterprise Number send the complete company name, address, and phone number; and the contact's person complete name, address, phone number, and email mailbox in an email message to < [email protected] >. URL = ftp://ftp.isi.edu/in-notes/iana/assignments/enterprise-numbers SGMP Vendor Specific Codes: [obsolete] Prefix: 1,255, URL = ftp://ftp.isi.edu/in-notes/iana/assignments/sgmp-vendor-specific- codes ADDRESS RESOLUTION PROTOCOL PARAMETERS The Address Resolution Protocol (ARP) specified in RFC826 has several parameters. The assigned values for these parameters are listed here. REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES The Reverse Address Resolution Protocol (RARP) specified in RFC903 uses the "Reverse" codes below. DYNAMIC REVERSE ARP The Dynamic Reverse Address Resolution Protocol (DRARP) uses the "DRARP" codes below. For further information, contact: David Brownell ( [email protected] ). INVERSE ADDRESS RESOULUTION PROTOCOL The Inverse Address Resolution Protocol (IARP) specified in RFC1293 uses the "InARP" codes below. Assignments: Number Operation Code (op) Reference Number Hardware Type (hrd) References ----------------------------------- ---------- Protocol Type (pro) Use the same codes as listed in the section called "Ethernet Numbers of Interest" (all hardware types use this code set for the protocol type). RFC826 Plummer, D., "An Ethernet Address Resolution Protocol or RFC903 Finlayson, R., Mann, T., Mogul, J., and M. Theimer, "A RFC1293 Bradley, T., and C. Brown, "Inverse Address Resolution [AGM] Andy Malis < [email protected] > [GXC1] George Clapp < [email protected] > [GXP] Gill Pratt <gill% [email protected] > [JXM] Joseph Murdock <---none---> [MXB1] Mike Burrows < [email protected] > [PXK] Philip Koch < [email protected] > [RXD2] Rajiv Dhingra < [email protected] > [TU] Tom Unger < [email protected] > [David Brownell] [Mark Laubach] [Yakov Rekhter] < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/arp-parameters IEEE 802 NUMBERS OF INTEREST 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). The IEEE likes to describe numbers in binary in bit transmission order, which is the opposite of the big-endian order used throughout the Internet protocol documentation. Link Service Access Point Description References ----------- ---------- IEEE Internet binary binary decimal 00000000 00000000 0 Null LSAP [IEEE] 01000000 00000010 2 Indiv LLC Sublayer Mgt [IEEE] 11000000 00000011 3 Group LLC Sublayer Mgt [IEEE] 00100000 00000100 4 SNA Path Control [IEEE] 01100000 00000110 6 Reserved (DOD IP) [RFC768,JBP] 01110000 00001110 14 PROWAY-LAN [IEEE] 01110010 01001110 78 EIA-RS 511 [IEEE] 01111010 01011110 94 ISI IP [JBP] 01110001 10001110 142 PROWAY-LAN [IEEE] 01010101 10101010 170 SNAP [IEEE] 01111111 11111110 254 ISO CLNS IS 8473 [RFC926,JXJ] 11111111 11111111 255 Global DSAP [IEEE] These numbers (and others) are assigned by the IEEE Standards Office. The address is: IEEE Registration Authority c/o Iris Ringel IEEE Standards Dept 445 Hoes Lane, P.O. Box 1331 Piscataway, NJ 08855-1331 Phone +1 908 562 3813 Fax: +1 908 562 1571 The fee is $1000 and it takes 10 working days after receipt of the request form and fee. They will not do anything via fax or phone. At an ad hoc special session on "IEEE 802 Networks and ARP", held during the TCP Vendors Workshop (August 1986), an approach to a consistent way to send DoD-IP datagrams and other IP related protocols (such as the Address Resolution Protocol (ARP)) on 802 networks was developed, using the SNAP extension (see RFC1042 ). RFC926 International Standards Organization, "Protocol for Providing RFC1042 Postel, J., and J. Reynolds, "A Standard for the [JXJ] <mystery contact> URL = ftp://ftp.isi.edu/in-notes/iana/assignments/ieee-802-numbers ETHER TYPES 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. If you need an Ether Type, contact: Xerox Systems Institute 3400 Hillview Ave. PO BOX 10034 Palo Alto, CA 94303 Phone: 415-813-7164 Contact: Fonda Lix Pallone The following list of EtherTypes is contributed unverified information from various sources. Ethernet Exp. Ethernet Description References ------------- ----------- ---------- decimal Hex decimal octal 000 0000-05DC - - IEEE802.3 Length Field [XEROX] 257 0101-01FF - - Experimental [XEROX] 512 0200 512 1000 XEROX PUP (see 0A00) [8,XEROX] 513 0201 - - PUP Addr Trans (see 0A01)[XEROX] The standard for transmission of IP datagrams over Ethernets and Experimental Ethernets is specified in RFC894 and RFC895 respectively. NOTE: Ethernet 48-bit address blocks are assigned by the IEEE. IEEE Registration Authority c/o Iris Ringel IEEE Standards Department 445 Hoes Lane, P.O. Box 1331 Piscataway, NJ 08855-1331 Phone +1 908 562 3813 Fax: +1 908 562 1571 IANA ETHERNET ADDRESS BLOCK The IANA owns an Ethernet address block which may be used for multicast address asignments or other special purposes. The address block in IEEE binary is: 0000 0000 0000 0000 0111 1010 In the normal Internet dotted decimal notation this is 0.0.94 since the bytes are transmitted higher order first and bits within bytes are transmitted lower order first (see "Data Notation" in the Introduction ). IEEE CSMA/CD and Token Bus bit transmission order: 00 00 5E IEEE Token Ring bit transmission order: 00 00 7A Appearance on the wire (bits transmitted from left to right): Appearance in memory (bits transmitted right-to-left within octets, octets transmitted left-to-right): The latter representation corresponds to the Internet standard bit-order, and is the format that most programmers have to deal with. Using this representation, the range of Internet Multicast addresses is: ETHERNET VENDOR ADDRESS COMPONENTS Ethernet hardware addresses are 48 bits, expressed as 12 hexadecimal digits (0-9, plus A-F, capitalized). These 12 hex digits consist of the first/left 6 digits (which should match the vendor of the Ethernet interface within the station) and the last/right 6 digits which specify the interface serial number for that interface vendor. Ethernet addresses might be written unhyphenated (e.g., 123456789ABC), or with one hyphen (e.g., 123456-789ABC), but should be written hyphenated by octets (e.g., 12-34-56-78-9A-BC). These addresses are physical station addresses, not multicast nor broadcast, so the second hex digit (reading from the left) will be even, not odd. At present, it is not clear how the IEEE assigns Ethernet block addresses. Whether in blocks of 2**24 or 2**25, and whether multicasts are assigned with that block or separately. A portion of the vendor block address is reportedly assigned serially, with the other portion intentionally assigned randomly. If there is a global algorithm for which addresses are designated to be physical (in a chipset) versus logical (assigned in software), or globally-assigned versus locally-assigned addresses, some of the known addresses do not follow the scheme (e.g., AA0003; 02xxxx). 00000C Cisco 00000E Fujitsu 00000F NeXT 000010 Sytek 00001D Cabletron 000020 DIAB (Data Intdustrier AB) 000022 Visual Technology 00002A TRW 000032 GPT Limited (reassigned from GEC Computers Ltd) 00005A S & Koch 00005E IANA 000065 Network General 00006B MIPS 000077 MIPS 00007A Ardent 000089 Cayman Systems Gatorbox 000093 Proteon 00009F Ameristar Technology 0000A2 Wellfleet 0000A3 Network Application Technology 0000A6 Network General (internal assignment, not for products) 0000A7 NCD X-terminals 0000A9 Network Systems 0000AA Xerox Xerox machines 0000B3 CIMLinc 0000B7 Dove Fastnet 0000BC Allen-Bradley 0000C0 Western Digital 0000C5 Farallon phone net card 0000C6 HP Intelligent Networks Operation (formerly Eon Systems) 0000C8 Altos 0000C9 Emulex Terminal Servers 0000D7 Dartmouth College (NED Router) 0000D8 3Com? Novell? PS/2 0000DD Gould 0000DE Unigraph 0000E2 Acer Counterpoint 0000EF Alantec 0000FD High Level Hardvare (Orion, UK) 000102 BBN BBN internal usage (not registered) 0020AF 3COM ??? 001700 Kabel 008064 Wyse Technology / Link Technologies 00802B IMAC ??? 00802D Xylogics, Inc. Annex terminal servers 00808C Frontier Software Development 0080C2 IEEE 802.1 Committee 0080D3 Shiva 00AA00 Intel 00DD00 Ungermann-Bass 00DD01 Ungermann-Bass 020701 Racal InterLan 020406 BBN BBN internal usage (not registered) 026086 Satelcom MegaPac (UK) 02608C 3Com IBM PC; Imagen; Valid; Cisco 02CF1F CMC Masscomp; Silicon Graphics; Prime EXL 080002 3Com (Formerly Bridge) 080003 ACC (Advanced Computer Communications) 080005 Symbolics Symbolics LISP machines 080008 BBN 080009 Hewlett-Packard 08000A Nestar Systems 08000B Unisys 080011 Tektronix, Inc. 080014 Excelan BBN Butterfly, Masscomp, Silicon Graphics 080017 NSC 08001A Data General 08001B Data General 08001E Apollo 080020 Sun Sun machines 080022 NBI 080025 CDC 080026 Norsk Data (Nord) 080027 PCS Computer Systems GmbH 080028 TI Explorer 08002B DEC 08002E Metaphor 08002F Prime Computer Prime 50-Series LHC300 080036 Intergraph CAE stations 080037 Fujitsu-Xerox 080038 Bull 080039 Spider Systems 080041 DCA Digital Comm. Assoc. 080045 ???? (maybe Xylogics, but they claim not to know this number) 080046 Sony 080047 Sequent 080049 Univation 08004C Encore 08004E BICC 080056 Stanford University 080058 ??? DECsystem-20 08005A IBM 080067 Comdesign 080068 Ridge 080069 Silicon Graphics 08006E Concurrent Masscomp 080075 DDE (Danish Data Elektronik A/S) 08007C Vitalink TransLAN III 080080 XIOS 080086 Imagen/QMS 080087 Xyplex terminal servers 080089 Kinetics AppleTalk-Ethernet interface 08008B Pyramid 08008D XyVision XyVision machines 080090 Retix Inc Bridges 484453 HDS ??? 800010 AT&T AA0000 DEC obsolete AA0001 DEC obsolete AA0002 DEC obsolete AA0003 DEC Global physical address for some DEC machines AA0004 DEC Local logical address for systems running ETHERNET MULTICAST ADDRESSES An Ethernet multicast address consists of the multicast bit, the 23-bit vendor component, and the 24-bit group identifier assigned by the vendor. For example, DEC is assigned the vendor component 08-00-2B, so multicast addresses assigned by DEC have the first 24-bits 09-00-2B (since the multicast bit is the low-order bit of the first byte, which is "the first bit on the wire"). Ethernet Type Address Field Usage Multicast Addresses: 01-00-5E-00-00-00- 0800 Internet Multicast RFC1112 01-00-5E-7F-FF-FF 01-00-5E-80-00-00- ???? Internet reserved by IANA 01-00-5E-FF-FF-FF 01-80-C2-00-00-00 -802- Spanning tree (for bridges) 09-00-02-04-00-01? 8080? Vitalink printer 09-00-02-04-00-02? 8080? Vitalink management 09-00-09-00-00-01 8005 HP Probe 09-00-09-00-00-01 -802- HP Probe 09-00-09-00-00-04 8005? HP DTC 09-00-1E-00-00-00 8019? Apollo DOMAIN 09-00-2B-00-00-00 6009? DEC MUMPS? 09-00-2B-00-00-01 8039? DEC DSM/DTP? 09-00-2B-00-00-02 803B? DEC VAXELN? 09-00-2B-00-00-03 8038 DEC Lanbridge Traffic Monitor (LTM) 09-00-2B-00-00-04 ???? DEC MAP End System Hello 09-00-2B-00-00-05 ???? DEC MAP Intermediate System Hello 09-00-2B-00-00-06 803D? DEC CSMA/CD Encryption? 09-00-2B-00-00-07 8040? DEC NetBios Emulator? 09-00-2B-00-00-0F 6004 DEC Local Area Transport (LAT) 09-00-2B-00-00-1x ???? DEC Experimental 09-00-2B-01-00-00 8038 DEC LanBridge Copy packets 09-00-2B-01-00-01 8038 DEC LanBridge Hello packets 09-00-2B-02-00-00 ???? DEC DNA Lev. 2 Routing Layer routers? 09-00-2B-02-01-00 803C? DEC DNA Naming Service Advertisement? 09-00-2B-02-01-01 803C? DEC DNA Naming Service Solicitation? 09-00-2B-02-01-02 803E? DEC DNA Time Service? 09-00-2B-03-xx-xx ???? DEC default filtering by bridges? 09-00-2B-04-00-00 8041? DEC Local Area Sys. Transport (LAST)? 09-00-2B-23-00-00 803A? DEC Argonaut Console? 09-00-4E-00-00-02? 8137? Novell IPX 09-00-56-00-00-00- ???? Stanford reserved 09-00-56-FE-FF-FF 09-00-56-FF-00-00- 805C Stanford V Kernel, version 6.0 09-00-56-FF-FF-FF 09-00-77-00-00-01 ???? Retix spanning tree bridges 09-00-7C-02-00-05 8080? Vitalink diagnostics 09-00-7C-05-00-01 8080? Vitalink gateway? 0D-1E-15-BA-DD-06 ???? HP AB-00-00-01-00-00 6001 DEC Maintenance Operation Protocol AB-00-00-02-00-00 6002 DEC Maintenance Operation Protocol AB-00-00-03-00-00 6003 DECNET Phase IV end node Hello AB-00-00-04-00-00 6003 DECNET Phase IV Router Hello packets AB-00-00-05-00-00 ???? Reserved DEC through AB-00-03-FF-FF-FF AB-00-03-00-00-00 6004 DEC Local Area Transport (LAT) - old AB-00-04-00-xx-xx ???? Reserved DEC customer private use AB-00-04-01-xx-yy 6007 DEC Local Area VAX Cluster groups CF-00-00-00-00-00 9000 Ethernet Configuration Test protocol Broadcast Address: FF-FF-FF-FF-FF-FF 0600 XNS packets, Hello or gateway search? FF-FF-FF-FF-FF-FF 0800 IP (e.g. RWHOD via UDP) as needed FF-FF-FF-FF-FF-FF 0804 CHAOS FF-FF-FF-FF-FF-FF 0806 ARP (for IP and CHAOS) as needed FF-FF-FF-FF-FF-FF 0BAD Banyan FF-FF-FF-FF-FF-FF 1600 VALID packets, Hello or gateway FF-FF-FF-FF-FF-FF 8035 Reverse ARP FF-FF-FF-FF-FF-FF 807C Merit Internodal (INP) FF-FF-FF-FF-FF-FF 809B EtherTalk RFC894 Hornig, C., "A Standard for the Transmission of IP Datagrams RFC895 Postel, J., "A Standard for the Transmission of IP Datagrams RFC1112 Deeering, S., "Host Extensions for IP Multicasting", [DCP1] David Plummer < [email protected] > [DT15] Daniel Tappan < [email protected] > [XEROX] Fonda Pallone (415-813-7164) URL = ftp://ftp.isi.edu/in-notes/iana/assignments/ethernet-numbers X.25 TYPE NUMBERS CCITT defines the high order two bits of the first octet of call user data as follows: 00 - Used for other CCITT recomendations (such as X.29) 01 - Reserved for use by "national" administrative 10 - Reserved for use by international administrative authoorities 11 - Reserved for arbitrary use between consenting DTEs Call User Data (hex) Protocol Reference -------- --------- 01 PAD [GS2] C5 Blacker front-end descr dev [AGM] CC IP [RFC877,AGM]* CD ISO-IP [AGM] CF PPP RFC1598 DD Network Monitoring [AGM]
RFC877 Korb, J., "A Standard for the Transmission of IP Datagrams RFC1598 Simpson, W., "PPPin X.25", RFC 1598 , Daydreamer, March 1994. URL = ftp://ftp.isi.edu/in-notes/iana/assignments/x25-type-numbers PUBLIC DATA NETWORK NUMBERS 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 standard for transmission of IP datagrams over the Public Data Network is specified in RFC-1356 [69]. [ABB2] A. Blasco Bonito < [email protected] > [AD67] Andy Davis < [email protected] > [AXH] Arthur Harvey < [email protected] > [AXM] Alex Martin <---none---> [BXD] Brian Dockter <---none---> [FXB] <mystery contact> [GB7] Gerd Beling < [email protected] > [JBP] Jon Postel < [email protected] . [JD21] Jonathan Dreyer < [email protected] > [JFW] Jon F. Wilkes < [email protected] > [JK64] mystery contact! [JXE2] Jeanne Evans <JME% [email protected] > [LZ15] Lee Ziegenhals < [email protected] > [MO2] Michael O'Brien < [email protected] > [OXG] Oyvind Gjerstad <ogj% [email protected] > [PAM6] Paul McNabb < [email protected] > [PXD] Peter Delchiappo <---none---> [PXF1] Per Futtrup <---none---> [RAM57] Rex Mann <---none---> [SXA3] Sten Andler <---none---> [TN] Thomas Narten < [email protected] > [TC27] Thomas Calderwood < [email protected] > [TXR] Tim Rylance < [email protected] > [UXB] <mystery contact> [VXT] V. Taylor < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/public-data-network- numbers MILNET LINK NUMBERS The word "link" here refers to a field in the original MILNET Host/IMP interface leader. The link was originally defined as an 8-bit field. Later specifications defined this field as the "message-id" with a length of 12 bits. The name link now refers to the high order 8 bits of this 12-bit message-id field. The Host/IMP interface is defined in BBN Report 1822 [BBN1822]. The low-order 4 bits of the message-id field are called the sub-link. Unless explicitly specified otherwise for a particular protocol, there is no sender to receiver significance to the sub-link. The sender may use the sub-link in any way he chooses (it is returned in the RFNM by the destination IMP), the receiver should ignore the sub-link. Link Assignments: Decimal Description References 0-63 BBNCC Monitoring [MB] 64-149 Unassigned [JBP] 150 Xerox NS IDP [ETHERNET,XEROX] 151 Unassigned [JBP] 152 PARC Universal Protocol [PUP,XEROX] 153 TIP Status Reporting [JGH] 154 TIP Accounting [JGH] 155 Internet Protocol [regular] [RFC791,JBP] 156-158 Internet Protocol [experimental] [RFC791,JBP] 159 Figleaf Link [JBW1] 160 Blacker Local Network Protocol [DM28] 161-194 Unassigned [JBP] 195 ISO-IP [RFC926,RXM] 196-247 Experimental Protocols [JBP] 248-255 Network Maintenance [JGH] MILNET LOGICAL ADDRESSES The MILNET facility for "logical addressing" is described in RFC878 and RFC1005 . A portion of the possible logical addresses are reserved for standard uses. There are 49,152 possible logical host addresses. Of these, 256 are reserved for assignment to well-known functions. Assignments for well-known functions are made by the IANA. Assignments for other logical host addresses are made by the NIC. Logical Address Assignments: 0 Reserved [JBP] 1 The BBN Core Gateways [MB] 2-254 Unassigned [JBP] 255 Reserved [JBP] MILNET X.25 ADDRESS MAPPINGS All MILNET hosts are assigned addresses by the Defense Data Network (DDN). The address of a MILNET host may be obtained from the Network Information Center (NIC), represented as an ASCII text string in what is called "host table format". This section describes the process by which MILNET X.25 addresses may be derived from addresses in the NIC host table format. A NIC host table address consists of the ASCII text string representations of four decimal numbers separated by periods, corresponding to the four octeted of a thirty-two bit Internet address. The four decimal numbers are referred to in this section as "n", "h' "l", and "i". Thus, a host table address may be represented as: "n.h.l.i". Each of these four numbers will have either one, two, or three decimal digits and will never have a value greater than 255. For example, in the host table, address: "10.2.0.124", n=10, h=2, l=0, and i=124. To convert a host table address to a MILNET X.25 address: If h < 64, the host table address corresponds to the X.25physical address: ZZZZ F IIIHHZZ (SS) In the example given above, the host table address 10.2.0.124 corresponds to the X.25 physical address 000001240200. If h > 64 or h = 64, the host table address corresponds to theX.25 logical address ZZZZ F RRRRRZZ (SS) Thus, the host table address 10.83.0.207 corresponds to the X.25 logical address 000012145500. In both cases, the "n" and "l" fields of the host table address are not used. [BBN1822] BBN, "Specifications for the Interconnection of a Host and RFC878 Malis, Andrew, "The ARPANET 1822L Host Access Protocol", RFC1005 Khanna, A., and A. Malis, "The ARPANET AHIP-E Host Access [DM28] Dennis Morris < [email protected] > [JBW1] Joseph Walters, Jr. < [email protected] > [JGH] Jim Herman < [email protected] > [MB] Michael Brescia < [email protected] > [RXM] Robert Myhill < [email protected] > [XEROX] Fonda Pallone <---none---> URL = ftp://ftp.isi.edu/in-notes/iana/assignments/milnet-parameters XNS PROTOCOL TYPES Assigned well-known socket numbers Assigned internet packet types URL = ftp://ftp.isi.edu/in-notes/iana/assignments/xns-protocol-types INTERNET / XNS PROTOCOL MAPPINGS Below 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. lower | | | | |--------|--------|--------| 3Mb Ethernet | 1001 | 1000 | 3000 | 10 Mb Ethernet| 0800 | 0200 | 0600 | MILNET | 155 | 152 | 150 | DoD IP | X | 12 | 22 | PUP | ? | X | ? | NS IP | 13 | 12 | X | URL = ftp://ftp.isi.edu/in-notes/iana/assignments/ip-xns-mapping PRONET 80 TYPE NUMBERS Below 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. Of these, protocols 1, 14, and 20 are the only ones that have ever been seen in ARP packets. For reference, the header is (one byte/line): Some protocols have been known to tuck stuff in the reserved fields. Those who need a protocol number on ProNET-10/80 should contact John Shriver ( [email protected] ). 1 IP 2 IP with trailing headers 3 Address Resolution Protocol 4 Proteon HDLC 5 VAX Debugging Protocol (MIT) 10 Novell NetWare (IPX and pre-IPX) (old format, 11 Vianetix 12 PUP 13 Watstar protocol (University of Waterloo) 14 XNS 15 Diganostics 16 Echo protocol (link level) 17 Banyan Vines 20 DECnet (DEUNA Emulation) 21 Chaosnet 23 IEEE 802.2 or ISO 8802/2 Data Link 24 Reverse Address Resolution Protocol 29 TokenVIEW-10 31 AppleTalk LAP Data Packet 33 Cornell Boot Server Location Protocol 34 Novell NetWare IPX (new format, no trailer, URL = ftp://ftp.isi.edu/in-notes/iana/assignments/pronet80-type-numbers NOVELL SAP NUMBERS OF INTEREST For the convenience of the Internet community the IANA maitains a list of Novell Service Access Point (SAP) numbers. This list is kept up-to-date- by contributions from the community. Please send corrections and additions to [email protected] . Novell SAPs Decimal Hex SAP Description = ==== =========0 0000 Unknown 1 0001 User 2 0002 User Group 3 0003 Print Queue or Print Group 4 0004 File Server (SLIST source) 5 0005 Job Server 6 0006 Gateway 7 0007 Print Server or Silent Print Server 8 0008 Archive Queue 9 0009 Archive Server 10 000a Job Queue 11 000b Administration 15 000F Novell TI-RPC 23 0017 Diagnostics 32 0020 NetBIOS 33 0021 NAS SNA Gateway 35 0023 NACS Async Gateway or Asynchronous Gateway 36 0024 Remote Bridge or Routing Service 38 0026 Bridge Server or Asynchronous Bridge Server 39 0027 TCP/IP Gateway Server 40 0028 Point to Point (Eicon) X.25 Bridge Server 41 0029 Eicon 3270 Gateway 42 002a CHI Corp ??? 44 002c PC Chalkboard 45 002d Time Synchronization Server or Asynchronous Timer 46 002e SAP Archive Server or SMS Target Service Agent 69 0045 DI3270 Gateway 71 0047 Advertising Print Server 75 004b Btrieve VAP/NLM 5.0 76 004c Netware SQL VAP/NLM Server 77 004d Xtree Network Version Netware XTree 80 0050 Btrieve VAP 4.11 82 0052 QuickLink (Cubix) 83 0053 Print Queue User 88 0058 Multipoint X.25 Eicon Router 96 0060 STLB/NLM ??? 100 0064 ARCserve 102 0066 ARCserve 3.0 114 0072 WAN Copy Utility 122 007a TES-Netware for VMS 146 0092 WATCOM Debugger or Emerald Tape Backup Server 149 0095 DDA OBGYN ??? 152 0098 Netware Access Server (Asynchronous gateway) 154 009a Netware for VMS II or Named Pipe Server 155 009b Netware Access Server 158 009e Portable Netware Server or SunLink NVT 161 00a1 Powerchute APC UPS NLM 170 00aa LAWserve ??? 172 00ac Compaq IDA Status Monitor 256 0100 PIPE STAIL ??? 258 0102 LAN Protect Bindery 259 0103 Oracle DataBase Server 263 0107 Netware 386 or RSPX Remote Console 271 010f Novell SNA Gateway 274 0112 Print Server (HP) 276 0114 CSA MUX (f/Communications Executive) 277 0115 CSA LCA (f/Communications Executive) 278 0116 CSA CM (f/Communications Executive) 279 0117 CSA SMA (f/Communications Executive) 280 0118 CSA DBA (f/Communications Executive) 281 0119 CSA NMA (f/Communications Executive) 282 011a CSA SSA (f/Communications Executive) 283 011b CSA STATUS (f/Communications Executive) 286 011e CSA APPC (f/Communications Executive) 294 0126 SNA TEST SSA Profile 298 012a CSA TRACE (f/Communications Executive) 304 0130 Communications Executive 307 0133 NNS Domain Server or Netware Naming Services Domain 309 0135 Netware Naming Services Profile 311 0137 Netware 386 Print Queue or NNS Print Queue 321 0141 LAN Spool Server (Vap, Intel) 338 0152 IRMALAN Gateway 340 0154 Named Pipe Server 360 0168 Intel PICKIT Comm Server or Intel CAS Talk Server 369 171 UNKNOWN??? 371 0173 Compaq 372 0174 Compaq SNMP Agent 373 0175 Compaq 384 0180 XTree Server or XTree Tools 394 18A UNKNOWN??? Running on a Novell Server 432 01b0 GARP Gateway (net research) 433 01b1 Binfview (Lan Support Group) 447 01bf Intel LanDesk Manager 458 01ca AXTEC ??? 459 01cb Netmode ??? 460 1CC UNKNOWN??? Sheva netmodem??? 472 01d8 Castelle FAXPress Server 474 01da Castelle LANPress Print Server 476 1DC Castille FAX/Xerox 7033 Fax Server/Excel Lan Fax 496 01f0 LEGATO ??? 501 01f5 LEGATO ??? 563 0233 NMS Agent or Netware Management Agent 567 0237 NMS IPX Discovery or LANtern Read/Write Channel 568 0238 NMS IP Discovery or LANtern Trap/Alarm Channel 570 023a LABtern 572 023c MAVERICK ??? 574 23E UNKNOWN??? Running on a Novell Server 575 023f Used by eleven various Novell Servers 590 024e Remote Something ??? 618 026a Network Management (NMS) Service Console 619 026b Time Synchronization Server (Netware 4.x) 632 0278 Directory Server (Netware 4.x) 772 0304 Novell SAA Gateway 776 0308 COM or VERMED 1 ??? 778 030a Gallacticom BBS 780 030c Intel Netport 2 or HP JetDirect or HP Quicksilver 800 0320 Attachmate Gateway 807 0327 Microsoft Diagnostiocs ??? 821 0335 MultiTech Systems Multisynch Comm Server 853 0355 Arcada Backup Exec 858 0358 MSLCD1 ??? 865 0361 NETINELO ??? 894 037e Twelve Novell file servers in the PC3M family 895 037f ViruSafe Notify 902 0386 HP Bridge 903 0387 HP Hub 916 0394 NetWare SAA Gateway 923 039b Lotus Notes 951 03b7 Certus Anti Virus NLM 964 03c4 ARCserve 4.0 (Cheyenne) 967 03c7 LANspool 3.5 (Intel) 990 03de Gupta Sequel Base Server or NetWare SQL 993 03e1 Univel Unixware 996 03e4 Univel Unixware 1020 03fc Intel Netport 1021 03fd Print SErver Queue ??? 1034 40A ipnServer??? Running on a Novell Server 1035 40B UNKNOWN??? 1037 40D LVERRMAN??? Running on a Novell Server 1038 40E LVLIC??? Running on a Novell Server 1040 410 UNKNOWN??? Running on a Novell Server 1044 0414 Kyocera 1065 0429 Site Lock Virus (Brightworks) 1074 0432 UFHELP R ??? 1075 433 Sunoptics SNMP Agent??? 1100 044c Backup ??? 1111 457 Canon GP55??? Running on a Canon GP55 network printer 1115 045b Dell SCSI Array (DSA) Monitor 1200 04b0 CD-Net (Meridian) 1217 4C1 UNKNOWN??? 1299 513 Emulux NQA??? Something from Emulex 1312 0520 Site Lock Checks 1321 0529 Site Lock Checks (Brightworks) 1325 052d Citrix OS/2 App Server 1344 536 Milan ??? 1408 0580 McAfee's NetShield anti-virus 1569 621 ?? Something from Emulex 1571 623 UNKNOWN??? Running on a Novell Server 1900 076C Xerox 2857 0b29 Site Lock 3113 0c29 Site Lock Applications 3116 0c2c Licensing Server 9088 2380 LAI Site Lock 9100 238c Meeting Maker 18440 4808 Site Lock Server or Site Lock Metering VAP/NLM 21845 5555 Site Lock User 25362 6312 Tapeware 28416 6f00 Rabbit Gateway (3270) 30467 7703 MODEM?? 32770 8002 NetPort Printers (Intel) or LANport 32776 8008 WordPerfect Network Version 34238 85BE Cisco Enhanced Interior Routing Protocol (EIGRP) 34952 8888 WordPerfect Network Version or Quick Network Management 36864 9000 McAfee's NetShield anti-virus 38404 9604 ?? CSA-NT_MON 61727 f11f Site Lock Metering VAP/NLM 61951 f1ff Site Lock 62723 F503 ?? SCA-NT 65535 ffff Any Service or Wildcard URL = ftp://ftp.isi.edu/in-notes/iana/assignments/novell-sap-numbers POINT-TO-POINT PROTOCOL FIELD ASSIGNMENTS PPP DLL PROTOCOL NUMBERS 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". Assigned PPP DLL Protocol Numbers Value (in hex) Protocol Name 0001 Padding Protocol 0003 to 001f reserved (transparency inefficient) 0021 Internet Protocol 0023 OSI Network Layer 0025 Xerox NS IDP 0027 DECnet Phase IV 0029 Appletalk 002b Novell IPX 002d Van Jacobson Compressed TCP/IP 002f Van Jacobson Uncompressed TCP/IP 0031 Bridging PDU 0033 Stream Protocol (ST-II) 0035 Banyan Vines 0037 reserved (until 1993) 0039 AppleTalk EDDP 003b AppleTalk SmartBuffered 003d Multi-Link 003f NETBIOS Framing 0041 Cisco Systems 0043 Ascom Timeplex 0045 Fujitsu Link Backup and Load Balancing (LBLB) 0047 DCA Remote Lan 0049 Serial Data Transport Protocol (PPP-SDTP) 004b SNA over 802.2 004d SNA 004f IP6 Header Compression 006f Stampede Bridging 007d reserved (Control Escape) RFC1661 007f reserved (compression inefficient) RFC1662 00cf reserved (PPP NLPID) 00fb compression on single link in multilink group 00fd 1st choice compression 00ff reserved (compression inefficient) 0201 802.1d Hello Packets 0203 IBM Source Routing BPDU 0205 DEC LANBridge100 Spanning Tree 0231 Luxcom 0233 Sigma Network Systems 8001-801f Not Used - reserved RFC1661 8021 Internet Protocol Control Protocol 8023 OSI Network Layer Control Protocol 8025 Xerox NS IDP Control Protocol 8027 DECnet Phase IV Control Protocol 8029 Appletalk Control Protocol 802b Novell IPX Control Protocol 802d reserved 802f reserved 8031 Bridging NCP 8033 Stream Protocol Control Protocol 8035 Banyan Vines Control Protocol 8037 reserved till 1993 8039 reserved 803b reserved 803d Multi-Link Control Protocol 803f NETBIOS Framing Control Protocol 807d Not Used - reserved RFC1661 8041 Cisco Systems Control Protocol 8043 Ascom Timeplex 8045 Fujitsu LBLB Control Protocol 8047 DCA Remote Lan Network Control Protocol (RLNCP) 8049 Serial Data Control Protocol (PPP-SDCP) 804b SNA over 802.2 Control Protocol 804d SNA Control Protocol 804f IP6 Header Compression Control Protocol 006f Stampede Bridging Control Protocol 80cf Not Used - reserved RFC1661 80fb compression on single link in multilink group control 80fd Compression Control Protocol 80ff Not Used - reserved RFC1661 c021 Link Control Protocol c023 Password Authentication Protocol c025 Link Quality Report c027 Shiva Password Authentication Protocol c029 CallBack Control Protocol (CBCP) c081 Container Control Protocol [KEN] c223 Challenge Handshake Authentication Protocol c281 Proprietary Authentication Protocol [KEN] c26f Stampede Bridging Authorization Protocol c481 Proprietary Node ID Authentication Protocol [KEN] Protocol field values in the "0xxx" to "3xxx" range identify the network-layer protocol of specific datagrams, and values in the "8xxx" to "bxxx" range identify datagrams belonging to the associated Network Control Protocol (NCP), if any. It is recommended that values in the "02xx" to "1exx" and "xx01" to "xx1f" ranges not be assigned, as they are compression inefficient. Protocol field values in the "4xxx" to "7xxx" range are used for protocols with low volume traffic which have no associated NCP. Protocol field values in the "cxxx" to "exxx" range identify datagrams as Control Protocols (such as LCP). PPP LCP AND IPCP CODES The Point-to-Point Protocol (PPP) Link Control Protocol (LCP), [146] the Compression Control Protocol (CCP), Internet Protocol Control Protocol (IPCP), [147] and other control protocols, contain an 8 bit Code field which identifies the type of packet. These Codes are assigned as follows: Code Packet Type ----------- 1 Configure-Request 2 Configure-Ack 3 Configure-Nak 4 Configure-Reject 5 Terminate-Request 6 Terminate-Ack 7 Code-Reject 8 * Protocol-Reject 9 * Echo-Request PPP LCP CONFIGURATION OPTION TYPES The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) specifies a number of Configuration Options [146] which are distinguished by an 8 bit Type field. These Types are assigned as follows: Type Configuration Option -------------------- 1 Maximum-Receive-Unit 2 Async-Control-Character-Map 3 Authentication-Protocol 4 Quality-Protocol 5 Magic-Number 6 RESERVED 7 Protocol-Field-Compression 8 Address-and-Control-Field-Compression 9 FCS-Alternatives PPP LCP FCS-ALTERNATIVES The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) FCS-Alternatives Configuration Option contains an 8-bit Options field which identifies the FCS used. These are assigned as follows: PPP LCP CALLBACK OPERATION FIELDS The Point-to-Point Protocol (PPP) Link Control Protocol (LCP) Callback Configuration Option contains an 8-bit Operations field which identifies the format of the Message. These are assigned as follows: Operation Description --------------------------- PPP IPCP CONFIGURATION OPTION TYPES The Point-to-Point Protocol (PPP) Internet Protocol Control Protocol (IPCP) specifies a number of Configuration Options [147] which are distinguished by an 8 bit Type field. These Types are assigned as follows: 1 IP-Addresses (deprecated) 2 IP-Compression-Protocol 3 IP-Address PPP ATCP CONFIGURATION OPTION TYPES The Point-to-Point Protocol (PPP) Apple Talk Control Protocol (ATCP) specifies a number of Configuration Options [RFC-1378] which are distinguished by an 8 bit Type field. These Types are assigned as follows: 1 AppleTalk-Address 2 Routing-Protocol 3 Suppress-Broadcasts 4 AT-Compression-Protocol 5 Reserved 6 Server-information 7 Zone-information 8 Default-Router-Address PPP OSINLCP CONFIGURATION OPTION TYPES The Point-to-Point Protocol (PPP) OSI Network Layer Control Protocol (OSINLCP) specifies a number of Configuration Options [RFC-1377] which are distinguished by an 8 bit Type field. These Types are assigned as follows: 1 Align-NPDU PPP BRIDGING CONFIGURATION OPTION TYPES The Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) specifies a number of Configuration Options which are distinguished by an 8 bit Type field. These Types are assigned as follows: 1 Bridge-Identification 2 Line-Identification 3 MAC-Support 4 Tinygram-Compression 5 LAN-Identification 6 MAC-Address 7 Spanning-Tree-Protocol PPP BRIDGING MAC TYPES The Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) contains an 8 bit MAC Type field which identifies the MAC encapsulated. These Types are assigned as follows: 0 Reserved 1 IEEE 802.3/Ethernet with cannonical addresses 2 IEEE 802.4 with cannonical addresses 3 IEEE 802.5 with non-cannonical addresses 4 FDDI with non-cannonical addresses PPP BRIDGING SPANNING TREE The Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP) Spanning Tree Configuration Option contains an 8-bit Protocol field which identifies the spanning tree used. These are assigned as follows: Protocol Spanning Tree --------------- 0 Null - no spanning tree protocol supported 1 IEEE 802.1D spanning tree protocol 2 IEEE 802.1G extended spanning tree protocol 3 IBM source route spanning tree protocol 4 DEC LANbridge 100 spanning tree protocol RFC1661 Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", RFC1662 Simpson, W., Editor, "PPP in HDLC-like Framing", STD 51 , RFC [KEN] < [email protected] > [SCHNEIDER] Kevin Schneider < [email protected] > URL = ftp://ftp.isi.edu/in-notes/iana/assignments/ppp-numbers MACHINE NAMES 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 . A machine name or CPU type may be up to 40 characters taken from the set of uppercase letters, digits, and the two punctuation characters hyphen and slash. It must start with a letter, and end with a letter or digit. AMIGA-500 AMIGA-500/010 AMIGA-500/020 AMIGA-500/EC030 AMIGA-500/030 AMIGA-600 AMIGA-1000 AMIGA-1000/010 AMIGA-1000/020 AMIGA-1000/EC030 AMIGA-1000/030 AMIGA-1200 AMIGA-1200/EC030 AMIGA-1200/030 AMIGA-1200/EC040 AMIGA-1200/LC040 AMIGA-1200/040 AMIGA-2000 AMIGA-2000/010 AMIGA-2000/020 AMIGA-2000/EC030 AMIGA-2000/030 AMIGA-2000/LC040 AMIGA-2000/EC040 AMIGA-2000/040 AMIGA-3000 AMIGA-3000/EC040 AMIGA-3000/LC040 AMIGA-3000/040 AMIGA-3000/060 AMIGA-4000/EC030 AMIGA-4000/030 AMIGA-4000/LC040 AMIGA-4000/040 AMIGA-4000/060 ALTO ALTOS-6800 AMDAHL-V7 APOLLO APPLE-MACINTOSH APPLE-POWERBOOK ATARI-104ST ATT-3B1 ATT-3B2 ATT-3B20 ATT-7300 AXP BBN-C/60 BURROUGHS-B/29 BURROUGHS-B/4800 BUTTERFLY C/30 C/70 CADLINC CADR CDC-170 CDC-170/750 CDC-173 CDTV CDTV/060 CD32 CELERITY-1200 CLUB-386 COMPAQ-386/20 COMTEN-3690 CP8040 CRAY-1 CRAY-X/MP CRAY-2 CTIWS-117 DANDELION DEC-10 DEC-1050 DEC-1077 DEC-1080 DEC-1090 DEC-1090B DEC-1090T DEC-2020T DEC-2040 DEC-2040T DEC-2050T DEC-2060 DEC-2060T DEC-2065 DEC-AXP DEC-FALCON DEC-KS10 DECSTATION DEC-VAX DEC-VAXCLUSTER DEC-VAXSTATION DEC-VAX-11730 DORADO DPS8/70M ELXSI-6400 EVEREX-386 FOONLY-F2 FOONLY-F3 FOONLY-F4 GOULD GOULD-6050 GOULD-6080 GOULD-9050 GOULD-9080 H-316 H-60/68 H-68 H-68/80 H-89 HONEYWELL-DPS-6 HONEYWELL-DPS-8/70 HP3000 HP3000/64 IBM-158 IBM-360/67 IBM-370/3033 IBM-3081 IBM-3084QX IBM-3101 IBM-4331 IBM-4341 IBM-4361 IBM-4381 IBM-4956 IBM-6152 IBM-PC IBM-PC/AT IBM-PC/RT IBM-PC/XT IBM-RS/6000 IBM-SERIES/1 IMAGEN IMAGEN-8/300 IMSAI INTEGRATED-SOLUTIONS INTEGRATED-SOLUTIONS-68K INTEGRATED-SOLUTIONS-CREATOR INTEGRATED-SOLUTIONS-CREATOR-8 INTEL-386 INTEL-IPSC IS-1 IS-68010 LMI LSI-11 LSI-11/2 LSI-11/23 LSI-11/73 M68000 MAC-II MAC-POWERBOOK MACINTOSH MASSCOMP MC500 MC68000 MICROPORT MICROVAX MICROVAX-I MV/8000 NAS3-5 NCR-COMTEN-3690 NEXT/N1000-316 NOW ONYX-Z8000 PDP-11 PDP-11/3 PDP-11/23 PDP-11/24 PDP-11/34 PDP-11/40 PDP-11/44 PDP-11/45 PDP-11/50 PDP-11/70 PDP-11/73 PE-7/32 PE-3205 PERQ PLEXUS-P/60 PLI PLURIBUS PRIME-2350 PRIME-2450 PRIME-2755 PRIME-9655 PRIME-9755 PRIME-9955II PRIME-2250 PRIME-2655 PRIME-9955 PRIME-9950 PRIME-9650 PRIME-9750 PRIME-2250 PRIME-750 PRIME-850 PRIME-550II PYRAMID-90 PYRAMID-90MX PYRAMID-90X RIDGE RIDGE-32 RIDGE-32C ROLM-1666 RS/6000 S1-MKIIA SMI SEQUENT-BALANCE-8000 SIEMENS SILICON-GRAPHICS SILICON-GRAPHICS-IRIS SGI-IRIS-2400 SGI-IRIS-2500 SGI-IRIS-3010 SGI-IRIS-3020 SGI-IRIS-3030 SGI-IRIS-3110 SGI-IRIS-3115 SGI-IRIS-3120 SGI-IRIS-3130 SGI-IRIS-4D/20 SGI-IRIS-4D/20G SGI-IRIS-4D/25 SGI-IRIS-4D/25G SGI-IRIS-4D/25S SGI-IRIS-4D/50 SGI-IRIS-4D/50G SGI-IRIS-4D/50GT SGI-IRIS-4D/60 SGI-IRIS-4D/60G SGI-IRIS-4D/60T SGI-IRIS-4D/60GT SGI-IRIS-4D/70 SGI-IRIS-4D/70G SGI-IRIS-4D/70GT SGI-IRIS-4D/80GT SGI-IRIS-4D/80S SGI-IRIS-4D/120GTX SGI-IRIS-4D/120S SGI-IRIS-4D/210GTX SGI-IRIS-4D/210S SGI-IRIS-4D/220GTX SGI-IRIS-4D/220S SGI-IRIS-4D/240GTX SGI-IRIS-4D/240S SGI-IRIS-4D/280GTX SGI-IRIS-4D/280S SGI-IRIS-CS/12 SGI-IRIS-4SERVER-8 SPERRY-DCP/10 SUN SUN-2 SUN-2/50 SUN-2/100 SUN-2/120 SUN-2/130 SUN-2/140 SUN-2/150 SUN-2/160 SUN-2/170 SUN-3/50 SUN-3/60 SUN-3/75 SUN-3/80 SUN-3/110 SUN-3/140 SUN-3/150 SUN-3/160 SUN-3/180 SUN-3/200 SUN-3/260 SUN-3/280 SUN-3/470 SUN-3/480 SUN-4/60 SUN-4/110 SUN-4/150 SUN-4/200 SUN-4/260 SUN-4/280 SUN-4/330 SUN-4/370 SUN-4/390 SUN-50 SUN-100 SUN-120 SUN-130 SUN-150 SUN-170 SUN-386i/250 SUN-68000 SYMBOLICS-3600 SYMBOLICS-3670 SYMMETRIC-375 SYMULT TANDEM-TXP TANDY-6000 TEK-6130 TI-EXPLORER TP-4000 TRS-80 UNIVAC-1100 UNIVAC-1100/60 UNIVAC-1100/62 UNIVAC-1100/63 UNIVAC-1100/64 UNIVAC-1100/70 UNIVAC-1160 UNKNOWN VAX VAX-11/725 VAX-11/730 VAX-11/750 VAX-11/780 VAX-11/785 VAX-11/790 VAX-11/8600 VAX-8600 VAXCLUSTER VAXSTATION WANG-PC002 WANG-VS100 WANG-VS400 WYSE-386 WYSE-WN5004 WYSE-WN5008 WYSE-WN5104 WYSE-WN5108 WYSE-WX15C WYSE-WX17C WYSE-WX17M WYSE-WX19C WYSE-WX19M WYSE-WYX14M WYSE-WYX5 XEROX-1108 XEROX-8010 ZENITH-148 RFC952 Harrenstien, K., Stahl, M., and E. Feinler, "DoD Internet URL = ftp://ftp.isi.edu/in-notes/iana/assignments/machine-names OPERATING SYSTEM NAMES 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 . A system name may be up to 40 characters taken from the set of uppercase letters, digits, and the three punctuation characters hyphen, period, and slash. It must start with a letter, and end with a letter or digit. AEGIS AMIGA-OS-1.2 AMIGA-OS-1.3 AMIGA-OS-2.0 AMIGA-OS-2.1 AMIGA-OS-3.0 AMIGA-OS-3.1 APOLLO AIX/370 AIX-PS/2 BS-2000 CEDAR CGW CHORUS CHRYSALIS CMOS CMS COS CPIX CTOS CTSS DCN DDNOS DOMAIN DOS EDX ELF EMBOS EMMOS EPOS FOONEX FORTH FUZZ GCOS GPOS HDOS IMAGEN INTERCOM IMPRESS INTERLISP IOS IRIX ISI-68020 ITS LISP LISPM LOCUS MACOS MINOS MOS MPE5 MPE/V MPE/IX MSDOS MULTICS MUSIC MUSIC/SP MVS MVS/SP NEXUS NMS NONSTOP NOS-2 NTOS OPENVMS OS/DDP OS/2 OS4 OS86 OSX PCDOS PERQ/OS PLI PSDOS/MIT PRIMOS RMX/RDOS ROS RSX11M RTE-A SATOPS SCO-OPEN-DESKTOP-1.0 SCO-OPEN-DESKTOP-1.1 SCO-OPEN-DESKTOP-2.0 SCO-OPEN-DESKTOP-3.0 SCO-OPEN-DESKTOP-LITE-3.0 SCO-OPEN-SERVER-3.0 SCO-UNIX-3.2.0 SCO-UNIX-3.2V2.0 SCO-UNIX-3.2V2.1 SCO-UNIX-3.2V4.0 SCO-UNIX-3.2V4.1 SCO-UNIX-3.2V4.2 SCO-XENIX-386-2.3.2 SCO-XENIX-386-2.3.3 SCO-XENIX-386-2.3.4 SCS SIMP SUN SUN-OS-3.5 SUN-OS-4.0 SWIFT TAC TANDEM TENEX THE-MAJOR-BBS TOPS10 TOPS20 TOS TP3010 TRSDOS ULTRIX UNIX UNIX-BSD UNIX-V1AT UNIX-V UNIX-V.1 UNIX-V.2 UNIX-V.3 UNIX-PC UNKNOWN UT2D V VM VM/370 VM/CMS VM/SP VMS VMS/EUNICE VRTX WAITS WANG WIN32 WYSE-WYXWARE X11R3 XDE XENIX URL = ftp://ftp.isi.edu/in-notes/iana/assignments/operating-system-names TERMINAL TYPE NAMES These are the Official Terminal Type Names. Their use is described in RFC930 . The maximum length of a name is 40 characters. A terminal names may be up to 40 characters taken from the set of uppercase letters, digits, and the two punctuation characters hyphen and slash. It must start with a letter, and end with a letter or digit. ADDS-CONSUL-980 ADDS-REGENT-100 ADDS-REGENT-20 ADDS-REGENT-200 ADDS-REGENT-25 ADDS-REGENT-40 ADDS-REGENT-60 ADDS-VIEWPOINT ADDS-VIEWPOINT-60 AED-512 AMPEX-DIALOGUE-210 AMPEX-DIALOGUE-80 AMPEX-210 AMPEX-230 ANDERSON-JACOBSON-510 ANDERSON-JACOBSON-630 ANDERSON-JACOBSON-832 ANDERSON-JACOBSON-841 ANN-ARBOR-AMBASSADOR ANSI ARDS BITGRAPH BUSSIPLEXER CALCOMP-565 CDC-456 CDI-1030 CDI-1203 C-ITOH-101 C-ITOH-50 C-ITOH-80 CLNZ COMPUCOLOR-II CONCEPT-100 CONCEPT-104 CONCEPT-108 DATA-100 DATA-GENERAL-6053 DATAGRAPHIX-132A DATAMEDIA-1520 DATAMEDIA-1521 DATAMEDIA-2500 DATAMEDIA-3025 DATAMEDIA-3025A DATAMEDIA-3045 DATAMEDIA-3045A DATAMEDIA-DT80/1 DATAPOINT-2200 DATAPOINT-3000 DATAPOINT-3300 DATAPOINT-3360 DEC-DECWRITER-I DEC-DECWRITER-II DEC-GIGI DEC-GT40 DEC-GT40A DEC-GT42 DEC-LA120 DEC-LA30 DEC-LA36 DEC-LA38 DEC-VT05 DEC-VT100 DEC-VT101 DEC-VT102 DEC-VT125 DEC-VT131 DEC-VT132 DEC-VT200 DEC-VT220 DEC-VT240 DEC-VT241 DEC-VT300 DEC-VT320 DEC-VT340 DEC-VT50 DEC-VT50H DEC-VT52 DEC-VT55 DEC-VT61 DEC-VT62 DELTA-DATA-5000 DELTA-DATA-NIH-7000 DELTA-TELTERM-2 DIABLO-1620 DIABLO-1640 DIGILOG-333 DTC-300S DTC-382 EDT-1200 ETOS52-APL ETOS52-CRT ETOS52-FDW ETOS52-FUP ETOS52-GFM ETOS52-SPR EXECUPORT-4000 EXECUPORT-4080 FACIT-TWIST-4440 FREEDOM-100 FREEDOM-110 FREEDOM-200 GENERAL-TERMINAL-100A GENERAL-TERMINAL-101 GIPSI-TX-M GIPSI-TX-ME GIPSI-TX-C4 GIPSI-TX-C8 GSI HAZELTINE-1420 HAZELTINE-1500 HAZELTINE-1510 HAZELTINE-1520 HAZELTINE-1552 HAZELTINE-2000 HAZELTINE-ESPRIT HITACHI-5601 HITACHI-5603 HITACHI-5603E HITACHI-5603EA HITACHI-560X HITACHI-560XE HITACHI-560XEA HITACHI-560PR HITACHI-HOAP1 HITACHI-HOAP2 HITACHI-HOAP3 HITACHI-HOAP4 HP-2392 HP-2621 HP-2621A HP-2621P HP-2623 HP-2626 HP-2626A HP-2626P HP-2627 HP-2640 HP-2640A HP-2640B HP-2645 HP-2645A HP-2648 HP-2648A HP-2649 HP-2649A IBM-1050 IBM-2741 IBM-3101 IBM-3101-10 IBM-3151 IBM-3179-2 IBM-3180-2 IBM-3196-A1 IBM-3275-2 IBM-3276-2 IBM-3276-3 IBM-3276-4 IBM-3277-2 IBM-3278-2 IBM-3278-3 IBM-3278-4 IBM-3278-5 IBM-3279-2 IBM-3279-3 IBM-3477-FC IBM-3477-FG IBM-5081 IBM-5151 IBM-5154 IBM-5251-11 IBM-5291-1 IBM-5292-2 IBM-5555-B01 IBM-5555-C01 IBM-6153 IBM-6154 IBM-6155 IBM-AED IBM-3278-2-E IBM-3278-3-E IBM-3278-4-E IBM-3278-5-E IBM-3279-2-E IBM-3279-3-E IMLAC INFOTON-100 INFOTON-400 INFOTONKAS ISC-8001 LSI-ADM-1 LSI-ADM-11 LSI-ADM-12 LSI-ADM-2 LSI-ADM-20 LSI-ADM-22 LSI-ADM-220 LSI-ADM-3 LSI-ADM-31 LSI-ADM-3A LSI-ADM-42 LSI-ADM-5 MEMOREX-1240 MICROBEE MICROTERM-ACT-IV MICROTERM-ACT-V MICROTERM-ERGO-301 MICROTERM-MIME-1 MICROTERM-MIME-2 MICROTERM-ACT-5A MICROTERM-TWIST NEC-5520 NETRONICS NETWORK-VIRTUAL-TERMINAL OMRON-8025AG PERKIN-ELMER-550 PERKIN-ELMER-1100 PERKIN-ELMER-1200 PERQ PLASMA-PANEL QUME-SPRINT-5 QUME-101 QUME-102 SOROC SOROC-120 SOUTHWEST-TECHNICAL-PRODUCTS-CT82 SUN SUPERBEE SUPERBEE-III-M TEC TEKTRONIX-4006 TEKTRONIX-4010 TEKTRONIX-4012 TEKTRONIX-4013 TEKTRONIX-4014 TEKTRONIX-4023 TEKTRONIX-4024 TEKTRONIX-4025 TEKTRONIX-4027 TEKTRONIX-4105 TEKTRONIX-4107 TEKTRONIX-4110 TEKTRONIX-4112 TEKTRONIX-4113 TEKTRONIX-4114 TEKTRONIX-4115 TEKTRONIX-4125 TEKTRONIX-4404 TELERAY-1061 TELERAY-3700 TELERAY-3800 TELETEC-DATASCREEN TELETERM-1030 TELETYPE-33 TELETYPE-35 TELETYPE-37 TELETYPE-38 TELETYPE-40 TELETYPE-43 TELEVIDEO-910 TELEVIDEO-912 TELEVIDEO-920 TELEVIDEO-920B TELEVIDEO-920C TELEVIDEO-925 TELEVIDEO-955 TELEVIDEO-950 TELEVIDEO-970 TELEVIDEO-975 TERMINET-1200 TERMINET-300 TI-700 TI-733 TI-735 TI-743 TI-745 TI-800 TYCOM UNIVAC-DCT-500 VIDEO-SYSTEMS-1200 VIDEO-SYSTEMS-5000 VOLKER-CRAIG-303 VOLKER-CRAIG-303A VOLKER-CRAIG-404 VISUAL-200 VISUAL-55 WYSE-30 WYSE-50 WYSE-60 WYSE-75 WYSE-85 WYSE-99GT WYSE-100 WYSE-120 WYSE-120ES WYSE-150 WYSE-150ES WYSE-160 WYSE-160ES WYSE-185 WYSE-185ES WYSE-285 WYSE-285ES WYSE-325 WYSE-325ES WYSE-350 WYSE-370 XEROX-1720 XTERM ZENITH-H19 ZENITH-Z29 ZENTEC-30 RFC930 Solomon, M., and E. Wimmers, "Telnet Terminal Type Option", URL = ftp://ftp.isi.edu/in-notes/iana/assignments/terminal-type-names PROTOCOL AND SERVICE NAMES 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 . A protocol or service may be up to 40 characters taken from the set of uppercase letters, digits, and the punctuation character hyphen. It must start with a letter, and end with a letter or digit. ARGUS - ARGUS Protocol ARP - Address Resolution Protocol AUTH - Authentication Service BBN-RCC-MON - BBN RCC Monitoring BL-IDM - Britton Lee Intelligent Database Machine BOOTP - Bootstrap Protocol BOOTPC - Bootstrap Protocol Client BOOTPS - Bootstrap Protocol Server BR-SAT-MON - Backroom SATNET Monitoring CFTP - CFTP CHAOS - CHAOS Protocol CHARGEN - Character Generator Protocol CISCO-FNA - CISCO FNATIVE CISCO-TNA - CISCO TNATIVE CISCO-SYS - CISCO SYSMAINT CLOCK - DCNET Time Server Protocol CMOT - Common Mgmnt Info Ser and Prot over TCP/IP COOKIE-JAR - Authentication Scheme CSNET-NS - CSNET Mailbox Nameserver Protocol DAYTIME - Daytime Protocol DCN-MEAS - DCN Measurement Subsystems Protocol DCP - Device Control Protocol DGP - Dissimilar Gateway Protocol DISCARD - Discard Protocol DMF-MAIL - Digest Message Format for Mail DOMAIN - Domain Name System ECHO - Echo Protocol EGP - Exterior Gateway Protocol EHF-MAIL - Encoding Header Field for Mail EMCON - Emission Control Protocol EMFIS-CNTL - EMFIS Control Service EMFIS-DATA - EMFIS Data Service FCONFIG - Fujitsu Config Protocol FINGER - Finger Protocol FTP - File Transfer Protocol FTP-DATA - File Transfer Protocol Data GGP - Gateway Gateway Protocol GRAPHICS - Graphics Protocol HMP - Host Monitoring Protocol HOST2-NS - Host2 Name Server HOSTNAME - Hostname Protocol ICMP - Internet Control Message Protocol IGMP - Internet Group Management Protocol IGP - Interior Gateway Protocol IMAP2 - Interim Mail Access Protocol version 2 INGRES-NET - INGRES-NET Service IP - Internet Protocol IPCU - Internet Packet Core Utility IPPC - Internet Pluribus Packet Core IP-ARC - Internet Protocol on ARCNET IP-ARPA - Internet Protocol on ARPANET IP-CMPRS - Compressing TCP/IP Headers IP-DC - Internet Protocol on DC Networks IP-DVMRP - Distance Vector Multicast Routing Protocol IP-E - Internet Protocol on Ethernet Networks IP-EE - Internet Protocol on Exp. Ethernet Nets IP-FDDI - Transmission of IP over FDDI IP-HC - Internet Protocol on Hyperchannnel IP-IEEE - Internet Protocol on IEEE 802 IP-IPX - Transmission of 802.2 over IPX Networks IP-MTU - IP MTU Discovery Options IP-NETBIOS - Internet Protocol over NetBIOS Networks IP-SLIP - Transmission of IP over Serial Lines IP-WB - Internet Protocol on Wideband Network IP-X25 - Internet Protocol on X.25 Networks IRTP - Internet Reliable Transaction Protocol ISI-GL - ISI Graphics Language Protocol ISO-TP4 - ISO Transport Protocol Class 4 ISO-TSAP - ISO TSAP LA-MAINT - IMP Logical Address Maintenance LARP - Locus Address Resoultion Protocol LDP - Loader Debugger Protocol LEAF-1 - Leaf-1 Protocol LEAF-2 - Leaf-2 Protocol LINK - Link Protocol LOC-SRV - Location Service LOGIN - Login Host Protocol MAIL - Format of Electronic Mail Messages MERIT-INP - MERIT Internodal Protocol METAGRAM - Metagram Relay MIB - Management Information Base MIT-ML-DEV - MIT ML Device MFE-NSP - MFE Network Services Protocol MIT-SUBNET - MIT Subnet Support MIT-DOV - MIT Dover Spooler MPM - Internet Message Protocol (Multimedia Mail) MPM-FLAGS - MPM Flags Protocol MPM-SND - MPM Send Protocol MSG-AUTH - MSG Authentication Protocol MSG-ICP - MSG ICP Protocol MUX - Multiplexing Protocol NAMESERVER - Host Name Server NETBIOS-DGM - NETBIOS Datagram Service NETBIOS-NS - NETBIOS Name Service NETBIOS-SSN - NETBIOS Session Service NETBLT - Bulk Data Transfer Protocol NETED - Network Standard Text Editor NETRJS - Remote Job Service NI-FTP - NI File Transfer Protocol NI-MAIL - NI Mail Protocol NICNAME - Who Is Protocol NFILE - A File Access Protocol NNTP - Network News Transfer Protocol NSW-FE - NSW User System Front End NTP - Network Time Protocol NVP-II - Network Voice Protocol OSPF - Open Shortest Path First Interior GW Protocol PCMAIL - Pcmail Transport Protocol POP2 - Post Office Protocol - Version 2 POP3 - Post Office Protocol - Version 3 PPP - Point-to-Point Protocol PRM - Packet Radio Measurement PUP - PUP Protocol PWDGEN - Password Generator Protocol QUOTE - Quote of the Day Protocol RARP - A Reverse Address Resolution Protocol RATP - Reliable Asynchronous Transfer Protocol RE-MAIL-CK - Remote Mail Checking Protocol RDP - Reliable Data Protocol RIP - Routing Information Protocol RJE - Remote Job Entry RLP - Resource Location Protocol RTELNET - Remote Telnet Service RVD - Remote Virtual Disk Protocol SAT-EXPAK - Satnet and Backroom EXPAK SAT-MON - SATNET Monitoring SEP - Sequential Exchange Protocol SFTP - Simple File Transfer Protocol SGMP - Simple Gateway Monitoring Protocol SNMP - Simple Network Management Protocol SMI - Structure of Management Information SMTP - Simple Mail Transfer Protocol SQLSRV - SQL Service ST - Stream Protocol STATSRV - Statistics Service SU-MIT-TG - SU/MIT Telnet Gateway Protocol SUN-RPC - SUN Remote Procedure Call SUPDUP - SUPDUP Protocol SUR-MEAS - Survey Measurement SWIFT-RVF - Remote Virtual File Protocol TACACS-DS - TACACS-Database Service TACNEWS - TAC News TCP - Transmission Control Protocol TCP-ACO - TCP Alternate Checksum Option TELNET - Telnet Protocol TFTP - Trivial File Transfer Protocol THINWIRE - Thinwire Protocol TIME - Time Server Protocol TP-TCP - ISO Transport Service on top of the TCP TRUNK-1 - Trunk-1 Protocol TRUNK-2 - Trunk-2 Protocol UCL - University College London Protocol UDP - User Datagram Protocol NNTP - Network News Transfer Protocol USERS - Active Users Protocol UUCP-PATH - UUCP Path Service VIA-FTP - VIA Systems-File Transfer Protocol VISA - VISA Protocol VMTP - Versatile Message Transaction Protocol WB-EXPAK - Wideband EXPAK WB-MON - Wideband Monitoring XNET - Cross Net Debugger XNS-IDP - Xerox NS IDP URL = ftp://ftp.isi.edu/in-notes/iana/assignments/service-names Security Considerations Security issues are not discussed in this memo. Authors' Addresses Joyce K. Reynolds USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695 Phone: +1 310-822-1511 EMail: [email protected] Jon Postel USC/Information Sciences Institute 4676 Admiralty Way Marina del Rey, California 90292-6695
Userpage tools
Assigned Port Numbers for TCP and UDP (RFC 1700)Tcp and udp port number assignments. Port numbers in the TCP/IP environment are discussed and listed in RFC 1700 . The RFC is a 400Kb+ file and will be displayed as a text document in your browser. Use your browser BACK button to return to this page when you are done with the document. You should be able to begin reading the downloaded document in about 10 seconds although the entire document will require about 40 seconds to download. The Technical Compendium includes a broad discussion of the various protocols in the TCP/IP environment . Service Name and Transport Protocol Port Number Registry
Contact Information
|
IMAGES
VIDEO
COMMENTS
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 Ports (1024-49151), and the Dynamic and/or Private. Ports (49152-65535); the different uses of these ranges are described in.
RFC 7605 Recommendations for Transport Port Use August 2015 There are a few good examples of reasons that more directly suggest that not only is a port number assignment not necessary, but it is directly counter-indicated: o Assigned port numbers are not intended to differentiate performance variations within the same service, e.g., high-speed ...
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.
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 ...
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 ...
In computer networking, a port or port number is a number assigned to uniquely identify a connection endpoint and to direct data to a specific service. At the software level, ... Port assignments in RFC 349; Port number Assignment 1 Telnet 3 File transfer 5 Remote job entry 7
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 ...
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 ...
Service names are assigned on a first-come, first-served process, as documented in . Port numbers are assigned in various ways, based on three ranges: System Ports (0-1023), User Ports (1024-49151), and the Dynamic and/or Private Ports (49152-65535); the different uses of these ranges are described in [ RFC6335 ].
This is a list of TCP and UDP port numbers used by protocols for operation of network applications. The Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP) only need one port for duplex, bidirectional traffic.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 ...
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.
Range Operating system 49152-65535: suggested by RFC 6335 and the Internet Assigned Numbers Authority (IANA) 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: used by Solaris OS [citation needed] and AIX OS.
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 Ports (1024-49151), and the Dynamic and/or Private. Ports (49152-65535); the different uses of these ranges are described in.
RFC 2748 Values are assigned relative to the respective Client-type: Merge Strategies: RFC 6401 0-127: IETF Review. ... Fibre Channel Port Types: RFC 4044 1-9999: Specification Required. 10000-99999: Private Use. 100000 and higher: Reserved. ... IAX Calling Type of Number: RFC 5457 Expert Review (Expert: Cullen Jennings) IAX Cause Codes: RFC ...
RFC 6056 Port Randomization Recommendations January 2011 It is also worth noting that, provided adequate algorithms are in use, the larger the range from which ephemeral ports are selected, the smaller the chances of an attacker are to guess the selected port number. In scenarios in which a specific client establishes transport- protocol instances with a specific service at a server, the ...
Ports in the System Ports range (0-1023) are also available for assignment through IANA. Because the System Ports range is both the smallest and the most densely assigned, the requirements for new assignments are more strict than those for the User Ports range, and will only be granted under the "IETF Review" or "IESG Approval" procedures RFC5226.
So any dynamic allocation scheme may pick an unused port that happened to correspond to a port number that had been "assigned" but was currently unused. ... RFC946 Nedved, R., "Telnet Terminal Location Number Option", RFC 946, Carnegie-Mellon University, May 1985. [RDC1041] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041,
TCP And UDP Port Number Assignments. Port numbers in the TCP/IP environment are discussed and listed in RFC 1700. The RFC is a 400Kb+ file and will be displayed as a text document in your browser. Use your browser BACK button to return to this page when you are done with the document.
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. Dynamic port numbers (ranging from 49152-65535) are not assigned. Assignment of a port number does not in any way imply an endorsement of an application or ...
Some client stations initiate connections using a source TU port number in the range of 0-1023, and there are servers listening on TU port numbers in the range of 1024-65535. ... Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700, October, 1994. Braden, R., "Requirements for Internet Hosts -- Communication Layers", STD 3, RFC 1122 ...
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 Ports (1024-49151), and the Dynamic and/or Private. Ports (49152-65535); the different uses of these ranges are described in.
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 ...
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.
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 Ports (1024-49151), and the Dynamic and/or Private. Ports (49152-65535); the different uses of these ranges are described in.