3/26/22, 6:02 PM
`
`RFC 790 - Assigned numbers
`
`Network Working Group
`Request for Comments: 790
`
`Obsoletes RFCs: 776, 770, 762, 758,
`755, 750, 739, 604, 503, 433, 349
`Obsoletes IENs: 127, 117, 93
`
`J. Postel
`ISI
`September 1981
`
`ASSIGNED NUMBERS
`
`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 Jon Postel. The assignment of
`numbers is also handled by Jon.
`If you are developing a protocol or
`application that will require the use of a link, socket, port, protocol,
`or network number please contact Jon to receive a number assignment.
`
`Jon Postel
`USC - Information Sciences Institute
`4676 Admiralty Way
`Marina del Rey, California 90291
`
`phone: (213) 822-1511
`
`ARPANET mail: POSTEL@ISIF
`
`Most of the protocols mentioned here are documented in the RFC series of
`notes. The more prominent and more generally used are documented in the
`Protocol Handbook [17] prepared by the Network Information Center {NIC).
`Some of the items listed are undocumented.
`In all cases the name and
`mailbox of the responsible individual is indicated.
`In the lists that
`follow, a bracketed entry, e.g., [17,iii], at the right hand margin of
`the page indicates a reference for the listed protocol, where the number
`cites the document and the "iii" cites the person.
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`1/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 1 of 16
`
`

`

`3/26/22, 6:02 PM
`
`Postel
`
`RFC 790 - Assigned numbers
`
`[Page 1]
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`2/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 2 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Network Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`ASSIGNED NETWORK NUMBERS
`
`This list of network numbers is used in the internet address [33].
`The Internet Protocol {IP) uses a 32 bit address and divides that
`address into a network part and a "rest" or local address part. The
`division takes 3 forms or classes.
`
`The first type, or class a, of address has a 7-bit network number
`and a 24-bit local address. This allows 128 class a networks.
`
`3
`2
`1
`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
`+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`I 0 I
`NETWORK
`Local Address
`+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`
`Class A Address
`
`The second type, or class b, of address has a 14-bit network
`number and a 16-bit local address. This allows 16,384 class b
`networks.
`
`3
`2
`1
`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
`+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`I 1 0 I
`NETWORK
`Local Address
`+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`
`Class B Address
`
`The third type, or class c, of address has a 21-bit network number
`and a 8-bit local address. This allows 2,097,152 class c
`networks.
`
`3
`2
`1
`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
`+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`I Local Address I
`11 1 01
`NETWORK
`+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
`
`Class C Address
`
`One notation for internet host addresses commonly used divides the
`32-bit address into four 8-bit fields and specifies the value of each
`field as a decimal number with the fields separated by periods. For
`example, the internet address of ISIF is 010.020.000.052.
`
`This notation will be used in the listing of assigned network
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 2]
`
`3/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 3 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Network Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`numbers. The class a networks will have nnn.rrr.rrr.rrr, the class b
`networks will have nnn.nnn.rrr.rrr, and the class c networks will
`have nnn.nnn.nnn.rrr, where nnn represents part or all of a network
`number and rrr represents part or all of a local address or rest
`field.
`
`Assigned Network Numbers
`
`Class A Networks
`
`BBN-PR
`SF-PR-1
`BBN-RCC
`SATNET
`SILL-PR
`SF-PR-2
`CHAOS
`CLARKNET
`BRAGG-PR
`ARPANET
`UCLNET
`CYCLADES
`
`Internet Address Name
`----------------
`000.rrr.rrr.rrr
`001.rrr.rrr.rrr
`002.rrr.rrr.rrr
`003.rrr.rrr.rrr
`004.rrr.rrr.rrr
`005.rrr.rrr.rrr
`006.rrr.rrr.rrr
`007.rrr.rrr.rrr
`008.rrr.rrr.rrr
`009.rrr.rrr.rrr
`010.rrr.rrr.rrr
`011.rrr.rrr.rrr
`012.rrr.rrr.rrr
`013.rrr.rrr.rrr
`TELENET
`014.rrr.rrr.rrr
`EPSS
`015.rrr.rrr.rrr
`DATAPAC
`016.rrr.rrr.rrr
`TRANSPAC
`017.rrr.rrr.rrr
`LCSNET
`018.rrr.rrr.rrr
`TYMNET
`019.rrr.rrr.rrr
`020.rrr.rrr.rrr DC-PR
`021.rrr.rrr.rrr
`EDN
`022.rrr.rrr.rrr DIALNET
`023.rrr.rrr.rrr MITRE
`024.rrr.rrr.rrr
`BBN-LOCAL
`025.rrr.rrr.rrr
`RSRE-PPSN
`026.rrr.rrr.rrr AUTODIN-II
`027.rrr.rrr.rrr
`NOSC-LCCN
`028.rrr.rrr.rrr WIDEBAND
`029.rrr.rrr.rrr
`DCN-COMSAT
`030.rrr.rrr.rrr
`DCN-UCL
`031.rrr.rrr.rrr
`BBN-SAT-TEST
`032.rrr.rrr.rrr UCL-CRl
`033.rrr.rrr.rrr UCL-CR2
`034.rrr.rrr.rrr MATNET
`035.rrr.rrr.rrr
`NULL
`
`Network
`
`References
`
`[ J BP]
`Reserved
`[DCA2]
`BBN Packet Radio Network
`[JEM]
`SF Packet Radio Network (1)
`[SGC]
`BBN RCC Network
`[DMll]
`Atlantic Satellite Network
`Ft. Sill Packet Radio Network[JEM]
`SF Packet Radio Network (2)
`[JEM]
`MIT CHAOS Network
`[MOON]
`SATNET subnet for Clarksburg[DMll]
`Ft. Bragg Packet Radio Net
`[JEM]
`ARPANET
`[17,1,VGC]
`University College London
`[PK]
`CYCLADES
`[VGC]
`Unassigned
`[ J BP]
`TELE NET
`[VGC]
`British Post Office EPSS
`[PK]
`DATAPAC
`[VGC]
`TRANSPAC
`[VGC]
`MIT LCS Network
`[43,10,DDC2]
`TYMNET
`[VGC]
`D.C. Packet Radio Network
`[VGC]
`DCEC EDN
`[ECS]
`DIALNET
`[26,16,MRC]
`MITRE Cablenet
`[44,APS]
`BBN Local Network
`[SGC]
`RSRE / PPSN
`[BD2]
`AUTODIN II
`[ECS]
`NOSC / LCCN
`[KTP]
`Wide Band Satellite Network [CJW2]
`COMSAT Dist. Comp. Network
`[DLMl]
`UCL Dist. Comp. Network
`[PK]
`BBN SATNET Test Network
`[DMll]
`UCL Cambridge Ring 1
`[PK]
`UCL Cambridge Ring 2
`[PK]
`Mobile Access Terminal Net
`[DMll]
`UCL/RSRE Null Network
`[BD2]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 3]
`
`4/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 4 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Network Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`Stanford University Ethernet
`036.rrr.rrr.rrr
`SU-NET
`Digital Equipment Network
`DECNET
`037.rrr.rrr.rrr
`Test Digital Equipment Net
`038.rrr.rrr.rrr DECNET-TEST
`SRI Local Network
`039.rrr.rrr.rrr
`SRINET
`CISL Multics Network
`040.rrr.rrr.rrr CISLNET
`BBN Local Network Testbed
`041.rrr.rrr.rrr
`BBN-LN-TEST
`LLL-Sl-NET
`042.rrr.rrr.rrr
`SlNET
`COMSAT INTELPOST
`043.rrr.rrr.rrr
`INTEL POST
`Amature Radio Experiment
`044.rrr.rrr.rrr
`AMPRNET
`044.rrr.rrr.rrr-126.rrr.rrr.rrr Unassigned
`127.rrr.rrr.rrr
`Reserved
`
`[MRC]
`[DRL]
`[DRL]
`[GEOF]
`[CH2]
`[KTP]
`[EAK]
`[DLMl]
`Net
`[HM]
`[JBP]
`[JBP]
`
`Class B Networks
`
`Internet Address Name
`
`Network
`
`References
`
`128.000.rrr.rrr
`Reserved
`128.001.rrr.rrr-128.254.rrr.rrr Unassigned
`191.255.rrr.rrr
`Reserved
`
`[JBP]
`[JBP]
`[JBP]
`
`Class C Networks
`
`Internet Address Name
`
`Network
`
`References
`
`192.000.001.rrr
`Reserved
`192.000.001.rrr-223.255.254.rrr Unassigned
`223.255.255.rrr
`Reserved
`
`Other Reserved Internet Addresses
`
`Internet Address Name
`
`Network
`
`224.000.000.000-255.255.255.255 Reserved
`
`[JBP]
`[JBP]
`[JBP]
`
`References
`
`[JBP]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 4]
`
`5/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 5 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Internet Version Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`ASSIGNED INTERNET VERSION NUMBERS
`
`In the Internet Protocol {IP) [33] 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 Octal
`-------
`0
`1-3
`4
`5
`6-14
`15
`
`0
`1-3
`4
`5
`6-16
`17
`
`Version
`-------
`Reserved
`Unassigned
`Internet Protocol
`ST Datagram Mode
`Unassigned
`Reserved
`
`References
`----------
`[JBP]
`[JBP]
`[33,JBP]
`[20,JWF]
`[JBP]
`[JBP]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 5]
`
`6/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 6 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Internet Protocol Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`ASSIGNED INTERNET PROTOCOL NUMBERS
`
`In the Internet Protocol {IP) [33] there is a field, called Protocol,
`to identify the the next level protocol. This is an 8 bit field.
`
`Assigned Internet Protocol Numbers
`
`Octal
`
`Decimal
`-------
`0
`0
`1
`1
`2
`2
`3
`3
`4
`4
`5
`5
`6
`6
`7
`7
`10
`8
`11
`9
`12
`10
`11
`13
`14
`12
`15
`13
`16
`14
`17
`15
`20
`16
`21
`17
`22
`18
`23
`19
`24
`20
`21-62
`25-76
`77
`63
`100
`64
`101
`65
`66-68 102-104
`69
`105
`70
`106
`107
`71
`72-75 110-113
`76
`114
`77
`115
`78
`116
`79
`117
`80-254 120-376
`255
`377
`
`Protocol Numbers
`----------------
`Reserved
`ICMP
`Unassigned
`Gateway-to-Gateway
`CMCC Gateway Monitoring Message
`ST
`TCP
`UCL
`Unassigned
`Secure
`BBN RCC Monitoring
`NVP
`PUP
`Pluribus
`Telenet
`XNET
`Chaos
`User Datagram
`Multiplexing
`DCN
`TAC Monitoring
`Unassigned
`any local network
`SATNET and Backroom EXPAK
`MIT Subnet Support
`Unassigned
`SATNET Monitoring
`Unassigned
`Internet Packet Core Utility
`Unassigned
`Backroom SATNET Monitoring
`Unassigned
`WIDEBAND Monitoring
`WIDEBAND EXPAK
`Unassigned
`Reserved
`
`References
`----------
`[JBP]
`[53,JBP]
`[JBP]
`[48,49,VMS]
`[18,19,DFP]
`[20,JWF]
`[34,JBP]
`[PK]
`[JBP]
`[VGC]
`[VMS]
`[12,DC]
`[4,EAT3]
`[RDB2]
`[RDB2]
`[25,JFH2]
`[MOON]
`[42,JBP]
`[13,JBP]
`[DLMl]
`[55,RH6]
`[JBP]
`[JBP]
`[DMll]
`[NC3]
`[JBP]
`[DMll]
`[JBP]
`[DMll]
`[JBP]
`[DMll]
`[JBP]
`[DMll]
`[DMll]
`[JBP]
`[JBP]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 6]
`
`7/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 7 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Port or Socket Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`ASSIGNED PORT or SOCKET NUMBERS
`
`Ports are used in the TCP [34] and sockets are used in the AHHP
`[28,17] to name the ends of logical connections which carry long term
`conversations. For the purpose of providing services to unknown
`callers a service contact socket is defined. This list specifies the
`port or socket used by the server process as its contact socket.
`In
`the AHHP an Initial Connection Procedure ICP [39,17] is used between
`the user process and the server process to make the initial contact
`and establish the long term connections leaving the contact socket
`free to handle other callers.
`In the TCP no ICP is necessary since a
`port may engage in many simultaneous connections.
`
`To the extent possible these same port assignments are used with UDP
`[42].
`
`The assigned ports/sockets use a small part of the possible
`port/socket numbers. The assigned ports/sockets have all except the
`low order eight bits cleared to zero. The low order eight bits are
`specified here.
`
`Socket Assignments:
`
`General Assignments:
`
`Decimal Octal
`-------
`0-63
`64-131
`132-223
`224-255
`
`0-77
`100-203
`204-337
`340-377
`
`Description
`-----------
`Network Wide Standard Function
`Hosts Specific Functions
`Reserved for Future Use
`Any Experimental Function
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 7]
`
`8/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 8 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Port or Socket Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`Specific Assignments:
`
`Network Standard Functions
`
`Decimal Octal
`
`Description
`
`References
`
`1
`3
`5
`7
`9
`11
`13
`15
`17
`19
`21
`23
`25
`27
`29
`31
`33
`35
`37
`39
`41
`42
`43
`45
`47
`49
`51
`53
`55
`57
`59
`61-63
`
`1
`3
`5
`7
`11
`13
`15
`17
`21
`23
`25
`27
`31
`33
`35
`37
`41
`43
`45
`47
`51
`52
`53
`55
`57
`61
`63
`65
`67
`71
`73
`75-77
`
`or TTYTST
`
`Old Telnet
`Old File Transfer
`Remote Job Entry
`Echo
`Discard
`Who is on or SYSTAT
`Date and Time
`Who is up or NETSTAT
`Short Text Message
`Character generator
`New File Transfer
`New Telnet
`SMTP
`NSW User System w/COMPASS FE
`MSG-3 ICP
`MSG-3 Authentication
`Unassigned
`IO Station Spooler
`Time Server
`Unassigned
`Graphics
`Name Server
`Whois
`Message Processing Module
`NI FTP
`RAND Network Graphics Conference
`Message Generator Control
`AUTODIN II FTP
`ISI Graphics Language
`MTP
`New MIT Host Status
`Unassigned
`
`[40,JBP]
`[27,11,24,JBP]
`[6,17,JBP]
`[35,JBP]
`[32,JBP]
`[JBP]
`[JBP]
`[JBP]
`[JBP]
`[31,JBP]
`[36,JBP]
`[41,JBP]
`[54,JBP]
`[14,RHT]
`[29,RHT]
`[29,RHT]
`[JBP]
`[JBP]
`[22,JBP]
`[JBP]
`[46,17,JBP]
`[38,JBP]
`[JAKE]
`[37,JBP]
`[50,CJB]
`[30,MO2]
`[52,DFP]
`[21,EC5]
`[3,RB6]
`[45,JBP]
`[SWG]
`[JBP]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 8]
`
`9/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 9 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Port or Socket Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`Host Specific Functions
`
`Decimal Octal
`-------
`65
`67
`69
`69
`71
`73
`75
`77
`79
`81
`83
`85
`87
`89
`91
`93
`95
`97
`99
`101
`103
`105
`107
`109
`111
`113
`115-129
`131
`
`101
`103
`105
`105
`107
`111
`113
`115
`117
`121
`123
`125
`127
`131
`133
`135
`137
`141
`143
`145
`147
`151
`153
`155
`157
`161
`163-201
`203
`
`Description
`-----------
`Unassigned
`Datacomputer at CCA
`Unassigned
`Trivial File Transfer
`NETRJS {EBCDIC) at UCLA-CCN
`NETRJS (ASCII-68) at UCLA-CCN
`NETRJS (ASCII-63) at UCLA-CCN
`any private RJE server
`Name or Finger
`Unassigned
`MIT ML Device
`MIT ML Device
`any terminal link
`SU/MIT Telnet Gateway
`MIT Dover Spooler
`BBN RCC Accounting
`SUPDUP
`Datacomputer Status
`CADC - NIFTP via UCL
`NPL - NIFTP via UCL
`BNPL - NIFTP via UCL
`CAMBRIDGE - NIFTP via UCL
`HARWELL - NIFTP via UCL
`SWURCC - NIFTP via UCL
`ESSEX - NIFTP via UCL
`RUTHERFORD - NIFTP via UCL
`Unassigned
`Datacomputer
`
`Reserved for Future
`
`Use
`
`Decimal Octal
`-------
`132-223
`
`204-337
`
`Description
`-----------
`Reserved
`
`References
`----------
`[JBP]
`[ 8, JZS]
`[JBP]
`[47,KRS]
`[5,17,RTB]
`[5,17,RTB]
`[5,17,RTB]
`[JBP]
`[23,17,KLH]
`[JBP]
`[MOON]
`[MOON]
`[JBP]
`[MRC]
`[EBM]
`[DT]
`[15,MRC]
`[ 8, JZS]
`[PLH]
`[PLH]
`[PLH]
`[PLH]
`[PLH]
`[PLH]
`[PLH]
`[PLH]
`[JBP]
`[ 8, JZS]
`
`References
`----------
`[JBP]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 9]
`
`10/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 10 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Port or Socket Numbers
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`Experimental Functions
`
`Decimal
`-------
`224-239
`241
`243
`245
`247
`249-255
`
`Octal
`
`Description
`-----------
`340-357 Unassigned
`361
`NCP Measurement
`Survey Measurement
`363
`LINK
`365
`367
`TIPSRV
`RSEXEC
`371-377
`
`ASSIGNED LINK NUMBERS
`
`References
`
`[JBP]
`[9,JBP]
`[ 2,AV]
`[7,RDB2]
`[RHT]
`[51,RHT]
`
`The word "link" here refers to a field in the original ARPANET
`Host/IMP interface leader. The link was originally defined as an 8
`bit field. Some time after the ARPANET Host-to-Host (AHHP) protocol
`was defined and, by now, some time ago the definition of this field
`was changed to "Message-ID" and the length to 12 bits. The name link
`now refers to the high order 8 bits of this 12 bit message-id field.
`The low order 4 bits of the message-id field are to be zero unless
`specifically specified otherwise for the particular protocol used on
`that link. The Host/IMP interface is defined in BBN report 1822 [1].
`
`Link Assignments:
`
`Decimal Octal
`-------
`0
`1
`2-71
`72-150
`151
`152
`153
`154
`155
`156-158
`159-191
`192-195
`196-255
`224-255
`248-255
`
`Description
`-----------
`AHHP Control Messages
`0
`Reserved
`1
`AHHP Regular Messages
`2-107
`110-226 Reserved
`227
`CHAOS Protocol
`230
`PARC Universal Protocol
`231
`TIP Status Reporting
`232
`TIP Accounting
`233
`Internet Protocol (regular)
`234-236
`Internet Protocol (experimental)
`237-277 Measurements
`300-303 Unassigned
`Experimental Protocols
`304-377
`NVP
`340-377
`370-377 Network Maintenance
`
`References
`----------
`[ 28, 17, JBP]
`[JBP]
`[ 28, 17, JBP]
`[JBP]
`[MOON]
`[4,EAT3]
`[JGH]
`[JGH]
`[33,JBP]
`[33,JBP]
`[9,VGC]
`[JBP]
`[JBP]
`[12,17,DC]
`[JGH]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 10]
`
`11/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 11 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Documents
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`DOCUMENTS
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`[8]
`
`[9]
`
`[10]
`
`[11]
`
`[12]
`
`BBN, "Specifications for the Interconnection of a Host and an
`IMP", Report 1822, Bolt Beranek and Newman, Cambridge,
`Massachusetts, May 1978.
`
`Bhushan, A., "A Report on the Survey Project", RFC 530,
`NIC 17375, 22 June 1973.
`
`Bisbey, R., D. Hollingworth, and B. Britt, "Graphics Language
`(version 2.1)", ISI/TM-80-18, USC/Information Sciences
`Institute, July 1980.
`
`Boggs, D., J. Shoch, E. Taft, and R. Metcalfe, "PUP: An
`Internetwork Architecture", XEROX Palo Alto Research Center,
`CSL-79-10, July 1979; also in IEEE Transactions on
`Communication, Volume COM-28, Number 4, April 1980.
`
`Braden, R., "NETRJS Protocol", RFC 740, NIC 42423,
`22 November 1977. Also in [17].
`
`Bressler, B., "Remote Job Entry Protocol", RFC 407, NIC
`12112, 16 October 72. Also in [17].
`
`Bressler, R., "Inter-Entity Communication -- An Experiment",
`RFC 441, NIC 13773, 19 January 1973.
`
`CCA, "Datacomputer Version 5/4 User Manual", Computer
`Corporation of America, August 1979.
`
`Cerf, V., "NCP Statistics", RFC 388, NIC 11360,
`23 August 1972.
`
`Clark, D., "Revision of DSP Specification", Local Network Note
`9, Laboratory for Computer Science, MIT, 17 June 1977.
`
`Clements, R., "FTPSRV -- Extensions for Tenex Paged Files",
`RFC 683, NIC 32251, 3 April 1975. Also in [17].
`
`Cohen, D., "Specifications for the Network Voice Protocol
`(NVP)", NSC Note 68, 29 January 1976. Also as USC/Information
`Sciences Institute RR-75-39, March 1976, and as RFC 741,
`NIC 42444, 22 November 1977. Also in [17].
`
`[13]
`
`Cohen, D. and J. Postel, "Multiplexing Protocol", IEN 90,
`USC/Information Sciences Institute, May 1979.
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 11]
`
`12/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 12 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Documents
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`[14]
`
`[15]
`
`[16]
`
`[17]
`
`[18]
`
`[19]
`
`[20]
`
`[21]
`
`[22]
`
`[23]
`
`[24]
`
`[25]
`
`[26]
`
`[27]
`
`COMPASS, "Semi-Annual Technical Report", CADD-7603-0411,
`Massachusetts Computer Associates, 4 March 1976. Also as,
`"National Software Works, Status Report No. 1",
`RADC-TR-76-276, Volume 1, September 1976. And COMPASS. "Second
`Semi-Annual Report", CADD-7608-1611, Massachusetts Computer
`Associates, 16 August 1976.
`
`Crispin, M., "SUPDUP Protocol", RFC 734, NIC 41953,
`7 October 1977. Also in [17].
`
`Crispin, M. and I. Zabala, "DIALNET Protocols", Stanford
`University Artificial Intelligence Laboratory, July 1978.
`
`Feinler, E. and J. Postel, eds., "ARPANET Protocol Handbook",
`NIC 7104, for the Defense Communications Agency by SRI
`International, Menlo Park, California, Revised January 1978.
`
`Flood Page, D., "Gateway Monitoring Protocol", IEN 131,
`February 1980.
`
`Flood Page, D., "CMCC Performance Measurement Message
`Formats", IEN 157, September 1980.
`
`Forgie, J., "ST - A Proposed Internet Stream Protocol",
`IEN 119, M.I.T. Lincoln Laboratory, September 1979.
`
`Forsdick, H., and A. McKenzie, "FTP Functional Specification",
`Bolt Beranek and Newman, Report 4051, August 1979.
`
`Harrenstien, K., J. Postel, "Time Server", IEN 142,
`April 1980. Also in [17].
`
`Harrenstien, K., "Name/Finger", RFC 742, NIC 42758,
`30 December 1977. Also in [17].
`
`Harvey, B., "One More Try on the FTP", RFC 691, NIC 32700,
`6 June 1975.
`
`Haverty, J., "XNET Formats for Internet Protocol Version 4",
`IEN 158, October 1980.
`
`McCarthy, J. and L. Earnest, "DIALNET", Stanford University
`Artificial Intelligence Laboratory, Undated.
`
`McKenzie, A., "File Transfer Protocol", RFC 454, NIC 14333,
`16 February 1973.
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 12]
`
`13/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 13 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Documents
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`[28] McKenzie,A., "Host/Host Protocol for the ARPA Network",
`NIC 8246, January 1972. Also in [17].
`
`[29]
`
`NSW Protocol Committee, "MSG: The Interprocess Communication
`Facility for the National Software Works", CADD-7612-2411,
`Massachusetts Computer Associates, BBN 3237, Bolt Beranek and
`Newman, Revised 24 December 1976.
`
`[30] O'Brien, M., "A Network Graphical Conferencing System", RAND
`Corporation, N-1250-ARPA, August 1979.
`
`[31]
`
`[32]
`
`[33]
`
`[34]
`
`Postel, J., "Character Generator Process", RFC 429, NIC 13281,
`12 December 1972.
`
`Postel, J., "Discard Process", RFC 348, NIC 10427,
`30 May 1972.
`
`Postel, J., ed., "Internet Protocol - DARPA Internet Program
`Protocol Specification", RFC 791, USC/Information Sciences
`Institute, September 1981.
`
`Postel, J., ed., "Transmission Control Protocol - DARPA
`Internet Program Protocol Specification", RFC 793,
`USC/Information Sciences Institute, September 1981.
`
`[35]
`
`Postel, J., "Echo Process", RFC 347, NIC 10426, 30 May 1972.
`
`[36]
`
`[37]
`
`[38]
`
`[39]
`
`[40]
`
`[41]
`
`[42]
`
`Postel, J., "File Transfer Protocol", RFC 765, IEN 149,
`June 1980.
`
`Postel, J., "Internet Message Protocol", RFC 759, IEN 113,
`USC/Information Sciences Institute, August 1980.
`
`Postel, J., "Name Server", IEN 116, USC/Information Sciences
`Institute, August 1979.
`
`Postel, J., "Official Initial Connection Protocol", NIC 7101,
`11 June 1971. Also in [17].
`
`Postel, J., "Telnet Protocol", RFC 318, NIC 9348,
`3 April 1972.
`
`Postel, J., "Telnet Protocol Specification", RFC 764, IEN 148,
`June 1980.
`
`Postel, J., "User Datagram Protocol", RFC 768 USC/Information
`Sciences Institute, August 1980.
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 13]
`
`14/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 14 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`Documents
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`[43]
`
`[44]
`
`[45]
`
`[46]
`
`[47]
`
`[48]
`
`[49]
`
`[50]
`
`[51]
`
`[52]
`
`[53]
`
`[54]
`
`[55]
`
`Reed, D., "Protocols for the LCS Network", Local Network Note
`3, Laboratory for Computer Science, MIT, 29 November 1976.
`
`Skelton, A., S. Holmgren, and D. Wood, "The MITRE Cablenet
`Project", IEN 96, April 1979.
`
`Sluizer, S., and J. Postel, "Mail Transfer Protocol", RFC 780,
`USC/Information Sciences Institute, May 1981.
`
`Sproull, R., and E. Thomas. "A Networks Graphics Protocol",
`NIC 24308, 16 August 1974. Also in [17].
`
`Sollins, K., "The TFTP Protocol (revision 2)", RFC 783,
`MIT/LCS, June 1981.
`
`Strazisar, V., "Gateway Routing: An Implementation
`Specification", IEN 30, Bolt Berenak and Newman, April 1979.
`
`Strazisar, V., "How to Build a Gateway", IEN 109, Bolt Berenak
`and Newman, August 1979.
`
`The High Level Protocol Group, "A Network Independent File
`Transfer Protocol",
`INWG Protocol Note 86, December 1977.
`
`Thomas, R., "A Resource Sharing Executive for the ARPANET",
`AFIPS Conference Proceedings, 42:155-163, NCC, 1973.
`
`Flood Page, D., "A Simple Message Generator", IEN 172, Bolt
`Berenak and Newman, March 1981.
`
`Postel, J., "Internet Control Message Protocol - DARPA
`Internet Program Protocol Specification", RFC 792,
`USC/Information Sciences Institute, September 1981.
`
`Postel, J., "Simple Mail Transfer Protocol", RFC 788,
`USC/Information Sciences Institute, September 1981.
`
`Littauer, B., "A Host Monitoring Protocol"", IEN 197, Bolt
`Berenak and Newman, September 1981.
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 14]
`
`15/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 15 of 16
`
`

`

`3/26/22, 6:02 PM
`
`RFC 790
`
`People
`
`RFC 790 - Assigned numbers
`
`September 1981
`Assigned Numbers
`
`PEOPLE
`
`BBN
`UCL
`ISI
`UCLA
`BBN
`DCEC
`ARPA
`MIT
`BBN
`MIT
`ISI
`Stanford
`RSRE
`SRI
`BBN
`LL
`MIT
`SRI
`MIT
`BBN
`BBN
`UCL
`BBN
`Honeywell
`LLL
`UCL
`DEC
`
`Don Allen
`Chris Bennett
`Richard Bisbey
`Bob Braden
`Robert Bressler
`Ed Cain
`Vint Cerf
`J. Noel Chiappa
`Steve Chipman
`David Clark
`Danny Cohen
`Mark Crispin
`Brian Davies
`Jake Feinler
`David Flood Page
`Jim Forgie
`Stu Galley
`Geoff Goodfellow
`Ken Harrenstien
`Jack Haverty
`Jim Herman
`Peter Higginson
`Robert Hinden
`Charles Hornig
`Earl Killian
`Peter Kirstein
`David Lyons
`Hank Magnuski
`SRI
`Jim Mathis
`BBN
`Dale McNeill
`COMSAT
`David Mills
`MIT
`David Moon
`MIT
`Eliot Moss
`RAND
`Michael O'Brien
`BBN
`Ken Pogran
`ISI
`Jon Postel
`CCA
`Joanne Sattely
`MITRE
`Anita Skelton
`MIT
`Karen Sollins
`Virginia Strazisar BBN
`Ed Taft
`XEROX
`Dan Tappan
`BBN
`Robert Thomas
`BBN
`Al Vezza
`MIT
`Cliff Weinstein
`LL
`
`Allen@BBND
`UKSAT@ISIE
`Bisbey@ISIB
`Braden@ISIA
`Bressler@BBNE
`cain@EDN-Unix
`Cerf@ISIA
`JNC@MIT-XX
`Chipman@BBNA
`Clark@MIT-Multics
`Cohen@ISIB
`Admin.MRC@SU-SCORE
`T45@ISIE
`Feinler@SRI-KL
`DFloodPage@BBNE
`Forgie@BBNC
`SWG@MIT-DMS
`Geoff@DARCOM-KA
`KLH@MIT-AI
`JHaverty@BBN-Unix
`Herman@BBNE
`UKSAT@ISIE
`Hinden@BBNE
`Hornig@MIT-Multics
`EAK@MIT-MC
`Kirstein@ISIA
`Lyons@DEC-2136
`
`Mathis@SRI-KL
`DMcNeill@BBNE
`Mills@ISIE
`Moon@MIT-MC
`EBM@MIT-XX
`OBrien@RAND-Unix
`Pogran@BBND
`Postel@ISIF
`JZS@CCA
`skel ton@MITRE
`Sollins@MIT-XX
`Strazisar@BBNA
`Taft.PA@PARC
`Tappan@BBNG
`Thomas@BBNA
`AV@MIT-XX
`cjw@LL-11
`
`[DCA2]
`[CJB]
`[RB6]
`[RTB]
`[RDB2]
`[ECS]
`[VGC]
`[NC3]
`[SGC]
`[DDC2]
`[DC]
`[MRC]
`[BD2]
`[JAKE]
`[DFP]
`[JWF]
`[SWG]
`[GEOF]
`[KLH]
`[JFH2]
`[JGH]
`[PLH]
`[RH6]
`[CH2]
`[EAK]
`[PK]
`[DRL]
`[HM]
`[JEM]
`[DMll]
`[DLMl]
`[MOON]
`[EBM]
`[MO2]
`[KTP]
`[JBP]
`[JZS]
`[APS]
`[KRS]
`[VMS]
`[EAT3]
`[DT]
`[RHT]
`[AV]
`[CJW2]
`
`Postel
`
`https://datatracker.ietf.org/doc/htrnl/rfc790
`
`[Page 15]
`
`16/16
`
`I PR2022-00833
`CommScope, Inc. Exhibit 1009
`Page 16 of 16
`
`