Re: [Roll] aodv-rpl review
Charlie Perkins <charles.perkins@earthlink.net> Fri, 08 March 2019 01:00 UTC
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521C71310E8; Thu, 7 Mar 2019 17:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nm0_h5ItLhZr; Thu, 7 Mar 2019 17:00:29 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B700413123B; Thu, 7 Mar 2019 17:00:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1552006824; bh=W211nNSt6/9A9QTOjGPNJq/ZF50wEKc2xOvH NMCRG3I=; h=Received:Subject:To:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language: X-ELNK-Trace:X-Originating-IP; b=GCN86bWLiWapAqL3CX05R5oMaOLZni8zz 2FMk7hO78yoIo19sPSBj101voCGf9e4Reu05nEU+vh9lARVH8f02rohiU5LQFtJGgqR QQ00Q1qlnwYIqVW1WpiF7ErkAgA2o4ChQ5wLOnapGmPU5w3zO/E9qvdOv4NglWLTJ+P 81D2L0cauQMd3XlpSgPQwd/dzS10R7gPf4iUmYoqzsETFBmvUx0QxFDVb/WL2o+i9As jEP09l19yGGvx6O3zdD9zX7seVmBd+eO4EMrIvfIBu0zBp1sjSEcpSqC04ChwVyCXAN oDAFgMw56l9K+XZY0199sYr3PX1eUxwFmm5endP0g==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=hL++B0YsKVIyVACXV3CvLYolDZ4m01P2XCZnogWw5q7E3mIr7ONrPC5kOfB+Pn9o/vANL/WCJnEqAAyllM2stAz5CIVuKxClQbbeurlvcI/s9n91KTPCjh4n7ExaGVGHCzYepVNRHutZw59uuCOmVvVbNwLJcbUnB1ih4JDzbIIC2qj/g2mIdA2VPhjbIhDTI0G7nVZKcunTHHCHKIm5a13uCS4kn70f+Z/4hKap+gFQgdWZoNjr4o8BH6VFpqyGtdqAB4zoyKocrf+1O4VF94g0uspEoSEqKF7VpigWyUdHUzS3HSVXy3KSHqVr3lNsJpaZ+DGM0Qphl2g/Pofe8Q==; h=Received:Subject:To:References:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1h23s6-0002s2-PX; Thu, 07 Mar 2019 20:00:22 -0500
To: Peter van der Stok <consultancy@vanderstok.org>, Roll <roll@ietf.org>, Draft-ietf-roll-aodv-rpl <draft-ietf-roll-aodv-rpl@ietf.org>
References: <7e90f9a49be79a88261a3e77bc6e27f7@bbhmail.nl>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <73f19e3d-1cc1-b06f-80e0-9e7c9e10d574@earthlink.net>
Date: Thu, 07 Mar 2019 17:00:18 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <7e90f9a49be79a88261a3e77bc6e27f7@bbhmail.nl>
Content-Type: multipart/alternative; boundary="------------B2A202FB9294794948E213B1"
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95e9b6793e299fe64cbe5e414deed96f82350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/OLIhtUwMGCbMdZc7rZsMiW2MqpY>
Subject: Re: [Roll] aodv-rpl review
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Mar 2019 01:00:32 -0000
Hello Peter, I think our new revision will resolve most or all of your comments. We have greatly expanded the Security Considerations, and added clarifications about the relationship with RFC 6997. I also added some explanation about the difference between "application-specific" versus P2P routing. They are pretty much different and I hope that comes through better. Thanks for all of the suggestions! Regards, Charlie P. On 11/28/2018 1:06 AM, Peter van der Stok wrote: > Hi aodv-rpl co-authors, > > I promised to do a quick review of the document before passing it to > the shepherd. > > The document reads rather smoothly, and seems to be complete. > Question: are there any implementations, and has there been an > interop? I vaguely remember the subject being mentioned, but do not > remember the answer. > > I like the appendix A, it helps enormously to understand the > bidirectional asymmetric link concept. > > Major question: what is the relation with 6997 P2P-RPL. > Does this document replace RFC 6997. To me it seems that in the case > of symmetric links only, AODV-RPL degrades to P2P-RPL. Probably not in > an interoperable way given the different MOP etc. > May be you can explain your ideas in this respect. > RFC 6997 is "experimental" to go to STD when more experience was gained. > Does that also apply to this document, or is there an operational > direct need identified. > > Should 5548, 5673, 5826, 5867 not go to informational; you don't need > them to implement the spec. > > Last but not least: section 10 security Considerations is more than > terse; I am afraid that the security review will judge this > inadequate. You can look what has been done in the npdao draft; but I > cannot guarantee that this is sufficient. > The MANET WG has been active in describing threats in RFC 7985; may be > you can find inspiration there to categorize the problems and identify > the ones applying to AODV-RPL. > > Some minor syntactical things that hit my eye. > > You never write out RPL, although the other acronyms have been honored > as such. > In section 1 the term TargNode appears all of the sudden; suggest to > use Target Node in section 1. > You use application-specific routing and P2P routing; what is the > difference? > section 3: s/established are/are established/ > section 6.1: s/increse/increase/ > s/previous/previously/ > s/increased number/sequence number/ > > Greetings, > and thanks for the work, > > Peter > -- > Peter van der Stok > vanderstok consultancy > mailto: consultancy@vanderstok.org > <mailto:consultancy@vanderstok.org>, stokcons@bbhmail.nl > <mailto:stokcons@bbhmail.nl> > www: www.vanderstok.org <http://www.vanderstok.org> > tel NL: +31(0)492474673 F: +33(0)966015248
- [Roll] aodv-rpl review Peter van der Stok
- Re: [Roll] aodv-rpl review Charlie Perkins