RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Reported (2)

RFC 3455, "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)", January 2003

Note: This RFC has been obsoleted by RFC 7315

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: rai

Errata ID: 3929
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Gagandeep Singh
Date Reported: 2014-03-23

Section 6.3 says:

Therefore intermediaries participating in this mechanism MUST apply a
hop-by-hop integrity protection mechanism such us IPsec or other
available mechanisms in order to prevent such attacks.

It should say:

Therefore intermediaries participating in this mechanism MUST apply a
hop-by-hop integrity protection mechanism such as IPsec or other
available mechanisms in order to prevent such attacks.

Notes:

Ofcourse this errata doesn't alter the technical meaning, but it is nice to have documents free of spelling errors too.

Errata ID: 3973
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Zoltan Toth
Date Reported: 2014-04-24

Section 4.2 says:

      F6 Invite P1 -> UA
           INVITE sip:user1@192.0.2.4 SIP/2.0
           Via: SIP/2.0/UDP 192.0.2.10:5060;branch=z9hG4bKg48sh128
           Via: SIP/2.0/UDP 192.0.2.20:5060;branch=z9hG4bK03djaoe1
           To: sip:other-user@othernetwork.com
           From: sip:another-user@anothernetwork.com;tag=938s0
           Call-ID: 843817637684230998sdasdh09
           P-Called-Party-ID: sip:user1-business@example.com
           CSeq: 101 INVITE

It should say:

      F6 Invite P1 -> UA
           INVITE sip:user1@192.0.2.4 SIP/2.0
           Via: SIP/2.0/UDP 192.0.2.10:5060;branch=z9hG4bKg48sh128
           Via: SIP/2.0/UDP 192.0.2.20:5060;branch=z9hG4bK03djaoe1
           To: sip:other-user@othernetwork.com
           From: sip:another-user@anothernetwork.com;tag=938s0
           Call-ID: 843817637684230998sdasdh09
*          P-Called-Party-ID: <sip:user1-business@example.com>
           CSeq: 101 INVITE

Notes:

5.2 P-Called-Party-ID header syntax

The syntax of the P-Called-Party-ID header is described as follows:

P-Called-Party-ID = "P-Called-Party-ID" HCOLON
called-pty-id-spec
called-pty-id-spec = name-addr *(SEMI cpid-param)

RFC3261:
name-addr = [ display-name ] LAQUOT addr-spec RAQUOT

-> the SIP URI of the PCPI header in the example should be enclosed in angle quotes.

Report New Errata



Advanced Search