RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Held for Document Update (2)

RFC 3312, "Integration of Resource Management and Session Initiation Protocol (SIP)", October 2002

Source of RFC: sip (rai)

Errata ID: 3117

Status: Held for Document Update
Type: Editorial

Reported By: Beis Grigorios
Date Reported: 2012-02-08
Held for Document Update by: Robert Sparks

Section 8 says:

The port number of every "m=" line MUST be set to zero, but the connection address is arbitrary.

The desired status line corresponding to the precondition that
triggered the failure MUST use the "failure" strength-tag, as shown
in the example below:

      m=audio 20000 RTP/AVP 0
      a=des:qos failure e2e send


It should say:

The port number of every "m=" line MUST be set to zero, but the connection address is arbitrary.

The desired status line corresponding to the precondition that
triggered the failure MUST use the "failure" strength-tag, as shown
in the example below:

      m=audio 0 RTP/AVP 0
      a=des:qos failure e2e send

Notes:

The G711U codec's payload type 0 that appears in the m-line, probably led to the typo error with the incorrect port number (20000 instead of 0).

Errata ID: 3119

Status: Held for Document Update
Type: Editorial

Reported By: Beis Grigorios
Date Reported: 2012-02-09
Held for Document Update by: Robert Sparks

Section 9 says:

m=audio 20000 RTP/AVP 0
a=des:foo unknown e2e send

It should say:

m=audio 0 RTP/AVP 0
a=des:foo unknown e2e send

Notes:

Same typo as Errata ID: 3117. The port number must be set to zero.

Report New Errata



Search RFCs
Advanced Search
×