RFC Errata
Found 8 records.
Status: Verified (2)
RFC 1180, "TCP/IP tutorial", January 1991
Source of RFC: LegacyArea Assignment: int
Errata ID: 556
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Chao Yel
Date Reported: 2000-02-28
In Section 5.10, Table 12 - Delta's Route Table: [Based on Figure 9] Network "factory" should correspond to Delta Interface #2; Network "accounting" should correspond to Delta Interface #3.
Errata ID: 5074
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Erik Auerswald
Date Reported: 2017-07-29
Verifier Name: Éric Vyncke
Date Verified: 2024-01-12
Section 5.3 says:
When an incoming IP packet arrives it is never forwarded back out through the same network interface.
It should say:
When an incoming IP packet arrives it may be forwarded back out through the same network interface.
Notes:
IP routers can and do send IP packets out the ingress interface. An ICMP redirect message may be sent in this case.
This is different to Ethernet bridge behavior, where a frame will not be sent out the ingress interface.
An IP packet that egresses the ingress interface is carried in a new Ethernet frame, this is not the same frame that arrived at the ingress interface (different SRC and DST MAC addresses, decreased TTL in the IP header).
Status: Held for Document Update (4)
RFC 1180, "TCP/IP tutorial", January 1991
Source of RFC: LegacyArea Assignment: int
Errata ID: 3456
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: John Morley
Date Reported: 2013-01-15
Held for Document Update by: Brian Haberman
Section 5.4 says:
The portion of the address that is used for network number and for host number is defined by the upper bits in the 4-byte address. All example IP addresses in this tutorial are of type class C, meaning that the upper 3 bits indicate that 21 bits are the network number and 8 bits are the host number. This allows 2,097,152 class C networks up to 254 hosts on each network.
It should say:
The portions of the address that are used as network number and as host number are defined by the netmask. All example IP addresses in this tutorial are of type class C and have a netmask of 255.255.255.0, meaning that the first three bytes (24 bits) represent the network number and the last eight bits the host number. This allows 16,777,216 class C networks with up to 254 hosts on each network.
Notes:
The concept of IP address loses much of its meaning if the value of the
netmask is ignored. The paragraph as originally written doesn't make
sense, in particular "the upper 3 bits indicate that 21 bits are the network
number".
Errata ID: 4587
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Masoud Valizadeh
Date Reported: 2016-01-10
Held for Document Update by: Brian Haberman
Date Held: 2016-01-15
Section 2.2 says:
and if it is in a network application it is called a application message.
It should say:
and if it is in a network application it is called an application message.
Errata ID: 4590
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Masoud Valizadeh
Date Reported: 2016-01-10
Held for Document Update by: Brian Haberman
Date Held: 2016-01-15
Section 2.4 says:
It is seen from this structure that for computers with more than one physical network interface, the IP module is both a n-to-m multiplexer and an m-to-n de-multiplexer.
It should say:
It is seen from this structure that for computers with more than one physical network interface, the IP module is both an n-to-m multiplexer and an m-to-n de-multiplexer.
Errata ID: 4591
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Masoud Valizadeh
Date Reported: 2016-01-10
Held for Document Update by: Brian Haberman
Date Held: 2016-01-15
Section 3.1 says:
Each person has an unique name
It should say:
Each person has a unique name
Status: Rejected (2)
RFC 1180, "TCP/IP tutorial", January 1991
Source of RFC: LegacyArea Assignment: int
Errata ID: 4593
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Masoud Valizadeh
Date Reported: 2016-01-11
Rejected by: Brian Haberman
Date Rejected: 2016-01-15
Section 5.4 says:
The IP address space is administered by the NIC (Network Information Center). All internets that are connected to the single world-wide Internet must use network numbers assigned by the NIC. If you are setting up your own internet and you are not intending to connect it to the Internet, you should still obtain your network numbers from the NIC.
It should say:
The IP address space is administered by the IANA (Internet Assigned Numbers Authority). All internets that are connected to the single world-wide Internet must use network numbers assigned by the IANA. If you are setting up your own internet and you are not intending to connect it to the Internet (private network), you can choose any IP address for your network but it is recommended to use private ranges which are: class A 10.0.0.0 - 10.255.255.255 (16,777,216 IP addresses), class B 172.16.0.0 - 172.31.255.255 (1,048,576 IP addresses) and class C 192.168.0.0 - 192.168.255.255 (65,536 IP addresses).
Notes:
--VERIFIER NOTES--
The current text in RFC 1180 accurately reflects the administration of IP address at the time.
Errata ID: 4589
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Masoud Valizadeh
Date Reported: 2016-01-10
Rejected by: Brian Haberman
Date Rejected: 2016-01-15
Section 2.2 says:
A driver is software that communicates directly with the network interface hardware. A module is software that communicates with a driver, with network applications, or with another module.
It should say:
A driver is a software that communicates directly with the network interface hardware. A module is a software that communicates with a driver, with network applications or with another module.
Notes:
--VERIFIER NOTES--
The current text is grammatically correct.