RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 5 records.

Status: Verified (5)

RFC 4596, "Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension", July 2006

Source of RFC: sipping (rai)

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

Reported By: Eric Tremblay
Date Reported: 2008-01-16
Verifier Name: Cullen Jennings
Date Verified: 2009-01-08

Throughout the document, when it says:

msgserver

It should say:

actor="msg-taker"

Notes:

Throughout RFC4596, msgserver is used as a feature tag while its use was never standardized. A standards compliant proxy server would simply ignore this msgserver parameter. msgserver was used in some UA capabilities draft but was later changed to actor="msg-taker". Somehow this change did not get through to RFC4596.
See http://www1.ietf.org/mail-archive/web/sip/current/msg08884.html for when the change took place.

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

Reported By: Gunnar Hellstrom
Date Reported: 2016-06-20
Verifier Name: Ben Campbell
Date Verified: 2016-06-20

Section 3.9.2 says:

languages=

It should say:

language=

Notes:

There are seven occurrences of this error in the sip examples of section 3.9.2.
As comparison, section 3.16.2 has the correct spelling in its three occurrences.
The parameter name refers to the language feature tag from RFC 2987, named "language".

Errata ID: 45
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2006-08-17

Section 3.5.1 says:

Y2 represents an audio/video phone that should only used
when needed.

It should say:

Y2 represents an audio/video phone that should only be
used when needed.

Notes:

word omission

from pending

Errata ID: 761
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2006-08-17

Section 3.1 says:

3.1. Routing of INVITE and MESSAGE to Different UA

It should say:

3.1. Routing of INVITE and MESSAGE to Different UAs

Notes:

from pending

Errata ID: 763
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2006-08-17

Section 2 says:

The may prefer to reach
the user on a device that supports video (because a video-conference
is desired).  

It should say:

They may prefer to reach
the user on a device that supports video (because a video-conference
is desired). 

Notes:

from pending

Report New Errata



Advanced Search