RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

Found 1 record.

Status: Held for Document Update (1)

RFC 5644, "IP Performance Metrics (IPPM): Spatial and Multicast", October 2009

Note: This RFC has been updated by RFC 6248

Source of RFC: ippm (tsv)

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

Reported By: Cypryan T. Klish II
Date Reported: 2010-07-09
Held for Document Update by: Lars Eggert

Section 2.7 says:

Figure 2 is ambiguous for two reasons:

Use "X" for both types of nodes: 1) the graphic only labels intermediate nodes with "X" and 2) both "nodes that are points of interest" and "nodes that are not points of interest" are label "X" in the note following the graphic. Thus there is no difference between nodes that are points of interest and those that are not, and the distinction between the two types is not apparent

The destination node "Dst" has no representation in the "Hosts" identifier column.  the "Dst" label is in the same vertical column as the Hosts

It should say:

Change a subset of intermediate nodes (all currently labeled X) to "Y". Change the second line of the note to read "'Y' are nodes thatare not points of interest.

Shift the "Hosts column to the left to provide vertical separation for "Dst". Label "Dst" as "K" in the hosts column.


It would be useful to clarify if the nodes that are points of interest must be contiguous or if the subset can truly be selected in an arbitrary fashion. For a contiguous subset of point of interest nodes it is suggested that it would be useful to associate this with a higher abstract architectural construct (container) since the group might well align with a physical or administrative segment, or provider specific segment of the network. This would aid in modeling the system for performance management applications since a one to one relationship can be created between the higher level container object and the segment object

Report New Errata

Advanced Search