RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002

Source of RFC: mmusic (rai)

Errata ID: 3818
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Jörgen Axell
Date Reported: 2013-12-02
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-12-03

Section 4 says:

   The agent receiving the offer MAY generate an answer, or it MAY
   reject the offer.  The means for rejecting an offer are dependent on
   the higher layer protocol.  The offer/answer exchange is atomic; if
   the answer is rejected, the session reverts to the state prior to the
   offer (which may be absence of a session).

It should say:

   The agent receiving the offer MAY generate an answer, or it MAY
   reject the offer.  The means for rejecting an offer are dependent on
   the higher layer protocol.  The offer/answer exchange is atomic; if
   the offer is rejected, the session reverts to the state prior to the
   offer (which may be absence of a session).

Notes:

You can't reject an answer. When the answer is received the SDP negotiation is completed.

Status: Reported (1)

RFC 3264, "An Offer/Answer Model with Session Description Protocol (SDP)", June 2002

Source of RFC: mmusic (rai)

Errata ID: 5177
Status: Reported
Type: Technical
Publication Format(s) : TEXT

Reported By: Sandeep Kumar Aitha
Date Reported: 2017-11-03

Section 5.1 says:

Section 5.1 says:
However, for sendonly and sendrecv streams, the answer might indicate
different payload type numbers for the same codecs, in which case,
the offerer MUST send with the payload type numbers from the answer.

Section 6.2 says:
In the case of RTP, if a particular codec was referenced with a
specific payload type number in the offer, that same payload type
number SHOULD be used for that codec in the answer.

It should say:

Only one of the above statements can be correct.

Notes:

Above two statements are conflicting.
The answerer should be able to either map the payload type to a different codec or not.

Report New Errata