RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 4 records.

Status: Held for Document Update (4)

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

Source of RFC: sip (rai)

Errata ID: 4883

Status: Held for Document Update
Type: Technical

Reported By: Shraddha Soni
Date Reported: 2016-12-12
Held for Document Update by: Ben Campbell
Date Held: 2016-12-13

Section 11 says:

Therefore, a user agent
   including preconditions in the SDP MUST support the PRACK and UPDATE
   methods. Consequently, it MUST include the "100rel" [7] tag in the
   Supported header field and SHOULD include an Allow header field with
   the "UPDATE" tag [5].

It should say:

Therefore, a user agent
   including preconditions in the SDP MUST support the PRACK and UPDATE
   methods. Consequently, it MUST include the "100rel" [7] tag in the
   Supported header field and MUST include an Allow header field with
   the "UPDATE" tag [5].

Notes:

As stated in first line in the mentioned paragraph, the user agent MUST support the UPDATE method, hence even in Allow header field also, UPDATE method MUST be included.

As per RFC 2119
"SHOULD -This word, or the adjective "RECOMMENDED", mean that there
may exist valid reasons in particular circumstances to ignore a
particular item, but the full implications must be understood and
carefully weighed before choosing a different course. "

Here in precondition case, whether any chance of ignoring the UPDATE method happens ?

As per RFC 3261
Section 8.2.1 states -
"The Allow header field MUST list the set of methods supported by the UAS
generating the message. ... If the method is one supported by the server, processing continues."

and also in RFC 3261 Sections 20.5 states-
"All methods, including ACK and CANCEL, understood by the UA MUST be
included in the list of methods in the Allow header field, when
present."

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.

Errata ID: 4884

Status: Held for Document Update
Type: Editorial

Reported By: Shraddha Soni
Date Reported: 2016-12-12
Held for Document Update by: Ben Campbell
Date Held: 2016-12-12

Section 7 says:

If a peer has requested confirmation on a particular stream, an agent
   MUST mark that stream with a flag in its local status table. 

It should say:

If a peer has requested confirmation on a particular stream, an agent 
   MUST mark that stream with a flag in its local status table.  

Notes:

The only place in RFC, where 'agent' is mentioned instead of 'User Agent'. Use of 'User agent' is more appropriate in SIP context as per RFC 3261.
Unable to submit the errata when corrected text is mentioned as "user agent" Hence pasting same text in original text. Have submitted feedback online for the webpage issue.

Report New Errata



Search RFCs
Advanced Search
×