Network Working Group
`Request for Comments: 1340
`Obsoletes RFCs: 1060, 1010, 990, 960,
`943, 923, 900, 870, 820, 790, 776, 770,
`762, 758,755, 750, 739, 604, 503, 433, 349
`Obsoletes IENs: 127, 117, 93
`
`Status of this Memo
`
`ASSIGNED NUMBERS
`
`J. Reynolds
`J. Postel
`ISI
`July 1992
`
` 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.
`
`Table of Contents
`
` INTRODUCTION................................................... 2
` Data Notations................................................. 3
` Special Addresses.............................................. 4
` VERSION NUMBERS................................................ 6
` PROTOCOL NUMBERS............................................... 7
` WELL KNOWN PORT NUMBERS........................................ 9
` REGISTERED PORT NUMBERS........................................ 23
` INTERNET MULTICAST ADDRESSES................................... 27
` IANA ETHERNET ADDRESS BLOCK.................................... 29
` IP TOS PARAMETERS.............................................. 30
` IP TIME TO LIVE PARAMETER...................................... 32
` DOMAIN SYSTEM PARAMETERS....................................... 33
` BOOTP PARAMETERS............................................... 35
` NETWORK MANAGEMENT PARAMETERS.................................. 36
` MILNET LOGICAL ADDRESSES....................................... 49
` MILNET LINK NUMBERS............................................ 50
` MILNET X.25 ADDRESS MAPPINGS................................... 51
` IEEE 802 NUMBERS OF INTEREST................................... 53
` ETHERNET NUMBERS OF INTEREST................................... 54
` ETHERNET VENDOR ADDRESS COMPONENTS............................. 57
` ETHERNET MULTICAST ADDRESSES................................... 60
` XNS PROTOCOL TYPES............................................. 62
` PROTOCOL/TYPE FIELD ASSIGNMENTS................................ 63
` PRONET 80 TYPE NUMBERS......................................... 64
` POINT-TO-POINT PROTOCOL FIELD ASSIGNMENTS...................... 65
` ADDRESS RESOLUTION PROTOCOL PARAMETERS......................... 69
` REVERSE ADDRESS RESOLUTION PROTOCOL OPERATION CODES............ 70
` DYNAMIC REVERSE ARP............................................ 70
` INVERSE ADDRESS RESOULUTION PROTOCOL........................... 70
`X.25 TYPE NUMBERS.............................................. 71
`
`Reynolds & Postel
`
`[Page 1]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 1 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` PUBLIC DATA NETWORK NUMBERS.................................... 72
` TELNET OPTIONS................................................. 75
` MAIL ENCRYPTION TYPES.......................................... 76
` MIME TYPES..................................................... 77
` CHARACTER SETS................................................. 79
` MACHINE NAMES.................................................. 83
` SYSTEM NAMES................................................... 87
` PROTOCOL AND SERVICE NAMES..................................... 88
` TERMINAL TYPE NAMES............................................ 92
` DOCUMENTS...................................................... 96
` PEOPLE.........................................................109
` Security Considerations........................................139
` Authors’ Addresses.............................................139
`
`INTRODUCTION
`
` This Network Working Group Request for Comments documents the
` currently assigned values from several series of numbers used in
` network protocol implementations. 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.
`
` Joyce K. Reynolds
` Internet Assigned Numbers Authority
` USC - Information Sciences Institute
` 4676 Admiralty Way
` Marina del Rey, California 90292-6695
`
` Phone: (310) 822-1511
`
` Electronic mail: IANA@ISI.EDU
`
` Most of the protocols mentioned here 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 "IAB Official
` Protocol Standards" [62].
`
` In the entries below, the name and mailbox of the responsible
` individual is indicated. The bracketed entry, e.g., [nn,iii], at the
` right hand margin of the page indicates a reference for the listed
` protocol, where the number ("nn") cites the document and the letters
` ("iii") cites the person. Whenever possible, the letters are a NIC
` Ident as used in the WhoIs (NICNAME) service.
`
`Reynolds & Postel [Page 2]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 2 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
`Data Notations
`
` The convention in the documentation of Internet Protocols is to
` express numbers in decimal and to picture data in "big-endian" order
` [21]. 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.
`
` 0 1 2 3
` 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
` +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
` | 1 | 2 | 3 | 4 |
` +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
` | 5 | 6 | 7 | 8 |
` +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
` | 9 | 10 | 11 | 12 |
` +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`
` Transmission Order of Bytes
`
` 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).
`
` 0 1 2 3 4 5 6 7
` +-+-+-+-+-+-+-+-+
` |1 0 1 0 1 0 1 0|
` +-+-+-+-+-+-+-+-+
`
` Significance of Bits
`
` 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.
`
`Reynolds & Postel [Page 3]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 3 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
`Special Addresses:
`
` There are five classes of IP addresses: Class A through Class E
` [119]. Of these, Class E addresses are reserved for experimental
` use. A gateway which is not participating in these experiments must
` ignore all datagrams with a Class E destination IP address. ICMP
` Destination Unreachable or ICMP Redirect messages must not result
` from receiving such datagrams.
`
` There are certain special cases for IP addresses [11]. These special
` cases can be concisely summarized using the earlier notation for an
` IP address:
`
` IP-address ::= { <Network-number>, <Host-number> }
`
` or
`
` IP-address ::= { <Network-number>, <Subnet-number>,
` <Host-number> }
`
` if we also use the notation "-1" to mean the field contains all 1
` bits. Some common special cases are as follows:
`
` (a) {0, 0}
`
` This host on this network. Can only be used as a source
` address (see note later).
`
` (b) {0, <Host-number>}
`
` Specified host on this network. Can only be used as a
` source address.
`
` (c) { -1, -1}
`
` Limited broadcast. Can only be used as a destination
` address, and a datagram with this address must never be
` forwarded outside the (sub-)net of the source.
`
` (d) {<Network-number>, -1}
`
` Directed broadcast to specified network. Can only be used
` as a destination address.
`
` (e) {<Network-number>, <Subnet-number>, -1}
`
` Directed broadcast to specified subnet. Can only be used as
` a destination address.
`
`Reynolds & Postel [Page 4]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 4 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` (f) {<Network-number>, -1, -1}
`
` Directed broadcast to all subnets of specified subnetted
` network. Can only be used as a destination address.
`
` (g) {127, <any>}
`
` Internal host loopback address. Should never appear outside
` a host.
`
`Reynolds & Postel [Page 5]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 5 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` VERSION NUMBERS
`
` In the Internet Protocol (IP) [45,105] 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
` ------- ------- ------- ----------
` 0 Reserved [JBP]
` 1-3 Unassigned [JBP]
` 4 IP Internet Protocol [105,JBP]
` 5 ST ST Datagram Mode [49,JWF]
` 6-14 Unassigned [JBP]
` 15 Reserved [JBP]
`
`Reynolds & Postel [Page 6]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 6 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` PROTOCOL NUMBERS
`
` In the Internet Protocol (IP) [45,105] there is a field, called
` Protocol, to identify the the next level protocol. This is an 8 bit
` field.
`
` Assigned Internet Protocol Numbers
`
` Decimal Keyword Protocol References
` ------- ------- -------- ----------
` 0 Reserved [JBP]
` 1 ICMP Internet Control Message [97,JBP]
` 2 IGMP Internet Group Management [43,JBP]
` 3 GGP Gateway-to-Gateway [60,MB]
` 4 IP IP in IP (encasulation) [JBP]
` 5 ST Stream [49,JWF]
` 6 TCP Transmission Control [106,JBP]
` 7 UCL UCL [PK]
` 8 EGP Exterior Gateway Protocol [123,DLM1]
` 9 IGP any private interior gateway [JBP]
` 10 BBN-RCC-MON BBN RCC Monitoring [SGC]
` 11 NVP-II Network Voice Protocol [22,SC3]
` 12 PUP PUP [8,XEROX]
` 13 ARGUS ARGUS [RWS4]
` 14 EMCON EMCON [BN7]
` 15 XNET Cross Net Debugger [56,JFH2]
` 16 CHAOS Chaos [NC3]
` 17 UDP User Datagram [104,JBP]
` 18 MUX Multiplexing [23,JBP]
` 19 DCN-MEAS DCN Measurement Subsystems [DLM1]
` 20 HMP Host Monitoring [59,RH6]
` 21 PRM Packet Radio Measurement [ZSU]
` 22 XNS-IDP XEROX NS IDP [133,XEROX]
` 23 TRUNK-1 Trunk-1 [BWB6]
` 24 TRUNK-2 Trunk-2 [BWB6]
` 25 LEAF-1 Leaf-1 [BWB6]
` 26 LEAF-2 Leaf-2 [BWB6]
` 27 RDP Reliable Data Protocol [138,RH6]
` 28 IRTP Internet Reliable Transaction [79,TXM]
` 29 ISO-TP4 ISO Transport Protocol Class 4 [63,RC77]
` 30 NETBLT Bulk Data Transfer Protocol [20,DDC1]
` 31 MFE-NSP MFE Network Services Protocol [124,BCH2]
` 32 MERIT-INP MERIT Internodal Protocol [HWB]
` 33 SEP Sequential Exchange Protocol [JC120]
` 34 3PC Third Party Connect Protocol [SAF3]
` 35 IDPR Inter-Domain Policy Routing Protocol [MXS1]
` 36 XTP XTP [GXC]
` 37 DDP Datagram Delivery Protocol [WXC]
`
`Reynolds & Postel [Page 7]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 7 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` 38 IDPR-CMTP IDPR Control Message Transport Proto [MXS1]
` 39 TP++ TP++ Transport Protocol [DXF]
` 40 IL IL Transport Protocol [DXP2]
` 41-60 Unassigned [JBP]
` 61 any host internal protocol [JBP]
` 62 CFTP CFTP [50,HCF2]
` 63 any local network [JBP]
` 64 SAT-EXPAK SATNET and Backroom EXPAK [SHB]
` 65 KRYPTOLAN Kryptolan [PXL1]
` 66 RVD MIT Remote Virtual Disk Protocol [MBG]
` 67 IPPC Internet Pluribus Packet Core [SHB]
` 68 any distributed file system [JBP]
` 69 SAT-MON SATNET Monitoring [SHB]
` 70 VISA VISA Protocol [GXT1]
` 71 IPCV Internet Packet Core Utility [SHB]
` 72 CPNX Computer Protocol Network Executive [DXM2]
` 73 CPHB Computer Protocol Heart Beat [DXM2]
` 74 WSN Wang Span Network [VXD]
` 75 PVP Packet Video Protocol [SC3]
` 76 BR-SAT-MON Backroom SATNET Monitoring [SHB]
` 77 SUN-ND SUN ND PROTOCOL-Temporary [WM3]
` 78 WB-MON WIDEBAND Monitoring [SHB]
` 79 WB-EXPAK WIDEBAND EXPAK [SHB]
` 80 ISO-IP ISO Internet Protocol [MTR]
` 81 VMTP VMTP [DRC3]
` 82 SECURE-VMTP SECURE-VMTP [DRC3]
` 83 VINES VINES [BXH]
` 84 TTP TTP [JXS]
` 85 NSFNET-IGP NSFNET-IGP [HWB]
` 86 DGP Dissimilar Gateway Protocol [74,ML109]
` 87 TCF TCF [GAL5]
` 88 IGRP IGRP [18,GXS]
` 89 OSPFIGP OSPFIGP [83,JTM4]
` 90 Sprite-RPC Sprite RPC Protocol [143,BXW]
` 91 LARP Locus Address Resolution Protocol [BXH]
` 92 MTP Multicast Transport Protocol [SXA]
` 93 AX.25 AX.25 Frames [BK29]
` 94 IPIP IP-within-IP Encapsulation Protocol [JXI1]
` 95 MICP Mobile Internetworking Control Pro. [JXI1]
` 96 AES-SP3-D AES Security Protocol 3-D [HXH]
` 97 ETHERIP Ethernet-within-IP Encapsulation [RXH1]
` 98 ENCAP Encapsulation Header [148,RXB3]
` 99-254 Unassigned [JBP]
` 255 Reserved [JBP]
`
`Reynolds & Postel [Page 8]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 8 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` 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 [45,106] 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 [46,104].
`
`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
` ------- ------- ----------- ----------
` 0/tcp Reserved [JBP]
` 0/udp Reserved [JBP]
` tcpmux 1/tcp TCP Port Service Multiplexer [MKL]
` tcpmux 1/udp TCP Port Service Multiplexer [MKL]
` compressnet 2/tcp Management Utility [BV15]
` compressnet 2/udp Management Utility [BV15]
` compressnet 3/tcp Compression Process [BV15]
` compressnet 3/udp Compression Process [BV15]
` 4/tcp Unassigned [JBP]
` 4/udp Unassigned [JBP]
` rje 5/tcp Remote Job Entry [12,JBP]
` rje 5/udp Remote Job Entry [12,JBP]
` 6/tcp Unassigned [JBP]
` 6/udp Unassigned [JBP]
` echo 7/tcp Echo [95,JBP]
` echo 7/udp Echo [95,JBP]
` 8/tcp Unassigned [JBP]
` 8/udp Unassigned [JBP]
` discard 9/tcp Discard [94,JBP]
` discard 9/udp Discard [94,JBP]
` 10/tcp Unassigned [JBP]
` 10/udp Unassigned [JBP]
` systat 11/tcp Active Users [89,JBP]
`
`Reynolds & Postel [Page 9]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 9 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` systat 11/udp Active Users [89,JBP]
` 12/tcp Unassigned [JBP]
` 12/udp Unassigned [JBP]
` daytime 13/tcp Daytime [93,JBP]
` daytime 13/udp Daytime [93,JBP]
` 14/tcp Unassigned [JBP]
` 14/udp Unassigned [JBP]
` 15/tcp Unassigned [was netstat] [JBP]
` 15/udp Unassigned [JBP]
` 16/tcp Unassigned [JBP]
` 16/udp Unassigned [JBP]
` qotd 17/tcp Quote of the Day [100,JBP]
` qotd 17/udp Quote of the Day [100,JBP]
` msp 18/tcp Message Send Protocol [RXN]
` msp 18/udp Message Send Protocol [RXN]
` chargen 19/tcp Character Generator [92,JBP]
` chargen 19/udp Character Generator [92,JBP]
` ftp-data 20/tcp File Transfer [Default Data] [96,JBP]
` ftp-data 20/udp File Transfer [Default Data] [96,JBP]
` ftp 21/tcp File Transfer [Control] [96,JBP]
` ftp 21/udp File Transfer [Control] [96,JBP]
` 22/tcp Unassigned [JBP]
` 22/udp Unassigned [JBP]
` telnet 23/tcp Telnet [112,JBP]
` telnet 23/udp Telnet [112,JBP]
` 24/tcp any private mail system [RA11]
` 24/udp any private mail system [RA11]
` smtp 25/tcp Simple Mail Transfer [102,JBP]
` smtp 25/udp Simple Mail Transfer [102,JBP]
` 26/tcp Unassigned [JBP]
` 26/udp Unassigned [JBP]
` nsw-fe 27/tcp NSW User System FE [24,RHT]
` nsw-fe 27/udp NSW User System FE [24,RHT]
` 28/tcp Unassigned [JBP]
` 28/udp Unassigned [JBP]
` msg-icp 29/tcp MSG ICP [85,RHT]
` msg-icp 29/udp MSG ICP [85,RHT]
` 30/tcp Unassigned [JBP]
` 30/udp Unassigned [JBP]
` msg-auth 31/tcp MSG Authentication [85,RHT]
` msg-auth 31/udp MSG Authentication [85,RHT]
` 32/tcp Unassigned [JBP]
` 32/udp Unassigned [JBP]
` dsp 33/tcp Display Support Protocol [EXC]
` dsp 33/udp Display Support Protocol [EXC]
` 34/tcp Unassigned [JBP]
` 34/udp Unassigned [JBP]
` 35/tcp any private printer server [JBP]
`
`Reynolds & Postel [Page 10]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 10 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` 35/udp any private printer server [JBP]
` 36/tcp Unassigned [JBP]
` 36/udp Unassigned [JBP]
` time 37/tcp Time [108,JBP]
` time 37/udp Time [108,JBP]
` 38/tcp Unassigned [JBP]
` 38/udp Unassigned [JBP]
` rlp 39/tcp Resource Location Protocol [MA]
` rlp 39/udp Resource Location Protocol [MA]
` 40/tcp Unassigned [JBP]
` 40/udp Unassigned [JBP]
` graphics 41/tcp Graphics [129,JBP]
` graphics 41/udp Graphics [129,JBP]
` nameserver 42/tcp Host Name Server [99,JBP]
` nameserver 42/udp Host Name Server [99,JBP]
` nicname 43/tcp Who Is [55,ANM2]
` nicname 43/udp Who Is [55,ANM2]
` mpm-flags 44/tcp MPM FLAGS Protocol [JBP]
` mpm-flags 44/udp MPM FLAGS Protocol [JBP]
` mpm 45/tcp Message Processing Module [recv] [98,JBP]
` mpm 45/udp Message Processing Module [recv] [98,JBP]
` mpm-snd 46/tcp MPM [default send] [98,JBP]
` mpm-snd 46/udp MPM [default send] [98,JBP]
` ni-ftp 47/tcp NI FTP [134,SK8]
` ni-ftp 47/udp NI FTP [134,SK8]
` 48/tcp Unassigned [JBP]
` 48/udp Unassigned [JBP]
` login 49/tcp Login Host Protocol [PHD1]
` login 49/udp Login Host Protocol [PHD1]
` re-mail-ck 50/tcp Remote Mail Checking Protocol [171,SXD1]
` re-mail-ck 50/udp Remote Mail Checking Protocol [171,SXD1]
` la-maint 51/tcp IMP Logical Address Maintenance [76,AGM]
` la-maint 51/udp IMP Logical Address Maintenance [76,AGM]
` xns-time 52/tcp XNS Time Protocol [SXA]
` xns-time 52/udp XNS Time Protocol [SXA]
` domain 53/tcp Domain Name Server [81,95,PM1]
` domain 53/udp Domain Name Server [81,95,PM1]
` xns-ch 54/tcp XNS Clearinghouse [SXA]
` xns-ch 54/udp XNS Clearinghouse [SXA]
` isi-gl 55/tcp ISI Graphics Language [7,RB9]
` isi-gl 55/udp ISI Graphics Language [7,RB9]
` xns-auth 56/tcp XNS Authentication [SXA]
` xns-auth 56/udp XNS Authentication [SXA]
` 57/tcp any private terminal access [JBP]
` 57/udp any private terminal access [JBP]
` xns-mail 58/tcp XNS Mail [SXA]
` xns-mail 58/udp XNS Mail [SXA]
` 59/tcp any private file service [JBP]
`
`Reynolds & Postel [Page 11]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 11 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` 59/udp any private file service [JBP]
` 60/tcp Unassigned [JBP]
` 60/udp Unassigned [JBP]
` ni-mail 61/tcp NI MAIL [5,SK8]
` ni-mail 61/udp NI MAIL [5,SK8]
` acas 62/tcp ACA Services [EXW]
` acas 62/udp ACA Services [EXW]
` via-ftp 63/tcp VIA Systems - FTP [DXD]
` via-ftp 63/udp VIA Systems - FTP [DXD]
` covia 64/tcp Communications Integrator (CI) [TXD]
` covia 64/udp Communications Integrator (CI) [TXD]
` tacacs-ds 65/tcp TACACS-Database Service [3,KH43]
` tacacs-ds 65/udp TACACS-Database Service [3,KH43]
` sql*net 66/tcp Oracle SQL*NET [JFH2]
` sql*net 66/udp Oracle SQL*NET [JFH2]
` bootps 67/tcp Bootstrap Protocol Server [36,WJC2]
` bootps 67/udp Bootstrap Protocol Server [36,WJC2]
` bootpc 68/tcp Bootstrap Protocol Client [36,WJC2]
` bootpc 68/udp Bootstrap Protocol Client [36,WJC2]
` tftp 69/tcp Trivial File Transfer [126,DDC1]
` tftp 69/udp Trivial File Transfer [126,DDC1]
` gopher 70/tcp Gopher [MXC1]
` gopher 70/udp Gopher [MXC1]
` netrjs-1 71/tcp Remote Job Service [10,RTB3]
` netrjs-1 71/udp Remote Job Service [10,RTB3]
` netrjs-2 72/tcp Remote Job Service [10,RTB3]
` netrjs-2 72/udp Remote Job Service [10,RTB3]
` netrjs-3 73/tcp Remote Job Service [10,RTB3]
` netrjs-3 73/udp Remote Job Service [10,RTB3]
` netrjs-4 74/tcp Remote Job Service [10,RTB3]
` netrjs-4 74/udp Remote Job Service [10,RTB3]
` 75/tcp any private dial out service [JBP]
` 75/udp any private dial out service [JBP]
` 76/tcp Unassigned [JBP]
` 76/udp Unassigned [JBP]
` 77/tcp any private RJE service [JBP]
` 77/udp any private RJE service [JBP]
` vettcp 78/tcp vettcp [CXL1]
` vettcp 78/udp vettcp [CXL1]
` finger 79/tcp Finger [52,KLH]
` finger 79/udp Finger [52,KLH]
` www 80/tcp World Wide Web HTTP [TXL]
` www 80/udp World Wide Web HTTP [TXL]
` hosts2-ns 81/tcp HOSTS2 Name Server [EAK1]
` hosts2-ns 81/udp HOSTS2 Name Server [EAK1]
` xfer 82/tcp XFER Utility [TXS2]
` xfer 82/udp XFER Utility [TXS2]
` mit-ml-dev 83/tcp MIT ML Device [DXR3]
`
`Reynolds & Postel [Page 12]
`
`Packet Intelligence LLC Exh 2065
`Juniper Networks, Inc., et al v. Packet Intelligence LLC
`IPR2020-00337
`Page 12 of 139
`
`

`

`
`RFC 1340 Assigned Numbers July 1992
`
` mit-ml-dev 83/udp MIT ML Device [DXR3]
` ctf