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:08 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 7B6AC3A6DE0; Wed, 24 Sep 2008 07:08:44 -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 8E0D83A6DEC for <dna@core3.amsl.com>; Wed, 24 Sep 2008 07:08:43 -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 i4XgNqtNqiJo for <dna@core3.amsl.com>; Wed, 24 Sep 2008 07:08:38 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by core3.amsl.com (Postfix) with ESMTP id 827D53A69D9 for <dna@ietf.org>; Wed, 24 Sep 2008 07:08:14 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id d23so1986333fga.41 for <dna@ietf.org>; Wed, 24 Sep 2008 07:07:47 -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 :references:in-reply-to:cc:mime-version:content-type :content-transfer-encoding:content-disposition:message-id:from; bh=71V/pcjEz+Zr3oNQnPDQFDd5ybiC9B5aK/+XdizCbF4=; b=l5TRG2s+AkggWebknFdOY2clUADMR61Sjon0YmY+uB7wgsm2oPInikKQaG5TNSSKxF wDg1x3W2PdJDdx3wuQkPigltxd7vj96G+RD9GR2pfCO53hxrM35XxhXqw+RB0AWev5my jXdvHCKFIkQbJ8o8Uu7oKmqZlJ+9x+DNZXWk4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=to:subject:date:user-agent:references:in-reply-to:cc:mime-version :content-type:content-transfer-encoding:content-disposition :message-id:from; b=MnuFSXabVKwiLO7ShZHmzroBtR3sC8whtSg+ziNuhSsr+0AvbRYOUmbzLm1M8xCDK7 vBimSM860WPNFz/A4QJLbtELCcr7AW1psphvZ/xFnIiuoGNQS32URrr5F65KQlFTdyF9 2xaolHVGngfQtug4nQHTzCGWvGlkv3fZF7HIo=
Received: by 10.187.223.14 with SMTP id a14mr1366414far.3.1222265267114; Wed, 24 Sep 2008 07:07:47 -0700 (PDT)
Received: from klee.local ([212.119.9.178]) by mx.google.com with ESMTPS id 31sm2925826fkt.3.2008.09.24.07.07.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 24 Sep 2008 07:07:45 -0700 (PDT)
To: dna@ietf.org
Date: Wed, 24 Sep 2008 16:08:13 +0200
User-Agent: KMail/1.9.9
References: <48D905B2.4050108@ericsson.com> <3C31CDD06342EA4A8137716247B1CD68045B2A3B@zagh223a.ww300.siemens.net> <48DA483D.8090106@ericsson.com>
In-Reply-To: <48DA483D.8090106@ericsson.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200809241608.13501.julien.laganier.IETF@googlemail.com>
From: Julien Laganier <julien.laganier.ietf@googlemail.com>
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

Hello Suresh,

Why would different ARs use same MAC address.

By the way, may I suggest that DNA documents use the term link layer 
address rather than MAC address? 

I know it's longer but the MAC qualifier sounds a bit too specific to 
me...

--julien

 On Wednesday 24 September 2008, Suresh Krishnan wrote:
> Hi Domagoj,
>    In my view (or should I say in the MN's view) of the PMIP spec the
> new AR will be indistinguishable from the old AR. This is because the
> old AR will have the same link local AND MAC addresses. So, this is
> semantically equivalent to detaching and attaching to the SAME link.
> Hence Simple DNA will already work well with this scenario as well
> with no modifications.
>
> Thanks
> Suresh
>
> 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