Found 2 records.

Status: Verified (2)

RFC 5245, "Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols", April 2010

Note: This RFC has been obsoleted by RFC 8445, RFC 8839

Note: This RFC has been updated by RFC 6336

Errata ID: 2338
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Reif, Frank
Date Reported: 2010-07-20
Verifier Name: Robert Sparks
Date Verified: 2011-02-07

Section 15.1 says:

extension-att-name    = byte-string    ;from RFC 4566

It should say:

extension-att-name    = token    ;from RFC 4566

Notes:

"extension-att-name" may contain the SP (0x20) as defined for "byte-string" in RFC 4566.
The 'SP' character cannot be allowed within "extension-att-name" as it is also used as delimiter between "extension-att-name" and "extension-att-value".

Errata ID: 3149
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Marc Petit-huguenin
Date Reported: 2012-03-07
Verifier Name: Robert Sparks
Date Verified: 2012-04-13

Section 21.1.4 says:

Type of Attribute: session-level

It should say:

Type of Attribute: media-level

Notes:

Section 15.3 clearly says that "ice-mismatch" is media-level:

'"ice-mismatch" is a media-level
attribute only, and when present in an answer, indicates that the
offer arrived with a default destination for a media component that
didn't have a corresponding candidate attribute.'

Section Section 6.1 also implies that "ice-mismatch" is media-level:

"In some cases, the answer may omit a=candidate attributes for the
media streams, and instead include an a=ice-mismatch attribute for
one or more of the media streams in the SDP."

Report New Errata