RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Verified (2)

RFC 4730, "A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)", November 2006

Source of RFC: sipping (rai)

Errata ID: 13

Status: Verified
Type: Technical

Reported By: Eric Burger
Date Reported: 2006-11-30
Verifier Name: Cullen Jennings
Date Verified: 2009-01-08

Section 5.1 says:

   DRegexCharacter  = DIGIT / "A" / "B" / "C" / "D" / "R" / "*" / "#" /
                              "a" / "b" / "c" / "d" / "r"

It should say:

   DRegexCharacter  = DIGIT / "A" / "B" / "C" / "D" / "R" / "X" / "*" / "#"
                              "a" / "b" / "c" / "d" / "r" / "x"

Notes:

The ABNF for DRegex (page 29) is missing an 'x'.

Errata ID: 3209

Status: Verified
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2012-05-03
Verifier Name: Gonzalo Camarillo
Date Verified: 2013-04-04

Section 7.4, 7.5 says:

urn:ietf:xml:ns:kpml-...

It should say:

urn:ietf:params:xml:ns:kpml-...

Notes:

The headlines of Sections 7.4 and 7.5 contain garbled versions of
the IETF protocol parameter sub-namespaces defined in the RFC:
the hierarchical element "params:" is missing.

This flaw also is mirrored in the Table of Contents of the RFC.

Status: Held for Document Update (1)

RFC 4730, "A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)", November 2006

Source of RFC: sipping (rai)

Errata ID: 2265

Status: Held for Document Update
Type: Technical

Reported By: David Grant
Date Reported: 2010-05-18
Held for Document Update by: Robert Sparks

Section 10.2 says:

NOTIFY sip:ap@client.subB.example.com SIP/2.0
Via: SIP/2.0/UDP subA.example.com;branch=3qo3j0ouq
To: <sip:ap@subB.example.com>;tag=978675
From: <sip:gw@subA.example.com>;tag=9783453
Call-ID: 12345601@subA.example.com
CSeq: 3001 NOTIFY
Contact: <sip:gw27@subA.example.com>
Event: kpml
Subscription-State: active;expires=3442
Max-Forwards: 70
Content-Type: application/kpml-response+xml
Content-Length: 271

<?xml version="1.0" encoding="UTF-8"?>
<kpml-response xmlns="urn:ietf:params:xml:ns:kpml-response"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation=
        "urn:ietf:params:xml:ns:kpml-response kpml-response.xsd"
      version="1.0"
      code="200" text="OK"
      digits="9999888877776666"/>

It should say:

NOTIFY sip:ap@client.subB.example.com SIP/2.0
Via: SIP/2.0/UDP subA.example.com;branch=3qo3j0ouq
To: <sip:ap@subB.example.com>;tag=978675
From: <sip:gw@subA.example.com>;tag=9783453
Call-ID: 12345601@subA.example.com
CSeq: 3001 NOTIFY
Contact: <sip:gw27@subA.example.com>
Event: kpml
Subscription-State: active;expires=3442
Max-Forwards: 70
Content-Type: application/kpml-response+xml
Content-Length: 271

<?xml version="1.0" encoding="UTF-8"?>
<kpml-response xmlns="urn:ietf:params:xml:ns:kpml-response"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation=
        "urn:ietf:params:xml:ns:kpml-response kpml-response.xsd"
      version="1.0"
      code="200" text="OK"
      digits="9999888877776666" tag="card"/>

Notes:

The tag attribute is shown in the call-flow diagram, but not reproduced in the SIP message itself.

Report New Errata