Re: What's the good word?

Anil Rijsinghani <anil@levers.enet.dec.com> Fri, 15 May 1992 01:15 UTC

Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa04588; 14 May 92 21:15 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa16507; 14 May 92 21:21 EDT
Received: from harvard.harvard.edu by NRI.Reston.VA.US id aa16502; 14 May 92 21:21 EDT
Received: by harvard.harvard.edu (5.54/a0.25) (for IETF-archive@nri.reston.va.us) id AA15723; Thu, 14 May 92 21:20:33 EDT
Received: by Xylogics.COM (4.12/4.7_jlv1/7/90) id AA31307; Thu, 14 May 92 20:59:51 edt
Received: from inet-gw-2.pa.dec.com (17000110) by Xylogics.COM (4.12/4.7_jlv1/7/90) id AA30553; Thu, 14 May 92 20:59:45 edt
Received: by inet-gw-2.pa.dec.com; id AA00206; Thu, 14 May 92 17:59:17 -0700
Received: by us1rmc.mso.dec.com; id AA15909; Thu, 14 May 92 20:58:47 -0400
Message-Id: <9205150058.AA15909@us1rmc.mso.dec.com>
Received: from levers.enet; by us1rmc.enet; Thu, 14 May 92 20:58:58 EDT
Date: Thu, 14 May 92 20:58:58 EDT
From: Anil Rijsinghani <anil@levers.enet.dec.com>
To: gmalkin@levers.enet.dec.com, ietf-rip@levers.enet.dec.com
Cc: anil@levers.enet.dec.com
Apparently-To: ietf-rip@xylogics.com, gmalkin@xylogics.com
Subject: Re: What's the good word?

    Some comments on the two RIP-2 documents.  I have not monitored
    this list on a regular basis, so some of these may be due to
    a lack of background:

    1) The description of the "Routing Domain" and "Subnet Mask" sections
       are rather sketchy.  A clearer explanation of "RIP clouds" (and
       why they are needed), "subsumption", etc would be very helpful.

    2) The "Multicasting" section doesn't explain why IGMP (IP multicast)
       is a requirement.  This question, which was brought up on the
       list a couple of weeks back, drew some responses on
       why IP rather than hardware multicast is needed which left
       me somewhat confused.

       One school of thought held that since RIP packets are exchanged
       at the IP level, hardware addresses should not be mentioned.
       This (in my opinion) doesn't seem to be a sufficient reason to
       require yet another protocol - you want to make it easy for
       RIP-1 to be upgraded.  Another view said that it helped in ignoring
       certain messages, but it seems to me that there are other fields
       that can be used in the new format to achieve this, if it is
       indeed a requirement..

    Anil