RFC 2549, "IP over Avian Carriers with Quality of Service", April 1999

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.

Report New Errata