From dna-owner@webcamserver.eng.monash.edu.au  Fri Sep 10 10:11:43 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28726
	for <dna-archive@lists.ietf.org>; Fri, 10 Sep 2004 10:11:42 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LEPZ21K61M8Y60YH@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 11 Sep 2004 00:11:05 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 6A522AB545; Sat,
 11 Sep 2004 00:11:01 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 1F5354FB04; Sat,
 11 Sep 2004 00:11:01 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8AEA1O26158	for dna-list; Sat, 11 Sep 2004 00:10:01 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8AE9u626141	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 11 Sep 2004 00:09:56 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LEPZ0J84TU91WAQI@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 11 Sep 2004 00:09:48 +1000
Received: by localhost (Postfix, from userid 510)	id 8557A80002; Sat,
 11 Sep 2004 00:09:48 +1000 (EST)
Received: from jaju.cvnet.co.kr (unknown [219.252.92.142])
	by larry.its.monash.edu.au (Postfix) with SMTP id 23BBE3C011	for
 <dna@eng.monash.edu.au>; Sat, 11 Sep 2004 00:09:47 +1000 (EST)
Received: from 221.147.157.248 (221.147.157.248) by jaju.cvnet.co.kr with ZMAIL
 SMTP; Fri, 10 Sep 2004 23:09:27 +0900
Date: Fri, 10 Sep 2004 23:09:21 +0900
From: JinHyeock Choi <jinchoe@diffeo.com>
Subject: [DNA] [Announce] DNA in IPv6 Goals 01 I-D
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        Greg Daley <greg.daley@eng.monash.edu.au>
Cc: Dna <dna@eng.monash.edu.au>, jinchoe@samsung.com
Message-id: <00b501c4973f$c811f390$f89d93dd@jinchoe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
X-Spam-Level: **
References: <A381524E-6B51-11D8-8A26-000393CE1E8C@nomadiclab.com>
 <006c01c422ad$3ad1a180$ee2f024b@jinchoe>
 <00b501c45042$4dcf9590$f52f024b@jinchoe>
Content-Transfer-Encoding: 7BIT

Dear DNA Group

We have closed the existing issues and updated the issue list
accordingly. Kindly check it out at 

http://ctieware.eng.monash.edu.au/twiki/bin/view/DNA/DNAGoals

Also, incorporating the resolutions, we have updated DNA in IPv6 
Goals draft and submitted it. This draft is available at the URL:

http://www.diffeo.com/drafts/draft-ietf-dna-goals-01.txt
 
Soon we will have WG last call on it and your feedback will be 
highly appreciated. 

Thanks in advance for your kind consideration.

Best Regards

JinHyeock Choi and Greg Daley
(Authors)



From dna-owner@webcamserver.eng.monash.edu.au  Fri Sep 10 15:56:07 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27853
	for <dna-archive@lists.ietf.org>; Fri, 10 Sep 2004 15:56:06 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LEQB3G1PZO91WGWR@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Sat, 11 Sep 2004 05:56:02 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id DDCC6AB544; Sat,
 11 Sep 2004 05:55:44 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id D59B14FB0E; Sat,
 11 Sep 2004 05:55:38 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8AJsoU29874	for dna-list; Sat, 11 Sep 2004 05:54:50 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8AJsg629868	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 11 Sep 2004 05:54:42 +1000
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LEQB1Y64L68Y62AQ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Sat,
 11 Sep 2004 05:54:33 +1000
Received: by localhost (Postfix, from userid 510)	id C94CCAB542; Sat,
 11 Sep 2004 05:54:32 +1000 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 615D94FB05	for
 <dna@eng.monash.edu.au>; Sat, 11 Sep 2004 05:54:28 +1000 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27610; Fri,
 10 Sep 2004 15:54:23 -0400 (EDT)
Date: Fri, 10 Sep 2004 15:54:23 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-goals-01.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <200409101954.PAA27610@ietf.org>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_BE/xV+FXGyi8/Q0M+q0e1w)"
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)


--Boundary_(ID_BE/xV+FXGyi8/Q0M+q0e1w)
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Detecting Network Attachment Working Group of the IETF.

	Title		: Detecting Network Attachment in IPv6 Goals
	Author(s)	: J. Choi, G. Daley
	Filename	: draft-ietf-dna-goals-01.txt
	Pages		: 14
	Date		: 2004-9-10
	
At the time a host establishes a new link-layer connection, it may or
   may not have a valid IP configuration for Internet connectivity.  The
   host may check for link change, i.e.  determine whether a link change
   has occurred, and then, based on the result, it can automatically
   decide whether its IP configuration is still valid or not.  During
   link identity detection, the host may also collect necessary
   information to initiate a new IP configuration for the case that the
   IP subnet has changed.  In this memo, this procedure is called
   Detecting Network Attachment (DNA).  DNA schemes should be precise,
   sufficiently fast, secure and of limited signaling.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dna-goals-01.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dna-goals-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dna-goals-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_BE/xV+FXGyi8/Q0M+q0e1w)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_ohAoS/3ao/zDzEDIqtsZHw)"


--Boundary_(ID_ohAoS/3ao/zDzEDIqtsZHw)
Content-type: Message/External-body; server="mailserv@ietf.org";
 access-type=mail-server

Content-Type: text/plain
Content-ID:	<2004-9-10154151.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dna-goals-01.txt

--Boundary_(ID_ohAoS/3ao/zDzEDIqtsZHw)
Content-type: Message/External-body; directory=internet-drafts;
 access-type=anon-ftp; site=ftp.ietf.org; name=draft-ietf-dna-goals-01.txt
Content-disposition: attachment; filename=draft-ietf-dna-goals-01.txt

Content-Type: text/plain
Content-ID:	<2004-9-10154151.I-D@ietf.org>

--Boundary_(ID_ohAoS/3ao/zDzEDIqtsZHw)--

--Boundary_(ID_BE/xV+FXGyi8/Q0M+q0e1w)--


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 13 04:51:56 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07094
	for <dna-archive@lists.ietf.org>; Mon, 13 Sep 2004 04:51:54 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LETUPSPJRI96VLMN@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Mon, 13 Sep 2004 18:51:38 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 36605AB542; Mon,
 13 Sep 2004 18:49:47 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id E3DD14FB02; Mon,
 13 Sep 2004 18:49:46 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8D8ktQ06948	for dna-list; Mon, 13 Sep 2004 18:46:55 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8D8kt606944	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 13 Sep 2004 18:46:55 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LETUM6OW7I8X0ZGI@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Mon,
 13 Sep 2004 18:46:52 +1000
Received: by localhost (Postfix, from userid 510)	id 9EB14AB545; Mon,
 13 Sep 2004 18:46:52 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 02E8B4FB0D	for
 <dna@eng.monash.edu.au>; Mon, 13 Sep 2004 18:46:50 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP id 5237022000B	for
 <dna@eng.monash.edu.au>; Mon, 13 Sep 2004 11:46:46 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix)
 with ESMTP id 95E9A8	for <dna@eng.monash.edu.au>; Mon,
 13 Sep 2004 11:46:46 +0300 (EEST)
Date: Mon, 13 Sep 2004 11:46:47 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: [DNA] WG Last Call on draft-ietf-dna-goals-01.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Message-id: <726FF7DE-0561-11D9-B7CE-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT

WG Last Call on draft-ietf-dna-goals-01.txt starts today and runs for 
two
weeks, until Sep 27. This draft is intended to define a set of goals for
detecting network attachment, describing existing issues and important
properties of potential solutions.

It is *very important* that this draft be read and commented on by the 
WG
prior to submission to the IESG. Please make an effort to review the 
draft
within the Last Call period, and submit any comments to the mailing list
(any major comments) or directly the editor (JinHyeock, minor comments 
only).

The draft is available at the repository:
http://www.ietf.org/internet-drafts/draft-ietf-dna-goals-01.txt

--Greg & Pekka, the chairs



From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 23 03:18:35 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18149
	for <dna-archive@lists.ietf.org>; Thu, 23 Sep 2004 03:18:34 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LF7QAP83TA8ZE2CP@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 23 Sep 2004 17:14:21 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 3FB6980039; Thu,
 23 Sep 2004 17:13:47 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id EF8773C00D; Thu, 23 Sep 2004 17:13:46 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8N7CWv25561	for dna-list; Thu, 23 Sep 2004 17:12:32 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8N7CV625557	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 23 Sep 2004 17:12:31 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF7Q8DTZPS9PM0KO@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 23 Sep 2004 17:12:19 +1000
Received: by localhost (Postfix, from userid 510)	id B16D58002C; Thu,
 23 Sep 2004 17:11:26 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 07B3D3C013	for
 <dna@eng.monash.edu.au>; Thu, 23 Sep 2004 17:11:25 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP id 4967F22000B	for
 <dna@eng.monash.edu.au>; Thu, 23 Sep 2004 10:11:22 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix)
 with ESMTP id B2C7E8	for <dna@eng.monash.edu.au>; Thu,
 23 Sep 2004 10:11:22 +0300 (EEST)
Date: Thu, 23 Sep 2004 10:11:26 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Message-id: <C8988AF9-0D2F-11D9-A57E-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
Content-Transfer-Encoding: 7BIT

This is a reminder that the WG LC on draft-ietf-dna-goals-01.txt
is running and ends on next Monday, Sep 27th.  Please do read
the draft, and send your comments to the ML, even if it is
"I read it and I think it is good".

http://www.ietf.org/internet-drafts/draft-ietf-dna-goals-01.txt

--Greg & Pekka, the chairs



From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 23 03:29:51 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18761
	for <dna-archive@lists.ietf.org>; Thu, 23 Sep 2004 03:29:50 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF7QQ2LEE49EEBN0@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Thu, 23 Sep 2004 17:27:26 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 17A3080046; Thu,
 23 Sep 2004 17:25:49 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id C7D133C007; Thu, 23 Sep 2004 17:25:48 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8N7PgR25724	for dna-list; Thu, 23 Sep 2004 17:25:42 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8N7Pg625720	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 23 Sep 2004 17:25:42 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF7QOMPAYU9PM0KR@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 23 Sep 2004 17:25:25 +1000
Received: by localhost (Postfix, from userid 510)	id 5507280077; Thu,
 23 Sep 2004 17:23:24 +1000 (EST)
Received: from zmamail04.zma.compaq.com
 (zmamail04.zma.compaq.com [161.114.64.104])	by larry.its.monash.edu.au
 (Postfix) with ESMTP id B55273C00F	for <dna@eng.monash.edu.au>; Thu,
 23 Sep 2004 17:23:21 +1000 (EST)
Received: from tayexg11.americas.cpqcorp.net
 (tayexg11.americas.cpqcorp.net [16.103.130.186])	by zmamail04.zma.compaq.com
 (Postfix) with ESMTP	id DCAA250A5; Thu, 23 Sep 2004 03:23:19 -0400 (EDT)
Received: from tayexc13.americas.cpqcorp.net ([16.103.130.26])
 by tayexg11.americas.cpqcorp.net with Microsoft SMTPSVC(6.0.3790.0); Thu,
 23 Sep 2004 03:23:19 -0400
Date: Thu, 23 Sep 2004 03:23:20 -0400
From: "Bound, Jim" <jim.bound@hp.com>
Subject: RE: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        Dna <dna@eng.monash.edu.au>
Message-id: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Precedence: bulk
Thread-Topic: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
Thread-Index: AcShPZ+30CRs7L3uQmGzL2lP92KB9QAAIotw
Content-class: urn:content-classes:message
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
X-OriginalArrivalTime: 23 Sep 2004 07:23:19.0735 (UTC)
 FILETIME=[3380F470:01C4A13E]
Content-Transfer-Encoding: 7BIT

I read it and I think it is good.  Good work.
Sorry,
/jim 

> -----Original Message-----
> From: owner-dna@ecselists.eng.monash.edu.au 
> [mailto:owner-dna@ecselists.eng.monash.edu.au] On Behalf Of 
> Pekka Nikander
> Sent: Thursday, September 23, 2004 3:11 AM
> To: Dna
> Subject: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt 
> is running
> 
> This is a reminder that the WG LC on 
> draft-ietf-dna-goals-01.txt is running and ends on next 
> Monday, Sep 27th.  Please do read the draft, and send your 
> comments to the ML, even if it is "I read it and I think it is good".
> 
> http://www.ietf.org/internet-drafts/draft-ietf-dna-goals-01.txt
> 
> --Greg & Pekka, the chairs
> 
> 


From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 23 04:40:27 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22610
	for <dna-archive@lists.ietf.org>; Thu, 23 Sep 2004 04:40:26 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF7T1YRSRY9EE9EL@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Thu, 23 Sep 2004 18:33:40 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 26C9FAB543; Thu,
 23 Sep 2004 18:33:25 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id C8C3A4FB03; Thu, 23 Sep 2004 18:33:24 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8N8X6Y26502	for dna-list; Thu, 23 Sep 2004 18:33:06 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8N8X5626498	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 23 Sep 2004 18:33:05 +1000
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LF7T1FTUWQ8ZE26K@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Thu,
 23 Sep 2004 18:33:00 +1000
Received: by localhost (Postfix, from userid 510)	id D242CAB548; Thu,
 23 Sep 2004 18:32:59 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 01B2F4FB12	for
 <dna@eng.monash.edu.au>; Thu, 23 Sep 2004 18:32:58 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP id 41E4022000B	for
 <dna@eng.monash.edu.au>; Thu, 23 Sep 2004 11:32:56 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix)
 with ESMTP id A8BA18	for <dna@eng.monash.edu.au>; Thu,
 23 Sep 2004 11:32:56 +0300 (EEST)
Date: Thu, 23 Sep 2004 11:33:00 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: [DNA] WG LC comments on draft-ietf-dna-goals-01.txt
In-reply-to: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Message-id: <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
Content-Transfer-Encoding: 7BIT

> This is a reminder that the WG LC on
> draft-ietf-dna-goals-01.txt is running and ends on next
> Monday, Sep 27th.  Please do read the draft, and send your
> comments to the ML, even if it is "I read it and I think it is good".
>
> http://www.ietf.org/internet-drafts/draft-ietf-dna-goals-01.txt

Overall, I think that the draft is pretty good.  I am sending some
minor edits directly to the authors.

What is more considerable, in my opinion, are the following:

   1. I think we should make clear in the Introduction that
      we are here only dealing with IPv6.  That is clear from
      the context, i.e. our charter, but it should also be
      clearly stated _early_ in the document.  (Or did I just
      miss it?)

   2. I suggest that we add the following paragraph to the
      beginning of Section 3, just after the section title.

    The DNA working group has been chartered to define an improved
    scheme for detecting IPv6 network attachment.  In this section,
    we define the goals that any such solutions should aim to fulfil.

   3. With regard to goal G10, which currently states that ...

>      DNA schemes should take into consideration the case where a host
>      is attached to more than one link at the same time.

     ... should we add "or multiple times to the same link"?

--Pekka Nikander



From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 23 08:09:54 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05444
	for <dna-archive@lists.ietf.org>; Thu, 23 Sep 2004 08:09:52 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LF80I081FA8X2GUT@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 23 Sep 2004 22:06:28 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id A4D47AB542; Thu,
 23 Sep 2004 22:06:23 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 5C9E64FB03; Thu, 23 Sep 2004 22:06:23 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8NC5tA28417	for dna-list; Thu, 23 Sep 2004 22:05:55 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8NC5s628413	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 23 Sep 2004 22:05:54 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF80H8VRSO9TCO0Z@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 23 Sep 2004 22:05:47 +1000
Received: by localhost (Postfix, from userid 510)	id 1024AAB543; Thu,
 23 Sep 2004 22:05:47 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 746D24FB09; Thu,
 23 Sep 2004 22:05:46 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id A363322000C; Thu,
 23 Sep 2004 15:05:44 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id 1657F9; Thu,
 23 Sep 2004 15:05:45 +0300 (EEST)
Date: Thu, 23 Sep 2004 15:05:49 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: [DNA] New WG I-D: draft-ietf-dna-link-information
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Cc: Alper Yegin <alper.yegin@samsung.com>,
        Greg Daley <greg.daley@eng.monash.edu.au>
Message-id: <E8573EDC-0D58-11D9-A57E-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT

The chairs have decided to adopt draft-yegin-dna-l2-hints-02.txt
as a WG document, with the name draft-ietf-dna-link-information-00.txt

The draft editor is Alper Yegin.  We expect the draft to appear
in the I-D repositories in the near future.  Please read the
drafts and send comments to the list.  We hope to have the
draft ready for WG LC around the Washington D.C. IETF meeting.

--Pekka & Greg



From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 23 21:34:29 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10735
	for <dna-archive@lists.ietf.org>; Thu, 23 Sep 2004 21:34:25 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF8SJVF0V69EECKC@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Fri, 24 Sep 2004 11:29:52 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 1EBB880009; Fri,
 24 Sep 2004 11:29:37 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id C02C93C011; Fri, 24 Sep 2004 11:29:36 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8O1Su903801	for dna-list; Fri, 24 Sep 2004 11:28:56 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8O1St603797	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 24 Sep 2004 11:28:55 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF8SIO8C9A9EEI3B@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 24 Sep 2004 11:28:40 +1000
Received: by localhost (Postfix, from userid 510)	id 8DC3380007; Fri,
 24 Sep 2004 11:28:39 +1000 (EST)
Received: from mailout3.samsung.com (mailout3.samsung.com [203.254.224.33])
	by larry.its.monash.edu.au (Postfix) with ESMTP id AFAE73C003	for
 <dna@eng.monash.edu.au>; Fri, 24 Sep 2004 11:28:34 +1000 (EST)
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I4I00B38URKM9@mailout3.samsung.com> for dna@eng.monash.edu.au; Fri,
 24 Sep 2004 10:28:32 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
 by mailout3.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I4I0031IUR389@mailout3.samsung.com> for dna@eng.monash.edu.au;
 Fri, 24 Sep 2004 10:28:15 +0900 (KST)
Received: from jinchoe ([75.2.91.233])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTPA id <0I4I00HJRUR24D@mmp1.samsung.com> for dna@eng.monash.edu.au;
 Fri, 24 Sep 2004 10:28:14 +0900 (KST)
Date: Fri, 24 Sep 2004 10:28:15 +0900
From: JinHyeock Choi <jinchoe@samsung.com>
Subject: Re: [DNA] WG LC comments on draft-ietf-dna-goals-01.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        Dna <dna@eng.monash.edu.au>
Message-id: <011301c4a1d5$c3742010$e95b024b@jinchoe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka

Thanks for kind and helpful comments. 

> > This is a reminder that the WG LC on
> > draft-ietf-dna-goals-01.txt is running and ends on next
> > Monday, Sep 27th.  Please do read the draft, and send your
> > comments to the ML, even if it is "I read it and I think it is good".
> >
> > http://www.ietf.org/internet-drafts/draft-ietf-dna-goals-01.txt
> 
> Overall, I think that the draft is pretty good.  I am sending some
> minor edits directly to the authors.
> 
> What is more considerable, in my opinion, are the following:
> 
>    1. I think we should make clear in the Introduction that
>       we are here only dealing with IPv6.  That is clear from
>       the context, i.e. our charter, but it should also be
>       clearly stated _early_ in the document.  (Or did I just
>       miss it?)

The name of the draft is 'Detecting Network Attachment in 
IPv6 Goals' and I thought that was explicit enough. :-) 

Do you still think we need an additional statement? If so, 
I will add it in the Introduction.  

>    2. I suggest that we add the following paragraph to the
>       beginning of Section 3, just after the section title.
> 
>     The DNA working group has been chartered to define an improved
>     scheme for detecting IPv6 network attachment.  In this section,
>     we define the goals that any such solutions should aim to fulfil.

ok. 

>    3. With regard to goal G10, which currently states that ...
> 
> >      DNA schemes should take into consideration the case where a host
> >      is attached to more than one link at the same time.
> 
>      ... should we add "or multiple times to the same link"?

G10 is about the special case that a host is attached to multiple links 
at the same time and hears different RAs from different links. 

I see few reason to add "or multiple times to the same link". I think 
that's a different case and we may obscure the main issue, 'multiple 
attachment', if we add that.  

Thanks for your kind consideration. 
 
Best Regards

JinHyeock 


From dna-owner@webcamserver.eng.monash.edu.au  Fri Sep 24 04:03:20 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17707
	for <dna-archive@lists.ietf.org>; Fri, 24 Sep 2004 04:03:19 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LF969PR54U8ZE2J9@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 24 Sep 2004 18:02:30 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id C32BF80013; Fri,
 24 Sep 2004 18:02:17 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 4C7533C016; Fri, 24 Sep 2004 18:02:17 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8O81QL07538	for dna-list; Fri, 24 Sep 2004 18:01:26 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8O81P607534	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 24 Sep 2004 18:01:25 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LF968EB7HU8X2RH8@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Fri,
 24 Sep 2004 18:01:14 +1000
Received: by localhost (Postfix, from userid 510)	id 4FC8EAB549; Fri,
 24 Sep 2004 18:01:14 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 032014FB0E	for
 <dna@eng.monash.edu.au>; Fri, 24 Sep 2004 18:01:13 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id 86F68220010; Fri,
 24 Sep 2004 11:01:10 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id ED3FF9; Fri,
 24 Sep 2004 11:01:10 +0300 (EEST)
Date: Fri, 24 Sep 2004 11:01:14 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] WG LC comments on draft-ietf-dna-goals-01.txt
In-reply-to: <011301c4a1d5$c3742010$e95b024b@jinchoe>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@samsung.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
Content-Transfer-Encoding: 7BIT

>>    1. I think we should make clear in the Introduction that
>>       we are here only dealing with IPv6.  That is clear from
>>       the context, i.e. our charter, but it should also be
>>       clearly stated _early_ in the document.  (Or did I just
>>       miss it?)
>
> The name of the draft is 'Detecting Network Attachment in
> IPv6 Goals' and I thought that was explicit enough. :-)
>
> Do you still think we need an additional statement? If so,
> I will add it in the Introduction.

Please do.  The change may be as simple as changing "IP"
on the second line of introduction to "IPv6", just as a
reminder.

If you want to put there more, I would suggest also changing
the second last line of introduction:

>    Detecting Network Attachment (DNA).  DNA schemes should be precise,

s/Attachment (DNA)/Attachment for IPv6 (DNA)/

Or, alternatively, to add to the end of introduction:

    This draft considered the DNA procedure only from IPv6 point
    of view, unless otherwise explicitly mentioned.  Hence, the
    term "IP" is to be understood to denote IPv6 by default.

Or something like that.


[My issue #2 removed as we seem to agree on it.]

>>    3. With regard to goal G10, which currently states that ...
>>
>>>      DNA schemes should take into consideration the case where a host
>>>      is attached to more than one link at the same time.
>>
>>      ... should we add "or multiple times to the same link"?
>
> G10 is about the special case that a host is attached to multiple links
> at the same time and hears different RAs from different links.
>
> I see few reason to add "or multiple times to the same link". I think
> that's a different case and we may obscure the main issue, 'multiple
> attachment', if we add that.

Well, I was thinking about the situation where the host is
connected through several interfaces to the same link.
In some way, this is a special case of a host being connected
through several interfaces to several different links.

I am not sure how to formulate that properly, but IMHO the whole
continuum should be covered by G10.  I don't see it covered
by the other goals.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Fri Sep 24 16:29:51 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16686
	for <dna-archive@lists.ietf.org>; Fri, 24 Sep 2004 16:29:50 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LF9WD6YEC09EDEFE@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Sat, 25 Sep 2004 06:29:42 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id E19A980003; Sat,
 25 Sep 2004 06:29:33 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 871ED3C007; Sat, 25 Sep 2004 06:29:28 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8OKSTL14644	for dna-list; Sat, 25 Sep 2004 06:28:29 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8OKSG614638	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 25 Sep 2004 06:28:17 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LF9WBARNM88X2YOH@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Sat,
 25 Sep 2004 06:28:02 +1000
Received: by localhost (Postfix, from userid 510)	id 4BDD580003; Sat,
 25 Sep 2004 06:28:02 +1000 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 775293C00C	for
 <dna@eng.monash.edu.au>; Sat, 25 Sep 2004 06:28:00 +1000 (EST)
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I4K00001BILJ4@mailout2.samsung.com> for dna@eng.monash.edu.au; Sat,
 25 Sep 2004 05:27:57 +0900 (KST)
Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I4K00DZOBILX6@mailout2.samsung.com> for dna@eng.monash.edu.au;
 Sat, 25 Sep 2004 05:27:57 +0900 (KST)
Received: from Alperyegin ([105.253.155.6])
 by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTPA id <0I4K00D41BIDPU@mmp1.samsung.com> for dna@eng.monash.edu.au;
 Sat, 25 Sep 2004 05:27:57 +0900 (KST)
Date: Fri, 24 Sep 2004 13:27:49 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <C8988AF9-0D2F-11D9-A57E-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "'Dna'" <dna@eng.monash.edu.au>
Message-id: <007501c4a274$fa46da70$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
Content-Transfer-Encoding: 7BIT


Hello,

This document looks pretty good. I have couple of comments...

   To examine the status of the existing configuration, a host may check
   whether a 'link change' has occurred.  The term 'link' used in this
   document is as defined in RFC 2461 [4].

I think it is OK to talk about "link change" throughout the document.
But the first time it is brought up, I recommend its relation to "subnet
change" should be mentioned. Or, the relation between a link and a
subnet.

There should be an explicit statement about this work being limited to
IPv6, together with a reference to IPv4 work (DNAv4).

   Unlike wired environments, what constitutes wireless link is variable
   in both time and space.  It doesn't have clear boundaries.  This may
   be illustrated by the fact that a host may contact multiple (802.11)
   access points at the same time.

We better clarify what "contact" means. Is it being able to hear the
APs, or establish a link-layer connection with the APs, or something
else?

   Hints come in various forms, and differ in how they indicate a
   possible link change.  They can be link-layer event notifications,

You can put a reference to dna-l2-notifications I-D in here.

  G10 Hosts with multiple interfaces or in particular wireless
      environments may perceive routers reachable on different links.
      DNA schemes should take into consideration the case where a host
      is attached to more than one link at the same time.

I think DNA scheme is run per-interface. If so, we shall state that
somewhere in the document.

Regards,

Alper





From dna-owner@webcamserver.eng.monash.edu.au  Fri Sep 24 20:54:04 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06041
	for <dna-archive@lists.ietf.org>; Fri, 24 Sep 2004 20:54:03 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFA5AVQ7D08ZE3PQ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 25 Sep 2004 10:45:54 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 3FA8380004; Sat,
 25 Sep 2004 10:45:47 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id D5AD03C008; Sat, 25 Sep 2004 10:45:46 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8P0jDW16997	for dna-list; Sat, 25 Sep 2004 10:45:13 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8P0jD616992	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 25 Sep 2004 10:45:13 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFA59U91HU9ULRFZ@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat,
 25 Sep 2004 10:44:57 +1000
Received: by localhost (Postfix, from userid 510)	id F29F3AB54F; Sat,
 25 Sep 2004 10:44:56 +1000 (EST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 958044FD40	for
 <dna@eng.monash.edu.au>; Sat, 25 Sep 2004 05:37:10 +1000 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08724; Fri,
 24 Sep 2004 15:37:05 -0400 (EDT)
Date: Fri, 24 Sep 2004 15:37:05 -0400
From: Internet-Drafts@ietf.org
Subject: [DNA] I-D ACTION:draft-ietf-dna-link-information-00.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: i-d-announce@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <200409241937.PAA08724@ietf.org>
MIME-version: 1.0
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_SpEtCnyoN9A9HI1AeWldRw)"
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)


--Boundary_(ID_SpEtCnyoN9A9HI1AeWldRw)
Content-type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Detecting Network Attachment Working Group of the IETF.

	Title		: Link-layer Event Notifications for Detecting 
			  Network Attachments
	Author(s)	: A. Yegin, et al.
	Filename	: draft-ietf-dna-link-information-00.txt
	Pages		: 17
	Date		: 2004-9-24
	
Certain network access technologies are capable of providing various
link-layer status information to IP.  Link-layer event notifications
can help IP expeditiously detect configuration changes.  This draft
provides a non-exhaustive catalogue of information available from
well-known access technologies.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dna-link-information-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-dna-link-information-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dna-link-information-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--Boundary_(ID_SpEtCnyoN9A9HI1AeWldRw)
Content-type: MULTIPART/ALTERNATIVE;
 BOUNDARY="Boundary_(ID_Xn/Hj2jadMiKFIN3/J4fKA)"


--Boundary_(ID_Xn/Hj2jadMiKFIN3/J4fKA)
Content-type: Message/External-body; server="mailserv@ietf.org";
 access-type=mail-server

Content-Type: text/plain
Content-ID:	<2004-9-24145720.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dna-link-information-00.txt

--Boundary_(ID_Xn/Hj2jadMiKFIN3/J4fKA)
Content-type: Message/External-body; directory=internet-drafts;
 access-type=anon-ftp; site=ftp.ietf.org;
 name=draft-ietf-dna-link-information-00.txt
Content-disposition: attachment; filename=draft-ietf-dna-link-information-00.txt

Content-Type: text/plain
Content-ID:	<2004-9-24145720.I-D@ietf.org>

--Boundary_(ID_Xn/Hj2jadMiKFIN3/J4fKA)--

--Boundary_(ID_SpEtCnyoN9A9HI1AeWldRw)--


From dna-owner@webcamserver.eng.monash.edu.au  Sat Sep 25 07:55:48 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22027
	for <dna-archive@lists.ietf.org>; Sat, 25 Sep 2004 07:55:46 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFASOWA0J68X2DYA@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Sat, 25 Sep 2004 21:55:21 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 90696AB543; Sat,
 25 Sep 2004 21:55:15 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 468B74FB03; Sat, 25 Sep 2004 21:55:15 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8PBrxk23222	for dna-list; Sat, 25 Sep 2004 21:53:59 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8PBrv623218	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 25 Sep 2004 21:53:57 +1000
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFASN69WMW8ZE431@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Sat,
 25 Sep 2004 21:53:52 +1000
Received: by localhost (Postfix, from userid 510)	id 75A9DAB54D; Sat,
 25 Sep 2004 21:53:52 +1000 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by moe.its.monash.edu.au (Postfix) with ESMTP id BE7A84FB03	for
 <dna@eng.monash.edu.au>; Sat, 25 Sep 2004 21:53:48 +1000 (EST)
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I4L00001IDMKE@mailout2.samsung.com> for dna@eng.monash.edu.au; Sat,
 25 Sep 2004 20:53:46 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I4L00HG2IDLSZ@mailout2.samsung.com> for dna@eng.monash.edu.au;
 Sat, 25 Sep 2004 20:53:46 +0900 (KST)
Received: from jinchoe ([75.2.91.233])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I4L004HVIDLZF@mmp2.samsung.com> for
 dna@eng.monash.edu.au; Sat, 25 Sep 2004 20:53:45 +0900 (KST)
Date: Sat, 25 Sep 2004 20:53:46 +0900
From: JinHyeock Choi <jinchoe@samsung.com>
Subject: Re: [DNA] WG LC comments on draft-ietf-dna-goals-01.txt
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Dear Pekka

> > The name of the draft is 'Detecting Network Attachment in
> > IPv6 Goals' and I thought that was explicit enough. :-)
> >
> > Do you still think we need an additional statement? If so,
> > I will add it in the Introduction.
> 
> Please do.  The change may be as simple as changing "IP"
> on the second line of introduction to "IPv6", just as a
> reminder.

ok. I did this. 
 
> If you want to put there more, I would suggest also changing
> the second last line of introduction:
> 
> >    Detecting Network Attachment (DNA).  DNA schemes should be precise,
> 
> s/Attachment (DNA)/Attachment for IPv6 (DNA)/
> 
> Or, alternatively, to add to the end of introduction:
> 
>     This draft considered the DNA procedure only from IPv6 point
>     of view, unless otherwise explicitly mentioned.  Hence, the
>     term "IP" is to be understood to denote IPv6 by default.
> 
> Or something like that.

I added the above at the end of introduction. 

> >>    3. With regard to goal G10, which currently states that ...
> >>
> >>>      DNA schemes should take into consideration the case where a host
> >>>      is attached to more than one link at the same time.
> >>
> >>      ... should we add "or multiple times to the same link"?
> >
> > G10 is about the special case that a host is attached to multiple links
> > at the same time and hears different RAs from different links.
> >
> > I see few reason to add "or multiple times to the same link". I think
> > that's a different case and we may obscure the main issue, 'multiple
> > attachment', if we add that.
> 
> Well, I was thinking about the situation where the host is
> connected through several interfaces to the same link.
> In some way, this is a special case of a host being connected
> through several interfaces to several different links.
> 
> I am not sure how to formulate that properly, but IMHO the whole
> continuum should be covered by G10.  I don't see it covered
> by the other goals.

DNA scheme is run per-interface because some IP configuration, 
such as IPv6 address, is interface specific. 

There arise complexities if an interface of a host is attached to 
multiple links at the same time. For example, the presence of 
a different link identifier doesn't mean that the host is disconnected 
from the current link. 
 
However, when multiple interfaces of a host are connected to the 
same link, it will result in few problem. Each interface may run DNA 
scheme to check for link change and update its IP configuration in 
case of a link change. 

I think the expression 'multiple interfaces' in G10 is confusing. 
I propose to change G 10 as

   G10 Hosts in particular wireless environments may perceive routers
      reachable on different links.  DNA schemes should take into
      consideration the case where a host is attached to more than one
      link at the same time.

Also, as Alper pointed, we'd better explicitly mention that DNA is 
run per-interface. I added the following in Introduction.  

   ..........................of its IP configuration, is called Detecting Network
   Attachment (DNA).

   DNA scheme is run per interface because some IP configuration, such
   as IPv6 address, is interface specific.  When a host has multiple
   interfaces, each interface separately check for link change to verify
   each one's IP configuration.
 
The updated draft is available at 

http://www.diffeo.com/drafts/draft-ietf-dna-goals-02.txt

Best Regards

JinHyeock 



From dna-owner@webcamserver.eng.monash.edu.au  Sat Sep 25 07:57:25 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22103
	for <dna-archive@lists.ietf.org>; Sat, 25 Sep 2004 07:57:24 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFASQIDVHA9EEQW2@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Sat, 25 Sep 2004 21:56:44 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id A855EAB54D; Sat,
 25 Sep 2004 21:56:33 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 525204FB04; Sat,
 25 Sep 2004 21:56:33 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8PBuV723281	for dna-list; Sat, 25 Sep 2004 21:56:31 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8PBuU623277	for
 <dna@ecselists.eng.monash.edu.au>; Sat, 25 Sep 2004 21:56:30 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFASQ3QU6A8X2SLD@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Sat,
 25 Sep 2004 21:56:14 +1000
Received: by localhost (Postfix, from userid 510)	id 2D55380003; Sat,
 25 Sep 2004 21:56:14 +1000 (EST)
Received: from mailout1.samsung.com (mailout1.samsung.com [203.254.224.24])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 72F573C006	for
 <dna@eng.monash.edu.au>; Sat, 25 Sep 2004 21:56:12 +1000 (EST)
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 id <0I4L00401IHL56@mailout1.samsung.com> for dna@eng.monash.edu.au; Sat,
 25 Sep 2004 20:56:09 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0I4L00BHLIHLVN@mailout1.samsung.com> for dna@eng.monash.edu.au;
 Sat, 25 Sep 2004 20:56:09 +0900 (KST)
Received: from jinchoe ([75.2.91.233])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I4L00DAWIHL8W@mmp2.samsung.com> for
 dna@eng.monash.edu.au; Sat, 25 Sep 2004 20:56:09 +0900 (KST)
Date: Sat, 25 Sep 2004 20:56:09 +0900
From: JinHyeock Choi <jinchoe@samsung.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@samsung.com>, "'Dna'" <dna@eng.monash.edu.au>
Message-id: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: <007501c4a274$fa46da70$291d9069@sisa.samsung.com>
Content-Transfer-Encoding: 7BIT

Dear Alper

Thanks for helpful feedback. 

> This document looks pretty good. I have couple of comments...
> 
>    To examine the status of the existing configuration, a host may check
>    whether a 'link change' has occurred.  The term 'link' used in this
>    document is as defined in RFC 2461 [4].
> 
> I think it is OK to talk about "link change" throughout the document.
> But the first time it is brought up, I recommend its relation to "subnet
> change" should be mentioned. Or, the relation between a link and a
> subnet.

ok. I made a change as below. 

   To examine the status of the existing configuration, a host may check
   whether a 'link change' has occurred.  The term 'link' used in this
   document is as defined in RFC 2461 [4].  The notion 'link' is not
   identical with the notion 'subnet' as defined in RFC 3753 [7].  For
   example, there may be more than one subnets in a link.

More detailed comparison, I think, would be better done in terminology 
draft. It's my understanding that terminology related issues, such as Jason 
issue, will be treated there. 
 
> There should be an explicit statement about this work being limited to
> IPv6, together with a reference to IPv4 work (DNAv4).

ok. 

I explicitly mentioned 'IPv6 Only' as Pekka's suggested. At the end of 
Introduction, I added

   This draft considered the DNA procedure only from IPv6 point of view,
   unless otherwise explicitly mentioned.  Hence, the term "IP" is to be
   understood to denote IPv6 by default.  For IPv4 case, refer [15].

>    Unlike wired environments, what constitutes wireless link is variable
>    in both time and space.  It doesn't have clear boundaries.  This may
>    be illustrated by the fact that a host may contact multiple (802.11)
>    access points at the same time.
> 
> We better clarify what "contact" means. Is it being able to hear the
> APs, or establish a link-layer connection with the APs, or something
> else?

Precisely speaking, 

a host may be under the wireless coverage of more than one APs.

Definitely, not multiple link-layer connections because that's not allowed 
in 802.11 standard. I intentionally used the word 'contact' instead of 
'connect with'.  

>    Hints come in various forms, and differ in how they indicate a
>    possible link change.  They can be link-layer event notifications,
> 
> You can put a reference to dna-l2-notifications I-D in here.

ok

>   G10 Hosts with multiple interfaces or in particular wireless
>       environments may perceive routers reachable on different links.
>       DNA schemes should take into consideration the case where a host
>       is attached to more than one link at the same time.
> 
> I think DNA scheme is run per-interface. If so, we shall state that
> somewhere in the document.

Good point. Thanks. I added the following in Introduction.  

   ..........................of its IP configuration, is called Detecting Network
   Attachment (DNA).

   DNA scheme is run per interface because some IP configuration, such
   as IPv6 address, is interface specific.  When a host has multiple
   interfaces, each interface separately check for link change to verify
   each one's IP configuration.
 
The updated draft is available at 

http://www.diffeo.com/drafts/draft-ietf-dna-goals-pre02.txt

Thanks for your kind consideration. 

Best Regards

JinHyeock 


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 03:34:45 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09130
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 03:34:43 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDC3Q6S268X30JW@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 27 Sep 2004 17:32:30 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 53F16AB542; Mon,
 27 Sep 2004 17:32:26 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 09C7D4FB0A; Mon, 27 Sep 2004 17:32:26 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8R7VFP18957	for dna-list; Mon, 27 Sep 2004 17:31:15 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8R7VE618953	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 27 Sep 2004 17:31:14 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDC1WXHYC9UM2LQ@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 27 Sep 2004 17:30:59 +1000
Received: by localhost (Postfix, from userid 510)	id D944DAB543; Mon,
 27 Sep 2004 17:30:58 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id BDA4A4FB0B	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 17:30:56 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id D5E1A220010; Mon,
 27 Sep 2004 10:30:54 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id 574969; Mon,
 27 Sep 2004 10:30:55 +0300 (EEST)
Date: Mon, 27 Sep 2004 10:31:00 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: [DNA] Issue about multiply connected to the same link and DNA being
 per-interface or not (was Re: WG LC comments on draft-ietf-dna-goals-01.txt)
In-reply-to: <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@samsung.com>
Cc: Dna <dna@eng.monash.edu.au>
Message-id: <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
Content-Transfer-Encoding: 7BIT

>>> I see few reason to add "or multiple times to the same link". I think
>>> that's a different case and we may obscure the main issue, 'multiple
>>> attachment', if we add that.
>>
>> Well, I was thinking about the situation where the host is
>> connected through several interfaces to the same link.
>> In some way, this is a special case of a host being connected
>> through several interfaces to several different links.
>>
>> I am not sure how to formulate that properly, but IMHO the whole
>> continuum should be covered by G10.  I don't see it covered
>> by the other goals.
>
> DNA scheme is run per-interface because some IP configuration,
> such as IPv6 address, is interface specific.

Well, I do see there some potentiality for using DNA related
information across different interfaces.  Hence, I would _not_
like to mandate DNA to be per-interface.

For example, if a host has earlier been connected twice to the
same link through two different interfaces, and then it detects
that one of the interfaces has undergone a link change, IMHO that
is a strong indication that there may have been a link change
at the other interface, too.

<snip>

> However, when multiple interfaces of a host are connected to the
> same link, it will result in few problem. Each interface may run DNA
> scheme to check for link change and update its IP configuration in
> case of a link change.

I agree that there shouldn't be that many new *problems* related
to DNA.  However, I think it may be possible to use some DNA
related information for *optimising* behaviour.  We have to
remember that DNA is mostly about optimisation, anyway.

> I think the expression 'multiple interfaces' in G10 is confusing.
> I propose to change G 10 as
>
>    G10 Hosts in particular wireless environments may perceive routers
>       reachable on different links.  DNA schemes should take into
>       consideration the case where a host is attached to more than one
>       link at the same time.

This is better.

> Also, as Alper pointed, we'd better explicitly mention that DNA is
> run per-interface. I added the following in Introduction.
>
>    ..........................of its IP configuration, is called 
> Detecting Network
>    Attachment (DNA).
>
>    DNA scheme is run per interface because some IP configuration, such
>    as IPv6 address, is interface specific.  When a host has multiple
>    interfaces, each interface separately check for link change to 
> verify
>    each one's IP configuration.

As I wrote above, I don't agree with this.  I think this is unnecessary
in the goals document.  I don't think we should include it.
OTOH, if other's in the WG think otherwise, I won't insist.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 06:29:25 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17563
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 06:29:24 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDI9Q6UE09EF3D9@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Mon, 27 Sep 2004 20:29:17 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 899B8AB544; Mon,
 27 Sep 2004 20:29:04 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 3C1394FB11; Mon, 27 Sep 2004 20:29:04 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RASir20549	for dna-list; Mon, 27 Sep 2004 20:28:44 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RASg620545	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 27 Sep 2004 20:28:42 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDI8XDYV29UM30X@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 27 Sep 2004 20:28:26 +1000
Received: by localhost (Postfix, from userid 510)	id DE1ADAB54E; Mon,
 27 Sep 2004 20:28:25 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.199])
	by moe.its.monash.edu.au (Postfix) with ESMTP id B6AA34FB0E	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 20:28:22 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so3212474rnk for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 03:28:21 -0700 (PDT)
Received: by 10.38.2.75 with SMTP id 75mr51523rnb; Mon,
 27 Sep 2004 03:27:18 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Mon, 27 Sep 2004 03:27:18 -0700 (PDT)
Date: Mon, 27 Sep 2004 19:27:18 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>,
        jinchoe@diffeo.com, jinchoe@member.ams.org
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb04092703272ddbb242@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka

We are in a disagreement. 

> > DNA scheme is run per-interface because some IP configuration,
> > such as IPv6 address, is interface specific.
> 
> Well, I do see there some potentiality for using DNA related
> information across different interfaces.  Hence, I would _not_
> like to mandate DNA to be per-interface.
> 
> For example, if a host has earlier been connected twice to the
> same link through two different interfaces, and then it detects
> that one of the interfaces has undergone a link change, IMHO that
> is a strong indication that there may have been a link change
> at the other interface, too.

'mandate' may be a too strong a word but, I think, by default DNA 
will be run per-interface. Each interface should detect the identity 
of its currently attached link for itself. 

This doesn't mean each interface can't share DNA related information
among themselves. 

Even in the above example, the fact that one interface has undergone 
a link change doesn't automatically confirm that the other interface 
also has undergone a link change. As you wrote, though strong, that 
is just a hint, so the other interface needs to run DNA scheme to 
check for link change for itself.   

Moreover, in case a host has multiple interfaces, it's more likely 
each interface is of different link-layer technology. For example, 
a host would have a 802.11 interface and 802.16 interface rather than 
two 802.11 interfaces. In that case, what happened at one interface 
doesn't tell much about the status of the other interface.  

> <snip>
> 
> > However, when multiple interfaces of a host are connected to the
> > same link, it will result in few problem. Each interface may run DNA
> > scheme to check for link change and update its IP configuration in
> > case of a link change.
> 
> I agree that there shouldn't be that many new *problems* related
> to DNA.  However, I think it may be possible to use some DNA
> related information for *optimising* behaviour.  We have to
> remember that DNA is mostly about optimisation, anyway.

I agree that they may be the optimization possibility you pointed. 
However, it's not clear to me how we will reflect that in Goals.   

> > I think the expression 'multiple interfaces' in G10 is confusing.
> > I propose to change G 10 as
> >
> >    G10 Hosts in particular wireless environments may perceive routers
> >       reachable on different links.  DNA schemes should take into
> >       consideration the case where a host is attached to more than one
> >       link at the same time.
> 
> This is better.

ok. 

> > Also, as Alper pointed, we'd better explicitly mention that DNA is
> > run per-interface. I added the following in Introduction.
> >
> >    ..........................of its IP configuration, is called
> > Detecting Network
> >    Attachment (DNA).
> >
> >    DNA scheme is run per interface because some IP configuration, such
> >    as IPv6 address, is interface specific.  When a host has multiple
> >    interfaces, each interface separately check for link change to
> > verify
> >    each one's IP configuration.
> 
> As I wrote above, I don't agree with this.  I think this is unnecessary
> in the goals document.  I don't think we should include it.
> OTOH, if other's in the WG think otherwise, I won't insist.

Let me summarize my thoughts. 

In case there are multiple interfaces in a host, each interface should 
separately detect the identity of the currently attached link for itself. 

Do you disagree with this? If so, we are in a serious disagreement 
and would better find a way to resolve this. 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 06:37:25 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18013
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 06:37:24 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDIJVP28A9UM3A8@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Mon, 27 Sep 2004 20:37:24 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 5B7E2AB54E; Mon,
 27 Sep 2004 20:37:15 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id CF5FB4FB11; Mon,
 27 Sep 2004 20:37:14 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RAb9j20648	for dna-list; Mon, 27 Sep 2004 20:37:09 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RAb8620644	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 27 Sep 2004 20:37:08 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDIJLESE28ZE45H@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Mon,
 27 Sep 2004 20:37:02 +1000
Received: by localhost (Postfix, from userid 510)	id BC158AB542; Mon,
 27 Sep 2004 20:37:01 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 1FF5C4FB06	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 20:37:00 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id 576E9220008; Mon,
 27 Sep 2004 13:36:53 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id C52919; Mon,
 27 Sep 2004 13:36:53 +0300 (EEST)
Date: Mon, 27 Sep 2004 13:36:58 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <92e919fb04092703272ddbb242@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@gmail.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>,
        jinchoe@diffeo.com, jinchoe@member.ams.org
Message-id: <2908743E-1071-11D9-9F77-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb04092703272ddbb242@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

> We are in a disagreement.

Somewhat, yes.  But I don't think the disagreement is that bad.  :-)

<snip>

>>>    DNA scheme is run per interface because some IP configuration, 
>>> such
>>>    as IPv6 address, is interface specific.  When a host has multiple
>>>    interfaces, each interface separately check for link change to
>>> verify
>>>    each one's IP configuration.
>>
>> As I wrote above, I don't agree with this.  I think this is 
>> unnecessary
>> in the goals document.  I don't think we should include it.
>> OTOH, if other's in the WG think otherwise, I won't insist.
>
> Let me summarize my thoughts.
>
> In case there are multiple interfaces in a host, each interface should
> separately detect the identity of the currently attached link for 
> itself.
>
> Do you disagree with this? If so, we are in a serious disagreement
> and would better find a way to resolve this.

Well, I don't really disagree with you at that point.  However,
IMHO we would needlessly limit ourselves if we, in the goals
document, state that DNA schemes are (always) run per interface.
I would easily agree that they are "typically" or even "almost
always" run per interface.  However, there are cases where that
may not hold.  Hence my concern.

But I'd like to hear other opinions on this.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 07:25:38 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20665
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 07:25:37 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDK7NHVQ89EEKIM@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Mon, 27 Sep 2004 21:24:50 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 23D0980006; Mon,
 27 Sep 2004 21:24:40 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id CE48C3C007; Mon, 27 Sep 2004 21:24:39 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RBOSR21107	for dna-list; Mon, 27 Sep 2004 21:24:28 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RBOR621103	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 27 Sep 2004 21:24:27 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDK71M6JU9UM3DV@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 27 Sep 2004 21:24:11 +1000
Received: by localhost (Postfix, from userid 510)	id D9ADAAB542; Mon,
 27 Sep 2004 21:24:10 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.202])
	by curly.its.monash.edu.au (Postfix) with ESMTP id BAAEF4FB09	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 21:24:08 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so3771959rnl for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 04:24:07 -0700 (PDT)
Received: by 10.38.208.47 with SMTP id f47mr90228rng; Mon,
 27 Sep 2004 04:24:07 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Mon, 27 Sep 2004 04:24:07 -0700 (PDT)
Date: Mon, 27 Sep 2004 20:24:07 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <2908743E-1071-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>,
        jinchoe@diffeo.com, jinchoe@member.ams.org
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb04092704245c9d383a@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb04092703272ddbb242@mail.gmail.com>
 <2908743E-1071-11D9-9F77-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka

> > We are in a disagreement.
> 
> Somewhat, yes.  But I don't think the disagreement is that bad.  :-)

Glad and relieved to hear that. :-)
 
> <snip>
> 
> >>>    DNA scheme is run per interface because some IP configuration,
> >>> such
> >>>    as IPv6 address, is interface specific.  When a host has multiple
> >>>    interfaces, each interface separately check for link change to
> >>> verify
> >>>    each one's IP configuration.
> >>
> >> As I wrote above, I don't agree with this.  I think this is
> >> unnecessary
> >> in the goals document.  I don't think we should include it.
> >> OTOH, if other's in the WG think otherwise, I won't insist.
> >
> > Let me summarize my thoughts.
> >
> > In case there are multiple interfaces in a host, each interface should
> > separately detect the identity of the currently attached link for
> > itself.
> >
> > Do you disagree with this? If so, we are in a serious disagreement
> > and would better find a way to resolve this.
> 
> Well, I don't really disagree with you at that point.  However,
> IMHO we would needlessly limit ourselves if we, in the goals
> document, state that DNA schemes are (always) run per interface.
> I would easily agree that they are "typically" or even "almost
> always" run per interface.  However, there are cases where that
> may not hold.  Hence my concern.

I see your point. Kindly tell me your suggestion how we will 
resove this. Would you like us to remove the paragraphs?  
I can live with it but Alper may have a different opinion. If so, 
I will try to rephrase the parts to be acceptable to both of you.
 
> But I'd like to hear other opinions on this.
 
Me too. 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 07:37:14 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21293
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 07:37:12 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDKM5Z2NS8ZE5K5@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Mon, 27 Sep 2004 21:36:26 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 2DA1AAB545; Mon,
 27 Sep 2004 21:36:22 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id D9D854FB07; Mon, 27 Sep 2004 21:36:21 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RBa0P21233	for dna-list; Mon, 27 Sep 2004 21:36:00 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RBZv621229	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 27 Sep 2004 21:35:58 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDKLBEFDS8ZE4RQ@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Mon,
 27 Sep 2004 21:35:41 +1000
Received: by localhost (Postfix, from userid 510)	id E2001AB545; Mon,
 27 Sep 2004 21:35:40 +1000 (EST)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by curly.its.monash.edu.au (Postfix) with ESMTP id DAEAC4FB09	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 21:35:38 +1000 (EST)
Received: (from root@localhost)	by darkstar.iprg.nokia.com
 (8.11.0/8.11.0-DARKSTAR) id i8RB8B117674; Mon, 27 Sep 2004 04:08:11 -0700
Received: from trdhcp164175.nmp.nokia.com
 (172.22.164.175, claiming to be "[172.22.164.175]")	by darkstar.iprg.nokia.com
 smtpdn4agU3; Mon, 27 Sep 2004 04:08:09 -0700 (PDT)
Date: Mon, 27 Sep 2004 04:34:59 -0700
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <2908743E-1071-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: JinHyeock Choi <jinchoe@gmail.com>, JinHyeock Choi <jinchoe@samsung.com>,
        Dna <dna@eng.monash.edu.au>, jinchoe@diffeo.com,
        jinchoe@member.ams.org
Message-id: <4157FAE3.9070901@iprg.nokia.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
Precedence: bulk
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2)
 Gecko/20040804 Netscape/7.2 (ax)
X-mProtect: <200409271108> Nokia Silicon Valley Messaging Protection
X-Accept-Language: en-us, en
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

IMO, DNA needs to be per interface. and ofcourse information could
be shared between interfaces.

Vijay

Pekka Nikander wrote:
>> We are in a disagreement.
> 
> 
> Somewhat, yes.  But I don't think the disagreement is that bad.  :-)
> 
> <snip>
> 
>>>>    DNA scheme is run per interface because some IP configuration, such
>>>>    as IPv6 address, is interface specific.  When a host has multiple
>>>>    interfaces, each interface separately check for link change to
>>>> verify
>>>>    each one's IP configuration.
>>>
>>>
>>> As I wrote above, I don't agree with this.  I think this is unnecessary
>>> in the goals document.  I don't think we should include it.
>>> OTOH, if other's in the WG think otherwise, I won't insist.
>>
>>
>> Let me summarize my thoughts.
>>
>> In case there are multiple interfaces in a host, each interface should
>> separately detect the identity of the currently attached link for itself.
>>
>> Do you disagree with this? If so, we are in a serious disagreement
>> and would better find a way to resolve this.
> 
> 
> Well, I don't really disagree with you at that point.  However,
> IMHO we would needlessly limit ourselves if we, in the goals
> document, state that DNA schemes are (always) run per interface.
> I would easily agree that they are "typically" or even "almost
> always" run per interface.  However, there are cases where that
> may not hold.  Hence my concern.
> 
> But I'd like to hear other opinions on this.
> 
> --Pekka
> 



From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 09:01:48 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26799
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 09:01:47 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDNKDXG6K9UM3JZ@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Mon, 27 Sep 2004 23:01:22 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 967BBAB544; Mon,
 27 Sep 2004 23:01:13 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 3FA574FB05; Mon, 27 Sep 2004 23:01:13 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RD0jX22013	for dna-list; Mon, 27 Sep 2004 23:00:45 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RD0i622009	for
 <dna@ecselists.eng.monash.edu.au>; Mon, 27 Sep 2004 23:00:44 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDNJQDR6K9UM3JZ@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Mon,
 27 Sep 2004 23:00:42 +1000
Received: by localhost (Postfix, from userid 510)	id 03382AB54D; Mon,
 27 Sep 2004 23:00:41 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 527114FB15	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 23:00:40 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id 731E5220007; Mon,
 27 Sep 2004 16:00:38 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id E13A69; Mon,
 27 Sep 2004 16:00:38 +0300 (EEST)
Date: Mon, 27 Sep 2004 16:00:43 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <92e919fb04092704245c9d383a@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@gmail.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>,
        jinchoe@diffeo.com, jinchoe@member.ams.org
Message-id: <3D62D444-1085-11D9-9F77-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb04092703272ddbb242@mail.gmail.com>
 <2908743E-1071-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb04092704245c9d383a@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

>>>>>    DNA scheme is run per interface because some IP configuration,
>>>>> such
>>>>>    as IPv6 address, is interface specific.  When a host has 
>>>>> multiple
>>>>>    interfaces, each interface separately check for link change to
>>>>> verify
>>>>>    each one's IP configuration.

> I see your point. Kindly tell me your suggestion how we will
> resove this. Would you like us to remove the paragraphs?
> I can live with it but Alper may have a different opinion. If so,
> I will try to rephrase the parts to be acceptable to both of you.

To me it is OK enough if we add the word "typically", and simplify
the paragraph somewhat.

    DNA schemes are typically run per interface.  When a host has
    multiple interfaces, the host separately checks for link changes
    on each interface.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 12:45:12 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11806
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 12:45:11 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDVCT11BI8X347F@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 02:44:18 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 6D03680002; Tue,
 28 Sep 2004 02:44:09 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 133CE3C008; Tue, 28 Sep 2004 02:44:09 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RGhUv24086	for dna-list; Tue, 28 Sep 2004 02:43:30 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RGhR624082	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 02:43:27 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFDVBQQDYG9UM4AU@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 28 Sep 2004 02:43:19 +1000
Received: by localhost (Postfix, from userid 510)	id 6E3A5AB54C; Tue,
 28 Sep 2004 02:43:19 +1000 (EST)
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 5E8A64FB08	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 02:43:17 +1000 (EST)
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id i8RGhEil019294; Mon,
 27 Sep 2004 10:43:15 -0600 (MDT)
Received: from [129.146.89.81] (bobo.SFBay.Sun.COM [129.146.89.81])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2)
 with ESMTP id i8RGhCJQ011968; Mon, 27 Sep 2004 18:43:13 +0200 (MEST)
Date: Mon, 27 Sep 2004 09:43:51 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Message-id: <41584347.4010200@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Precedence: bulk
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Accept-Language: en-us, en
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka Nikander wrote:

> For example, if a host has earlier been connected twice to the
> same link through two different interfaces, and then it detects
> that one of the interfaces has undergone a link change, IMHO that
> is a strong indication that there may have been a link change
> at the other interface, too.

Pekka,
do you have a concrete example where this makes sense?

I don't have a problem relaxing the wording in the goals draft to not 
accidentically preclude optimizations which share information between 
interfaces, but I don't understand your example above.

   Erik


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 13:50:31 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16350
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 13:50:30 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDXL88PDU8ZE5RS@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 03:48:20 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 21175AB543; Tue,
 28 Sep 2004 03:48:14 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id CAD624FB0C; Tue, 28 Sep 2004 03:48:13 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RHlkB24688	for dna-list; Tue, 28 Sep 2004 03:47:46 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RHlj624684	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 03:47:45 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFDXKLTRDW8ZE56F@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Tue,
 28 Sep 2004 03:47:44 +1000
Received: by localhost (Postfix, from userid 510)	id 2DCDC80002; Tue,
 28 Sep 2004 03:47:44 +1000 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 72EEE3C003	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 03:47:42 +1000 (EST)
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I4P00701O3F6S@mailout2.samsung.com> for dna@eng.monash.edu.au; Tue,
 28 Sep 2004 02:47:39 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I4P00AIQO3EAG@mailout2.samsung.com> for dna@eng.monash.edu.au;
 Tue, 28 Sep 2004 02:47:39 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I4P00D82O3CEC@mmp2.samsung.com> for
 dna@eng.monash.edu.au; Tue, 28 Sep 2004 02:47:38 +0900 (KST)
Date: Mon, 27 Sep 2004 10:47:36 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "'JinHyeock Choi'" <jinchoe@samsung.com>, "'Dna'" <dna@eng.monash.edu.au>
Message-id: <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
Content-Transfer-Encoding: 7BIT

Hi JinHyeock,


>    To examine the status of the existing configuration, a host may
check
>    whether a 'link change' has occurred.  The term 'link' used in this
>    document is as defined in RFC 2461 [4].  The notion 'link' is not
>    identical with the notion 'subnet' as defined in RFC 3753 [7].  For
>    example, there may be more than one subnets in a link.

Also "A host connected to a link may be part of one or more of the
subnets on the link."

> More detailed comparison, I think, would be better done in terminology
> draft. It's my understanding that terminology related issues, such as
> Jason
> issue, will be treated there.

I'd agree. But where is that I-D, I heard about it but haven't seen it. 

> > There should be an explicit statement about this work being limited
to
> > IPv6, together with a reference to IPv4 work (DNAv4).
> 
> ok.
> 
> I explicitly mentioned 'IPv6 Only' as Pekka's suggested. At the end of
> Introduction, I added
> 
>    This draft considered the DNA procedure only from IPv6 point of
view,
>    unless otherwise explicitly mentioned.  Hence, the term "IP" is to
be
>    understood to denote IPv6 by default.  For IPv4 case, refer [15].
> 
> >    Unlike wired environments, what constitutes wireless link is
variable
> >    in both time and space.  It doesn't have clear boundaries.  This
may
> >    be illustrated by the fact that a host may contact multiple
(802.11)
> >    access points at the same time.
> >
> > We better clarify what "contact" means. Is it being able to hear the
> > APs, or establish a link-layer connection with the APs, or something
> > else?
> 
> Precisely speaking,
> 
> a host may be under the wireless coverage of more than one APs.
> 
> Definitely, not multiple link-layer connections because that's not
allowed
> in 802.11 standard. I intentionally used the word 'contact' instead of
> 'connect with'.

Bernard mentioned that one STA connecting to multiple APs simultaneously
is not prohibited by the spec, and it is feasible. I recommend you
replace "contact" with "be within the coverage are of". This reflects
your intention, and uses common terms. 

> 
> >    Hints come in various forms, and differ in how they indicate a
> >    possible link change.  They can be link-layer event
notifications,
> >
> > You can put a reference to dna-l2-notifications I-D in here.
> 
> ok
> 
> >   G10 Hosts with multiple interfaces or in particular wireless
> >       environments may perceive routers reachable on different
links.
> >       DNA schemes should take into consideration the case where a
host
> >       is attached to more than one link at the same time.
> >
> > I think DNA scheme is run per-interface. If so, we shall state that
> > somewhere in the document.
> 
> Good point. Thanks. I added the following in Introduction.
> 
>    ..........................of its IP configuration, is called
Detecting
> Network
>    Attachment (DNA).
> 
>    DNA scheme is run per interface because some IP configuration, such
>    as IPv6 address, is interface specific.  When a host has multiple
>    interfaces, each interface separately check for link change to
verify
>    each one's IP configuration.
> 
> The updated draft is available at
> 
> http://www.diffeo.com/drafts/draft-ietf-dna-goals-pre02.txt

Thank you.

Alper




From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 19:05:44 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18508
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 19:05:42 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFE8NJ3L3S8X35QJ@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 09:04:53 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 2B6C7AB558; Tue,
 28 Sep 2004 09:04:38 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id E0D884FB03; Tue,
 28 Sep 2004 09:04:37 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RN1pu27705	for dna-list; Tue, 28 Sep 2004 09:01:51 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RN1n627701	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 09:01:49 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFE8JQ5KFG9EF9S5@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 28 Sep 2004 09:01:36 +1000
Received: by localhost (Postfix, from userid 510)	id E42BB80004; Tue,
 28 Sep 2004 09:01:35 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.198])
	by larry.its.monash.edu.au (Postfix) with ESMTP id B43E93C003	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 09:01:34 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so5514rnk for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 16:01:33 -0700 (PDT)
Received: by 10.38.208.53 with SMTP id f53mr466035rng; Mon,
 27 Sep 2004 16:01:26 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Mon, 27 Sep 2004 16:00:46 -0700 (PDT)
Date: Tue, 28 Sep 2004 08:00:46 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@samsung.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb040927160068a7f20b@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
 <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
Content-Transfer-Encoding: 7BIT

Alper

> >    To examine the status of the existing configuration, a host may
> check
> >    whether a 'link change' has occurred.  The term 'link' used in this
> >    document is as defined in RFC 2461 [4].  The notion 'link' is not
> >    identical with the notion 'subnet' as defined in RFC 3753 [7].  For
> >    example, there may be more than one subnets in a link.
> 
> Also "A host connected to a link may be part of one or more of the
> subnets on the link."

ok. Then the sentence will be

   ................................................................The
term 'link' used in this
   document is as defined in RFC 2461 [4].  The notion 'link' is not
   identical with the notion 'subnet' as defined in RFC 3753 [7].  For
   example, there may be more than one subnets in a link and a 
   host connected to a link may be part of one or more of the subnets 
   on the link.

> > More detailed comparison, I think, would be better done in terminology
> > draft. It's my understanding that terminology related issues, such as
> > Jason
> > issue, will be treated there.
> 
> I'd agree. But where is that I-D, I heard about it but haven't seen it.

I saw it. It exists. :-) 
 
> > > There should be an explicit statement about this work being limited
> to
> > > IPv6, together with a reference to IPv4 work (DNAv4).
> >
> > ok.
> >
> > I explicitly mentioned 'IPv6 Only' as Pekka's suggested. At the end of
> > Introduction, I added
> >
> >    This draft considered the DNA procedure only from IPv6 point of
> view,
> >    unless otherwise explicitly mentioned.  Hence, the term "IP" is to
> be
> >    understood to denote IPv6 by default.  For IPv4 case, refer [15].
> >
> > >    Unlike wired environments, what constitutes wireless link is
> variable
> > >    in both time and space.  It doesn't have clear boundaries.  This
> may
> > >    be illustrated by the fact that a host may contact multiple
> (802.11)
> > >    access points at the same time.
> > >
> > > We better clarify what "contact" means. Is it being able to hear the
> > > APs, or establish a link-layer connection with the APs, or something
> > > else?
> >
> > Precisely speaking,
> >
> > a host may be under the wireless coverage of more than one APs.
> >
> > Definitely, not multiple link-layer connections because that's not
> allowed
> > in 802.11 standard. I intentionally used the word 'contact' instead of
> > 'connect with'.
> 
> Bernard mentioned that one STA connecting to multiple APs simultaneously
> is not prohibited by the spec, and it is feasible. I recommend you
> replace "contact" with "be within the coverage are of". This reflects
> your intention, and uses common terms.

ok. The sentence will be 

        ...... a host may be with in the coverage area of multiple
        (802.11) access points at the same time.

> >    DNA scheme is run per interface because some IP configuration, such
> >    as IPv6 address, is interface specific.  When a host has multiple
> >    interfaces, each interface separately check for link change to
> >    verify each one's IP configuration.

Pekka is not entirely happy to add the above paragraphs. We exchanged
thoughts and kindly give your opinion on it.  

Thanks for your kind consideration. 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 19:05:46 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18524
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 19:05:44 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFE8NSHP288ZE5XU@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 09:04:58 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 7C08DAB553; Tue,
 28 Sep 2004 09:04:52 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 38C804FB03; Tue,
 28 Sep 2004 09:04:52 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RN29327724	for dna-list; Tue, 28 Sep 2004 09:02:09 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RN28627720	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 09:02:08 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFE8KDMWQO9EF9S5@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 28 Sep 2004 09:02:07 +1000
Received: by localhost (Postfix, from userid 510)	id 98ED5AB54E; Tue,
 28 Sep 2004 09:02:07 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.207])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 77D5A4FB03	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 09:02:05 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so3888053rnl for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 16:02:04 -0700 (PDT)
Received: by 10.38.88.53 with SMTP id l53mr213055rnb; Mon,
 27 Sep 2004 16:02:04 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Mon, 27 Sep 2004 16:02:04 -0700 (PDT)
Date: Tue, 28 Sep 2004 08:02:04 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <92e919fb040927160068a7f20b@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@samsung.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb04092716021386c050@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
 <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
 <92e919fb040927160068a7f20b@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

Alper

> >    To examine the status of the existing configuration, a host may
> check
> >    whether a 'link change' has occurred.  The term 'link' used in this
> >    document is as defined in RFC 2461 [4].  The notion 'link' is not
> >    identical with the notion 'subnet' as defined in RFC 3753 [7].  For
> >    example, there may be more than one subnets in a link.
> 
> Also "A host connected to a link may be part of one or more of the
> subnets on the link."

ok. Then the sentence will be

   ................................................................The
term 'link' used in this
   document is as defined in RFC 2461 [4].  The notion 'link' is not
   identical with the notion 'subnet' as defined in RFC 3753 [7].  For
   example, there may be more than one subnets in a link and a 
   host connected to a link may be part of one or more of the subnets 
   on the link.

> > More detailed comparison, I think, would be better done in terminology
> > draft. It's my understanding that terminology related issues, such as
> > Jason
> > issue, will be treated there.
> 
> I'd agree. But where is that I-D, I heard about it but haven't seen it.

I saw it. It exists. :-) 
 
> > > There should be an explicit statement about this work being limited
> to
> > > IPv6, together with a reference to IPv4 work (DNAv4).
> >
> > ok.
> >
> > I explicitly mentioned 'IPv6 Only' as Pekka's suggested. At the end of
> > Introduction, I added
> >
> >    This draft considered the DNA procedure only from IPv6 point of
> view,
> >    unless otherwise explicitly mentioned.  Hence, the term "IP" is to
> be
> >    understood to denote IPv6 by default.  For IPv4 case, refer [15].
> >
> > >    Unlike wired environments, what constitutes wireless link is
> variable
> > >    in both time and space.  It doesn't have clear boundaries.  This
> may
> > >    be illustrated by the fact that a host may contact multiple
> (802.11)
> > >    access points at the same time.
> > >
> > > We better clarify what "contact" means. Is it being able to hear the
> > > APs, or establish a link-layer connection with the APs, or something
> > > else?
> >
> > Precisely speaking,
> >
> > a host may be under the wireless coverage of more than one APs.
> >
> > Definitely, not multiple link-layer connections because that's not
> allowed
> > in 802.11 standard. I intentionally used the word 'contact' instead of
> > 'connect with'.
> 
> Bernard mentioned that one STA connecting to multiple APs simultaneously
> is not prohibited by the spec, and it is feasible. I recommend you
> replace "contact" with "be within the coverage are of". This reflects
> your intention, and uses common terms.

ok. The sentence will be 

        ...... a host may be with in the coverage area of multiple
        (802.11) access points at the same time.

> >    DNA scheme is run per interface because some IP configuration, such
> >    as IPv6 address, is interface specific.  When a host has multiple
> >    interfaces, each interface separately check for link change to
> >    verify each one's IP configuration.

Pekka is not entirely happy to add the above paragraphs. We exchanged
thoughts and kindly give your opinion on it.  

Thanks for your kind consideration. 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 19:08:27 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18756
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 19:08:26 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFE8NMM11C9UM5NQ@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Tue, 28 Sep 2004 09:05:00 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 67B5080007; Tue,
 28 Sep 2004 09:04:44 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 1D2BF3C006; Tue, 28 Sep 2004 09:04:44 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8RN1rw27712	for dna-list; Tue, 28 Sep 2004 09:01:53 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8RN1q627708	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 09:01:52 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFE8K0BQYS8X3H7P@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Tue,
 28 Sep 2004 09:01:50 +1000
Received: by localhost (Postfix, from userid 510)	id AF2DA80002; Tue,
 28 Sep 2004 09:01:49 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.198])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 907FB3C005	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 09:01:48 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so5545rnk for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 16:01:47 -0700 (PDT)
Received: by 10.38.208.53 with SMTP id f53mr466304rng; Mon,
 27 Sep 2004 16:01:46 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Mon, 27 Sep 2004 16:00:46 -0700 (PDT)
Date: Tue, 28 Sep 2004 08:00:46 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@samsung.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb040927160068a7f20b@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
 <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
Content-Transfer-Encoding: 7BIT

Alper

> >    To examine the status of the existing configuration, a host may
> check
> >    whether a 'link change' has occurred.  The term 'link' used in this
> >    document is as defined in RFC 2461 [4].  The notion 'link' is not
> >    identical with the notion 'subnet' as defined in RFC 3753 [7].  For
> >    example, there may be more than one subnets in a link.
> 
> Also "A host connected to a link may be part of one or more of the
> subnets on the link."

ok. Then the sentence will be

   ................................................................The
term 'link' used in this
   document is as defined in RFC 2461 [4].  The notion 'link' is not
   identical with the notion 'subnet' as defined in RFC 3753 [7].  For
   example, there may be more than one subnets in a link and a 
   host connected to a link may be part of one or more of the subnets 
   on the link.

> > More detailed comparison, I think, would be better done in terminology
> > draft. It's my understanding that terminology related issues, such as
> > Jason
> > issue, will be treated there.
> 
> I'd agree. But where is that I-D, I heard about it but haven't seen it.

I saw it. It exists. :-) 
 
> > > There should be an explicit statement about this work being limited
> to
> > > IPv6, together with a reference to IPv4 work (DNAv4).
> >
> > ok.
> >
> > I explicitly mentioned 'IPv6 Only' as Pekka's suggested. At the end of
> > Introduction, I added
> >
> >    This draft considered the DNA procedure only from IPv6 point of
> view,
> >    unless otherwise explicitly mentioned.  Hence, the term "IP" is to
> be
> >    understood to denote IPv6 by default.  For IPv4 case, refer [15].
> >
> > >    Unlike wired environments, what constitutes wireless link is
> variable
> > >    in both time and space.  It doesn't have clear boundaries.  This
> may
> > >    be illustrated by the fact that a host may contact multiple
> (802.11)
> > >    access points at the same time.
> > >
> > > We better clarify what "contact" means. Is it being able to hear the
> > > APs, or establish a link-layer connection with the APs, or something
> > > else?
> >
> > Precisely speaking,
> >
> > a host may be under the wireless coverage of more than one APs.
> >
> > Definitely, not multiple link-layer connections because that's not
> allowed
> > in 802.11 standard. I intentionally used the word 'contact' instead of
> > 'connect with'.
> 
> Bernard mentioned that one STA connecting to multiple APs simultaneously
> is not prohibited by the spec, and it is feasible. I recommend you
> replace "contact" with "be within the coverage are of". This reflects
> your intention, and uses common terms.

ok. The sentence will be 

        ...... a host may be with in the coverage area of multiple
        (802.11) access points at the same time.

> >    DNA scheme is run per interface because some IP configuration, such
> >    as IPv6 address, is interface specific.  When a host has multiple
> >    interfaces, each interface separately check for link change to
> >    verify each one's IP configuration.

Pekka is not entirely happy to add the above paragraphs. We exchanged
thoughts and kindly give your opinion on it.  

Thanks for your kind consideration. 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Mon Sep 27 23:38:59 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06284
	for <dna-archive@lists.ietf.org>; Mon, 27 Sep 2004 23:38:58 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFEI1UQ6O68ZE646@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 13:33:36 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 3E6A1AB552; Tue,
 28 Sep 2004 13:33:31 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id D89A54FB0A; Tue,
 28 Sep 2004 13:33:30 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8S3X2M30538	for dna-list; Tue, 28 Sep 2004 13:33:02 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8S3X1630532	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 13:33:01 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFEI12VF0O9EFC6A@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 28 Sep 2004 13:32:54 +1000
Received: by localhost (Postfix, from userid 510)	id D877D80002; Tue,
 28 Sep 2004 13:32:53 +1000 (EST)
Received: from salary.cs.uiuc.edu (salary.cs.uiuc.edu [128.174.252.217])
	by larry.its.monash.edu.au (Postfix) with ESMTP id E63CE3C009	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 13:32:51 +1000 (EST)
Received: from salad.cs.uiuc.edu (salad.cs.uiuc.edu [128.174.252.214])
	by salary.cs.uiuc.edu (8.12.10/8.12.10) with ESMTP id i8S3WoDM025963	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 22:32:50 -0500 (CDT)
Received: from localhost (kaichen@localhost)
	by salad.cs.uiuc.edu (8.9.3p3/8.9.3) with ESMTP id WAA05312	for
 <dna@eng.monash.edu.au>; Mon, 27 Sep 2004 22:32:50 -0500 (CDT)
Date: Mon, 27 Sep 2004 22:32:49 -0500 (CDT)
From: Kai Chen <kaichen@cs.uiuc.edu>
Subject: [DNA] persistent TCP connection under 802.11 outage
Sender: owner-dna@ecselists.eng.monash.edu.au
To: dna@eng.monash.edu.au
Message-id: <Pine.GSO.4.58.0409272220130.5301@salad.cs.uiuc.edu>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
Content-Transfer-Encoding: 7BIT


Dear DNA members:

Sorry if this question has been asked before. I am trying to keep a TCP
connection persistent (e.g. SSH, FTP) over a 802.11 AP even after the
wireless link experiences temparary outage.

Currently the scenario goes like this:
1) 802.11 NIC detects loss of link;
2) OS tears down the interface and clears all the exisiting TCP states;
3) when the link is back, AP's DHCP likely gives the host the same IP;
4) however, the old TCP connections cannot continue due to lack of
socket states in the kernel.

Does anyone know how to solve (or approach) this problem under both
Windows XP and Linux? If the NIC's device driver can shield the link
outage from the upper layer, this problem should go away, correct?

Any pointers are greatly appreciated. Thanks very much in advance.

--
Kai Chen
Computer Science Department
Univ. of Illinois at Urbana-Champaign
Urbana, IL 61801, U.S.A.






From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 05:24:58 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08324
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 05:24:57 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFEUB5Q0S89UM84X@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Tue, 28 Sep 2004 19:24:47 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 1E089AB54C; Tue,
 28 Sep 2004 19:24:37 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id C9F874FB0A; Tue,
 28 Sep 2004 19:24:36 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8S9Nnq01792	for dna-list; Tue, 28 Sep 2004 19:23:49 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8S9Nm601781	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 19:23:48 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFEUA1PVGI8X0SFA@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Tue,
 28 Sep 2004 19:23:46 +1000
Received: by localhost (Postfix, from userid 510)	id 2D14FAB543; Tue,
 28 Sep 2004 19:23:43 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 264E84FB0B	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 19:23:41 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id B58E3220006; Tue,
 28 Sep 2004 12:23:38 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id 3D62F9; Tue,
 28 Sep 2004 12:23:39 +0300 (EEST)
Date: Tue, 28 Sep 2004 12:23:44 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <41584347.4010200@sun.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Erik Nordmark <erik.nordmark@sun.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Message-id: <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <41584347.4010200@sun.com>
Content-Transfer-Encoding: 7BIT

Erik

>> For example, if a host has earlier been connected twice to the
>> same link through two different interfaces, and then it detects
>> that one of the interfaces has undergone a link change, IMHO that
>> is a strong indication that there may have been a link change
>> at the other interface, too.
>
> do you have a concrete example where this makes sense?

The specific example, though simplistic, that I've had in my mind
is my home setting with my laptop.  I have a bridged Ethernet and
WLAN.  When my laptop notices that I've disconnected it from the
Ethernet, I may have just moving it around in our house, and it
is still connected to the same link through WLAN.  On the other
hand, I may have suspended it and moved it e.g. to the office,
in which case it is now attached to a different WLAN.

Another example that I could imagine is a large operator network
that from an IPv6 point of view acts as a single, large "LAN"
or NBMA link.  (I know one operator that has plans like that.)
The operator might offer different radio access technologies to
access that "large LAN".  When one radio interface undergoes a
change, it may make sense to quickly verify whether the other
interfaces still are connected to the "large LAN".

In general, if two interfaces are connected to the same subnet,
and one of the undergoes a link change, it often makes sense to
check if the other one has also went through a link change.

> I don't have a problem relaxing the wording in the goals draft
> to not accidentically preclude optimizations which share
> information between interfaces, but I don't understand your
> example above.

I was mostly objecting the notion that we should keep DNA on
separate interfaces _completely_ independent.  To me, it looks
like that there are cases when they are not.  I am oblivious
how to handle this, through link hints, relaxing the language
in the goals draft, or whatever.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 05:29:04 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08422
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 05:29:03 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFEUETVS2Y8X0SFA@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 19:27:51 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id B4ADBAB543; Tue,
 28 Sep 2004 19:27:34 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 6AC1F4FB14; Tue, 28 Sep 2004 19:27:34 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8S9RVZ01888	for dna-list; Tue, 28 Sep 2004 19:27:31 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8S9RU601881	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 19:27:30 +1000
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFEUEER3AI9UM84Z@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 28 Sep 2004 19:27:14 +1000
Received: by localhost (Postfix, from userid 510)	id 88FEEAB54D; Tue,
 28 Sep 2004 19:27:14 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 789224FB0E	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 19:27:13 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id 8F055220003; Tue,
 28 Sep 2004 12:27:11 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id 166B49; Tue,
 28 Sep 2004 12:27:12 +0300 (EEST)
Date: Tue, 28 Sep 2004 12:27:16 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <92e919fb040927160068a7f20b@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@gmail.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>,
        Alper Yegin <alper.yegin@samsung.com>, Dna <dna@eng.monash.edu.au>
Message-id: <96A953E8-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
 <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
 <92e919fb040927160068a7f20b@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

>>>    To examine the status of the existing configuration, a host may
>>>    check
>>>    whether a 'link change' has occurred.  The term 'link' used in 
>>> this
>>>    document is as defined in RFC 2461 [4].  The notion 'link' is not
>>>    identical with the notion 'subnet' as defined in RFC 3753 [7].  
>>> For
>>>    example, there may be more than one subnets in a link.
>>
>> Also "A host connected to a link may be part of one or more of the
>> subnets on the link."
>
> ok. Then the sentence will be
>
>    ................................................................The
>    term 'link' used in this
>    document is as defined in RFC 2461 [4].  The notion 'link' is not
>    identical with the notion 'subnet' as defined in RFC 3753 [7].  For
>    example, there may be more than one subnets in a link and a
>    host connected to a link may be part of one or more of the subnets
>    on the link.

Looks good to me.

>> Bernard mentioned that one STA connecting to multiple APs 
>> simultaneously
>> is not prohibited by the spec, and it is feasible. I recommend you
>> replace "contact" with "be within the coverage are of". This reflects
>> your intention, and uses common terms.
>
> ok. The sentence will be
>
>         ...... a host may be with in the coverage area of multiple
>         (802.11) access points at the same time.

Looks good to me other than do we need to mention 802.11 here?
If it is true for 802.11, it may be true for other wireless
technologies, too.

>>>    DNA scheme is run per interface because some IP configuration, 
>>> such
>>>    as IPv6 address, is interface specific.  When a host has multiple
>>>    interfaces, each interface separately check for link change to
>>>    verify each one's IP configuration.
>
> Pekka is not entirely happy to add the above paragraphs. We exchanged
> thoughts and kindly give your opinion on it.

Right.  But that discussion now has its own thread.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 06:49:08 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12313
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 06:49:07 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFEX8IH2WA9EFEH4@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Tue, 28 Sep 2004 20:48:55 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 837C580003; Tue,
 28 Sep 2004 20:48:46 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id E6C773C00B; Tue, 28 Sep 2004 20:48:45 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8SAmOs02805	for dna-list; Tue, 28 Sep 2004 20:48:24 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8SAmN602801	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 20:48:23 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFEX7Z04P88X3EF8@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Tue,
 28 Sep 2004 20:48:21 +1000
Received: by localhost (Postfix, from userid 510)	id 669BCAB543; Tue,
 28 Sep 2004 20:48:20 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id BB2E04FB08	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 20:48:18 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP id BA8FD220003	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 13:48:14 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix)
 with ESMTP id 4209D9	for <dna@eng.monash.edu.au>; Tue,
 28 Sep 2004 13:48:15 +0300 (EEST)
Date: Tue, 28 Sep 2004 13:48:20 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: [DNA] Preparing Washington D.C. agenda
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Dna <dna@eng.monash.edu.au>
Message-id: <E9B3CAB4-113B-11D9-9F77-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT

Folks,

[According to Greg, he is quite busy right now, and therefore
we have decided that I'll take care of the meeting agenda
this time.]

I am starting to prepare agenda for the D.C. meeting.  As we
have made good progress with the goals draft, it looks like
that the time is ripe for starting work on the new solution(s).
Hence, I am soliciting for revised and new drafts in the
solutions space so that we get discussion going.  If needed,
we can then form a design team later on.

As usual, any drafts to be discussed at the face-to-face meeting
should have been announced at the ML well before the meeting,
and have clear interest among the WG participants.  If you are
an author of such a draft, and would like to discuss it, please
send me a note, giving

  - name of the draft
  - tentative list of open issues to be discussed
  - amount of time requested

My current plan is to request a two hour slot, provided that
we have concrete enough proposals so that we can have
productive face-to-face discussions.

The important dates are as follows:
  Oct 18 - Internet Draft Cut-off for initial documents (-00)
  Oct 25 - Working Group and BOF scheduling closes
  Oct 25 - Internet Draft final submission cut-off

So far, I have made tentative plans as follows, on the assumption
that the BCP would be mature enough.  If it will turn up to be
not mature enough, we can allocate more time for solutions work.
And, of course, if there appears any controversies on the link
information draft, we can shift some more attention to it, too.

   5 min     Introduction & Agenda bashing
   5 min     Documents status
  10 min     Link information draft
  30 min     Best Current Practise draft
  60 min     Solutions work
  10 min     Wrap up

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 07:12:48 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13242
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 07:12:47 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFEY1E5ATO8X3IT9@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 21:11:23 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id BCA5BAB545; Tue,
 28 Sep 2004 21:11:16 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 75B6E4FB11; Tue, 28 Sep 2004 21:11:16 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8SBB2e03040	for dna-list; Tue, 28 Sep 2004 21:11:02 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8SBB0603036	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 21:11:00 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFEY0UNSPG8ZE6EF@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Tue,
 28 Sep 2004 21:10:51 +1000
Received: by localhost (Postfix, from userid 510)	id A38FE80002; Tue,
 28 Sep 2004 21:10:50 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.200])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 8331A3C010	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 21:10:48 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so75341rnk for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 04:10:47 -0700 (PDT)
Received: by 10.38.162.50 with SMTP id k50mr444773rne; Tue,
 28 Sep 2004 04:10:47 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Tue, 28 Sep 2004 04:10:47 -0700 (PDT)
Date: Tue, 28 Sep 2004 20:10:47 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <96A953E8-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>,
        Alper Yegin <alper.yegin@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb04092804105b742675@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
 <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
 <92e919fb040927160068a7f20b@mail.gmail.com>
 <96A953E8-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka

> > ok. Then the sentence will be
> >
> >    ................................................................The
> >    term 'link' used in this
> >    document is as defined in RFC 2461 [4].  The notion 'link' is not
> >    identical with the notion 'subnet' as defined in RFC 3753 [7].  For
> >    example, there may be more than one subnets in a link and a
> >    host connected to a link may be part of one or more of the subnets
> >    on the link.
> 
> Looks good to me.

Glad to hear that from you. :-)
 
> >> Bernard mentioned that one STA connecting to multiple APs
> >> simultaneously
> >> is not prohibited by the spec, and it is feasible. I recommend you
> >> replace "contact" with "be within the coverage are of". This reflects
> >> your intention, and uses common terms.
> >
> > ok. The sentence will be
> >
> >         ...... a host may be with in the coverage area of multiple
> >         (802.11) access points at the same time.
> 
> Looks good to me other than do we need to mention 802.11 here?
> If it is true for 802.11, it may be true for other wireless
> technologies, too.

That's right. I guess this is the common property of wireless technologies. 
However, the paragraph is intended to provide a concrete and tangible 
example that will underline my point. So I think it will do more good 
than harm to mention 802.11. Moreover, some wirless technologies 
use the term 'base station', instead of 'access point'. :-) 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 09:16:44 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20808
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 09:16:43 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFF2CNKW168ZE5VL@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Tue, 28 Sep 2004 23:15:04 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 67DA880002; Tue,
 28 Sep 2004 23:14:53 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 239463C008; Tue, 28 Sep 2004 23:14:53 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8SDESM04168	for dna-list; Tue, 28 Sep 2004 23:14:28 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8SDEQ604164	for
 <dna@ecselists.eng.monash.edu.au>; Tue, 28 Sep 2004 23:14:26 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFF2C185FE9EFG3A@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue,
 28 Sep 2004 23:14:23 +1000
Received: by localhost (Postfix, from userid 510)	id 897EF80002; Tue,
 28 Sep 2004 23:14:23 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.200])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 658483C003	for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 23:14:21 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 75so3955703rnl for
 <dna@eng.monash.edu.au>; Tue, 28 Sep 2004 06:14:17 -0700 (PDT)
Received: by 10.38.165.31 with SMTP id n31mr903480rne; Tue,
 28 Sep 2004 06:14:16 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Tue, 28 Sep 2004 06:14:16 -0700 (PDT)
Date: Tue, 28 Sep 2004 22:14:16 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: Erik Nordmark <erik.nordmark@sun.com>,
        JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb040928061478934620@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <41584347.4010200@sun.com>
 <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka

> >> For example, if a host has earlier been connected twice to the
> >> same link through two different interfaces, and then it detects
> >> that one of the interfaces has undergone a link change, IMHO that
> >> is a strong indication that there may have been a link change
> >> at the other interface, too.
> >
> > do you have a concrete example where this makes sense?
> 
> The specific example, though simplistic, that I've had in my mind
> is my home setting with my laptop.  I have a bridged Ethernet and
> WLAN.  When my laptop notices that I've disconnected it from the
> Ethernet, I may have just moving it around in our house, and it
> is still connected to the same link through WLAN.  On the other
> hand, I may have suspended it and moved it e.g. to the office,
> in which case it is now attached to a different WLAN.
> 
> Another example that I could imagine is a large operator network
> that from an IPv6 point of view acts as a single, large "LAN"
> or NBMA link.  (I know one operator that has plans like that.)
> The operator might offer different radio access technologies to
> access that "large LAN".  When one radio interface undergoes a
> change, it may make sense to quickly verify whether the other
> interfaces still are connected to the "large LAN".
> 
> In general, if two interfaces are connected to the same subnet,
> and one of the undergoes a link change, it often makes sense to
> check if the other one has also went through a link change.

I think the relation between a link change in one interface and 
a link change in another interface is similar to the relation between 
a link change in IP layer and a link-layer change in MAC layer. 
When a host changes its link-layer connection, it make sense to 
check whether a link change also has happened. However, 
a link-layer change doesn't automatically imply a link change, 
so IP layer can't solely depend on it and (typically) checks for 
link change for itself. So I guess their relationship is neither 
completely dependent nor completely independent, but, in between, 
interdependent. (It's as if I talk about the man-woman relationship. :-))

> > I don't have a problem relaxing the wording in the goals draft
> > to not accidentically preclude optimizations which share
> > information between interfaces, but I don't understand your
> > example above.
> 
> I was mostly objecting the notion that we should keep DNA on
> separate interfaces _completely_ independent.  To me, it looks
> like that there are cases when they are not.  I am oblivious
> how to handle this, through link hints, relaxing the language
> in the goals draft, or whatever.

It's not my intention to argue that we should keep DNA on 
separate interface _completely_ independent. 

It seems that we are in agreement that 

1. DNA schemes are typically run per interface.
2. When a host has multiple interfaces, the DNA related 
   informations can be shared between interfaces for the 
   better performance. DNA on separate interfaces need 
   not be completely independent. 

I think we have reached a common ground and would like to 
adopt your rewriting to resolve this issue. 

   DNA schemes are typically run per interface.  When a host has
   multiple interfaces, the host separately checks for link changes
   on each interface.

Kindly give your opinion on it. 

Best Regards

JinHyeock 

P.S.
This is 15th August, the greatest Korean holiday, HanGaWi. From 
earlier days, we celebrated good harvest with families under full
moon. Happy HanGaWi to all. :-)


From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 18:28:55 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29761
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 18:28:54 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFFLN86ULA9UMBEL@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Wed, 29 Sep 2004 08:28:01 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 1DAF1AB544; Wed,
 29 Sep 2004 08:27:50 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id CAAE14FB08; Wed, 29 Sep 2004 08:27:49 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8SMRCO09406	for dna-list; Wed, 29 Sep 2004 08:27:12 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8SMRB609402	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 29 Sep 2004 08:27:11 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFFLMBZNWG8X3HJW@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Wed,
 29 Sep 2004 08:27:07 +1000
Received: by localhost (Postfix, from userid 510)	id EB0E3AB543; Wed,
 29 Sep 2004 08:27:06 +1000 (EST)
Received: from mailout1.samsung.com (mailout1.samsung.com [203.254.224.24])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 58B1C4FB0B	for
 <dna@eng.monash.edu.au>; Wed, 29 Sep 2004 08:27:05 +1000 (EST)
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 id <0I4R00B01VP2LC@mailout1.samsung.com> for dna@eng.monash.edu.au; Wed,
 29 Sep 2004 07:27:02 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0I4R00KDWVP1YO@mailout1.samsung.com> for dna@eng.monash.edu.au;
 Wed, 29 Sep 2004 07:27:02 +0900 (KST)
Received: from Alperyegin ([105.253.155.49])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I4R00BZ2VOXHH@mmp2.samsung.com> for
 dna@eng.monash.edu.au; Wed, 29 Sep 2004 07:27:01 +0900 (KST)
Date: Tue, 28 Sep 2004 15:26:55 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <92e919fb040928061478934620@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "'JinHyeock Choi'" <jinchoe@gmail.com>,
        "'Pekka Nikander'" <pekka.nikander@nomadiclab.com>
Cc: "'Erik Nordmark'" <erik.nordmark@sun.com>,
        "'JinHyeock Choi'" <jinchoe@samsung.com>,
        "'Dna'" <dna@eng.monash.edu.au>
Message-id: <006401c4a5aa$45069860$6501a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT


> > I was mostly objecting the notion that we should keep DNA on
> > separate interfaces _completely_ independent.  

That was not my intention when I said "DNA scheme is run per-interface".
What I meant was the result that is produced by DNA scheme (e.g.,
whether IP reconfig is necessary) must have a target interface. It
cannot be per host, which may have multiple interfaces. Getting to that
result may use input from other network interfaces, and even non-network
interfaces (e.g., GPS), that's fine. 

The current text refers to "host" changing links. Actually, it is a
network interface on the host that is changing links. A dual-interfaced
host may disconnect eth0 from link_x connect eth1 to link_x. Host is
still connected to the same link, hence no "link change per-host", yet
the IP configurations on the eth0 and eth1 has to change. 

Maybe we should say "DNA scheme is run per-interface. While the
detection is performed for an interface, the DNA scheme may take hints
from other interfaces when useful. "

Alper






From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 18:59:09 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01272
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 18:59:08 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFFMLZ2XHY9UM9VZ@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Wed, 29 Sep 2004 08:55:16 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id D35BEAB544; Wed,
 29 Sep 2004 08:55:03 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 7ADA24FB10; Wed, 29 Sep 2004 08:55:03 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8SMqsb09784	for dna-list; Wed, 29 Sep 2004 08:52:54 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8SMqs609780	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 29 Sep 2004 08:52:54 +1000
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFFMJ5M2R08ZE6RV@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Wed,
 29 Sep 2004 08:52:48 +1000
Received: by localhost (Postfix, from userid 510)	id BD615AB54C; Wed,
 29 Sep 2004 08:52:47 +1000 (EST)
Received: from internaut.com
 (c-67-182-139-247.client.comcast.net [67.182.139.247])
	by moe.its.monash.edu.au (Postfix) with ESMTP id 8754F4FB0C	for
 <dna@eng.monash.edu.au>; Wed, 29 Sep 2004 08:52:44 +1000 (EST)
Received: from localhost (aboba@localhost)	by internaut.com (8.10.2/8.10.2)
 with ESMTP id i8SMhZn13130; Tue, 28 Sep 2004 15:43:36 -0700
Date: Tue, 28 Sep 2004 15:43:35 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
Subject: Re: [DNA] persistent TCP connection under 802.11 outage
In-reply-to: <Pine.GSO.4.58.0409272220130.5301@salad.cs.uiuc.edu>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Kai Chen <kaichen@cs.uiuc.edu>
Cc: dna@eng.monash.edu.au
Message-id: <Pine.LNX.4.56.0409281525130.11131@internaut.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: <Pine.GSO.4.58.0409272220130.5301@salad.cs.uiuc.edu>
Content-Transfer-Encoding: 7BIT

> Sorry if this question has been asked before. I am trying to keep a TCP
> connection persistent (e.g. SSH, FTP) over a 802.11 AP even after the
> wireless link experiences temporary outage.

Please be specific about the manner in which the "outage" is generated.
Did you pull the plug on the AP, or is the AP shedding load in an orderly
way (e.g. by Disassociating its associated stations)?

>
> Currently the scenario goes like this:
> 1) 802.11 NIC detects loss of link;
> 2) OS tears down the interface and clears all the exisiting TCP states;

I do not believe that 2) is appropriate behavior: Transport protocols
should not tear down state on receipt of a "link down" indication.

Research by MIT LCS and others has shown that WLAN links need not
necessarily be in the "up" (low packet loss) or "down" (100% packet
loss) state -- they can be intermediate states where a large fraction
of packets are lost or where connectivity is intermittent.  This is
particularly true for 802.11 adhoc operation in mesh networks.

Even in an indoor Infrastructure WLAN network where the classic
"up"/"down" model usually holds, it is possible for a STA to wander out of
range and then come back.  Where no explicit packet exchange
(e.g. Disassociate, Deauthenticate, etc.) has occurred, the "link down"
determination is typically made in an implementation specific way, based
on RSSI, packet loss, etc.

Implementations vary widely;  some will send a "link down" in only a
few seconds, others will take much longer.  The details are highly
dependent on the rate negotiation algorithm, which is not part
of the 802.11 standard.

In general, tearing down transport state on receipt of a "link down" makes
transport protocols more brittle than they need to be.  It can be argued
that this is true even given an explicit packet exchange -- a given AP
might be shutting down for maintenance and the STA might scan and
associate with another nearby AP soon after.  In this case, what good
did it do to tear down transport state?

> Does anyone know how to solve (or approach) this problem under both
> Windows XP and Linux? If the NIC's device driver can shield the link
> outage from the upper layer, this problem should go away, correct?

Shielding the outage is certainly one way to approach the problem, but a
better way is to fix the transport code so that it doesn't respond to
"link down" events.

I'm in the process of editing a document on the subject.  Comments
welcome:
http://www.drizzle.com/~aboba/IAB/draft-iab-link-indications-00.txt


From dna-owner@webcamserver.eng.monash.edu.au  Tue Sep 28 19:11:50 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01986
	for <dna-archive@lists.ietf.org>; Tue, 28 Sep 2004 19:11:49 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFFN37J41E9EFIDK@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Wed, 29 Sep 2004 09:09:16 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 9A1A4AB54C; Wed,
 29 Sep 2004 09:08:57 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 540F54FB03; Wed,
 29 Sep 2004 09:08:57 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8SN6nQ09955	for dna-list; Wed, 29 Sep 2004 09:06:49 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8SN6m609951	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 29 Sep 2004 09:06:48 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFFN0EAMI88ZE6S6@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Wed,
 29 Sep 2004 09:06:42 +1000
Received: by localhost (Postfix, from userid 510)	id C9F9C80002; Wed,
 29 Sep 2004 09:06:41 +1000 (EST)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 88E813C004	for
 <dna@eng.monash.edu.au>; Wed, 29 Sep 2004 09:06:39 +1000 (EST)
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by brmea-mail-4.sun.com (8.12.10/8.12.9) with ESMTP id i8SN6b53004013; Tue,
 28 Sep 2004 17:06:37 -0600 (MDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2)
 with ESMTP id i8SN6YJQ014979; Wed, 29 Sep 2004 01:06:35 +0200 (MEST)
Date: Tue, 28 Sep 2004 16:07:12 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Message-id: <4159EEA0.80804@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
Precedence: bulk
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <41584347.4010200@sun.com>
 <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

Pekka Nikander wrote:

>>> For example, if a host has earlier been connected twice to the
>>> same link through two different interfaces, and then it detects
>>> that one of the interfaces has undergone a link change, IMHO that
>>> is a strong indication that there may have been a link change
>>> at the other interface, too.

> The specific example, though simplistic, that I've had in my mind
> is my home setting with my laptop.  I have a bridged Ethernet and
> WLAN.  When my laptop notices that I've disconnected it from the
> Ethernet, I may have just moving it around in our house, and it
> is still connected to the same link through WLAN.  On the other
> hand, I may have suspended it and moved it e.g. to the office,
> in which case it is now attached to a different WLAN.

Yes, but your neighborhood ISP might provide metro Ethernet including
your house and your office. Taking GPRS and 802.11 as the interfaces 
illustrates this better - detecting attachment to a new link on one of
them doesn't say much about the other link.

In your example the more likely hint is that the laptop has been 
suspeded for some time, hence reverifying things makes a lot of sense.

  > Another example that I could imagine is a large operator network
> that from an IPv6 point of view acts as a single, large "LAN"
> or NBMA link.  (I know one operator that has plans like that.)
> The operator might offer different radio access technologies to
> access that "large LAN".  When one radio interface undergoes a
> change, it may make sense to quickly verify whether the other
> interfaces still are connected to the "large LAN".

But I still don't see why there would be a correlation since the 
technologies and operators might be different.

> In general, if two interfaces are connected to the same subnet,
> and one of the undergoes a link change, it often makes sense to
> check if the other one has also went through a link change.

I still don't understanding which assumption you are making.

A counter example would be that I have wired Ethernet and 802.11 in the 
house. Just because I unplug from the wire to walk around, or untangle 
some other wires on the floor in my office, doesn't mean I'm likely
to have changed the 802.11 AP. In any case, if I change the 802.11 AP
the device driver will associate with another AP hence can provide a 
hint to DNA.

> I was mostly objecting the notion that we should keep DNA on
> separate interfaces _completely_ independent.  To me, it looks
> like that there are cases when they are not.  I am oblivious
> how to handle this, through link hints, relaxing the language
> in the goals draft, or whatever.

Yes, at least across interfaces with compatible technology it makes 
sense to share retained information. Imagine a host which remembers DNA 
info (prefixes, default routers) and binds them with some L2 key (the 
MAC address of the Ethernet bridge or AP).
If the host has multiple Ethernets interfaces (or multiple 802.11 
interfaces) it should be able to find this cached information and make 
use of it; we shouldn't require that the same Ethernet wire be plugged 
in as the last time.

    Erik


From dna-owner@webcamserver.eng.monash.edu.au  Wed Sep 29 09:53:21 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04522
	for <dna-archive@lists.ietf.org>; Wed, 29 Sep 2004 09:53:20 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFGHXWZFR68X3KQE@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Wed, 29 Sep 2004 23:52:47 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id BC4BB80002; Wed,
 29 Sep 2004 23:52:42 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 6AA603C008; Wed, 29 Sep 2004 23:52:42 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8TDoSh18680	for dna-list; Wed, 29 Sep 2004 23:50:28 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8TDoQ618676	for
 <dna@ecselists.eng.monash.edu.au>; Wed, 29 Sep 2004 23:50:26 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFGHUZZKRU9X3JDJ@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed,
 29 Sep 2004 23:50:21 +1000
Received: by localhost (Postfix, from userid 510)	id BC700AB542; Wed,
 29 Sep 2004 23:50:21 +1000 (EST)
Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.196])
	by curly.its.monash.edu.au (Postfix) with ESMTP id AAF9E4FB0B	for
 <dna@eng.monash.edu.au>; Wed, 29 Sep 2004 23:50:19 +1000 (EST)
Received: by mproxy.gmail.com with SMTP id 73so142504rnl for
 <dna@eng.monash.edu.au>; Wed, 29 Sep 2004 06:50:18 -0700 (PDT)
Received: by 10.38.92.61 with SMTP id p61mr345535rnb; Wed,
 29 Sep 2004 06:50:18 -0700 (PDT)
Received: by 10.38.125.23 with HTTP; Wed, 29 Sep 2004 06:50:18 -0700 (PDT)
Date: Wed, 29 Sep 2004 22:50:18 +0900
From: JinHyeock Choi <jinchoe@gmail.com>
Subject: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
In-reply-to: <92e919fb04092804105b742675@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        Erik Nordmark <erik.nordmark@sun.com>, jim.bound@hp.com,
        vijayd@iprg.nokia.com
Cc: JinHyeock Choi <jinchoe@samsung.com>,
        Alper Yegin <alper.yegin@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: JinHyeock Choi <jinchoe@gmail.com>
Message-id: <92e919fb0409290650192c6e0b@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: <001401c4a2f6$a5cfa580$e95b024b@jinchoe>
 <003e01c4a4ba$14083110$291d9069@sisa.samsung.com>
 <92e919fb040927160068a7f20b@mail.gmail.com>
 <96A953E8-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb04092804105b742675@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

Dear Pekka, Jim, Alper, Vijay and Erik 
(in chronological order of comments :-)) 

Thanks for valuable feedback during WG LC. I incorporated your 
comments to modify the draft, that is available at 

http://www.diffeo.com/drafts/draft-ietf-dna-goals-pre02.txt

Kindly check whether your opinions are properly represented. 
In case of anything incorrect or missing, kindly let me know. 

Thanks in advance for your kind consideration. 

Best Regards

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Wed Sep 29 10:34:58 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09219
	for <dna-archive@lists.ietf.org>; Wed, 29 Sep 2004 10:34:57 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFGJ9CYR3M9X3JUP@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Thu, 30 Sep 2004 00:30:29 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id C450080006; Thu,
 30 Sep 2004 00:30:10 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id 79DC23C002; Thu, 30 Sep 2004 00:30:10 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8TETvO19230	for dna-list; Thu, 30 Sep 2004 00:29:57 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8TETu619226	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 30 Sep 2004 00:29:56 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFGJ8ULAEG9X3JUP@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 30 Sep 2004 00:29:46 +1000
Received: by localhost (Postfix, from userid 510)	id 474AFAB542; Thu,
 30 Sep 2004 00:29:46 +1000 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 7DA2B4FB08	for
 <dna@eng.monash.edu.au>; Thu, 30 Sep 2004 00:29:43 +1000 (EST)
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I4T00I0149HA4@mailout2.samsung.com> for dna@eng.monash.edu.au; Wed,
 29 Sep 2004 23:29:41 +0900 (KST)
Received: from ep_ms3_bk (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I4T00AO649G6N@mailout2.samsung.com> for dna@eng.monash.edu.au;
 Wed, 29 Sep 2004 23:29:40 +0900 (KST)
Received: from localhost (ms3.samsung.com [203.254.225.112])
 by ms3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with SMTP id <0I4T000Q249GD9@ms3.samsung.com> for
 dna@eng.monash.edu.au; Wed, 29 Sep 2004 23:29:40 +0900 (KST)
Date: Wed, 29 Sep 2004 14:29:37 +0000 (GMT)
From: SOOHONG PARK <soohong.park@samsung.com>
Subject: Re: Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
Sender: owner-dna@ecselists.eng.monash.edu.au
X-Sender: =?windows-1252?B?U2Ftc3VuZyBFbGVjdHJvbmljcz9Nb2Jp?=
 =?windows-1252?B?bGUgUGxhdGZvcm0gTGFiP0VuZ2luZWVy?=
To: JinHyeock Choi <jinchoe@gmail.com>
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        Erik Nordmark <erik.nordmark@sun.com>,
        "jim.bound@hp.com " <jim.bound@hp.com>,
        "vijayd@iprg.nokia.com " <vijayd@iprg.nokia.com>,
        JinHyeock Choi <jinchoe@samsung.com>,
        Alper Yegin <alper.yegin@samsung.com>, Dna <dna@eng.monash.edu.au>
Reply-to: soohong.park@samsung.com
Message-id: <3548984.1096468162668.JavaMail.weblogic@ep_app11>
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: 7BIT
X-Priority: 3
Precedence: bulk
Msgkey: 20040929142922666@soohong.park
X-MTR: 20040929142922666@soohong.park
X-EPLocale: en_US.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
X-Spam-Level: *
Content-Transfer-Encoding: 7BIT


I second this draft to be moved forward...

Just minor clarification,

Current references list in this draft should be reorganized
since several references are not cited around this draft.


Hope this helps.


Thanks

Daniel


------- Original Message -------
Sender : JinHyeock Choi<jinchoe@gmail.com>
Date   : Sep 29, 2004 22:50
Title  : Re: [DNA] Reminder: WG LC on draft-ietf-dna-goals-01.txt is running
Dear Pekka, Jim, Alper, Vijay and Erik 
(in chronological order of comments :-)) 

Thanks for valuable feedback during WG LC. I incorporated your 
comments to modify the draft, that is available at 

http://www.diffeo.com/drafts/draft-ietf-dna-goals-pre02.txt

Kindly check whether your opinions are properly represented. 
In case of anything incorrect or missing, kindly let me know. 

Thanks in advance for your kind consideration. 

Best Regards

JinHyeock



 
 
 
 
 
Regards   
 
Daniel (Soohong Daniel Park)
Mobile Platform Laboratory. SAMSUNG Electronics
Homepage:http://www.vsix.net/daniel 
 
 


From dna-owner@webcamserver.eng.monash.edu.au  Wed Sep 29 15:59:57 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03814
	for <dna-archive@lists.ietf.org>; Wed, 29 Sep 2004 15:59:55 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFGUQIR8YY8ZE7IE@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 30 Sep 2004 05:58:38 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 52A5CAB542; Thu,
 30 Sep 2004 05:58:35 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 9D7B04FB07; Thu, 30 Sep 2004 05:58:28 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8TJvaY22457	for dna-list; Thu, 30 Sep 2004 05:57:36 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8TJvS622451	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 30 Sep 2004 05:57:28 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFGUOSW3W89X3LJP@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 30 Sep 2004 05:57:12 +1000
Received: by localhost (Postfix, from userid 510)	id 60D1CAB542; Thu,
 30 Sep 2004 05:57:12 +1000 (EST)
Received: from mailout2.samsung.com (mailout2.samsung.com [203.254.224.25])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 507CE4FB02	for
 <dna@eng.monash.edu.au>; Thu, 30 Sep 2004 05:57:09 +1000 (EST)
Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 id <0I4T00601JF6RE@mailout2.samsung.com> for dna@eng.monash.edu.au; Thu,
 30 Sep 2004 04:57:07 +0900 (KST)
Received: from ep_mmp2 (mailout2.samsung.com [203.254.224.25])
 by mailout2.samsung.com
 (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
 with ESMTP id <0I4T00FX0JF60H@mailout2.samsung.com> for dna@eng.monash.edu.au;
 Thu, 30 Sep 2004 04:57:06 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I4T00JFJJF4Z9@mmp2.samsung.com> for
 dna@eng.monash.edu.au; Thu, 30 Sep 2004 04:57:06 +0900 (KST)
Date: Wed, 29 Sep 2004 12:57:03 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: [DNA] Feedback on draft-iab-link-indications
In-reply-to: <Pine.LNX.4.56.0409281525130.11131@internaut.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "'Bernard Aboba'" <aboba@internaut.com>, iab@ietf.org
Cc: dna@eng.monash.edu.au
Message-id: <00d701c4a65e$7f07a2c0$6501a8c0@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT

 
> I'm in the process of editing a document on the subject.  Comments
> welcome:
> http://www.drizzle.com/~aboba/IAB/draft-iab-link-indications-00.txt

I'm glad to see IAB is producing a document on link-layer indications.
This would be useful in many places. Thanks.

Let me register my feedback on the document.

This document has a good coverage. I'd recommend addition of DNAv6
discussions, with a reference to draft-ietf-dna-link-information-00.txt.
Also, a discussion around anticipation (link going up/down) would be
useful. Relevant references are draft-ietf-mipshop-fast-mipv6-02.txt and
draft-ietf-mipshop-80211fh-01.txt. 

The document is focused on IEEE 802.11. I think other wireless and wired
L2s are worth considering (802.3, gprs, cdma2000, etc.)


   Where the reliability of a link layer indication may be suspect, ...

I'm not sure what is meant by an unreliable L2 indication. An example
would help here.


   As a result, in situations where the Weak Host model is implemented,
...

What is a "weak host"? A reference to where it is defined would be
helpful.


   The result is that link
   layer indications may not be worth considering if they are wrong only
   a small fraction of the time.

Did you mean "correct only", or "wrong even" instead of "wrong only"?


   As noted earlier, in many circumstances, the definition of "link up"
   or "link down" may not be clear.  For example, where no response is
   provided to multiple retransmissions, a mobile node may wish to scan
   for an alternative point of attachment, since the likely reason for
   the loss is that it has moved out of range of the Access Point.
   However, in a stationary point-to-point installation, it is more
   likely that the link has become impaired, and therefore may return to
   service at a future point.  As a result, the definition of "link
   down" may change depending on the usage scenario.

Well, this is a L2 design issue imho. Once it assesses the situation as
link down and takes actions accordingly (including delivering a link
down event notification), the consumer of the L2 notification has
nothing to do but take it.


   2.4.  Layer compression

This section is not making any statement, other than providing
references. Layer compression's impact on the L2 indications (e.g., L3
information delivered by L2) can be discussed. Btw, PPP has the same
nature.


   2.5.  Remoting implications

When an access network element other than the L2 access device needs to
react to link events, remoting the notification is necessary. Please see
http://yegin.org/alper/draft-yegin-l2-triggers-00.txt.


   Since link layer indications are typically insecure, proposals
   incorporating them need to consider the potential security
   implications of spoofed or modified link layer indications, as well
   as the potential denial of service attacks.  This is particularly
   important in situations where insecure link layer indications are as
   a substitute for secure mechanisms operating at a higher layer.

Unless they are remoted, the indications are delivered within the same
node stack. I'm not sure which insecurity is this text referring to.


   As a result, link
   layer indications as implemented in [IEEE80211F] enable an attacker
   to disassociate a station located anywhere within the ESS, simply by
   sending a Reassociation Request frame.

This is due to the insecure design of that link-layer. What can we do
about it within the scope of L2 notifications and their consumers? If
the L2 is tricked into doing something, and it is simply notifying the
upper-layers after the fact, done is done...


   Claim and Defend
     Prior to configuration of a Link-Local IPv4 address, it is
     necessary to run a claim and defend protocol [IPv4LL].  Since a
     host needs to be present to defend its address against another
     claimant, and address conflicts are relatively likely, a host
     returning from sleep mode or receiving a "link up" indication could
     encounter an address conflict were it to utilize a formerly
     configured Link-Local IPv4 address without rerunning claim and
     defend.

Is this an issue for the link-layer indication, or its specific
consumer? I think the latter.


     Premature "link up" indications result in both security
     vulnerabilities and potential problems with IP address assignment.
     By causing the DS to be updated once a Reassociation Response is
     sent, [IEEE80211F] enables an attacker to disconnect attached
     stations at will by sending a Reassociation Request from anywhere
     within the ESS.

Again, this is a L2 design bug. Warning people about their presence is
good, but I wonder what we can recommend based on that.


   Link Layer Prefix Advertisement

I think "L2 suffix advertisement" is worth mentioning as well (e.g., via
PPP).

Regards,

Alper







From dna-owner@webcamserver.eng.monash.edu.au  Wed Sep 29 17:06:27 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14491
	for <dna-archive@lists.ietf.org>; Wed, 29 Sep 2004 17:06:26 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFGX36F0ZI9X3LPY@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Thu, 30 Sep 2004 07:06:15 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 5D632AB54C; Thu,
 30 Sep 2004 07:06:03 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id D7EBD4FB02; Thu,
 30 Sep 2004 07:06:02 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8TL5ZR23097	for dna-list; Thu, 30 Sep 2004 07:05:35 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8TL5U623093	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 30 Sep 2004 07:05:30 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFGX25AXPQ9X3LQ2@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 30 Sep 2004 07:05:14 +1000
Received: by localhost (Postfix, from userid 510)	id D84CCAB542; Thu,
 30 Sep 2004 07:05:13 +1000 (EST)
Received: from internaut.com
 (c-67-182-139-247.client.comcast.net [67.182.139.247])
	by curly.its.monash.edu.au (Postfix) with ESMTP id A00BA4FB05	for
 <dna@eng.monash.edu.au>; Thu, 30 Sep 2004 07:05:11 +1000 (EST)
Received: from localhost (aboba@localhost)	by internaut.com (8.10.2/8.10.2)
 with ESMTP id i8TKtRk32099; Wed, 29 Sep 2004 13:55:27 -0700
Date: Wed, 29 Sep 2004 13:55:27 -0700 (PDT)
From: Bernard Aboba <aboba@internaut.com>
Subject: [DNA] Re: Feedback on draft-iab-link-indications
In-reply-to: <00d701c4a65e$7f07a2c0$6501a8c0@sisa.samsung.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Alper Yegin <alper.yegin@samsung.com>
Cc: iab@ietf.org, dna@eng.monash.edu.au
Message-id: <Pine.LNX.4.56.0409291326470.30079@internaut.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: <00d701c4a65e$7f07a2c0$6501a8c0@sisa.samsung.com>
Content-Transfer-Encoding: 7BIT

Thanks for the feedback.

>    Where the reliability of a link layer indication may be suspect, ...
>
> I'm not sure what is meant by an unreliable L2 indication. An example
> would help here.

I was thinking of some of the recent research results from MIT Roofnet,
where many of the links are neither "up" nor "down", but rather in an
intermediate state.  Will fill in the details.

>    As a result, in situations where the Weak Host model is implemented,
> ...
>
> What is a "weak host"? A reference to where it is defined would be
> helpful.

OK.  I'll add this to the glossary.  I was thinking of the "weak host
model" where the outgoing interface is determined by the routing table.

>    The result is that link
>    layer indications may not be worth considering if they are wrong only
>    a small fraction of the time.
>
> Did you mean "correct only", or "wrong even" instead of "wrong only"?

I meant "wrong even".  That is a small probability of a mistake can make
the hint not worth considering if the penalty for being wrong is large.

> Well, this is a L2 design issue imho. Once it assesses the situation as
> link down and takes actions accordingly (including delivering a link
> down event notification), the consumer of the L2 notification has
> nothing to do but take it.

The problem is that in some scenarios (such as mesh networks) it is
sometimes unclear whether a link is "up" or "down".  The up/down model
assumes that a link is either in a state where it has low loss ("up") or
very high loss ("down").  In adhoc mesh networks there can be intermediate
states were loss is low in one direction and high in the other direction
(asymmetry);  or where loss is intermediate in one or both directions.

Even in 802.11 Infrastructure mode, link "up"/"down" indications are
heavily implementation dependent.  A link can have very high loss ("down")
at one rate, and be usable ("up") at another rate.  Tests show that rate
negotiation performance can vary widely.  Some implementations are fast,
others are very slow to recognize when the link has disappeared entirely.

Plus, even if the link to one AP is "down" there may be other APs in
the same SSID, so that Reassociation may be possible.  So if there is an
alternative link that can be brought "up" then it may make sense to
suppress sending a "down" indication after rate negotiation fails.

>    2.4.  Layer compression
>
> This section is not making any statement, other than providing
> references. Layer compression's impact on the L2 indications (e.g., L3
> information delivered by L2) can be discussed. Btw, PPP has the same
> nature.

Yes, that is a good suggestion.  I will work on it.


>    2.5.  Remoting implications
>
> When an access network element other than the L2 access device needs to
> react to link events, remoting the notification is necessary. Please see
> http://yegin.org/alper/draft-yegin-l2-triggers-00.txt.

This is taken care of by existing routing protocols when the route
metric takes L2 into account (such as ETX).  For example, with ETX an
increase in L2 loss will result in an increase in the routing metric which
will cause downstream nodes to find alternate paths.  If the link goes
down, then the route metric goes to infinity.

> Unless they are remoted, the indications are delivered within the same
> node stack. I'm not sure which insecurity is this text referring to.

L2 indication "remoting" can be thought of as a routing problem, so that
routing security issues arise.

> This is due to the insecure design of that link-layer. What can we do
> about it within the scope of L2 notifications and their consumers? If
> the L2 is tricked into doing something, and it is simply notifying the
> upper-layers after the fact, done is done...

The problem is caused because 802.11F spoofs a multicast packet indicating
that the host has attached before the host has authenticated itself.  The
problem would not occur if the AP did nothing and let the host's first
sent packet cause learning to occur in the switches.  Since the AP cannot
forward STA packets until authentication completes,  switch learning
cannot occurr prematurely this way.

>      returning from sleep mode or receiving a "link up" indication could
>      encounter an address conflict were it to utilize a formerly
>      configured Link-Local IPv4 address without rerunning claim and
>      defend.
>
> Is this an issue for the link-layer indication, or its specific
> consumer? I think the latter.

Yes -- the latter.

> Again, this is a L2 design bug. Warning people about their presence is
> good, but I wonder what we can recommend based on that.

It's an example of an L2 that is unclear about the definition of
"link up" and "link down".  The lack of standardization of roaming
and rate negotiation in 802.11 are other examples.


> I think "L2 suffix advertisement" is worth mentioning as well (e.g., via
> PPP).

OK.


From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 07:56:12 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13102
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 07:56:09 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFHS5407XS8X3KRF@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Thu, 30 Sep 2004 21:54:55 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 49CA880005; Thu,
 30 Sep 2004 21:54:51 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id D77EB3C006; Thu, 30 Sep 2004 21:54:50 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UBqEk32086	for dna-list; Thu, 30 Sep 2004 21:52:14 +1000
Received: from ALPHA1.ITS.MONASH.EDU.AU
 (alpha1.its.monash.edu.au [130.194.1.1])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UBqC632082	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 30 Sep 2004 21:52:12 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFHS1MCYMS9EFY6M@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 30 Sep 2004 21:52:02 +1000
Received: by localhost (Postfix, from userid 510)	id 801E580002; Thu,
 30 Sep 2004 21:52:02 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by larry.its.monash.edu.au (Postfix) with ESMTP id DD5133C006	for
 <dna@eng.monash.edu.au>; Thu, 30 Sep 2004 21:52:00 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id B86FD220003; Thu,
 30 Sep 2004 14:51:57 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id 4D7EC8; Thu,
 30 Sep 2004 14:51:58 +0300 (EEST)
Date: Thu, 30 Sep 2004 14:52:04 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <92e919fb040928061478934620@mail.gmail.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@gmail.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>,
        Erik Nordmark <erik.nordmark@sun.com>
Message-id: <25A7E532-12D7-11D9-A1D1-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; format=flowed; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <41584347.4010200@sun.com>
 <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb040928061478934620@mail.gmail.com>
Content-Transfer-Encoding: 7BIT

> It seems that we are in agreement that
>
> 1. DNA schemes are typically run per interface.
> 2. When a host has multiple interfaces, the DNA related
>    informations can be shared between interfaces for the
>    better performance. DNA on separate interfaces need
>    not be completely independent.

Agreed.

> I think we have reached a common ground and would like to
> adopt your rewriting to resolve this issue.
>
>    DNA schemes are typically run per interface.  When a host has
>    multiple interfaces, the host separately checks for link changes
>    on each interface.

Sounds good enough.  I wish I could suggest a slightly different
tone, but I don't have the energy right now.  Hence, this is good.

--Pekka



From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 07:56:41 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13126
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 07:56:40 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFHS5L85ES9EFTG4@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Thu, 30 Sep 2004 21:55:24 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 6D655AB54D; Thu,
 30 Sep 2004 21:55:14 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 1DCCB4FB04; Thu,
 30 Sep 2004 21:55:14 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UBt7L32130	for dna-list; Thu, 30 Sep 2004 21:55:07 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UBt7632126	for
 <dna@ecselists.eng.monash.edu.au>; Thu, 30 Sep 2004 21:55:07 +1000
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFHS52YDI09EFTG4@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu,
 30 Sep 2004 21:54:50 +1000
Received: by localhost (Postfix, from userid 510)	id 025FFAB545; Thu,
 30 Sep 2004 21:54:49 +1000 (EST)
Received: from pegasus.hiit.fi (pegasus.hiit.fi [212.68.1.186])
	by curly.its.monash.edu.au (Postfix) with ESMTP id 5F86E4FB08	for
 <dna@eng.monash.edu.au>; Thu, 30 Sep 2004 21:54:49 +1000 (EST)
Received: from n97.nomadiclab.com (teldanex.hiit.fi [128.214.112.65])
	by pegasus.hiit.fi (Postfix) with ESMTP	id 6F126220003; Thu,
 30 Sep 2004 14:54:47 +0300 (EEST)
Received: from [IPv6:::1] (teldanex-vpn.local.pnr.iki.fi [192.168.0.194])
	by n97.nomadiclab.com (Postfix) with ESMTP	id 06F8F8; Thu,
 30 Sep 2004 14:54:48 +0300 (EEST)
Date: Thu, 30 Sep 2004 14:54:53 +0300
From: Pekka Nikander <pekka.nikander@nomadiclab.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
In-reply-to: <4159EEA0.80804@sun.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Erik Nordmark <erik.nordmark@sun.com>
Cc: JinHyeock Choi <jinchoe@samsung.com>, Dna <dna@eng.monash.edu.au>
Message-id: <8A7A1100-12D7-11D9-A1D1-000D9331AFB0@nomadiclab.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.619)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <41584347.4010200@sun.com>
 <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com> <4159EEA0.80804@sun.com>
Content-Transfer-Encoding: 7BIT

Erik,

> I still don't understanding which assumption you are making.

I guess I wasn't clear enough in my own thinking.  I was mostly
motivated by the fear of painting ourselves somehow into a corner.

>> I was mostly objecting the notion that we should keep DNA on
>> separate interfaces _completely_ independent.  To me, it looks
>> like that there are cases when they are not.  I am oblivious
>> how to handle this, through link hints, relaxing the language
>> in the goals draft, or whatever.
>
> Yes, at least across interfaces with compatible technology
> it makes sense to share retained information. Imagine a host
> which remembers DNA info (prefixes, default routers) and binds
> them with some L2 key (the MAC address of the Ethernet bridge or
> AP).  If the host has multiple Ethernets interfaces (or multiple
> 802.11 interfaces) it should be able to find this cached
> information and make use of it; we shouldn't require that
> the same Ethernet wire be plugged in as the last time.

Good example, thanks!

--Pekka





From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 12:01:50 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03650
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 12:01:48 -0400 (EDT)
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI0Q6EBOW8ZE7FS@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 1 Oct 2004 02:00:58 +1000
Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 42C4D80004; Fri,
 01 Oct 2004 02:00:54 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by larry.its.monash.edu.au
 (Postfix) with ESMTP	id E7F813C00A; Fri, 01 Oct 2004 02:00:53 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UFxvp02493	for dna-list; Fri, 01 Oct 2004 01:59:57 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UFxt602489	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 01 Oct 2004 01:59:55 +1000
Received: from localhost ([130.194.13.87]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI0OSNDTY8ZE7FS@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Fri,
 01 Oct 2004 01:59:47 +1000
Received: by localhost (Postfix, from userid 510)	id 7DB18AB543; Fri,
 01 Oct 2004 01:59:47 +1000 (EST)
Received: from jaju.cvnet.co.kr (unknown [219.252.92.142])
	by curly.its.monash.edu.au (Postfix) with SMTP id EAE474FB09	for
 <dna@eng.monash.edu.au>; Fri, 01 Oct 2004 01:59:44 +1000 (EST)
Received: from 221.147.158.237 (221.147.158.237) by jaju.cvnet.co.kr with ZMAIL
 SMTP; Fri, 01 Oct 2004 00:59:31 +0900
Date: Fri, 01 Oct 2004 00:59:19 +0900
From: JinHyeock Choi <jinchoe@diffeo.com>
Subject: Re: [DNA] Issue about multiply connected to the same link and DNA
 being per-interface or not (was Re: WG LC comments on
 draft-ietf-dna-goals-01.txt)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        JinHyeock Choi <jinchoe@gmail.com>
Cc: Dna <dna@eng.monash.edu.au>, Erik Nordmark <erik.nordmark@sun.com>
Message-id: <00af01c4a706$78894180$ed9e93dd@jinchoe>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
X-Spam-Level: **
References: 
 <9C422444DE99BC46B3AD3C6EAFC9711B0766082B@tayexc13.americas.cpqcorp.net>
 <2D999597-0D3B-11D9-A57E-000D9331AFB0@nomadiclab.com>
 <011301c4a1d5$c3742010$e95b024b@jinchoe>
 <E7F315E6-0DFF-11D9-9B24-000D9331AFB0@nomadiclab.com>
 <000e01c4a2f6$505d1ab0$e95b024b@jinchoe>
 <2E0EE4FA-1057-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <41584347.4010200@sun.com>
 <17E2D104-1130-11D9-9F77-000D9331AFB0@nomadiclab.com>
 <92e919fb040928061478934620@mail.gmail.com>
 <25A7E532-12D7-11D9-A1D1-000D9331AFB0@nomadiclab.com>
Content-Transfer-Encoding: 7BIT

> > It seems that we are in agreement that
> >
> > 1. DNA schemes are typically run per interface.
> > 2. When a host has multiple interfaces, the DNA related
> >    informations can be shared between interfaces for the
> >    better performance. DNA on separate interfaces need
> >    not be completely independent.
> 
> Agreed.

Glad to hear that. 

> > I think we have reached a common ground and would like to
> > adopt your rewriting to resolve this issue.
> >
> >    DNA schemes are typically run per interface.  When a host has
> >    multiple interfaces, the host separately checks for link changes
> >    on each interface.
> 
> Sounds good enough.  I wish I could suggest a slightly different
> tone, but I don't have the energy right now.  Hence, this is good.

I am glad that we have found a common ground acceptable to both 
parties without much crawling and wish every contention to be 
resolved in this manner. Thanks for your trouble and I hope it's not 
me who wore you down. For me, sometimes, editing is the choice 
between the unpalatable and the unbearable. :-) 

JinHyeock


From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 14:04:44 2004
Received: from ALPHA8.ITS.MONASH.EDU.AU (alpha8.its.monash.edu.au [130.194.1.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15208
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 14:04:43 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI4UNQE828ZE8AM@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 1 Oct 2004 03:59:11 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id DB4E7AB54D; Fri,
 01 Oct 2004 03:59:02 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 832404FB06; Fri,
 01 Oct 2004 03:59:02 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UHwbP03780	for dna-list; Fri, 01 Oct 2004 03:58:37 +1000
Received: from ALPHA8.ITS.MONASH.EDU.AU
 (alpha8.its.monash.edu.au [130.194.1.8])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UHwZ603776	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 01 Oct 2004 03:58:35 +1000
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI4U2ADLI8X3HW4@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Fri,
 01 Oct 2004 03:58:34 +1000
Received: by localhost (Postfix, from userid 510)	id 44810AB54C; Fri,
 01 Oct 2004 03:58:34 +1000 (EST)
Received: from oak.research.panasonic.com
 (oak.Research.Panasonic.COM [150.169.1.4])	by moe.its.monash.edu.au (Postfix)
 with ESMTP id 2CE4C4FB03	for <dna@eng.monash.edu.au>; Fri,
 01 Oct 2004 03:58:32 +1000 (EST)
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])	by oak.research.panasonic.com
 (1.1.1/1.1.1) with SMTP id i8UHwLH7028604; Thu, 30 Sep 2004 13:58:21 -0400
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with ESMTP id A1F503C815F; Thu,
 30 Sep 2004 13:57:10 -0400 (EDT)
Received: from pintlmail.MITL.Research.Panasonic.COM
 (pintlmail.mitl.researc	h.panasonic.com [150.169.1.62])
 by redwood.research.panasonic.com (Postfix)	with ESMTP id 955DE3C8135; Thu,
 30 Sep 2004 13:57:10 -0400 (EDT)
Received: from [66.90.7.4] by pintlmail.MITL.Research.Panasonic.COM(mshttpd)
	; Thu, 30 Sep 2004 13:58:21 -0400
Date: Thu, 30 Sep 2004 13:58:21 -0400
From: Brijesh Kumar <kumarb@research.panasonic.com>
Subject: Re: [DNA] Issue about multiply connected to the same link andDNAbe	ing
 per-interface or not (was Re: WG LC commentsondraft-ietf-dna-goals-01.	txt)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: JinHyeock Choi <jinchoe@diffeo.com>
Cc: Pekka Nikander <pekka.nikander@nomadiclab.com>,
        JinHyeock Choi <jinchoe@gmail.com>, Dna <dna@eng.monash.edu.au>,
        Erik Nordmark <erik.nordmark@sun.com>
Message-id: <2852b256a4.256a42852b@pintlmail.MITL.Research.Panasonic.COM>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-disposition: inline
Content-transfer-encoding: 7BIT
Precedence: bulk
X-Accept-Language: en
X-imss-version: 2.0
X-imss-result: Passed
X-imss-scores: Clean:75.50468 C:17 M:1 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (0.2500 1.0000)
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT


----- Original Message -----
From: JinHyeock Choi <jinchoe@diffeo.com>
Date: Thursday, September 30, 2004 11:59 am
Subject: Re: [DNA] Issue about multiply connected to the same link and DNAbe ing per-interface or not (was Re: WG LC comments ondraft-ietf-dna-goals-01. txt)

> > > It seems that we are in agreement that
> > >
> > > 1. DNA schemes are typically run per interface.
> > > 2. When a host has multiple interfaces, the DNA related
> > >    informations can be shared between interfaces for the
> > >    better performance. DNA on separate interfaces need
> > >    not be completely independent.
> > 
> > Agreed.
> 
> Glad to hear that. 

I would like to add something to this interesting conversation.

Actually, it is hard to determine when multiple interfaces can share DNA related information and when they can't without some external knowledge. If two interfaces share the same link layer, you would most likely need to share the DNA information since both device interfaces will try to connect to the same attachment point. However, it need not be the case in all cases since interfaces may be configured to whatever a user wants. For example, interface A may be configured to connect to Red Basestation and interface B can be configured to connect to only Blue Base stations. How will a system determine if interfaces should share DNA information or not?

If the interfaces have different link layers, then they will most likely connect to two different attachment points, which may or may not be on the same sub-network. Again, in thhis case also, it is hard to determine whether interfaces can share DNA information or not?.

I think that sharing information between interfaces is good goal, but the mechanisms to achieve don't seem quite straight forward. 

Cheers,

--brijesh





From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 14:15:52 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15982
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 14:15:50 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI5DP1WD68ZE8AM@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 1 Oct 2004 04:14:33 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id C5CE3AB54D; Fri,
 01 Oct 2004 04:14:23 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id 3FD9E4FB05; Fri,
 01 Oct 2004 04:14:22 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UIE4104145	for dna-list; Fri, 01 Oct 2004 04:14:04 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UIDx604138	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 01 Oct 2004 04:13:59 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFI5CU763Q9EG0I9@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 01 Oct 2004 04:13:42 +1000
Received: by localhost (Postfix, from userid 510)	id 7019880002; Fri,
 01 Oct 2004 04:13:42 +1000 (EST)
Received: from nwkea-mail-2.sun.com (nwkea-mail-2.sun.com [192.18.42.14])
	by larry.its.monash.edu.au (Postfix) with ESMTP id 853C03C00A	for
 <dna@eng.monash.edu.au>; Fri, 01 Oct 2004 04:13:40 +1000 (EST)
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id i8UIDT35006540; Thu,
 30 Sep 2004 11:13:30 -0700 (PDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2)
 with ESMTP id i8UIDQJQ027537; Thu, 30 Sep 2004 20:13:27 +0200 (MEST)
Date: Thu, 30 Sep 2004 11:14:05 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Issue about multiply connected to the same link andDNAbe ing
 per-interface or not (was Re: WG LC commentsondraft-ietf-dna-goals-01. txt)
In-reply-to: <2852b256a4.256a42852b@pintlmail.MITL.Research.Panasonic.COM>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brijesh Kumar <kumarb@research.panasonic.com>
Cc: JinHyeock Choi <jinchoe@diffeo.com>,
        Pekka Nikander <pekka.nikander@nomadiclab.com>,
        JinHyeock Choi <jinchoe@gmail.com>, Dna <dna@eng.monash.edu.au>
Message-id: <415C4CED.4040308@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
Precedence: bulk
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Accept-Language: en-us, en
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: <2852b256a4.256a42852b@pintlmail.MITL.Research.Panasonic.COM>
Content-Transfer-Encoding: 7BIT

Brijesh Kumar wrote:

> Actually, it is hard to determine when multiple interfaces can share DNA related information and when they can't without some external knowledge. If two interfaces share the same link layer, you would most likely need to share the DNA information since both device interfaces will try to connect to the same attachment point. However, it need not be the case in all cases since interfaces may be configured to whatever a user wants. For example, interface A may be configured to connect to Red Basestation and interface B can be configured to connect to only Blue Base stations. How will a system determine if interfaces should share DNA information or not?

I can answer the question with an example solution. I picked the 
complete-prefix list (but I could have picked a linkid solution as well 
for this example).
If the prefix lists are maintained independently of the network 
interfaces, then the fact that a prefix is seen in a RA on the wlan0 
interface, where the prefix was recently heard (less than the prefix 
lifetime) on the eth3 interface, means that the host can assume that 
wlan0 is now connected to the same link as eth3 was connected to before.
Thus it can apply the prefix list and default routers it knew back on eth3.

Of course, there might be security easons to limit this. For instance, 
if the host knows that wlan0 is insecure somehow.

    Erik


From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 14:47:59 2004
Received: from ALPHA1.ITS.MONASH.EDU.AU (alpha1.its.monash.edu.au [130.194.1.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18084
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 14:47:58 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFI6HYEKIS9X3SRC@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Fri, 01 Oct 2004 04:46:12 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 5D850AB545; Fri,
 01 Oct 2004 04:46:04 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 938074FB09; Fri, 01 Oct 2004 04:46:00 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UIjcR04452	for dna-list; Fri, 01 Oct 2004 04:45:38 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UIjU604448	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 01 Oct 2004 04:45:31 +1000
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI6H6C0728X3H4I@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Fri,
 01 Oct 2004 04:45:27 +1000
Received: by localhost (Postfix, from userid 510)	id C3A74AB54C; Fri,
 01 Oct 2004 04:45:26 +1000 (EST)
Received: from oak.research.panasonic.com
 (oak.Research.Panasonic.COM [150.169.1.4])	by moe.its.monash.edu.au (Postfix)
 with ESMTP id A999B4FB09	for <dna@eng.monash.edu.au>; Fri,
 01 Oct 2004 04:45:24 +1000 (EST)
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])	by oak.research.panasonic.com
 (1.1.1/1.1.1) with SMTP id i8UIjLhc030261; Thu, 30 Sep 2004 14:45:21 -0400
Received: from redwood.research.panasonic.com
 (redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with ESMTP id A96943C8138; Thu,
 30 Sep 2004 14:44:10 -0400 (EDT)
Received: from pintlmail.MITL.Research.Panasonic.COM
 (pintlmail.mitl.researc	h.panasonic.com [150.169.1.62])
 by redwood.research.panasonic.com (Postfix)	with ESMTP id 9EACE3C8135; Thu,
 30 Sep 2004 14:44:10 -0400 (EDT)
Received: from [66.90.7.4] by pintlmail.MITL.Research.Panasonic.COM(mshttpd)
	; Thu, 30 Sep 2004 14:45:21 -0400
Date: Thu, 30 Sep 2004 14:45:21 -0400
From: Brijesh Kumar <kumarb@research.panasonic.com>
Subject: Re: [DNA] Issue about multiply connected to the same linkandDNAbe i
	ngper-interface or not (was Re: WG LCcommentsondraft-ietf-dna-goals-01. t	x	t)
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Erik Nordmark <erik.nordmark@sun.com>
Cc: JinHyeock Choi <jinchoe@diffeo.com>,
        Pekka Nikander <pekka.nikander@nomadiclab.com>,
        JinHyeock Choi <jinchoe@gmail.com>, Dna <dna@eng.monash.edu.au>
Message-id: <216e124a2b.24a2b216e1@pintlmail.MITL.Research.Panasonic.COM>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.09 (built Jan  7 2003)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Precedence: bulk
X-imss-version: 2.0
X-imss-result: Passed
X-imss-scores: Clean:33.31713 C:17 M:1 S:5 R:5
X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (0.2500 1.0000)
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc3 (2004-09-03)
Content-Transfer-Encoding: 7BIT



----- Original Message -----
From: Erik Nordmark <erik.nordmark@sun.com>

> Brijesh Kumar wrote:
> 
> > Actually, it is hard to determine when multiple interfaces can 
> share DNA related information and when they can't without some 
> external knowledge. If two interfaces share the same link layer, 
> you would most likely need to share the DNA information since both 
> device interfaces will try to connect to the same attachment 
> point. However, it need not be the case in all cases since 
> interfaces may be configured to whatever a user wants. For 
> example, interface A may be configured to connect to Red 
> Basestation and interface B can be configured to connect to only 
> Blue Base stations. How will a system determine if interfaces 
> should share DNA information or not?
> 
> I can answer the question with an example solution. I picked the 
> complete-prefix list (but I could have picked a linkid solution as 
> well 
> for this example).
> If the prefix lists are maintained independently of the network 
> interfaces, then the fact that a prefix is seen in a RA on the 
> wlan0 
> interface, where the prefix was recently heard (less than the 
> prefix 
> lifetime) on the eth3 interface, means that the host can assume 
> that 
> wlan0 is now connected to the same link as eth3 was connected to 
> before.Thus it can apply the prefix list and default routers it 
> knew back on eth3.


Erik:

In the above scenario, you are right.

But, I am not sure when a device moves if the inter-relationship 
between two interfaces continues based on past knowledge of prefixes. 
May be the device movement caused the first interface to loose the 
connectivity, and the second interface to attach to a new attachment 
point (no RA received yet to determine any thing about the network).

> 
> Of course, there might be security easons to limit this. For 
> instance, 
> if the host knows that wlan0 is insecure somehow.

Interesting observation.

cheers,

--brijesh



From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 14:51:30 2004
Received: from ALPHA9.ITS.MONASH.EDU.AU (alpha9.its.monash.edu.au [130.194.1.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18352
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 14:51:29 -0400 (EDT)
Received: from localhost ([130.194.13.88]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI6NC92068X3RSU@vaxh.its.monash.edu.au> for
 dna-archive@lists.ietf.org; Fri, 1 Oct 2004 04:50:28 +1000
Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id C24D5AB54D; Fri,
 01 Oct 2004 04:50:24 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])
	by moe.its.monash.edu.au (Postfix) with ESMTP	id D2B394FB02; Fri,
 01 Oct 2004 04:50:20 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UIo7104525	for dna-list; Fri, 01 Oct 2004 04:50:07 +1000
Received: from ALPHA9.ITS.MONASH.EDU.AU
 (alpha9.its.monash.edu.au [130.194.1.9])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UIo0604518	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 01 Oct 2004 04:50:01 +1000
Received: from localhost ([130.194.13.82]) by vaxh.its.monash.edu.au
 (PMDF V5.2-31 #39306)
 with ESMTP id <01LFI6MJMCRC8X3RSU@vaxh.its.monash.edu.au> for
 dna@ecselists.eng.monash.edu.au (ORCPT rfc822;dna@eng.monash.edu.au); Fri,
 01 Oct 2004 04:49:46 +1000
Received: by localhost (Postfix, from userid 510)	id 7C61080003; Fri,
 01 Oct 2004 04:49:46 +1000 (EST)
Received: from mailout1.samsung.com (mailout1.samsung.com [203.254.224.24])
	by larry.its.monash.edu.au (Postfix) with ESMTP id AE42B3C00E	for
 <dna@eng.monash.edu.au>; Fri, 01 Oct 2004 04:49:43 +1000 (EST)
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 id <0I4V00G01AYUCX@mailout1.samsung.com> for dna@eng.monash.edu.au; Fri,
 01 Oct 2004 03:49:42 +0900 (KST)
Received: from ep_mmp2 (mailout1.samsung.com [203.254.224.24])
 by mailout1.samsung.com
 (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
 with ESMTP id <0I4V00F30AYT4K@mailout1.samsung.com> for dna@eng.monash.edu.au;
 Fri, 01 Oct 2004 03:49:41 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
 by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23
 2003)) with ESMTPA id <0I4V00HJ7AYRH6@mmp2.samsung.com> for
 dna@eng.monash.edu.au; Fri, 01 Oct 2004 03:49:41 +0900 (KST)
Date: Thu, 30 Sep 2004 11:49:38 -0700
From: Alper Yegin <alper.yegin@samsung.com>
Subject: [DNA] RE: Feedback on draft-iab-link-indications
In-reply-to: <Pine.LNX.4.56.0409291326470.30079@internaut.com>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: "'Bernard Aboba'" <aboba@internaut.com>
Cc: iab@ietf.org, dna@eng.monash.edu.au
Message-id: <000001c4a71e$3e748e60$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Precedence: bulk
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
Content-Transfer-Encoding: 7BIT

> > Well, this is a L2 design issue imho. Once it assesses the situation
as
> > link down and takes actions accordingly (including delivering a link
> > down event notification), the consumer of the L2 notification has
> > nothing to do but take it.
> 
> The problem is that in some scenarios (such as mesh networks) it is
> sometimes unclear whether a link is "up" or "down".  The up/down model
> assumes that a link is either in a state where it has low loss ("up")
or
> very high loss ("down").  In adhoc mesh networks there can be
intermediate
> states were loss is low in one direction and high in the other
direction
> (asymmetry);  

How is the interface treated in that case? It is like "link up for
transmission, down for reception". Is this how it is presented to the IP
stack, and the forwarding takes this into account somehow?

> or where loss is intermediate in one or both directions.
> 
> Even in 802.11 Infrastructure mode, link "up"/"down" indications are
> heavily implementation dependent.  A link can have very high loss
("down")
> at one rate, and be usable ("up") at another rate.  Tests show that
rate
> negotiation performance can vary widely.  Some implementations are
fast,
> others are very slow to recognize when the link has disappeared
entirely.

Yes, I agree correct and consistent implementation of link up/down on
the L2 is important.

> Plus, even if the link to one AP is "down" there may be other APs in
> the same SSID, so that Reassociation may be possible.  So if there is
an
> alternative link that can be brought "up" then it may make sense to
> suppress sending a "down" indication after rate negotiation fails.

Maybe. The downside is, if the L2 is going to suppress the events, it
better know which ones to suppress. This requires pushing some of the
logic from upper-layer to L2. After all, the consumers of L2
notifications are the ones that know which ones are interesting.

> >    2.5.  Remoting implications
> >
> > When an access network element other than the L2 access device needs
to
> > react to link events, remoting the notification is necessary. Please
see
> > http://yegin.org/alper/draft-yegin-l2-triggers-00.txt.
> 
> This is taken care of by existing routing protocols when the route
> metric takes L2 into account (such as ETX).  For example, with ETX an
> increase in L2 loss will result in an increase in the routing metric
which
> will cause downstream nodes to find alternate paths.  If the link goes
> down, then the route metric goes to infinity.

The simple example I had was sending an unsolicited router advertisement
as soon as a new host attaches to the network. That happens with
cdma2k/3GPP2, though the L2 attachment point and first hop router are
the same (PDSN).

> > This is due to the insecure design of that link-layer. What can we
do
> > about it within the scope of L2 notifications and their consumers?
If
> > the L2 is tricked into doing something, and it is simply notifying
the
> > upper-layers after the fact, done is done...
> 
> The problem is caused because 802.11F spoofs a multicast packet
indicating
> that the host has attached before the host has authenticated itself.
The
> problem would not occur if the AP did nothing and let the host's first
> sent packet cause learning to occur in the switches.  Since the AP
cannot
> forward STA packets until authentication completes,  switch learning
> cannot occurr prematurely this way.

I understand. I think this is just an example of a incorrectly
implemented link up on IEEE 802.11 and how it breaks things. If we
characterize the text like that, than I can understand how it fits this
document.

Alper




From dna-owner@webcamserver.eng.monash.edu.au  Thu Sep 30 15:14:12 2004
Received: from ALPHA6.ITS.MONASH.EDU.AU (alpha6.its.monash.edu.au [130.194.1.25])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20996
	for <dna-archive@lists.ietf.org>; Thu, 30 Sep 2004 15:14:11 -0400 (EDT)
Received: from localhost ([130.194.13.87]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFI7CRTDXE9EG3U5@vaxc.its.monash.edu.au>
 for dna-archive@lists.ietf.org; Fri, 01 Oct 2004 05:11:28 +1000
Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1])
	by localhost (Postfix) with ESMTP	id 25B83AB545; Fri,
 01 Oct 2004 05:10:55 +1000 (EST)
Received: from webcamserver.eng.monash.edu.au
 (webcamserver.eng.monash.edu.au [130.194.5.143])	by curly.its.monash.edu.au
 (Postfix) with ESMTP	id 18B494FB07; Fri, 01 Oct 2004 05:10:52 +1000 (EST)
Received: (from majordomo@localhost)	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) id i8UJAEo04748	for dna-list; Fri, 01 Oct 2004 05:10:14 +1000
Received: from ALPHA6.ITS.MONASH.EDU.AU
 (alpha6.its.monash.edu.au [130.194.1.25])	by webcamserver.eng.monash.edu.au
 (8.11.6/8.11.0) with ESMTP id i8UJA6604744	for
 <dna@ecselists.eng.monash.edu.au>; Fri, 01 Oct 2004 05:10:06 +1000
Received: from localhost ([130.194.13.82]) by vaxc.its.monash.edu.au
 (PMDF V6.1 #39306) with ESMTP id <01LFI7BD5RF69X3RQQ@vaxc.its.monash.edu.au>
 for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri,
 01 Oct 2004 05:09:47 +1000
Received: by localhost (Postfix, from userid 510)	id 184D980002; Fri,
 01 Oct 2004 05:09:46 +1000 (EST)
Received: from brmea-mail-3.sun.com (brmea-mail-3.Sun.COM [192.18.98.34])
	by larry.its.monash.edu.au (Postfix) with ESMTP id C319B3C00C	for
 <dna@eng.monash.edu.au>; Fri, 01 Oct 2004 05:09:44 +1000 (EST)
Received: from bebop.France.Sun.COM ([129.157.174.15])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id i8UJ9cil020368; Thu,
 30 Sep 2004 13:09:39 -0600 (MDT)
Received: from [192.9.61.11] (punchin-nordmark.SFBay.Sun.COM [192.9.61.11])
	by bebop.France.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2)
 with ESMTP id i8UJ9ZJQ000933; Thu, 30 Sep 2004 21:09:36 +0200 (MEST)
Date: Thu, 30 Sep 2004 12:10:15 -0700
From: Erik Nordmark <erik.nordmark@sun.com>
Subject: Re: [DNA] Issue about multiply connected to the same linkandDNAbe i
	ngper-interface or not (was Re: WG LCcommentsondraft-ietf-dna-goals-01. t	x	t)
In-reply-to: <216e124a2b.24a2b216e1@pintlmail.MITL.Research.Panasonic.COM>
Sender: owner-dna@ecselists.eng.monash.edu.au
To: Brijesh Kumar <kumarb@research.panasonic.com>
Cc: JinHyeock Choi <jinchoe@diffeo.com>,
        Pekka Nikander <pekka.nikander@nomadiclab.com>,
        JinHyeock Choi <jinchoe@gmail.com>, Dna <dna@eng.monash.edu.au>
Message-id: <415C5A17.8060209@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en
Precedence: bulk
User-Agent: Mozilla Thunderbird 0.8 (X11/20040916)
X-Spam-Checker-Version: SpamAssassin 3.0.0-rc2 (2004-08-15)
References: <216e124a2b.24a2b216e1@pintlmail.MITL.Research.Panasonic.COM>
Content-Transfer-Encoding: 7BIT

Brijesh Kumar wrote:

> In the above scenario, you are right.
> 
> But, I am not sure when a device moves if the inter-relationship 
> between two interfaces continues based on past knowledge of prefixes. 
> May be the device movement caused the first interface to loose the 
> connectivity, and the second interface to attach to a new attachment 
> point (no RA received yet to determine any thing about the network).

In general you need to receive at least RA to verify that the interface 
is connected to a particular link.

There are exceptions when things can be determined at L2.
The "non movement" L2 exceptions are things like PPP multilink and IEEE 
802.3ad link aggregation where L2 knows that two or more L2 interfaces 
are "bonded" together to form one. Typically this is completely hidden 
from the IP software.

But in the case of DNA there might be interesting hints from L2
that do not require L3 verification. For instance, if the L2 detects 
that it has changed 802.11 APs, and that the MAC address of the AP is 
the same as the AP I used 5 minutes ago, then it would probably be 
reasonable to use whatever L3 configuration I had 5 minutes ago (asuming 
I retained it) (of course, subject to the prefix and default router 
lifetimes for that retained information).

    Erik



