RE: [VRRP] Comments on draft-ietf-vrrp-unified-mib-01.txt

[<Kalyan.Tata@nokia.com>]

Hi, 
	I am in the process of updating the draft with Mukesh's 
	comments and some other corrections I found. 

	I am sending this message to mibs mailing list to see 
	if any onc else has some comments/corrections/questions etc. 
	in the general MIB layout. 

	Please let me know if you have any comments and I will incorporate
	the changes in the updated draft I am planning to submit.

Thanks
kalyan


-----Original Message-----
From: vrrp-bounces@ietf.org [mailto:vrrp-bounces@ietf.org]On Behalf Of
ext Mukesh.Gupta@nokia.com
Sent: 12 September, 2004 00:25
To: Tata Kalyan (Nokia-ES/MtView)
Cc: srinivaskalyan@mailcity.com; vrrp@ietf.org
Subject: [VRRP] Comments on draft-ietf-vrrp-unified-mib-01.txt


Kalyan,

Another round of review for draft-ietf-vrrp-unified-mib-01.txt.
I have the following comments:

- The recent change in the VRRPv6 draft 06 version (unfortunately
  the draft has expired but can be accessed at 
  http://www.watersprings.org/pub/id/draft-ietf-vrrp-ipv6-spec-06.txt)
  allows multiple IPv6 address per virtual router.  The MIB needs to
  be updated for this change.
    0 Description of objects vrrpOperationsIpv4AddrCount, 
      vrrpOperationsPrimaryIpAddrType, vrrpOperationsPrimaryIpAddr 
      have to be changed.
    0 Page 22 says that the VRRP Associated Address Table is for 
      IPv4 only.  It needs to be changed.
    ...
    ...

- The difference between vrrpOperationsMasterIpAddr* and 
  vrrpOperationsPrimaryIpAddr* is not clear in the description.

- vrrpOperationsPriority: should we write that value 0 and 255
  should not be allowed.

- vrrpOperationsVersion DESCRIPTION: Should we say that this 
  object contains VRRP version instead of IP version.

- In the references, authors' names are listed by the rule:
  First author name should be <Lastname>, <First Initial>.
  and all the other authors are listed as <First Initial>. 
  <Lastname>, (e.g. McCloghrie, K., D. Perkins, J. Schoenwaelder
  ...)

Editorial:
- section 1: Do not refer to the draft.  Write RFC xxxx with a RFC
  editor note as done at other places in the same draft.

- Page 7: Put RFC editor note whereever RFC xxxx is mentioned.

Minor nits:
- 2 spaces are needed between the end of a sentence and the beginning
  of a new one.

- section 1, line 2: 2 spaces needed before Though :)

- page 6, line 2 of point number 4: remove some extra spaces.

- page 7, CONTACT-INFO: a blank line between Kalyan Tata and
  the Nokia Inc is not needed.

- Page 18, replace "Initiates" with "initiates" (small case i)

- Page 19, replace "Prior" with "prior"

- DESCRIPTION of vrrpOperationsMasterIpAddr:  replace "Source" with
  "source"

- Page 22, replace "Appropriately" with "appropriately"

- Page 22, replace "and the 'vrrpOperState' object" with "and allow 
  the 'vrrpOperState' object"

- Page 23, replace "transitioned to'initialize'" with "transitioned 
  to 'initialize'"

- Page 29, remove blank line between SYNTAX and MAX-ACCESS of 
  vrrpStatisticsIpTtlErrors

- Page 30, remove 2 blank lines between SYNTAX and MAX-ACCESS of 
  vrrpStatisticsInvldTypePktsRcvd

- Except in the name of the objects, replace all occurances of Ipv4
  and Ipv6 to IPv4 and IPv6

- In the authors' Addresses section: replace "Fair Child" with 
  "Fairchild" and replace "Mountainview" with "Mountain View"

Regards
Mukesh

_______________________________________________
vrrp mailing list
vrrp@ietf.org
https://www1.ietf.org/mailman/listinfo/vrrp