RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt

"Narayanan Vidya-CVN065" <vidya@motorola.com> Tue, 25 October 2005 19:54 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUsP-0008PW-T3; Tue, 25 Oct 2005 15:54:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUUsO-0008P4-41 for mip6@megatron.ietf.org; Tue, 25 Oct 2005 15:54:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16337 for <mip6@ietf.org>; Tue, 25 Oct 2005 15:54:13 -0400 (EDT)
Received: from motgate8.mot.com ([129.188.136.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUV5I-00088o-SR for mip6@ietf.org; Tue, 25 Oct 2005 16:07:55 -0400
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131]) by motgate8.mot.com (8.12.11/Motgate7) with ESMTP id j9PK6AtZ023506 for <mip6@ietf.org>; Tue, 25 Oct 2005 13:06:10 -0700 (MST)
Received: from de01exm69.ds.mot.com (de01exm69.am.mot.com [10.176.8.25]) by il06exr01.mot.com (8.13.1/8.13.0) with ESMTP id j9PK4A8K024304 for <mip6@ietf.org>; Tue, 25 Oct 2005 15:04:10 -0500 (CDT)
x-mimeole: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Date: Tue, 25 Oct 2005 15:54:06 -0400
Message-ID: <0B40B6F9CB990B428819561A2A55613A10416E@de01exm69.ds.mot.com>
Thread-Topic: [Mip6] draft-dupont-mip6-dhaadharmful-00.txt
Thread-Index: AcXZmden90FGxjanR6GWQ3RjjXy6dgAA1E1A
From: Narayanan Vidya-CVN065 <vidya@motorola.com>
To: Francis.Dupont@enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
Cc: mip6@ietf.org, Kilian Weniger <Kilian.Weniger@eu.panasonic.com>, James Kempf <Kempf@docomolabs-usa.com>, Petrescu Alexandru-AAP021 <alexandru.petrescu@motorola.com>
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

>    
>    1. Are we working on failover mechanisms in the WG? 
>    
> => yes, "Improving home agent reliability" is in the charter 
> and clearly something needed for deployment.
> 

Yes, it seems to be in the charter. But, I recall that the chairs were
questioning this in Paris - there seemed to be some feeling that this
can be vendor specific for the moment and it was agreed that we would
discuss on the ML to decide if it is critical enough to be looked at in
the WG right now. I might have missed the discussion - was there a
consensus on this? 

Anyway, I would agree that this is important. 


>    2. Are we working on load balancing mechanisms in the WG? 
>    
> => it is not explicitely in the charter.

But, there certainly is a lot of discussion on this topic on the ML :) 

> 
>    3. Do we expect a common architecture/solution to solve the two? 
>    
> => I believe the answer is no because failover is far easier.
> 
>    If the answer to 3 is 'yes', then I think we are limited 
> in the number
>    of solutions to consider (and this, I believe, is likely 
> to be a good
>    thing). 
>    
> => but a 'yes' to 3 can be an obstacle to find quickly good 
> solutions for failover...


Agreed. But, looking at the number of discussions that are hinging on
load balancing, we must either consciously keep them separate or combine
them. Combining them is good from an architectural standpoint, but, as
you say, it is likely to delay quick solutions for failover. 

> 
> PS: the right way is to get feedback from operators: the goal 
> of the IETF is not to produce X pages of junk specs per day, 
> but to provide good (i.e., fulfilling real requirements) 
> specs to operators and customers.
> At least it should be the goal...
> 

I second that :) 

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6