RFC Errata
Found 4 records.
Status: Reported (1)
RFC 2549, "IP over Avian Carriers with Quality of Service", April 1999
Source of RFC: INDEPENDENT
Errata ID: 6206
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Derek McCullough
Date Reported: 2020-06-07
Throughout the document, when it says:
Multicasting is supported, but requires the implementation of a clone device. Carriers may be lost if they are based on a tree as it is being pruned. The carriers propagate via an inheritance tree. The carriers have an average TTL of 15 years, so their use in expanding ring searches is limited. Additional quality of service discussion can be found in a Michelin's guide.
It should say:
Multicasting is supported, but requires the implementation of a clone device. Carriers may be lost if they are based on a tree as it is being pruned. The carriers propagate via an inheritance tree. The carriers have an average TTL of 15 years, so their use in expanding ring searches is limited. NOTE: Geese are for UDP only, as they are indifferent to any query, regardless of target. Expect all Geese allocated traffic to be one way only. Additional quality of service discussion can be found in a Michelin's guide.
Notes:
Geese have not been thoroughly considered for their jerk-ishness and need to be included in the documentation as a warning to anyone considering utilization of aviary modes of data transportation.
Status: Rejected (3)
RFC 2549, "IP over Avian Carriers with Quality of Service", April 1999
Source of RFC: INDEPENDENT
Errata ID: 3793
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Anne van Kesteren
Date Reported: 2013-11-10
Rejected by: Nevil Brownlee (ISE)
Date Rejected: 2014-01-17
In the Security Considerations
It should say:
Hawks.
Notes:
Per mnot.
--- Verifier Notes ---
1. This erratum doesn't say which phrase in the original
text needs changing.
2. Errata are intended to note Editorial or Technical changes;
as far as I can see this one is neither.
Errata ID: 8289
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Pavel Pikirenia
Date Reported: 2025-02-08
Rejected by: Eliot Lear
Date Rejected: 2025-02-13
Throughout the document, when it says:
Multicasting is supported, but requires the implementation of a clone device.
It should say:
Multicasting is supported, but requires the implementation of a cloning and memory-altering device.
Notes:
As the destination addresses are brain-embedded in carriers, simply using a cloning device on a carrier would result in multiple packets sent to the same unicast address. Following this issue, an implementation of a memory-altering functionality would be required to change the destination address when replicating packets to reach multiple receivers.
--VERIFIER NOTES--
Thank you for your errata report. An addressing model is not fully specified, particular source address selection. Memory is apparently necessary only for the destination address, and for multicast that represents no conflict.
Errata ID: 8283
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Peter Shirley
Date Reported: 2025-02-05
Rejected by: Eliot Lear
Date Rejected: 2025-02-06
Section 1 says:
The following quality of service levels are available: Concorde, First, Business, and Coach. Concorde class offers expedited data delivery. One major benefit to using Avian Carriers is that this is the only networking technology that earns frequent flyer miles, plus the Concorde and First classes of service earn 50% bonus miles per packet.
It should say:
The following quality of service levels are available: First, Business, and Coach. One major benefit to using Avian Carriers is that this is the only networking technology that earns frequent flyer miles, plus First class service earn 50% bonus miles per packet.
Notes:
Concorde service levels have been unavailable since 2003.
--VERIFIER NOTES--
Thank you for your report.
While the Concorde itself hasn't flown *commercially* for quite some time, nothing prevents that from happening in the future, and Informational documents do not require implementations.