From nobody Mon May 8 02:10:04 2017 Return-Path: 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 6FF491287A3 for ; Mon, 8 May 2017 02:10:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.079 X-Spam-Level: X-Spam-Status: No, score=0.079 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 4W7VcGuS-4h2 for ; Mon, 8 May 2017 02:10:02 -0700 (PDT) Received: from lb3-smtp-cloud6.xs4all.net (lb3-smtp-cloud6.xs4all.net [194.109.24.31]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0BA3126FB3 for ; Mon, 8 May 2017 02:10:01 -0700 (PDT) Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:200]) by smtp-cloud6.xs4all.net with ESMTP id Hl9y1v0095W6tKc01l9y7Q; Mon, 08 May 2017 11:09:58 +0200 Received: from 2001:983:a264:1:dc54:e466:7fb6:5f27 by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 08 May 2017 11:09:58 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 08 May 2017 11:09:58 +0200 From: peter van der Stok To: Roll Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org Message-ID: <3dc1b14e7b812d079f89caa17a1ee509@xs4all.nl> X-Sender: stokcons@xs4all.nl User-Agent: XS4ALL Webmail Archived-At: Subject: [Roll] Roll meeting in Prague X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 09:10:03 -0000 Hi all, During the meeting in Chicago, and also earlier, we were obliged to cut F2F exchanges due to the constrained time resource (1 hour). For Prague, we decided to ask for 2 hours F2F meeting time. We encourage everybody to grasp this opportunity to present their work. For example, I hope we receive more info on the progress of ccast and dis-modif, not present in Chicago. Greetings, Ines + peter -- Peter van der Stok vanderstok consultancy mailto: consultancy@vanderstok.org www: www.vanderstok.org tel NL: +31(0)492474673 F: +33(0)966015248 From nobody Mon May 8 06:02:09 2017 Return-Path: X-Original-To: roll@ietf.org Delivered-To: roll@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF819129465; Mon, 8 May 2017 06:02:07 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: Cc: roll-chairs@ietf.org, aretana@cisco.com, roll@ietf.org, maria.ines.robles@ericsson.com X-Test-IDTracker: no X-IETF-IDTracker: 6.50.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <149424852791.19294.11978512508930523968.idtracker@ietfa.amsl.com> Date: Mon, 08 May 2017 06:02:07 -0700 Archived-At: Subject: [Roll] roll - New Meeting Session Request for IETF 99 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 13:02:08 -0000 A new meeting session request has just been submitted by Ines Robles, a Chair of the roll working group. --------------------------------------------------------- Working Group Name: Routing Over Low power and Lossy networks Area Name: Routing Area Session Requester: Ines Robles Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 50 Conflicts to Avoid: First Priority: 6tisch 6lo manet anima 6man Second Priority: rtgarea t2trg core Third Priority: intarea lwig rtgwg pce ipwave People who must be present: Michael Richardson Peter Van der Stok Alvaro Retana Ines Robles Resources Requested: Special Requests: Meetecho Support --------------------------------------------------------- From nobody Mon May 8 07:24:58 2017 Return-Path: X-Original-To: roll@ietf.org Delivered-To: roll@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB188128961; Mon, 8 May 2017 07:24:56 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: Cc: roll-chairs@ietf.org, aretana@cisco.com, roll@ietf.org, maria.ines.robles@ericsson.com X-Test-IDTracker: no X-IETF-IDTracker: 6.50.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <149425349660.9654.2510390537204429524.idtracker@ietfa.amsl.com> Date: Mon, 08 May 2017 07:24:56 -0700 Archived-At: Subject: [Roll] roll - Update to a Meeting Session Request for IETF 99 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 14:24:57 -0000 An update to a meeting session request has just been submitted by Ines Robles, a Chair of the roll working group. --------------------------------------------------------- Working Group Name: Routing Over Low power and Lossy networks Area Name: Routing Area Session Requester: Ines Robles Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 50 Conflicts to Avoid: First Priority: 6tisch 6lo manet anima 6man core Second Priority: rtgarea t2trg Third Priority: intarea lwig rtgwg pce ipwave People who must be present: Michael Richardson Peter Van der Stok Alvaro Retana Ines Robles Resources Requested: Special Requests: Meetecho Support --------------------------------------------------------- From nobody Mon May 8 07:40:12 2017 Return-Path: X-Original-To: roll@ietf.org Delivered-To: roll@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A65D129405; Mon, 8 May 2017 07:40:09 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: Cc: roll-chairs@ietf.org, aretana@cisco.com, roll@ietf.org, maria.ines.robles@ericsson.com X-Test-IDTracker: no X-IETF-IDTracker: 6.50.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <149425440934.10046.2111873931080500079.idtracker@ietfa.amsl.com> Date: Mon, 08 May 2017 07:40:09 -0700 Archived-At: Subject: [Roll] roll - Update to a Meeting Session Request for IETF 99 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 14:40:09 -0000 An update to a meeting session request has just been submitted by Ines Robles, a Chair of the roll working group. --------------------------------------------------------- Working Group Name: Routing Over Low power and Lossy networks Area Name: Routing Area Session Requester: Ines Robles Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 50 Conflicts to Avoid: First Priority: 6man anima manet 6lo 6tisch core Second Priority: t2trg rtgarea lpwan lwig Third Priority: intarea rtgwg pce ipwave ace People who must be present: Michael Richardson Peter Van der Stok Alvaro Retana Ines Robles Resources Requested: Special Requests: Meetecho Support --------------------------------------------------------- From nobody Wed May 10 09:24:55 2017 Return-Path: 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 27724129C5D for ; Wed, 10 May 2017 09:24:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 EIcr67u5cjnG for ; Wed, 10 May 2017 09:24:53 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35E9B12947B for ; Wed, 10 May 2017 09:24:53 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id DFAF920183 for ; Wed, 10 May 2017 12:51:11 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 186A8636E0 for ; Wed, 10 May 2017 12:24:52 -0400 (EDT) From: Michael Richardson To: roll@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2017 16:24:55 -0000 --=-=-= Content-Type: text/plain It has been suggested that in draft-ietf-roll-useofrplinfo-14 that we change the presentation of the use cases. That instead of having 12 storing and then 12 non-storing cases, that we instead have 12 cases, and within each discuss the non-storing and storing subcases. Doing this involves moving a lot of text around, so before we do this, we'd like to get some rough consensus that this would be a better presentation. Do we need to do the run-through of the Berlin IETF96 slides again at the Prague meeting? https://docs.google.com/presentation/d/1zdjzlLo-gWa1DEug3zQ7aMqWJ3PDM4Hajt-uAOexynA/edit?usp=sharing https://docs.google.com/presentation/d/1zdjzlLo-gWa1DEug3zQ7aMqWJ3PDM4Hajt-uAOexynA/pub?start=false&loop=false&delayms=60000 http://www.sandelman.ca/SSW/ietf/roll/useofrplinfo/ietf96-slides-v1.pdf Given that 2460bis has not given us the desired collapse of the HbH option type as we thought would happen, upon the advice of reviewers and Area Director(s), useofrplinfo will be revised to update RFC6553 to change the HbH type code. Let us get that text ready, and so the WG can react better. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlkTPtMACgkQgItw+93Q 3WX8SAgAhYe4aGphsKhbRA3nPtTkssnj/+dxfUKA/GDW8uw1YzqNypnQNjVNIuGF szUi2pBIEfIBFjXxc3Y45+UkPNYhPjSGetQQ/mCGroCI54UHFmM70rirRRvZQBFW Mf7UTGLWQ/zJ9jfe0EqGoopsN0/8vXtMDivSjSWUx5yw+pusPZE1hEcs/H0niSyH rloZZ1skCAKJMtgHyIIckF+3jn+KRz4UQr9FMINteid+yyO0SkHX7xO/G9BlU3UN Ao1bWXXbQRepgAAxwq9ItA1kJBK56MXSD8mv/ZF1Q6zUlB7EzPp7H4OaOUib33IO rzIUznGcDC4jBEpHqDBtfViE6QhwUw== =dgvB -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed May 10 09:38:46 2017 Return-Path: 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 7AE2912E03A for ; Wed, 10 May 2017 09:38:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=att.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 MV_FsMcBeQ5k for ; Wed, 10 May 2017 09:38:33 -0700 (PDT) Received: from nm11-vm10.access.bullet.mail.bf1.yahoo.com (nm11-vm10.access.bullet.mail.bf1.yahoo.com [216.109.114.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DC7D12E037 for ; Wed, 10 May 2017 09:38:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1494434311; bh=n2Q+8mOnx8PgEaq41zHZLmcZmMlwXAoiArnlPkoySB8=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=VSQbbbmeuAsyn+BYE3tZ6UghlJJFhyPxmixFQMP1xFCbr/IWYKj+aWGaoT/tBjuM0CZpTAvWaBCAFJnSNrMZQJ7TGTRXO2ZpqAfO21s+Jo1Ufh/WYOyV4vkMvy8BiDEDvCru8Yty9UgaYQy0Q/zfyXoiwpxtlFSHQopHFJA7AUU= Received: from [66.196.81.165] by nm11.access.bullet.mail.bf1.yahoo.com with NNFMP; 10 May 2017 16:38:31 -0000 Received: from [98.139.244.52] by tm11.access.bullet.mail.bf1.yahoo.com with NNFMP; 10 May 2017 16:38:31 -0000 Received: from [127.0.0.1] by smtp114.sbc.mail.bf1.yahoo.com with NNFMP; 10 May 2017 16:38:31 -0000 X-Yahoo-Newman-Id: 635120.78661.bm@smtp114.sbc.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 0pcRRzgVM1mxri0GKid0tpPbS.guU.VVIX3K_o_RtKKdpom hL9yAK_IS1wCfc1XohlFpfeRhazzez7pCa357WmXxjCdCGdlgF2v8hqQXrGB Iq_3wu3do2S7z9k9JFPfHo9moV2AwRoFodSOEkyTHcT8ZpoocpI_H3gkdhch LOpeQqkkjjvGQhJz0D8r52eKufErfmcb.1PVdMEzbv4CWWfdnswbc6zl8KpK ZgxZmhwUkDW1xPruUEgIoazv_n4dmVdPXIzP7drvXTzDAAR_TC7Jb5G4R7WJ xXFpBTXuRWztz2kUx.FKrBBLbZjhDzPTTdAMo9zmwzWsUwXeuO2nxXxgg6hj gPhpY34_vwuTGnDEHKp15rNi2WRKtrjM3SH_o.D2NsuBRdD0OMNwjY9Xl.I_ agKQVkJQApZKecbDmuxbztah26Dt1AFYSVofO6Bgn90Qs9r7NoAzgSSlz5yv 9Ngxaiivmwf7NqrphpQ0XtOHBfJxhN2YKbFbBTyv..jwuDmW5pv6tWaJhc4E z4jyVhLB3B4zdO8OjimvFTSaSsy6Urbe4n2y_zzDRqm5X719QPMFci46hLb_ HxN4z5g-- X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo- User-Agent: Microsoft-MacOutlook/14.7.3.170325 Date: Wed, 10 May 2017 09:38:27 -0700 From: Don Sturek To: Routing Over Low power and Lossy networks Message-ID: Thread-Topic: [Roll] re-organizing use-of-rplinfo document: worth the typing? References: <6352.1494433492@obiwan.sandelman.ca> In-Reply-To: <6352.1494433492@obiwan.sandelman.ca> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Archived-At: Subject: Re: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2017 16:38:37 -0000 Hi Michael, I think implementers will use either one of storing or non-storing. At least for me, having a dedicated section describing the specific method of operation is useful (versus having to read through and skip over the MOP not in use). Plus it saves you having to edit the current draft! Don Sturek On 5/10/17, 9:24 AM, "Roll on behalf of Michael Richardson" wrote: > >It has been suggested that in draft-ietf-roll-useofrplinfo-14 that we >change >the presentation of the use cases. That instead of having 12 storing and >then 12 non-storing cases, that we instead have 12 cases, and within each >discuss the non-storing and storing subcases. > >Doing this involves moving a lot of text around, so before we do this, >we'd >like to get some rough consensus that this would be a better presentation. > >Do we need to do the run-through of the Berlin IETF96 slides again at the >Prague meeting? > >https://docs.google.com/presentation/d/1zdjzlLo-gWa1DEug3zQ7aMqWJ3PDM4Hajt >-uAOexynA/edit?usp=sharing > >https://docs.google.com/presentation/d/1zdjzlLo-gWa1DEug3zQ7aMqWJ3PDM4Hajt >-uAOexynA/pub?start=false&loop=false&delayms=60000 > >http://www.sandelman.ca/SSW/ietf/roll/useofrplinfo/ietf96-slides-v1.pdf > > >Given that 2460bis has not given us the desired collapse of the HbH option >type as we thought would happen, upon the advice of reviewers and Area >Director(s), useofrplinfo will be revised to update RFC6553 to change the >HbH >type code. Let us get that text ready, and so the WG can react better. > > >-- >Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > >_______________________________________________ >Roll mailing list >Roll@ietf.org >https://www.ietf.org/mailman/listinfo/roll From nobody Thu May 11 00:52:21 2017 Return-Path: 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 8DAFD124281 for ; Thu, 11 May 2017 00:52:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.621 X-Spam-Level: X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 zVXqx4d4WOJW for ; Thu, 11 May 2017 00:52:17 -0700 (PDT) Received: from lb2-smtp-cloud2.xs4all.net (lb2-smtp-cloud2.xs4all.net [194.109.24.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F67E129AB2 for ; Thu, 11 May 2017 00:52:16 -0700 (PDT) Received: from webmail.xs4all.nl ([IPv6:2001:888:0:22:194:109:20:214]) by smtp-cloud2.xs4all.net with ESMTP id JvsE1v00T0F6qFb01vsENM; Thu, 11 May 2017 09:52:15 +0200 Received: from 2001:983:a264:1:3ce9:9016:97cc:6e3b by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Thu, 11 May 2017 09:52:14 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 11 May 2017 09:52:14 +0200 From: peter van der Stok To: Routing Over Low power and Lossy networks Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org In-Reply-To: References: <6352.1494433492@obiwan.sandelman.ca> Message-ID: X-Sender: stokcons@xs4all.nl User-Agent: XS4ALL Webmail Archived-At: Subject: Re: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 May 2017 07:52:20 -0000 Hi Michael, I got the clear impression that the draft needs thorough re-writing anyway. That being the case and noticing that reviewers have problems to get to the end of the document, I wanted to suggest the following re-ordering. One use-case which describes the longest trajectory from outside, to inside, and outside the RPL LAN, decomposed in parts, say, a,b,c,d All the other use cases just tables with their composition of parts in the wanted order. If you want to separate in storing and non-storing is less a concern to me. If that does not augment readability (size) and significantly increases the rewrite, then don't bother. Peter Don Sturek schreef op 2017-05-10 18:38: > Hi Michael, > > I think implementers will use either one of storing or non-storing. At > least for me, having a dedicated section describing the specific method > of > operation is useful (versus having to read through and skip over the > MOP > not in use). > > Plus it saves you having to edit the current draft! > > Don Sturek > > > > On 5/10/17, 9:24 AM, "Roll on behalf of Michael Richardson" > wrote: > >> >> It has been suggested that in draft-ietf-roll-useofrplinfo-14 that we >> change >> the presentation of the use cases. That instead of having 12 storing >> and >> then 12 non-storing cases, that we instead have 12 cases, and within >> each >> discuss the non-storing and storing subcases. >> >> Doing this involves moving a lot of text around, so before we do this, >> we'd >> like to get some rough consensus that this would be a better >> presentation. >> >> Do we need to do the run-through of the Berlin IETF96 slides again at >> the >> Prague meeting? >> >> https://docs.google.com/presentation/d/1zdjzlLo-gWa1DEug3zQ7aMqWJ3PDM4Hajt >> -uAOexynA/edit?usp=sharing >> >> https://docs.google.com/presentation/d/1zdjzlLo-gWa1DEug3zQ7aMqWJ3PDM4Hajt >> -uAOexynA/pub?start=false&loop=false&delayms=60000 >> >> http://www.sandelman.ca/SSW/ietf/roll/useofrplinfo/ietf96-slides-v1.pdf >> >> >> Given that 2460bis has not given us the desired collapse of the HbH >> option >> type as we thought would happen, upon the advice of reviewers and >> Area >> Director(s), useofrplinfo will be revised to update RFC6553 to change >> the >> HbH >> type code. Let us get that text ready, and so the WG can react >> better. >> >> >> -- >> Michael Richardson , Sandelman Software Works >> -= IPv6 IoT consulting =- >> >> >> >> _______________________________________________ >> Roll mailing list >> Roll@ietf.org >> https://www.ietf.org/mailman/listinfo/roll > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll From nobody Thu May 11 05:34:18 2017 Return-Path: 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 AECA7129B19 for ; Thu, 11 May 2017 05:34:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 OdAd7CP1I0Ll for ; Thu, 11 May 2017 05:34:14 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAC8512EC05 for ; Thu, 11 May 2017 05:31:53 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 83253E1A1 for ; Thu, 11 May 2017 08:58:15 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C41B7636BB for ; Thu, 11 May 2017 08:31:52 -0400 (EDT) From: Michael Richardson To: Routing Over Low power and Lossy networks In-Reply-To: References: <6352.1494433492@obiwan.sandelman.ca> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: Re: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 May 2017 12:34:17 -0000 --=-=-= Content-Type: text/plain Don Sturek wrote: > I think implementers will use either one of storing or non-storing. At Yes, that's true. I'm more concerned for reviewers in some ways. > least for me, having a dedicated section describing the specific method > of operation is useful (versus having to read through and skip over the > MOP not in use). > Plus it saves you having to edit the current draft! Agreed. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlkUWbgACgkQgItw+93Q 3WWl3AgApEVQAEVlEeGbQti/GRIj7GNKIsVR6uw7YebK+W4rFQwFnSdufs9hww/J mD++ltUED8snzfMYurydBlDHOBxk8RPCwKC5XK1Lwv0zrpkN5IME84/qaBOEOwj0 MhF2wKFqVKAiEwRKf/Z+qRCDTqNyHjXrQmtcnr6c5dbqjFlzrPyz2jIpVKjZsy68 JbBRLoGD6siSDCQtbXNqwfini5eYDPgoKgh87OCNwWwXUjpDLt1jF4lLVX+Dpn7W jGkWldMBsiKgY2qR6mbzVHSzU8Li01WOPAoYDm7/DL8sjmxYs8WP1Q6Lk7ZbqLsI rBHgnBSYZqXl8zbMb2pXa+iFpzVRbA== =YZni -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu May 11 23:22:43 2017 Return-Path: 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 30789129572 for ; Thu, 11 May 2017 23:22:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=gmail.com 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 Ic8qmSn8Acv7 for ; Thu, 11 May 2017 23:22:40 -0700 (PDT) Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8D1E12957B for ; Thu, 11 May 2017 23:18:08 -0700 (PDT) Received: by mail-pf0-x22c.google.com with SMTP id e64so25146477pfd.1 for ; Thu, 11 May 2017 23:18:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :references:in-reply-to:to; bh=70RZ6/cUhnd9PD/2cWqH15pnrq+6+5zxK4gbnnx0PZk=; b=N1x8W17c0jRJMl5nPmU1tuNV/y5NLpeolmzLfrpgc8zNPtjb/6THt1xAlxz/TnGAVm 05IrrrYFF9cc4YbvLxOjegc9KIB1buPladZN8tnbrWaE0wZrBqdvgnOcloUqWr7raD63 jtRudo2bhhv1ZPFwkBQj0EgQ92ahAdVZE20WZjYx6LmQskCc+RsxKNSKfEKQiyUBeRVb 22mYc+1HSOz1aDdIw7XmwOfyLYVCt1DPE2O09J7HMKfgy5OeY+Mjl0APaij7y0keY3HL +xvXGPpjimmDeeZCs/AEaxpulPUpVBmBhn8MwIyPGqElZpTq7hiYiP6+bx6XiMjvZWlw t/sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:references:in-reply-to:to; bh=70RZ6/cUhnd9PD/2cWqH15pnrq+6+5zxK4gbnnx0PZk=; b=qLn7x2Vyv4osL5efzMC9rDemDDl/UTNyv//v2EAWkjpQ2wQQgmROQ7iEVr35BDedlH C/rAkxhOjO65W7ELsJENh5EVJMalhPIPCd43dw5bhfZeMKz3wXlCd4un4Q0JL0PwDm3B XathTMnXZneJpPuw5ku3PyHxtbjQGPZ1aNdnqBZjKVWsyTxlVKCg+DK//fONVNNA5srV 0UqR21U8hp6DeGLulwWYBZnyPQVJnKMtsUksk42P77PJVjwWrksE8/eTbC+AsLdBLbKH IyNvH6qo5cD676sPRu0Zo8lDXLLdQ3bko/LCrvnbt9b6IiyzQyXoT532GiVBkXt79Ua8 hykQ== X-Gm-Message-State: AODbwcB4Pb1hWZpunVyHRNppkz3+ncBgqWFXwLxEX83nF+z3PZQvsbfK TfT91XKMPb2R/D7Zelw= X-Received: by 10.99.109.130 with SMTP id i124mr2679354pgc.117.1494569888229; Thu, 11 May 2017 23:18:08 -0700 (PDT) Received: from [100.126.31.11] ([27.59.77.231]) by smtp.gmail.com with ESMTPSA id u194sm2037599pgc.2.2017.05.11.23.18.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 May 2017 23:18:07 -0700 (PDT) From: Rahul Jadhav Content-Type: multipart/alternative; boundary=Apple-Mail-BE872A77-AE8D-444F-A53C-896D71F54F3F Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Fri, 12 May 2017 11:48:04 +0530 Message-Id: <486101F3-020B-4D40-B4F9-1B6A698C0018@gmail.com> References: <6352.1494433492@obiwan.sandelman.ca> <21405.1494505912@obiwan.sandelman.ca> In-Reply-To: <21405.1494505912@obiwan.sandelman.ca> To: Routing Over Low power and Lossy networks X-Mailer: iPhone Mail (14E304) Archived-At: Subject: Re: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2017 06:22:42 -0000 --Apple-Mail-BE872A77-AE8D-444F-A53C-896D71F54F3F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable As someone who had previously reviewed the draft, I can say it is not an eas= y going with reviewing the draft. But i didn't had any suggestions on improv= ing the readability then. The proposal to modify it to put 12 cases with storing, non storing section i= n each case sounds good to me... It will also reduce some repeatative text p= ut in context to explaining the scenario of the case. Also the tabular view f= or header changes is also repeatative in some case (raf to root flow for e.g= .). Not sure if the table view for header manipulation for storing, non stor= ing be merged easily for all cases with good readability. Regards, Rahul > On 11-May-2017, at 6:01 PM, Michael Richardson wro= te: >=20 >=20 > Don Sturek wrote: >> I think implementers will use either one of storing or non-storing. At >=20 > Yes, that's true. > I'm more concerned for reviewers in some ways. >=20 >> least for me, having a dedicated section describing the specific method >> of operation is useful (versus having to read through and skip over the >> MOP not in use). >=20 >> Plus it saves you having to edit the current draft! >=20 > Agreed. >=20 > -- > Michael Richardson , Sandelman Software Works > -=3D IPv6 IoT consulting =3D- >=20 >=20 >=20 > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll --Apple-Mail-BE872A77-AE8D-444F-A53C-896D71F54F3F Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

As someone who had previously revi= ewed the draft, I can say it is not an easy going with reviewing the draft. B= ut i didn't had any suggestions on improving the readability then.

The proposal to modify it to put 12 cases with storing, non s= toring section in each case sounds good to me... It will also reduce some re= peatative text&nbs= p;put in context to explaining the scenario of the case. Also the tabular vi= ew for header changes is also repeatative in some case (raf to root flow for= e.g.). Not sure if the table view for header manipulation for storing, non s= toring be merged easily for all cases with good readability.

Rahul

On 11-May-2017= , at 6:01 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:


Don Sturek <d.sturek@att.net> wrote:
I think implementers will use either one of storing or non-storing.  = ;At

Yes, that's true.I'm more concerned for reviewers in some ways.

least for me, having a dedicated secti= on describing the specific method
of operation is useful (versus having to read through and skip o= ver the
MOP not in us= e).

= Plus it saves you having to edit the current draft!
<= span>
Agreed.

--
= Michael Richardson <mcr+IE= TF@sandelman.ca>, Sandelman Software Works
-=3D IPv6= IoT consulting =3D-



______________= _________________________________
Roll mailing listRoll@ietf.org
<= a href=3D"https://www.ietf.org/mailman/listinfo/roll">https://www.ietf.org/m= ailman/listinfo/roll
= --Apple-Mail-BE872A77-AE8D-444F-A53C-896D71F54F3F-- From nobody Fri May 12 05:13:28 2017 Return-Path: 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 27B3D129404 for ; Fri, 12 May 2017 05:13:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=googlemail.com 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 1EPkajUKuRo7 for ; Fri, 12 May 2017 05:13:23 -0700 (PDT) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C5081294F4 for ; Fri, 12 May 2017 05:08:36 -0700 (PDT) Received: by mail-it0-x22e.google.com with SMTP id c15so9241546ith.0 for ; Fri, 12 May 2017 05:08:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=cqx1RHQNbARwnwCCkkyQynYUkCkJZyag61uWSBoNKz8=; b=Q2siwZs3BDtEXzY+rE9OGbKeRorNWsuhCBMaPPzQifxrC6E3XMuKtnyEW5ACpg5Qj8 fZ8b0JcI0wHb+ufWimK2Svllse6rVAqv06XMSlP2Y/AjNTcAsW5UV0HN5G6Xi6BxvKY3 iYV7tzrdeoyA5sX19zi/1JWuhocfvuphsmsKBElLxc288LKN2P8Heoz73nVc6sLW/JcB 8CayLghXOqbtqpiVxOFG/QzhrvGVumagUpg2L+jt9459FNzoNo4iVfYQLiHqtO9aLa/l IVBMDzEEudv5R5c+e6EvScfcaLdrl66YQBZqnkuL5PUHYcmG8RRl1nN80h7gojchz+Db aukA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=cqx1RHQNbARwnwCCkkyQynYUkCkJZyag61uWSBoNKz8=; b=pyu9TUzpQMkrbM20Ew1GtL4vkVZBRwZD4YaK0BUd9O/5IpJA9S5nRtqqE52FgMrXBk I8qpCxTj5k3ADO1rGTecgfgvdFV7079AI77jOWLhmTrl1vKAkMai6npVgnAZ7VDAkenj bfOjtdTtQUlLHVL49vzboqPl4alKBhj86TMOmzedR242dxu6hyM6MiOKlD4gvi5NezX4 rg3KSfPFTB978bBkvKUIzSrIZo5p1vHE91r9b6hy3DyRLfaWMRBmS3sVoRT1lNscBsgZ i8tywpt92b7d61X17JdnrBLLMRxCz+muj3i85AX+QXmXz+i7UUPXSolRXXaq9u3Vtl60 DOxw== X-Gm-Message-State: AODbwcCuKUCodqsS1gDn4eHYcQPHEToDO+EQkXoJ8YMqkp2oG0H86Qu9 awbuFmDuW3iooGFmJzijcLy2girY0g== X-Received: by 10.36.120.23 with SMTP id p23mr3309833itc.106.1494590915629; Fri, 12 May 2017 05:08:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.97.132 with HTTP; Fri, 12 May 2017 05:08:35 -0700 (PDT) In-Reply-To: <486101F3-020B-4D40-B4F9-1B6A698C0018@gmail.com> References: <6352.1494433492@obiwan.sandelman.ca> <21405.1494505912@obiwan.sandelman.ca> <486101F3-020B-4D40-B4F9-1B6A698C0018@gmail.com> From: Ines Robles Date: Fri, 12 May 2017 09:08:35 -0300 Message-ID: To: Routing Over Low power and Lossy networks Content-Type: multipart/alternative; boundary="001a11485dd89c5ff6054f5290d9" Archived-At: Subject: Re: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2017 12:13:26 -0000 --001a11485dd89c5ff6054f5290d9 Content-Type: text/plain; charset="UTF-8" Thank you very much for all your comments, We are working to improve the readability. Cheers, Ines. 2017-05-12 3:18 GMT-03:00 Rahul Jadhav : > > As someone who had previously reviewed the draft, I can say it is not an > easy going with reviewing the draft. But i didn't had any suggestions on > improving the readability then. > > The proposal to modify it to put 12 cases with storing, non storing > section in each case sounds good to me... It will also reduce some > repeatative text put in context to explaining the scenario of the case. > Also the tabular view for header changes is also repeatative in some case > (raf to root flow for e.g.). Not sure if the table view for header > manipulation for storing, non storing be merged easily for all cases with > good readability. > > Regards, > Rahul > > On 11-May-2017, at 6:01 PM, Michael Richardson > wrote: > > > Don Sturek wrote: > > I think implementers will use either one of storing or non-storing. At > > > Yes, that's true. > I'm more concerned for reviewers in some ways. > > least for me, having a dedicated section describing the specific method > > of operation is useful (versus having to read through and skip over the > > MOP not in use). > > > Plus it saves you having to edit the current draft! > > > Agreed. > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll > > --001a11485dd89c5ff6054f5290d9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you very much for all your comments,

<= div>We are working =C2=A0to improve the readability.

Cheers,

Ines.

2017-05-12 3:18 GMT-03:00 Rahul Jadhav = <rahul.ietf@gmail.com>:

As someone who had previously reviewed the draf= t, I can say it is not an easy going with reviewing the draft. But i didn&#= 39;t had any suggestions on improving the readability then.

<= /div>
The proposal to modify it to put 12 cases with storing, non stori= ng section in each case sounds good to me... It will also reduce some repea= tative text=C2=A0pu= t in context to explaining the scenario of the case. Also the tabular view = for header changes is also repeatative in some case (raf to root flow for e= .g.). Not sure if the table view for header manipulation for storing, non s= toring be merged easily for all cases with good readability.<= /div>

Regards,
Rahul
On 11-May-2017, at 6:01 PM, Michael Richardson <mcr+ietf@sandelman.ca> wr= ote:


Don= Sturek <d.sturek@= att.net> wrote:
I think im= plementers will use either one of storing or non-storing.=C2=A0 At

Yes, that's true.
I'm more concerned for reviewers in some ways.
=
least for me, having a dedicated sectio= n describing the specific method
of operation is useful (versus having to read through and skip= over the
MOP not in= use).

Plus it saves you having to edit the current draft!

Agreed.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works<= /span>
-=3D IPv6 IoT consulting =3D-

<= span>

_______________________________________________
Roll mailing list
Roll@ietf.org
= https://www.ietf.org/mailman/listinfo/roll

___________________________________________= ____
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll


--001a11485dd89c5ff6054f5290d9-- From nobody Fri May 12 06:26:06 2017 Return-Path: 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 B719012422F for ; Fri, 12 May 2017 06:26:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no 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 1-REpcksTIhC for ; Fri, 12 May 2017 06:26:04 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B047D127369 for ; Fri, 12 May 2017 06:21:22 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5406CE1D7 for ; Fri, 12 May 2017 09:47:47 -0400 (EDT) Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 13D6B636BB for ; Fri, 12 May 2017 09:21:21 -0400 (EDT) From: Michael Richardson To: Routing Over Low power and Lossy networks In-Reply-To: <486101F3-020B-4D40-B4F9-1B6A698C0018@gmail.com> References: <6352.1494433492@obiwan.sandelman.ca> <21405.1494505912@obiwan.sandelman.ca> <486101F3-020B-4D40-B4F9-1B6A698C0018@gmail.com> X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: Re: [Roll] re-organizing use-of-rplinfo document: worth the typing? X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 May 2017 13:26:06 -0000 --=-=-= Content-Type: text/plain Rahul Jadhav wrote: > case. Also the tabular view for header changes is also repeatative in > some case (raf to root flow for e.g.). Not sure if the table view for > header manipulation for storing, non storing be merged easily for all > cases with good readability. The tables are hard to maintain/update. Should we even keep them? on the other hand, they are already done. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlkVttAACgkQgItw+93Q 3WUd9Af/bQlcH5cnO/qG63zjnnK3zy+uNg0nzAMuzvDauXj3SgQmTNWSlIFnvidl kv1yg0YHcocOjbbT7mCqMqt6O6VvHy1p7nIsESQnPb4N/Dt7neN6ZBgFr2YdwePy 1HofhCl/vyj8DWuWVAupq0k6aFhVPijNfsGx62zen7nShHlZ/2OxO6tt4IBVIn85 TN60HWjXyRoQZXrOX3WgvEP57fk0UrGpaQeIEKdxEOUfLGSHr5sH2f5QgPLFpQK1 TBcVpTw7YSw2j+orkqoRH53baImz64PP23e/tx8Dflu4t6qYIGmFRB7q1lvTuCJv X2qzXjioNTQf3op/45AgU/sSnMtSsQ== =2KLK -----END PGP SIGNATURE----- --=-=-=-- From nobody Sat May 13 09:08:29 2017 Return-Path: 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 41FE3127241 for ; Sat, 13 May 2017 09:08:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 DOU4ahz6IrCD for ; Sat, 13 May 2017 09:08:26 -0700 (PDT) Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86C111273E2 for ; Sat, 13 May 2017 09:06:33 -0700 (PDT) Received: by mail-pg0-x22f.google.com with SMTP id u28so42672889pgn.1 for ; Sat, 13 May 2017 09:06:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:references:to:date; bh=UpNPPlaR2ku4zt+WfDZkygxUTeJHOo3faZHMIct/CC0=; b=UU3FfL47Hc2vIpHPmsaLftr+s1olo79OElSXQ4gd/4VBvwqN2btzDF/iwBzCaT7x3H vxfMrh4wkfYSoFK2zFwgsiwBrhOHKZS76JSQM9ewMZF9I7K5Z1uS9LFsl2YklMzxfLeg 3EK+ulfyFzKwT4f7xzAwQd2gxpzm+gX7zCpc0LcnHIaWlPApSYQPC11735t8E4tLZjwk Ikzr013XzzJ9xnaLgA4ViReVM+rOzltNV7svPZHZZtactbJjE/C8/2211cn4SaMGMbFh mdk5qIxa/v26/zxA6HT48b7zdO6M04RU/O4HJGgJ65MwQG2A+Tw5tWjx/zCzH+Sf3v2o PX3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:references :to:date; bh=UpNPPlaR2ku4zt+WfDZkygxUTeJHOo3faZHMIct/CC0=; b=rkxCv7+Fr7KSayo1DIgFnWUpMLLlkYpNFIATJ681Ut/Pt1plDcNMrtseP14s7KzlpF NvENPvaYKEHYvw9fkRwXtEEq9+FAoR5eDsIe2iNfVrsy7TJnoIyOkF/eWaDtYrcrm3Py jUlVS36hj7FaSrkVB3+KrTKt0y9Wm57lNHjUz5mbtsCBhNvnxEqQ+Cle8PfVNmvO6MYa sFTiJiHNaR90MkDpI+cB4sTDN9cJvsuLVZ1ngijUGNIbnhWU5e50x+4gqSQ0SVZNRQOt 1PHeWxs4BD44iUTqX78X+7xfrij6fKMAoErDeCE+BNWW7fT0kcylLCAOaLpPJRhc2zMw ZD0Q== X-Gm-Message-State: AODbwcAC+VplhPPom00QKVWc55+8Z36CB54bX9rT3DjSFiwVRKgozcz8 TnmQzsnpweq3cjWRLEA= X-Received: by 10.98.153.216 with SMTP id t85mr10395747pfk.178.1494691592961; Sat, 13 May 2017 09:06:32 -0700 (PDT) Received: from [192.168.1.102] ([119.82.122.102]) by smtp.gmail.com with ESMTPSA id q28sm10921937pgc.0.2017.05.13.09.06.31 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 13 May 2017 09:06:32 -0700 (PDT) From: Rahul Jadhav Content-Type: multipart/alternative; boundary="Apple-Mail=_88F0A4C7-CEAC-4E00-B12F-5E23C1B09858" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Message-Id: References: <149466113235.13534.9559511443941453863.idtracker@ietfa.amsl.com> To: Routing Over Low power and Lossy networks Date: Sat, 13 May 2017 21:36:33 +0530 X-Mailer: Apple Mail (2.3259) Archived-At: Subject: [Roll] Fwd: New Version Notification for draft-jadhav-roll-efficient-npdao-01.txt X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 May 2017 16:08:28 -0000 --Apple-Mail=_88F0A4C7-CEAC-4E00-B12F-5E23C1B09858 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear All,=20 The solution for NPDAO improvements was presented in IETF98.=20 And based on the discussions there, following are the changes to the ID: 1. Improved readability a. Removed couple of unnecessary sections b. Fixed wordings in some places 2. Applicability for 6tisch 3. Updated security considerations 4. Fixed example section For completeness, attaching link to the discussion that happened on the = ML:=20 https://www.ietf.org/mail-archive/web/roll/current/msg09639.html = Looking forward for reviews and feedback. Thanks, Rahul > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: New Version Notification for = draft-jadhav-roll-efficient-npdao-01.txt > Date: 13 May 2017 at 1:08:52 PM IST > To: "Rabi Sahoo" , "JADHAV RAHUL" = , "Rahul Arvind Jadhav" , = "Zhen Cao" , "Rabi Narayan Sahoo" = >=20 >=20 > A new version of I-D, draft-jadhav-roll-efficient-npdao-01.txt > has been successfully submitted by Rahul Arvind Jadhav and posted to = the > IETF repository. >=20 > Name: draft-jadhav-roll-efficient-npdao > Revision: 01 > Title: No-Path DAO modifications > Document date: 2017-05-12 > Group: Individual Submission > Pages: 12 > URL: = https://www.ietf.org/internet-drafts/draft-jadhav-roll-efficient-npdao-01.= txt > Status: = https://datatracker.ietf.org/doc/draft-jadhav-roll-efficient-npdao/ > Htmlized: = https://tools.ietf.org/html/draft-jadhav-roll-efficient-npdao-01 > Htmlized: = https://datatracker.ietf.org/doc/html/draft-jadhav-roll-efficient-npdao-01= > Diff: = https://www.ietf.org/rfcdiff?url2=3Ddraft-jadhav-roll-efficient-npdao-01 >=20 > Abstract: > This document describes the problems associated with the use of No- > Path DAO messaging in RPL and a signaling changes to improve route > invalidation efficiency. >=20 >=20 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > The IETF Secretariat >=20 --Apple-Mail=_88F0A4C7-CEAC-4E00-B12F-5E23C1B09858 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

Dear All, 

The solution for NPDAO improvements was = presented in IETF98. 
And based = on the discussions there, following are the changes to the ID:
1.  =    Improved readability
a.       Removed = couple of unnecessary sections
b.      Fixed = wordings in some places
2.    = Applicability for 6tisch
3.    Updated security = considerations
4.   Fixed example section

For completeness, attaching link = to the discussion that happened on the ML: 
https://www.ietf.org/mail-archive/web/roll/current/msg09639.htm= l

Looking forward for reviews and feedback.

Thanks,
Rahul



Begin = forwarded message:

From: = internet-drafts@ietf.org
Subject: = New Version = Notification for draft-jadhav-roll-efficient-npdao-01.txt
Date: = 13 May 2017 at 1:08:52 PM = IST
To: = "Rabi Sahoo" <rabinarayans@huawei.com>, "JADHAV RAHUL" <rahul.ietf@gmail.com>, "Rahul Arvind Jadhav" <rahul.ietf@gmail.com>, "Zhen Cao" <zhencao.ietf@gmail.com>, "Rabi Narayan Sahoo" <rabinarayans@huawei.com>


A new version = of I-D, draft-jadhav-roll-efficient-npdao-01.txt
has been = successfully submitted by Rahul Arvind Jadhav and posted to the
IETF repository.

Name: = draft-jadhav-roll-efficient-npdao
Revision: 01
Title:= = No-Path DAO modifications
Document date: = 2017-05-12
Group: Individual Submission
Pages:= = 12
URL: =            https://www.ietf.org/internet-drafts/draft-jadhav-roll-efficien= t-npdao-01.txt
Status: =         https://datatracker.ietf.org/doc/draft-jadhav-roll-efficient-np= dao/
Htmlized:       https://tools.ietf.org/html/draft-jadhav-roll-efficient-npdao-0= 1
Htmlized:       https://datatracker.ietf.org/doc/html/draft-jadhav-roll-efficie= nt-npdao-01
Diff: =           https://www.ietf.org/rfcdiff?url2=3Ddraft-jadhav-roll-efficient= -npdao-01

Abstract:
=   This document describes the problems associated with the use = of No-
  Path DAO messaging in RPL and a = signaling changes to improve route
=   invalidation efficiency.




Please note that it may take a = couple of minutes from the time of submission
until the = htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


= --Apple-Mail=_88F0A4C7-CEAC-4E00-B12F-5E23C1B09858-- From nobody Mon May 29 07:13:34 2017 Return-Path: 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 9ACCB1274D2 for ; Mon, 29 May 2017 07:13:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=googlemail.com 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 5kg_wMWq6xZB for ; Mon, 29 May 2017 07:13:30 -0700 (PDT) Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D81812420B for ; Mon, 29 May 2017 07:13:30 -0700 (PDT) Received: by mail-io0-x232.google.com with SMTP id k91so41770222ioi.1 for ; Mon, 29 May 2017 07:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=eqf3UgzvTKmqNK1SH28AvCMaFy6wcw6/XtxHy6lppiY=; b=F0/kPC4s+v7Ls3hLVUjNAx9jzVjGSmQFqEQGgy+mhgUluj4zbk9H66CssWtMNDiSfb T/YS3TfBoeFhaR3QUvRHMat40lMwGYqVw3sx0gkIG402xD3yT8tVOoK9LIDtfUujBQj+ 7ivXSaeYcLnPEIUos/wZsZIOK2hI2CJC84UFY1e5TS4Kf6+BBZ2T2+EQaCCmNe+jEtD8 J2n1nve9v/RmeYdLYGcJPx2mWYueDk78kg7u7fR0QJnI7wigQBbFfuXpnWY66V4PZlHF L/TZvy10XDi6Qzt2najct9zpzTWkOwxguRa6n61W6pj7aSKTE6/S0S2IkAGM8q986+aY jgzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=eqf3UgzvTKmqNK1SH28AvCMaFy6wcw6/XtxHy6lppiY=; b=j85A5YDrGCdaLzVE+iW6++r6N5lXWDj0TO4Y1RCYceb5woY3kVeU+Lb/tpGnUaQjWH eby1E66eVIXKi5sQ20TNFP7lZSiSIXtlgS1Htt8W9BsJKtkWkR2pgV5shTD0Tf/dSPQl Ll4qJ8nBj6H6J96Y+s3PdFczx8VOWwy69RR9KD1FcRH6jrY/T0kkpRrwmqDAXsyhFgY9 /S1a1n2gj0wWJiu84iUSWrFzzbFbSigwKNxRnMgocvPoGQHF2Zt5Rg4+j5AZ+sWXQixv zqnSX0fNjNO/El392kTqElg3B63WfMkbO6rsLDxsq2onYWfiWtZCA72dp7+43c8H4+ls bdaQ== X-Gm-Message-State: AODbwcCX5KSv+9VTO3jqx7rzYYfCV4R8Xytxr7EIOCRtBWvwCSAGa0VK KzvJVK4kRAX23iU7Ahj6N/wn7+GmRA== X-Received: by 10.107.34.208 with SMTP id i199mr13528048ioi.210.1496067209337; Mon, 29 May 2017 07:13:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.73.65 with HTTP; Mon, 29 May 2017 07:13:28 -0700 (PDT) From: Ines Robles Date: Mon, 29 May 2017 17:13:28 +0300 Message-ID: To: Routing Over Low power and Lossy networks Cc: "Rahul Arvind Jadhav (Rahul Arvind Jadhav, 2012 Labs)" , peter van der Stok Content-Type: multipart/alternative; boundary="001a1140402c92ab830550aa4afd" Archived-At: Subject: [Roll] WG adoption call for draft-jadhav-roll-efficient-npdao-01 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 May 2017 14:13:33 -0000 --001a1140402c92ab830550aa4afd Content-Type: text/plain; charset="UTF-8" Dear all, This starts a ROLL Working Group adoption call for draft-jadhav-roll-efficient-npdao-01. https://datatracker.ietf.org/doc/draft-jadhav-roll-efficient-npdao/ Please send your opinion (for or against) to the mailing list on adopting this document as a Roll WG document. This call will end at 00:00 UTC on June 12, 2017. Regards, Peter, Ines 2017-05-13 19:06 GMT+03:00 Rahul Jadhav : > > Dear All, > > The solution for NPDAO improvements was presented in IETF98. > And based on the discussions there, following are the changes to the ID: > 1. Improved readability > a. Removed couple of unnecessary sections > b. Fixed wordings in some places > 2. Applicability for 6tisch > 3. Updated security considerations > 4. Fixed example section > > For completeness, attaching link to the discussion that happened on the > ML: > https://www.ietf.org/mail-archive/web/roll/current/msg09639.html > > Looking forward for reviews and feedback. > > Thanks, > Rahul > > > > Begin forwarded message: > > *From: *internet-drafts@ietf.org > *Subject: **New Version Notification for > draft-jadhav-roll-efficient-npdao-01.txt* > *Date: *13 May 2017 at 1:08:52 PM IST > *To: *"Rabi Sahoo" , "JADHAV RAHUL" < > rahul.ietf@gmail.com>, "Rahul Arvind Jadhav" , > "Zhen Cao" , "Rabi Narayan Sahoo" < > rabinarayans@huawei.com> > > > A new version of I-D, draft-jadhav-roll-efficient-npdao-01.txt > has been successfully submitted by Rahul Arvind Jadhav and posted to the > IETF repository. > > Name: draft-jadhav-roll-efficient-npdao > Revision: 01 > Title: No-Path DAO modifications > Document date: 2017-05-12 > Group: Individual Submission > Pages: 12 > URL: https://www.ietf.org/internet-drafts/draft- > jadhav-roll-efficient-npdao-01.txt > Status: https://datatracker.ietf.org/doc/draft-jadhav- > roll-efficient-npdao/ > Htmlized: https://tools.ietf.org/html/draft-jadhav-roll- > efficient-npdao-01 > Htmlized: https://datatracker.ietf.org/doc/html/draft- > jadhav-roll-efficient-npdao-01 > Diff: https://www.ietf.org/rfcdiff?url2=draft-jadhav- > roll-efficient-npdao-01 > > Abstract: > This document describes the problems associated with the use of No- > Path DAO messaging in RPL and a signaling changes to improve route > invalidation efficiency. > > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll > > --001a1140402c92ab830550aa4afd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,
=C2=A0
This starts a ROLL Wor= king Group adoption call for draft-jadhav-roll-efficient-npdao-01.
=C2=A0
=C2=A0
Please send your opinion (f= or or against) to the mailing list on adopting this document as a Roll WG d= ocument. This call will end at 00:00 UTC on June 12, 2017.
=C2=A0=
Regards,
=C2=A0
Peter, Ines

2017-05-13 19:06 GMT+0= 3:00 Rahul Jadhav <rahul.ietf@gmail.com>:

=
Dear All,=C2=A0

The solution f= or NPDAO improvements was presented in IETF98.=C2=A0
And bas= ed on the discussions there, following are the changes to the ID:=
1.=C2=A0 =C2=A0=C2=A0=C2=A0Impr= oved readability
a.=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Removed couple of unnecessary secti= ons
b.=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0Fixed wordings in some places
= 2.=C2=A0 =C2=A0 Applicability for 6tisch
3.=C2=A0=C2=A0=C2=A0=C2=A0Updated security conside= rations
4. =C2=A0=C2=A0Fixed example section

For completeness, attaching link to the discussion= that happened on the ML:=C2=A0

Looking for= ward for reviews and feedback.

Thank= s,
Rahul



Begin forwarded message:

Subject: New Version Notifica= tion for draft-jadhav-roll-efficient-npdao-01.txt
=
Date: 13 May 20= 17 at 1:08:52 PM IST
<= b>To: "Rabi Sahoo" <rabinarayans@huawei.com>, &qu= ot;JADHAV RAHUL" <rahul.ietf@gmail.com>, "Rahul Arvind Jadhav" <= rahul.ietf@gmail.= com>, "Zhen Cao" <zhencao.ietf@gmail.com>, "Rabi Narayan S= ahoo" <rabinarayans@huawei.com>


A new ve= rsion of I-D, draft-jadhav-roll-efficient-npdao-01.txt
has been suc= cessfully submitted by Rahul Arvind Jadhav and posted to the
IETF reposi= tory.

Name: draft-jadhav-roll-efficie= nt-npdao
Revision: 01
Title: No-Path DAO modifications
Document date: 2017-= 05-12
Group: Individual Submission
Pag= es: 12
URL: =C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0htt= ps://www.ietf.org/internet-drafts/draft-jadhav-roll-efficient-npd= ao-01.txt
Status: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0https://datatracker.ietf.org/doc/draft-jadha= v-roll-efficient-npdao/
Htmlized: =C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0https://tools.ietf.org/html/draft-jadhav-= roll-efficient-npdao-01
Htmlized: =C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0https://datatracker.ietf.org/do= c/html/draft-jadhav-roll-efficient-npdao-01
Diff: =C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0https://www.ietf.org/rfcdiff?url2=3Ddraft-jadhav-roll-efficient-= npdao-01

Abstract:
=C2=A0=C2=A0This document describes the p= roblems associated with the use of No-
=C2=A0=C2=A0Path DAO messaging i= n RPL and a signaling changes to improve route
=C2=A0=C2=A0invalidation= efficiency.




Please note that it may take a couple of mi= nutes from the time of submission
until the htmlized version and diff ar= e available at tools.ie= tf.org.

The IETF Secretariat



_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll


--001a1140402c92ab830550aa4afd--