Re: [dhcwg] Interface

Erik Nordmark <> Thu, 20 September 2001 08:24 UTC

Received: from ( [] (may be forged)) by (8.9.1a/8.9.1a) with ESMTP id EAA03704; Thu, 20 Sep 2001 04:24:59 -0400 (EDT)
Received: from (localhost []) by (8.9.1a/8.9.1) with ESMTP id EAA15411; Thu, 20 Sep 2001 04:23:02 -0400 (EDT)
Received: from (odin []) by (8.9.1a/8.9.1) with ESMTP id EAA15380 for <>; Thu, 20 Sep 2001 04:22:59 -0400 (EDT)
Received: from (patan.Sun.COM []) by (8.9.1a/8.9.1a) with ESMTP id EAA03691 for <>; Thu, 20 Sep 2001 04:22:55 -0400 (EDT)
Received: from bebop.France.Sun.COM ([]) by (8.9.3+Sun/8.9.3) with ESMTP id CAA06215; Thu, 20 Sep 2001 02:22:06 -0600 (MDT)
Received: from lillen (lillen []) by bebop.France.Sun.COM (8.10.2+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id f8K8MFg13464; Thu, 20 Sep 2001 10:22:15 +0200 (MET DST)
Date: Thu, 20 Sep 2001 10:18:00 +0200 (CEST)
From: Erik Nordmark <>
Reply-To: Erik Nordmark <>
Subject: Re: [dhcwg] Interface
To: Ted Lemon <>
Cc: Erik Nordmark <>, "Bernie Volz (EUD)" <>, "'Guja, ArturX'" <>,
In-Reply-To: "Your message with ID" <>
Message-ID: <Roam.SIMC.>
MIME-Version: 1.0
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <>

> > I suspect that the real constraint is that the client MUST send the
> > message on an interface attached to the same *LINK* as the interface it
> > is trying to configure. When the client has multiple interfaces attached to
> > the same link the server/relay can't tell which one was used (short of
> > inspecting the source MAC address which may or may not differ).
> How does the client know that two interfaces are attached to the same
> link?   Better to leave well enough alone.

I suspect IEEE 802.3ad could tell the client such a fact. Of course one
could view 802.3ad as providing a single interface to IP, but the scoped
address architecture does include the ability of having IP "see" multiple
interfaces to the same link.

But that's beside the point - which is to not overconstrain the spec 
with MUSTs that aren't quite true.


dhcwg mailing list