From dna-owner@webcamserver.eng.monash.edu.au Wed Aug 02 15:48:10 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8MhO-0002Wm-T7 for dna-archive@lists.ietf.org; Wed, 02 Aug 2006 15:48:10 -0400 Received: from alpha8.its.monash.edu.au ([130.194.1.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8MhM-0008RY-Hp for dna-archive@lists.ietf.org; Wed, 02 Aug 2006 15:48:10 -0400 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M5JM3HK3W48YED2R@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Thu, 03 Aug 2006 05:44:51 +1000 Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id C63DFAB543; Thu, 03 Aug 2006 05:44:46 +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 823474FB02; Thu, 03 Aug 2006 05:44:46 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k72JghL11392 for dna-list; Thu, 03 Aug 2006 05:42:43 +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 k72Jggu11388 for ; Thu, 03 Aug 2006 05:42:42 +1000 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M5JM0QYQ788XF956@vaxc.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu, 03 Aug 2006 05:42:35 +1000 Received: by localhost (Postfix, from userid 510) id 26860AB543; Thu, 03 Aug 2006 05:42:35 +1000 (EST) Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by curly.its.monash.edu.au (Postfix) with ESMTP id 0ABE54FB13 for ; Thu, 03 Aug 2006 05:42:32 +1000 (EST) Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id k72JutBX008123 for ; Wed, 02 Aug 2006 14:56:58 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 02 Aug 2006 14:42:00 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 02 Aug 2006 14:39:33 -0500 Received: from [142.133.10.140] ([142.133.10.140]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 02 Aug 2006 14:39:32 -0500 Date: Wed, 02 Aug 2006 15:48:52 -0400 From: Suresh Krishnan Subject: [DNA] [Fwd: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt] Sender: owner-dna@ecselists.eng.monash.edu.au To: Dna Cc: Greg Daley Message-id: <44D101A4.2000106@ericsson.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_5gb3GcXWoaf7Atub5PhWWA)" User-Agent: Thunderbird 1.5 (X11/20060313) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-OriginalArrivalTime: 02 Aug 2006 19:39:32.0804 (UTC) FILETIME=[60C6E040:01C6B66B] X-Spam-Score: 0.1 (/) X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a This is a multi-part message in MIME format. --Boundary_(ID_5gb3GcXWoaf7Atub5PhWWA) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT Hi Folks, The ipv6 chairs have come up with a way to extend the flag bits in a router advertisement. The good news is that both the reserved bits in the current 8 bit flags field are available for allocation. Once a registry is setup for these bits we will go ahead and make a request for allocation of these two bits to the combined DNA proposal. Cheers Suresh --Boundary_(ID_5gb3GcXWoaf7Atub5PhWWA) Content-type: message/rfc822; name="I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt" Return-path: Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by ecamlmw720.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 01 Aug 2006 17:05:49 -0400 Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 01 Aug 2006 16:05:47 -0500 Received: from esealmw127.eemea.ericsson.se ([130.100.184.162]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 01 Aug 2006 23:05:44 +0200 Received: from mailgw1.ericsson.se ([193.180.251.59]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 01 Aug 2006 23:05:43 +0200 Received: from megatron.ietf.org (stiedprmman1.ietf.org [156.154.16.145]) by mailgw1.ericsson.se (Symantec Mail Security) with ESMTP id C340C88F; Tue, 01 Aug 2006 23:05:42 +0200 (CEST) Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G81Q4-0002ia-8s; Tue, 01 Aug 2006 17:04:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G81Q2-0002i1-8o for i-d-announce@ietf.org; Tue, 01 Aug 2006 17:04:50 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G80zW-0004Hi-4l for i-d-announce@ietf.org; Tue, 01 Aug 2006 16:37:26 -0400 Received: from ns4.neustar.com ([156.154.24.139]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G80kc-0006ff-NS for i-d-announce@ietf.org; Tue, 01 Aug 2006 16:22:04 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id B43762ACAC for ; Tue, 01 Aug 2006 19:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1G80Fd-0004yw-Fb for i-d-announce@ietf.org; Tue, 01 Aug 2006 15:50:01 -0400 Date: Tue, 01 Aug 2006 15:50:01 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-haberman-ipv6-ra-flags-option-00.txt To: i-d-announce@ietf.org Cc: Errors-to: i-d-announce-bounces@ietf.org Reply-to: internet-drafts@ietf.org Message-id: MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_27vxCaGp3UFgcQ2zqWsGeQ)" Precedence: list X-Spam-Score: -5.9 (-----) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 X-Brightmail-Tracker: AAAAAA== List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: List-Help: List-Id: i-d-announce.ietf.org X-OriginalArrivalTime: 01 Aug 2006 21:05:43.0607 (UTC) FILETIME=[40670C70:01C6B5AE] --Boundary_(ID_27vxCaGp3UFgcQ2zqWsGeQ) Content-type: TEXT/PLAIN Content-transfer-encoding: 7BIT A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IPv6 Router Advertisement Flags Option Author(s) : B. Haberman, R. Hinden Filename : draft-haberman-ipv6-ra-flags-option-00.txt Pages : 7 Date : 2006-8-1 The IPv6 Neighbor Discovery's Router Advertisement message contains an 8-bit field reserved for single-bit flags. Several protocols have reserved flags in this field and others are preparing to reserve a sufficient number of flags to exhaust the field. This document defines an option to the Router Advertisement message that expands the available number of flag bits available. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-haberman-ipv6-ra-flags-option-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-haberman-ipv6-ra-flags-option-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-haberman-ipv6-ra-flags-option-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_27vxCaGp3UFgcQ2zqWsGeQ) Content-type: multipart/alternative; boundary="Boundary_(ID_mlPvM4fURyC6U+UTv7Cilg)" --Boundary_(ID_mlPvM4fURyC6U+UTv7Cilg) Content-type: Message/External-body; access-type=mail-server; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-8-1141246.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-haberman-ipv6-ra-flags-option-00.txt --Boundary_(ID_mlPvM4fURyC6U+UTv7Cilg) Content-type: Message/External-body; name=draft-haberman-ipv6-ra-flags-option-00.txt; site=ftp.ietf.org; access-type=anon-ftp; directory=internet-drafts Content-disposition: attachment; filename=draft-haberman-ipv6-ra-flags-option-00.txt Content-Type: text/plain Content-ID: <2006-8-1141246.I-D@ietf.org> --Boundary_(ID_mlPvM4fURyC6U+UTv7Cilg)-- --Boundary_(ID_27vxCaGp3UFgcQ2zqWsGeQ) MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --Boundary_(ID_27vxCaGp3UFgcQ2zqWsGeQ)-- --Boundary_(ID_5gb3GcXWoaf7Atub5PhWWA)-- From dna-owner@webcamserver.eng.monash.edu.au Wed Aug 02 15:53:27 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8MmV-0001jq-H1 for dna-archive@lists.ietf.org; Wed, 02 Aug 2006 15:53:27 -0400 Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8MmS-0000Ps-Nu for dna-archive@lists.ietf.org; Wed, 02 Aug 2006 15:53:27 -0400 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M5JMDPN1GI8WY8J4@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Thu, 03 Aug 2006 05:53:03 +1000 Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id B91CEAB545; Thu, 03 Aug 2006 05:53: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 7112A4FB0A; Thu, 03 Aug 2006 05:53:01 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k72JqiR11578 for dna-list; Thu, 03 Aug 2006 05:52:44 +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 k72Jqhu11574 for ; Thu, 03 Aug 2006 05:52:43 +1000 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M5JMDA2YRG8WY8J4@vaxh.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu, 03 Aug 2006 05:52:41 +1000 Received: by localhost (Postfix, from userid 510) id 4288EAB542; Thu, 03 Aug 2006 05:52:41 +1000 (EST) Received: from imr1.ericy.com (imr1.ericy.com [198.24.6.9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by moe.its.monash.edu.au (Postfix) with ESMTP id 27B334FB0E for ; Thu, 03 Aug 2006 05:52:39 +1000 (EST) Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id k72JqVvQ003718; Wed, 02 Aug 2006 14:52:36 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 02 Aug 2006 14:52:29 -0500 Received: from [142.133.10.140] ([142.133.10.140]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 02 Aug 2006 14:52:29 -0500 Date: Wed, 02 Aug 2006 16:01:49 -0400 From: Suresh Krishnan Subject: [DNA] IETF66 minutes and slides Sender: owner-dna@ecselists.eng.monash.edu.au To: Dna Cc: Greg Daley Message-id: <44D104AD.8000305@ericsson.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5 (X11/20060313) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-OriginalArrivalTime: 02 Aug 2006 19:52:29.0368 (UTC) FILETIME=[2FA52380:01C6B66D] X-Spam-Score: 0.1 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Hi Folks, The dna working group minutes and slides from IETF66 are now available at the IETF66 meeting materials page located at https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=66 Thanks to Shinta Sugimoto and Michael Richardson for volunteering to take minutes. If you see any required corrections to the minutes please send them to the chairs or to the list by Thursday 10th August 2006. Cheers Suresh From dna-owner@webcamserver.eng.monash.edu.au Wed Aug 02 17:01:23 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G8NqF-0004Oi-Ce for dna-archive@lists.ietf.org; Wed, 02 Aug 2006 17:01:23 -0400 Received: from alpha8.its.monash.edu.au ([130.194.1.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G8NqC-0004sW-J1 for dna-archive@lists.ietf.org; Wed, 02 Aug 2006 17:01:23 -0400 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M5JOR5CP628WYBSI@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Thu, 03 Aug 2006 07:01:09 +1000 Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 8D140AB544; Thu, 03 Aug 2006 07:01:07 +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 44CD14FB03; Thu, 03 Aug 2006 07:01:07 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k72L03k12280 for dna-list; Thu, 03 Aug 2006 07:00:03 +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 k72L02u12276 for ; Thu, 03 Aug 2006 07:00:02 +1000 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M5JOPG5KZ28ZE4JU@vaxc.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu, 03 Aug 2006 06:59:47 +1000 Received: by localhost (Postfix, from userid 510) id 62503AB542; Thu, 03 Aug 2006 06:59:47 +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 1302B4FB04 for ; Thu, 03 Aug 2006 06:59:45 +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 ESMTP id k72Kxll6012874 for ; Wed, 02 Aug 2006 16:59:47 -0400 Received: from [150.169.1.180] ([150.169.1.180]) by redwood.research.panasonic.com (MOS 3.7.4b-GA) with ESMTP id AHQ86704; Wed, 02 Aug 2006 16:57:16 -0400 (EDT) Date: Wed, 02 Aug 2006 16:59:44 -0400 From: Greg Daley Subject: [DNA] Document merger: next steps. Sender: owner-dna@ecselists.eng.monash.edu.au To: Dna Message-id: <44D11240.30706@research.panasonic.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Dear WG, I've looked through the documents and it looks like draft-ietf-dna-protocol-01 will make a good basis for the document, with the revisions proposed by JinHyeock, to the host's change detection procedures. So while most of the document will have to be edited to ensure consistency between original and externally sourced content, certain sections will have limited disruption. Particularly, inspection of draft-ietf-dna-cpl-02 indicates only one subsection which refers to router configuration variables: section 3.1, which refers to safe delays for CPL generation (MIN_DELAY_BETWEEN_RAS, etc). Similarly draft-ietf-dna-hosts-03.txt refers to router configurations only a few times: In section 3.1, it describes justification of why DNA is performed (restating goals from RFC4135), regarding routers leaving prefixes out of advertisements. Sections 4.2.1, 5.4 and 5.6 make passing reference to the RFC 3775 Advertisement Interval Option. Given that CPL relies on underlying link-indications, this is not necessary to use in the combined document. Section 6.2 discusses inconsistencies between routers on the same link in their configurations. This is probably useful to retain as a warning. As such the descriptions of the DNA host algorithm can be merged into that from draft-ietf-dna-protocol without introducing further relationships between host and router text in the combined document. One possible exception if Tentative Options. The existing Tentative Options document is divided into host and router sections already, with the host and router components being largely independent. The remaining issues for tentative options are that the security considerations (section 5) allow the router to make assumptions of the router solicitation intervals from the host, and appendix C describes modified procedures which ignore neighbour cache entries. SUGGESTED ACTIONS: 1. Design the relationship between text sources for Host side operations (following JinHyeock's plan). (Subsection by subsection (not specific text)). 2. Formalize the Table of Contents for the combined document. 3. Merge (router side) Tentative Options into the (router side) protocol document. 4. Identify if text from existing documents is close to what is needed for each subsection. 5. Generate a task list of sub-sections which need (b) editing from existing sources (c) merger of multiple sources (d) complete rewrite (e) further consultation/issue resolution. I'm assuming that all sections need to be modified, and may then be placed in a category: (a) accepted text. Once we have an idea of which class each subsection goes in, we can make efforts to generate text for a new draft. Does this make sense? Greg From dna-owner@webcamserver.eng.monash.edu.au Tue Aug 08 21:16:32 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GAcgS-0004Jl-2H for dna-archive@lists.ietf.org; Tue, 08 Aug 2006 21:16:32 -0400 Received: from alpha1.its.monash.edu.au ([130.194.1.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GAcgP-0000DD-0f for dna-archive@lists.ietf.org; Tue, 08 Aug 2006 21:16:32 -0400 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M5SBBI3Q0M8XNN0M@vaxc.its.monash.edu.au> for dna-archive@lists.ietf.org; Wed, 09 Aug 2006 11:14:00 +1000 Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 2B72CAB547; Wed, 09 Aug 2006 11:13:48 +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 DB4764FB07; Wed, 09 Aug 2006 11:13:47 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k79173810441 for dna-list; Wed, 09 Aug 2006 11:07:03 +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 k79172u10437 for ; Wed, 09 Aug 2006 11:07:02 +1000 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M5SB2X3Q5U8XNN0M@vaxc.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed, 09 Aug 2006 11:06:57 +1000 Received: by localhost (Postfix, from userid 510) id 19A89AB545; Wed, 09 Aug 2006 11:06:57 +1000 (EST) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by curly.its.monash.edu.au (Postfix) with ESMTP id 338184FB02 for ; Wed, 09 Aug 2006 11:06:55 +1000 (EST) Received: by nf-out-0910.google.com with SMTP id a4so32835nfc for ; Tue, 08 Aug 2006 18:06:53 -0700 (PDT) Received: by 10.78.117.10 with SMTP id p10mr88182huc; Tue, 08 Aug 2006 18:06:53 -0700 (PDT) Received: by 10.78.196.17 with HTTP; Tue, 08 Aug 2006 18:06:52 -0700 (PDT) Date: Wed, 09 Aug 2006 10:06:52 +0900 From: JinHyeock Choi Subject: Re: [DNA] Document merger: next steps. In-reply-to: <44D11240.30706@research.panasonic.com> Sender: owner-dna@ecselists.eng.monash.edu.au To: Greg Daley Cc: Dna Message-id: <92e919fb0608081806h829aac4r928a3c47baf0f76b@mail.gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT Content-disposition: inline DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gcIApc1VO8xzk3wSdpaCHQZBbG2WT4oE85u+oA5jEXLhdV/tComXXagLXiFxxz/pJusN1cEr6PEwhrcRtbhOxti8MtpR7ze7pwrQbBkqUavT+de5Bd0huQe03MAQWwqfLUM5fTRQiiHqa2TF6UT79jcbOk9+rNH8lPc+ZKXwcTo= X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: References: <44D11240.30706@research.panasonic.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Dear Greg Thanks for your work. > SUGGESTED ACTIONS: > > > 1. Design the relationship between text sources for > Host side operations (following JinHyeock's plan). > (Subsection by subsection (not specific text)). > > 2. Formalize the Table of Contents for the combined > document. > > 3. Merge (router side) Tentative Options into the > (router side) protocol document. > > 4. Identify if text from existing documents is close > to what is needed for each subsection. > > 5. Generate a task list of sub-sections which need > (b) editing from existing sources > (c) merger of multiple sources > (d) complete rewrite > (e) further consultation/issue resolution. > > I'm assuming that all sections need to be modified, > and may then be placed in a category: (a) accepted text. > > > Once we have an idea of which class each subsection goes in, > we can make efforts to generate text for a new draft. > > Does this make sense? yes. I think the above is good enough that we can start working on THE ONLY draft. :-) Especially, if we do the #2 right, i.e. organize ToC in a good way from the start, I guess the rest will be much easier. Thanks for your kind consideration. Best Regards JinHyeock From dna-owner@webcamserver.eng.monash.edu.au Fri Aug 11 07:55:58 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GBVcM-00056w-Ep for dna-archive@lists.ietf.org; Fri, 11 Aug 2006 07:55:58 -0400 Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GBVE5-0002tC-Tj for dna-archive@lists.ietf.org; Fri, 11 Aug 2006 07:30:56 -0400 Received: from larry.its.monash.edu.au ([130.194.13.82]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M5VPBKK6048WYM3G@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Fri, 11 Aug 2006 21:27:10 +1000 Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id DEE8A80004; Fri, 11 Aug 2006 21:27:05 +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 984433C003; Fri, 11 Aug 2006 21:27:05 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k7BBOx717123 for dna-list; Fri, 11 Aug 2006 21:24: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 k7BBOtu17119 for ; Fri, 11 Aug 2006 21:24:55 +1000 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M5VP8REUFW8WYM3G@vaxh.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Fri, 11 Aug 2006 21:24:50 +1000 Received: by localhost (Postfix, from userid 510) id 13717AB542; Fri, 11 Aug 2006 21:24:50 +1000 (EST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by curly.its.monash.edu.au (Postfix) with ESMTP id 3A4094FB0B for ; Fri, 11 Aug 2006 21:24:49 +1000 (EST) Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 32E6389873; Fri, 11 Aug 2006 14:24:44 +0300 (EEST) Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id DD9328986D; Fri, 11 Aug 2006 14:24:43 +0300 (EEST) Date: Fri, 11 Aug 2006 14:24:30 +0300 From: Jari Arkko Subject: Re: [DNA] QUESTION: Remove Link Down information in draft-ietf-dna-link-information-03 In-reply-to: Sender: owner-dna@ecselists.eng.monash.edu.au To: Bernard Aboba , alper.yegin@yegin.org, gregd@research.panasonic.com, kempf@docomolabs-usa.com Cc: dna@eng.monash.edu.au Message-id: <44DC68EE.6090605@piuha.net> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-Virus-Scanned: ClamAV using ClamSMTP References: <32313484.1153464145799.JavaMail.root@dapmg001.ext.nokia.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 I'm late in responding to this thread (due to a vacation), but original question was whether there's an objection to removing the link down indication from the DNA document. To answer that question we do not need to conclude that link down is harmful, fundamentally different, or hopelessly broken. All we need to know is that it is not currently needed by the DNA mechanisms and that it has some potential issues in some situations. Also, the use, security, and other aspects of such indications are highly dependent on what application you have in mind for them. As a result, I would strongly urge that we do not include link down in the document at this time. Lets conclude this discussion, make the changes, ship the document, and move on. --Jari From dna-owner@webcamserver.eng.monash.edu.au Wed Aug 23 10:18:27 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GFtYp-0003Ql-6J for dna-archive@lists.ietf.org; Wed, 23 Aug 2006 10:18:27 -0400 Received: from alpha8.its.monash.edu.au ([130.194.1.8]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GFtYh-0004WF-BR for dna-archive@lists.ietf.org; Wed, 23 Aug 2006 10:18:27 -0400 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M6CMR9RG928WW0NU@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Thu, 24 Aug 2006 00:17:09 +1000 Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 5609BAB542; Thu, 24 Aug 2006 00:17:05 +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 120AD4FB0C; Thu, 24 Aug 2006 00:17:05 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k7NEEum11401 for dna-list; Thu, 24 Aug 2006 00:14:56 +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 k7NEEtu11397 for ; Thu, 24 Aug 2006 00:14:55 +1000 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M6CMOJVF0W8WW0NR@vaxh.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu, 24 Aug 2006 00:14:44 +1000 Received: by localhost (Postfix, from userid 510) id 7B372AB542; Thu, 24 Aug 2006 00:14:44 +1000 (EST) Received: from imr2.ericy.com (imr2.ericy.com [198.24.6.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by moe.its.monash.edu.au (Postfix) with ESMTP id 311A64FB0A for ; Thu, 24 Aug 2006 00:14:43 +1000 (EST) Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id k7NEU6ON013336 for ; Wed, 23 Aug 2006 09:30:07 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Aug 2006 09:14:38 -0500 Received: from [142.133.10.140] ([142.133.10.140]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 Aug 2006 09:14:38 -0500 Date: Wed, 23 Aug 2006 10:16:29 -0400 From: Suresh Krishnan Subject: [DNA] Removal of link down from link info Sender: owner-dna@ecselists.eng.monash.edu.au To: Dna Message-id: <44EC633D.2080803@ericsson.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 1.5 (X11/20060313) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-OriginalArrivalTime: 23 Aug 2006 14:14:38.0545 (UTC) FILETIME=[77F7C410:01C6C6BE] X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Hi Folks, We had asked the wg if it would be ok to remove the link down indications from the link information draft. We did receive a few opinions to remove it from the draft and a few to keep it in the draft since 802.21 was working on it. The fact remains that this information is not used by the dna solution and hence dispensable. Since keeping the information in the draft and trying to secure it is likely to take a long time, we think it is a better idea to remove this information for now. If this information is later required by any other wg, we can revisit the issue. Thanks Suresh and Greg From dna-owner@webcamserver.eng.monash.edu.au Fri Aug 25 14:53:43 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGgoJ-00087I-Oj for dna-archive@lists.ietf.org; Fri, 25 Aug 2006 14:53:43 -0400 Received: from alpha6.its.monash.edu.au ([130.194.1.25]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GGgoI-0004Z9-0E for dna-archive@lists.ietf.org; Fri, 25 Aug 2006 14:53:43 -0400 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M6FOZOWC7M8XQS7U@vaxc.its.monash.edu.au> for dna-archive@lists.ietf.org; Sat, 26 Aug 2006 04:53:32 +1000 Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id BF0F2AB543; Sat, 26 Aug 2006 04:53:21 +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 775504FB04; Sat, 26 Aug 2006 04:53:21 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k7PIqer12332 for dna-list; Sat, 26 Aug 2006 04:52:40 +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 k7PIqcu12328 for ; Sat, 26 Aug 2006 04:52:38 +1000 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M6FOYN0OJG8ZHLC4@vaxc.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat, 26 Aug 2006 04:52:32 +1000 Received: by localhost (Postfix, from userid 510) id 1B56EAB542; Sat, 26 Aug 2006 04:52:32 +1000 (EST) Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by curly.its.monash.edu.au (Postfix) with ESMTP id EBAA74FB05 for ; Sat, 26 Aug 2006 04:52:30 +1000 (EST) Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e35.co.us.ibm.com (8.13.8/8.12.11) with ESMTP id k7PIqPfs022383 for ; Fri, 25 Aug 2006 14:52:25 -0400 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay04.boulder.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k7PIqOp9241404 for ; Fri, 25 Aug 2006 12:52:25 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k7PIqObF014072 for ; Fri, 25 Aug 2006 12:52:24 -0600 Received: from cichlid.raleigh.ibm.com (sig-9-76-134-149.mts.ibm.com [9.76.134.149]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k7PIqNJL013992; Fri, 25 Aug 2006 12:52:24 -0600 Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.13.7/8.12.5) with ESMTP id k7PIqAYa003439; Fri, 25 Aug 2006 14:52:15 -0400 Date: Fri, 25 Aug 2006 14:52:10 -0400 From: Thomas Narten Subject: Re: [DNA] REVIEW of draft-ietf-dna-network In-reply-to: <44EF2E9D.8010009@enst-bretagne.fr> Sender: owner-dna@ecselists.eng.monash.edu.au To: Nicolas Montavont Cc: john.loughney@nokia.com, dna@eng.monash.edu.au, gregd@research.panasonic.com, Sathya Narayanan , Julien Laganier Message-id: <200608251852.k7PIqAYa003439@cichlid.raleigh.ibm.com> MIME-version: 1.0 Content-type: TEXT/PLAIN Content-transfer-encoding: 7BIT X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: References: <44EF2E9D.8010009@enst-bretagne.fr> Comments: In-reply-to Nicolas Montavont message dated "Fri, 25 Aug 2006 19:08:45 +0200." X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa > We'll send a new version of the document in few days, just the time to > check with you if you have other concern / suggestions. Going back through some older mail, I see that this thread started as: > From: Suresh Krishnan > To: Dna > Cc: Greg Daley > Date: Tue, 04 Jul 2006 18:25:50 -0400 > Subject: [DNA] REVIEWS NEEDED: draft-ietf-dna-network > Reply-to: suresh.krishnan@ericsson.com > Hi Folks, > The DNA routers draft (renamed to draft-ietf-dna-network-00) is ready > to be last called before being sent to the IESG for publication. Please > take some time to read the draft and respond to the mailing list with > your reviews. > Thanks > Suresh & Greg Just skimming this document quickly, I'm immediately wondering how it relates to the other dna documents, and the "merged" document in particular. The introduction includes: It should be noted that many already deployed routers will not support these recommendations, and that hosts SHOULD NOT rely on their being in place, unless they have particular reason to do so. This to me implies that this document actual defines changes. But I thought that is what the other "merged" document was doing. So I'm immediately confused about how this document relates to the merged one. I'd suggest that we suspend work on this document until the merged document is available. IMO, it's not possible to properly review this document without knowing what is in the other document and how to scope the topic of this one. (Indeed, I continue to wonder why there is a need for multiple documents in this space at all, but that's a separate discussion). Chairs, could we temporarily suspend work on this document (and not forward it to the IESG) until the other document is available and both can be reviewed together? Thomas From dna-owner@webcamserver.eng.monash.edu.au Fri Aug 25 15:30:40 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GGhO4-00015E-NW for dna-archive@lists.ietf.org; Fri, 25 Aug 2006 15:30:40 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GGfVq-0005kD-5g for dna-archive@lists.ietf.org; Fri, 25 Aug 2006 13:30:34 -0400 Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GGfLe-0001jn-Sh for dna-archive@lists.ietf.org; Fri, 25 Aug 2006 13:20:07 -0400 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M6FLP1J4Y08Y5EWF@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Sat, 26 Aug 2006 03:19:18 +1000 Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 214BEAB543; Sat, 26 Aug 2006 03:19: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 CCA094FB05; Sat, 26 Aug 2006 03:19:15 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k7PHEbM11055 for dna-list; Sat, 26 Aug 2006 03:14:37 +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 k7PHEZu11051 for ; Sat, 26 Aug 2006 03:14:35 +1000 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M6FLIWTRDY8ZHPI9@vaxc.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat, 26 Aug 2006 03:14:20 +1000 Received: by localhost (Postfix, from userid 510) id 986C2AB542; Sat, 26 Aug 2006 03:14:19 +1000 (EST) Received: from laposte.rennes.enst-bretagne.fr (laposte.rennes.enst-bretagne.fr [192.44.77.17]) by moe.its.monash.edu.au (Postfix) with ESMTP id 5B17F4FB02 for ; Sat, 26 Aug 2006 03:14:18 +1000 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.10.03) with ESMTP id k7PHEEuc013807; Fri, 25 Aug 2006 19:14:14 +0200 Received: from l1.rennes.enst-bretagne.fr (l1.rennes.enst-bretagne.fr [192.44.77.3]) by laposte.rennes.enst-bretagne.fr (8.13.4/8.13.4/2004.09.01) with ESMTP id k7PHEAnB013802; Fri, 25 Aug 2006 19:14:10 +0200 Received: from [192.44.77.137] (nik [192.44.77.137]) (authenticated bits=0) by l1.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id k7PHE8ve019874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Aug 2006 19:14:09 +0200 Date: Fri, 25 Aug 2006 19:08:45 +0200 From: Nicolas Montavont Subject: Re: [DNA] REVIEW of draft-ietf-dna-network In-reply-to: Sender: owner-dna@ecselists.eng.monash.edu.au To: john.loughney@nokia.com Cc: dna@eng.monash.edu.au, gregd@research.panasonic.com, Sathya Narayanan , Julien Laganier Message-id: <44EF2E9D.8010009@enst-bretagne.fr> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060725) X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-Virus-Scanned: amavisd-new at enst-bretagne.fr References: X-Spam-Score: -2.3 (--) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Dear John and Julien, Thank you very much for your comments on the routers BCP. Find inline some other comments. We'll send a new version of the document in few days, just the time to check with you if you have other concern / suggestions. john.loughney@nokia.com wrote: [skip] >3) Also: > > Such hosts need to determine if they have moved to a new IPv6 link > rapidly, ... > >As the attachment is fairly binary, I don't think that the movement can >be >rapid, but it is more that the rate of change in re-attaching to >different >links may be rapid or not. I think this should be re-worded. > > You're right, but here we wanted to say that the determination of the link (re) attachment must be quite rapid. We replaced with Julien's suggestion. >5) Question on this definition: > > Reachability Detection: Determination that a device (such as a > router) is currently reachable, over both a wireless medium, and > any attached fixed network. This is typically achieved using > Neighbor Unreachability Detection procedure [1]. > >Is there a reason why it must be both wireless and wired? Could you >have >only wireless links on the router? I think reachability detection >doesn't >specifically require such a configuration. > > This is right. We just wanted to have some detail, and say that if the node is connected to an AP (through wireless), which AP is connected to the AR (through wire), both links should be working. Anyway, this might be obvious, so we remove "over both a wireless medium, and any attached fixed network." >9) Appendicies are always non-normative in RFCs, I assume this document >is meant >to be informational, so maybe it is a non-issue. I found that having the >recommendations >as a non-normative appendicies is a little strange. I think it might >make sense if >this were in the body of the text. > > We had them in the body of the text in the begining and then decided to move it because of some feedback we recieved. Somebody thought that the information is a little too much detail and better off in the appendix. We could move it back in, if more people thought that it is better. >John > > And comments from Julien: Julien Laganier wrote: >On Wednesday 05 July 2006 00:25, Suresh Krishnan wrote: > > [skip] >> >> Link-Change: Link-Change occurs when a host moves from a >> point-of-attachment on a link, to another point-of-attachment >> where it is unable to reach devices belonging to the previous >> link, without being forwarded through a router. >> >> > >Why not simply have: > > Link-Change: Link-Change occurs when a host moves from a > point-of-attachment on a given link to another > point-of-attachment on a different link. > > Your decription makes it sounds like there will be link-change every time you change AP - thats not true - only if change needs a new router to forward data to the old link. Our text is more precise in that sense, isn't it? > > >> When a host solicits and attempts to schedule a multicast RA >> >> > >=> When a host solicits and the router attempts to schedule a > multicast RA > > Our formulation seems good: it is indirectly that the host intends to schedule a RA. >>[...] >> >>5.1 Providing Router Authorization >> >> In DNA, some hosts will begin configuration procedures based on a >> single message transmitted by a router. As such the ability of >> routing infrastructure to prove its authenticity and authorization >> is important to support correct operation of hosts. Authentication >> and authorization mechanisms exist which allow hosts to check >> security of routers when they receive Router Advertisements >> indicating link change. >> >> > >The mechanisms mentionned above are SEND, or there are others? If this >is SEND only I suggest citing SEND here, by e.g. rephrasing as: > > In DNA, some hosts will begin configuration procedures based on a > single message transmitted by a router. As such the ability of > routing infrastructure to prove its authenticity and authorization > is important to support correct operation of hosts. Secure > Neighbor Discovery (SEND) [4] defines authentication and > authorization mechanisms which allow hosts to check security of > routers when they receive Router Advertisements indicating link > change. > > We don't want to be too specific, and we don't believe that we loose anything by not mentionning SEND here. Just in case someting else shows up >That's it. > >Best, > >--julien > > > Nicolas, Sathya and Greg. From dna-owner@webcamserver.eng.monash.edu.au Wed Aug 30 15:53:05 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GIW7V-0006U5-Tf for dna-archive@lists.ietf.org; Wed, 30 Aug 2006 15:53:05 -0400 Received: from alpha1.its.monash.edu.au ([130.194.1.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GIW7T-00085t-Tp for dna-archive@lists.ietf.org; Wed, 30 Aug 2006 15:53:05 -0400 Received: from larry.its.monash.edu.au ([130.194.13.82]) by vaxc.its.monash.edu.au (PMDF V6.1 #31276) with ESMTP id <01M6MQILP8M28ZI9PO@vaxc.its.monash.edu.au> for dna-archive@lists.ietf.org; Thu, 31 Aug 2006 05:52:30 +1000 Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 36DB780003; Thu, 31 Aug 2006 05:52:23 +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 D79CF3C01D; Thu, 31 Aug 2006 05:52:22 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k7UJoDn27183 for dna-list; Thu, 31 Aug 2006 05:50:13 +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 k7UJoDu27179 for ; Thu, 31 Aug 2006 05:50:13 +1000 Received: from larry.its.monash.edu.au ([130.194.13.82]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M6MQFTBYJM8Y64SA@vaxh.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu, 31 Aug 2006 05:50:09 +1000 Received: by localhost (Postfix, from userid 510) id 02DDF80002; Thu, 31 Aug 2006 05:50:08 +1000 (EST) Received: from ns0.neustar.com (ns0.neustar.com [156.154.16.158]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by larry.its.monash.edu.au (Postfix) with ESMTP id B1C7F3C01A for ; Thu, 31 Aug 2006 05:50:07 +1000 (EST) Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id DEEB93290C; Wed, 30 Aug 2006 19:50:01 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1GIW4X-0003gj-P0; Wed, 30 Aug 2006 15:50:01 -0400 Date: Wed, 30 Aug 2006 15:50:01 -0400 From: Internet-Drafts@ietf.org Subject: [DNA] I-D ACTION:draft-ietf-dna-frd-02.txt Sender: owner-dna@ecselists.eng.monash.edu.au To: i-d-announce@ietf.org Cc: dna@eng.monash.edu.au Message-id: MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_gANgJhVwRLLzSz9zKYUbhw)" X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: X-Spam-Score: 0.2 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 --Boundary_(ID_gANgJhVwRLLzSz9zKYUbhw) 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 : Fast Router Discovery with L2 support Author(s) : J. Choi, et al. Filename : draft-ietf-dna-frd-02.txt Pages : 20 Date : 2006-8-30 For efficient Detecting Network Attachment (DNA), a host should quickly receive a Router Advertisement (RA) message upon a new link- layer connection. This draft presents a quick RA acquisition scheme with the support of a link-layer entity, Point of Attachment (PoA). Upon a new network attachment, the PoA may either trigger an Access Router (AR) to immediately send an unicast RA, "RA Triggering" or send such an RA for itself, "RA Proxying". We may put "RA Triggering" or "RA Proxying" functionality on a PoA to get the optimized result without IPv6 standard change. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dna-frd-02.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-frd-02.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-frd-02.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_gANgJhVwRLLzSz9zKYUbhw) Content-type: multipart/alternative; boundary="Boundary_(ID_AR39s3nChK9P+CV72ZQHdg)" --Boundary_(ID_AR39s3nChK9P+CV72ZQHdg) Content-type: Message/External-body; access-type=mail-server; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-8-30133154.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dna-frd-02.txt --Boundary_(ID_AR39s3nChK9P+CV72ZQHdg) Content-type: Message/External-body; name=draft-ietf-dna-frd-02.txt; site=ftp.ietf.org; access-type=anon-ftp; directory=internet-drafts Content-disposition: attachment; filename=draft-ietf-dna-frd-02.txt Content-Type: text/plain Content-ID: <2006-8-30133154.I-D@ietf.org> --Boundary_(ID_AR39s3nChK9P+CV72ZQHdg)-- --Boundary_(ID_gANgJhVwRLLzSz9zKYUbhw)-- From dna-owner@webcamserver.eng.monash.edu.au Thu Aug 31 09:07:56 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GImGy-0007wY-Fx for dna-archive@lists.ietf.org; Thu, 31 Aug 2006 09:07:56 -0400 Received: from alpha9.its.monash.edu.au ([130.194.1.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GImGw-0004Ec-H6 for dna-archive@lists.ietf.org; Thu, 31 Aug 2006 09:07:56 -0400 Received: from moe.its.monash.edu.au ([130.194.13.88]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M6NQJTR0DK8WW71K@vaxh.its.monash.edu.au> for dna-archive@lists.ietf.org; Thu, 31 Aug 2006 23:04:13 +1000 Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 9BAFEAB543; Thu, 31 Aug 2006 23:04:10 +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 520184FB04; Thu, 31 Aug 2006 23:04:10 +1000 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id k7VCvQ505707 for dna-list; Thu, 31 Aug 2006 22:57:26 +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 k7VCvKu05703 for ; Thu, 31 Aug 2006 22:57:20 +1000 Received: from curly.its.monash.edu.au ([130.194.13.87]) by vaxh.its.monash.edu.au (PMDF V6.2-1x9 #31276) with ESMTP id <01M6NQBB19BE8WW9F5@vaxh.its.monash.edu.au> for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Thu, 31 Aug 2006 22:57:18 +1000 Received: by localhost (Postfix, from userid 510) id 8093BAB543; Thu, 31 Aug 2006 22:57:18 +1000 (EST) Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by curly.its.monash.edu.au (Postfix) with ESMTP id A836A4FB09 for ; Thu, 31 Aug 2006 22:57:15 +1000 (EST) Received: from [192.168.1.103] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 44F4DE1600174E80; Thu, 31 Aug 2006 14:56:32 +0200 Date: Thu, 31 Aug 2006 14:56:52 +0200 From: Julien Laganier Subject: Re: [DNA] REVIEW of draft-ietf-dna-network In-reply-to: <44EF2E9D.8010009@enst-bretagne.fr> Sender: owner-dna@ecselists.eng.monash.edu.au To: Nicolas Montavont Cc: dna@eng.monash.edu.au, gregd@research.panasonic.com, Sathya Narayanan Message-id: <200608311456.52762.julien.IETF@laposte.net> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.8.2 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) X-Spam-Level: References: <44EF2E9D.8010009@enst-bretagne.fr> X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Hi Nicolas, On Friday 25 August 2006 19:08, Nicolas Montavont wrote: > Dear John and Julien, > > Thank you very much for your comments on the routers BCP. > Find inline some other comments. Some more comments below... > And comments from Julien: > > Julien Laganier wrote: > > >> Link-Change: Link-Change occurs when a host moves from a > >> point-of-attachment on a link, to another > >> point-of-attachment where it is unable to reach devices > >> belonging to the previous link, without being forwarded through > >> a router. > > > >Why not simply have: > > > > Link-Change: Link-Change occurs when a host moves from a > > point-of-attachment on a given link to another > > point-of-attachment on a different link. > > Your decription makes it sounds like there will be link-change > every time you change AP - thats not true - only if change needs a > new router to forward data to the old link. Our text is more > precise in that sense, isn't it? Well, as I read my description it says that a link change occurs when the node attach to a *different* link, it doesn't says anything about changing APs. From an IP point of view if you change APs but stay in the same DS under one router then you're still on the same link. But anyway that's not so important. > >> When a host solicits and attempts to schedule a multicast RA > > > >=> When a host solicits and the router attempts to schedule a > > multicast RA > > Our formulation seems good: it is indirectly that the host intends > to schedule a RA. Ok I got it. It might be clearer if explicitly written down: "When a host solicits and attempts to make the router schedule a multicast RA" Thanks. --julien