From dna-owner@webcamserver.eng.monash.edu.au Fri Mar 02 12:41:00 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HNBka-00081Y-1v for dna-archive@lists.ietf.org; Fri, 02 Mar 2007 12:41:00 -0500 Received: from stan.its.monash.edu.au ([130.194.13.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HNBkX-0008QM-SX for dna-archive@lists.ietf.org; Fri, 02 Mar 2007 12:41:00 -0500 Received: from larry.its.monash.edu.au ([130.194.13.82]) by stan.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JEA00CWMEG22790@stan.its.monash.edu.au> for dna-archive@lists.ietf.org; Sat, 03 Mar 2007 04:40:50 +1100 (EST) Received: from larry.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id C4F3C80002; Sat, 03 Mar 2007 04:40:49 +1100 (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 9F1563C008; Sat, 03 Mar 2007 04:40:47 +1100 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id l22Hcgf22265 for dna-list; Sat, 03 Mar 2007 04:38:42 +1100 Received: from kyle.its.monash.edu.au (kyle.its.monash.edu.au [130.194.13.163]) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) with ESMTP id l22Hcgs22261 for ; Sat, 03 Mar 2007 04:38:42 +1100 Received: from larry.its.monash.edu.au ([130.194.13.82]) by kyle.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) id <0JEA00901C59EA00@kyle.its.monash.edu.au> (original mail from sathya@research.panasonic.com) for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat, 03 Mar 2007 04:38:42 +1100 (EST) Received: from larry.its.monash.edu.au ([130.194.13.82]) by kyle.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JEA005SSECHCE90@kyle.its.monash.edu.au> for dna@eng.monash.edu.au; Sat, 03 Mar 2007 04:38:42 +1100 (EST) Received: by localhost (Postfix, from userid 510) id D28B680003; Sat, 03 Mar 2007 04:38:42 +1100 (EST) Received: from oak.research.panasonic.com (oak.Research.Panasonic.COM [150.169.1.4]) by larry.its.monash.edu.au (Postfix) with ESMTP id C6ED43C019 for ; Sat, 03 Mar 2007 04:38:40 +1100 (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 l22Ha31o030677 for ; Fri, 02 Mar 2007 12:38:35 -0500 Received: from [150.169.17.2] ([150.169.17.2]) by redwood.research.panasonic.com (MOS 3.8.3-GA) with ESMTP id ATL33888; Fri, 02 Mar 2007 12:39:52 -0500 (EST) Date: Fri, 02 Mar 2007 12:38:39 -0500 From: Sathya Narayanan Subject: Re: [DNA] Re: Flash renumbering In-reply-to: <42E63B2A.20800@sun.com> Sender: owner-dna@ecselists.eng.monash.edu.au To: Dna Message-id: <45E8611F.5090106@Research.Panasonic.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 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) References: <1ed7c20f5b.20f5b1ed7c@pintlmail.MITL.Research.Panasonic.COM> <"42 E5AB7E.6020803"@sun.com> <42E5B15B.7060609@Research.Panasonic.COM> <42E63B2A.20800@sun.com> User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Spam-Level: X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Based on Thomas's comments, I am looking at the sections 5.1.10, 5.1.11 in -04 and section 12 (RENUMBERING CONSIDERATIONS) in RFC 2461. This is related to flash renumbering which we discussed within the DT and on the mailing list long time ago. Section 12 in RFC 2461 doesn't have any explicit statements on what is allowed and what is not - the discussion is about deprecating a prefix by advertising it with shorter and shorter lifetime and advertising the prefix with zero lifetime until its original valid lifetime expires. Now, I am quoting from Erik's email below: "I guess we need to first agree what goals we are trying to satisfy. I see three possible levels: 1. do nothing special for flash renumbering and immediate reassignment (other than telling network admin to not immediately reassign prefixes) 2. do something so that a host can recover, but it might take a while (e.g., 90 minutes) 3. handle it without any delay " The text in 5.1.10 itself can be improved - but I want to make sure that our goal is to do 3, i.e., even though it is recommended that network adminstrators NOT do flash renumbering, we still recommend behavior for the routers to "handle it without any delay". Please comment. - Sathya Erik Nordmark wrote: > Sathya Narayanan wrote: > >>> Based on the comment above, we would also have to forbid the routers >>> from using learned prefixes as part of the DNA solution. >> >> >> >> ... why? The problems becomes worse with wrong state for upto 7 days >> only with reassignment. The above comment is only about flash >> renumbering which will be corrected within 90 minutes and is not that >> bad (A) > > > I guess we need to first agree what goals we are trying to satisfy. I > see three possible levels: > 1. do nothing special for flash renumbering and immediate reassignment > (other than telling network admin to not immediately reassign prefixes) > 2. do something so that a host can recover, but it might take a while > (e.g., 90 minutes) > 3. handle it without any delay > > Which goal are you attempting for? (And we should ask the same of the > whole WG.) > > I was assuming you were trying for #3, since in some cases you'd > recover in zero time. But in order to accomplish #3 we'd also have to > remove any notion of using learned prefixes in the routers. > > And if we want to reach #2 then I don't think we need to affect the > efficiency of the normal DNA operations, but instead have some slower > sanity check which can recover. > >> By suggesting that this is suspicious, we are suggesting that the >> prefix-lifetime being greater than 90 minutes is not necessarily right - >> in effect putting an upper limit on the prefix-lifetime and overruling >> 2461. Right? Is it OK to do that? > > > Good question. I wish I had a firm answer. We have an inherent > conflict between RFC 2461, which was designed we long default > lifetimes just so that a host wouldn't throw away its addresses and > prefixes just because a router died for a short time. > > But our need to quickly and reliably detect movement, if we combine it > with the renumbering and reassignment issue, is in conflict. We can't > solve both. > > Hence the best I think we can do is to use the absence of a 'link up' > as a way to tell the host to stay in the RFC 2461/62 "stability is > important" mode. > > Note that your suggestion to use a RS to reverify each prefix has the > same issue as triggering a sanity check after 90 minutes, since it > would also remove a prefix from aggressively than 2461 if the > advertising router is temporarily down. > >> In support of my argument above marked (A), this solution doesn't >> address the flash renumbering problem - only flash renumbering with >> early reassignment. But, I do agree that this simpler defensive >> scheme can handle the low-probability occurance of flash-renumbering >> with early >> reassignment. > > > Flash renumbering without any reassignment wouldn't cause any > additional problems for DNA, would it? I think it is only an > issue/feature of RFC 2461/62. > > Erik > From dna-owner@webcamserver.eng.monash.edu.au Tue Mar 06 15:52:07 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOgdj-0007ir-Uf for dna-archive@lists.ietf.org; Tue, 06 Mar 2007 15:52:07 -0500 Received: from kenny.its.monash.edu.au ([130.194.13.164]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOgdh-0003Ni-Hj for dna-archive@lists.ietf.org; Tue, 06 Mar 2007 15:52:07 -0500 Received: from curly.its.monash.edu.au ([130.194.13.87]) by kenny.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JEI00KF11YMM270@kenny.its.monash.edu.au> for dna-archive@lists.ietf.org; Wed, 07 Mar 2007 07:51:59 +1100 (EST) Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id ABA2FAB544; Wed, 07 Mar 2007 07:51:57 +1100 (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 DA8A94FB04; Wed, 07 Mar 2007 07:51:55 +1100 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id l26KoCx15767 for dna-list; Wed, 07 Mar 2007 07:50:12 +1100 Received: from kyle.its.monash.edu.au (kyle.its.monash.edu.au [130.194.13.163]) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) with ESMTP id l26KoCs15763 for ; Wed, 07 Mar 2007 07:50:12 +1100 Received: from moe.its.monash.edu.au ([130.194.13.88]) by kyle.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) id <0JEH00K01Z7ACN00@kyle.its.monash.edu.au> (original mail from ietf@ietf.org) for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Wed, 07 Mar 2007 07:50:12 +1100 (EST) Received: from moe.its.monash.edu.au ([130.194.13.88]) by kyle.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JEI00HNC1VM8370@kyle.its.monash.edu.au> for dna@eng.monash.edu.au; Wed, 07 Mar 2007 07:50:12 +1100 (EST) Received: by localhost (Postfix, from userid 510) id 88A86AB543; Wed, 07 Mar 2007 07:50:12 +1100 (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 moe.its.monash.edu.au (Postfix) with ESMTP id 419734FB02 for ; Wed, 07 Mar 2007 07:50:07 +1100 (EST) Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 0309332A6D; Tue, 06 Mar 2007 20:50:03 +0000 (GMT) Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1HOgbi-00065Y-SD; Tue, 06 Mar 2007 15:50:02 -0500 Date: Tue, 06 Mar 2007 15:50:02 -0500 From: Internet-Drafts@ietf.org Subject: [DNA] I-D ACTION:draft-ietf-dna-protocol-05.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=NextPart X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) X-Spam-Level: X-Spam-Score: 0.3 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 --NextPart 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 Networks (DNAv6) Author(s) : J. Kempf Filename : draft-ietf-dna-protocol-05.txt Pages : 51 Date : 2007-3-6 Efficient detection of network attachment in IPv6 needs the following three components: a method for hosts to detect link change in the presence of unmodified (non-DNAv6) routers, a method for the host to query routers on the link to identify the link (Link Identification) and a method for the routers on the link to consistently respond to such a query with minimal delay (Fast RA). Solving the link identification based strictly on RFC 2461 is difficult because of the flexibility offered to routers in terms of prefixes advertised in a router advertisement (RA) message. Similarly, the random delay in responding to router solicitation messages imposed by RFC 2461 makes it difficult to receive an RA quickly. In this memo, a mechanism that requires the hosts to monitor all the prefixes advertised on the link and use it for link identification in the presence of non-DNAv6 routers is presented. A more efficient link-identification mechanism requiring the DNAv6 routers to monitor the link for advertised prefixes to assist the hosts in link identification combined with a fast router advertisement mechanism that selects the order of response for the router deterministicly is also presented. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-dna-protocol-05.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-protocol-05.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-protocol-05.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. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2007-3-6124058.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-dna-protocol-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-dna-protocol-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2007-3-6124058.I-D@ietf.org> --OtherAccess-- --NextPart-- From dna-owner@webcamserver.eng.monash.edu.au Fri Mar 09 16:22:49 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPmY5-0004aP-FY for dna-archive@lists.ietf.org; Fri, 09 Mar 2007 16:22:49 -0500 Received: from cartman.its.monash.edu.au ([130.194.13.166]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPmXy-0007CC-EM for dna-archive@lists.ietf.org; Fri, 09 Mar 2007 16:22:49 -0500 Received: from moe.its.monash.edu.au ([130.194.13.88]) by cartman.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JEN00HTYNDKY3R0@cartman.its.monash.edu.au> for dna-archive@lists.ietf.org; Sat, 10 Mar 2007 08:22:33 +1100 (EST) Received: from moe.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 8AE22AB547; Sat, 10 Mar 2007 08:22:32 +1100 (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 756F94FB05; Sat, 10 Mar 2007 08:22:30 +1100 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id l29LKlL31828 for dna-list; Sat, 10 Mar 2007 08:20:47 +1100 Received: from cartman.its.monash.edu.au (cartman.its.monash.edu.au [130.194.13.166]) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) with ESMTP id l29LKls31824 for ; Sat, 10 Mar 2007 08:20:47 +1100 Received: from moe.its.monash.edu.au ([130.194.13.88]) by cartman.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) id <0JEN00801MV5TV00@cartman.its.monash.edu.au> (original mail from suresh.krishnan@ericsson.com) for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Sat, 10 Mar 2007 08:20:43 +1100 (EST) Received: from moe.its.monash.edu.au ([130.194.13.88]) by cartman.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JEN00HQ4NAJY3R0@cartman.its.monash.edu.au> for dna@eng.monash.edu.au; Sat, 10 Mar 2007 08:20:43 +1100 (EST) Received: by localhost (Postfix, from userid 510) id BEE71AB545; Sat, 10 Mar 2007 08:20:43 +1100 (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 5B83D4FB12 for ; Sat, 10 Mar 2007 08:20:42 +1100 (EST) Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l29Lj9Jd023196 for ; Fri, 09 Mar 2007 15:45:09 -0600 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 09 Mar 2007 15:20:35 -0600 Received: from [142.133.10.140] ([142.133.10.140]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 09 Mar 2007 15:20:35 -0600 Date: Fri, 09 Mar 2007 16:22:37 -0500 From: Suresh Krishnan Subject: [DNA] DNA Protocol Document Sender: owner-dna@ecselists.eng.monash.edu.au To: Dna Message-id: <45F1D01D.7000901@ericsson.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) User-Agent: Thunderbird 1.5 (X11/20060313) X-OriginalArrivalTime: 09 Mar 2007 21:20:35.0898 (UTC) FILETIME=[C720D9A0:01C76290] X-Spam-Level: X-Spam-Score: 0.1 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Hi Folks, The next dna wg meeting is coming up really soon. We have a short (1 hour slot) and the main(sole) item of discussion at the next meeting would be the combined protocol document. The latest version of the protocol document is available at http://www.ietf.org/internet-drafts/draft-ietf-dna-protocol-05.txt Please read the document before the meeting. You can send your comments to the mailing list or raise them at the meeting. If you feel that the document is ready to go, please explicitly indicate so. Thanks Suresh & Greg From dna-owner@webcamserver.eng.monash.edu.au Mon Mar 12 16:49:34 2007 Return-path: Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQrSY-00025s-Hp for dna-archive@lists.ietf.org; Mon, 12 Mar 2007 16:49:34 -0400 Received: from cartman.its.monash.edu.au ([130.194.13.166]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQrSN-0008FQ-8W for dna-archive@lists.ietf.org; Mon, 12 Mar 2007 16:49:34 -0400 Received: from curly.its.monash.edu.au ([130.194.13.87]) by cartman.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JET00AWA5TZFZ00@cartman.its.monash.edu.au> for dna-archive@lists.ietf.org; Tue, 13 Mar 2007 07:49:12 +1100 (EST) Received: from curly.its.monash.edu.au (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 2315AAB544; Tue, 13 Mar 2007 07:49:11 +1100 (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 B62E74FB07; Tue, 13 Mar 2007 07:49:08 +1100 (EST) Received: (from majordomo@localhost) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) id l2CKle818852 for dna-list; Tue, 13 Mar 2007 07:47:40 +1100 Received: from kenny.its.monash.edu.au (kenny.its.monash.edu.au [130.194.13.164]) by webcamserver.eng.monash.edu.au (8.11.6/8.11.0) with ESMTP id l2CKles18848 for ; Tue, 13 Mar 2007 07:47:40 +1100 Received: from moe.its.monash.edu.au ([130.194.13.88]) by kenny.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) id <0JES00201ZT52G00@kenny.its.monash.edu.au> (original mail from jari.arkko@piuha.net) for dna@ecselists.eng.monash.edu.au (ORCPT dna@eng.monash.edu.au); Tue, 13 Mar 2007 07:47:40 +1100 (EST) Received: from moe.its.monash.edu.au ([130.194.13.88]) by kenny.its.monash.edu.au (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTP id <0JET006U85REIG00@kenny.its.monash.edu.au> for dna@eng.monash.edu.au; Tue, 13 Mar 2007 07:47:40 +1100 (EST) Received: by localhost (Postfix, from userid 510) id B0558AB542; Tue, 13 Mar 2007 07:47:40 +1100 (EST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by moe.its.monash.edu.au (Postfix) with ESMTP id 3DCB14FB03 for ; Tue, 13 Mar 2007 07:47:39 +1100 (EST) Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E8FD1198720 for ; Mon, 12 Mar 2007 22:47:33 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id A68EB19871C for ; Mon, 12 Mar 2007 22:47:33 +0200 (EET) Date: Mon, 12 Mar 2007 22:47:35 +0200 From: Jari Arkko Subject: [DNA] Moving forward with draft-ietf-dna-link-information-06.txt In-reply-to: Sender: owner-dna@ecselists.eng.monash.edu.au To: dna@eng.monash.edu.au Message-id: <45F5BC67.2090005@piuha.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) X-Virus-Scanned: ClamAV using ClamSMTP References: User-Agent: Thunderbird 1.5.0.10 (X11/20070306) X-Spam-Level: X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Hi all, I reviewed the revision and went through the IETF Last Call discussion again. I think the new revision corresponds to what was requested during Last Call. We also have confirmation from Bernard that his issues were resolved by the new revision. However, I am not completely satisfied by the way that the issues raised by Thomas and Pekka were addressed. I am taking the draft forward, however. But I have a set of changes below that will go in as RFC Editor notes, or to -07 if the draft needs to be revised for other reasons during IESG review. The changes relate to making sure that the informational nature of the document is clear. Insert a new paragraph between the 2nd and 3rd paragraph of Section 1: OLD: NEW: Link-layer event notifications can help IP expeditiously detect configuration changes. This document provides a non-exhaustive catalog of information available from some access technologies, and discusses the interpretation of this information at the IP layer. This document is not intended to specify or change the behaviour of these access technologies in any manner. Section 3: OLD: notification must be delivered NEW: notification is delivered OLD: notification must be generated and what information must be included in it NEW: notification is generated and what information is included in it Section 3.1: OLD: must generate a link up NEW: generates a link up OLD: notification must be the IPv4 NEW: notification is the IPv4 Section 3.2: OLD: notification must be delivered NEW: notification is delivered OLD: address must be provided NEW: address is provided Section 3.3: OLD: must be generated NEW: is generated OLD: must cause a link up NEW: causes a link up OLD: notification must be generated, if one NEW: notification is generated, if one OLD: notification must be generated. NEW: notification is generated. From mana_kaya@so-net.ne.jp Thu Mar 22 13:30:58 2007 Return-path: Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUR7p-0002oc-Tk for dna-archive@megatron.ietf.org; Thu, 22 Mar 2007 13:30:57 -0400 Received: from [124.234.232.144] (helo=nifty.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HUR7n-0003G9-Lk for dna-archive@megatron.ietf.org; Thu, 22 Mar 2007 13:30:57 -0400 Received: from OhPVr6611p (unknown [126.249.254.18]) by smtp20 with ESMTP id hoK11NHbhlyA604R.1 for ; Fri, 23 Mar 2007 02:31:02 +0800 (CST) X-Originating-IP: [126.249.254.18] Subject: =?iso-2022-jp?B?GyRCTyJNbUBoOHgzKyJ2GyhC?= From: "nakao" To: X-Mailer: Microsoft Outlook Express 6.00.2900.2180 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_06B6_01C7633A.16835FF0" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Spam-Score: 3.3 (+++) X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb This is a multi-part message in MIME format. ------=_NextPart_000_06B6_01C7633A.16835FF0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit SEXしてくれる女性を確実に見つけられます　http://urfb.com/?h238 全て無料で使えるのでお試し下さい /_/_/_/_/_/_/_/_/_/_/_/_/_/ メール不要 saki_honda19@yahoo.fr /_/_/_/_/_/_/_/_/_/_/_/_/_/ ------=_NextPart_000_06B6_01C7633A.16835FF0 Content-Type: text/html; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable
SEX=1B$B$7$F$/$l$k=3Dw@-$r3Nhttp://urfb.com/?h238
=1B$BA4$FL5NA$G;H$($k$N$G$*;n$72<$5$$=1B(B
=
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
/_/_/_/_/_/_/_/_/_/_/_/_/_/
=1B$B%a!<%kITMW=1B(B
saki_honda19@yahoo.fr
/_/_/_/_/_/_/_/_/_/_/_/_/_/
 
 
------=_NextPart_000_06B6_01C7633A.16835FF0--