From: Jeroen Massar <jeroen@unfix.org>
To: John Heffner <jheffner@psc.edu>
Cc: 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: Tue, 06 Dec 2005 00:10:59 +0100 [thread overview]
Message-ID: <4394C903.40801@unfix.org> (raw)
In-Reply-To: <4394C5B6.8020301@psc.edu>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
John Heffner wrote:
> Jeroen Massar wrote:
>> 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.
>>
>>
>> RFC1122 is a document about multicast. ARP is broadcast see the very old
>> RFC826/STD0037. Multicast didn't even work on much of the hardware from
>> the times that that document was written.
>
> ??? RFC 1122 is the Hosts Requirements RFC. It applies to any host
> implementing IP. Maybe you're thinking of 1112?
Oops, mixed up a number. 1122 refers to 826, with 1027 extending it
partially for situations where one is multihomed.
Section 3.3.4 of 1122 is about IP and not about ARP, which is, just like
IP directly on top of Ethernet.
Greets,
Jeroen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 238 bytes --]
next prev parent reply other threads:[~2005-12-05 23:10 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
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 [this message]
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=4394C903.40801@unfix.org \
--to=jeroen@unfix.org \
--cc=a1426z@gawab.com \
--cc=elf@buici.com \
--cc=greearb@candelatech.com \
--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).