Re: [dna] Applicability statement for Simple DNA (Providing text to resolve issue #11)

Julien Laganier <julien.laganier.ietf@googlemail.com> Wed, 24 September 2008 14:14 UTC

Return-Path: <dna-bounces@ietf.org>
X-Original-To: dna-archive@lists.ietf.org
Delivered-To: ietfarch-dna-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F3C728C285; Wed, 24 Sep 2008 07:14:32 -0700 (PDT)
X-Original-To: dna@core3.amsl.com
Delivered-To: dna@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0DD13A6D28 for <dna@core3.amsl.com>; Wed, 24 Sep 2008 07:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3h9mf2tlSHHC for <dna@core3.amsl.com>; Wed, 24 Sep 2008 07:14:29 -0700 (PDT)
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by core3.amsl.com (Postfix) with ESMTP id 40D9A3A6A07 for <dna@ietf.org>; Wed, 24 Sep 2008 07:14:29 -0700 (PDT)
Received: by fk-out-0910.google.com with SMTP id 18so2607430fkq.5 for <dna@ietf.org>; Wed, 24 Sep 2008 07:14:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:to:subject:date:user-agent:cc :references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id:from; bh=Omy4sahohnnqsaWH70qOVwJmDn2EkvcrZIaj+XYYCqk=; b=BE8HfIDzvxRzkFwdy2vA6rUfGmSCH15ccCMUuXQp21NsQeCDN75+8rd+h8GwTlAW/v Wnya+LfMj0Cu+3Ti/1c2jLLyPlF2ZHcETCVgfsHof5R3cqixgUehgGoIId0xlbFn3wkL F7ndjZmbhcyYo8QN4YyTUmiovOq9VsRnPI/WE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=to:subject:date:user-agent:cc:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id:from; b=pw5rJVD5mYDu8jhLp6jZNAAIG4d+B0MRiMAdeaZvUCnXg1zd/NtDb1W/eXu9CrTPBC L7LqZqU/BAZsOZc6XnieASdEj0qvUQcYjEha9DffwX3nRvHucjKTAyKWJ7NK+XCx8gcQ a6iP/xg/XiL7H04RbO3q5cOSUVYgW/d9+LJW4=
Received: by 10.187.248.1 with SMTP id a1mr1373222fas.24.1222265643322; Wed, 24 Sep 2008 07:14:03 -0700 (PDT)
Received: from klee.local ([212.119.9.178]) by mx.google.com with ESMTPS id 21sm2664203fkx.13.2008.09.24.07.14.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 24 Sep 2008 07:14:02 -0700 (PDT)
To: "Premec, Domagoj" <domagoj.premec@siemens.com>
Date: Wed, 24 Sep 2008 16:14:30 +0200
User-Agent: KMail/1.9.9
References: <48D905B2.4050108@ericsson.com> <200809241548.18327.julien.laganier.IETF@googlemail.com> <3C31CDD06342EA4A8137716247B1CD68045B2AD2@zagh223a.ww300.siemens.net>
In-Reply-To: <3C31CDD06342EA4A8137716247B1CD68045B2AD2@zagh223a.ww300.siemens.net>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200809241614.30437.julien.laganier.IETF@googlemail.com>
From: Julien Laganier <julien.laganier.ietf@googlemail.com>
Cc: dna@ietf.org
Subject: Re: [dna] Applicability statement for Simple DNA (Providing text to resolve issue #11)
X-BeenThere: dna@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNA working group mailing list <dna.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dna>, <mailto:dna-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/dna>
List-Post: <mailto:dna@ietf.org>
List-Help: <mailto:dna-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dna>, <mailto:dna-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dna-bounces@ietf.org
Errors-To: dna-bounces@ietf.org

As per RFC5213 all of the MAGs of a PMIPv6 domain that can serve as 
default router for a MN would present the same link-local address to 
the MN. The link-layer address is either pre-configured on all MAGs, or 
sent by the LMA to the MAG in a Binding Acknowledgement.

--julien

On Wednesday 24 September 2008, Premec, Domagoj wrote:
> I was thinking of both the IP and the link-layer address. From the
> host perspective, this looks similar to the case where the current
> default router goes down and at the same time a new default router
> appears on the link. I'm not sure about the case where both ARs are
> using the same IP address but their link layer addresses are
> different. Updating only the link layer address while the IP address
> remains the same may be considered as a special case, but I'm not
> sure if there are any security considerations.
>
> domagoj
>
> > -----Original Message-----
> > From: Julien Laganier [mailto:julien.laganier.ietf@googlemail.com]
> > Sent: 24. rujan 2008 15:48
> > To: dna@ietf.org
> > Cc: Premec, Domagoj; Suresh Krishnan; JinHyeock Choi; JinHyeock
> > Choi Subject: Re: [dna] Applicability statement for Simple DNA
> > (Providing text to resolve issue #11)
> >
> > Quick question for clarification.
> >
> > You said "the host should quickly update its default router
> > to the address of the new AR".
> >
> > By "address" I'm assuming you mean "link layer address". Is
> > that correct?
> >
> > --julien
> >
> > On Wednesday 24 September 2008, Premec, Domagoj wrote:
> > > I think that there may be cases where the host may benefit
> >
> > from simple
> >
> > > DNA even when it attaches to a previously unvisited link.
> >
> > For example,
> >
> > > as the host moves within the PMIP domain, the IPv6 prefix
> >
> > assigned to
> >
> > > the host moves together with the host across ARs (MAGs).
> > > When attaching to a new link the host will see the new AR
> >
> > advertising
> >
> > > the same prefix, but the old AR will not be reachable any more.
> > > In this case, the host should quickly update its default router
> > > to the address of the new AR to avoid loosing packets sent to the
> >
> > address of
> >
> > > a previous default router. There is no need for the host to
> > > execute any address configuration/verification procedures. This
> >
> > would provide
> >
> > > better handover perfomance when moving within the PMIP
> >
> > domain. Is this
> >
> > > someting that could be accomodated by the simple DNA?
> > >
> > > domagoj
> > >
> > > > -----Original Message-----
> > > > From: dna-bounces@ietf.org [mailto:dna-bounces@ietf.org]
> >
> > On Behalf
> >
> > > > Of Suresh Krishnan
> > > > Sent: 23. rujan 2008 17:05
> > > > To: dna@ietf.org; JinHyeock Choi; JinHyeock Choi
> > > > Subject: [dna] Applicability statement for Simple DNA
> > > > (Providing text to resolve issue #11)
> > > >
> > > > Hi Folks,
> > > >
> > > >    I propose to add the following text to a new section called
> > > > "Applicability" to resolve issue #11. The previous
> > > > applicability section will be moved into a new section called
> > > > "Working assumptions".
> > > >
> > > > NEW TEXT:
> > > > =========
> > > >
> > > >     The Simple DNA protocol is provides substantial
> >
> > benefits in some
> >
> > > > scenarios and does not provide any benefit at all in
> >
> > certain other
> >
> > > > scenarios.  This is intentional as Simple DNA was designed for
> > > > simplicity rather than completeness.  In particular, the
> >
> > Simple DNA
> >
> > > >     protocol provides maximum benefits when a host moves
> >
> > between a
> >
> > > > small
> > > >     set of known links.  When a host moves to a
> >
> > completely new link
> >
> > > > that
> > > >     is previously unknown, the performance of the Simple DNA
> > > > protocol will be identical to that using standard
> >
> > neighbor discovery
> >
> > > > procedures [RFC4861].
> > > >
> > > > If you have any issues with this text, please respond to
> >
> > this mail
> >
> > > > on list.
> > > >
> > > > Thanks
> > > > Suresh
> > > >
> > > > _______________________________________________
> > > > dna mailing list
> > > > dna@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/dna
> > >
> > > _______________________________________________
> > > dna mailing list
> > > dna@ietf.org
> > > https://www.ietf.org/mailman/listinfo/dna
_______________________________________________
dna mailing list
dna@ietf.org
https://www.ietf.org/mailman/listinfo/dna