RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Held for Document Update (3)

RFC 5140, "A Telephony Gateway REgistration Protocol (TGREP)", March 2008

Source of RFC: iptel (rai)

Errata ID: 1355

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-03-11
Held for Document Update by: Robert Sparks

Section 3, pg.7 says:

      - Prefix (Hexadecimal Routing Number): This attribute is used to
        represent the list of Hexadecimal prefixes to which the
        respective route can complete calls.

It should say:

      - Prefix (Pentadecimal Routing Number): This attribute is used to
        represent the list of Pentadecimal prefixes to which the
        respective route can complete calls.

Notes:

There are no *Hexa*decimal Routing Numbers in TRIP or TGREP; but there
are *Penta*decimal Routing Numbers (see RFC 3219, Section 5.1.1.3).
The rest of RFC 5140 never uses "Hexadecimal", only "Pentadecimal".

Errata ID: 1356

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-03-11
Held for Document Update by: Robert Sparks

Section 4.4.5, pg.13 says:

   The LS receiving this attribute should disseminate to other peers,
   both internal and external to the ITAD.

It should say:

                                                     vvvv
   The LS receiving this attribute should disseminate it to other peers,
   both internal and external to the ITAD.

Notes:

cf. similar subsections of RFC 5140 (4.*.5)

Errata ID: 1357

Status: Held for Document Update
Type: Editorial

Reported By: Alfred Hoenes
Date Reported: 2008-03-11
Held for Document Update by: Robert Sparks

Section 6.7, pg.20 says:

                                    [...].  TGREP should specify its
   choice address family through the route-type capability in the OPEN
   message.  And route-type specification in the OPEN message violating
   the above rule should be rejected with a NOTIFICATION message.

It should say:

                                    [...].  TGREP should specify its
|  choice of address family through the route-type capability in the
|  OPEN message.  Any route-type specification in the OPEN message
   violating the above rule should be rejected with a NOTIFICATION
   message.

Notes:

a) missing "of"
b) "And" --> "Any"

Report New Errata



Search RFCs
Advanced Search
×