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

"Premec, Domagoj" <domagoj.premec@siemens.com> Wed, 24 September 2008 14:04 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 7985428C24D; Wed, 24 Sep 2008 07:04:17 -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 CD3703A6DD3 for <dna@core3.amsl.com>; Wed, 24 Sep 2008 07:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level:
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 5R1Z7nrSYRKb for <dna@core3.amsl.com>; Wed, 24 Sep 2008 07:04:13 -0700 (PDT)
Received: from mxs2.siemens.at (mxs2.siemens.at [194.138.12.133]) by core3.amsl.com (Postfix) with ESMTP id 8B86528C2E9 for <dna@ietf.org>; Wed, 24 Sep 2008 07:03:51 -0700 (PDT)
Received: from vies1kbx.sie.siemens.at ([158.226.129.82]) by mxs2.siemens.at with ESMTP id m8OE3bLF005345; Wed, 24 Sep 2008 16:03:37 +0200
Received: from nets139a.ww300.siemens.net ([192.168.217.3]) by vies1kbx.sie.siemens.at (8.12.11.20060308/8.12.1) with ESMTP id m8OE3Y1I002095; Wed, 24 Sep 2008 16:03:34 +0200
Received: from zagh223a.ww300.siemens.net ([141.29.124.9]) by nets139a.ww300.siemens.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Sep 2008 16:03:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 24 Sep 2008 16:03:21 +0200
Message-ID: <3C31CDD06342EA4A8137716247B1CD68045B2AD2@zagh223a.ww300.siemens.net>
In-Reply-To: <200809241548.18327.julien.laganier.IETF@googlemail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dna] Applicability statement for Simple DNA (Providing text to resolve issue #11)
Thread-Index: AckeTCudgGiIWWl2Q1O5K7QKTOznQwAACedA
References: <48D905B2.4050108@ericsson.com> <3C31CDD06342EA4A8137716247B1CD68045B2A3B@zagh223a.ww300.siemens.net> <200809241548.18327.julien.laganier.IETF@googlemail.com>
From: "Premec, Domagoj" <domagoj.premec@siemens.com>
To: Julien Laganier <julien.laganier.ietf@googlemail.com>, dna@ietf.org
X-OriginalArrivalTime: 24 Sep 2008 14:03:33.0029 (UTC) FILETIME=[54795550:01C91E4E]
X-purgate: clean
X-purgate: This mail is considered clean
X-purgate-type: clean
X-purgate-Ad: Checked for Spam by eleven - eXpurgate www.eXpurgate.net
X-purgate-ID: 149917::080924160337-0B627BA0-7DDE3091/0-0/0-15
X-purgate-size: 4089/999999
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

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
> 
> 
> 
> --
> --julien
> 
> [ New email address: julien.laganier.IETF@googlemail.com ]
> 
_______________________________________________
dna mailing list
dna@ietf.org
https://www.ietf.org/mailman/listinfo/dna