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:28:33 -0800 [thread overview]
Message-ID: <4394BF11.2070205@hp.com> (raw)
In-Reply-To: <4394BCD5.1060505@psc.edu>
John Heffner wrote:
> Jeroen Massar wrote:
>
>> I wonder how many RFC's it violates. An interface must only answer ARP's
>> on the interface that it is configured on, not anything else.
>
>
> Not true. See RFC 1122, section 3.3.4. The standard leaves this
> decision up to the implementation, for good reason.
>
> From 1122 (note the use of MAY, not MUST or SHOULD):
> "
> There are two key requirement issues related to multihoming:
>
> (A) A host MAY silently discard an incoming datagram whose
> destination address does not correspond to the physical
> interface through which it is received.
>
> (B) A host MAY restrict itself to sending (non-source-
> routed) IP datagrams only through the physical
> interface that corresponds to the IP source address of
> the datagrams.
> "
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
next prev parent reply other threads:[~2005-12-05 22:28 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 [this message]
2005-12-05 22:30 ` John Heffner
2005-12-05 22:43 ` Rick Jones
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=4394BF11.2070205@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).