Re: [dhcwg] Interface

Ted Lemon <mellon@nominum.com> Fri, 21 September 2001 16:12 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 MAA29714; Fri, 21 Sep 2001 12:12:01 -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 MAA18101; Fri, 21 Sep 2001 12:10:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA18073 for <dhcwg@ns.ietf.org>; Fri, 21 Sep 2001 12:10:18 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29663 for <dhcwg@ietf.org>; Fri, 21 Sep 2001 12:10:55 -0400 (EDT)
Received: from grosse.bisbee.fugue.com (205-140-116-229.ip.theriver.com [205.140.116.229]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id f8LFgEv14271; Fri, 21 Sep 2001 08:42:14 -0700 (PDT)
Received: from grosse.bisbee.fugue.com (localhost [127.0.0.1]) by grosse.bisbee.fugue.com (8.11.3/8.6.11) with ESMTP id f8LGA9t01896; Fri, 21 Sep 2001 09:10:09 -0700 (MST)
Message-Id: <200109211610.f8LGA9t01896@grosse.bisbee.fugue.com>
To: Erik Nordmark <Erik.Nordmark@eng.sun.com>
cc: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>, "'Guja, ArturX'" <ArturX.Guja@intel.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] Interface
In-Reply-To: Message from Erik Nordmark <Erik.Nordmark@eng.sun.com> of "Fri, 21 Sep 2001 10:26:56 +0200." <Roam.SIMC.2.0.6.1001060816.11273.nordmark@bebop.france>
Date: Fri, 21 Sep 2001 09:10:09 -0700
From: Ted Lemon <mellon@nominum.com>
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

> OK - I sense the equivalent of grade inflation here caused by
> presumed clueless implementors. Need to update RFC 2119 with the
> "REALLY MUST" and "REALLY MUST NOT" to deal with this :-) :-)

*grin*    I think there's some truth to it, but you're making it out to
 be worse than it is.

> No, I did NOT! Please re-read the email thread.

Oops, sorry.

> 	MUST send on that interface since otherwise the agent will be
> 	confused.
> This statement is incorrect.

Okay, I'll buy that.

> But if the statement is instead
> 	MUST send on that interface to ensure that the packet is guaranteed
> 	to appear on the correct link (*). If the message appears on the wrong
> 	link the agent will be confused.
> 	*) This ensures that the packet arrives on the correct link even
> 	in the case when a node has multiple interfaces on the same link
> 	but has incorrect information about which interfaces connect to
> 	which links.
> I think the footnote can be omitted - but it might help future readers to
> understand the background.

This wording works for me (I'll let Ralph decide about the footnote).
Thanks for continuing to beat me up about this!  :'}

			       _MelloN_

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
http://www1.ietf.org/mailman/listinfo/dhcwg