RFC Errata
RFC 4295, "Mobile IPv6 Management Information Base", April 2006
Source of RFC: mip6 (int)
Errata ID: 137
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2006-07-08
Held for Document Update by: Brian Haberman
Date Held: 2013-03-16
(7) description too unspecific, and punctuation The DESCRIPTION clause of the mip6HaCompliance2 MODULE-COMPLIANCE, on page 95, says: "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring of the home agent | functionality specifically the Home Agent List | and the home-agent-registration-related statistics, There are a number of INDEX objects [...] for reasons as in item (5) and item (6) above, it should better say: "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and | support detailed monitoring of the home agent | functionality, specifically the Home Agent List | and the home-agent-registration-related statistics. There are a number of INDEX objects [...] (8) punctuation, and extraneous blank line The DESCRIPTION clause of the mip6HaCompliance3 MODULE-COMPLIANCE, on page 96, says: "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring and control of the home agent | functionality specifically the Home Agent List | and the home-agent-registration-related statistics, | There are a number of INDEX objects [...] It should say (see above items for rationale and similarity): "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB and support monitoring and control of the home agent | functionality, specifically the Home Agent List | and the home-agent-registration-related statistics. There are a number of INDEX objects [...] (9) punctuation, and extraneous blank line The DESCRIPTION clause of the mip6HaReadOnlyCompliance2 MODULE-COMPLIANCE, on page 99, says: "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the home agent | functionality specifically the Home Agent List and the home-agent-registration-related statistics. | There are a number of INDEX objects [...] It should say (see above items for rationale and similarity): "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring of the home agent | functionality, specifically the Home Agent List and the home-agent-registration-related statistics. There are a number of INDEX objects [...] (10) punctuation, and extraneous blank line The DESCRIPTION clause of the mip6HaReadOnlyCompliance3 MODULE-COMPLIANCE, on page 101, says: "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and ? support monitoring and control of the home agent | functionality specifically the Home Agent List | and the home-agent-registration-related statistics, | There are a number of INDEX objects [...] It should say (see above items for rationale and similarity): "The compliance statement for SNMP entities that implement the MOBILEIPV6-MIB without support for read-write (i.e., in read-only mode) and support monitoring and control of the home agent | functionality, specifically the Home Agent List | and the home-agent-registration-related statistics. There are a number of INDEX objects [...] Furthermore, arguably the words "and control" should better be deleted since write access is not required.
Notes:
The items below are presented in RFC textual order.
I use change bars ('|' in column 1) and occasionally
up/down pointing marker lines ('^^^'/'vvv') to emphasize
the location of textual issues and/or proposed corrections.
Modified text has been re-adjusted to match RFC formatting
rules, where appropriate.
from pending