RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 3 records.

Status: Held for Document Update (3)

RFC 5098, "Signaling MIB for PacketCable and IPCablecom Multimedia Terminal Adapters (MTAs)", February 2008

Note: This RFC has been updated by RFC 9141

Source of RFC: ipcdn (ops)

Errata ID: 1347
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2008-03-04
Held for Document Update by: Dan Romascanu

Section 5, pg.12 says:

  pktcSigDevCodecTable OBJECT-TYPE
     ...
     DESCRIPTION
        " ...

          Codec Type     Maximum Number of Simultaneous Codecs
          PCMA                             3

          PCMA                             2
          PCMU                             1

          PCMA                             1
|
          PCMU                             2

          PCMU                             3

          PCMA                             1
          G729                             1

          G729                             2

          PCMU                             1
          G729                             1

It should say:

  pktcSigDevCodecTable OBJECT-TYPE
     ...
     DESCRIPTION
        " ...

          Codec Type     Maximum Number of Simultaneous Codecs
|
          PCMA                             3

          PCMA                             2
          PCMU                             1

          PCMA                             1
          PCMU                             2

          PCMU                             3

          PCMA                             1
          G729                             1

          G729                             2

          PCMU                             1
          G729                             1

Notes:

Issue: Spurious blank line distorts grouping of example
line and turns example ineffective.
Correction: Delete the spurious line, but add a blank line
after the headline, for clarity.

Errata ID: 1348
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2008-03-04
Held for Document Update by: Dan Romascanu

Section 5, pg.20 says:

  pktcSigCapabilityVendorExt      OBJECT-TYPE
     ...
     DESCRIPTION
        " The vendor extension allows vendors to provide a list of
          additional capabilities.

          The syntax for this MIB object in ABNF ([RFC5234]) is
          specified to be zero or more occurrences of vendor
          extensions, as follows:

           pktcSigCapabilityVendorExt  = *(vendor-extension)
|          vendor-extension = (ext symbol alphanum) DQUOTE ; DQUOTE
|          ext      = DQUOTE %x58 DQUOTE
|          symbol   = (DQUOTE %x2D DQUOTE)/(DQUOTE %x2D DQUOTE)
           alphanum = 1*6(ALPHA/DIGIT)

         "

It should say:

  pktcSigCapabilityVendorExt      OBJECT-TYPE
     ...
     DESCRIPTION
        " The vendor extension allows vendors to provide a list of
          additional capabilities.

          The syntax for this MIB object in ABNF ([RFC5234]) is
          specified to be zero or more occurrences of vendor
          extensions, as follows:

           pktcSigCapabilityVendorExt  = *(vendor-extension)
|          vendor-extension = ext symbol alphanum ";" 
|          ext      = %x58               ; uppercase only X
|          symbol   = %x2B / %x2D        ; + or -
           alphanum = 1*6(ALPHA/DIGIT)

         "

Notes:

Symptom: ABNF grossly nonsensical:
ABNF comment '; DQUOTE' perhaps intended as non-comment;
all DQUOTEs apparently should be removed;
two identical alternatives for symbol do not make sense.

Correction is based on earlier draft versions, applying the
corrections necessary to obtain valid ABNF, yet specifying
what probably was intended.

Alternatively, the following line might be substituted above:

| symbol = "+" / "-"

Errata ID: 1349
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT

Reported By: Alfred Hoenes
Date Reported: 2008-03-04
Held for Document Update by: Dan Romascanu

Section 5,pg.31-33 says:

-

It should say:

         osi                             any value  (not used)

Notes:

Incomplete specification:

The line given as 'corrected text' is missing from the tabular
listings of all (other) cases possible, in the DESCRIPTION clauses
of the following three scalar MIB objects, on pp.31-33 of the RFC:

pktcSigDevVmwiAfterDTAS
pktcSigDevVmwiAfterRPAS
pktcSigDevVmwiDTASAfterLR

Report New Errata



Advanced Search