RFC Errata
Found 2 records.
Status: Held for Document Update (2)
RFC 1633, "Integrated Services in the Internet Architecture: an Overview", June 1994
Source of RFC: LegacyArea Assignment: tsv
Errata ID: 2272
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: jonsimchol
Date Reported: 2010-05-18
Held for Document Update by: Wes Eddy
Section 5.1.3 says:
Although receiver-initiated reservation is the natural choice for multicast sessions, the justification for receiver initiateion may appear weaker for unicast sessions, where the sender may be the logical session initiator.
It should say:
Although receiver-initiated reservation is the natural choice for multicast sessions, the justification for receiver initiation may appear weaker for unicast sessions, where the sender may be the logical session initiator.
Notes:
initiateion -> initiation
Errata ID: 2273
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: jonsimchol
Date Reported: 2010-05-18
Held for Document Update by: Wes Eddy
Section 5.1.3 says:
RSVP uses receiver-initiation of rservations [RSVP93b]. A receiver is assumed to learn the senders' offered flowspecs by a higher-level mechanism ("out of band"), it then generates its own desired flowspec and propagates it towards the senders, making reservations in each router along the way.
It should say:
RSVP uses receiver-initiation of reservations [RSVP93b]. A receiver is assumed to learn the senders' offered flowspecs by a higher-level mechanism ("out of band"), it then generates its own desired flowspec and propagates it towards the senders, making reservations in each router along the way.
Notes:
rservations -> reservations