RE: 2461bis and host-load-sharing

"Soliman, Hesham" <H.Soliman@flarion.com> Thu, 01 December 2005 18:06 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhspT-0003n5-VM; Thu, 01 Dec 2005 13:06:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EhspS-0003n0-VJ for ipv6@megatron.ietf.org; Thu, 01 Dec 2005 13:06:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26177 for <ipv6@ietf.org>; Thu, 1 Dec 2005 13:05:59 -0500 (EST)
Received: from mail.flarion.com ([63.103.94.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Eht9y-0007kN-TG for ipv6@ietf.org; Thu, 01 Dec 2005 13:27:59 -0500
Received: from ftmailserver.flariontech.com ([10.10.1.140]) by mail.flarion.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 1 Dec 2005 13:06:36 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 01 Dec 2005 13:06:36 -0500
Message-ID: <A11736FE943F1A408F8BBB1B9F5FE8AD03274ACE@ftmailserver.flariontech.com>
Thread-Topic: 2461bis and host-load-sharing
Thread-Index: AcX2E8IQQFk9JKBZSiOxJp+gAchBegAf2cEAAAIkOeAAAYgtQA==
From: "Soliman, Hesham" <H.Soliman@flarion.com>
To: Dave Thaler <dthaler@windows.microsoft.com>, Bob Hinden <bob.hinden@nokia.com>
X-OriginalArrivalTime: 01 Dec 2005 18:06:36.0671 (UTC) FILETIME=[F85980F0:01C5F6A1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Content-Transfer-Encoding: quoted-printable
Cc: ipv6@ietf.org
Subject: RE: 2461bis and host-load-sharing
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org


 > A draft standard can't have a normative reference to a proposed
 > standard.
 > 
 > I believe the options are:
 > a) remove the problematic text from 2461bis and don't replace it with
 > anything (i.e., be silent on the issue).  I'm not sure what the state
 > of 4311 changes to then, since it's updating an obsoleted RFC.
 > b) replace the text with a note that is classified as an 
 > informative reference to 4311.
 > c) replace the text with the 2 paragraphs from 4311, and have 2461bis
 > also obsolete 4311.  This doesn't yet qualify per Draft 
 > Standard rules
 > so I don't think this option is really viable without 
 > delaying 2461bis. 
 > 
 > I believe Hesham is suggesting (b), and if appropriate text can be
 > constructed I would support this.

=> Thanks for the detailed description. Yes I was suggesting (b) above.

Hesham

 > 
 > -Dave
 > 
 > > -----Original Message-----
 > > From: Soliman, Hesham [mailto:H.Soliman@flarion.com]
 > > Sent: Thursday, December 01, 2005 8:22 AM
 > > To: Bob Hinden
 > > Cc: Dave Thaler; ipv6@ietf.org
 > > Subject: RE: 2461bis and host-load-sharing
 > > 
 > > Hi Bob,
 > > 
 > >  > > Dave,
 > >  > >
 > >  > > I think we can handle this during IESG last call. Does anyone
 > >  > > oppose Dave's suggestion
 > >  > > below to update this statement according to RFC 4311 ?
 > >  >
 > >  > Before answering the question, what would the exact change be to
 > >  > draft-ietf-ipv6-2461bis-05.txt?
 > > 
 > > => Sorry, I think I assumed too much. I was proposing the 
 > removal of
 > > that sentence and replacing it with a reference to RFC 4311. I can
 > > send exact text to the list.
 > > 
 > > Hesham
 > > 
 > >  >
 > >  > One consideration is that the update to 2661 is being 
 > submitted at
 > >  > Draft standard and we need to be carefull to not make 
 > incompatible
 > >  > changes.  This probably not the case here, but I would 
 > like to see
 > >  > the proposed text.
 > >  >
 > >  > Thanks,
 > >  > Bob
 > >  >
 > >  >
 > >  > > Thx,
 > >  > > Hesham
 > >  > >
 > >  > > -----Original Message-----
 > >  > > From: ipv6-bounces@ietf.org
 > > [mailto:ipv6-bounces@ietf.org]On Behalf
 > > > Of Dave Thaler
 > > > Sent: Wednesday, November 23, 2005 1:37 PM
 > > > To: JINMEI Tatuya / ????
 > > > Cc: margaret@thingmagic.com; ipv6@ietf.org
 > > > Subject: 2461bis and host-load-sharing
 > > >
 > > > draft-ietf-ipv6-2461bis-05.txt  says in 6.3.6:
 > > >
 > > >     An implementation may choose to always return the 
 > same router or
 > > >
 > > >     cycle through the router list in a round-robin 
 > fashion as long
 > > >
 > > >     as it always returns a reachable or a probably 
 > reachable router
 > > >
 > > >     when one is available.
 > > >
 > > > However RFC 4311 
 > (draft-ietf-ipv6-host-load-sharing-04.txt) updates
 > > >
 > > > RFC 2461, is a Proposed Standard, and says:
 > > >
 > > >     [ND] ...
 > > >
 > > >     specifies that an implementation may always choose the same
 > router
 > > >
 > > >     (e.g., the first in the list) or may cycle through 
 > the routers
 > in
 > > >
 > > >     a round-robin manner.  Both of these suggestions are
 > problematic.
 > > >
 > > >     [...]
 > > >
 > > > If 2461bis is intended to obsolete RFC 2461, then I think the
 > > > statement
 > > >
 > > > in 6.3.6 should be updated to be in accordance with RFC 4311.
 > > > Otherwise
 > > >
 > > > RFC 4311 will have to be republished to update 2461bis.
 > > >
 > > > -Dave
 > > >
 > > > ========================================================
 > > > This email may contain confidential and privileged 
 > material for the
 > > > sole
 > > > use of the intended recipient.  Any review or distribution by
 > > > others is
 > > > strictly prohibited.  If you are not the intended 
 > recipient please
 > > > contact
 > > > the sender and delete all copies.
 > > > ========================================================
 > > >
 > > > 
 > --------------------------------------------------------------------
 > > > IETF IPv6 working group mailing list
 > > > ipv6@ietf.org
 > > > Administrative Requests: 
https://www1.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------