netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: John Heffner <jheffner@psc.edu>
Cc: Jeroen Massar <jeroen@unfix.org>, Marc Singer <elf@buici.com>,
	Ben Greear <greearb@candelatech.com>, Al Boldi <a1426z@gawab.com>,
	netdev@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [RFC] ip / ifconfig redesign
Date: Mon, 05 Dec 2005 14:43:53 -0800	[thread overview]
Message-ID: <4394C2A9.6000606@hp.com> (raw)
In-Reply-To: <4394BF9E.90303@psc.edu>

John Heffner wrote:
> Rick Jones wrote:
> 
>> That's the discussion related to things like the "Strong ES" (end 
>> system) model right?  As such, isn't that discussing what _IP_ may do 
>> rather than what ARP may do?  1122 doesn't say much about the 
>> interfaces/MAC's that should be part of a given ARP reply.  ARP seems 
>> to be RFC 826 and probably others, and the algorithm described in 826 
>> doesn't seem to be specific on the topic of interfaces - at least not 
>> to my really brief read.
>>
>> rick jones
> 
> 
> Yes, but if an interface will accept packets for a certain IP address, 
> and will send packets with that IP address, is there any reason it can't 
> ARP for that address?

If ARP RFC's say it shouldn't :) (I don't know that it does) ARP is ARP, 
accepting IPs is IP.  The maze of twisty passages may be similar, but they are 
distinct.

Is a MAC address a property of the host, or of the interface connected to the host?

rick jones
is on netdev, so no need for direct reply to my address...

  reply	other threads:[~2005-12-05 22:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02 19:53 [RFC] ip / ifconfig redesign Al Boldi
2005-12-02 19:59 ` Pekka Savola
2005-12-02 20:08 ` Ben Greear
2005-12-02 20:38 ` linux-os (Dick Johnson)
2005-12-02 22:49   ` Jesper Juhl
2005-12-10 18:51   ` Stefan Smietanowski
2005-12-02 22:40 ` Jeff V. Merkey
2005-12-03 13:46 ` Al Boldi
2005-12-03 18:33   ` Ben Greear
2005-12-03 20:25     ` Al Boldi
2005-12-05 14:01     ` John W. Linville
2005-12-05 14:20       ` Jeroen Massar
2005-12-05 17:40       ` Marc Singer
2005-12-05 17:59         ` Jeroen Massar
2005-12-05 20:56           ` Marc Singer
2005-12-05 22:19           ` John Heffner
2005-12-05 22:28             ` Rick Jones
2005-12-05 22:30               ` John Heffner
2005-12-05 22:43                 ` Rick Jones [this message]
2005-12-05 23:03                   ` John Heffner
2005-12-06  5:13                     ` Marc Singer
2005-12-05 22:48             ` Jeroen Massar
2005-12-05 22:56               ` John Heffner
2005-12-05 23:10                 ` Jeroen Massar
2005-12-06  5:18               ` Marc Singer
2005-12-05 18:00         ` Ben Greear
2005-12-05 20:10           ` John W. Linville
2005-12-05 21:03           ` Marc Singer
2005-12-05 20:48       ` Al Boldi
2005-12-14 14:19 ` Al Boldi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4394C2A9.6000606@hp.com \
    --to=rick.jones2@hp.com \
    --cc=a1426z@gawab.com \
    --cc=elf@buici.com \
    --cc=greearb@candelatech.com \
    --cc=jeroen@unfix.org \
    --cc=jheffner@psc.edu \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).