RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 12 records.

Status: Verified (11)

RFC 5102, "Information Model for IP Flow Information Export", January 2008

Note: This RFC has been obsoleted by RFC 7012

Note: This RFC has been updated by RFC 6313

Source of RFC: ipfix (ops)

Errata ID: 1307
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: RFC Editor
Date Reported: 2008-02-04
Verifier Name: Dan Romascanu
Date Verified: 2008-02-04

Section 7.3 says:

*  URI: urn:ietf:params:xml:ns:ipfix-info-15

  ...

*  URI: urn:ietf:params:xml:schema:ipfix-info-15

It should say:

*  URI: urn:ietf:params:xml:ns:ipfix-info

  ...

*  URI: urn:ietf:params:xml:schema:ipfix-info

Notes:

Discovered by Pearl Liang of IANA.

Errata ID: 1492
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Simon Perreault
Date Reported: 2008-08-21
Verifier Name: Dan Romascanu
Date Verified: 2009-08-03

Section Appendix A says:

         See RFC 793 for the definition of the TCP
         source port field.

It should say:

         See RFC 793 for the definition of the TCP
         destination port field.

Notes:

This is for elementId="183".

Errata ID: 1736
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2009-03-24
Verifier Name: Dan Romascanu
Date Verified: 2009-08-02

Section 5.4.22. says:

            0      1      2      3      4      5      6      7
         +------+------+------+------+------+------+------+------+
         | MCv4 | RES. | RES. |  T   |   IPv6 multicast scope    |
         +------+------+------+------+------+------+------+------+

It should say:

            0      1      2      3      4      5      6      7
         +------+------+------+------+------+------+------+------+
         |   IPv6 multicast scope    |  T   | RES. | RES. | MCv4 |
         +------+------+------+------+------+------+------+------+

Notes:

The diagram is back to front.

Errata ID: 1737
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2009-03-24
Verifier Name: Dan Romascanu
Date Verified: 2009-08-02

Section 5.8.5. says:

           0      1      2      3      4      5      6      7
       +------+------+------+------+------+------+------+------+
       | EOOL | NOP  | SEC  | LSR  |  TS  |E-SEC |CIPSO |  RR  | ...
       +------+------+------+------+------+------+------+------+

           8      9     10     11     12     13     14     15
       +------+------+------+------+------+------+------+------+
   ... | SID  | SSR  | ZSU  | MTUP | MTUR | FINN | VISA |ENCODE| ...
       +------+------+------+------+------+------+------+------+

          16     17     18     19     20     21     22     23
       +------+------+------+------+------+------+------+------+
   ... |IMITD | EIP  |  TR  |ADDEXT|RTRALT| SDB  |NSAPA | DPS  | ...
       +------+------+------+------+------+------+------+------+

          24     25     26     27     28     29     30     31
       +------+------+------+------+------+------+------+------+
   ... | UMP  |  QS  |   to be assigned by IANA  |  EXP |      |
       +------+------+------+------+------+------+------+------+

It should say:

           0      1      2      3      4      5      6      7
       +------+------+------+------+------+------+------+------+
       |  RR  |CIPSO |E-SEC |  TS  | LSR  | SEC  | NOP  | EOOL | ...
       +------+------+------+------+------+------+------+------+

           8      9     10     11     12     13     14     15
       +------+------+------+------+------+------+------+------+
   ... |ENCODE| VISA | FINN | MTUR | MTUP | ZSU  | SSR  | SID  | ...
       +------+------+------+------+------+------+------+------+

          16     17     18     19     20     21     22     23
       +------+------+------+------+------+------+------+------+
   ... | DPS  |NSAPA | SDB  |RTRALT|ADDEXT|  TR  | EIP  |IMITD | ...
       +------+------+------+------+------+------+------+------+

          24     25     26     27     28     29     30     31
       +------+------+------+------+------+------+------+------+
   ... |      |  EXP |   to be assigned by IANA  |  QS  | UMP  |
       +------+------+------+------+------+------+------+------+

Notes:

The diagram is back to front.

Errata ID: 1738
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2009-03-24
Verifier Name: Dan Romascanu
Date Verified: 2009-08-02

Section 5.8.6. says:

              0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          | Res | FRA1| RH  | FRA0| UNK | Res | HOP | DST |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... | PAY | AH  | ESP |         Reserved            | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             24    25    26    27    28    29    30    31
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     |
          +-----+-----+-----+-----+-----+-----+-----+-----+

It should say:

             0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          | DST | HOP | Res | UNK | FRA0| RH  | FRA1| Res |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |         Reserved            | ESP | AH  | PAY |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             24    25    26    27    28    29    30    31
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     |
          +-----+-----+-----+-----+-----+-----+-----+-----+

Notes:

The diagram is back to front.

Errata ID: 1739
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2009-03-24
Verifier Name: Dan Romascanu
Date Verified: 2009-08-02

Section 5.8.8. says:

              0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          |   0 |   1 |   2 |   3 |   4 |   5 |   6 |   7 |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |   8 |   9 |  10 |  11 |  12 |  13 |  14 |  15 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  16 |  17 |  18 |  19 |  20 |  21 |  22 |  23 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

                                . . .

             56    57    58    59    60    61    62    63
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  56 |  57 |  58 |  59 |  60 |  61 |  62 |  63 |
          +-----+-----+-----+-----+-----+-----+-----+-----+

It should say:

              0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          |   7 |   6 |   5 |   4 |   3 |   2 |   1 |   0 |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  15 |  14 |  13 |  12 |  11 |  10 |   9 |   8 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  23 |  22 |  21 |  20 |  19 |  18 |  17 |  16 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

                                . . .

             56    57    58    59    60    61    62    63
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  63 |  62 |  61 |  60 |  59 |  58 |  57 |  56 |
          +-----+-----+-----+-----+-----+-----+-----+-----+


Notes:

The diagram is back to front.

Errata ID: 2944
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2011-08-22
Verifier Name: Dan Romascanu
Date Verified: 2011-08-22

Section 5.8.5 says:

           0      1      2      3      4      5      6      7
       +------+------+------+------+------+------+------+------+
       | EOOL | NOP  | SEC  | LSR  |  TS  |E-SEC |CIPSO |  RR  | ...
       +------+------+------+------+------+------+------+------+

           8      9     10     11     12     13     14     15
       +------+------+------+------+------+------+------+------+
   ... | SID  | SSR  | ZSU  | MTUP | MTUR | FINN | VISA |ENCODE| ...
       +------+------+------+------+------+------+------+------+

          16     17     18     19     20     21     22     23
       +------+------+------+------+------+------+------+------+
   ... |IMITD | EIP  |  TR  |ADDEXT|RTRALT| SDB  |NSAPA | DPS  | ...
       +------+------+------+------+------+------+------+------+

          24     25     26     27     28     29     30     31
       +------+------+------+------+------+------+------+------+
   ... | UMP  |  QS  |   to be assigned by IANA  |  EXP |      |
       +------+------+------+------+------+------+------+------+

It should say:

           0      1      2      3      4      5      6      7
       +------+------+------+------+------+------+------+------+
       |      |  EXP |   to be assigned by IANA  |  QS  | UMP  | ...
       +------+------+------+------+------+------+------+------+


           8      9     10     11     12     13     14     15
       +------+------+------+------+------+------+------+------+
   ... | DPS  |NSAPA | SDB  |RTRALT|ADDEXT|  TR  | EIP  |IMITD | ...
       +------+------+------+------+------+------+------+------+


          16     17     18     19     20     21     22     23
       +------+------+------+------+------+------+------+------+
   ... |ENCODE| VISA | FINN | MTUR | MTUP | ZSU  | SSR  | SID  | ...
       +------+------+------+------+------+------+------+------+


          24     25     26     27     28     29     30     31
       +------+------+------+------+------+------+------+------+
   ... |  RR  |CIPSO |E-SEC |  TS  | LSR  | SEC  | NOP  | EOOL |
       +------+------+------+------+------+------+------+------+

Notes:

The bits were originally shown in the wrong order.

Errata 1737 tried to correct this by reversing the bits, but overlooked reversing the bytes.

Note that the network bit numbering in the figure is exactly the reverse of the "Bit" value in the following table.

Errata ID: 2945
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2011-08-22
Verifier Name: Dan Romascanu
Date Verified: 2011-08-22

Section 5.8.6 says:

              0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          | Res | FRA1| RH  | FRA0| UNK | Res | HOP | DST |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... | PAY | AH  | ESP |         Reserved            | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             24    25    26    27    28    29    30    31
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     |
          +-----+-----+-----+-----+-----+-----+-----+-----+

It should say:

             0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          |                  Reserved                     | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |                  Reserved                     | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |         Reserved            | ESP | AH  | PAY | ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             24    25    26    27    28    29    30    31
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... | DST | HOP | Res | UNK | FRA0| RH  | FRA1| Res |
          +-----+-----+-----+-----+-----+-----+-----+-----+

Notes:

The bits were originally shown in the wrong order.

Errata 1738 tried to correct this by reversing the bits, but overlooked reversing the bytes.

Note that the network bit numbering in the figure is exactly the reverse of the "Bit" value in the following table.

Errata ID: 2946
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2011-08-22
Verifier Name: Dan Romascanu
Date Verified: 2011-08-22

Section 5.8.8 says:

              0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          |   0 |   1 |   2 |   3 |   4 |   5 |   6 |   7 |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |   8 |   9 |  10 |  11 |  12 |  13 |  14 |  15 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  16 |  17 |  18 |  19 |  20 |  21 |  22 |  23 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

                                . . .

             56    57    58    59    60    61    62    63
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  56 |  57 |  58 |  59 |  60 |  61 |  62 |  63 |
          +-----+-----+-----+-----+-----+-----+-----+-----+

It should say:

              0     1     2     3     4     5     6     7
          +-----+-----+-----+-----+-----+-----+-----+-----+
          |  63 |  62 |  61 |  60 |  59 |  58 |  57 |  56 |  ...
          +-----+-----+-----+-----+-----+-----+-----+-----+

              8     9    10    11    12    13    14    15
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  55 |  54 |  53 |  52 |  51 |  50 |  49 |  48 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

             16    17    18    19    20    21    22    23
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |  47 |  46 |  45 |  44 |  43 |  42 |  41 |  40 |...
          +-----+-----+-----+-----+-----+-----+-----+-----+

                                . . .

             56    57    58    59    60    61    62    63
          +-----+-----+-----+-----+-----+-----+-----+-----+
      ... |   7 |   6 |   5 |   4 |   3 |   2 |   1 |   0 |
          +-----+-----+-----+-----+-----+-----+-----+-----+ 

Notes:

The bits were originally shown in the wrong order.

Errata 1739 tried to correct this by reversing the bits, but overlooked reversing the bytes.

Errata ID: 4984
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2017-03-30
Verifier Name: Benoit Claise
Date Verified: 2017-07-27

Section 5.2.10, appA says:

Each bit represents an Information Element in the Data Record 
with the n-th bit
representing the n-th Information Element.

It should say:

Each bit represents an Information Element in the Data Record,
with the n-th least significant bit
representing the n-th Information Element.

Notes:

A misunderstand arose as to whether bits were assigned in host order or network order - so clarify that the bits are assigned from the least significant to the most significant, ie right-to-left rather than left-to-right.

Moreover, this clarification applies to IANA's IPFIX registry.

NB RFC 8038 re-uses this definition for mibIndexIndicator. Consistency between the definitions is desirable.

Errata ID: 2879
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2011-08-01
Verifier Name: Dan Romascanu
Date Verified: 2011-08-02

Section 2.3 says:

   o  Middleboxes [RFC3234] may change Flow properties, such as the
      Differentiated Service Code Point (DSCP) value or the source IP
      address.  If an IPFIX Observation Point is located in the path of
      a Flow before one or more middleboxes that potentially modify
      packets of the Flow, then it may be desirable to also report Flow
      properties after the modification performed by the middleboxes.
      An example is an Observation Point before a packet marker changing
      a packet's IPv4 Type of Service (TOS) field that is encoded in
      Information Element classOfServiceIPv4.  Then the value observed
      and reported by Information Element classOfServiceIPv4 is valid at
      the Observation Point, but not after the packet passed the packet
      marker.  For reporting the change value of the TOS field, the
      IPFIX information model uses Information Elements that have a name
      prefix "post", for example, "postClassOfServiceIPv4".

It should say:

   o  Middleboxes [RFC3234] may change Flow properties, such as the
      Differentiated Service Code Point (DSCP) value or the source IP
      address.  If an IPFIX Observation Point is located in the path of
      a Flow before one or more middleboxes that potentially modify
      packets of the Flow, then it may be desirable to also report Flow
      properties after the modification performed by the middleboxes.
      An example is an Observation Point before a packet marker changing
      a packet's IPv4 Type of Service (TOS) field that is encoded in
      Information Element ipClassOfService.  Then the value observed
      and reported by Information Element ipClassOfService is valid at
      the Observation Point, but not after the packet passed the packet
      marker.  For reporting the change value of the TOS field, the
      IPFIX information model uses Information Elements that have a name
      prefix "post", for example, "postIpClassOfService".

Notes:

s/ClassOfServiceIPv4/ipClassOfService/ (twice)
s/postClassOfServiceIPv4/postIpClassOfService/ (once)

Also correct another instance of "postClassOfServiceIPv4" in section 5:

OLD
Information Elements with a name having the "post" prefix, for
example, "postClassOfServiceIPv4"
NEW
Information Elements with a name having the "post" prefix, for
example, "postIpClassOfService"
END

Status: Held for Document Update (1)

RFC 5102, "Information Model for IP Flow Information Export", January 2008

Note: This RFC has been obsoleted by RFC 7012

Note: This RFC has been updated by RFC 6313

Source of RFC: ipfix (ops)

Errata ID: 3101
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT

Reported By: Paul Aitken
Date Reported: 2012-01-31
Held for Document Update by: ron bonica

Section 5.9. says:

   Timestamps flowStartSysUpTime and flowEndSysUpTime are relative
   timestamps indicating the time relative to the last (re-
   )initialization of the IPFIX Device.  For reporting the time of the
   last (re-)initialization, systemInitTimeMilliseconds can be reported,
   for example, in Data Records defined by Option Templates.

It should say:

   Timestamps flowStartSysUpTime and flowEndSysUpTime are relative
   timestamps indicating the time relative to the last
   (re-)initialization of the IPFIX Device.  For reporting the time of the
   last (re-)initialization, systemInitTimeMilliseconds can be reported,
   for example, in Data Records defined by Option Templates.

Notes:

Poor formatting of "(re-)initialization" in the 3rd paragraph of section 5.9

Report New Errata



Advanced Search