RE: [dhcwg] Interface

"Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se> Thu, 20 September 2001 18:01 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17800; Thu, 20 Sep 2001 14:01:13 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA05136; Thu, 20 Sep 2001 13:54:10 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA05112 for <dhcwg@optimus.ietf.org>; Thu, 20 Sep 2001 13:54:08 -0400 (EDT)
Received: from imr1.ericy.com (imr1.ericy.com [208.237.135.240]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17539 for <dhcwg@ietf.org>; Thu, 20 Sep 2001 13:54:04 -0400 (EDT)
Received: from mr6.exu.ericsson.se (mr6u3.ericy.com [208.237.135.123]) by imr1.ericy.com (8.11.3/8.11.3) with ESMTP id f8KHrP712896 for <dhcwg@ietf.org>; Thu, 20 Sep 2001 12:53:25 -0500 (CDT)
Received: from eamrcnt749 (eamrcnt749.exu.ericsson.se [138.85.133.47]) by mr6.exu.ericsson.se (8.11.3/8.11.3) with SMTP id f8KHrPR26472 for <dhcwg@ietf.org>; Thu, 20 Sep 2001 12:53:25 -0500 (CDT)
Received: FROM eamrcnt761.exu.ericsson.se BY eamrcnt749 ; Thu Sep 20 12:53:24 2001 -0500
Received: by eamrcnt761.exu.ericsson.se with Internet Mail Service (5.5.2653.19) id <THQPN8XN>; Thu, 20 Sep 2001 12:53:24 -0500
Message-ID: <66F66129A77AD411B76200508B65AC697B3638@eambunt705.ena-east.ericsson.se>
From: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
To: "'Erik Nordmark'" <Erik.Nordmark@eng.sun.com>, Ted Lemon <mellon@nominum.com>
Cc: "'Guja, ArturX'" <ArturX.Guja@intel.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] Interface
Date: Thu, 20 Sep 2001 12:53:15 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C141FD.1FA06060"
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org

Perhaps I'm confused, but don't we have an issue that we should attempt to resolve when a client has multiple interfaces to the same link?

A client may not know this.

I believe IAs should be client specific, not interface specific. But, that still doesn't solve the problem because hows does the server know that there are two interfaces on that client? (Instead of treating all IAs to belong to the first interface.) This could lead to significant problems if we allow a server to tell a client all of the IAs for that client on that link (in an Advertise, for example).

- Bernie

-----Original Message-----
From: Erik Nordmark [mailto:Erik.Nordmark@eng.sun.com]
Sent: Thursday, September 20, 2001 1:12 PM
To: Ted Lemon
Cc: Erik Nordmark; Bernie Volz (EUD); 'Guja, ArturX'; dhcwg@ietf.org
Subject: Re: [dhcwg] Interface 


> 
> > But that's beside the point - which is to not overconstrain the spec 
> > with MUSTs that aren't quite true.
> 
> The point is to come up with a working, implementable protocol
> definition, that does not only work if you happen to be running
> 802.3ad in a certain obscure implementation.

Ted,

the tone of your statement reads like an attack on a particular unnamed 
implementation.  I certainly did not describe an existing implementation -
in fact I have no idea whether there exists an IEEE 802.3ad that does what
I described. (And the whole mention about implementation was in response to
a question whether there was an automatic way for hosts to determine that
multiple interfaces are connected to the same link.) Sigh :-(

What I did point out is that the IPv6 architecture allows multiple interfaces
connected to the same link. That is the real issue.

> Most implementors will not run into the corner case you've just
> described, but those same implementors have a pretty good chance of
> producing a non-interoperable client implementation if that MUST isn't
> there.  In the corner case you've described, unless I am very much
> mistaken, the MUST will _not_ cause a problem.  So the MUST should
> stay.

I don't think MUSTs are intended to prescribe rules for a subset of
the implementations - their original use was to describe (often subtle)
things that implementors had overlooked in the past that caused rather bad
things to the network (such a broadcast storms).
Today MUSTs are used to make firm statements for behavior
that applies to all implementations.

So you seem to be describing a case where a SHOULD applies. RFC 2119:
3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.

Alternatively text along the lines of this makes sense
	"... MUST (unless where the client has multiple interfaces connected to
	the same link [SCOPING-ARCH] in which case the ... MUST be for one
	of the interfaces connected to the same link) ..."

  Erik