Re: multicast address for rip2
Fred Baker <fbaker@acc.com> Fri, 17 April 1992 22:46 UTC
Received: from nri.nri.reston.va.us by ietf.NRI.Reston.VA.US id aa02615;
17 Apr 92 18:46 EDT
Received: from nri.reston.va.us by NRI.Reston.VA.US id aa12096;
17 Apr 92 18:50 EDT
Received: from harvard.harvard.edu by NRI.Reston.VA.US id aa12082;
17 Apr 92 18:50 EDT
Received: by harvard.harvard.edu (5.54/a0.25)
(for IETF-archive@nri.reston.va.us) id AA27453; Fri, 17 Apr 92 17:48:20 EST
Received: by Xylogics.COM (4.12/4.7_jlv1/7/90)
id AA29188; Fri, 17 Apr 92 18:48:50 edt
Received: from saffron.acc.com (2040c081) by Xylogics.COM (4.12/4.7_jlv1/7/90)
id AA31303; Fri, 17 Apr 92 18:48:43 edt
Received: by saffron.acc.com (4.1/SMI-4.1)
id AA04783; Fri, 17 Apr 92 15:46:42 PDT
Date: Fri, 17 Apr 92 15:46:42 PDT
From: Fred Baker <fbaker@acc.com>
Message-Id: <9204172246.AA04783@saffron.acc.com>
To: postel@isi.edu
Subject: Re: multicast address for rip2
Cc: gmalkin@acc.com, ietf-rip@acc.com
>> Hi. I think you need an Ethernet multicast address, not an IP multicast >> address. True or False? Jon: The requirement is that RIP listeners be unable to hear RIP-II multicasts in certain contexts. RFC 1112 defines the way one does this as using an IP Multicast address, similar to OSPF's "All OSPF Routers" and "All OSPF Designated Routers". An Ethernet Multicast address only helps on Ethernet; On Token Ring, where the IP Functional Address or a Broadcast address would have to be used due to chip shortcomings, or on a point to point link that has little or no concept of data link addressing, IP is the only protocol that could do that filtering. The IP Multicast Address implies an Ethernet Multicast Address; but it's the IP Multicast that we need. Fred
- Re: multicast address for rip2 Fred Baker
- Re: multicast address for rip2 postel