| To: | Werner Almesberger <almesber@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: neighbour cache vs. invalid addresses |
| From: | "James R. Leu" <jleu@xxxxxxxxxxxxxx> |
| Date: | Sat, 29 Apr 2000 18:41:40 -0500 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <200004292230.AAA09376@lrcsun15.epfl.ch>; from Werner Almesberger on Sun, Apr 30, 2000 at 12:30:35AM +0200 |
| Organization: | none |
| References: | <20000429145725.A5529@doit.wisc.edu> <200004292230.AAA09376@lrcsun15.epfl.ch> |
| Reply-to: | jleu@xxxxxxxxxxxxxx |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Sun, Apr 30, 2000 at 12:30:35AM +0200, Werner Almesberger wrote: > James R. Leu wrote: > > Broadcast and multicast do have defined meanings on CLIP interfaces, > > mapping this meaning to the neigh_table is where the problem comes in. > > RFC1577 and (RFC2225 update of 1577) have little encouragement for > multicast (section 8 or 10) and make a rather fuzzy statement about > broadcast (section 7 or 9). > > You probably mean MARS, RFC2022. That's a different story. I was actually thinking of the way Cisco handles broadcast and multicast over static point-to-point or point-to-multipoint ATM sub interfaces. <snip> > It's more on how to make it fail gracefully :-) So does this mean there isn't any talk of adding this support? Jim -- James R. Leu |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: neighbour cache vs. invalid addresses, Werner Almesberger |
|---|---|
| Next by Date: | Re: neighbour cache vs. invalid addresses, Werner Almesberger |
| Previous by Thread: | Re: neighbour cache vs. invalid addresses, Werner Almesberger |
| Next by Thread: | Re: neighbour cache vs. invalid addresses, Werner Almesberger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |