RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 3219, "Telephony Routing over IP (TRIP)", January 2002

Source of RFC: iptel (rai)

Errata ID: 322

Status: Verified
Type: Technical

Reported By: Jonathan Rosenberg
Date Reported: 2002-09-06

Section 10.3.1.1 says:

   -  If the LS is configured to use the MultiExitDisc attribute to
      break ties, and the candidate routes differ in the value of the
      MultiExitDisc attribute, then select the route that has the
      lowest value of MultiExitDisc, else
   -  Select the route that was advertised by the external LS that
      has the lowest TRIP Identifier.

It should say:

   -  If the LS is configured to use the MultiExitDisc attribute to
      break ties, and the candidate routes differ in the value of the
      MultiExitDisc attribute, then select the route that has the
      highest value of MultiExitDisc, else
   -  Select the route that was advertised by the external LS that
      has the lowest ITAD number.

Status: Held for Document Update (1)

RFC 3219, "Telephony Routing over IP (TRIP)", January 2002

Source of RFC: iptel (rai)

Errata ID: 2634

Status: Held for Document Update
Type: Editorial

Reported By: Dale R. Worley
Date Reported: 2010-11-16
Held for Document Update by: Robert Sparks

Section 5.1.1.3 says:

      PentaDecimal-routing-number   = *pentadecimal-digit
-     pentadecimal-routing-digit    = PENTADECIMAL-DIGIT

It should say:

      PentaDecimal-routing-number   = *pentadecimal-digit
-     pentadecimal-digit            = PENTADECIMAL-DIGIT

Notes:

BNF variable "pentadecimal-routing-digit" should be "pentadecimal-digit", by analogy with section 5.1.1.2.

Report New Errata



Search RFCs
Advanced Search
×