From nobody Sun Jul 1 10:48:34 2018 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 83EB4130E98; Sun, 1 Jul 2018 10:48:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 e-G7O_e3DaOk; Sun, 1 Jul 2018 10:48:12 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 D9464130EAF; Sun, 1 Jul 2018 10:48:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w61Hm7Il022871; Sun, 1 Jul 2018 19:48:08 +0200 (CEST) Received: from [192.168.217.114] (p5DC7FF04.dip0.t-ipconnect.de [93.199.255.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 41JdCC525NzDXdS; Sun, 1 Jul 2018 19:48:07 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 552160085.3122081-f7f70c9c5d32c022ade2dc78838d3624 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Message-Id: <5836EACF-38A8-4AFE-9339-7932945213F1@tzi.org> Date: Sun, 1 Jul 2018 19:48:07 +0200 To: lo <6lo@ietf.org>, tisch <6tisch@ietf.org>, lp-wan , lwip@ietf.org, Routing Over Low power and Lossy networks X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: [Roll] Constrained Node/Network Cluster @ IETF102: FINAL AGENDA X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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: Sun, 01 Jul 2018 17:48:25 -0000 I forgot to send the update of my usual eclectic condensed agenda based on the "FINAL" AGENDA for IETF102. Remember that "FINAL" means this will be the basis for printed agenda sheets, there is still some potential for changes after that. The only change from the previous draft agenda (apart from different room assignments) seems to be the move of SECDISPATCH on top of the first CORE slot and of SUIT into what previously was the SECDISPATCH slot. The conflicts ACE vs. DISPATCH as well as CBOR vs. 6LO vs. TEEP remain. All times are EDT (UTC-0400). (You can get pure UTC times on https://datatracker.ietf.org/meeting/agenda-utc, for those who want to listen from remote.) Gr=C3=BC=C3=9Fe, Carsten SATURDAY/SUNDAY -- Hackathon (including various interops) (Centre Ville) -- Sun 1800-2000: HotRFC (Viger) MONDAY, July 16, 2018 0930-1200 Morning Session I Duluth ART dispatch Dispatch WG - Joint with ARTAREA Laurier INT 6man IPv6 Maintenance WG Place du Canada RTG detnet Deterministic Networking WG Viger SEC *** ace Authentication and Authorization for = Constrained Environments WG 1330-1530 Afternoon Session I Laurier INT ipwave IP Wireless Access in Vehicular = Environments WG Place du Canada SEC tls Transport Layer Security WG 1550-1750 Afternoon Session II Duluth ART *** core Constrained RESTful Environments WG Laurier INT intarea Internet Area Working Group WG Viger SEC secdispatch Security Dispatch WG 1810-1940 Afternoon Session III Laurier GEN rfcplusplus The label "RFC" BOF TUESDAY, July 17, 2018 0930-1200 Morning Session I Place du Canada IRTF irtfopen IRTF Open Meeting St-Paul/St-Cath RTG babel Babel routing protocol WG Duluth RTG *** roll Routing Over Low power and Lossy = networks WG 1330-1530 Afternoon Session I Van Horne ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG Duluth INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Laurier RTG rtgarea Routing Area Open Meeting Viger SEC *** teep Trusted Execution Environment = Provisioning WG 1550-1820 Afternoon Session II Place du Canada ART httpbis Hypertext Transfer Protocol WG Viger IRTF cfrg Crypto Forum - 1720 - 1820 Centre Ville IRTF icnrg Information-Centric Networking Van Horne SEC acme Automated Certificate Management = Environment WG - 1720 - 1820 Van Horne SEC oauth Web Authorization Protocol WG - 1550 - = 1720 Duluth TSV taps Transport Services WG WEDNESDAY, July 18, 2018 0930-1200 Morning Session I Van Horne OPS anima Autonomic Networking Integrated Model = and Approach WG St-Paul/St-Cath RTG bier Bit Indexed Explicit Replication WG Duluth SEC *** suit Software Updates for Internet of Things = WG Place du Canada TSV quic QUIC WG 1330-1500 Afternoon Session I Laurier ART httpbis Hypertext Transfer Protocol WG Duluth INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG 1520-1650 Afternoon Session II Centre Ville INT homenet Home Networking WG Viger TSV tsvarea Transport Area Open Meeting THURSDAY, July 19, 2018 0930-1200 Morning Session I Duluth INT dnssd Extensions for Scalable DNS Service = Discovery WG Centre Ville INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Place du Canada IRTF maprg Measurement and Analysis for Protocols Viger SEC mls Messaging Layer Security WG Van Horne SEC oauth Web Authorization Protocol WG - 0930 - = 1100 1330-1530 Afternoon Session I Laurier OPS v6ops IPv6 Operations WG Centre Ville RTG rift Routing In Fat Trees WG Place du Canada SEC saag Security Area Open Meeting 1550-1750 Afternoon Session II Laurier IRTF*** t2trg Thing-to-Thing Viger OPS driu DNS Resolver Identification and Use BOF Centre Ville TSV tsvwg Transport Area Working Group WG 1810-1910 Afternoon Session III Van Horne ART *** core Constrained RESTful Environments WG Laurier SEC tls Transport Layer Security WG Centre Ville TSV tsvwg Transport Area Working Group WG FRIDAY, July 20, 2018 0930-1130 Morning Session I Centre Ville IRTF*** dinrg Decentralized Internet Infrastructure = Proposed RG Place du Canada OPS v6ops IPv6 Operations WG St-Paul/St-Cath TSV rmcat RTP Media Congestion Avoidance = Techniques WG 1150-1320 Afternoon Session I Duluth INT *** lwig Light-Weight Implementation Guidance WG Laurier IRTF panrg Path Aware Networking Proposed RG Centre Ville SEC tokbind Token Binding WG From nobody Mon Jul 2 16:43:39 2018 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 B1B0E131231; Mon, 2 Jul 2018 16:43:37 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: roll@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153057501769.16480.8128377636015125246@ietfa.amsl.com> Date: Mon, 02 Jul 2018 16:43:37 -0700 Archived-At: Subject: [Roll] I-D Action: draft-ietf-roll-aodv-rpl-04.txt X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2018 23:43:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Over Low power and Lossy networks WG of the IETF. Title : Asymmetric AODV-P2P-RPL in Low-Power and Lossy Networks (LLNs) Authors : Satish Anamalamudi Mingui Zhang Abdur Rashid Sangi Charles E. Perkins S.V.R Anand Bing Liu Filename : draft-ietf-roll-aodv-rpl-04.txt Pages : 24 Date : 2018-07-02 Abstract: Route discovery for symmetric and asymmetric Point-to-Point (P2P) traffic flows is a desirable feature in Low power and Lossy Networks (LLNs). For that purpose, this document specifies a reactive P2P route discovery mechanism for both hop-by-hop routing and source routing: Ad Hoc On-demand Distance Vector Routing (AODV) based RPL protocol. Paired Instances are used to construct directional paths, in case some of the links between source and target node are asymmetric. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-roll-aodv-rpl/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-roll-aodv-rpl-04 https://datatracker.ietf.org/doc/html/draft-ietf-roll-aodv-rpl-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-aodv-rpl-04 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Jul 3 01:45:45 2018 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 E3083130E40 for ; Tue, 3 Jul 2018 01:45:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=imt-atlantique.fr 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 XA8AHpnxN2hD for ; Tue, 3 Jul 2018 01:45:40 -0700 (PDT) Received: from zproxy110.enst.fr (zproxy110.enst.fr [137.194.2.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93FAD130E45 for ; Tue, 3 Jul 2018 01:45:40 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 70E418152F for ; Tue, 3 Jul 2018 10:45:39 +0200 (CEST) Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id 7Cil7p3Q8Dcb for ; Tue, 3 Jul 2018 10:45:38 +0200 (CEST) Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 0DF2981902 for ; Tue, 3 Jul 2018 10:45:38 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy110.enst.fr 0DF2981902 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1530607538; bh=K4RkkjkMXC1aX8ue6qU2omVLUftI6n2PcoyuHjNPs2U=; h=From:Date:To:Message-Id:Mime-Version; b=C0di3JcoZGx3gZSCTUoYUiWltdcMzr81oCyjqkC5MjnFdrnOPRPOvQunzZxH27R+s 3FNmhqfRqG2+/EBW+xyI/gWk9vdqdRD0hOeHqUzc14WV3cAhSszAY2EsNLU51ewvfF WJZ7GhwyZLT9IR91+ajMShaWFbVchSuyobEwBo2s= X-Virus-Scanned: amavisd-new at zproxy110.enst.fr Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id bTwL8rTUd4Ep for ; Tue, 3 Jul 2018 10:45:37 +0200 (CEST) Received: from [IPv6:2001:660:4701:6001:742e:90aa:d0dd:b166] (unknown [IPv6:2001:660:4701:6001:742e:90aa:d0dd:b166]) by zproxy110.enst.fr (Postfix) with ESMTPSA id D8BB3817CE for ; Tue, 3 Jul 2018 10:45:37 +0200 (CEST) From: "Georgios Z. Papadopoulos" Content-Type: multipart/alternative; boundary="Apple-Mail=_7B502E73-7DB8-4DF3-8365-33310BED2399" Date: Tue, 3 Jul 2018 10:45:36 +0200 References: <153057502225.16048.10821705285334035281.idtracker@ietfa.amsl.com> To: Routing Over Low power and Lossy networks Message-Id: <167124C9-8BCD-4B7B-94CA-92F4E5FF7864@imt-atlantique.fr> Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Archived-At: Subject: [Roll] Fwd: New Version Notification for draft-koutsiamanis-roll-nsa-extension-02.txt X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 03 Jul 2018 08:45:44 -0000 --Apple-Mail=_7B502E73-7DB8-4DF3-8365-33310BED2399 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hello ROLL, The new version of =E2=80=9CRPL DAG Metric Container Node State and = Attribute object type extension=E2=80=9D draft has been submitted. As usual, comments are more than welcome :-) Aris, Georgios, Pascal and Nicolas ____________________________________ Georgios Z. Papadopoulos, Ph.D. Associate Professor, IMT Atlantique, Rennes web: www.georgiospapadopoulos.com = twitter: @gzpapadopoulos = ____________________________________ > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: New Version Notification for = draft-koutsiamanis-roll-nsa-extension-02.txt > Date: July 3, 2018 at 01:43:42 GMT+2 > To: "Nicolas Montavont" , "Pascal = Thubert" , "Georgios Papadopoulos" = , "Remous-Aris Koutsiamanis" = >=20 >=20 > A new version of I-D, draft-koutsiamanis-roll-nsa-extension-02.txt > has been successfully submitted by Remous-Aris Koutsiamanis and posted = to the > IETF repository. >=20 > Name: draft-koutsiamanis-roll-nsa-extension > Revision: 02 > Title: RPL DAG Metric Container Node State and = Attribute object type extension > Document date: 2018-07-03 > Group: Individual Submission > Pages: 12 > URL: = https://www.ietf.org/internet-drafts/draft-koutsiamanis-roll-nsa-extension= -02.txt > Status: = https://datatracker.ietf.org/doc/draft-koutsiamanis-roll-nsa-extension/ > Htmlized: = https://tools.ietf.org/html/draft-koutsiamanis-roll-nsa-extension-02 > Htmlized: = https://datatracker.ietf.org/doc/html/draft-koutsiamanis-roll-nsa-extensio= n > Diff: = https://www.ietf.org/rfcdiff?url2=3Ddraft-koutsiamanis-roll-nsa-extension-= 02 >=20 > Abstract: > Implementing 6TiSCH Packet Replication and Elimination from / to the > RPL root requires the ability to forward copies of packets over > different paths via different RPL parents. Selecting the = appropriate > parents to achieve ultra-low latency and jitter requires information > about a node's parents. This document details what information = needs > to be transmitted and how it is encoded within a packet to enable > this functionality. >=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=_7B502E73-7DB8-4DF3-8365-33310BED2399 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hello ROLL,

The new version of =E2=80=9CRPL DAG Metric Container Node = State and Attribute object type extension=E2=80=9D draft has been = submitted.

As = usual, comments are more than welcome :-)
Aris, = Georgios, Pascal and Nicolas

____________________________________

Georgios Z. = Papadopoulos, Ph.D.
Associate Professor, IMT = Atlantique, Rennes

web:   www.georgiospapadopoulos.com
twitter:  @gzpapadopoulos
____________________________________

Begin forwarded message:

From: = internet-drafts@ietf.org
Subject: = New Version = Notification for draft-koutsiamanis-roll-nsa-extension-02.txt
Date: = July 3, 2018 at 01:43:42 = GMT+2
To: = "Nicolas Montavont" <nicolas.montavont@imt-atlantique.fr>, "Pascal Thubert" = <pthubert@cisco.com>, "Georgios Papadopoulos" <georgios.papadopoulos@imt-atlantique.fr>, "Remous-Aris = Koutsiamanis" <aris@ariskou.com>


A new version = of I-D, draft-koutsiamanis-roll-nsa-extension-02.txt
has = been successfully submitted by Remous-Aris Koutsiamanis and posted to = the
IETF repository.

Name: = draft-koutsiamanis-roll-nsa-extension
Revision: 02
Title:= = RPL DAG Metric Container Node State and Attribute object type = extension
Document date: 2018-07-03
Group:= = Individual Submission
Pages: 12
URL: =            https://www.ietf.org/internet-drafts/draft-koutsiamanis-roll-ns= a-extension-02.txt
Status: =         https://datatracker.ietf.org/doc/draft-koutsiamanis-roll-nsa-ex= tension/
Htmlized: =       https://tools.ietf.org/html/draft-koutsiamanis-roll-nsa-extensi= on-02
Htmlized:       https://datatracker.ietf.org/doc/html/draft-koutsiamanis-roll-n= sa-extension
Diff: =           https://www.ietf.org/rfcdiff?url2=3Ddraft-koutsiamanis-roll-nsa= -extension-02

Abstract:
=   Implementing 6TiSCH Packet Replication and Elimination from = / to the
  RPL root requires the ability to = forward copies of packets over
  different = paths via different RPL parents.  Selecting the appropriate
  parents to achieve ultra-low latency and jitter = requires information
  about a node's parents. =  This document details what information needs
=   to be transmitted and how it is encoded within a packet to = enable
  this functionality.




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=_7B502E73-7DB8-4DF3-8365-33310BED2399-- From nobody Tue Jul 3 03:57:09 2018 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 1FD7C130E5C for ; Tue, 3 Jul 2018 03:57:08 -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=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 7j_EPlLgpLJF for ; Tue, 3 Jul 2018 03:57:06 -0700 (PDT) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 8B0D2130E5A for ; Tue, 3 Jul 2018 03:57:06 -0700 (PDT) Received: by mail-io0-x236.google.com with SMTP id z19-v6so1311449ioh.4 for ; Tue, 03 Jul 2018 03:57:06 -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=W1BDqHq632kRDtV51jS0wVMeAeu78bVwIRufaXmH8MM=; b=gtR7w9UCK1nsCIHbhcDPRKhuNAg6OUC6L8F4EwHwvbkRufrD6oBnJhjkMxJqpQ2Gnb L1bI0YJaeXEcuie9zgn/vbG/j2hr2P8RrzeaQwrwNXoecgorY0P9IpC9xYc04d3LLCfM sP7H4cYdYocOOo+n7CihSzfLyO/k6/tyGQNUtO5YYr/xyaa27bqq+5X5Cm0Ris/icIah zU8gU30JIkobBw2bKQM2VzWwxooU1YL65YPeOwSy8J2zRIF4YwTV+57BlPbRdAnoCPMh 2SjY9mB/xRWrfXSuf/RmFm3ox5+V5R2mvN4zNI+Z6NaSqEi7GvxSFEt76FnH+GmPngNT tpgA== 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=W1BDqHq632kRDtV51jS0wVMeAeu78bVwIRufaXmH8MM=; b=Q1bfNdyPqRv/HlZ2PySefj/s8sZzSlcE556z0AMVGUMC4Qn0NDi1LQBjgIPDsCAZmW Mq8+5h0uwiOmZZiN4E9n4TUUND2gvL6afmnB8PB/rvOrE8u5aBJjhUt9MOM9hQFRC5SO 9gd3SlrDXUlO0sKSeYBp+Wnjo21VfqQtrKZ547V0hYcdNrp3p1y+0ksFGO9pSFKaGYJf qII+nb3QkezcMp8UooY2I7TjjWgQjnzHjzrYzjbKBpoCToozI6nwyDMXVmAPmiCEUuLn 74BWo6BQZYWNEUMf4WlFCNyC4yA6zKOLEztWPgrW6axac9n/1YuHblQJFi98kYHpxJPH sarw== X-Gm-Message-State: APt69E0YTagju9FelH6Ht5ctUE4SKoQElndVXJ2oo18ILvyuibOThRDM z8wuL90rDRJOVFcMfI4z5X/UCQ/XRhguN88LmvdlHQ== X-Google-Smtp-Source: AAOMgpfnn+J1eMLHpk/HuM+VgQKUPM87/Q1KoNeYIe9kuXnmEvw9bQQEhKPzHHOdq/kIRHCAa11vydlodHhzuUn0ngw= X-Received: by 2002:a6b:2353:: with SMTP id j80-v6mr21788697ioj.99.1530615425432; Tue, 03 Jul 2018 03:57:05 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 03:57:04 -0700 (PDT) From: Ines Robles Date: Tue, 3 Jul 2018 13:57:04 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="000000000000b880060570162c63" Archived-At: Subject: [Roll] Call for adoption for draft-rahul-roll-rpl-observations X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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: Tue, 03 Jul 2018 10:57:08 -0000 --000000000000b880060570162c63 Content-Type: text/plain; charset="UTF-8" Dear all, This is the call for adoption for "RPL Observations"- draft-rahul-roll-rpl-observations-01. This call for adoption finalizes on 20th July. Please read the draft and reply to the list with your comments, remarks, suggestions and votes on the adoption of this document. Many thanks, Ines and Peter --000000000000b880060570162c63 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

This is the call f= or adoption for "RPL Observations"- draft-rahul-roll-rpl-observat= ions-01. This call for adoption finalizes on 20th July.

Please read the draft and reply to the list with your comments, remar= ks, suggestions and votes on the adoption of this document.

<= /div>
Many thanks,

Ines and Peter
--000000000000b880060570162c63-- From nobody Tue Jul 3 09:04:42 2018 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 73125130FA9; Tue, 3 Jul 2018 09:00:20 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: roll@ietf.org, aretana.ietf@gmail.com X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153063362040.4893.14612045170518576197.idtracker@ietfa.amsl.com> Date: Tue, 03 Jul 2018 09:00:20 -0700 Archived-At: Subject: [Roll] roll - Requested session has been scheduled for IETF 102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jul 2018 16:00:31 -0000 Dear Ines Robles, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. roll Session 1 (2:30 requested) Tuesday, 17 July 2018, Morning Session I 0930-1200 Room Name: Duluth size: 150 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/102/sessions/roll.ics Request Information: --------------------------------------------------------- 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.5 Hours Number of Attendees: 50 Conflicts to Avoid: First Priority: anima manet 6tisch core ace Second Priority: rtgarea 6lo 6man lwig cbor t2trg Third Priority: rtgwg intarea lpwan People who must be present: Michael Richardson Peter Van der Stok Alvaro Retana Ines Robles Resources Requested: Special Requests: Meetecho Support --------------------------------------------------------- From nobody Wed Jul 4 02:21:03 2018 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 36916130E42 for ; Wed, 4 Jul 2018 02:21:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 EDC0zVvTLR_3 for ; Wed, 4 Jul 2018 02:21:00 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0005.hostedemail.com [216.40.44.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18089130E3F for ; Wed, 4 Jul 2018 02:21:00 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id 66DCE837F27D for ; Wed, 4 Jul 2018 09:20:58 +0000 (UTC) X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :, RULES_HIT:41:72:152:355:379:582:800:962:967:973:983:988:989:1152:1189:1208:1221:1260:1263:1313:1314:1345:1381:1431:1436:1437:1516:1517:1518:1534:1540:1566:1575:1588:1589:1592:1594:1711:1714:1730:1776:1792:2525:2561:2564:2682:2685:2829:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3586:3622:3865:3867:3868:3870:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4659:5007:6261:6298:6659:8603:9015:9025:9177:9388:10004:10214:10400:10848:11232:11658:11914:12043:12555:12679:12895:12986:13071:13139:13199:13229:13439:13846:14096:14180:14181:14721:21060:21080:21433:21451:21625:21691:30048:30054, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:25, LUA_SUMMARY:none X-HE-Tag: train54_874289c90247 X-Filterd-Recvd-Size: 2438 Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf09.hostedemail.com (Postfix) with ESMTPA for ; Wed, 4 Jul 2018 09:20:58 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_caec613962259ae6d9653364f7fe0b03" Date: Wed, 04 Jul 2018 11:20:57 +0200 From: Peter van der Stok To: Roll Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org Message-ID: <8a7489c211ef4a08a8f40a1916938705@bbhmail.nl> X-Sender: stokcons@bbhmail.nl User-Agent: Roundcube Webmail/1.2.7 X-Originating-IP: [82.95.140.48] Archived-At: Subject: [Roll] Roll meeting during iet102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jul 2018 09:21:03 -0000 --=_caec613962259ae6d9653364f7fe0b03 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi ROLL, We are preparing the slides and the agenda for the ROLL meeting in Montreal. Two subjects needs to be filled in the slides that concern us all: Who volunteers to be minute taker or jabber scribe. Please tell us. Ines and Peter -- Peter van der Stok vanderstok consultancy mailto: consultancy@vanderstok.org www: www.vanderstok.org [1] tel NL: +31(0)492474673 F: +33(0)966015248 Links: ------ [1] http://www.vanderstok.org --=_caec613962259ae6d9653364f7fe0b03 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi ROLL,

We are preparing the slides and the agenda for the ROLL= meeting in Montreal.
Two subjects needs to be filled in the slides th= at concern us all:

Who volunteers to be minute taker or jabber s= cribe.

Please tell us.

Ines and Peter
--
= Peter van der Stok
vanderstok consultancy
mailto: consultancy@vanderstok.org
www: = = www.vanderstok.org
tel NL: +31(0)492474673    &nbs= p;F: +33(0)966015248
--=_caec613962259ae6d9653364f7fe0b03-- From nobody Wed Jul 4 02:38:25 2018 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 BC624130E42 for ; Wed, 4 Jul 2018 02:38:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 opDipCfpfT8P for ; Wed, 4 Jul 2018 02:38:20 -0700 (PDT) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 BDA56130DC4 for ; Wed, 4 Jul 2018 02:38:20 -0700 (PDT) Received: by mail-io0-x236.google.com with SMTP id l25-v6so4296063ioh.12 for ; Wed, 04 Jul 2018 02:38:20 -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=QQs5IbKdJCpvNpPkBkbBYA8CUaslUFQYQ7QkcqB01P4=; b=bw4cjkgfdLt1UUVoqJJWv2LJ6HvD2THrbU2cPGWQ6qWKE31LnT7A+4LA/HKp2oBcDz 7InrdRzfrxDbBHFU6YJmPtnHi3fr7uXDdebq3qBsnfyBf4OeEauN7B0hksx4vl5sdVRG LFFAQ+uWHna2CMp+OAMLM2kZNcPdsoSL/1IHe47fwj84c2gxMLmAIJueqDog7BCMBjSr TOzgDKEwogcuXJPAAtr6ed9vNeQe9ZUqzUULxeMzSAEO4gS+j3qYtoDYQxoEeV62nWP+ ZtYsRSVdH29Q1xObLqp+lvklOzS3LMXHnTCCVUzsQPzxm/G759lfPNS1nVFftnki3zqP wKcg== 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=QQs5IbKdJCpvNpPkBkbBYA8CUaslUFQYQ7QkcqB01P4=; b=FSqVI2vyLqYLS37oFeGQaAPOOUtql30gGtZfYpbVacqm7zPZwGv7piZaH35j1tUHZ/ o4JyRD8ikvjiwF3uZr5xfDjQcj4VHpnXgvKlMniy9/JUn2GMvsKhP/BUKD+uyLHtsYj/ tmvzlG41l2KYNK9pfozV7bzSz4Arvb4MkviWR4YO/rY7jc4YIkKfobERy+nj4wW413uy 0hJqmQSdx5uUQszv90MA8rsOl9LTe/s7ZgUtLFmucK41tDTUdXEVhO7dJ8PN7bFAzglR 6aZbwn93SFxK8HBWmhGN9pBvv6oktgdveVbDwAN+ZBOxcgGGMzKnTPTk1LBP7z5+/h3W 9sLQ== X-Gm-Message-State: APt69E1cRFE/s1hGQ6nwUBOduP9HuEWnAfERqibOk82j7iHpCyzjQ9eh ObUmfTza+GZQDzXktjGSBNLXJzMvpH8t35W29mIK2g== X-Google-Smtp-Source: AAOMgpc6a6jVVQJZMAKojVIUfTM7bFUfZg4QgYdTJhuIS5fTnI8IKonnlr8lgdjAXpXhBsgq260oUofzylHTZv5/vhg= X-Received: by 2002:a6b:2353:: with SMTP id j80-v6mr842112ioj.99.1530697099494; Wed, 04 Jul 2018 02:38:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 02:38:18 -0700 (PDT) From: Ines Robles Date: Wed, 4 Jul 2018 12:38:18 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="000000000000dfc9d7057029305c" Archived-At: Subject: [Roll] WGLC for draft-ietf-roll-aodv-rpl-04 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jul 2018 09:38:23 -0000 --000000000000dfc9d7057029305c Content-Type: text/plain; charset="UTF-8" Dear all, A Working Group Last call (WGLC) starts today (04/07) until 20/07 for draft-ietf-roll-aodv-rpl-04 The draft is available here: https://datatracker.ietf.org/doc/draft-ietf-roll-aodv-rpl/ Please review this draft to see if you think that it is ready for publication and send comments to the list stating your view. Thank you very much in advance, Peter and Ines. --000000000000dfc9d7057029305c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,=C2=A0
A Working Group Last call (WGLC) starts today (04/0= 7) until 20/07 for draft-ietf-roll-aodv-rpl-04

The draft is available here:=C2=A0

Please review this draft to see if you think that it is read= y for publication and send comments to the list stating your view.=C2=A0


T= hank you very much in advance,

Peter and Ines.

--000000000000dfc9d7057029305c-- From nobody Wed Jul 4 02:41:00 2018 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 AA719130E46 for ; Wed, 4 Jul 2018 02:40:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 qM3CbOMKtRtV for ; Wed, 4 Jul 2018 02:40:57 -0700 (PDT) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 D7BA2130DC4 for ; Wed, 4 Jul 2018 02:40:56 -0700 (PDT) Received: by mail-it0-x22b.google.com with SMTP id a195-v6so6975262itd.3 for ; Wed, 04 Jul 2018 02:40:56 -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; bh=qO2fujsavsVtKhOeZhb188ssUnYVewDWAgeqr29d+YI=; b=U9AJXWRN4WilviR91E8/Z7SOJXinRBucxx6Gq14bV3+0G3z6lP5WiuamzNDRiiy4AS Py+xpxtV3YJ/8QgcmBcnqvCe37CICxOM75zZL18SxWe35nbR22ZPET6wq/uuCCzKrsOf pfDCvnPPVI6R0OTFwr5+EhOFF8QWBw7T57gk8MERY1FTPXB6AEq8d1f8ovWgKEU6OYyO hmCg92Sf2yXAAfb6YgjfHhPfn57di8Ae6mGeUHuVliXLA3Uxo8xhLdoye7k2NxN/qANG CpJLQsE93VaFTf4flwy8UD86vrHbwyJFAkz8rOEDl+goAlafcfe6pMB/EdHCqp1AM/MP 8lgQ== 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; bh=qO2fujsavsVtKhOeZhb188ssUnYVewDWAgeqr29d+YI=; b=bt2jkE29cC+k3GlpCYF5Qy74xJBIh6SEe+Fej/JZR5I94/maV07RpJ5mbYVP1FaWnu 0z2eLopy+hMLDHp+qOJYPAie4eUqVirNHHmGmZSUL9TV8tX7a/YtxwyHvKLZfxwJNuZR RbYnMS8shxf2XqWYpwDmpFD+uTlnjYRzFHP5e1+aDP5ClMbEZBd8qrHfDYfmWmuPFBQt 1xD3ktnk769Aoz8lXLAr9Rw7fnd8RE91fW73XLZeXDn2qT8di16iIjyguQXKO9BCoao+ PjZ8bn+xD2RJvKU6Df/8iy3Ul5HKoYchvCSRoTEERHXKP1w1vwaO4lyNIfpkxkcivV3q +XKw== X-Gm-Message-State: APt69E1t+Jrtd3TpjbrgX4dqh8V8DTqv+wl1rYHEE3MgDTmoPUGm2wIe lH22f2N/p6b33hGrwkHPNmFw6awVyALavZtzMCBgpA== X-Google-Smtp-Source: AAOMgpeEb3QTfDYdshqiJnVuBVroQXqxNYaQQtJ8iVvVcQmRTE4z59tmBvV39VP288kHXKMkj4f+WT7DZYEpebn9VwA= X-Received: by 2002:a02:1bdc:: with SMTP id 89-v6mr949003jas.72.1530697255526; Wed, 04 Jul 2018 02:40:55 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 02:40:54 -0700 (PDT) From: Ines Robles Date: Wed, 4 Jul 2018 12:40:54 +0300 Message-ID: To: roll , consultancy@vanderstok.org Content-Type: multipart/alternative; boundary="0000000000002ca58b0570293a99" Archived-At: Subject: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jul 2018 09:40:59 -0000 --0000000000002ca58b0570293a99 Content-Type: text/plain; charset="UTF-8" Dear all, A Working Group Last call (WGLC) starts today (04/07) until 20/07 for draft-ietf-roll-efficient-npdao-03 The draft is available here: https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ Please review this draft to see if you think that it is ready for publication and send comments to the list stating your view. Thank you very much in advance, Ines and Peter --0000000000002ca58b0570293a99 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,=C2=A0
A Working Group Last call (WGLC) starts today (04/0= 7) until 20/07 for=C2=A0draft-ietf-roll-efficient-npdao-03
<= br>
The draft is available here:=C2=A0

Please review this draft to see if you think that it is ready for pu= blication and send comments to the list stating your view.=C2=A0


Thank you= very much in advance,

Ines and Peter
--0000000000002ca58b0570293a99-- From nobody Wed Jul 4 09:04:33 2018 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 68402130E19 for ; Wed, 4 Jul 2018 09:04:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 921oeQIKh_EU for ; Wed, 4 Jul 2018 09:04:28 -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 19E12130E50 for ; Wed, 4 Jul 2018 09:04:28 -0700 (PDT) Received: by mail-io0-x232.google.com with SMTP id q9-v6so5274086ioj.8 for ; Wed, 04 Jul 2018 09:04:28 -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=+H/huU7mp3GTLEehBnMASCcX1f3EgaNEoAhrx1fFsTg=; b=MbOWLw6HFqr59K0faor60pHvDiy6tFsig9y/6unYGjDzUSW+Y0Q3btVbBMEPwzWEOI tlzAWqe9Y13rNpASwxoq4gQDEydvbvD+DpTGnFS7geDSc+u0d1Wci5lXEi2CFQY/5X7m myp9sosWfAL8faS94mvbXnDs6h46ingpixB84StfbzyLdkltGzfmRza3Recs1E4r5+6x 6qlRPhmO4wfQwrJjVu/PNMbfrREFyhC6oOgimO3hKKq+LNuZSQ8vyk7KiNiHeUFfY0zd jj6e3PK5r9upVo/DYp1gOrZaUSguTXGALZFyhhmUYwGDXhDTknXFFhQXetLWoBX59b/A ZxgQ== 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=+H/huU7mp3GTLEehBnMASCcX1f3EgaNEoAhrx1fFsTg=; b=XOT9C2MHj4xplpmT8YCp+3s5kM4pzBiCBnOPnnKK0ClhiIc7uqBrY67GsulHbgrT9f 8/2Cs1PfKro1kXEDZQCCmeK+bzHUW3mhGyxocnvtW2B7Rzr6R5LDXjFeYLb1EPtZudvi m0H9VgO+7sPDhTIjspkiepRvzYQduHbDOyd/Zz4DhK9v9SiYe2vm1pRrNKGOlaXwu4sh cjLZxqVZrdjMlcthZglrmP4Uboq5wBPpR4CepLB1ccUAURdgoJpnVCpOwCq9iPO+09Ul h8r6XxAM9oDByl7+UPNqHS5Krq4Ycj+Z3D9tx3ahnhq8SL6xBbZraGrhTb85IRgN8ytC AGNw== X-Gm-Message-State: APt69E2V2ou7UnUKmoj1hXn3g7Bj4A2+cUSl/970sP6b+T6nQJolQFuF yQpBXIB1C+59g5zCCObB0p1QAcY+VCuT+EvsZ9IBVQ== X-Google-Smtp-Source: AAOMgpfR+73e4+lPdNE26jZp0pR4CHpIts3Yt/4ZPoJS4TnL8WiNplDoWuX95zBR6ZEzckl5gzimvpOtbrX4zNJZJDg= X-Received: by 2002:a6b:bf04:: with SMTP id p4-v6mr2040374iof.15.1530720266683; Wed, 04 Jul 2018 09:04:26 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 09:04:26 -0700 (PDT) From: Ines Robles Date: Wed, 4 Jul 2018 19:04:26 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="000000000000bf0b2005702e9555" Archived-At: Subject: [Roll] Agenda for IETF 102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jul 2018 16:04:32 -0000 --000000000000bf0b2005702e9555 Content-Type: text/plain; charset="UTF-8" Dear all, Please find a first version of the agenda for the ROLL meeting at IETF 102 https://datatracker.ietf.org/meeting/102/materials/agenda-102-roll-00 Comments welcome :) Thanks, Ines and Peter --000000000000bf0b2005702e9555 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

Please find a first version o= f the agenda for the ROLL meeting at IETF 102



Thanks,

--000000000000bf0b2005702e9555-- From nobody Wed Jul 4 09:14:29 2018 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 0B802130DE1 for ; Wed, 4 Jul 2018 09:14:27 -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=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 yteXQjVc9V-1 for ; Wed, 4 Jul 2018 09:14:25 -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 9003C12785F for ; Wed, 4 Jul 2018 09:14:25 -0700 (PDT) Received: by mail-it0-x22e.google.com with SMTP id 16-v6so8414887itl.5 for ; Wed, 04 Jul 2018 09:14:25 -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=LZJT+sBrwsjs3mJMgm2AscUOYahA4HkH63Aq46W+EhU=; b=NzUtE6uquiP19IzAgLwca2QlI5SYq+k7sVnLsYysaL//zkNsNHcmcUUXmAL5qmXZfv 4KPn2sKtrGiQJGgi+hJQT1uhg+a9D3j1hLaSTCUA5qL6qvPhpQsNwoWqcGG+YY86QTma 9LUnimxGgOPy/srl9n37Y1tNCD3AANcDAOEU6KgoFkRP1aKMIRg1mPVYE+HDH1J4t6yO r2SG8fHP7+a2J4nDP2hSj8jRAzdKc6ymC9GTjkGuFMleQmHfGFe+P/ja3ObfJupJA9Ub dfI8EBVeualCZuq2r3xhep8P5CtqM33IJRshDTTv9+QmZRaubrdBYXHXdVNYk+VY/dp1 Sgng== 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=LZJT+sBrwsjs3mJMgm2AscUOYahA4HkH63Aq46W+EhU=; b=JNpeqorJ1hvo9hGqmohGrRaoWJzr+PGQSv5sHwUyLhMzEx09bU5t7EKtR6p7AdlEcT ImO6Co4UmgsIcBkOgAaNT7Yd3KTbL0VIqMZou5LogRlmQvgqYy9/p2jVgTDayVhSIWON E4FfzVsEc9JBiRd1/SK1SuEQjuiedV9sohwOGWleRvpGOnT9RUTFJYkYLy6tVU1l+Sin xJf9xwhv7WpHaKQ78VweAgJLGPsGI1lD3suGIpnc41Fcg1Qeiz4AJ7JEQ37EPtGLRAmz VRxqzlaGltwwbV7LbTqaKEOkgx8v4NRyaR2Z8k2QWEhv9KYFgAznyE4QS3D0LbMq2rwy P+zA== X-Gm-Message-State: APt69E2oVOfgCot/BL9EvkMucP5NnAp6pCoqoaRvyCrJee/CGtp1UK1/ KZCGNFaGBpUITezSgVCpKi6WE/7AlceCy4KFxTY= X-Google-Smtp-Source: AAOMgpd/cWSy+C72J34DsioIyHwRVobSaAtALl1eDjbZse4tx280O7aJ9nEjl5/u7Dz5xVjx4dUWY8Nptb7zQ9EAnAw= X-Received: by 2002:a24:1f14:: with SMTP id d20-v6mr2175596itd.83.1530720864365; Wed, 04 Jul 2018 09:14:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Wed, 4 Jul 2018 09:14:23 -0700 (PDT) From: Ines Robles Date: Wed, 4 Jul 2018 19:14:23 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="0000000000005eff5405702eb922" Archived-At: Subject: [Roll] Slides for IETF 102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.26 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, 04 Jul 2018 16:14:28 -0000 --0000000000005eff5405702eb922 Content-Type: text/plain; charset="UTF-8" Dear Presenters, Please send us the slides (pdf format) to be presented at the IETF no later than Friday 12th July. Thank you, Ines and Peter. --0000000000005eff5405702eb922 Content-Type: text/html; charset="UTF-8"
Dear Presenters,

Please send us the slides (pdf format) to be presented at the IETF no later than Friday 12th July.

Thank you,

Ines and Peter.
--0000000000005eff5405702eb922-- From nobody Sat Jul 14 13:16:45 2018 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 36C48130E4D for ; Sat, 14 Jul 2018 13:16:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 v8i19RZe0rVa for ; Sat, 14 Jul 2018 13:16:42 -0700 (PDT) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 8BB5712F1A5 for ; Sat, 14 Jul 2018 13:16:42 -0700 (PDT) Received: by mail-it0-x22b.google.com with SMTP id j185-v6so15950477ite.1 for ; Sat, 14 Jul 2018 13:16:42 -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=TAXXvlmSrbjBEwuqnvNgUZMQoNbvnOtqWkh8gQPgctc=; b=AARYKArwevv6/bZ4zT5jxZ8q9Q5wbvnHtE8q8W9qtJ1adAvdrAx5EYz+wp+NTuVhjO Xs4dK11so5dyDVNsAYkwseWnBlfZS1nyy2B+udBximv8Ti5YWgkuiTC32IwxLSTTDXRA 7ipWIW/c6NAurOwnSuJOg0uW2LRDG6idS/jS9lHS8HbnnEWloPrwz0aGC7W2g7MIUdd5 EEJAC8hI2+21dWmTOirEmsEm8X2k4+h8tzRADAGOvB+DSktKtzmlu7hJRLOA368o8cjF I5hdCiYtHUa6cuzodxS2gjYn1iyfmsF3h0L2VatOowDEa7ErU8waBg/RY0MmgrmlwiQy 2Zwg== 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=TAXXvlmSrbjBEwuqnvNgUZMQoNbvnOtqWkh8gQPgctc=; b=E72IiYsdRYkzvZ5js0s0JgqzTT7mPxeHujjyXwXqeY4K3rDKE2ahc2D3fStf1AtbEe 5a9ky4iZlbcAGQ6jVS42IBFZ35tQCadXdSHVs7k/PLpUPs5c1quvY32mrI6xs8MazAy+ /bugc1L1Bwyh8j8fwGA1d7Vbm1RTUTNEwBGMlWd8Rebt6YFW4oXj53nQ/h616f+UHm7L BWRoJ56zoAydZNHWIL69YJhQOua4FejzhsiGRT0b1ZMyV3vMCAYmRes0wB2eRsmzlon/ Gdggew29BWjw0crLjoWrFg7CEdY8z1kxdmuBfUNJy+Z2sAeFBH/k/+R70cFeavHnsXZW pnwA== X-Gm-Message-State: AOUpUlFKrTa1stn5PQanWf2feRfPYjzoFc2ACcV7TMoogpElaMfdEpRK cniRY12EKXQTP2Rngdx5iRDqsyGjiGtx3iGp/IR3hA== X-Google-Smtp-Source: AAOMgpfrt9N9VDoCdPlxYn9yI9NjeWuZuOmsOdaDk2WC30Md9/Ia5B/muNgbNBnX++p+jhvdbUNShBjThSOqzYQtln4= X-Received: by 2002:a02:1bdc:: with SMTP id 89-v6mr9363953jas.72.1531599401446; Sat, 14 Jul 2018 13:16:41 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Sat, 14 Jul 2018 13:16:40 -0700 (PDT) From: Ines Robles Date: Sat, 14 Jul 2018 23:16:40 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="00000000000042ef7d0570fb46fa" Archived-At: Subject: [Roll] Slides - agenda - IETF 102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 14 Jul 2018 20:16:44 -0000 --00000000000042ef7d0570fb46fa Content-Type: text/plain; charset="UTF-8" Dear all, Please find: - The agenda https://datatracker.ietf.org/meeting/102/materials/agenda-102-roll-02 - A draft version of the slides https://datatracker.ietf.org/meeting/102/materials/slides-102-roll-roll-ietf102-v1-00 Comments welcome, Thanks, Ines and Peter --00000000000042ef7d0570fb46fa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

Please find:
 --00000000000042ef7d0570fb46fa-- From nobody Sun Jul 15 03:29:29 2018 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 382C7130EAC; Sun, 15 Jul 2018 03:29:28 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: roll@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153165056819.21623.3967136787870814938@ietfa.amsl.com> Date: Sun, 15 Jul 2018 03:29:28 -0700 Archived-At: Subject: [Roll] I-D Action: draft-ietf-roll-mpl-yang-02.txt X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jul 2018 10:29:28 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Over Low power and Lossy networks WG of the IETF. Title : A YANG model for Multicast Protocol for Low power and lossy Networks (MPL) Author : Peter van der Stok Filename : draft-ietf-roll-mpl-yang-02.txt Pages : 30 Date : 2018-07-15 Abstract: This document defines a YANG data model for management of Multicast Protocol for Low power and lossy Networks (MPL) implementations. The data model includes configuration data and state data. Note Discussion and suggestions for improvement are requested, and should be sent to roll@ietf.org. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-roll-mpl-yang/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-roll-mpl-yang-02 https://datatracker.ietf.org/doc/html/draft-ietf-roll-mpl-yang-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-mpl-yang-02 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Jul 15 03:33:30 2018 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 58B38130EAC; Sun, 15 Jul 2018 03:33:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.919 X-Spam-Level: X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] 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 e_hp7zElPjtC; Sun, 15 Jul 2018 03:33:25 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0182.hostedemail.com [216.40.44.182]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39560130E23; Sun, 15 Jul 2018 03:33:25 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay04.hostedemail.com (Postfix) with ESMTP id 36BF0180A812D; Sun, 15 Jul 2018 10:33:24 +0000 (UTC) X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C X-Spam-Summary: 2, -8.5, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::, RULES_HIT:41:72:152:355:379:582:599:800:962:967:973:983:988:989:1049:1152:1189:1208:1212:1221:1260:1313:1314:1345:1431:1436:1437:1516:1517:1518:1535:1543:1575:1588:1589:1592:1594:1711:1730:1777:1792:2068:2069:2198:2199:2288:2328:2525:2528:2553:2559:2568:2570:2633:2682:2685:2703:2741:2771:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3353:3622:3865:3866:3867:3868:3870:3871:3872:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4118:4250:4321:4605:4860:5007:6117:6119:6261:6298:7875:7903:8603:9010:9025:9177:10004:10400:11658:12379:12740:13139, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:24, LUA_SUMMARY:none X-HE-Tag: ink82_74fc83eca8e54 X-Filterd-Recvd-Size: 7134 Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf01.hostedemail.com (Postfix) with ESMTPA; Sun, 15 Jul 2018 10:33:23 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_68b52e6814a146912cc11181d12422da" Date: Sun, 15 Jul 2018 12:33:23 +0200 From: Peter van der Stok To: Routing Over Low power and Lossy networks Cc: i-d-announce@ietf.org Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org In-Reply-To: <153165056819.21623.3967136787870814938@ietfa.amsl.com> References: <153165056819.21623.3967136787870814938@ietfa.amsl.com> Message-ID: X-Sender: stokcons@bbhmail.nl User-Agent: Roundcube Webmail/1.2.7 X-Originating-IP: [31.133.147.176] Archived-At: Subject: Re: [Roll] I-D Action: draft-ietf-roll-mpl-yang-02.txt X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Sun, 15 Jul 2018 10:33:29 -0000 --=_68b52e6814a146912cc11181d12422da Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi Roll, A late submission of the mpl yang draft. Changes from version 01 to version 02 o Added NMDA section. o added module explanation in model section; modules are enhances of domain module o IANA considerations added Peter internet-drafts@ietf.org schreef op 2018-07-15 12:29: > A New Internet-Draft is available from the on-line Internet-Drafts directories. > This draft is a work item of the Routing Over Low power and Lossy networks WG of the IETF. > > Title : A YANG model for Multicast Protocol for Low power and lossy Networks (MPL) > Author : Peter van der Stok > Filename : draft-ietf-roll-mpl-yang-02.txt > Pages : 30 > Date : 2018-07-15 > > Abstract: > This document defines a YANG data model for management of Multicast > Protocol for Low power and lossy Networks (MPL) implementations. The > data model includes configuration data and state data. > > Note > > Discussion and suggestions for improvement are requested, and should > be sent to roll@ietf.org. > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-roll-mpl-yang/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-roll-mpl-yang-02 > https://datatracker.ietf.org/doc/html/draft-ietf-roll-mpl-yang-02 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-mpl-yang-02 > > 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. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll --=_68b52e6814a146912cc11181d12422da Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi Roll,

A late submission of the mpl yang draft.

Changes from version 01 to version 02

   o  = Added NMDA section.

   o  added module explanat= ion in model section; modules are enhances of domain module

&n= bsp;  o  IANA considerations added

Peter

internet-drafts@ietf.org schreef op 2018-07-15 12:29:

=
A New Internet-Draft is available from the on-line Internet-Drafts d= irectories.
This draft is a work item of the Routing Over Low power a= nd Lossy networks WG of the IETF.

     = ;   Title         &n= bsp; : A YANG model for Multicast Protocol for Low power and lossy Net= works (MPL)
        Author &n= bsp;        : Peter van der Stok     Filename       &n= bsp;: draft-ietf-roll-mpl-yang-02.txt
    Pages &= nbsp;         : 30
 = ;   Date         &nb= sp;  : 2018-07-15

Abstract:
   T= his document defines a YANG data model for management of Multicast
&n= bsp;  Protocol for Low power and lossy Networks (MPL) implementat= ions.  The
   data model includes configuration d= ata and state data.

Note

   Discussi= on and suggestions for improvement are requested, and should
 &n= bsp; be sent to ro= ll@ietf.org.


The IETF datatracker status page for thi= s draft is:
https://datatracker.ietf= =2Eorg/doc/draft-ietf-roll-mpl-yang/

There are also htmlize= d versions available at:
https://tools= =2Eietf.org/html/draft-ietf-roll-mpl-yang-02
https://datatracker.ietf.org/doc/html/draft-ietf-roll-mp= l-yang-02

A diff from the previous version is available at:=
https://www.ietf.org/rfcdiff?ur= l2=3Ddraft-ietf-roll-mpl-yang-02


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

Intern= et-Drafts are also available by anonymous FTP at:
ftp://ft= p.ietf.org/internet-drafts/

_______________________________= ________________
Roll mailing list
Roll@ietf.org
https://= www.ietf.org/mailman/listinfo/roll
--=_68b52e6814a146912cc11181d12422da-- From nobody Mon Jul 16 03:53:58 2018 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 D74AC130E50 for ; Mon, 16 Jul 2018 03:53:56 -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, HTML_MESSAGE=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 (1024-bit key) header.d=imt-atlantique.fr 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 eKNJ5C699JAp for ; Mon, 16 Jul 2018 03:53:53 -0700 (PDT) Received: from zproxy110.enst.fr (zproxy110.enst.fr [137.194.2.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DBD8130DF0 for ; Mon, 16 Jul 2018 03:53:53 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 7F007811D9; Mon, 16 Jul 2018 12:53:50 +0200 (CEST) Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id sKXgxrosB85X; Mon, 16 Jul 2018 12:53:49 +0200 (CEST) Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id CEB2D81630; Mon, 16 Jul 2018 12:53:49 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy110.enst.fr CEB2D81630 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1531738429; bh=bwNeYHCOO63l6Mk5hQX88rjbFYuBOJzJFxoJDbJspy8=; h=Mime-Version:From:Date:Message-Id:To; b=cpCC/79Q6L76lJn/byoxB2XyFDoxLoFfYMBmnINvxuuDYy03AfySi7d8uO2TrdRo4 7L4hkGI/rppEgxK4xRkch+JIn8etPrWf/14gWVjJ8Xk/cXMcvo3WB/fvZ/cGxmZSPX 7K8eQvmqrH1KcPEggH6IqE1e5d4Rusbi/EmCYUBs= X-Virus-Scanned: amavisd-new at zproxy110.enst.fr Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id LfyvPcmrAWfs; Mon, 16 Jul 2018 12:53:49 +0200 (CEST) Received: from [192.168.1.3] (ppp005054255208.access.hol.gr [5.54.255.208]) by zproxy110.enst.fr (Postfix) with ESMTPSA id DA21F811D9; Mon, 16 Jul 2018 12:53:48 +0200 (CEST) Content-Type: multipart/alternative; boundary="Apple-Mail=_0087EFB3-B9D2-46A4-BEAE-26D7EC429D55" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: "Georgios Z. Papadopoulos" In-Reply-To: Date: Mon, 16 Jul 2018 13:53:46 +0300 Cc: Routing Over Low power and Lossy networks , Ines Robles , peter van der Stok Message-Id: References: To: Rahul Jadhav , "Pascal Thubert (pthubert)" X-Mailer: Apple Mail (2.3124) Archived-At: Subject: Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 16 Jul 2018 10:53:57 -0000 --Apple-Mail=_0087EFB3-B9D2-46A4-BEAE-26D7EC429D55 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Dear Roll, Rahul and co-authors, I find this proposal useful, and quite ready to go. Please find my (perhaps minor) comments below. =E2=80=94 =E2=80=94 [1] 1.2. Current No-Path DAO messaging "Subsequently parents or ancestors would release any resources (such as = the routing entry) it maintains on behalf of target node.=E2=80=9D [GP] What could be other type of resources, apart from a routing entry, = that a parent or ancestors may release?=20 Could you provide some more examples? [2] 3.1. Req#1: Tolerant to link failures to the previous parents =E2=80=9CTherefore, it is required that the NPDAO message MUST be = tolerant to the link failure during the switching.=E2=80=9D [GP] How it can be tolerant, when there is a link failure? What could be = the potential means to be tolerant? [3] 4.1. Change in RPL route invalidation semantics =E2=80=9CThe trigger for the common ancestor node to generate this DCO = is the change in the next hop for the target on reception of an update = message in the form of regular DAO for the target.=E2=80=9D [GP] I am having some troubles to understand this sentence, is it = possible to be rephrased? [4] 4.3. Destination Cleanup Object (DCO) =E2=80=9CThe DCO message always traverses downstream and cleans up route = information and other state information associated with the given = target.=E2=80=9D [GP] Similar to comment [1], is it possible to give some examples of = state information? =E2=80=94 =E2=80=94=20 Best, Georgios ____________________________________ Georgios Z. Papadopoulos, Ph.D. Associate Professor, IMT Atlantique, Rennes web: www.georgiospapadopoulos.com = twitter: @gzpapadopoulos = ____________________________________ > On Jul 4, 2018, at 11:40, Ines Robles = wrote: >=20 > Dear all,=20 >=20 > A Working Group Last call (WGLC) starts today (04/07) until 20/07 for = draft-ietf-roll-efficient-npdao-03 >=20 > The draft is available here:=20 > https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ = >=20 > Please review this draft to see if you think that it is ready for = publication and send comments to the list stating your view.=20 >=20 >=20 > Thank you very much in advance, >=20 > Ines and Peter > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll --Apple-Mail=_0087EFB3-B9D2-46A4-BEAE-26D7EC429D55 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Dear Roll, Rahul and co-authors,

I find this proposal useful, = and quite ready to go.
Please = find my (perhaps minor) comments below.
=E2=80=94= =E2=80=94

[1] = 1.2. Current No-Path DAO messaging
"Subsequently = parents or ancestors would release any resources (such as the routing = entry) it maintains on behalf of target node.=E2=80=9D

[GP] What could be other = type of resources, apart from a routing entry, that a parent or = ancestors may release? 
Could you provide some = more examples?


[2] 3.1. Req#1: = Tolerant to link failures to the previous parents
=E2=80=9CTherefore, it is required that the NPDAO message = MUST be tolerant to the link failure during the switching.=E2=80=9D
<= div class=3D"">
[GP] How it can be = tolerant, when there is a link failure? What could be the potential = means to be tolerant?


[3] 4.1. Change in RPL = route invalidation semantics
=E2=80=9CThe trigger = for the common ancestor node to generate this DCO is the change in the = next hop for the target on reception of an update message in the form of = regular DAO for the target.=E2=80=9D

[GP] I am having some troubles to = understand this sentence, is it possible to be rephrased?


[4] 4.3. Destination Cleanup Object (DCO)
=E2=80=9CThe DCO message always traverses downstream and = cleans up route information and other state information associated with = the given target.=E2=80=9D

[GP] Similar to comment [1], is it possible to give some = examples of state information?

=E2=80=94 = =E2=80=94 
Best,
Georgios

____________________________________

Georgios Z. = Papadopoulos, Ph.D.
Associate Professor, IMT = Atlantique, Rennes

web:   www.georgiospapadopoulos.com
twitter:  @gzpapadopoulos
____________________________________

On Jul 4, 2018, at 11:40, Ines Robles <mariainesrobles@googlemail.com> wrote:

Dear all, 

A Working Group Last call (WGLC) starts today = (04/07) until 20/07 for draft-ietf-roll-efficient-npdao-03

The draft is available here: 
https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npda= o/

Please review this draft to see if you think = that it is ready for publication and send comments to the list stating = your view. 


Thank you very much in advance,

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

= --Apple-Mail=_0087EFB3-B9D2-46A4-BEAE-26D7EC429D55-- From nobody Mon Jul 16 10:28:52 2018 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 25FEE130E21 for ; Mon, 16 Jul 2018 10:28:50 -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, 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 yTpua6Z3TBa4 for ; Mon, 16 Jul 2018 10:28:47 -0700 (PDT) Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::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 B8383130E12 for ; Mon, 16 Jul 2018 10:28:47 -0700 (PDT) Received: by mail-vk0-x233.google.com with SMTP id h22-v6so22077746vke.4 for ; Mon, 16 Jul 2018 10:28:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ZF+6GINPQQlAnIORmYnA9YTgAX6/Pff9lXXiA3o3YHk=; b=YU8CqerpU2n5Rzu0lYLUoJMtUkXReQOaOeaayrCYg0jYmeoKgfuTFH+8t5fcDS47Zu jL9s/4N9o0kmeNXSo6VYAyl6llvqMI79K6g1wVeusHEFKp2rF3H/vPlF8dsVxHsT5kAx eEJDJ/4aSk+FZ85heaetv0FHPLk73hoc49rLmxg8JXWjv38m8qbvDvZbBFN5foRNMlPn 7+lFaWi8CKd0+9ntAaixf3pM8T/7cUO0+kEActDllQFS+n1kFo3v5d9/VLdoGqpr6L/T TSX7Yg+lLpiQ+VA8Gz27URdhGYMqiXK+7n6YcbscxbrDKTPXhQM5TErbTU4zt8L+UL6z JfCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ZF+6GINPQQlAnIORmYnA9YTgAX6/Pff9lXXiA3o3YHk=; b=dEgLD9zDRkYWm98/k2xIem1H5CyqL2sF3GJdlTg6nrhld3aULJ4lCHvaYk8f9qnS1B eWGsJGCWxBSrMmGmGgAM2Kkm/AGYylBho6FKi0DAg1xsdcqFffwV/kPUp+X1JyDk9GK2 03gxP/NaZoZusKzlCgYu8R0C64FctgDGSEjX9hN22WzxBk0VeoaOBt3tdMtR0ZhVi+G6 T9N4q80xLdvwgB9Fr2GRdA2F85C+Keuqv93R4mTraYomri5zaeMzlecpkzDSVrtYhjXh ng9zfBaXdx/VJDi8bLlvuX13JhbXNqjZssdemQQn/xdA5fzmYgylrnTC3EFBEuq4hwHK OqtA== X-Gm-Message-State: AOUpUlGmoh2zT4LjK2U8axcb/qQOGRd7sFTeQLmVtNlxaZctw94Vvxoi Eob0uZ1iaC10zpWLj5hz5SQFr87sjdZYmFCG0bs= X-Google-Smtp-Source: AAOMgpf/R5bPhsr3qiEdYtIsMWCWK2la1ElNtzA8G/J1Eby0ANqFih9mFyKeGaFZdzijxMlTrSqHCF3lDg8mHLJbwas= X-Received: by 2002:a1f:df42:: with SMTP id w63-v6mr9735765vkg.135.1531762126542; Mon, 16 Jul 2018 10:28:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Rahul Jadhav Date: Mon, 16 Jul 2018 13:28:35 -0400 Message-ID: To: "Georgios Z. Papadopoulos" Cc: "Pascal Thubert (pthubert)" , Routing Over Low power and Lossy networks , Ines Robles , "consultancy@vanderstok.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 16 Jul 2018 17:28:50 -0000 Thank you Georgios for the review. Please find my response inline below. Best, Rahul On Mon, 16 Jul 2018 at 06:53, Georgios Z. Papadopoulos wrote: > > Dear Roll, Rahul and co-authors, > > I find this proposal useful, and quite ready to go. > Please find my (perhaps minor) comments below. > =E2=80=94 =E2=80=94 > > [1] 1.2. Current No-Path DAO messaging > "Subsequently parents or ancestors would release any resources (such as t= he routing entry) it maintains on behalf of target node.=E2=80=9D > > [GP] What could be other type of resources, apart from a routing entry, t= hat a parent or ancestors may release? > Could you provide some more examples? [RJ]: another something usually done in context to route removal is decreasing the ref-cnt for the corresponding next-hop nbr-table entry ... such that if the ref-cnt reaches 0/zero the neighbor table entry could as well be deleted. > > > [2] 3.1. Req#1: Tolerant to link failures to the previous parents > =E2=80=9CTherefore, it is required that the NPDAO message MUST be toleran= t to the link failure during the switching.=E2=80=9D > > [GP] How it can be tolerant, when there is a link failure? What could be = the potential means to be tolerant? [RJ]: The text states that any new route-invalidation mechanism defined should be tolerant to link failures. The link referred here represents link between the node and its previous parent (from whom the node is now disassociating). The way the draft achieves this tolerance is by having the route invalidation get done through the new route that is newly established and not depend on the previous link which is failed. > > > [3] 4.1. Change in RPL route invalidation semantics > =E2=80=9CThe trigger for the common ancestor node to generate this DCO is= the change in the next hop for the target on reception of an update messag= e in the form of regular DAO for the target.=E2=80=9D > > [GP] I am having some troubles to understand this sentence, is it possibl= e to be rephrased? [RJ]: "The common ancestor node generates this DCO in response to the change in the next-hop on receiving a regular DAO for the target." Do you think this rephrase works better ? > > > [4] 4.3. Destination Cleanup Object (DCO) > =E2=80=9CThe DCO message always traverses downstream and cleans up route = information and other state information associated with the given target.= =E2=80=9D > > [GP] Similar to comment [1], is it possible to give some examples of stat= e information? [RJ]: mentioned as part of [1] response. > > =E2=80=94 =E2=80=94 > Best, > Georgios > > ____________________________________ > > Georgios Z. Papadopoulos, Ph.D. > Associate Professor, IMT Atlantique, Rennes > > web: www.georgiospapadopoulos.com > twitter: @gzpapadopoulos > ____________________________________ > > On Jul 4, 2018, at 11:40, Ines Robles wr= ote: > > Dear all, > > A Working Group Last call (WGLC) starts today (04/07) until 20/07 for dra= ft-ietf-roll-efficient-npdao-03 > > The draft is available here: > https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ > > Please review this draft to see if you think that it is ready for publica= tion and send comments to the list stating your view. > > > Thank you very much in advance, > > Ines and Peter > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll > > From nobody Mon Jul 16 15:20:34 2018 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 907DF1310A6 for ; Mon, 16 Jul 2018 15:20:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 1N2PBit71oDn for ; Mon, 16 Jul 2018 15:20:30 -0700 (PDT) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 69C6F130E78 for ; Mon, 16 Jul 2018 15:20:30 -0700 (PDT) Received: by mail-it0-x231.google.com with SMTP id p4-v6so23181234itf.2 for ; Mon, 16 Jul 2018 15:20:30 -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 :cc; bh=hJW137JySSAgWHO9l7t/P9UapFk62URBUxvDY5+iGN8=; b=I4df7onw1SuEuF+Vz5vAbV2WP23nfk6qAhD41BDy++Hb/UUNVsCENQNPkP4+XYUv1L w+TtP+EM6K130n9F/LOl43KNJcota3gkSAenoisJIYYiijMQ6panhXahKAAc5Fi1o144 rrfLOxzCNqdQB5LC3J/rt5KdpC5cD6Wv6wE2qED1hmEOwhOyAxdgSukuvmwlpX+U6JrW 2NYwg6itef0eHPG67f360SpGv39eFhya1UpUr5MJVegge/69RpGBQgbanAdLQGVUrX9f YSYHdjrtGLjxVcYt7KpR5OTLpoInId02R+/KsWaRNagzaOB1ihlHzye8WSWgUW6g7s8x q2Ug== 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:cc; bh=hJW137JySSAgWHO9l7t/P9UapFk62URBUxvDY5+iGN8=; b=cxLOChgcTMWLQJ3l7W+XBHXI7TEypDDAXhpsRYFcdQcBRtgBETUsLFyO2OMA1IzL9q ni8KQ9zlmQjgR9Lkyvaq1rOiASB5cTqncSV9+yVZxR61t69KlzfSlyJXaEDet28mNEvb G9Izm44Q9uB4Tk0fpv0Fm82PuKyNd+ZrFnlYINa4jemzYxabt2x+HalotCLrq/L5f2PC Z9eNk5IbpVFVsAFHU40OlzSQIq4xc531c8BeAF3/jvhzKjpAOqiv0FHc+kf1JPwIuQR8 RAwMGVf7/RedE5zMZxNXVnbXDCnSWRiFzts34aiSAy/AWQIICAz9i31MZKrUMv/4lGeh 9zxw== X-Gm-Message-State: AOUpUlG7PUu3a1Ed8sNNA6LmFGEZLBRLDjTUea/HKdAvshvpmDnAZlxh wSKztpowukaVnL6mVfMFwAP/oCzmJwsXGEE3Z1B1MQ== X-Google-Smtp-Source: AAOMgpclGZN3EsjQPOt0B6wlh6v7x06oNUhnyq3uXtHBoC3W4ZTibSrcQh7vQ8mC0bX6Dj62STnT/LyBIiewAxh5IhQ= X-Received: by 2002:a24:1fc7:: with SMTP id d190-v6mr13489482itd.52.1531779629039; Mon, 16 Jul 2018 15:20:29 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Mon, 16 Jul 2018 15:20:28 -0700 (PDT) In-Reply-To: References: From: Ines Robles Date: Tue, 17 Jul 2018 01:20:28 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="000000000000a9c4d80571253cfd" Archived-At: Subject: Re: [Roll] Slides - agenda - IETF 102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 16 Jul 2018 22:20:32 -0000 --000000000000a9c4d80571253cfd Content-Type: text/plain; charset="UTF-8" Dear all, please find an updated version of the slides: https://datatracker.ietf.org/meeting/102/materials/slides-102-roll-complete-set-roll-00 Comments welcome, Thanks, Ines and Peter. 2018-07-14 23:16 GMT+03:00 Ines Robles : > Dear all, > > Please find: > > - The agenda > > https://datatracker.ietf.org/meeting/102/materials/agenda-102-roll-02 > > > - A draft version of the slides > > https://datatracker.ietf.org/meeting/102/materials/slides- > 102-roll-roll-ietf102-v1-00 > > > Comments welcome, > > Thanks, > > Ines and Peter > --000000000000a9c4d80571253cfd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

please find an updated versio= n of the slides:



Comments welcome,

Thanks,

Ines and Peter.
=

2018-07-14 = 23:16 GMT+03:00 Ines Robles <mariainesrobles@googlemail.com<= /a>>:

--000000000000a9c4d80571253cfd-- From nobody Tue Jul 17 02:36:08 2018 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 6C2D7130F20 for ; Tue, 17 Jul 2018 02:35:57 -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=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 9IZGu_4RGFII for ; Tue, 17 Jul 2018 02:35:54 -0700 (PDT) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::229]) (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 4F375130E29 for ; Tue, 17 Jul 2018 02:35:54 -0700 (PDT) Received: by mail-it0-x229.google.com with SMTP id v71-v6so913600itb.3 for ; Tue, 17 Jul 2018 02:35:54 -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 :cc; bh=b/TiUjygIWkdcPehQ1p1ys5Rv+QS0nwC72AW0ENxwTo=; b=Bb5Mpyk3i47YASBQkiBZCkVLw5Ey4iS0znRBRl9ZxDWEdVtb2EUoz4BjNrSJ9Y9+hZ f5vljcfrlXzpMyqzlmmMfD4dLekM1X4JnHcevXaH3s3dtKIIBOz5WyQah7ehHyrIR/BN TLoDs74H/H3zEq4w4OWt9X6oO1WX9If6Le2K6t+5GYaq2v+uOqqfZI/9iyJFyVoCSoDl 0JQYX+cMijKlG3VqAy91F/cOvJEm+N1NzWg1XBTB3GXAUXNsIFPWvdqAZnzfcbxNShae EpJjBWe3NvpGFBzCXWn51kTaDTFDiFBzE5DgQt3iQm9lUu+ipw5Bf6+s+zPShN0mvVbp T62Q== 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:cc; bh=b/TiUjygIWkdcPehQ1p1ys5Rv+QS0nwC72AW0ENxwTo=; b=BeebQZHGdMikOXd9odx8FNaU0jZZz4qSnBcclaB/kbp0y6mnW/rTWY6aAHo4mbnE+D DCfd8i3wpkpCGgV7rlliLPNxjJooh1MPy2lybxJwFMMo+R3BeQe6uQHU4paBZC1DU4XU TfcCPHZvKQQxKvyXhmxq6t4LQIMYrZKVGgvcxEH7juXcbLE2LDaOZ4TU65MLAz6wMPda WcD9lEm7mw0jkc0p8bK/lKXXkYD+ho+Ly5IhtuRrOven2JSKQB30JNKN8wNfN8UGEQ7T oqVvlI1vd1Or+Y72DFCpuk3uIsBeRPnVvH5V5eR1TdVyhtDBhSMldrk07wI56Ktc2P2w BQZw== X-Gm-Message-State: AOUpUlGGFgd9s4tFAPihsDNXpaAbaxweBfbw5aeaCMIJg2e2jl0xP79e boMG6m2Y0TqJ+R94arxYouNS8+yFfdACjRi+8givJA== X-Google-Smtp-Source: AAOMgpcyj6XLDPu7JrDwp9Qo2rMWEHqoXhOLL18Ea6CPmjEzLqfhsSilYx6IZde3Yy3r7lm+S3Ozx2GuJnTPY3ULc2s= X-Received: by 2002:a24:85c6:: with SMTP id r189-v6mr866954itd.83.1531820153290; Tue, 17 Jul 2018 02:35:53 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 02:35:52 -0700 (PDT) In-Reply-To: References: From: Ines Robles Date: Tue, 17 Jul 2018 12:35:52 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="00000000000018c7d905712eacaa" Archived-At: Subject: Re: [Roll] Slides - agenda - IETF 102 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 17 Jul 2018 09:36:08 -0000 --00000000000018c7d905712eacaa Content-Type: text/plain; charset="UTF-8" Dear all, A new version (v4) of the slides was uploaded https://datatracker.ietf.org/meeting/102/materials/slides-102-roll-complete-set-roll-v4-00 Thanks, Ines and Peter 2018-07-17 1:20 GMT+03:00 Ines Robles : > Dear all, > > please find an updated version of the slides: > > https://datatracker.ietf.org/meeting/102/materials/slides- > 102-roll-complete-set-roll-00 > > > Comments welcome, > > Thanks, > > Ines and Peter. > > 2018-07-14 23:16 GMT+03:00 Ines Robles : > >> Dear all, >> >> Please find: >> >> - The agenda >> >> https://datatracker.ietf.org/meeting/102/materials/agenda-102-roll-02 >> >> >> - A draft version of the slides >> >> https://datatracker.ietf.org/meeting/102/materials/slides-10 >> 2-roll-roll-ietf102-v1-00 >> >> >> Comments welcome, >> >> Thanks, >> >> Ines and Peter >> > > --00000000000018c7d905712eacaa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

A new version (v4) of the sli= des was uploaded


Thanks,

Ines and Peter

2018-07-17 1:20 GMT+03:00 Ines Robles <mariainesr= obles@googlemail.com>:
Dear all,

please find an updated version of= the slides:



Comments welcome,

Thanks,

Ines and Peter.

2018-07-14 23:16 GMT+0= 3:00 Ines Robles <mariainesrobles@googlemail.com>= ;:
Dear all,
=
Please find:

- The agenda


<= div>
- A draft version of the slides

https://datatracker.ietf.org/meeting/102/materials/slides-102-roll-roll-ietf102-v1-00


Comments welcome,

<= div>Thanks,

Ines and Peter


--00000000000018c7d905712eacaa-- From nobody Tue Jul 17 04:05:58 2018 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 C5402130E11 for ; Tue, 17 Jul 2018 04:05:55 -0700 (PDT) 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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=imt-atlantique.fr 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 O9UTYg41pExs for ; Tue, 17 Jul 2018 04:05:52 -0700 (PDT) Received: from zproxy120.enst.fr (zproxy120.enst.fr [137.194.2.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1385130E17 for ; Tue, 17 Jul 2018 04:05:51 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]) by zproxy120.enst.fr (Postfix) with ESMTP id 1247680F3F; Tue, 17 Jul 2018 13:05:50 +0200 (CEST) Received: from zproxy120.enst.fr ([IPv6:::1]) by localhost (zproxy120.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id YMdwMoyteh1U; Tue, 17 Jul 2018 13:05:48 +0200 (CEST) Received: from localhost (localhost [IPv6:::1]) by zproxy120.enst.fr (Postfix) with ESMTP id E159880F63; Tue, 17 Jul 2018 13:05:47 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy120.enst.fr E159880F63 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1531825547; bh=FnG5CK73elY1mJ7df+OopXtlkhcLsPTUmOeGZqpEH6M=; h=Mime-Version:From:Date:Message-Id:To; b=S6U1BoEH1lgUAi9KnfjshS9GcnDKEARw6b5U8W02nKClM4UFOnrh4TXDpNUPeiBPi QzAdRXi1LQeH7hp+HnK4NoCMpNm7dGGQAHmm8J26ijcuMl+zETz3DIpYBHNJHKh5Q1 FX2eBrROyOQAU9rp2vtpmebR/Sz2ZbxjelMAKNj0= X-Virus-Scanned: amavisd-new at zproxy120.enst.fr Received: from zproxy120.enst.fr ([IPv6:::1]) by localhost (zproxy120.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id E_VsZpWhBuzi; Tue, 17 Jul 2018 13:05:47 +0200 (CEST) Received: from [192.168.1.3] (ppp046177011092.access.hol.gr [46.177.11.92]) by zproxy120.enst.fr (Postfix) with ESMTPSA id 2D30880F3F; Tue, 17 Jul 2018 13:05:47 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: "Georgios Z. Papadopoulos" In-Reply-To: Date: Tue, 17 Jul 2018 14:05:45 +0300 Cc: "Pascal Thubert (pthubert)" , Routing Over Low power and Lossy networks , Ines Robles , "consultancy@vanderstok.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3491D5D3-9753-4B6C-B45E-DF9E93B5EB01@imt-atlantique.fr> References: To: Rahul Jadhav X-Mailer: Apple Mail (2.3124) Archived-At: Subject: Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 17 Jul 2018 11:05:56 -0000 Hello Rahul, Many thanks for your quick response. Please find my response inline: Cheers, Georgios > On Jul 16, 2018, at 20:28, Rahul Jadhav wrote: >=20 > Thank you Georgios for the review. > Please find my response inline below. >=20 > Best, > Rahul >=20 > On Mon, 16 Jul 2018 at 06:53, Georgios Z. Papadopoulos > wrote: >>=20 >> Dear Roll, Rahul and co-authors, >>=20 >> I find this proposal useful, and quite ready to go. >> Please find my (perhaps minor) comments below. >> =E2=80=94 =E2=80=94 >>=20 >> [1] 1.2. Current No-Path DAO messaging >> "Subsequently parents or ancestors would release any resources (such = as the routing entry) it maintains on behalf of target node.=E2=80=9D >>=20 >> [GP] What could be other type of resources, apart from a routing = entry, that a parent or ancestors may release? >> Could you provide some more examples? >=20 > [RJ]: another something usually done in context to route removal is > decreasing the ref-cnt for the corresponding next-hop nbr-table entry > ... such that if the ref-cnt reaches 0/zero the neighbor table entry > could as well be deleted. [GP] Many thanks for the example. I believe it would be helpful to provide such another example in the = draft. >>=20 >>=20 >> [2] 3.1. Req#1: Tolerant to link failures to the previous parents >> =E2=80=9CTherefore, it is required that the NPDAO message MUST be = tolerant to the link failure during the switching.=E2=80=9D >>=20 >> [GP] How it can be tolerant, when there is a link failure? What could = be the potential means to be tolerant? >=20 > [RJ]: The text states that any new route-invalidation mechanism > defined should be tolerant to link failures. The link referred here > represents link between the node and its previous parent (from whom > the node is now disassociating). The way the draft achieves this > tolerance is by having the route invalidation get done through the new > route that is newly established and not depend on the previous link > which is failed. [GP] Many thanks for the clarification. Do you think you could provide such explanation in the draft? >>=20 >>=20 >> [3] 4.1. Change in RPL route invalidation semantics >> =E2=80=9CThe trigger for the common ancestor node to generate this = DCO is the change in the next hop for the target on reception of an = update message in the form of regular DAO for the target.=E2=80=9D >>=20 >> [GP] I am having some troubles to understand this sentence, is it = possible to be rephrased? >=20 > [RJ]: "The common ancestor node generates this DCO in response to the > change in the next-hop on receiving a regular DAO for the target." > Do you think this rephrase works better ? [GP] Yes, definitely. Many thanks. >>=20 >>=20 >> [4] 4.3. Destination Cleanup Object (DCO) >> =E2=80=9CThe DCO message always traverses downstream and cleans up = route information and other state information associated with the given = target.=E2=80=9D >>=20 >> [GP] Similar to comment [1], is it possible to give some examples of = state information? >=20 > [RJ]: mentioned as part of [1] response. [GP] Great, thanks. >>=20 >> =E2=80=94 =E2=80=94 >> Best, >> Georgios >>=20 >> ____________________________________ >>=20 >> Georgios Z. Papadopoulos, Ph.D. >> Associate Professor, IMT Atlantique, Rennes >>=20 >> web: www.georgiospapadopoulos.com >> twitter: @gzpapadopoulos >> ____________________________________ >>=20 >> On Jul 4, 2018, at 11:40, Ines Robles = wrote: >>=20 >> Dear all, >>=20 >> A Working Group Last call (WGLC) starts today (04/07) until 20/07 for = draft-ietf-roll-efficient-npdao-03 >>=20 >> The draft is available here: >> https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ >>=20 >> Please review this draft to see if you think that it is ready for = publication and send comments to the list stating your view. >>=20 >>=20 >> Thank you very much in advance, >>=20 >> Ines and Peter >> _______________________________________________ >> Roll mailing list >> Roll@ietf.org >> https://www.ietf.org/mailman/listinfo/roll >>=20 >>=20 From nobody Tue Jul 17 09:40:27 2018 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 C8381130EB0 for ; Tue, 17 Jul 2018 09:40:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 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_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 nDX9BH7DB4fW for ; Tue, 17 Jul 2018 09:40:24 -0700 (PDT) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (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 B382A130EC1 for ; Tue, 17 Jul 2018 09:40:24 -0700 (PDT) Received: by mail-vk0-x234.google.com with SMTP id 125-v6so922544vke.11 for ; Tue, 17 Jul 2018 09:40:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FdKJt9c8sQdjny9uG9Y4hn4pecZ+cdiNh6BRstahycw=; b=YLs5c4gXkB0oP1s8Iueiz512WOTkUn0yApbTDvyKaUh4GHyARInVfuZWXh85uRHETI 5Q9bWRbVdLPZMXTMtcVGN69Nap/GrRpannNAFwlHOS8Ke4aEDAAx5uOLQStATtmHEVKR NA90/uIysIX8S7pZ39hKa5KVAllvG/DyMVko2XJSNS6QCCvmcaiQAiq0xZeCDpbremwX aetgDBecvTkjZ8E+wObEuqZwcG/Bh+oiLU1hI4Cf3biKGYGWTLf8r6ydZ0/5MLAJFRC9 Rou8IsEoiyU/frXX7RzHv6EQdAMLnAStT8ijJpIN9zKHi8lyYJgnxSuGQqQ9IHGFJno3 VF9g== 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; bh=FdKJt9c8sQdjny9uG9Y4hn4pecZ+cdiNh6BRstahycw=; b=kt5QJ94JKr2it3CrQ09CPfAlAwaKqKQFDn/rrCTk6/YGe5qGeQDCnzIaboB2uEu1Fa SQBFV6DYNg6riHv7aTDVIha4FbWkXEkTGFryK5Gcy2WBVf2GRudGJBlWXVnt0tCZJj3B hauaoJ7mmTS7dfJ9aug+phxqwqN0tXX6Lrgk9PKkD+ielUgKIR0LWDI583aYvCUXkQpJ yAOs4cU5M9eAsnk35swXkZTIBLx/QCgkvbcf5VVg5b+kFPIJ64P5aJNIUWCoRwMnHoDb lxhonFam1Sz3qqTyW7+OkUTAK9/cqU208CRYToo3NU+bAcjVJjWzIxkBr/Zy46twWjwt 6CbQ== X-Gm-Message-State: AOUpUlEws7mKXZDav02Z5bI61FfZrIrxacOEVDhweN6uZbH1gXyGUwRQ x4hNbf87nqVuGTl3ipl+0w+tJlbAsBmEiJNYAqtbiA== X-Google-Smtp-Source: AAOMgpfWvpwkLRfhHb2scuQ3JhOkl3CRXO8U+4DJLeSRhkBTup2EOd+LUvX/e+asbw6TmZaBba6ZQuHgeD4Dae3R9yM= X-Received: by 2002:a1f:4049:: with SMTP id n70-v6mr1345383vka.140.1531845623101; Tue, 17 Jul 2018 09:40:23 -0700 (PDT) MIME-Version: 1.0 From: Rahul Jadhav Date: Tue, 17 Jul 2018 12:40:11 -0400 Message-ID: To: Routing Over Low power and Lossy networks Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [Roll] rpl routing and linux-kernel X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 17 Jul 2018 16:40:27 -0000 Hello ROLL, While trying to integrate RPL with linux kernel and we had certain design choices. In that context I have some specific questions, especially towards linux-kernel integration and not towards RPL protocol implementation itself. Assuming RPL implementation will be in userspace, questions are: 1. We can add/del routes using rtnetlink interfaces ... this can be used for the routes learnt by RPL as well ... But RPL needs to maintain some additional per-route information on the 6LBR ... To be very specific, we need to store parent information in context to every route. Is it possible to do it with rtnetlink? I didn't find an option to do that. If it ain't possible then what could be an alt approach? 2. RPL requires that certain extended ipv6 options be added in data flows .. What is the best way to do this? It is possible to do this with netfilter+libnfq but i m not sure whether this is the best approach. If there is anyone who tried this before, it would be great to have a discussion in person while we are in IETF102. Please let know if you are available for discussion. Thanks, Rahul From nobody Tue Jul 17 11:25:14 2018 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 780CD130EF3 for ; Tue, 17 Jul 2018 11:25:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 hVFIgP7do3nG for ; Tue, 17 Jul 2018 11:25:10 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0222.hostedemail.com [216.40.44.222]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D269131001 for ; Tue, 17 Jul 2018 11:25:10 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id DEA23837F24C for ; Tue, 17 Jul 2018 18:25:08 +0000 (UTC) X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :, RULES_HIT:41:72:152:355:379:582:800:962:967:973:983:988:989:1152:1189:1208:1221:1260:1263:1313:1314:1345:1381:1431:1436:1437:1516:1517:1518:1534:1541:1575:1588:1589:1592:1594:1711:1730:1776:1792:2525:2561:2564:2682:2685:2693:2829:2859:2911:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3352:3586:3622:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4362:4425:4659:5007:6119:6261:6298:6659:8603:9010:9015:9025:9177:9388:10004:10400:10848:11232:11658:11914:12043:12295:12555:12679:12895:12986:13071:13139:13161:13199:13210:13229:13439:13846:14096:14180:14181:14195:14721:21060:21063:21080:21324:21433:21451:21625:21691:21740:30006:30041:30048:30054:30070, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LF X-HE-Tag: class03_8437264a59b34 X-Filterd-Recvd-Size: 4435 Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf08.hostedemail.com (Postfix) with ESMTPA for ; Tue, 17 Jul 2018 18:25:08 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_7c567f0ae4e5ed9a8234ab392b9f8a26" Date: Tue, 17 Jul 2018 14:25:08 -0400 From: Peter van der Stok To: Roll Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org Message-ID: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> X-Sender: stokcons@bbhmail.nl User-Agent: Roundcube Webmail/1.2.7 X-Originating-IP: [31.133.147.176] Archived-At: Subject: [Roll] acceptance of individual drafts X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 17 Jul 2018 18:25:13 -0000 --=_7c567f0ae4e5ed9a8234ab392b9f8a26 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi Roll, This morning we had several interesting presentations of individual drafts. They all fit within the charter of ROLL, and represent worthy subjects. It would be pleasure to take them in as roll WG documents, provided there is enough interest in the WG to work on the subjects. Below there is a list of drafts for which I like an answer to the following questions: Did you read a version of the document, Do you intend to read a version of the document. Will you react on the ML concerning the document. Are you willing to do a review of the document? Will you contribute to the document? Answering to only one question positively for a subset of the documents is probably sufficient to gauge interest. The list of drafts is: Bier RPL design team document rahul-roll-rpl-observation koutsiamanis-roll-nsa-estension ji-roll-traffic-aware-objective function thubert-roll-unaware-leaves For draft rahul-rpl-observation, the consideration that it should go to RFC is no relevant for these questions, because we can use the document extensively in the WG without publishing it in the end. Thanks for your reactions and contributions. Peter&Ines -- Peter van der Stok vanderstok consultancy mailto: consultancy@vanderstok.org www: www.vanderstok.org [1] tel NL: +31(0)492474673 F: +33(0)966015248 Links: ------ [1] http://www.vanderstok.org --=_7c567f0ae4e5ed9a8234ab392b9f8a26 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi Roll,

This morning we had several interesting presentations o= f individual drafts.
They all fit within the charter of ROLL, and repr= esent worthy subjects.

It would be pleasure to take them in as r= oll WG documents, provided there is enough interest in the WG to work on th= e subjects.

Below there is a list of drafts for which I like an = answer to the following questions:
Did you read a version of the docum= ent,
Do you intend to read a version of the document.
Will you re= act on the ML concerning the document.
Are you willing to do a review = of the document?
Will you contribute to the document?

Answe= ring to only one question positively for a subset of the documents is proba= bly sufficient to gauge interest.

The list of drafts is:
Bi= er RPL design team document
rahul-roll-rpl-observation
koutsiaman= is-roll-nsa-estension
ji-roll-traffic-aware-objective function
th= ubert-roll-unaware-leaves


For draft rahul-rpl-observation,= the consideration that it should go to RFC is no relevant for these questi= ons, because we can use the document extensively in the WG without publishi= ng it in the end.

Thanks for your reactions and contributions.
Peter&Ines
--
= Peter van der Stok
vanderstok consultancy
mailto: consultancy@vanderstok.org
www: = = www.vanderstok.org
tel NL: +31(0)492474673    &nbs= p;F: +33(0)966015248
--=_7c567f0ae4e5ed9a8234ab392b9f8a26-- From nobody Tue Jul 17 12:45:28 2018 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 C028F130E44 for ; Tue, 17 Jul 2018 12:45:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 (1024-bit key) header.d=imt-atlantique.fr 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 rxmKAwIJgPa8 for ; Tue, 17 Jul 2018 12:45:20 -0700 (PDT) Received: from zproxy130.enst.fr (zproxy130.enst.fr [137.194.2.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 777AC124BE5 for ; Tue, 17 Jul 2018 12:45:20 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id 4FCA31204AE for ; Tue, 17 Jul 2018 21:45:19 +0200 (CEST) Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id r2W7x-gXj0le for ; Tue, 17 Jul 2018 21:45:18 +0200 (CEST) Received: from localhost (localhost [IPv6:::1]) by zproxy130.enst.fr (Postfix) with ESMTP id 83A371209C7 for ; Tue, 17 Jul 2018 21:45:18 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy130.enst.fr 83A371209C7 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1531856718; bh=7P/5wNYsAZg4Xs+NQnjNKCGOrgwMDKcmjNQPGixPzgk=; h=From:Message-Id:Mime-Version:Date:To; b=h0/4XvZro2lsg11zGEJflpzAzjT1iCKk0TSNHB5cvtrUqFq+10VsUP3HWMWy2lNjv JoLGYEGqT3TsARRke0oticceT3wfMSf+PUELt+6//PXNuohhyWrb1qM6ChHGYiOuGY GbxCcYXheqGah4Fwq7dLIkoueaz6eFVL04Qqfnxk= X-Virus-Scanned: amavisd-new at zproxy130.enst.fr Received: from zproxy130.enst.fr ([IPv6:::1]) by localhost (zproxy130.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id JDy2lAh_HSK7 for ; Tue, 17 Jul 2018 21:45:18 +0200 (CEST) Received: from [192.168.1.2] (ppp079166215114.access.hol.gr [79.166.215.114]) by zproxy130.enst.fr (Postfix) with ESMTPSA id 0E0891204AE for ; Tue, 17 Jul 2018 21:45:17 +0200 (CEST) From: "Georgios Z. Papadopoulos" Content-Type: multipart/alternative; boundary="Apple-Mail=_545C9A3F-4B8B-4DFE-912E-6CACE2870126" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Date: Tue, 17 Jul 2018 22:45:16 +0300 References: To: Routing Over Low power and Lossy networks In-Reply-To: X-Mailer: Apple Mail (2.3124) Archived-At: Subject: Re: [Roll] Extension point for node information X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 17 Jul 2018 19:45:26 -0000 --Apple-Mail=_545C9A3F-4B8B-4DFE-912E-6CACE2870126 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Dear Roll, Please find this e-mail as a friendly reminder. This is the e-mail that Aris mentioned during his presentation.=20 We are looking forward for your feedbacks. Best, Georgios and Aris ____________________________________ Georgios Z. Papadopoulos, Ph.D. Associate Professor, IMT Atlantique, Rennes web: www.georgiospapadopoulos.com = twitter: @gzpapadopoulos = ____________________________________ > On May 30, 2018, at 00:30, Remous-Aris Koutsiamanis = wrote: >=20 > Dear all, >=20 > we are working on issues of parent selection and DODAG selection. > We have already worked on two drafts which add information to the DIO = DAG MC to support these choices. > We are debating where in the DAG MC to put information regarding node = state. >=20 > In draft draft-koutsiamanis-roll-nsa-extension-01 we put the "Parent = Node Set" information (the list of a node's parent IPv6 addresses) in a = new TLV nested within the NSA metric object. > However, in draft draft-ji-roll-traffic-aware-objective-function-01 we = added the "Packet Transmission Rate" information as a new metric object = type directly withing the DAG MC as new Routing-MC-Type (i.e., at the = same "level" as the other 6551-defined metric object like ETX, Node = Energy, etc.). > We are now debating if we maybe should re-position the "Packet = Transmission Rate" information nested withing the NSA metric object, as = with "the Parent Node Set", or not. >=20 > Both these drafts propose carrying information which is semantically = similar: information internal to a node. > We are wondering what would be more correct to do: > a) ask for new Routing-MC-Type allocation and create new metric = objects. > b) ask for new NSA TLV type allocation and create as nested TLV within = the NSA metric object. >=20 > We have noted that in RFC6551 there is the NSA metric object and also = a separate node-information metric object specifically for energy, the = "Node Energy (NE) object". > It would seem that the existing NE object should be nested within the = NSA metric object if all node information is to be put within NSA. > If not, we expect that we should be able put our own additions at the = same level (i.e. use case a, above, to ask for new Routing-MC-Type = allocation). Should we do this? >=20 > If none of the above, is there a reason why an exception was made = especially for energy information? >=20 > Kind regards, > Aris > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll --Apple-Mail=_545C9A3F-4B8B-4DFE-912E-6CACE2870126 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Dear Roll,

Please find this e-mail as a friendly reminder.
This is the e-mail that Aris mentioned during his = presentation. 

We are looking forward for your feedbacks.

Best,
Georgios and Aris

____________________________________

Georgios Z. = Papadopoulos, Ph.D.
Associate Professor, IMT = Atlantique, Rennes

web:   www.georgiospapadopoulos.com
twitter:  @gzpapadopoulos
____________________________________

On May 30, 2018, at 00:30, Remous-Aris Koutsiamanis <aris@ariskou.com> = wrote:

Dear all,

we are = working on issues of parent selection and DODAG selection.
We have already worked on two drafts which add information to = the DIO DAG MC to support these choices.
We are debating = where in the DAG MC to put information regarding node state.

In draft = draft-koutsiamanis-roll-nsa-extension-01 we put the "Parent Node Set" = information (the list of a node's parent IPv6 addresses) in a new TLV = nested within the NSA metric object.
However, in draft = draft-ji-roll-traffic-aware-objective-function-01 we added the "Packet = Transmission Rate" information as a new metric object type directly = withing the DAG MC as  new Routing-MC-Type (i.e., at the same = "level" as the other 6551-defined metric object like ETX, Node Energy, = etc.).
We are now debating if we maybe should re-position = the "Packet Transmission Rate" information nested withing the NSA metric = object, as with "the Parent Node Set", or not.

Both these drafts propose carrying information which is = semantically similar: information internal to a node.
We = are wondering what would be more correct to do:
a) ask for = new Routing-MC-Type allocation and create new metric objects.
b) ask for new NSA TLV type allocation and create as nested = TLV within the NSA metric object.

We have = noted that in RFC6551 there is the NSA metric object and also a separate = node-information metric object specifically for energy, the "Node Energy = (NE) object".
It would seem that the existing NE object = should be nested within the NSA metric object if all node information is = to be put within NSA.
If not, we expect that we should be = able put our own additions at the same level (i.e. use case a, above, to = ask for new Routing-MC-Type allocation). Should we do this?

If none of the above, is there a reason why an = exception was made especially for energy information?

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

= --Apple-Mail=_545C9A3F-4B8B-4DFE-912E-6CACE2870126-- From nobody Wed Jul 18 00:38:02 2018 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 E69911310FE for ; Wed, 18 Jul 2018 00:38:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 nH-NTkTCsQY7 for ; Wed, 18 Jul 2018 00:37:58 -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 4692C1310E9 for ; Wed, 18 Jul 2018 00:37:58 -0700 (PDT) Received: by mail-io0-x232.google.com with SMTP id q19-v6so3243228ioh.11 for ; Wed, 18 Jul 2018 00:37:58 -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=UubBpKmAFGuM9lD+FBF60bh2crnK4f4lItdV4QMs0yE=; b=hvm05xoW3GN/71P41YvZTKDd+kGD1MdCjlwA8ANy0Y3cz3xJ0oWtzrJMSdtj67GR33 GJzV6rng5dJztH5hZ4JuJgaLDYyfHKoLSP4+37LGrbmTWZpvIC766bVs2yxDHbWbBJGz dtUIc5HDHSqqkCQ+W8GSGeRevSs1VIPUEl/V62d3bTguEvgqPHCIpf1+tK2SbYMwNksx h7aP/ePR9lIFARW9s8DBRxTsebTX+ew77GI80jQLp6JIjkab3/71tZyLWIqMdzFqRwMu vKtXiN+XpegLnOmcb90Qc9a4DYhDirTi8UZ7juHY60O1Ephg5NbcKwt+16eCvg7YsIWU 6t+g== 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=UubBpKmAFGuM9lD+FBF60bh2crnK4f4lItdV4QMs0yE=; b=hrSYCi41CmaMzgkn2KXY224/Qoi138J2sKprxUCcnrKsHuTsKHN+PYFAfc07AcYM9Y L/W7eYZXppE+6VXiHvkdYfqG4GBRXF4FVdzdDCbI+5eKyZbQr7hWG436SQ9M7ClL7fT1 WnQ1JxLPKy9QSDnkGetNDfvYuuPNhesZUZRonYFfNp0dtICY6gMbuZ/2fhHOpJBVSr20 t7VqThmlbyx7fSP3nDvK4arF8P0OccDzhnX8N42gn749ntsJDF1dC9bNENIumcrJKrK0 b/+yc3/qWCEYksECN4W8ORDJnP9IAwVWVLqjGWYNWhGBOUFyfWs4AEVyvve/t6s694/Y 9hRA== X-Gm-Message-State: AOUpUlE6Ea2PeKYktMYlZkXCs68kTpxhW9dLTj0MeB9ltHCK117rLTCf Mk8ySLXT9dXqpT1VGXkav+VNhq7l//0quC9yKSU0Tg== X-Google-Smtp-Source: AA+uWPx2JbUo3TrT5DMqZJeZOONbqbJisiNWCT5HysjkbOvRJ5u9a/XhhcwtbekrYpm74LSGjgdaz5ZmzrTK2//ByIw= X-Received: by 2002:a6b:bf04:: with SMTP id p4-v6mr4079986iof.15.1531899477228; Wed, 18 Jul 2018 00:37:57 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:e204:0:0:0:0:0 with HTTP; Wed, 18 Jul 2018 00:37:56 -0700 (PDT) From: Ines Robles Date: Wed, 18 Jul 2018 10:37:56 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="0000000000002c053c0571412462" Archived-At: Subject: [Roll] Minute - IETF 102 - X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 18 Jul 2018 07:38:01 -0000 --0000000000002c053c0571412462 Content-Type: text/plain; charset="UTF-8" Dear all, First of all, MILLION THANKS to Dominique for being our minute taker :D Please find the minute in the following link https://datatracker.ietf.org/meeting/102/materials/minutes-102-roll-00 Comments welcome before August 10th. Cheers, Ines and Peter --0000000000002c053c0571412462 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

First of all, MILLION THANKS = to Dominique for being our minute taker :D=C2=A0

Ple= ase find the minute in the following link

https://datatracker.ietf.org/meeting/102/materials/minutes-102-roll-0= 0

Comments welcome before August 10th.

Cheers,

Ines and Peter
=
--0000000000002c053c0571412462-- From nobody Wed Jul 18 06:37:55 2018 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 CA05D1311E3 for ; Wed, 18 Jul 2018 06:37:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 ggT9fEy6VNyZ for ; Wed, 18 Jul 2018 06:37:41 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 5B6771311A6 for ; Wed, 18 Jul 2018 06:37:40 -0700 (PDT) Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A6088E9044EA4 for ; Wed, 18 Jul 2018 14:37:36 +0100 (IST) Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.399.0; Wed, 18 Jul 2018 14:37:38 +0100 Received: from DGGEMM526-MBS.china.huawei.com ([169.254.7.233]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0382.000; Wed, 18 Jul 2018 21:37:33 +0800 From: "Liubing (Remy)" To: "Pascal Thubert (pthubert)" , Charlie Perkins CC: Routing Over Low power and Lossy networks Thread-Topic: Explaining RPLinstance pairing and shift Thread-Index: AdQemOpvi8XHxI8ZT0iOoB0fk5arcA== Date: Wed, 18 Jul 2018 13:37:32 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.124.182.71] Content-Type: multipart/alternative; boundary="_000_BB09947B5326FE42BA3918FA28765C2EE4C551dggemm526mbschina_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [Roll] Explaining RPLinstance pairing and shift X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 18 Jul 2018 13:37:53 -0000 --_000_BB09947B5326FE42BA3918FA28765C2EE4C551dggemm526mbschina_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Pascal, Regarding to the discussion that we had at the meeting, I'd like to explain= the motivation for RPLInstance pairing and Shift. Why we need RPLInstance pairing? Multiple instances can coexist between the same pair of OrigNode and TargNo= de at the same time, if two applications running on the TargNode have diffe= rent requirements on routes to the same TargNode, thus the routes need to b= e built separately. In order to match the RREP-DIO to the correct RREQ-DIO,= the RPLInstanceID must be paired. One convenient option is to let the RREQ= -instance and the RREP-instance share the same ID. And there will be no con= flict because the RPLInstanceID is local and the RREQ and RREP instances ha= ve different DODAGIDs. There can be other ways for pairing but will result = in extra overhead because the ID of the RREQ-instance needs to be carried s= omehow. Why we need the shift? Two OrigNodes may use the same local RPLInstaceID to find routes to the sam= e TargNode at the same time. According to the previous RPLInstaceID pairing= mechanism, the IDs of the two RREP-instances will be the same as well. How= ever, it is obligate to differentiate the two RREP-instances. That's why we= need to shift the instance ID to another one at the TargNode. The original= instance ID can be recovered whenever needed at the intermediate nodes or = the OrigNode. Many thanks for agreeing to review our draft. Best regards, Remy --_000_BB09947B5326FE42BA3918FA28765C2EE4C551dggemm526mbschina_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Pascal,=

 

Regarding to the discussion tha= t we had at the meeting, I’d like to explain the motivation for RPLIn= stance pairing and Shift.

 

Why we need RPLInstance pairing= ?

Multiple instances can coexist = between the same pair of OrigNode and TargNode at the same time, if two app= lications running on the TargNode have different requirements on routes to = the same TargNode, thus the routes need to be built separately. In order to match the RREP-DIO to the correct RREQ= -DIO, the RPLInstanceID must be paired. One convenient option is to let the= RREQ-instance and the RREP-instance share the same ID. And there will be n= o conflict because the RPLInstanceID is local and the RREQ and RREP instances have different DODAGIDs. There ca= n be other ways for pairing but will result in extra overhead because the I= D of the RREQ-instance needs to be carried somehow.

 

Why we need the shift?

Two OrigNodes may use the same = local RPLInstaceID to find routes to the same TargNode at the same time. Ac= cording to the previous RPLInstaceID pairing mechanism, the IDs of the two = RREP-instances will be the same as well. However, it is obligate to differentiate the two RREP-instances. That̵= 7;s why we need to shift the instance ID to another one at the TargNode. Th= e original instance ID can be recovered whenever needed at the intermediate= nodes or the OrigNode.

 

Many thanks for agreeing to rev= iew our draft.

 

Best regards,=

Remy

--_000_BB09947B5326FE42BA3918FA28765C2EE4C551dggemm526mbschina_-- From nobody Wed Jul 18 14:30:17 2018 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 368CE131060 for ; Wed, 18 Jul 2018 14:30:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.509 X-Spam-Level: X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 78Nu-4qWO4yS for ; Wed, 18 Jul 2018 14:30:12 -0700 (PDT) Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E71E0130FC7 for ; Wed, 18 Jul 2018 14:30:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12232; q=dns/txt; s=iport; t=1531949411; x=1533159011; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=8cUBwr2R4nPMWOB+KsTBzt0knJhKmJlL9gwNf6rD/LU=; b=X0uGO70oEmS/KpTrHAU4zycRaFE3sth0X9FSgRvCv7WqHWrqAxeX+WQ+ 2jBm9leSu9gqEiwdVv2qGkY93L4oJHjiw9WeJzronqppsX8Az+UkBYt5t WNfbe4NXQK3lS+fKEFbhtrKE46zTRIdqfy1sYHfveqyNa2PMyYwCIc15m 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C+AADOsE9b/40NJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJTdmN/KAqLeIwsggyQKoUPgXoLhGwCgnkhNBgBAgEBAgE?= =?us-ascii?q?BAm0ohTYBAQEELToSEAIBCBEEAQEvMh0IAQEEAQ0FCIMZgRtMAxWrVIpKiQK?= =?us-ascii?q?BVz+BEYMRglaCCYVyAoxajQYJAohshjGNbpFwAhEUgSQdOIFScBWDJJBTb4t?= =?us-ascii?q?wgRoBAQ?= X-IronPort-AV: E=Sophos;i="5.51,371,1526342400"; d="scan'208,217";a="144535605" Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2018 21:30:10 +0000 Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id w6ILUAD6016969 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 18 Jul 2018 21:30:10 GMT Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 18 Jul 2018 16:30:10 -0500 Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1320.000; Wed, 18 Jul 2018 16:30:10 -0500 From: "Pascal Thubert (pthubert)" To: "Liubing (Remy)" , Charlie Perkins CC: Routing Over Low power and Lossy networks Thread-Topic: Explaining RPLinstance pairing and shift Thread-Index: AdQemOpvi8XHxI8ZT0iOoB0fk5arcAAQ2FTA Date: Wed, 18 Jul 2018 21:29:42 +0000 Deferred-Delivery: Wed, 18 Jul 2018 21:29:30 +0000 Message-ID: <389acab036d649f1aa74d6ac591574e8@XCH-RCD-001.cisco.com> References: In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.24.74.234] Content-Type: multipart/alternative; boundary="_000_389acab036d649f1aa74d6ac591574e8XCHRCD001ciscocom_" MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com X-Outbound-Node: alln-core-8.cisco.com Archived-At: Subject: Re: [Roll] Explaining RPLinstance pairing and shift X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 18 Jul 2018 21:30:15 -0000 --_000_389acab036d649f1aa74d6ac591574e8XCHRCD001ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Remy : I agree with all that. My point was more a format question and does not sug= gest a change of design. The tuple (IPv6 @, instance ID) identifies uniquely a DODAG. In the case of= a local instance, the name space of the instance ID is local to the node t= hat owns the IPv6 address. So far so good. With AODV RPL, the caller IP1 forms a tuple (IP1, ID1) for the DODAG 1 asso= ciated to the RREQ, and the responder IP2 forms another (IP2, ID2) for the = DODAG 2 associated to the reply. The packets from the caller are tagged wi= th (IP2, ID2) while packets from the responder are tagged (IP1, ID1). If you look at it this is very similar to a user-SAP, provider-SAP in OSI. = My only question was this idea of shifting. Why call things shifts when the= point is that these are different and unrelated instance IDs, from differe= nt namespaces? The OSI response to a create_SAP.req(usap) is a create_SAP.c= onf(uSAP, pSAP) and then for the data we have data.req(pSAP) and data.ind(= uSAP). I thought you'd use that classical model. I expected that the RREP that for= ms the DODAG 2 identified by (IP2, ID2 )would have a new option in it, like= a ID-correlator option that would contain (IP1, ID1). So people that see t= he RREP can correlate the 2 easily. Do I make sense? Pascal From: Liubing (Remy) Sent: mercredi 18 juillet 2018 09:38 To: Pascal Thubert (pthubert) ; Charlie Perkins Cc: Routing Over Low power and Lossy networks Subject: Explaining RPLinstance pairing and shift Hello Pascal, Regarding to the discussion that we had at the meeting, I'd like to explain= the motivation for RPLInstance pairing and Shift. Why we need RPLInstance pairing? Multiple instances can coexist between the same pair of OrigNode and TargNo= de at the same time, if two applications running on the TargNode have diffe= rent requirements on routes to the same TargNode, thus the routes need to b= e built separately. In order to match the RREP-DIO to the correct RREQ-DIO,= the RPLInstanceID must be paired. One convenient option is to let the RREQ= -instance and the RREP-instance share the same ID. And there will be no con= flict because the RPLInstanceID is local and the RREQ and RREP instances ha= ve different DODAGIDs. There can be other ways for pairing but will result = in extra overhead because the ID of the RREQ-instance needs to be carried s= omehow. Why we need the shift? Two OrigNodes may use the same local RPLInstaceID to find routes to the sam= e TargNode at the same time. According to the previous RPLInstaceID pairing= mechanism, the IDs of the two RREP-instances will be the same as well. How= ever, it is obligate to differentiate the two RREP-instances. That's why we= need to shift the instance ID to another one at the TargNode. The original= instance ID can be recovered whenever needed at the intermediate nodes or = the OrigNode. Many thanks for agreeing to review our draft. Best regards, Remy --_000_389acab036d649f1aa74d6ac591574e8XCHRCD001ciscocom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Remy :

 

I agr= ee with all that. My point was more a format question and does not suggest = a change of design.

=  

The t= uple (IPv6 @, instance ID) identifies uniquely a DODAG. In the case of a lo= cal instance, the name space of the instance ID is local to the node that o= wns the IPv6 address. So far so good.

=  

With = AODV RPL, the caller IP1 forms a tuple (IP1, ID1) for the DODAG 1 associate= d to the RREQ, and the responder IP2 forms another (IP2, ID2) for the DODAG= 2 associated to the reply.  The packets from the caller are tagged with (IP2, ID2) while packets from the responde= r are tagged (IP1, ID1).

=  

If yo= u look at it this is very similar to a user-SAP, provider-SAP in OSI. My on= ly question was this idea of shifting. Why call things shifts when the poin= t is that these are different and unrelated instance IDs, from different namespaces? The OSI response to a create_SAP.= req(usap) is a create_SAP.conf(uSAP, pSAP) and then for the data we have da= ta.req(pSAP)  and data.ind(uSAP).

=  

I tho= ught you’d use that classical model. I expected that the RREP that fo= rms the DODAG 2 identified by (IP2, ID2 )would have a new option in it, lik= e a ID-correlator option that would contain (IP1, ID1). So people that see the RREP can correlate the 2 easily. <= /o:p>

=  

Do I = make sense?

=  

Pasca= l

=  

=  

From: = Liubing (Remy) <remy.liubing@huawei.com>
Sent: mercredi 18 juillet 2018 09:38
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Charlie Pe= rkins <charles.perkins@earthlink.net>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org><= br> Subject: Explaining RPLinstance pairing and shift<= /p>

 =

Hello Pas= cal,

&nbs= p;

Regarding= to the discussion that we had at the meeting, I’d like to explain th= e motivation for RPLInstance pairing and Shift.

&nbs= p;

Why we ne= ed RPLInstance pairing?

Multiple = instances can coexist between the same pair of OrigNode and TargNode at the= same time, if two applications running on the TargNode have different requ= irements on routes to the same TargNode, thus the routes need to be built separately. In order to match the RREP-DI= O to the correct RREQ-DIO, the RPLInstanceID must be paired. One convenient= option is to let the RREQ-instance and the RREP-instance share the same ID= . And there will be no conflict because the RPLInstanceID is local and the RREQ and RREP instances have di= fferent DODAGIDs. There can be other ways for pairing but will result in ex= tra overhead because the ID of the RREQ-instance needs to be carried someho= w.

&nbs= p;

Why we ne= ed the shift?

Two OrigN= odes may use the same local RPLInstaceID to find routes to the same TargNod= e at the same time. According to the previous RPLInstaceID pairing mechanis= m, the IDs of the two RREP-instances will be the same as well. However, it is obligate to differentiate the two= RREP-instances. That’s why we need to shift the instance ID to anoth= er one at the TargNode. The original instance ID can be recovered whenever = needed at the intermediate nodes or the OrigNode.

&nbs= p;

Many than= ks for agreeing to review our draft.

&nbs= p;

Best rega= rds,

Remy=

--_000_389acab036d649f1aa74d6ac591574e8XCHRCD001ciscocom_-- From nobody Wed Jul 18 19:20:39 2018 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 E8F17130DC1 for ; Wed, 18 Jul 2018 19:20:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 PhEbUGmQur8d for ; Wed, 18 Jul 2018 19:20:35 -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 54DAE130E18 for ; Wed, 18 Jul 2018 19:20:35 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 600A72008C for ; Wed, 18 Jul 2018 22:36:24 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id 584391A76; Wed, 18 Jul 2018 22:16:00 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 55F811A54 for ; Wed, 18 Jul 2018 22:16:00 -0400 (EDT) From: Michael Richardson To: Routing Over Low power and Lossy networks In-Reply-To: References: X-Mailer: MH-E 8.6; nmh 1.7+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] rpl routing and linux-kernel X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 02:20:38 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, I'm not sure that the ROLL list is a good place for Linux-specific implementation questions. In particular, it seems that most implementers a= re on monolithic embedded kernels (contiki, openwsn, etc.) There are discussions on unstrung-workers@lists.sandelman.ca about Linux kernel integration (none recently through). Discussions also occur on linux-wpan@vger.kernel.org. It would be a good place to start a new thread. Rahul Jadhav wrote: > Hello ROLL, > While trying to integrate RPL with linux kernel and we had certain > design choices. In that context I have some specific questions, > especially towards linux-kernel integration and not towards RPL > protocol implementation itself. Assuming RPL implementation will be in > userspace, questions are: > 1. We can add/del routes using rtnetlink interfaces ... this can be > used for the routes learnt by RPL as well ... But RPL needs to > maintain some additional per-route information on the 6LBR ... To be > very specific, we need to store parent information in context to every > route. Is it possible to do it with rtnetlink? I didn't find an option > to do that. If it ain't possible then what could be an alt approach? > 2. RPL requires that certain extended ipv6 options be added in data > flows .. What is the best way to do this? It is possible to do this > with netfilter+libnfq but i m not sure whether this is the best > approach. > If there is anyone who tried this before, it would be great to have a > discussion in person while we are in IETF102. Please let know if you > are available for discussion. > Thanks, > Rahul > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll =2D-=20 Michael Richardson , Sandelman Software Works -=3D IPv6 IoT consulting =3D- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBW0/0XYCLcPvd0N1lAQKKQwf+IiN+bsCxfvVSyZYSlk1X2f5WxKfC+Sdp fzUIWHpEwnDgTzHLa6uWBtJoKoWX7riWD8GW9QstUkMaxhgQhuSjmATyIDBxAuJA 5SI2n45BCzIYmZMX7zJc0BoXA89NeAeqeeYHcGdcXJsQe655U+Fi0bitAC+DBCxB yiN4WnAcbVtUDvO712Zcvr0PydBUKjtggsrzY1+uQL01IdP/SLJ89hYF1ae6xEM4 1l2O7xucvuGWBSqRujwq5DHBplI7mgcKhcoMDT7QYM4muBBjYyeZtFXjmAeWyRYp pMas6leFGDZvcnuW4oD+c8Qm5y8H6T+U3KH3gaRZ2cofaARnRqPjyw== =8QPT -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Jul 19 06:27:50 2018 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 BEEAF130DF3 for ; Thu, 19 Jul 2018 06:27:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mail-udp-cl.20150623.gappssmtp.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 l0lHw-qDk-WS for ; Thu, 19 Jul 2018 06:27:45 -0700 (PDT) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 98909130DEA for ; Thu, 19 Jul 2018 06:27:45 -0700 (PDT) Received: by mail-it0-x235.google.com with SMTP id h2-v6so9170612itj.1 for ; Thu, 19 Jul 2018 06:27:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail-udp-cl.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=6Idgv3MbKFnAwF7OF4lxSkGaLSv+7DDMaf51v1OfkkU=; b=0rpRZozTzS0o4ejeJnISvjXYhXAJ9M5VhC91PXgIEzijybKhOYJ8XyTCsDqMMBjMhQ jXAQweohU0v7gYDpYTJf3yTM7cm4Efqp51pUDzb/zdSeI/0YtI2d2UodoTlZ/5BwrmaI IUabN9X+cRlnvFxWZYRX8J8JjKzHjwx65BirNive5c3xqE2/xI9ggpDB6Hk7pvp4XXgp kqrMdI9ori6UMMiwAyd8s9Kc8itLfUuyXqT1m8jgRYnZWRzlJar1QcRMaYscXzeZY8++ qWsJ0ANR7OcjyPDTd8dj4/H+oCJ2eDTfKAzERIZ53BRkgFcfOBLhiyep1TSVP+DYMcpb HYAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=6Idgv3MbKFnAwF7OF4lxSkGaLSv+7DDMaf51v1OfkkU=; b=IQVoy5zJCIAWwoQzTrCSxocfnebr7KA7GzKcothjmHwYx4Vxgfb7Ml4U71YGZw4s6G 2T1RbWhlSUUiRdvWr85ESj+MfCg7qdstoNVrJWilwywDBgNRo1PKwpaoy+O+soFkuh5A MmIvGrX4ntKDyfetG4+aJWFMDhdrgSVSUrbQSih2akLn5uMZcckWuDGwRKAyPKKk4tyi VFAZk1ihNM1J+nE0nk3K+H3iaaYrfKh6SOe/G4rXEtuhlqEqHVZB3iyjM7TN7MN93COn jx6sq1rpv8VVwhp3nxrBLKFqUMvNtjxtpPZBBfPUvKoeojQRDQlbxGf8rhdb7Fc586d/ +8qw== X-Gm-Message-State: AOUpUlHpK0EsZ/rEG7/NzJiju9E7U9R/g5ATA150QkxbT8YcPihZsoEJ fyizW2NkwneGk2BwHlx985Um9FAPjm0G65a10nO51DS0ijg= X-Google-Smtp-Source: AAOMgpf97AYzAVUDOuifByNmJo+NHv5U0je0enLLoJenVvT/TJhwsqsnrhfvETRuwL/rQ4UwsuOTHio5bS8dx6OvG7g= X-Received: by 2002:aca:cc0b:: with SMTP id c11-v6mr10587683oig.314.1532006864765; Thu, 19 Jul 2018 06:27:44 -0700 (PDT) MIME-Version: 1.0 References: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> In-Reply-To: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> From: "Prof. Diego Dujovne" Date: Thu, 19 Jul 2018 09:27:30 -0400 Message-ID: To: consultancy@vanderstok.org, roll Content-Type: multipart/alternative; boundary="000000000000f7dd9105715a24f4" Archived-At: Subject: Re: [Roll] acceptance of individual drafts X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 13:27:49 -0000 --000000000000f7dd9105715a24f4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Peter, I will review koutsiamanis-roll-nsa-extension. Regards, Diego Dujovne El mar., 17 de jul. de 2018 14:25, Peter van der Stok escribi=C3=B3: > Hi Roll, > > This morning we had several interesting presentations of individual draft= s. > They all fit within the charter of ROLL, and represent worthy subjects. > > It would be pleasure to take them in as roll WG documents, provided there > is enough interest in the WG to work on the subjects. > > Below there is a list of drafts for which I like an answer to the > following questions: > Did you read a version of the document, > Do you intend to read a version of the document. > Will you react on the ML concerning the document. > Are you willing to do a review of the document? > Will you contribute to the document? > > Answering to only one question positively for a subset of the documents i= s > probably sufficient to gauge interest. > > The list of drafts is: > Bier RPL design team document > rahul-roll-rpl-observation > koutsiamanis-roll-nsa-estension > ji-roll-traffic-aware-objective function > thubert-roll-unaware-leaves > > > For draft rahul-rpl-observation, the consideration that it should go to > RFC is no relevant for these questions, because we can use the document > extensively in the WG without publishing it in the end. > > Thanks for your reactions and contributions. > > Peter&Ines > -- > Peter van der Stok > vanderstok consultancy > mailto: consultancy@vanderstok.org > www: www.vanderstok.org > tel NL: +31(0)492474673 F: +33(0)966015248 > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll > --000000000000f7dd9105715a24f4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Peter,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 I will review=C2=A0
koutsiamanis-roll-nsa-= e= xtension.
Regards,

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0Diego Dujovne

El mar., 17 de jul. de 2018 14:25, Peter van der Stok <stokcons@bbhmail.nl> escribi=C3=B3:=
Hi Roll,

This morning we had several interesting presentations of in= dividual drafts.
They all fit within the charter of ROLL, and represent = worthy subjects.

It would be pleasure to take them in as roll WG doc= uments, provided there is enough interest in the WG to work on the subjects= .

Below there is a list of drafts for which I like an answer to the = following questions:
Did you read a version of the document,
Do you i= ntend to read a version of the document.
Will you react on the ML concer= ning the document.
Are you willing to do a review of the document?
Wi= ll you contribute to the document?

Answering to only one question po= sitively for a subset of the documents is probably sufficient to gauge inte= rest.

The list of drafts is:
Bier RPL design team document
rah= ul-roll-rpl-observation
koutsiamanis-roll-nsa-estension
ji-roll-traff= ic-aware-objective function
thubert-roll-unaware-leaves


For d= raft rahul-rpl-observation, the consideration that it should go to RFC is n= o relevant for these questions, because we can use the document extensively= in the WG without publishing it in the end.

Thanks for your reactio= ns and contributions.

Peter&Ines
--
Peter van der Stok
vanderstok consultancy
mailto: <= a href=3D"mailto:consultancy@vanderstok.org" target=3D"_blank" rel=3D"noref= errer">consultancy@vanderstok.org
www: www.vanderstok.or= g
tel NL: +31(0)492474673 =C2=A0=C2=A0=C2=A0=C2=A0F: +33(0)96601524= 8
_______________________________________________
Roll mailing list
Roll@= ietf.org
https://www.ietf.org/mailman/listinfo/roll<= br>
--000000000000f7dd9105715a24f4-- From nobody Thu Jul 19 06:35:48 2018 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 D4CFE130F47 for ; Thu, 19 Jul 2018 06:35:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 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_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 FBqpFDXZtQ9w for ; Thu, 19 Jul 2018 06:35:42 -0700 (PDT) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::234]) (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 0F046130F06 for ; Thu, 19 Jul 2018 06:35:42 -0700 (PDT) Received: by mail-ua0-x234.google.com with SMTP id r10-v6so5192459uao.1 for ; Thu, 19 Jul 2018 06:35:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=7/2WNzK22xt0qCLnrTtqkKHzFIlB2QKSkBjeRPts5aM=; b=hzlEIe3NtUprfbpOJ5xFNBGn10evBmzKl4Ys/i9dPwuWM2KDbtFK+1uXbJXZUtupIY pGMd4AfWsLfYSrUiNhG6dDDWOLdfgzSiXx5/Mso3G9mhwz85thxH3oWHhZZZRneFNQ1l bjyY48EN4mT0nrMBHhBlXTtiysFbCpY7omYFIoa4rUlUOY8N5eG4QLsZrhB+/XrhLxLB 2LnSgq9/wI+yc1kStB7puhAtW6P4EU7S9TaeTzA0E2bUA7GT62q1h3ZhsHDPo8ZZmowy JJRMwavFC4AuiA9nN6eP1PBz8n0ByXZ7PvSvK/FEfXBFYIQtNZUDHeqF/lmkSgaABGP+ hEGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=7/2WNzK22xt0qCLnrTtqkKHzFIlB2QKSkBjeRPts5aM=; b=kqSwuu/YyGh1RvRGKX3iF7v03engbalefhOxdGjMY5Tf1gw7YBdmQHRIIsvkv3Nu2g BkGHVd3NOu3ayjsrXaLeGZPRmowSD3B9ra0TtIM+NKystDauRIOO09gi1LvBNDgYx+sH 5uzbIyBWbC+tOtT6jF1NbJ+YZurcLdc5d2IKNLjcxMZYC0+BRUNMHh38FqpG8ECCUiOV u9lkb0sEmc+zpkwaFS5CiiYzw1T/542023z8+z1tLzjKf6WHiN0HSlZjGk7Siavjqw9M +0eR+i3gqrwNkRkndrkJCqWwgNcGJwCMX2iKaLg5T7KWyRdJl/Aom6CZVd8tCGHW+DBR lGFw== X-Gm-Message-State: AOUpUlFEu3pDuvg4jV3iXuQWxUTQ5hCCtxbXDQzI30JwWY4HGMRwvR3+ wNygiKpH+z4l+1zyn0535+4EYfPFHzAqBEzG+q8JOEii X-Google-Smtp-Source: AAOMgpevDy4AnPrIn3/NdEIrDGEF0xEUFsLlOADy0g4HLN/to+/jS32MMLERq/5Kr3UbQot/HH9DqNowJnE7IOy71PU= X-Received: by 2002:ab0:4946:: with SMTP id a6-v6mr6684088uad.82.1532007340622; Thu, 19 Jul 2018 06:35:40 -0700 (PDT) MIME-Version: 1.0 References: <17294.1531966560@localhost> In-Reply-To: <17294.1531966560@localhost> From: Rahul Jadhav Date: Thu, 19 Jul 2018 09:35:44 -0400 Message-ID: To: Routing Over Low power and Lossy networks Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Roll] rpl routing and linux-kernel X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 13:35:47 -0000 Thanks Michael for the pointers. Will followup on linux-wpan@vger.kernel.org On Wed, 18 Jul 2018 at 22:20, Michael Richardson wrote: > > > Hi, I'm not sure that the ROLL list is a good place for Linux-specific > implementation questions. In particular, it seems that most implementers are > on monolithic embedded kernels (contiki, openwsn, etc.) > > There are discussions on unstrung-workers@lists.sandelman.ca about Linux > kernel integration (none recently through). > > Discussions also occur on linux-wpan@vger.kernel.org. > It would be a good place to start a new thread. > > Rahul Jadhav wrote: > > Hello ROLL, > > > While trying to integrate RPL with linux kernel and we had certain > > design choices. In that context I have some specific questions, > > especially towards linux-kernel integration and not towards RPL > > protocol implementation itself. Assuming RPL implementation will be in > > userspace, questions are: > > > 1. We can add/del routes using rtnetlink interfaces ... this can be > > used for the routes learnt by RPL as well ... But RPL needs to > > maintain some additional per-route information on the 6LBR ... To be > > very specific, we need to store parent information in context to every > > route. Is it possible to do it with rtnetlink? I didn't find an option > > to do that. If it ain't possible then what could be an alt approach? > > > 2. RPL requires that certain extended ipv6 options be added in data > > flows .. What is the best way to do this? It is possible to do this > > with netfilter+libnfq but i m not sure whether this is the best > > approach. > > > If there is anyone who tried this before, it would be great to have a > > discussion in person while we are in IETF102. Please let know if you > > are available for discussion. > > > Thanks, > > Rahul > > > _______________________________________________ > > Roll mailing list > > Roll@ietf.org > > https://www.ietf.org/mailman/listinfo/roll > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll From nobody Thu Jul 19 08:40:04 2018 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 29539130ED9 for ; Thu, 19 Jul 2018 08:39:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 JJvvtJ3Qc7sO for ; Thu, 19 Jul 2018 08:39:55 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0157.hostedemail.com [216.40.44.157]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 003A612F1A6 for ; Thu, 19 Jul 2018 08:39:54 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id CADFD837F24C for ; Thu, 19 Jul 2018 15:39:53 +0000 (UTC) X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C X-Spam-Summary: 50, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :, RULES_HIT:41:72:152:355:379:582:800:962:967:973:983:988:989:1152:1189:1208:1221:1260:1263:1313:1314:1345:1381:1431:1436:1437:1516:1517:1518:1534:1541:1575:1588:1589:1592:1594:1711:1714:1730:1776:1792:2525:2561:2564:2682:2685:2829:2859:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3350:3586:3622:3865:3866:3867:3868:3870:3871:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4659:5007:6261:6298:6659:7980:8603:9015:9025:9177:9388:10004:10215:10400:10848:11232:11658:11914:12043:12555:12679:12895:12986:13071:13139:13199:13229:13439:13846:14096:14180:14181:14721:14818:21060:21080:21433:21451:21625:21691:30019:30048:30054, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:25, LUA_SUMMARY:none X-HE-Tag: story50_73797198c5247 X-Filterd-Recvd-Size: 2834 Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf10.hostedemail.com (Postfix) with ESMTPA for ; Thu, 19 Jul 2018 15:39:53 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_495859836ab8988941d11044624da1bd" Date: Thu, 19 Jul 2018 12:39:53 -0300 From: Peter van der Stok To: Roll Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org Message-ID: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> X-Sender: stokcons@bbhmail.nl User-Agent: Roundcube Webmail/1.2.7 X-Originating-IP: [31.133.147.176] Archived-At: Subject: [Roll] github for roll X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 15:39:59 -0000 --=_495859836ab8988941d11044624da1bd Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi Roll, with the help of Jaime a github for roll has been set up; I have invited some authors as members; I made a random selection that covers the roll drafts. Can other interested authors contact me to be added as member (author of draft) And can interested authors enter the draft repositories in the roll WG github. Is anyone opposed to this initiative?? Please let the WG know your opinion. Many thanks, Peter -- Peter van der Stok vanderstok consultancy mailto: consultancy@vanderstok.org www: www.vanderstok.org [1] tel NL: +31(0)492474673 F: +33(0)966015248 Links: ------ [1] http://www.vanderstok.org --=_495859836ab8988941d11044624da1bd Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi Roll,

with the help of Jaime a github for roll has been set u= p;
I have invited some authors as members;
I made a random select= ion that covers the roll drafts.

Can other interested authors co= ntact me to be added as member (author of draft)
And can interested au= thors enter the draft repositories in the roll WG github.

Is any= one opposed to this initiative??

Please let the WG know your opi= nion.

Many thanks,

Peter
--
= Peter van der Stok
vanderstok consultancy
mailto: consultancy@vanderstok.org
www: = = www.vanderstok.org
tel NL: +31(0)492474673    &nbs= p;F: +33(0)966015248
--=_495859836ab8988941d11044624da1bd-- From nobody Thu Jul 19 08:45:35 2018 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 B9C1312F1A6 for ; Thu, 19 Jul 2018 08:45:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 jZGYoLPh0paH for ; Thu, 19 Jul 2018 08:45:29 -0700 (PDT) Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 A878E130E19 for ; Thu, 19 Jul 2018 08:45:28 -0700 (PDT) Received: from lhreml709-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 13CE31739BC6E for ; Thu, 19 Jul 2018 16:45:25 +0100 (IST) Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.399.0; Thu, 19 Jul 2018 16:45:25 +0100 Received: from DGGEMM526-MBS.china.huawei.com ([169.254.7.233]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0382.000; Thu, 19 Jul 2018 23:45:20 +0800 From: "Liubing (Remy)" To: "Pascal Thubert (pthubert)" , Charlie Perkins CC: Routing Over Low power and Lossy networks Thread-Topic: Explaining RPLinstance pairing and shift Thread-Index: AdQemOpvi8XHxI8ZT0iOoB0fk5arcAAQ2FTAACYMe2A= Date: Thu, 19 Jul 2018 15:45:20 +0000 Message-ID: References: <389acab036d649f1aa74d6ac591574e8@XCH-RCD-001.cisco.com> In-Reply-To: <389acab036d649f1aa74d6ac591574e8@XCH-RCD-001.cisco.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.124.182.69] Content-Type: multipart/alternative; boundary="_000_BB09947B5326FE42BA3918FA28765C2EE4F12Cdggemm526mbschina_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [Roll] =?gb2312?b?tPC4tDogRXhwbGFpbmluZyBSUExpbnN0YW5jZSBwYWly?= =?gb2312?b?aW5nIGFuZCBzaGlmdA==?= X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 15:45:33 -0000 --_000_BB09947B5326FE42BA3918FA28765C2EE4F12Cdggemm526mbschina_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGVsbG8gUGFzY2FsLA0KDQpUaGFuayB5b3UgdmVyeSBtdWNoIGZvciB5b3VyIGNvbW1lbnRzLg0K DQpZb3VyIHNvbHV0aW9uIGlzIGRvYWJsZSBhbmQgc3RyYWlnaHRmb3J3YXJkIGZvciBjb21wcmVo ZW5zaW9uLiBZb3Whr3JlIHN1Z2dlc3RpbmcgdGhhdCB0aGUgc2Vjb25kIERPREFHIHVzZXMgKElQ MiwgSUQyKSBhbmQgY2FycmllcyAoSVAxLCBJRDEpIGFzIGFuIG9wdGlvbi4gT3VyIHBhaXJpbmcg YW5kIHNoaWZ0aW5nIG1lY2hhbmlzbXMgaGF2ZSB0aGUgc2FtZSBmdW5jdGlvbmFsaXR5LiBPdXIg c29sdXRpb24gaXMgdG8gdXNlIChJUDIsIElEMSkgZm9yIHRoZSBSUkVQIERPREFHLCBhbmQgSVAx IGlzIGNhcnJpZWQgaW4gdGhlIFRhcmdldCBPcHRpb24uIElmIElEMSBpcyBhbHJlYWR5IG9jY3Vw aWVkIGF0IElQMiwgYSBzaGlmdCBpcyBuZWVkZWQuDQoNClRoZXNlIHR3byBzb2x1dGlvbnMgYXJl IGFsbCBkZXNpZ25lZCBmb3IgobBjb3JuZXIgY2FzZXOhsTogaW4gbW9zdCBjYXNlcywgdGhlcmUg aXMgb25seSBvbmUgaW5zdGFuY2UgYmV0d2VlbiBhIHBhaXIgb2YgT3JpZ05vZGUgYW5kIFRhcmdO b2RlLCBhbmQgaXShr3MgcmFyZSB0aGF0IHR3byBPcmlnTm9kZXMgdXNlIHRoZSBzYW1lIFJQTGlu c3RhbmNlSUQgdG8gYnVpbGQgcm91dGVzIHRvIHRoZSBzYW1lIFRhcmdOb2RlLg0KDQpUaGUgYWR2 YW50YWdlIG9mIG91ciBzb2x1dGlvbiBpcyB0aGF0IGl0IGhhcyBubyBleHRyYSBvdmVyaGVhZCBp biBtb3N0IGNhc2VzLCBiZWNhdXNlIG5vIGV4dHJhIG9wdGlvbiBpcyBuZWVkZWQuDQoNCkJlc3Qg cmVnYXJkcywNClJlbXkNCreivP7IyzogUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KSBbbWFpbHRv OnB0aHViZXJ0QGNpc2NvLmNvbV0NCreiy83KsbzkOiAyMDE4xOo31MIxOcjVIDU6MzANCsrVvP7I yzogTGl1YmluZyAoUmVteSkgPHJlbXkubGl1YmluZ0BodWF3ZWkuY29tPjsgQ2hhcmxpZSBQZXJr aW5zIDxjaGFybGVzLnBlcmtpbnNAZWFydGhsaW5rLm5ldD4NCrOty806IFJvdXRpbmcgT3ZlciBM b3cgcG93ZXIgYW5kIExvc3N5IG5ldHdvcmtzIDxyb2xsQGlldGYub3JnPg0K1vfM4jogUkU6IEV4 cGxhaW5pbmcgUlBMaW5zdGFuY2UgcGFpcmluZyBhbmQgc2hpZnQNCkhlbGxvIFJlbXkgOg0KDQpJ IGFncmVlIHdpdGggYWxsIHRoYXQuIE15IHBvaW50IHdhcyBtb3JlIGEgZm9ybWF0IHF1ZXN0aW9u IGFuZCBkb2VzIG5vdCBzdWdnZXN0IGEgY2hhbmdlIG9mIGRlc2lnbi4NCg0KVGhlIHR1cGxlIChJ UHY2IEAsIGluc3RhbmNlIElEKSBpZGVudGlmaWVzIHVuaXF1ZWx5IGEgRE9EQUcuIEluIHRoZSBj YXNlIG9mIGEgbG9jYWwgaW5zdGFuY2UsIHRoZSBuYW1lIHNwYWNlIG9mIHRoZSBpbnN0YW5jZSBJ RCBpcyBsb2NhbCB0byB0aGUgbm9kZSB0aGF0IG93bnMgdGhlIElQdjYgYWRkcmVzcy4gU28gZmFy IHNvIGdvb2QuDQoNCldpdGggQU9EViBSUEwsIHRoZSBjYWxsZXIgSVAxIGZvcm1zIGEgdHVwbGUg KElQMSwgSUQxKSBmb3IgdGhlIERPREFHIDEgYXNzb2NpYXRlZCB0byB0aGUgUlJFUSwgYW5kIHRo ZSByZXNwb25kZXIgSVAyIGZvcm1zIGFub3RoZXIgKElQMiwgSUQyKSBmb3IgdGhlIERPREFHIDIg YXNzb2NpYXRlZCB0byB0aGUgcmVwbHkuICBUaGUgcGFja2V0cyBmcm9tIHRoZSBjYWxsZXIgYXJl IHRhZ2dlZCB3aXRoIChJUDIsIElEMikgd2hpbGUgcGFja2V0cyBmcm9tIHRoZSByZXNwb25kZXIg YXJlIHRhZ2dlZCAoSVAxLCBJRDEpLg0KDQpJZiB5b3UgbG9vayBhdCBpdCB0aGlzIGlzIHZlcnkg c2ltaWxhciB0byBhIHVzZXItU0FQLCBwcm92aWRlci1TQVAgaW4gT1NJLiBNeSBvbmx5IHF1ZXN0 aW9uIHdhcyB0aGlzIGlkZWEgb2Ygc2hpZnRpbmcuIFdoeSBjYWxsIHRoaW5ncyBzaGlmdHMgd2hl biB0aGUgcG9pbnQgaXMgdGhhdCB0aGVzZSBhcmUgZGlmZmVyZW50IGFuZCB1bnJlbGF0ZWQgaW5z dGFuY2UgSURzLCBmcm9tIGRpZmZlcmVudCBuYW1lc3BhY2VzPyBUaGUgT1NJIHJlc3BvbnNlIHRv IGEgY3JlYXRlX1NBUC5yZXEodXNhcCkgaXMgYSBjcmVhdGVfU0FQLmNvbmYodVNBUCwgcFNBUCkg YW5kIHRoZW4gZm9yIHRoZSBkYXRhIHdlIGhhdmUgZGF0YS5yZXEocFNBUCkgIGFuZCBkYXRhLmlu ZCh1U0FQKS4NCg0KSSB0aG91Z2h0IHlvdaGvZCB1c2UgdGhhdCBjbGFzc2ljYWwgbW9kZWwuIEkg ZXhwZWN0ZWQgdGhhdCB0aGUgUlJFUCB0aGF0IGZvcm1zIHRoZSBET0RBRyAyIGlkZW50aWZpZWQg YnkgKElQMiwgSUQyICl3b3VsZCBoYXZlIGEgbmV3IG9wdGlvbiBpbiBpdCwgbGlrZSBhIElELWNv cnJlbGF0b3Igb3B0aW9uIHRoYXQgd291bGQgY29udGFpbiAoSVAxLCBJRDEpLiBTbyBwZW9wbGUg dGhhdCBzZWUgdGhlIFJSRVAgY2FuIGNvcnJlbGF0ZSB0aGUgMiBlYXNpbHkuDQoNCkRvIEkgbWFr ZSBzZW5zZT8NCg0KUGFzY2FsDQoNCg0KRnJvbTogTGl1YmluZyAoUmVteSkgPHJlbXkubGl1Ymlu Z0BodWF3ZWkuY29tPG1haWx0bzpyZW15LmxpdWJpbmdAaHVhd2VpLmNvbT4+DQpTZW50OiBtZXJj cmVkaSAxOCBqdWlsbGV0IDIwMTggMDk6MzgNClRvOiBQYXNjYWwgVGh1YmVydCAocHRodWJlcnQp IDxwdGh1YmVydEBjaXNjby5jb208bWFpbHRvOnB0aHViZXJ0QGNpc2NvLmNvbT4+OyBDaGFybGll IFBlcmtpbnMgPGNoYXJsZXMucGVya2luc0BlYXJ0aGxpbmsubmV0PG1haWx0bzpjaGFybGVzLnBl cmtpbnNAZWFydGhsaW5rLm5ldD4+DQpDYzogUm91dGluZyBPdmVyIExvdyBwb3dlciBhbmQgTG9z c3kgbmV0d29ya3MgPHJvbGxAaWV0Zi5vcmc8bWFpbHRvOnJvbGxAaWV0Zi5vcmc+Pg0KU3ViamVj dDogRXhwbGFpbmluZyBSUExpbnN0YW5jZSBwYWlyaW5nIGFuZCBzaGlmdA0KDQpIZWxsbyBQYXNj YWwsDQoNClJlZ2FyZGluZyB0byB0aGUgZGlzY3Vzc2lvbiB0aGF0IHdlIGhhZCBhdCB0aGUgbWVl dGluZywgSaGvZCBsaWtlIHRvIGV4cGxhaW4gdGhlIG1vdGl2YXRpb24gZm9yIFJQTEluc3RhbmNl IHBhaXJpbmcgYW5kIFNoaWZ0Lg0KDQpXaHkgd2UgbmVlZCBSUExJbnN0YW5jZSBwYWlyaW5nPw0K TXVsdGlwbGUgaW5zdGFuY2VzIGNhbiBjb2V4aXN0IGJldHdlZW4gdGhlIHNhbWUgcGFpciBvZiBP cmlnTm9kZSBhbmQgVGFyZ05vZGUgYXQgdGhlIHNhbWUgdGltZSwgaWYgdHdvIGFwcGxpY2F0aW9u cyBydW5uaW5nIG9uIHRoZSBUYXJnTm9kZSBoYXZlIGRpZmZlcmVudCByZXF1aXJlbWVudHMgb24g cm91dGVzIHRvIHRoZSBzYW1lIFRhcmdOb2RlLCB0aHVzIHRoZSByb3V0ZXMgbmVlZCB0byBiZSBi dWlsdCBzZXBhcmF0ZWx5LiBJbiBvcmRlciB0byBtYXRjaCB0aGUgUlJFUC1ESU8gdG8gdGhlIGNv cnJlY3QgUlJFUS1ESU8sIHRoZSBSUExJbnN0YW5jZUlEIG11c3QgYmUgcGFpcmVkLiBPbmUgY29u dmVuaWVudCBvcHRpb24gaXMgdG8gbGV0IHRoZSBSUkVRLWluc3RhbmNlIGFuZCB0aGUgUlJFUC1p bnN0YW5jZSBzaGFyZSB0aGUgc2FtZSBJRC4gQW5kIHRoZXJlIHdpbGwgYmUgbm8gY29uZmxpY3Qg YmVjYXVzZSB0aGUgUlBMSW5zdGFuY2VJRCBpcyBsb2NhbCBhbmQgdGhlIFJSRVEgYW5kIFJSRVAg aW5zdGFuY2VzIGhhdmUgZGlmZmVyZW50IERPREFHSURzLiBUaGVyZSBjYW4gYmUgb3RoZXIgd2F5 cyBmb3IgcGFpcmluZyBidXQgd2lsbCByZXN1bHQgaW4gZXh0cmEgb3ZlcmhlYWQgYmVjYXVzZSB0 aGUgSUQgb2YgdGhlIFJSRVEtaW5zdGFuY2UgbmVlZHMgdG8gYmUgY2FycmllZCBzb21laG93Lg0K DQpXaHkgd2UgbmVlZCB0aGUgc2hpZnQ/DQpUd28gT3JpZ05vZGVzIG1heSB1c2UgdGhlIHNhbWUg bG9jYWwgUlBMSW5zdGFjZUlEIHRvIGZpbmQgcm91dGVzIHRvIHRoZSBzYW1lIFRhcmdOb2RlIGF0 IHRoZSBzYW1lIHRpbWUuIEFjY29yZGluZyB0byB0aGUgcHJldmlvdXMgUlBMSW5zdGFjZUlEIHBh aXJpbmcgbWVjaGFuaXNtLCB0aGUgSURzIG9mIHRoZSB0d28gUlJFUC1pbnN0YW5jZXMgd2lsbCBi ZSB0aGUgc2FtZSBhcyB3ZWxsLiBIb3dldmVyLCBpdCBpcyBvYmxpZ2F0ZSB0byBkaWZmZXJlbnRp YXRlIHRoZSB0d28gUlJFUC1pbnN0YW5jZXMuIFRoYXShr3Mgd2h5IHdlIG5lZWQgdG8gc2hpZnQg dGhlIGluc3RhbmNlIElEIHRvIGFub3RoZXIgb25lIGF0IHRoZSBUYXJnTm9kZS4gVGhlIG9yaWdp bmFsIGluc3RhbmNlIElEIGNhbiBiZSByZWNvdmVyZWQgd2hlbmV2ZXIgbmVlZGVkIGF0IHRoZSBp bnRlcm1lZGlhdGUgbm9kZXMgb3IgdGhlIE9yaWdOb2RlLg0KDQpNYW55IHRoYW5rcyBmb3IgYWdy ZWVpbmcgdG8gcmV2aWV3IG91ciBkcmFmdC4NCg0KQmVzdCByZWdhcmRzLA0KUmVteQ0K --_000_BB09947B5326FE42BA3918FA28765C2EE4F12Cdggemm526mbschina_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hello P= ascal,

&n= bsp;

Thank y= ou very much for your comments.

&n= bsp;

Your so= lution is doable and straightforward for comprehension. You=A1=AFre suggest= ing that the second DODAG uses (IP2, ID2) and carries (IP1, ID1) as an opti= on. Our pairing and shifting mechanisms have the same functionality. Our solution is to use (IP2, ID1) for the RREP DOD= AG, and IP1 is carried in the Target Option. If ID1 is already occupied at = IP2, a shift is needed.

&n= bsp;

These t= wo solutions are all designed for =A1=B0corner cases=A1=B1: in most cases, = there is only one instance between a pair of OrigNode and TargNode, and it= =A1=AFs rare that two OrigNodes use the same RPLinstanceID to build routes to the same TargNode.

&n= bsp;

The adv= antage of our solution is that it has no extra overhead in most cases, beca= use no extra option is needed.

&n= bsp;

Best re= gards,

Remy

=B7=A2=BC=FE=C8=CB: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com]
=B7=A2=CB=CD=CA=B1=BC=E4:<= /span> 2018=C4=EA7=D4=C219=C8=D5 5:30
=CA=D5=BC=FE=C8=CB: Liubing (Remy) <remy.liubing@huawei.com>; Charlie Perkins <= ;charles.perkins@earthlink.net>
=B3=AD=CB=CD: Routing Over Low power and Lossy networks <roll@ietf.org>
=D6=F7=CC=E2: RE: Explaining RPLinstance pairing and shift

Hello Remy :

 

I agree with all that. My point was more a format question and do= es not suggest a change of design.

 

The tuple (IPv6 @, instance ID) identifies uniquely a DODAG. In t= he case of a local instance, the name space of the instance ID is local to = the node that owns the IPv6 address. So far so good.

 

With AODV RPL, the caller IP1 forms a tuple (IP1, ID1) for the DO= DAG 1 associated to the RREQ, and the responder IP2 forms another (IP2, ID2= ) for the DODAG 2 associated to the reply.  The packets from the caller are tagged with (IP2, ID2) while packets= from the responder are tagged (IP1, ID1).

 

If you look at it this is very similar to a user-SAP, provider-SA= P in OSI. My only question was this idea of shifting. Why call things shift= s when the point is that these are different and unrelated instance IDs, from different namespaces? The OSI response to= a create_SAP.req(usap) is a create_SAP.conf(uSAP, pSAP) and then for the d= ata we have data.req(pSAP)  and data.ind(uSAP).

 

I thought you=A1=AFd use that classical model. I expected that th= e RREP that forms the DODAG 2 identified by (IP2, ID2 )would have a new opt= ion in it, like a ID-correlator option that would contain (IP1, ID1). So people that see the RREP can correlate the 2 = easily.

 

Do I make sense?

 

Pascal

 

 

From: Liubing (Remy) <remy.liubing@huawei.com>
Sent: mercredi 18 juillet 2018 09:38
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Charlie Perkins <charles.perkins@earthlink.net>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Explaining RPLinstance pairing and shift<= /p>

 

Hello Pascal,=

 

Regarding to the discussion tha= t we had at the meeting, I=A1=AFd like to explain the motivation for RPLIns= tance pairing and Shift.

 

Why we need RPLInstance pairing= ?

Multiple instances can coexist = between the same pair of OrigNode and TargNode at the same time, if two app= lications running on the TargNode have different requirements on routes to = the same TargNode, thus the routes need to be built separately. In order to match the RREP-DIO to the correct RREQ= -DIO, the RPLInstanceID must be paired. One convenient option is to let the= RREQ-instance and the RREP-instance share the same ID. And there will be n= o conflict because the RPLInstanceID is local and the RREQ and RREP instances have different DODAGIDs. There ca= n be other ways for pairing but will result in extra overhead because the I= D of the RREQ-instance needs to be carried somehow.

 

Why we need the shift?

Two OrigNodes may use the same = local RPLInstaceID to find routes to the same TargNode at the same time. Ac= cording to the previous RPLInstaceID pairing mechanism, the IDs of the two = RREP-instances will be the same as well. However, it is obligate to differentiate the two RREP-instances. That=A1= =AFs why we need to shift the instance ID to another one at the TargNode. T= he original instance ID can be recovered whenever needed at the intermediat= e nodes or the OrigNode.

 

Many thanks for agreeing to rev= iew our draft.

 

Best regards,=

Remy

--_000_BB09947B5326FE42BA3918FA28765C2EE4F12Cdggemm526mbschina_-- From nobody Thu Jul 19 09:45:17 2018 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 100B5126CB6 for ; Thu, 19 Jul 2018 09:45:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.51 X-Spam-Level: X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 EI9soPxMMpXj for ; Thu, 19 Jul 2018 09:45:08 -0700 (PDT) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B521130DD1 for ; Thu, 19 Jul 2018 09:45:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22925; q=dns/txt; s=iport; t=1532018708; x=1533228308; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Tpem1hn4L9GSzg7Sqgt3lYYPunPWOXJcXKaLP3462Aw=; b=Jm3U85tHMVQ2omzfEva3yz0UDS4EqSBh7zhsygTZuYCbin8MpXOsLUSC 21JBftE3vAdj4kS5hNvjS8gDNxNCHZSJry83Q7uWZnNR5F52ZzrOMDb0o jo4z/Ir4qBrM3kjG7pHGaQgnzKwfEGIq3PfDqp2V0vUwhqda28CAMtGHl Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CwAAA8v1Bb/4sNJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJXdmN/KAqDdIgEjCyCDHWURoF6C4RsAheCbiE0GAECAQE?= =?us-ascii?q?CAQECbSiFNgEBAQEDLToSEAIBBgIRBAEBKAUCAjAUCQgBAQQBDQUIE4MGgRt?= =?us-ascii?q?MAxWOA5tBCIEsikqJAoFXP4ERghNJNYJWggkzH4JHglkCjFyNDAkCiHCGMo1?= =?us-ascii?q?0kXYCERSBJB04gVJwFYMkkFNviluBGgEB?= X-IronPort-AV: E=Sophos;i="5.51,375,1526342400"; d="scan'208,217";a="208132795" Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2018 16:45:06 +0000 Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id w6JGj6nY027082 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jul 2018 16:45:06 GMT Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 19 Jul 2018 11:45:06 -0500 Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1320.000; Thu, 19 Jul 2018 11:45:06 -0500 From: "Pascal Thubert (pthubert)" To: "Liubing (Remy)" , Charlie Perkins CC: Routing Over Low power and Lossy networks Thread-Topic: Explaining RPLinstance pairing and shift Thread-Index: AdQemOpvi8XHxI8ZT0iOoB0fk5arcAAQ2FTAACYMe2AAAoSdsA== Date: Thu, 19 Jul 2018 16:44:59 +0000 Deferred-Delivery: Thu, 19 Jul 2018 16:44:59 +0000 Message-ID: <85b196caa6eb4e85b3cee161f8fd59e6@XCH-ALN-001.cisco.com> References: <389acab036d649f1aa74d6ac591574e8@XCH-RCD-001.cisco.com> In-Reply-To: Accept-Language: fr-FR, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.24.122.153] Content-Type: multipart/alternative; boundary="_000_85b196caa6eb4e85b3cee161f8fd59e6XCHALN001ciscocom_" MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com X-Outbound-Node: alln-core-6.cisco.com Archived-At: Subject: Re: [Roll] Explaining RPLinstance pairing and shift X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 16:45:14 -0000 --_000_85b196caa6eb4e85b3cee161f8fd59e6XCHALN001ciscocom_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGVsbG8gUmVteSA6ICkNCg0KVGhpcyBpcyBub3QgcmVhbGx5IGFib3V0IDwgc29sdXRpb26hsSBz aW5jZSB3ZSBhZ3JlZSBvbiB0aGUgZmxvd3MuIEl0IGlzIGFib3V0IHNpZ25hbGluZy4gV2hhdKGv cyB0aGUgbW9zdCBhcHByb3ByaWF0ZSB3YXkgdG8gdHJhbnNwb3J0IChJUDEsIElEMSkgYmFjayBz byBpdCBpcyBzZW1hbnRpY2FsbHkgY2xlYXIgYW5kIHVuYW1iaWd1b3VzLg0KVGhlIGRyYWZ0IGlz IG92ZXJsb2FkaW5nIHRhcmdldCBmb3IgSVAxOyBJdCBtYWtlcyBzZW5zZSwgc28geW91IGRvIG5v dCBoYXZlIHRvIHB1dCBpdCB0d2ljZSBpbiB0aGUgcGFja2V0LiBTdGlsbCBJIHNlZSB0aGF0IGFz IGEgY29tcHJlc3Npb24sIGEgcmVmZXJlbmNlLiBTaWduYWxpbmcgd2lzZSwgSaGvbSBPSyB0byBt YWtlIHRoZSBJRDIgYW4gb3B0aW9uIGp1c3QgYmVmb3JlIHRoZSB0YXJnZXQgaXQgcmVsYXRlcyB0 by4gSaGvbSBub3QgaGFwcHkgd2l0aCBjYWxsaW5nIHRoaW5ncyBhIHNoaWZ0LiBJdCBpcyBhIGRp ZmZlcmVudCBJRCBmcm9tIGEgZGlmZmVyZW50IHNwYWNlLiBKdXN0IGNhbGwgaXQgYW4gSUQuDQoN CkFueXdheSwgSaGvbGwgdW5kZXJzdGFuZCBiZXR0ZXIgd2hlbiBJIHJldmlldyB0aGUgYWxsIGRy YWZ0IGFzIHByb21pc2Vkoa0NCg0KQ2hlZXJzLA0KDQpQYXNjYWwNCg0KDQpGcm9tOiBMaXViaW5n IChSZW15KSA8cmVteS5saXViaW5nQGh1YXdlaS5jb20+DQpTZW50OiBqZXVkaSAxOSBqdWlsbGV0 IDIwMTggMTE6NDUNClRvOiBQYXNjYWwgVGh1YmVydCAocHRodWJlcnQpIDxwdGh1YmVydEBjaXNj by5jb20+OyBDaGFybGllIFBlcmtpbnMgPGNoYXJsZXMucGVya2luc0BlYXJ0aGxpbmsubmV0Pg0K Q2M6IFJvdXRpbmcgT3ZlciBMb3cgcG93ZXIgYW5kIExvc3N5IG5ldHdvcmtzIDxyb2xsQGlldGYu b3JnPg0KU3ViamVjdDogtPC4tDogRXhwbGFpbmluZyBSUExpbnN0YW5jZSBwYWlyaW5nIGFuZCBz aGlmdA0KDQpIZWxsbyBQYXNjYWwsDQoNClRoYW5rIHlvdSB2ZXJ5IG11Y2ggZm9yIHlvdXIgY29t bWVudHMuDQoNCllvdXIgc29sdXRpb24gaXMgZG9hYmxlIGFuZCBzdHJhaWdodGZvcndhcmQgZm9y IGNvbXByZWhlbnNpb24uIFlvdaGvcmUgc3VnZ2VzdGluZyB0aGF0IHRoZSBzZWNvbmQgRE9EQUcg dXNlcyAoSVAyLCBJRDIpIGFuZCBjYXJyaWVzIChJUDEsIElEMSkgYXMgYW4gb3B0aW9uLiBPdXIg cGFpcmluZyBhbmQgc2hpZnRpbmcgbWVjaGFuaXNtcyBoYXZlIHRoZSBzYW1lIGZ1bmN0aW9uYWxp dHkuIE91ciBzb2x1dGlvbiBpcyB0byB1c2UgKElQMiwgSUQxKSBmb3IgdGhlIFJSRVAgRE9EQUcs IGFuZCBJUDEgaXMgY2FycmllZCBpbiB0aGUgVGFyZ2V0IE9wdGlvbi4gSWYgSUQxIGlzIGFscmVh ZHkgb2NjdXBpZWQgYXQgSVAyLCBhIHNoaWZ0IGlzIG5lZWRlZC4NCg0KVGhlc2UgdHdvIHNvbHV0 aW9ucyBhcmUgYWxsIGRlc2lnbmVkIGZvciChsGNvcm5lciBjYXNlc6GxOiBpbiBtb3N0IGNhc2Vz LCB0aGVyZSBpcyBvbmx5IG9uZSBpbnN0YW5jZSBiZXR3ZWVuIGEgcGFpciBvZiBPcmlnTm9kZSBh bmQgVGFyZ05vZGUsIGFuZCBpdKGvcyByYXJlIHRoYXQgdHdvIE9yaWdOb2RlcyB1c2UgdGhlIHNh bWUgUlBMaW5zdGFuY2VJRCB0byBidWlsZCByb3V0ZXMgdG8gdGhlIHNhbWUgVGFyZ05vZGUuDQoN ClRoZSBhZHZhbnRhZ2Ugb2Ygb3VyIHNvbHV0aW9uIGlzIHRoYXQgaXQgaGFzIG5vIGV4dHJhIG92 ZXJoZWFkIGluIG1vc3QgY2FzZXMsIGJlY2F1c2Ugbm8gZXh0cmEgb3B0aW9uIGlzIG5lZWRlZC4N Cg0KQmVzdCByZWdhcmRzLA0KUmVteQ0Kt6K8/sjLOiBQYXNjYWwgVGh1YmVydCAocHRodWJlcnQp IFttYWlsdG86cHRodWJlcnRAY2lzY28uY29tXQ0Kt6LLzcqxvOQ6IDIwMTjE6jfUwjE5yNUgNToz MA0KytW8/sjLOiBMaXViaW5nIChSZW15KSA8cmVteS5saXViaW5nQGh1YXdlaS5jb208bWFpbHRv OnJlbXkubGl1YmluZ0BodWF3ZWkuY29tPj47IENoYXJsaWUgUGVya2lucyA8Y2hhcmxlcy5wZXJr aW5zQGVhcnRobGluay5uZXQ8bWFpbHRvOmNoYXJsZXMucGVya2luc0BlYXJ0aGxpbmsubmV0Pj4N CrOty806IFJvdXRpbmcgT3ZlciBMb3cgcG93ZXIgYW5kIExvc3N5IG5ldHdvcmtzIDxyb2xsQGll dGYub3JnPG1haWx0bzpyb2xsQGlldGYub3JnPj4NCtb3zOI6IFJFOiBFeHBsYWluaW5nIFJQTGlu c3RhbmNlIHBhaXJpbmcgYW5kIHNoaWZ0DQpIZWxsbyBSZW15IDoNCg0KSSBhZ3JlZSB3aXRoIGFs bCB0aGF0LiBNeSBwb2ludCB3YXMgbW9yZSBhIGZvcm1hdCBxdWVzdGlvbiBhbmQgZG9lcyBub3Qg c3VnZ2VzdCBhIGNoYW5nZSBvZiBkZXNpZ24uDQoNClRoZSB0dXBsZSAoSVB2NiBALCBpbnN0YW5j ZSBJRCkgaWRlbnRpZmllcyB1bmlxdWVseSBhIERPREFHLiBJbiB0aGUgY2FzZSBvZiBhIGxvY2Fs IGluc3RhbmNlLCB0aGUgbmFtZSBzcGFjZSBvZiB0aGUgaW5zdGFuY2UgSUQgaXMgbG9jYWwgdG8g dGhlIG5vZGUgdGhhdCBvd25zIHRoZSBJUHY2IGFkZHJlc3MuIFNvIGZhciBzbyBnb29kLg0KDQpX aXRoIEFPRFYgUlBMLCB0aGUgY2FsbGVyIElQMSBmb3JtcyBhIHR1cGxlIChJUDEsIElEMSkgZm9y IHRoZSBET0RBRyAxIGFzc29jaWF0ZWQgdG8gdGhlIFJSRVEsIGFuZCB0aGUgcmVzcG9uZGVyIElQ MiBmb3JtcyBhbm90aGVyIChJUDIsIElEMikgZm9yIHRoZSBET0RBRyAyIGFzc29jaWF0ZWQgdG8g dGhlIHJlcGx5LiAgVGhlIHBhY2tldHMgZnJvbSB0aGUgY2FsbGVyIGFyZSB0YWdnZWQgd2l0aCAo SVAyLCBJRDIpIHdoaWxlIHBhY2tldHMgZnJvbSB0aGUgcmVzcG9uZGVyIGFyZSB0YWdnZWQgKElQ MSwgSUQxKS4NCg0KSWYgeW91IGxvb2sgYXQgaXQgdGhpcyBpcyB2ZXJ5IHNpbWlsYXIgdG8gYSB1 c2VyLVNBUCwgcHJvdmlkZXItU0FQIGluIE9TSS4gTXkgb25seSBxdWVzdGlvbiB3YXMgdGhpcyBp ZGVhIG9mIHNoaWZ0aW5nLiBXaHkgY2FsbCB0aGluZ3Mgc2hpZnRzIHdoZW4gdGhlIHBvaW50IGlz IHRoYXQgdGhlc2UgYXJlIGRpZmZlcmVudCBhbmQgdW5yZWxhdGVkIGluc3RhbmNlIElEcywgZnJv bSBkaWZmZXJlbnQgbmFtZXNwYWNlcz8gVGhlIE9TSSByZXNwb25zZSB0byBhIGNyZWF0ZV9TQVAu cmVxKHVzYXApIGlzIGEgY3JlYXRlX1NBUC5jb25mKHVTQVAsIHBTQVApIGFuZCB0aGVuIGZvciB0 aGUgZGF0YSB3ZSBoYXZlIGRhdGEucmVxKHBTQVApICBhbmQgZGF0YS5pbmQodVNBUCkuDQoNCkkg dGhvdWdodCB5b3Whr2QgdXNlIHRoYXQgY2xhc3NpY2FsIG1vZGVsLiBJIGV4cGVjdGVkIHRoYXQg dGhlIFJSRVAgdGhhdCBmb3JtcyB0aGUgRE9EQUcgMiBpZGVudGlmaWVkIGJ5IChJUDIsIElEMiAp d291bGQgaGF2ZSBhIG5ldyBvcHRpb24gaW4gaXQsIGxpa2UgYSBJRC1jb3JyZWxhdG9yIG9wdGlv biB0aGF0IHdvdWxkIGNvbnRhaW4gKElQMSwgSUQxKS4gU28gcGVvcGxlIHRoYXQgc2VlIHRoZSBS UkVQIGNhbiBjb3JyZWxhdGUgdGhlIDIgZWFzaWx5Lg0KDQpEbyBJIG1ha2Ugc2Vuc2U/DQoNClBh c2NhbA0KDQoNCkZyb206IExpdWJpbmcgKFJlbXkpIDxyZW15LmxpdWJpbmdAaHVhd2VpLmNvbTxt YWlsdG86cmVteS5saXViaW5nQGh1YXdlaS5jb20+Pg0KU2VudDogbWVyY3JlZGkgMTgganVpbGxl dCAyMDE4IDA5OjM4DQpUbzogUGFzY2FsIFRodWJlcnQgKHB0aHViZXJ0KSA8cHRodWJlcnRAY2lz Y28uY29tPG1haWx0bzpwdGh1YmVydEBjaXNjby5jb20+PjsgQ2hhcmxpZSBQZXJraW5zIDxjaGFy bGVzLnBlcmtpbnNAZWFydGhsaW5rLm5ldDxtYWlsdG86Y2hhcmxlcy5wZXJraW5zQGVhcnRobGlu ay5uZXQ+Pg0KQ2M6IFJvdXRpbmcgT3ZlciBMb3cgcG93ZXIgYW5kIExvc3N5IG5ldHdvcmtzIDxy b2xsQGlldGYub3JnPG1haWx0bzpyb2xsQGlldGYub3JnPj4NClN1YmplY3Q6IEV4cGxhaW5pbmcg UlBMaW5zdGFuY2UgcGFpcmluZyBhbmQgc2hpZnQNCg0KSGVsbG8gUGFzY2FsLA0KDQpSZWdhcmRp bmcgdG8gdGhlIGRpc2N1c3Npb24gdGhhdCB3ZSBoYWQgYXQgdGhlIG1lZXRpbmcsIEmhr2QgbGlr ZSB0byBleHBsYWluIHRoZSBtb3RpdmF0aW9uIGZvciBSUExJbnN0YW5jZSBwYWlyaW5nIGFuZCBT aGlmdC4NCg0KV2h5IHdlIG5lZWQgUlBMSW5zdGFuY2UgcGFpcmluZz8NCk11bHRpcGxlIGluc3Rh bmNlcyBjYW4gY29leGlzdCBiZXR3ZWVuIHRoZSBzYW1lIHBhaXIgb2YgT3JpZ05vZGUgYW5kIFRh cmdOb2RlIGF0IHRoZSBzYW1lIHRpbWUsIGlmIHR3byBhcHBsaWNhdGlvbnMgcnVubmluZyBvbiB0 aGUgVGFyZ05vZGUgaGF2ZSBkaWZmZXJlbnQgcmVxdWlyZW1lbnRzIG9uIHJvdXRlcyB0byB0aGUg c2FtZSBUYXJnTm9kZSwgdGh1cyB0aGUgcm91dGVzIG5lZWQgdG8gYmUgYnVpbHQgc2VwYXJhdGVs eS4gSW4gb3JkZXIgdG8gbWF0Y2ggdGhlIFJSRVAtRElPIHRvIHRoZSBjb3JyZWN0IFJSRVEtRElP LCB0aGUgUlBMSW5zdGFuY2VJRCBtdXN0IGJlIHBhaXJlZC4gT25lIGNvbnZlbmllbnQgb3B0aW9u IGlzIHRvIGxldCB0aGUgUlJFUS1pbnN0YW5jZSBhbmQgdGhlIFJSRVAtaW5zdGFuY2Ugc2hhcmUg dGhlIHNhbWUgSUQuIEFuZCB0aGVyZSB3aWxsIGJlIG5vIGNvbmZsaWN0IGJlY2F1c2UgdGhlIFJQ TEluc3RhbmNlSUQgaXMgbG9jYWwgYW5kIHRoZSBSUkVRIGFuZCBSUkVQIGluc3RhbmNlcyBoYXZl IGRpZmZlcmVudCBET0RBR0lEcy4gVGhlcmUgY2FuIGJlIG90aGVyIHdheXMgZm9yIHBhaXJpbmcg YnV0IHdpbGwgcmVzdWx0IGluIGV4dHJhIG92ZXJoZWFkIGJlY2F1c2UgdGhlIElEIG9mIHRoZSBS UkVRLWluc3RhbmNlIG5lZWRzIHRvIGJlIGNhcnJpZWQgc29tZWhvdy4NCg0KV2h5IHdlIG5lZWQg dGhlIHNoaWZ0Pw0KVHdvIE9yaWdOb2RlcyBtYXkgdXNlIHRoZSBzYW1lIGxvY2FsIFJQTEluc3Rh Y2VJRCB0byBmaW5kIHJvdXRlcyB0byB0aGUgc2FtZSBUYXJnTm9kZSBhdCB0aGUgc2FtZSB0aW1l LiBBY2NvcmRpbmcgdG8gdGhlIHByZXZpb3VzIFJQTEluc3RhY2VJRCBwYWlyaW5nIG1lY2hhbmlz bSwgdGhlIElEcyBvZiB0aGUgdHdvIFJSRVAtaW5zdGFuY2VzIHdpbGwgYmUgdGhlIHNhbWUgYXMg d2VsbC4gSG93ZXZlciwgaXQgaXMgb2JsaWdhdGUgdG8gZGlmZmVyZW50aWF0ZSB0aGUgdHdvIFJS RVAtaW5zdGFuY2VzLiBUaGF0oa9zIHdoeSB3ZSBuZWVkIHRvIHNoaWZ0IHRoZSBpbnN0YW5jZSBJ RCB0byBhbm90aGVyIG9uZSBhdCB0aGUgVGFyZ05vZGUuIFRoZSBvcmlnaW5hbCBpbnN0YW5jZSBJ RCBjYW4gYmUgcmVjb3ZlcmVkIHdoZW5ldmVyIG5lZWRlZCBhdCB0aGUgaW50ZXJtZWRpYXRlIG5v ZGVzIG9yIHRoZSBPcmlnTm9kZS4NCg0KTWFueSB0aGFua3MgZm9yIGFncmVlaW5nIHRvIHJldmll dyBvdXIgZHJhZnQuDQoNCkJlc3QgcmVnYXJkcywNClJlbXkNCg== --_000_85b196caa6eb4e85b3cee161f8fd59e6XCHALN001ciscocom_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hello Remy : )

 

This is not really about « solution=A1=B1 = since we agree on the flows. It is about signaling. What=A1=AFs the most ap= propriate way to transport (IP1, ID1) back so it is semanti= cally clear and unambiguous.

The draft is overloading target for IP1; It makes sen= se, so you do not have to put it twice in the packet. Still I see that as a= compression, a reference. Signaling wise, I=A1=AFm OK to make the ID2 an option just before the target it rela= tes to. I=A1=AFm not happy with calling things a shift. It is a different I= D from a different space. Just call it an ID.

 

Anyway, I=A1=AFll understand better when I review the= all draft as promised=A1=AD

 

Cheers,

 

Pascal

 

 

From: = Liubing (Remy) <remy.liubing@huawei.com>
Sent: jeudi 19 juillet 2018 11:45
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Charlie Pe= rkins <charles.perkins@earthlink.net>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org><= br> Subject: =B4=F0=B8=B4: Explai= ning RPLinstance pairing and shift

 =

Hello Pascal,

 

Thank you very much fo= r your comments.

 

Your solution is doabl= e and straightforward for comprehension. You=A1=AFre suggesting that the se= cond DODAG uses (IP2, ID2) and carries (IP1, ID1) as an option. Our pairing= and shifting mechanisms have the same functionality. Our solution is to use (IP2, ID1) for the RREP DODAG, and IP1 is carried i= n the Target Option. If ID1 is already occupied at IP2, a shift is needed.<= o:p>

 

These two solutions ar= e all designed for =A1=B0corner cases=A1=B1: in most cases, there is only o= ne instance between a pair of OrigNode and TargNode, and it=A1=AFs rare tha= t two OrigNodes use the same RPLinstanceID to build routes to the same TargNode.

 

The advantage of our s= olution is that it has no extra overhead in most cases, because no extra op= tion is needed.

 

Best regards,

Remy=

=B7=A2=BC=FE=C8=CB: Pascal Thubert (pthubert) [mailto:pt= hubert@cisco.com]
=B7=A2=CB=CD=CA=B1=BC=E4: 2018=C4=EA7=D4=C219=C8=D5 5:30
=CA=D5=BC=FE=C8=CB: Liubing (Remy) <<= a href=3D"mailto:remy.liubing@huawei.com">remy.liubing@huawei.com>; = Charlie Perkins <charle= s.perkins@earthlink.net>
=B3=AD=CB=CD: Routing Over Low power and= Lossy networks <roll@ietf.org><= br> =D6=F7=CC=E2: RE: Explaining RPLinstance= pairing and shift

Hello Remy :

 

I agr= ee with all that. My point was more a format question and does not suggest = a change of design.

=  

The t= uple (IPv6 @, instance ID) identifies uniquely a DODAG. In the case of a lo= cal instance, the name space of the instance ID is local to the node that o= wns the IPv6 address. So far so good.

=  

With = AODV RPL, the caller IP1 forms a tuple (IP1, ID1) for the DODAG 1 associate= d to the RREQ, and the responder IP2 forms another (IP2, ID2) for the DODAG= 2 associated to the reply.  The packets from the caller are tagged with (IP2, ID2) while packets from the responde= r are tagged (IP1, ID1).

=  

If yo= u look at it this is very similar to a user-SAP, provider-SAP in OSI. My on= ly question was this idea of shifting. Why call things shifts when the poin= t is that these are different and unrelated instance IDs, from different namespaces? The OSI response to a create_SAP.= req(usap) is a create_SAP.conf(uSAP, pSAP) and then for the data we have da= ta.req(pSAP)  and data.ind(uSAP).

=  

I tho= ught you=A1=AFd use that classical model. I expected that the RREP that for= ms the DODAG 2 identified by (IP2, ID2 )would have a new option in it, like= a ID-correlator option that would contain (IP1, ID1). So people that see the RREP can correlate the 2 easily. <= /o:p>

=  

Do I = make sense?

=  

Pasca= l

=  

=  

From: = Liubing (Remy) <remy.liubing@= huawei.com>
Sent: mercredi 18 juillet 2018 09:38
To: Pascal Thubert (pthubert) <pthubert@cisco.com>; Charlie Perkins <charles.perkins@earthlink.net>
Cc: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Explaining RPLinstance pairing and shift<= /p>

 =

Hello Pascal,

 

Regarding to the discussion that we had at the meeti= ng, I=A1=AFd like to explain the motivation for RPLInstance pairing and Shi= ft.

 

Why we need RPLInstance pairing?

Multiple instances can coexist between the same pair= of OrigNode and TargNode at the same time, if two applications running on = the TargNode have different requirements on routes to the same TargNode, th= us the routes need to be built separately. In order to match the RREP-DIO to the correct RREQ-DIO, the RPLInstanceID = must be paired. One convenient option is to let the RREQ-instance and the R= REP-instance share the same ID. And there will be no conflict because the R= PLInstanceID is local and the RREQ and RREP instances have different DODAGIDs. There can be other ways for pa= iring but will result in extra overhead because the ID of the RREQ-instance= needs to be carried somehow.

 

Why we need the shift?

Two OrigNodes may use the same local RPLInstaceID to= find routes to the same TargNode at the same time. According to the previo= us RPLInstaceID pairing mechanism, the IDs of the two RREP-instances will b= e the same as well. However, it is obligate to differentiate the two RREP-instances. That=A1=AFs why we need = to shift the instance ID to another one at the TargNode. The original insta= nce ID can be recovered whenever needed at the intermediate nodes or the Or= igNode.

 

Many thanks for agreeing to review our draft.

 

Best regards,

Remy

--_000_85b196caa6eb4e85b3cee161f8fd59e6XCHALN001ciscocom_-- From nobody Thu Jul 19 19:34:56 2018 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 CCE81130E12; Thu, 19 Jul 2018 19:34:49 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: roll@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: roll@ietf.org Message-ID: <153205408976.10604.14398437854810525618@ietfa.amsl.com> Date: Thu, 19 Jul 2018 19:34:49 -0700 Archived-At: Subject: [Roll] I-D Action: draft-ietf-roll-efficient-npdao-04.txt X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 List-Id: Routing Over Low power and Lossy networks List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jul 2018 02:34:50 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Routing Over Low power and Lossy networks WG of the IETF. Title : Efficient Route Invalidation Authors : Rahul Arvind Jadhav Pascal Thubert Rabi Narayan Sahoo Zhen Cao Filename : draft-ietf-roll-efficient-npdao-04.txt Pages : 15 Date : 2018-07-19 Abstract: This document describes the problems associated with the use of No- Path DAO messaging in RPL and signaling changes to improve route invalidation efficiency. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-roll-efficient-npdao-04 https://datatracker.ietf.org/doc/html/draft-ietf-roll-efficient-npdao-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-roll-efficient-npdao-04 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Jul 19 19:45:09 2018 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 0600013103F for ; Thu, 19 Jul 2018 19:45:07 -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, 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 XoRJV0U-APel for ; Thu, 19 Jul 2018 19:45:04 -0700 (PDT) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 59397130E12 for ; Thu, 19 Jul 2018 19:45:04 -0700 (PDT) Received: by mail-ua0-x230.google.com with SMTP id r10-v6so6558336uao.1 for ; Thu, 19 Jul 2018 19:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=1OwSmKRLbZAnvefMkclMLn6xvFTBggDoaompymRPuSI=; b=Fcd8KJf089JTYFNnN1znFy/fKB2poxd4a4vcLZbPDCd99IOF64AvBvYc29XwyPvB/D 2N69KtSRc/SfFC1sWUOfKwk1e0ZB6AnbyKZUow9rNH4OYXueTYLM1EEpLXTBHxwME74V fhrt4glssO2QdjglqyozD+b53mNfoJGvCasK7y4j+aeLe+MD15XovNgi6lKu9ck8nzrz UawT0/MSGCQYbqMp7cyxdcQ+nKeuCqiVqqkR0axXKCmsKFaAIemt2FnYhzaKxtWVI8Vp BHsTYy+izhFZ4hOVrtCURXTQWUg6VddnetRlNf/hO8zeYjzBvk9v8qd3eImZ643F8Pi7 42Tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=1OwSmKRLbZAnvefMkclMLn6xvFTBggDoaompymRPuSI=; b=IUyGfyBdF3LttAS55Vyw3M8+rtXsLBu+36KnQxQ/GggzZd3rzBLQE+DTHM4P95UV3u 7ZhpnMXPYhtEAiFnPu/12edcQB3ePWWr09DokG4VibdHQrb5vQrp41i2S+VDefpAgRqM K2s+th3Jy6XFsrE9wTxPSIDpVDa/TX+KmCrC+jOWSOICd8um2GDM7aifGCv28qaZf94t B/DehdaKyc6mD7pJl4eDmwA8khytzLl7nekziAECa9L3NbUTW6GiSXKMolEJUjuT4bQL 5j5mazxHFRwxPG8KFKamy4E38uo1XuXnBBswARVfsZDQ74CbW9BsLO+dnlmfWUWnMajH cPRQ== X-Gm-Message-State: AOUpUlFJJG8IrWlQPo4ceh+Y2C+hQLpl69WIHeBNAq5mi9j8VOe56qOG 7+FE/QAaNXAFR1sSWC5HR5nj9TCm9G+xSnFcSRKtxABtIB0= X-Google-Smtp-Source: AAOMgpcE2c/uycVBR2W2oDn0htjgSFKr9yb05zj7rMOD9aaJjTD8kRxKJzvUJV7bE3QdQ0yDJ/dtURe6RiMBQg/5Ts4= X-Received: by 2002:ab0:25cc:: with SMTP id y12-v6mr127456uan.188.1532054703149; Thu, 19 Jul 2018 19:45:03 -0700 (PDT) MIME-Version: 1.0 References: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> In-Reply-To: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> From: Rahul Jadhav Date: Thu, 19 Jul 2018 22:44:52 -0400 Message-ID: To: "consultancy@vanderstok.org" , Routing Over Low power and Lossy networks Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Roll] github for roll X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 02:45:07 -0000 Thanks Peter, Jaime for setting this up. It should be much easier to edit/collaborate using github. FYI, I used instructions from https://github.com/martinthomson/i-d-template for setting up the build env. One thing that i found missing was the "roll-wg.github.io" repo which results in certain links not working if you use above template. But i guess we can do without it. On Thu, 19 Jul 2018 at 11:40, Peter van der Stok wrote: > > Hi Roll, > > with the help of Jaime a github for roll has been set up; > I have invited some authors as members; > I made a random selection that covers the roll drafts. > > Can other interested authors contact me to be added as member (author of draft) > And can interested authors enter the draft repositories in the roll WG github. > > Is anyone opposed to this initiative?? > > Please let the WG know your opinion. > > Many thanks, > > Peter > -- > Peter van der Stok > vanderstok consultancy > mailto: consultancy@vanderstok.org > www: www.vanderstok.org > tel NL: +31(0)492474673 F: +33(0)966015248 > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll From nobody Thu Jul 19 19:47:13 2018 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 8655E13102D for ; Thu, 19 Jul 2018 19:47:12 -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, 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 VEmgNcjHpS3j for ; Thu, 19 Jul 2018 19:47:09 -0700 (PDT) Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 57A18130E12 for ; Thu, 19 Jul 2018 19:47:09 -0700 (PDT) Received: by mail-vk0-x22a.google.com with SMTP id b14-v6so5389623vke.13 for ; Thu, 19 Jul 2018 19:47:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BscTdE4QHDDjGYEDfXoM823dpwtDNpz/1ZLBHkuQpfE=; b=pUFfQ6xNh6TO86pBl+wGoTXwxGIKCTlDqd9n91CWi7KkB/950qLrSYvnPEI8771ZuI qZh0WuzV2vzr/14RfEcx8uKx52XlGrVf+ByWhnvroSxljTUsnLJVCoqEKcxBd+Oke4h1 5nyE+VgDbRCL2+ZPryfzTjZhkqO90gCcywoMYtdv0IZBelqGGCffAZFmWSZQ484IoFq+ Jq0uldo1oigVUrZ6ok2a7Yk9ly5DZdr/GVz1VmSHPSPDGn6fGkpiGLtJnULtXas7nlpa rVyHcSy8xKBY/O0KIhMgxe/i7Js7od978aU13tG8oHuYj+NzRzVxNLi6muNBXu+x0zEc Zkag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BscTdE4QHDDjGYEDfXoM823dpwtDNpz/1ZLBHkuQpfE=; b=AGkjILVT9+UuKhJgewdg6niFcT/spKNNgr2jDMZAy201CNsyNRGil68amkNdDVOMcr WLtIC/u47osdJW1BG3uFUo+PfsIHZu5xSs80KAyXfW3G1nHHX66OSctvszaz4fBNWLZd GFsEMLeGtoWT9KvUNRH+/M2Rp8L1V+Zqd07rpljKIj0uMBYQCSEps4fZZYiVkogJ6n3a hgr/XFdp/Xaz9eP8SpcQ8v6E48l6+XpC4T2u4jfdwbnrqBb3nagCSQq85TSRo60Ve12n O9X8Sl9oazHpyS6XCOaxhd2B1jCRnSaaFtxkayGcvh95dlj/L0txtJ6xjeEHZSWIVPg8 BGKA== X-Gm-Message-State: AOUpUlGrAvKSYz0ddsnodXvm1SrIqwWa3ER+8p7MdJhguDHRxYLkunaK SOC1zVEzrALNqG6ej/hP6ZQ8mlaImeQtEGb2B6LaoujH X-Google-Smtp-Source: AAOMgpeshr9jhENDUTqmu0Jb/4tjm+UPJMSXP2fmI9mFPodolzPUT/jcrOHl1CLAogwMykAriULWsJu7kklOEM4ckLc= X-Received: by 2002:a1f:7c4:: with SMTP id 187-v6mr115975vkh.60.1532054828356; Thu, 19 Jul 2018 19:47:08 -0700 (PDT) MIME-Version: 1.0 References: <3491D5D3-9753-4B6C-B45E-DF9E93B5EB01@imt-atlantique.fr> In-Reply-To: <3491D5D3-9753-4B6C-B45E-DF9E93B5EB01@imt-atlantique.fr> From: Rahul Jadhav Date: Thu, 19 Jul 2018 22:46:57 -0400 Message-ID: To: "Georgios Z. Papadopoulos" Cc: Routing Over Low power and Lossy networks Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 02:47:13 -0000 Thank you Georgios for the review. I just pushed -04 which incorporates your comments. On Tue, 17 Jul 2018 at 07:05, Georgios Z. Papadopoulos wrote: > > Hello Rahul, > > Many thanks for your quick response. > Please find my response inline: > > Cheers, > Georgios > > > On Jul 16, 2018, at 20:28, Rahul Jadhav wrote: > > > > Thank you Georgios for the review. > > Please find my response inline below. > > > > Best, > > Rahul > > > > On Mon, 16 Jul 2018 at 06:53, Georgios Z. Papadopoulos > > wrote: > >> > >> Dear Roll, Rahul and co-authors, > >> > >> I find this proposal useful, and quite ready to go. > >> Please find my (perhaps minor) comments below. > >> =E2=80=94 =E2=80=94 > >> > >> [1] 1.2. Current No-Path DAO messaging > >> "Subsequently parents or ancestors would release any resources (such a= s the routing entry) it maintains on behalf of target node.=E2=80=9D > >> > >> [GP] What could be other type of resources, apart from a routing entry= , that a parent or ancestors may release? > >> Could you provide some more examples? > > > > [RJ]: another something usually done in context to route removal is > > decreasing the ref-cnt for the corresponding next-hop nbr-table entry > > ... such that if the ref-cnt reaches 0/zero the neighbor table entry > > could as well be deleted. > > [GP] Many thanks for the example. > I believe it would be helpful to provide such another example in the draf= t. > > >> > >> > >> [2] 3.1. Req#1: Tolerant to link failures to the previous parents > >> =E2=80=9CTherefore, it is required that the NPDAO message MUST be tole= rant to the link failure during the switching.=E2=80=9D > >> > >> [GP] How it can be tolerant, when there is a link failure? What could = be the potential means to be tolerant? > > > > [RJ]: The text states that any new route-invalidation mechanism > > defined should be tolerant to link failures. The link referred here > > represents link between the node and its previous parent (from whom > > the node is now disassociating). The way the draft achieves this > > tolerance is by having the route invalidation get done through the new > > route that is newly established and not depend on the previous link > > which is failed. > > [GP] Many thanks for the clarification. > Do you think you could provide such explanation in the draft? > > >> > >> > >> [3] 4.1. Change in RPL route invalidation semantics > >> =E2=80=9CThe trigger for the common ancestor node to generate this DCO= is the change in the next hop for the target on reception of an update mes= sage in the form of regular DAO for the target.=E2=80=9D > >> > >> [GP] I am having some troubles to understand this sentence, is it poss= ible to be rephrased? > > > > [RJ]: "The common ancestor node generates this DCO in response to the > > change in the next-hop on receiving a regular DAO for the target." > > Do you think this rephrase works better ? > > [GP] Yes, definitely. Many thanks. > > >> > >> > >> [4] 4.3. Destination Cleanup Object (DCO) > >> =E2=80=9CThe DCO message always traverses downstream and cleans up rou= te information and other state information associated with the given target= .=E2=80=9D > >> > >> [GP] Similar to comment [1], is it possible to give some examples of s= tate information? > > > > [RJ]: mentioned as part of [1] response. > > [GP] Great, thanks. > > >> > >> =E2=80=94 =E2=80=94 > >> Best, > >> Georgios > >> > >> ____________________________________ > >> > >> Georgios Z. Papadopoulos, Ph.D. > >> Associate Professor, IMT Atlantique, Rennes > >> > >> web: www.georgiospapadopoulos.com > >> twitter: @gzpapadopoulos > >> ____________________________________ > >> > >> On Jul 4, 2018, at 11:40, Ines Robles = wrote: > >> > >> Dear all, > >> > >> A Working Group Last call (WGLC) starts today (04/07) until 20/07 for = draft-ietf-roll-efficient-npdao-03 > >> > >> The draft is available here: > >> https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ > >> > >> Please review this draft to see if you think that it is ready for publ= ication and send comments to the list stating your view. > >> > >> > >> Thank you very much in advance, > >> > >> Ines and Peter > >> _______________________________________________ > >> Roll mailing list > >> Roll@ietf.org > >> https://www.ietf.org/mailman/listinfo/roll > >> > >> > From nobody Thu Jul 19 20:22:04 2018 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 D31A5130FC8 for ; Thu, 19 Jul 2018 20:22:02 -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, 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 rSdyqaMLno9S for ; Thu, 19 Jul 2018 20:21:58 -0700 (PDT) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 39433130EB5 for ; Thu, 19 Jul 2018 20:21:56 -0700 (PDT) Received: by mail-vk0-x22d.google.com with SMTP id s23-v6so5422757vks.7 for ; Thu, 19 Jul 2018 20:21:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZmPWL+SBn8MAcIljkthuT2yNN1VnJRvAFitPhEHwulM=; b=M5uvYMnTnm9W24oRPBwspDTDet1/tbsGJ43reiJ7Q7Z0mJiD8BNlL6tL1ktB0/ErEd FfGJ6aq+8PdhJpM8KawCRbz+3GixaFqt9cMyb6ADlxA8gZvMsXWVnMvhEKBPVS3CJOgA uV+aVeXDIQJ762yLLjC8TXM0iGspY/EdhfqbgXZW4NDjJ6lyejR+72HyTYlv6rwiytmF 13JJIGQ6iNcgyBohuXHytAg5Og2Hd7K2JwG8ctYeYGFXBt93QX6PUCWTdqoeKVi/beKn h7uI+XW0fU9Y4gR2ciCaw33Tz/ubkIjtK3RKwMPnwQHzYIqECg2jQ8HUmRWfit2U12Op /hPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZmPWL+SBn8MAcIljkthuT2yNN1VnJRvAFitPhEHwulM=; b=JV9rpFOrWqwDDJeuZ47Pk+j6HT3WcvGnMa/z5G8nUid051j65R+qSNXjD33c95tvOQ 5QhxaMxH4A+F13Xwes+7OzX5lRyA+wiJscyAWMMqN6O1p50Rnck4fjULlvfnyWsGbGSR dca2QnCDHka4/fnAMtjrGKNvYMHRvaQiZB91Fb2oMhORsPB6/XHFmiNRgnEKsrfvNxCz AlBPDWwXXCazMb6MPdAVjMKW+hgEEKAB8+R/bOb96BctSXb91E6B7YeBPEPd/fSvKn9c 3SHQdmPXuidwJpgu2dlb0+nbB4ggc73Aw5ctMBw65Y6rxhe/MV9JnibPA2nJObsdKmB1 ML7A== X-Gm-Message-State: AOUpUlFijRjJcZF9Tqr8VyUioXUXA/juYOsagWdu3nBj/HqAAUEwwr7t eIlryXlNH3ETCpH3Cnk/7KemyrlPvnWVhcImJy76rT8/r54= X-Google-Smtp-Source: AAOMgpeNLqlvELWyGMzUnJ3+K877vHJ0J8ah4AC4mhjq4oJpJD7Q0lLM7gtxgEt6ajg3aPfmyVxFvKo0cySSfV/XKFo= X-Received: by 2002:a1f:a50:: with SMTP id 77-v6mr160020vkk.74.1532056915156; Thu, 19 Jul 2018 20:21:55 -0700 (PDT) MIME-Version: 1.0 References: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> In-Reply-To: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> From: Rahul Jadhav Date: Thu, 19 Jul 2018 23:21:43 -0400 Message-ID: To: "consultancy@vanderstok.org" , Routing Over Low power and Lossy networks Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Roll] acceptance of individual drafts X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 03:22:03 -0000 koutsiamanis-roll-nsa-estension, ji-roll-traffic-aware-objective function - have reviewed the document and possibly contribute in the future. thubert-roll-unaware-leaves, bier-rpl - haven't reviewed any version, but will review in the future. Regards, Rahul - have read a version. But i On Tue, 17 Jul 2018 at 14:25, Peter van der Stok wrote: > > Hi Roll, > > This morning we had several interesting presentations of individual drafts. > They all fit within the charter of ROLL, and represent worthy subjects. > > It would be pleasure to take them in as roll WG documents, provided there is enough interest in the WG to work on the subjects. > > Below there is a list of drafts for which I like an answer to the following questions: > Did you read a version of the document, > Do you intend to read a version of the document. > Will you react on the ML concerning the document. > Are you willing to do a review of the document? > Will you contribute to the document? > > Answering to only one question positively for a subset of the documents is probably sufficient to gauge interest. > > The list of drafts is: > Bier RPL design team document > rahul-roll-rpl-observation > koutsiamanis-roll-nsa-estension > ji-roll-traffic-aware-objective function > thubert-roll-unaware-leaves > > > For draft rahul-rpl-observation, the consideration that it should go to RFC is no relevant for these questions, because we can use the document extensively in the WG without publishing it in the end. > > Thanks for your reactions and contributions. > > Peter&Ines > -- > Peter van der Stok > vanderstok consultancy > mailto: consultancy@vanderstok.org > www: www.vanderstok.org > tel NL: +31(0)492474673 F: +33(0)966015248 > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll From nobody Thu Jul 19 20:52:56 2018 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 A74BB1277D2 for ; Thu, 19 Jul 2018 20:52:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 XoWcklFTXA1M for ; Thu, 19 Jul 2018 20:52:51 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 E1982130E7D for ; Thu, 19 Jul 2018 20:52:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w6K3qlEl024673; Fri, 20 Jul 2018 05:52:47 +0200 (CEST) Received: from dhcp-9193.meeting.ietf.org (dhcp-9193.meeting.ietf.org [31.133.145.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 41Wxmb1wXPzDWhH; Fri, 20 Jul 2018 05:52:47 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Carsten Bormann In-Reply-To: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> Date: Thu, 19 Jul 2018 23:52:45 -0400 X-Mao-Original-Outgoing-Id: 553751564.019356-8ac38cf780dbeea40d17127af83dc1ba Content-Transfer-Encoding: quoted-printable Message-Id: <70E2607B-2762-443B-9729-5392096399E3@tzi.org> References: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> To: peter van der Stok , Routing Over Low power and Lossy networks X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Roll] github for roll X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 03:52:55 -0000 Thank you and Jaime for going forward with this! On Jul 19, 2018, at 11:39, Peter van der Stok = wrote: >=20 > I made a random selection that covers the roll drafts. All draft authors need to be in the team for each draft. Gr=C3=BC=C3=9Fe, Carsten From nobody Fri Jul 20 01:15:17 2018 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 4D8C91310BB for ; Fri, 20 Jul 2018 01:15:14 -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, HTML_MESSAGE=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 (1024-bit key) header.d=imt-atlantique.fr 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 KhNBMSKCM1_V for ; Fri, 20 Jul 2018 01:15:05 -0700 (PDT) Received: from zproxy110.enst.fr (zproxy110.enst.fr [137.194.2.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07897130F83 for ; Fri, 20 Jul 2018 01:15:04 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 33A9581318; Fri, 20 Jul 2018 10:15:03 +0200 (CEST) Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10032) with ESMTP id HEj0DkqntFGS; Fri, 20 Jul 2018 10:15:02 +0200 (CEST) Received: from localhost (localhost [IPv6:::1]) by zproxy110.enst.fr (Postfix) with ESMTP id 4F19D81FA8; Fri, 20 Jul 2018 10:15:02 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 zproxy110.enst.fr 4F19D81FA8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=imt-atlantique.fr; s=50EA75E8-DE22-11E6-A6DE-0662BA474D24; t=1532074502; bh=5RiQ/u1bY8Yr9Whn2+mr+nrd2G5Qc9ekspG+ftqtEpM=; h=Mime-Version:From:Date:Message-Id:To; b=RK0DUsx4Sg/ObI2LixjwCuseZaSA07NHeaswB2iVpyPy8Y1J041QBxM/OAxjQGdQm ZNq/q8sCxfAROLMZZ6k9LEAu72cbFW1/SNWNxDqqKb9Hr9PcpIBmEOsWGXBNZcwblG 5z8Mg7QEltDFEx3LCrdtD0MdlHczy8cMoPStAQl4= X-Virus-Scanned: amavisd-new at zproxy110.enst.fr Received: from zproxy110.enst.fr ([IPv6:::1]) by localhost (zproxy110.enst.fr [IPv6:::1]) (amavisd-new, port 10026) with ESMTP id B7SoLtMu7cuU; Fri, 20 Jul 2018 10:15:02 +0200 (CEST) Received: from [192.168.43.206] (unknown [37.168.226.42]) by zproxy110.enst.fr (Postfix) with ESMTPSA id 79FF181318; Fri, 20 Jul 2018 10:15:01 +0200 (CEST) Content-Type: multipart/alternative; boundary="Apple-Mail=_77296BE5-C3AD-46AE-80D1-7C7EEC494BFB" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) From: "Georgios Z. Papadopoulos" In-Reply-To: Date: Fri, 20 Jul 2018 11:14:59 +0300 Cc: Routing Over Low power and Lossy networks Message-Id: References: <3491D5D3-9753-4B6C-B45E-DF9E93B5EB01@imt-atlantique.fr> To: Rahul Jadhav X-Mailer: Apple Mail (2.3124) Archived-At: Subject: Re: [Roll] WGLC for draft-ietf-roll-efficient-npdao-03 X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 08:15:14 -0000 --Apple-Mail=_77296BE5-C3AD-46AE-80D1-7C7EEC494BFB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Many thanks Rahul for considering them.=20 Georgios ____________________________________ Georgios Z. Papadopoulos, Ph.D. Associate Professor, IMT Atlantique, Rennes web: www.georgiospapadopoulos.com = twitter: @gzpapadopoulos = ____________________________________ > On Jul 20, 2018, at 05:46, Rahul Jadhav wrote: >=20 > Thank you Georgios for the review. I just pushed -04 which > incorporates your comments. > On Tue, 17 Jul 2018 at 07:05, Georgios Z. Papadopoulos > wrote: >>=20 >> Hello Rahul, >>=20 >> Many thanks for your quick response. >> Please find my response inline: >>=20 >> Cheers, >> Georgios >>=20 >>> On Jul 16, 2018, at 20:28, Rahul Jadhav = wrote: >>>=20 >>> Thank you Georgios for the review. >>> Please find my response inline below. >>>=20 >>> Best, >>> Rahul >>>=20 >>> On Mon, 16 Jul 2018 at 06:53, Georgios Z. Papadopoulos >>> wrote: >>>>=20 >>>> Dear Roll, Rahul and co-authors, >>>>=20 >>>> I find this proposal useful, and quite ready to go. >>>> Please find my (perhaps minor) comments below. >>>> =E2=80=94 =E2=80=94 >>>>=20 >>>> [1] 1.2. Current No-Path DAO messaging >>>> "Subsequently parents or ancestors would release any resources = (such as the routing entry) it maintains on behalf of target node.=E2=80=9D= >>>>=20 >>>> [GP] What could be other type of resources, apart from a routing = entry, that a parent or ancestors may release? >>>> Could you provide some more examples? >>>=20 >>> [RJ]: another something usually done in context to route removal is >>> decreasing the ref-cnt for the corresponding next-hop nbr-table = entry >>> ... such that if the ref-cnt reaches 0/zero the neighbor table entry >>> could as well be deleted. >>=20 >> [GP] Many thanks for the example. >> I believe it would be helpful to provide such another example in the = draft. >>=20 >>>>=20 >>>>=20 >>>> [2] 3.1. Req#1: Tolerant to link failures to the previous parents >>>> =E2=80=9CTherefore, it is required that the NPDAO message MUST be = tolerant to the link failure during the switching.=E2=80=9D >>>>=20 >>>> [GP] How it can be tolerant, when there is a link failure? What = could be the potential means to be tolerant? >>>=20 >>> [RJ]: The text states that any new route-invalidation mechanism >>> defined should be tolerant to link failures. The link referred here >>> represents link between the node and its previous parent (from whom >>> the node is now disassociating). The way the draft achieves this >>> tolerance is by having the route invalidation get done through the = new >>> route that is newly established and not depend on the previous link >>> which is failed. >>=20 >> [GP] Many thanks for the clarification. >> Do you think you could provide such explanation in the draft? >>=20 >>>>=20 >>>>=20 >>>> [3] 4.1. Change in RPL route invalidation semantics >>>> =E2=80=9CThe trigger for the common ancestor node to generate this = DCO is the change in the next hop for the target on reception of an = update message in the form of regular DAO for the target.=E2=80=9D >>>>=20 >>>> [GP] I am having some troubles to understand this sentence, is it = possible to be rephrased? >>>=20 >>> [RJ]: "The common ancestor node generates this DCO in response to = the >>> change in the next-hop on receiving a regular DAO for the target." >>> Do you think this rephrase works better ? >>=20 >> [GP] Yes, definitely. Many thanks. >>=20 >>>>=20 >>>>=20 >>>> [4] 4.3. Destination Cleanup Object (DCO) >>>> =E2=80=9CThe DCO message always traverses downstream and cleans up = route information and other state information associated with the given = target.=E2=80=9D >>>>=20 >>>> [GP] Similar to comment [1], is it possible to give some examples = of state information? >>>=20 >>> [RJ]: mentioned as part of [1] response. >>=20 >> [GP] Great, thanks. >>=20 >>>>=20 >>>> =E2=80=94 =E2=80=94 >>>> Best, >>>> Georgios >>>>=20 >>>> ____________________________________ >>>>=20 >>>> Georgios Z. Papadopoulos, Ph.D. >>>> Associate Professor, IMT Atlantique, Rennes >>>>=20 >>>> web: www.georgiospapadopoulos.com >>>> twitter: @gzpapadopoulos >>>> ____________________________________ >>>>=20 >>>> On Jul 4, 2018, at 11:40, Ines Robles = wrote: >>>>=20 >>>> Dear all, >>>>=20 >>>> A Working Group Last call (WGLC) starts today (04/07) until 20/07 = for draft-ietf-roll-efficient-npdao-03 >>>>=20 >>>> The draft is available here: >>>> https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npdao/ >>>>=20 >>>> Please review this draft to see if you think that it is ready for = publication and send comments to the list stating your view. >>>>=20 >>>>=20 >>>> Thank you very much in advance, >>>>=20 >>>> Ines and Peter >>>> _______________________________________________ >>>> Roll mailing list >>>> Roll@ietf.org >>>> https://www.ietf.org/mailman/listinfo/roll >>>>=20 >>>>=20 >>=20 --Apple-Mail=_77296BE5-C3AD-46AE-80D1-7C7EEC494BFB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Many thanks Rahul for considering them. 
Georgios

____________________________________

Georgios Z. = Papadopoulos, Ph.D.
Associate Professor, IMT = Atlantique, Rennes

web:   www.georgiospapadopoulos.com
twitter:  @gzpapadopoulos
____________________________________

On Jul 20, 2018, at 05:46, Rahul Jadhav <rahul.ietf@gmail.com> wrote:

Thank = you Georgios for the review. I just pushed -04 which
incorporates your comments.
On Tue, 17 Jul 2018 = at 07:05, Georgios Z. Papadopoulos
<georgios.papadopoulos@imt-atlantique.fr> wrote:

Hello = Rahul,

Many thanks for your quick = response.
Please find my response inline:

Cheers,
Georgios

On Jul 16, 2018, at = 20:28, Rahul Jadhav <rahul.ietf@gmail.com> wrote:

Thank you Georgios for the review.
Please find = my response inline below.

Best,
Rahul

On Mon, 16 Jul 2018 at = 06:53, Georgios Z. Papadopoulos
<georgios.papadopoulos@imt-atlantique.fr> wrote:

Dear = Roll, Rahul and co-authors,

I find this = proposal useful, and quite ready to go.
Please find my = (perhaps minor) comments below.
=E2=80=94 =E2=80=94

[1] 1.2. Current No-Path DAO messaging
"Subsequently parents or ancestors would release any = resources (such as the routing entry) it maintains on behalf of target = node.=E2=80=9D

[GP] What could be other = type of resources, apart from a routing entry, that a parent or = ancestors may release?
Could you provide some more = examples?

[RJ]: another = something usually done in context to route removal is
decreasing the ref-cnt for the corresponding next-hop = nbr-table entry
... such that if the ref-cnt reaches = 0/zero the neighbor table entry
could as well be = deleted.

[GP] Many thanks for = the example.
I believe it would be helpful to provide such = another example in the draft.



[2] 3.1. Req#1: Tolerant to link failures to = the previous parents
=E2=80=9CTherefore, it is required = that the NPDAO message MUST be tolerant to the link failure during the = switching.=E2=80=9D

[GP] How it can be = tolerant, when there is a link failure? What could be the potential = means to be tolerant?

[RJ]: = The text states that any new route-invalidation mechanism
defined should be tolerant to link failures. The link = referred here
represents link between the node and its = previous parent (from whom
the node is now = disassociating). The way the draft achieves this
tolerance = is by having the route invalidation get done through the new
route that is newly established and not depend on the = previous link
which is failed.

[GP] Many thanks for the = clarification.
Do you think you could provide such = explanation in the draft?



[3] 4.1. Change in RPL route invalidation = semantics
=E2=80=9CThe trigger for the common ancestor = node to generate this DCO is the change in the next hop for the target = on reception of an update message in the form of regular DAO for the = target.=E2=80=9D

[GP] I am having some = troubles to understand this sentence, is it possible to be rephrased?

[RJ]: "The common ancestor node = generates this DCO in response to the
change in the = next-hop on receiving a regular DAO for the target."
Do = you think this rephrase works better ?

[GP] Yes, definitely. Many thanks.



[4] 4.3. Destination Cleanup = Object (DCO)
=E2=80=9CThe DCO message always traverses = downstream and cleans up route information and other state information = associated with the given target.=E2=80=9D

[GP] Similar to comment [1], is it possible to give some = examples of state information?

[RJ]: mentioned as part of [1] response.

[GP] Great, thanks.


=E2=80=94 =E2=80=94
Best,
Georgios

____________________________________

Georgios Z. Papadopoulos, Ph.D.
Associate = Professor, IMT Atlantique, Rennes

web: =   www.georgiospapadopoulos.com
twitter: =  @gzpapadopoulos
____________________________________

On Jul 4, 2018, at 11:40, Ines Robles <mariainesrobles@googlemail.com> wrote:
Dear all,

A Working Group Last = call (WGLC) starts today (04/07) until 20/07 for = draft-ietf-roll-efficient-npdao-03

The = draft is available here:
https://datatracker.ietf.org/doc/draft-ietf-roll-efficient-npda= o/

Please review this draft to see if = you think that it is ready for publication and send comments to the list = stating your view.


Thank you = very much in advance,

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




= --Apple-Mail=_77296BE5-C3AD-46AE-80D1-7C7EEC494BFB-- From nobody Fri Jul 20 04:48:08 2018 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 B3DEB1311A3 for ; Fri, 20 Jul 2018 04:48:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 EVAaJPm4Nl19 for ; Fri, 20 Jul 2018 04:47:58 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0184.hostedemail.com [216.40.44.184]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B125D13118C for ; Fri, 20 Jul 2018 04:47:56 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay03.hostedemail.com (Postfix) with ESMTP id 7166B837F24C; Fri, 20 Jul 2018 11:47:55 +0000 (UTC) X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C X-Spam-Summary: 2, 0, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::::, RULES_HIT:41:72:152:355:379:582:599:800:960:962:967:983:988:989:1152:1189:1208:1221:1260:1313:1314:1345:1359:1431:1436:1437:1516:1517:1518:1534:1541:1568:1575:1588:1589:1592:1594:1711:1714:1730:1776:1792:2198:2199:2528:2553:2559:2562:2827:3138:3139:3140:3141:3142:3622:3865:3867:3868:3870:3873:3874:4321:4362:5007:6117:6261:6298:6657:6659:6678:7464:7875:7903:8603:9040:9177:10004:10214:10400:10848:11232:11658:11783:11914:12043:12740:12895:13071:13139:14096:14180:14181:14721:21060:21080:21433:21451:21625:30054:30090, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:not bulk, SPF:fn, MSBL:0, DNSBL:neutral, Custom_rules:0:0:0, LFtime:24, LUA_SUMMARY:none X-HE-Tag: scarf08_280697e13b829 X-Filterd-Recvd-Size: 3130 Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf10.hostedemail.com (Postfix) with ESMTPA; Fri, 20 Jul 2018 11:47:55 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_07cef1c56279cb37e7f1cb5450cfd232" Date: Fri, 20 Jul 2018 08:47:54 -0300 From: Peter van der Stok To: Carsten Bormann Cc: peter van der Stok , Routing Over Low power and Lossy networks Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org In-Reply-To: <70E2607B-2762-443B-9729-5392096399E3@tzi.org> References: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> <70E2607B-2762-443B-9729-5392096399E3@tzi.org> Message-ID: <23bfc943f3111b7fa92ccd69f7b9f5f8@bbhmail.nl> X-Sender: stokcons@bbhmail.nl User-Agent: Roundcube Webmail/1.2.7 X-Originating-IP: [31.133.147.176] Archived-At: Subject: Re: [Roll] github for roll X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 11:48:05 -0000 --=_07cef1c56279cb37e7f1cb5450cfd232 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Hi all, I think, I sent an invitation to all authors now. Some may have received several invitations. That happened due to a no brainer process. thanks for your collaboration, Greetings, Peter Carsten Bormann schreef op 2018-07-20 00:52: > Thank you and Jaime for going forward with this! > > On Jul 19, 2018, at 11:39, Peter van der Stok wrote: > >> I made a random selection that covers the roll drafts. > > All draft authors need to be in the team for each draft. > > Grüße, Carsten --=_07cef1c56279cb37e7f1cb5450cfd232 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi all,

I think, I sent an invitation to all authors now.
S= ome may have received several invitations. That happened due to a no braine= r process.

thanks for your collaboration,

Greetings,<= br />
Peter

Carsten Bormann schreef op 2018-07-20 00:52:

= Thank you and Jaime for going forward with this!

On Jul 19, 201= 8, at 11:39, Peter van der Stok <stokcons@bbhmail.nl> wrote:

I made a random selection that covers the roll = drafts.

All draft authors need to be in the team for each draft.

= Grüße, Carsten

--=_07cef1c56279cb37e7f1cb5450cfd232-- From nobody Fri Jul 20 07:13:31 2018 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 577D3130E68 for ; Fri, 20 Jul 2018 07:13:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 QYnYivTqjc35 for ; Fri, 20 Jul 2018 07:13:28 -0700 (PDT) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::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 DCF9D1311B6 for ; Fri, 20 Jul 2018 07:13:25 -0700 (PDT) Received: by mail-it0-x22c.google.com with SMTP id s7-v6so14839542itb.4 for ; Fri, 20 Jul 2018 07:13:25 -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 :cc; bh=wQJvHuUY69m0ZJUmy+Zk9pzIApSgUdbIJpWqrrOczGI=; b=r4e50SuAOom/qThKaRAbrcR38kjdO/D3R/wcmqOpsHpM+fPjE2qTY2Qc0KbpKRvMEj u6rIlRGgcoMASmMkUlIxHZLidn/4F2GgMDdNtwwMpoo2WShLq9/Q+VX1iOcFUArtcUis HHBVNICxVzrJ7gSKgMV+UMDhflpzVKAQGjAveIsFcn11Um8flLjwzZb9p1T4sZRlAzdB b1X0s8v6fONoS30/WgEIuAEJO7FTLwI4ONdqhsDrHGvj8iZkimXyBBB0qB3tL++sPsAR 13lDrjU2qAAvn6uO2kKvDhQ1grjkIvg8YPYvIgfK+Cc3ApB5WfnAvJPxPnWTDap+S6Ty kcWw== 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:cc; bh=wQJvHuUY69m0ZJUmy+Zk9pzIApSgUdbIJpWqrrOczGI=; b=H8jyanKEMq3FwpLXUNbeeHxnIKXLDJScItnGRrrF5GBoXQUyYK2MCA7YIHbfvyAF6W 1RxVFCKHNmfK5ie5i2jP02Pi63SISybBxRVcFcNYhKlyKfhoxKFp86PDdonNrWrIZCu+ nQuqohXSpyC5cxte3J7jMSyf82vFacWzOdAvX5NsjLP2emdnysXA9A5FRrt9EqS4+cfN YUKeBvLGfizF9dKz+H6dzK7MeG3auyX4bEoFZIGRk+qvlgfUoE8CazIflP9miOEmEHHl oF/OKQHxFtI2l7HKcMiBm6F0AZaAcFAW6TwrV1nF4OgH/pSGTMqQ3L8zCjUkoky/OjLH TxPw== X-Gm-Message-State: AOUpUlG4HEQon2jQwy3rAb3vRN/yjF1aA1bGueXzCaDqtNpT1t+GlwhO pWzF5N2tFXzbRXg9UL0RVNj6qmw4AzTyOmRc+vsE6acq X-Google-Smtp-Source: AAOMgpeO0IVNMmNeILje5srJ5qVUfLpnfsEBzSDfxLlVSbD4HbgGFGfY+SMAs2bs5YRx+jMVnXspjbDEl2r5RbCEQCI= X-Received: by 2002:a24:1fc7:: with SMTP id d190-v6mr1913204itd.52.1532096004778; Fri, 20 Jul 2018 07:13:24 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:1705:0:0:0:0:0 with HTTP; Fri, 20 Jul 2018 07:13:24 -0700 (PDT) In-Reply-To: References: <12f6a8ddd767c68da730f2ce2f377cb3@bbhmail.nl> From: Ines Robles Date: Fri, 20 Jul 2018 17:13:24 +0300 Message-ID: To: Routing Over Low power and Lossy networks Content-Type: multipart/alternative; boundary="000000000000206f5405716ee63a" Archived-At: Subject: Re: [Roll] github for roll X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 14:13:30 -0000 --000000000000206f5405716ee63a Content-Type: text/plain; charset="UTF-8" Thanks Rahul for pointing that issue, we created the repo and added the links with the instructions in the wiki. we followed the instructions for useofrplinfo and it worked, now waiting for the email that we should get after submission using the "Automated Process " Cheers, Ines 2018-07-20 5:44 GMT+03:00 Rahul Jadhav : > Thanks Peter, Jaime for setting this up. > It should be much easier to edit/collaborate using github. > FYI, I used instructions from > https://github.com/martinthomson/i-d-template for setting up the build > env. > One thing that i found missing was the "roll-wg.github.io" repo which > results in certain links not working if you use above template. But i > guess we can do without it. > > On Thu, 19 Jul 2018 at 11:40, Peter van der Stok > wrote: > > > > Hi Roll, > > > > with the help of Jaime a github for roll has been set up; > > I have invited some authors as members; > > I made a random selection that covers the roll drafts. > > > > Can other interested authors contact me to be added as member (author of > draft) > > And can interested authors enter the draft repositories in the roll WG > github. > > > > Is anyone opposed to this initiative?? > > > > Please let the WG know your opinion. > > > > Many thanks, > > > > Peter > > -- > > Peter van der Stok > > vanderstok consultancy > > mailto: consultancy@vanderstok.org > > www: www.vanderstok.org > > tel NL: +31(0)492474673 F: +33(0)966015248 > > _______________________________________________ > > 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 > --000000000000206f5405716ee63a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Rahul for pointing that issue,=C2=A0

=
we created the repo and added the links with the instructions in the w= iki.=C2=A0

we followed the instructions for useofr= plinfo and it worked, now waiting for the email that we should get after su= bmission using the "Automated Process "

= Cheers,

Ines

2018-07-20 5:44 GMT+03:00 Rahul Jadhav <rahul.ietf@gmail.com>:
Tha= nks Peter, Jaime for setting this up.
It should be much easier to edit/collaborate using github.
FYI, I used instructions from
https://github.com/martinthomson/i-d-template = for setting up the build
env.
One thing that i found missing was the "roll-wg.github.io" rep= o which
results in certain links not working if you use above template. But i
guess we can do without it.

On Thu, 19 Jul 2018 at 11:40, Peter van der Stok <stokcons@bbhmail.nl> wrote:
>
> Hi Roll,
>
> with the help of Jaime a github for roll has been set up;
> I have invited some authors as members;
> I made a random selection that covers the roll drafts.
>
> Can other interested authors contact me to be added as member (author = of draft)
> And can interested authors enter the draft repositories in the roll WG= github.
>
> Is anyone opposed to this initiative??
>
> Please let the WG know your opinion.
>
> Many thanks,
>
> Peter
> --
> Peter van der Stok
> vanderstok consultancy
> mailto: consultancy@vand= erstok.org
> www: www.vanderstok.org
> tel NL: +31(0)492474673=C2=A0 =C2=A0 =C2=A0F: +33(0)966015248
> _______________________________________________
> 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

--000000000000206f5405716ee63a-- From nobody Fri Jul 20 11:39:06 2018 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 B2452130DF1 for ; Fri, 20 Jul 2018 11:39:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 jiFV0Qmzhrm4 for ; Fri, 20 Jul 2018 11:38:59 -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 2192C129385 for ; Fri, 20 Jul 2018 11:38:59 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 123512008D; Fri, 20 Jul 2018 14:54:55 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id ED472263F; Fri, 20 Jul 2018 14:34:23 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id EB04E24E5; Fri, 20 Jul 2018 14:34:23 -0400 (EDT) From: Michael Richardson To: consultancy@vanderstok.org cc: Roll In-Reply-To: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> References: <22116446e1239aadd9ccc0c7b6d546ca@bbhmail.nl> X-Mailer: MH-E 8.6; nmh 1.7+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] acceptance of individual drafts X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 18:39:04 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Peter van der Stok wrote: > For draft rahul-rpl-observation, the consideration that it should go > to RFC is no relevant for these questions, because we can use the > document extensively in the WG without publishing it in the end. Agreed, but you still want to adopt it, so that it gets priority over non-WG documents for time, right? =2D-=20 ] Never tell me the odds! | ipv6 mesh network= s [=20 ] Michael Richardson, Sandelman Software Works | network architect= [=20 ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [=20 =09 --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBW1IrLYCLcPvd0N1lAQL3xgf/XnOJ/eeIWC1tkdqOmsV7l8oyxCRJ8WuM Hn/BVzbvCvmwwJchwaE+xDmsz4t5HZNVyHa31mArJGDmjfEp77de2DBGv7g+1oZl PvHOKCzFSdItCYEHhbkASGtEi1Z6k72nxpAFZ6sGkNHlv8wsNHikMbh5Mzmm06Pl Rtud2aFnVM1YP+xoQmdrjRNZVnF255mEftKthpi45vnonhsfN6JYFDl+TtbF5V4h DWRT9Gj+hWKZZAvs0zgbfsns8cXmPRkshdQd6gbwsqp/MLrr7A1vVZp2a1Jsfv53 I3esMFjbRzfPwfNYjX9b9GFk8AJqg5yvXab7quPAeOdk3JVb1ol9cQ== =3Trs -----END PGP SIGNATURE----- --=-=-=-- From nobody Mon Jul 23 05:29:23 2018 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 7A881130E74 for ; Mon, 23 Jul 2018 05:29:21 -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 P0qf4kC1huQI for ; Mon, 23 Jul 2018 05:29:19 -0700 (PDT) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 DFC36130DE1 for ; Mon, 23 Jul 2018 05:29:18 -0700 (PDT) Received: by mail-oi0-x22f.google.com with SMTP id 13-v6so775610ois.1 for ; Mon, 23 Jul 2018 05:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=WGOfw/5KbgMhuqw4P5Wucg7LcFcPa0Ev5XRLhu89E3E=; b=qcm7KIKSqw4B7uV5OmHJnhKLa9JWkd/+rUBgagx1vQ5HTBUlSkRwnOpeixqka/678l 7IRAoK9AyBcQ10lP4qw6evwRl+5SfRJsUZq/uTzWkdh3PXH+d+rFBQvOLrpW7yfVSft6 2s5Fq3hpVCd8iNWSzgkl08ds3R0unxgG3YTHPH3J1pPsTvMjdBJwkWETXENN0pCqHNrT 3GHbVnXBRF6M7T6pY4e763hMpCbD903Kb6kkYfxddyetc7MDFXjXG2JZYAutrt8ExC6z 4qi/BikySKM91w1M3i+YV0FoEswO0z7maydf1Mxl1G12jhnFRxxMi/yt6M+tL2KSsL6m QfZQ== 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=WGOfw/5KbgMhuqw4P5Wucg7LcFcPa0Ev5XRLhu89E3E=; b=LF3/NSLx+LhAmRtUDZqweH6z948HcF1LBPuMz/V0QONqq2kSVXY4ZPvnZSwEEmOYXJ fRWxsBj0YZaFyvk2sIckSOsWEavi/nEwt53x5a8QocAKjhN5G2T1b5ulwWiR7+yGCvlK 4uodyOTcbgPg6z/S/Xt4A1jSvIq+ycoqju1dyr7FW4ECwl7bc6SaDmyYBU7Bs7t3yabF uq+LzID1myGCkEQ9q4J9b0STzLka8cKKmOAzDgyf3Dohw41wqVKtD4QcnFahT7qaz0rg K5vdgvNI/vfvAnA9xxfYgME5t/P+r9WV+amOs2oyIg78hjp0pG2YBVq5zBeavlMtSjL/ hnkw== X-Gm-Message-State: AOUpUlEQG688TDwVi4VLWRZ+VRLmM3eoC1pbw4au7Bvai6Nh9ucWocgs +E17YPQPhOf0ZuVYv1ZS01tar9FQ/Fd/j0F+T1m5p9oB X-Google-Smtp-Source: AAOMgpcNkVxUgIwLyMtNdjDW8dzpxAw3XgV1Rv3AeIoRjNpCoY59nWnf2OMYIpkoCpaHAAK1PFsiKQWtiePCFwLTh1c= X-Received: by 2002:aca:dc08:: with SMTP id t8-v6mr8878392oig.226.1532348958148; Mon, 23 Jul 2018 05:29:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:d32:0:0:0:0:0 with HTTP; Mon, 23 Jul 2018 05:29:17 -0700 (PDT) In-Reply-To: <17294.1531966560@localhost> References: <17294.1531966560@localhost> From: Abdussalam Baryun Date: Mon, 23 Jul 2018 14:29:17 +0200 Message-ID: To: Routing Over Low power and Lossy networks , Michael Richardson , rahul.ietf@gmail.com Content-Type: multipart/alternative; boundary="000000000000528c620571a9cb20" Archived-At: Subject: Re: [Roll] rpl routing and linux-kernel X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 23 Jul 2018 12:29:22 -0000 --000000000000528c620571a9cb20 Content-Type: text/plain; charset="UTF-8" On Thu, Jul 19, 2018 at 4:16 AM, Michael Richardson wrote: > > Hi, I'm not sure that the ROLL list is a good place for Linux-specific > implementation questions. In particular, it seems that most implementers > are > on monolithic embedded kernels (contiki, openwsn, etc.) > Why? I don't care about most implementers, I care about our RFCs implemented and discussed in IETF lists, not outside, if we follow implementers some day we will leave the ROLL list as they did !!!! IMHO ROLL list is a good place for implementing RFCs into Linux, I don't agree that the questions are Linux specific, but implement specific. > There are discussions on unstrung-workers@lists.sandelman.ca about Linux > kernel integration (none recently through). > > Discussions also occur on linux-wpan@vger.kernel.org. > It would be a good place to start a new thread. > but also IMHO we need to have some summary with discuss in this list about implementations of WG RFCs. > > Rahul Jadhav wrote: > > Hello ROLL, > > > While trying to integrate RPL with linux kernel and we had certain > > design choices. In that context I have some specific questions, > > especially towards linux-kernel integration and not towards RPL > > protocol implementation itself. Assuming RPL implementation will be > in > > userspace, questions are: > > > 1. We can add/del routes using rtnetlink interfaces ... this can be > > used for the routes learnt by RPL as well ... But RPL needs to > > maintain some additional per-route information on the 6LBR ... To be > > very specific, we need to store parent information in context to > every > > route. Is it possible to do it with rtnetlink? I didn't find an > option > > to do that. If it ain't possible then what could be an alt approach? > > > 2. RPL requires that certain extended ipv6 options be added in data > > flows .. What is the best way to do this? It is possible to do this > > with netfilter+libnfq but i m not sure whether this is the best > > approach. > > > If there is anyone who tried this before, it would be great to have a > > discussion in person while we are in IETF102. Please let know if you > > are available for discussion. > > > Thanks, > > Rahul > > > _______________________________________________ > > Roll mailing list > > Roll@ietf.org > > https://www.ietf.org/mailman/listinfo/roll > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > > > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll > > --000000000000528c620571a9cb20 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Jul 19, 2018 at 4:16 AM, Michael Richardson &= lt;mcr+ietf@sand= elman.ca> wrote:

Hi, I'm not sure that the ROLL list is a good place for Linux-specific<= br> implementation questions.=C2=A0 In particular, it seems that most implement= ers are
on monolithic embedded kernels (contiki, openwsn, etc.)

Why?=C2=A0I don't care about most implementers, I care= about our RFCs implemented and discussed in IETF lists, not outside, if we= =C2=A0follow implementers some day we will leave the ROLL list as they did = !!!!=C2=A0

IMHO =C2=A0ROLL list is a good place fo= r implementing RFCs into Linux, I don't agree that the questions are Li= nux specific, but implement specific.



There are discussions on unstrung-workers@lists.sandelman.ca about Linux
kernel integration (none recently through).

Discussions also occur on lin= ux-wpan@vger.kernel.org.
It would be a good place to start a new thread.

but also IMHO we need to have some summary with discuss=C2=A0in th= is list about implementations of WG RFCs.
=C2=A0

Rahul Jadhav <rahul.ietf@gmail.c= om> wrote:
=C2=A0 =C2=A0 > Hello ROLL,

=C2=A0 =C2=A0 > While trying to integrate RPL with linux kernel and we h= ad certain
=C2=A0 =C2=A0 > design choices. In that context I have some specific que= stions,
=C2=A0 =C2=A0 > especially towards linux-kernel integration and not towa= rds RPL
=C2=A0 =C2=A0 > protocol implementation itself. Assuming RPL implementat= ion will be in
=C2=A0 =C2=A0 > userspace, questions are:

=C2=A0 =C2=A0 > 1. We can add/del routes using rtnetlink interfaces ... = this can be
=C2=A0 =C2=A0 > used for the routes learnt by RPL as well ... But RPL ne= eds to
=C2=A0 =C2=A0 > maintain some additional per-route information on the 6L= BR ... To be
=C2=A0 =C2=A0 > very specific, we need to store parent information in co= ntext to every
=C2=A0 =C2=A0 > route. Is it possible to do it with rtnetlink? I didn= 9;t find an option
=C2=A0 =C2=A0 > to do that. If it ain't possible then what could be = an alt approach?

=C2=A0 =C2=A0 > 2. RPL requires that certain extended ipv6 options be ad= ded in data
=C2=A0 =C2=A0 > flows .. What is the best way to do this? It is possible= to do this
=C2=A0 =C2=A0 > with netfilter+libnfq but i m not sure whether this is t= he best
=C2=A0 =C2=A0 > approach.

=C2=A0 =C2=A0 > If there is anyone who tried this before, it would be gr= eat to have a
=C2=A0 =C2=A0 > discussion in person while we are in IETF102. Please let= know if you
=C2=A0 =C2=A0 > are available for discussion.

=C2=A0 =C2=A0 > Thanks,
=C2=A0 =C2=A0 > Rahul

=C2=A0 =C2=A0 > _______________________________________________
=C2=A0 =C2=A0 > Roll mailing list
=C2=A0 =C2=A0 > Roll@ietf.org
=C2=A0 =C2=A0 > https://www.ietf.org/mailman/listi= nfo/roll

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




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


--000000000000528c620571a9cb20-- From nobody Mon Jul 30 00:54:41 2018 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 D6AD6130E32 for ; Mon, 30 Jul 2018 00:54:38 -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=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 wJBI24xD2njd for ; Mon, 30 Jul 2018 00:54:37 -0700 (PDT) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 4D5BE130E6F for ; Mon, 30 Jul 2018 00:54:37 -0700 (PDT) Received: by mail-io0-x22b.google.com with SMTP id k16-v6so9079483iom.12 for ; Mon, 30 Jul 2018 00:54:37 -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=368ovykTMNd1kraWmS+SiZMHFAS1moIZ2MDqJkcFgiM=; b=EqEJLUPVPhY0XJPBXy9xPAsrMZ1vuQ2VXy2jb/xXoHnOt7URjjn0rbagLoBRCZ8qKv D6JlRgEpTgYbVwCXNQVn2GSuL2mH1U2JxK+SKgHPOteRtIIiqphGM9+s8EcAupyORhYf Gbqp1OdqTD9dW1SiVhZ0AHf4DXfaqdD6R0d9qkQZPEngsHisbYUAAQej3K91Wwt3SaZO Fg4ts3iJPtxdbpV/t5CwoyMTXEftZHSpzMQcCzCtslNOD9/kP7OXUnnPRWL+mjWlbuz/ X8MVbFUiF17kbDZ+xzXf60O9MOo88xQ3SIxTZf5njMrrJzOxll/uGCW13O/MQy8wQ4WH QCsQ== 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=368ovykTMNd1kraWmS+SiZMHFAS1moIZ2MDqJkcFgiM=; b=POsbHQ0gxfvqtgzNsN3449zGYPbcmv40nZcRb1LwpwujBRnKyYPaVevL+ab6LLdrV3 pbh9UWQFyyMaPnR3ySBzBkHwq1wx0mKvTUd7cCRiaFHoNcCU5sopEqgp6EwO8HadkJcj Rubj9+6uf9BEkDtEoUtrjB5zNRCkqTHimb8P8RDRLAzdt+ae+hZZdABJ834qy6NrubFr M572TJG4CvKL96cuKJs5m1A+RV6FmRm/UgJbtJgpJcIWmspbhYOjGLIeG+vBJoYhS+UH KN+ls2wuKMZNlWko7GVXWwYGcD2bDzhweYVO97j8LIuJ0ie6jbuFwv057hLQLFqVdjKT I8Fw== X-Gm-Message-State: AOUpUlEDoIJLHxDOrCfLCHY5IeO804TNTETumw/PFedX7BsW5BGTvIrn ldh5W8TeLOqC9NGNCbGsSx7JUsOq5y43N5OyOrr95wtB X-Google-Smtp-Source: AAOMgpfDkpKBJBW5OuONBce/7hcp1lO5jNDC7PLWDkxH3MZ8b8bY0vMDAZimf1oy+uasEW7BnD0d9jV3M6bfrlSqpKs= X-Received: by 2002:a6b:3b47:: with SMTP id i68-v6mr12796995ioa.133.1532937276319; Mon, 30 Jul 2018 00:54:36 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:1705:0:0:0:0:0 with HTTP; Mon, 30 Jul 2018 00:54:35 -0700 (PDT) From: Ines Robles Date: Mon, 30 Jul 2018 10:54:35 +0300 Message-ID: To: roll Content-Type: multipart/alternative; boundary="000000000000d171ae057232c53a" Archived-At: Subject: [Roll] Last calls extension - review request X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 30 Jul 2018 07:54:39 -0000 --000000000000d171ae057232c53a Content-Type: text/plain; charset="UTF-8" Dear all, We extend these calls until 10-08-2018: - WGLC for draft-ietf-roll-efficient-npdao-03 - WGLC for draft-ietf-roll-aodv-rpl-04 - Call for adoption for draft-rahul-roll-rpl-observations During the IETF 102 we got some reviewers for these documents. Please, It would be nice if you could do the review before 10-08. Thank you, Ines and Peter. --000000000000d171ae057232c53a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,=C2=A0

We extend th= ese calls until 10-08-2018:=C2=A0

- WGLC for draft= -ietf-roll-efficient-npdao-03
- WGLC for draft-ietf-roll-aodv-rpl= -04
- Call for adoption for draft-rahul-roll-rpl-observations

During the IETF 102 we got some reviewers for these d= ocuments. Please, It would be nice if you could do the review before 10-08.=

Thank you,

Ines and Pete= r.
--000000000000d171ae057232c53a-- From nobody Mon Jul 30 12:59:07 2018 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 BE7B012F1AB for ; Mon, 30 Jul 2018 12:59:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 Eahy2ZV5wk9a for ; Mon, 30 Jul 2018 12:59:03 -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 BE10F124D68 for ; Mon, 30 Jul 2018 12:59:03 -0700 (PDT) Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 08D492008C for ; Mon, 30 Jul 2018 16:15:33 -0400 (EDT) Received: by sandelman.ca (Postfix, from userid 179) id A27F81826; Mon, 30 Jul 2018 15:59:02 -0400 (EDT) Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9EE511821 for ; Mon, 30 Jul 2018 15:59:02 -0400 (EDT) From: Michael Richardson To: roll@ietf.org X-Attribution: mcr X-Mailer: MH-E 8.6; nmh 1.7+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] WRT adopting draft-rahul-roll-rpl-observations as WG document X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 30 Jul 2018 19:59:06 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable {been watching the youtube video of the ROLL session} 1) I think that the work in roll-rpl-observations is really important. -> that's why we should adopt the document so that it can have priority over other non-WG documents in the agenda. As our AD pointed out, we don't have to publish it. 2) Starting rfc6550bis or rfc6550updates is very important!!! We have some options on how to do this, one of which is to publish a bun= ch of very small updates. That's probably the lowest latency way, but it does cause more IESG and RFC-EDITOR work. So I think that we will be forced to publish a ~60-page update document that collects all sorts of things. 3) I'd like to move to obsolete (mark as "historical") storing mode in favo= ur of dao-projection mode. I think that this is mostly orthogonal to the u= pdates work, but if we agree that we are going in that direction, there might be updates that we don't need to do. 4) We need a new node capabilities mechanism. It could be quite controversial as there are a lot of design choices here. maybe we shoul= d=20 probably encourage implementations, and then experimental RFCs. =2D-=20 Michael Richardson , Sandelman Software Works -=3D IPv6 IoT consulting =3D- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBW19uBoCLcPvd0N1lAQLQ0wgAwGK6gX1rO58G99ZCeBgx1d+Cp5qcWBdy FCqOnm1wuH/Bo5icOOpAOKBf/jQzDaAgdhIuzz+ra8RMdhRJ0sDnIZf9Z88tOSaL lHI0rjrcbUoEVBP/4BxU8nZDjZWB3vuwd5YFFf/uQu/+GDb6/i7gUQ4N7OL+9YLg UnI+kMiAj7IRri+VcyRgzh0pv1zqz1HtQ7SnTSEB6zxkzHcud0Jq3uTiLfChsrUb 7Xr79358bZXvZxfcJYoYcUPa7qL00+hWYpk1nEmDpeZAKWNFpxCz/a0QIwklUOvB UCHU1Y9A/Nl54ock+tQD+7nIit96vlltHcPTwKO6J7uclwFY6XUl5g== =xCMa -----END PGP SIGNATURE----- --=-=-=-- From nobody Mon Jul 30 16:58:22 2018 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 96A04130E61 for ; Mon, 30 Jul 2018 16:58:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, 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 0lVnpSMlNjAJ for ; Mon, 30 Jul 2018 16:58:18 -0700 (PDT) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 599BA130F66 for ; Mon, 30 Jul 2018 16:58:18 -0700 (PDT) Received: by mail-wr1-x435.google.com with SMTP id e7-v6so14649205wrs.9 for ; Mon, 30 Jul 2018 16:58:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=dd3VBcb0DrBBiDAmyWSCZLVfnFKQ+4R0JrXVMs/QLCg=; b=nXVn2ERIkx7nRIk34RoPncd4yL7kLOsNnZuBOQ6/0O45eL9OXJihfdW6InI8ueUPIn 4tWHogXh/6otEvExAgdv6dM5RKq8rv9s9YPFsopK6yYkV/tgR+4VKt06ftLHPdt9DKfz jBNGQFMkG4D/4uXvPoLl/Vn6AvmbUMZ+iM1SnmRM3jVGuzRRGFUFw/A8xOWWK2VQgWgy 5ula+yrcdwAsnLpnObeE9rsMEMHNN28JeqG0lDaVwfLJW/Prvy/5WmIHKOiWwXRQjxie ywz/1KAI/6yyyv+cRV5eQSz2WnOvG0niomLcpJ4uGqcKoLzJbx0Mqqrl0r7Y49g9DYCY J3ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=dd3VBcb0DrBBiDAmyWSCZLVfnFKQ+4R0JrXVMs/QLCg=; b=MwGvmkDPAZrH6IXOFDDqAdCauSBUVBmCwLZ2QJz4BFO15L6SwFD3wP/TpJmmdBNOr0 QedAYIKSgWwtXk0rwyODpWyOzEhrKmsC4olpN2d7/tdQUdxgC7JbZcPtPJHbh+p/kgBJ kCsspyrM/9VnnqH8GUPx7ebKMfhemasvkgwSgOaTxNf3nQa3hqyA+ugmJsKmnDgO9h1H z6iTi3cjmLcvZX6gxVCzaWAVtKBCxO9wxZoLig+b0uGaerZWlhsAlDTSY3x9LRF3qm0T Tx254oxJOs4D75cN+ksj3B+qV23GpoyfMl8Yi6T+qT8SRzNwXwaePD3oLnvmlgphMi6a 364w== X-Gm-Message-State: AOUpUlEu9jtZ0DfqF3knyG95iIlynqMBNxWV+IFxv205cB7LnhKG48qs 8dUkF3P9aCxlt0z9/lLZC6W8Glgf X-Google-Smtp-Source: AAOMgpctwzftG0P+tbMEV8um5xmTLHs2o5T93KZkPMMgxhxnOjIGwoi9530bLZhQjEwAL7uHnLyX1w== X-Received: by 2002:a5d:494c:: with SMTP id r12-v6mr19342477wrs.66.1532995096426; Mon, 30 Jul 2018 16:58:16 -0700 (PDT) Received: from ?IPv6:2001:8a0:6a52:4102:ca69:cdff:fe98:c1b4? ([2001:8a0:6a52:4102:ca69:cdff:fe98:c1b4]) by smtp.gmail.com with ESMTPSA id d7-v6sm15007574wro.92.2018.07.30.16.58.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 30 Jul 2018 16:58:15 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_A79B9D15-4E29-48A3-B05C-A5C4209A3814" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: =?utf-8?Q?Jo=C3=A3o_Pedro_Taveira?= X-Mailbutler-Link-Tracking-Uuid: In-Reply-To: Date: Tue, 31 Jul 2018 00:58:09 +0100 Cc: Michael Richardson , rahul.ietf@gmail.com Message-Id: References: <17294.1531966560@localhost> To: Routing Over Low power and Lossy networks X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Roll] rpl routing and linux-kernel X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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, 30 Jul 2018 23:58:22 -0000 --Apple-Mail=_A79B9D15-4E29-48A3-B05C-A5C4209A3814 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Rahul, I watch the youtube video of ROLL session (thanks to Michael last = mail to list) and I notice you ask about RPL implementations in linux = kernel. About my kernel implementation attempt history, roadmap and = status, please check = https://github.com/joaopedrotaveira/linux-rpl/issues/1 = . There=E2=80=99s = a link with my initial plan and my failures. If we could try to make it happen, it would great. Send me your = questions to my email or make presure on github repo. I just would like = to move this subject to any other channel. Abdussalam, I agree with Michael, there are discussions about this = subject were they should be. And IMHO, I never leaved, I=E2=80=99m still = here. Best Regards, Jo=C3=A3o Pedro Taveira > On 23 Jul 2018, at 13:29, Abdussalam Baryun = wrote: >=20 >=20 >=20 > On Thu, Jul 19, 2018 at 4:16 AM, Michael Richardson = > wrote: >=20 > Hi, I'm not sure that the ROLL list is a good place for Linux-specific > implementation questions. In particular, it seems that most = implementers are > on monolithic embedded kernels (contiki, openwsn, etc.) >=20 > Why? I don't care about most implementers, I care about our RFCs = implemented and discussed in IETF lists, not outside, if we follow = implementers some day we will leave the ROLL list as they did !!!!=20 >=20 > IMHO ROLL list is a good place for implementing RFCs into Linux, I = don't agree that the questions are Linux specific, but implement = specific. >=20 >=20 >=20 > There are discussions on unstrung-workers@lists.sandelman.ca = about Linux > kernel integration (none recently through). >=20 > Discussions also occur on linux-wpan@vger.kernel.org = . > It would be a good place to start a new thread. >=20 > but also IMHO we need to have some summary with discuss in this list = about implementations of WG RFCs. > =20 >=20 > Rahul Jadhav > = wrote: > > Hello ROLL, >=20 > > While trying to integrate RPL with linux kernel and we had = certain > > design choices. In that context I have some specific questions, > > especially towards linux-kernel integration and not towards RPL > > protocol implementation itself. Assuming RPL implementation will = be in > > userspace, questions are: >=20 > > 1. We can add/del routes using rtnetlink interfaces ... this can = be > > used for the routes learnt by RPL as well ... But RPL needs to > > maintain some additional per-route information on the 6LBR ... = To be > > very specific, we need to store parent information in context to = every > > route. Is it possible to do it with rtnetlink? I didn't find an = option > > to do that. If it ain't possible then what could be an alt = approach? >=20 > > 2. RPL requires that certain extended ipv6 options be added in = data > > flows .. What is the best way to do this? It is possible to do = this > > with netfilter+libnfq but i m not sure whether this is the best > > approach. >=20 > > If there is anyone who tried this before, it would be great to = have a > > discussion in person while we are in IETF102. Please let know if = you > > are available for discussion. >=20 > > Thanks, > > Rahul >=20 > > _______________________________________________ > > Roll mailing list > > Roll@ietf.org > > https://www.ietf.org/mailman/listinfo/roll = >=20 > --=20 > Michael Richardson >, Sandelman Software Works > -=3D IPv6 IoT consulting =3D- >=20 >=20 >=20 >=20 > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll = >=20 >=20 > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll = ________________________________________ Jo=C3=A3o Pedro Taveira Pinto Silva e-mail: joao.p.taveira@gmail.com github: joaopedrotaveira linkedin: joaopedrotaveira = --Apple-Mail=_A79B9D15-4E29-48A3-B05C-A5C4209A3814 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

Rahul, = I watch the youtube video of ROLL session (thanks to Michael last mail = to list) and I notice you ask about RPL implementations in linux kernel. = About my kernel implementation attempt history, roadmap and status, = please check https://github.com/joaopedrotaveira/linux-rpl/issues/1. = There=E2=80=99s a link with my initial plan and my failures.

If we could try to make = it happen, it would great. Send me your questions to my email or make = presure on github repo. I just would like to move this subject to any = other channel.

Abdussalam, I agree with Michael, there are discussions about = this subject were they should be. And IMHO, I never leaved, I=E2=80=99m = still here.

Best = Regards,
Jo=C3=A3o Pedro Taveira

On 23 = Jul 2018, at 13:29, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:



On Thu, Jul 19, 2018 at 4:16 AM, = Michael Richardson <mcr+ietf@sandelman.ca> wrote:

Hi, = I'm not sure that the ROLL list is a good place for Linux-specific
implementation questions.  In particular, it seems that = most implementers are
on monolithic embedded kernels = (contiki, openwsn, etc.)

Why? I don't care about most = implementers, I care about our RFCs implemented and discussed in IETF = lists, not outside, if we follow implementers some day we will = leave the ROLL list as they did !!!! 

IMHO  ROLL list is a good place = for implementing RFCs into Linux, I don't agree that the questions are = Linux specific, but implement specific.



There are discussions on unstrung-workers@lists.sandelman.ca about Linux
kernel integration (none recently through).

Discussions also occur on linux-wpan@vger.kernel.org.
It would be a = good place to start a new thread.

but also IMHO we need to = have some summary with discuss in this list about implementations = of WG RFCs.
 

Rahul Jadhav <rahul.ietf@gmail.com> wrote:
  =   > Hello = ROLL,

    > While trying to = integrate RPL with linux kernel and we had certain
  =   > design = choices. In that context I have some specific questions,
    > especially towards = linux-kernel integration and not towards RPL
  =   > protocol = implementation itself. Assuming RPL implementation will be in
    > userspace, questions = are:

    > 1. We can add/del = routes using rtnetlink interfaces ... this can be
  =   > used for = the routes learnt by RPL as well ... But RPL needs to
 =   > maintain = some additional per-route information on the 6LBR ... To be
    > very specific, we need = to store parent information in context to every
  =   > route. Is = it possible to do it with rtnetlink? I didn't find an option
    > to do that. If it = ain't possible then what could be an alt approach?

    > 2. RPL requires that = certain extended ipv6 options be added in data
  =   > flows .. = What is the best way to do this? It is possible to do this
    > with netfilter+libnfq = but i m not sure whether this is the best
  =   > = approach.

    > If there is anyone who = tried this before, it would be great to have a
  =   > discussion = in person while we are in IETF102. Please let know if you
    > are available for = discussion.

    > Thanks,
    > Rahul

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

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




_______________________________________________
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

________________________________________
Jo=C3= =A3o Pedro Taveira Pinto Silva
e-mail: joao.p.taveira@gmail.com
linkedin: joaopedrotaveira



= --Apple-Mail=_A79B9D15-4E29-48A3-B05C-A5C4209A3814-- From nobody Tue Jul 31 00:02:01 2018 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 35739130DDB for ; Tue, 31 Jul 2018 00:01:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] 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 wiDxd0iiESfV for ; Tue, 31 Jul 2018 00:01:56 -0700 (PDT) Received: from smtprelay.hostedemail.com (smtprelay0100.hostedemail.com [216.40.44.100]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C2E812DD85 for ; Tue, 31 Jul 2018 00:01:56 -0700 (PDT) Received: from filter.hostedemail.com (clb03-v110.bra.tucows.net [216.40.38.60]) by smtprelay08.hostedemail.com (Postfix) with ESMTP id 0FC23182CF67F; Tue, 31 Jul 2018 07:01:55 +0000 (UTC) X-Session-Marker: 73746F6B636F6E73406262686D61696C2E6E6C X-Spam-Summary: 2, -10, 0, , d41d8cd98f00b204, stokcons@bbhmail.nl, :::, RULES_HIT:41:72:152:355:379:582:599:800:857:962:967:973:983:988:989:1152:1189:1208:1212:1221:1260:1313:1314:1345:1359:1431:1436:1437:1516:1517:1518:1535:1542:1575:1588:1589:1592:1594:1711:1730:1776:1792:2068:2069:2198:2199:2525:2528:2559:2564:2682:2685:2693:2859:2895:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3353:3622:3865:3866:3867:3868:3870:3871:3872:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4250:4321:4362:4860:5007:6117:6119:6120:6261:6657:6659:6678:7875:7901:7903:8603:9010:9025:9038:9040:9177:9389:10004:10400:10848:11232:11658:11914:12043:12109:12114:12291:12379:12438:12663:12683:12740:12895:13071:13139:13439:13846:14093:14095:14096:14180:14181:14721:14799:21060:21080:21326:21433:21451:21627:21740:21773:21790:30054:30060:30062:30070, 0, RBL:216.40.42.5:@bbhmail.nl:.lbl8.mailshell.net-62.8.55.100 66.201.201.201, CacheIP:none, Bayesian:0.5, 0.5, 0.5, Netcheck:none, DomainCache:0, MSF:n X-HE-Tag: sleep74_4ae854174f92f X-Filterd-Recvd-Size: 5876 Received: from mail.bbhmail.nl (imap-ext [216.40.42.5]) (Authenticated sender: webmail@stokcons@bbhmail.nl) by omf09.hostedemail.com (Postfix) with ESMTPA; Tue, 31 Jul 2018 07:01:54 +0000 (UTC) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_d6158e08a3f12d198e6ee11979d189f8" Date: Tue, 31 Jul 2018 09:01:54 +0200 From: Peter van der Stok To: Routing Over Low power and Lossy networks Cc: Michael Richardson Organization: vanderstok consultancy Reply-To: consultancy@vanderstok.org Mail-Reply-To: consultancy@vanderstok.org In-Reply-To: <30663.1532980742@localhost> References: <30663.1532980742@localhost> Message-ID: <22dd687bb26c96a86b7c0612c2af2ed7@bbhmail.nl> X-Sender: stokcons@bbhmail.nl User-Agent: Roundcube Webmail/1.2.7 X-Originating-IP: [5.206.216.229] Archived-At: Subject: Re: [Roll] WRT adopting draft-rahul-roll-rpl-observations as WG document X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 31 Jul 2018 07:01:59 -0000 --=_d6158e08a3f12d198e6ee11979d189f8 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Hi Michael, thanks for a drastic point of view concerning 6550bis with removal of storing mode.What will removing SM mean for existing installations?. Removing SM means at least a 6550bis RFC and no update documents. Personally I am in favor of RPL 1.2 such that legacy can be managed. BTW are there volunteers for the writing? Peter Michael Richardson schreef op 2018-07-30 21:59: > {been watching the youtube video of the ROLL session} > > 1) I think that the work in roll-rpl-observations is really important. > -> that's why we should adopt the document so that it can have priority > over other non-WG documents in the agenda. > As our AD pointed out, we don't have to publish it. > > 2) Starting rfc6550bis or rfc6550updates is very important!!! > We have some options on how to do this, one of which is to publish a bunch > of very small updates. That's probably the lowest latency way, but it > does cause more IESG and RFC-EDITOR work. > So I think that we will be forced to publish a ~60-page update document > that collects all sorts of things. > > 3) I'd like to move to obsolete (mark as "historical") storing mode in favour > of dao-projection mode. I think that this is mostly orthogonal to the updates work, but > if we agree that we are going in that direction, there might be updates > that we don't need to do. > > 4) We need a new node capabilities mechanism. It could be quite > controversial as there are a lot of design choices here. maybe we should > probably encourage implementations, and then experimental RFCs. > _______________________________________________ > Roll mailing list > Roll@ietf.org > https://www.ietf.org/mailman/listinfo/roll --=_d6158e08a3f12d198e6ee11979d189f8 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 Hi Michael,

thanks for a drastic point of view concerning 6550bi= s with removal of storing mode.What will removing SM mean for existing inst= allations?.
Removing SM means at least a 6550bis RFC and no update doc= uments.

Personally I am in favor of RPL 1.2 such that legacy can= be managed.

BTW are there volunteers for the writing?

Peter


Michael Richardson schreef op 2018-07-30 21:59:

=
{been watching the youtube video of the ROLL session}

1)= I think that the work in roll-rpl-observations is really important.
=    -> that's why we should adopt the document so that it = can have priority
      over other non-= WG documents in the agenda.
   As our AD pointed out, = we don't have to publish it.

2) Starting rfc6550bis or rfc6550u= pdates is very important!!!
   We have some options on= how to do this, one of which is to publish a bunch
   = ;of very small updates.  That's probably the lowest latency way, but i= t
   does cause more IESG and RFC-EDITOR work.
&= nbsp;  So I think that we will be forced to publish a ~60-page up= date document
   that collects all sorts of things.
3) I'd like to move to obsolete (mark as "historical") storing mo= de in favour
   of dao-projection mode.  I think = that this is mostly orthogonal to the updates work, but
  &= nbsp;if we agree that we are going in that direction, there might be update= s
   that we don't need to do.

4) We need = a new node capabilities mechanism.  It could be quite
 &nbs= p; controversial as there are a lot of design choices here.  mayb= e we should
   probably encourage implementations, an= d then experimental RFCs.

= _______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll
--=_d6158e08a3f12d198e6ee11979d189f8-- From nobody Tue Jul 31 05:46:00 2018 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 1F4D4128B14 for ; Tue, 31 Jul 2018 05:45:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -12.61 X-Spam-Level: X-Spam-Status: No, score=-12.61 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 nh4Motk0huGt for ; Tue, 31 Jul 2018 05:45:56 -0700 (PDT) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0958B1252B7 for ; Tue, 31 Jul 2018 05:45:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10765; q=dns/txt; s=iport; t=1533041156; x=1534250756; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=sVz6d4GHjFbhG/5ZeS+tk+dmZlThjOkI5YITdGrACJo=; b=eYIfs2wLzqWm7D4RnpEP380NHp0fzi0pe6c7pyDaceB7I8U6OMRJ5LXB B2K0suj0Xz3xZjPkwElBwGRSNEKi1hn7ME3o0BT5lQhla3AWT0tCAdnu6 qhWOiN93TIT2ccplPZR0H5md2lieIXyU9clVDkDXTETK7fFj3Su/AoQJG U=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DkAAChWWBb/5ldJa1bGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYMkKmN/KIN+iAaMQ4FokGOFGYF6CxgBCoRJAheDDCE0GAECAQE?= =?us-ascii?q?CAQECbRwMhTcCAQMBASEEBkELEAIBCD8DAgICJQsUEQIEDgWDIAGBG2QPrA9?= =?us-ascii?q?7M4pEBYkEF4FBP4ESJwwTgkyDGwEBgUEBATWCajGCBCACmhUJAo82gUiEHYg?= =?us-ascii?q?oiA+KBQIRFIEkHTiBUnAVOyoBgj6CJRd6AQeHV4U+b41WgjoBAQ?= X-IronPort-AV: E=Sophos;i="5.51,427,1526342400"; d="scan'208,217";a="150397292" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jul 2018 12:45:41 +0000 Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id w6VCjfb4002879 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 31 Jul 2018 12:45:41 GMT Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 31 Jul 2018 07:45:40 -0500 Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1320.000; Tue, 31 Jul 2018 07:45:40 -0500 From: "Pascal Thubert (pthubert)" To: "consultancy@vanderstok.org" , "Routing Over Low power and Lossy networks" CC: Michael Richardson Thread-Topic: [Roll] WRT adopting draft-rahul-roll-rpl-observations as WG document Thread-Index: AQHUKD/OFRFc8FVrF0SF7ky5DiFo6aSpPAsAgAAMO84= Date: Tue, 31 Jul 2018 12:45:40 +0000 Message-ID: <28813905-00C9-4720-B20E-25B43DAAF394@cisco.com> References: <30663.1532980742@localhost>, <22dd687bb26c96a86b7c0612c2af2ed7@bbhmail.nl> In-Reply-To: <22dd687bb26c96a86b7c0612c2af2ed7@bbhmail.nl> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted Content-Type: multipart/alternative; boundary="_000_2881390500C94720B20E25B43DAAF394ciscocom_" MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com X-Outbound-Node: rcdn-core-2.cisco.com Archived-At: Subject: Re: [Roll] WRT adopting draft-rahul-roll-rpl-observations as WG document X-BeenThere: roll@ietf.org X-Mailman-Version: 2.1.27 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: Tue, 31 Jul 2018 12:45:58 -0000 --_000_2881390500C94720B20E25B43DAAF394ciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGVsbG8gYWxsDQoNCkkgYWdyZWUgd2l0aCBwcmV0dHkgbXVjaCBldmVyeXRoaW5nIHRoYXQgTWlj aGFlbCBzdWdnZXN0ZWQgYnV0IHRoZSByZW1vdmFsIG9mIHN0b3Jpbmcgbm9kZS4gUGxlYXNlIHJl bWVtYmVyIHRoYXQgUlBMIGlzIGEgcm91dGluZyBwcm90b2NvbCBhbmQgdGhhdCBpdCBjYW4gYmUg dXNlZCBpbiB2YXJpb3VzIGVudmlyb25tZW50cy4NCg0KU3RvcmluZyBtb2RlIGhhcyBhbiBhbmNl c3RvciB0aGF0IGRpZCB3ZWxsIGluIE1hbmV0IHR5cGUgb2YgbmV0d29ya3MuIEl0IGNhbiBiZSB1 c2VkIGluIGhvbWUgYW5kIGluIHNtYXJ0Z3JpZCBuZXR3b3JraW5nIHdoZXJlIG1lbW9yeSBpcyBu b3QgbmVjZXNzYXJpbHkgYSBjb25zdHJhaW50LiBJdCBpcyB1c2VkIGJldHdlZW4g4oCcbm9ybWFs 4oCdIHJvdXRlcnMgdG8gYm9vdHN0cmFwIGEgZmFicmljIGluIEFOSU1BLiBFdmVuIGlmIGl0IGlt cGxpZXMgc3RhdGVzLCBpdCBpcyBzdGlsbCBhIGxvdCBsZXNzIHRoYW4gZm9yIGEgY2xhc3NpY2Fs IElHUC4NCg0KV2UgY2Fubm90IGV2ZW4gY29uc2lkZXIgbWFraW5nIGl0IGhpc3RvcmljLiBJdCBq dXN0IGhhcyBhbiBhcHBsaWNhYmlsaXR5IHRoYXQgZG9lcyBub3QgaW5jbHVkZSBsYXJnZSBkb2Rh Z3Mgb2YgbWVtb3J5IGNvbnN0cmFpbmVkIGRldmljZXMuDQoNCkkgYWdyZWUgdGhvdWdoIHdpdGgg dGhlIHNwaXJpdCBpbiBNaWNoYWVs4oCZcyBtYWlsIHdoZXJlYnkgcm91dGUgcHJvamVjdGlvbiBw cm92aWRlcyBhbiBoeWJyaWRhdGlvbiBvZiBhIG5vbiBzdG9yaW5nIGluZnJhc3RydWN0dXJlIHdp dGggcGFydGljdWxhciBzdG9yaW5nIG1vZGUgcHJvamVjdGVkIHJvdXRlcyB0aGF0IG1ha2Ugc3Rv cmluZyBhcHBsaWNhYmxlIHRvIG1lbW9yeSBjb25zdHJhaW5lZCBub2RlcywgYW5kIHRoYXQgd2Ug bmVlZCBhIG5ldyBzcGVjIHRvIGFkdmVydGlzZSBuZWlnaGJvcmhvb2QgKHBlZXJzIGFuZCBkZWx0 YSBSYW5rKSBhbmQgY2FwYWJpbGl0aWVzIChlZyBhbW91bnQgb3Igc3RvcmluZyBtb2RlIHJvdXRl cyB0aGF0IGNhbiBiZSBoZWxkKSB0byB0aGUgcm9vdC4NCg0KQ2hlZXJzDQoNClBhc2NhbA0KDQpM ZSAzMSBqdWlsLiAyMDE4IMOgIDA5OjAyLCBQZXRlciB2YW4gZGVyIFN0b2sgPHN0b2tjb25zQGJi aG1haWwubmw8bWFpbHRvOnN0b2tjb25zQGJiaG1haWwubmw+PiBhIMOpY3JpdCA6DQoNCkhpIE1p Y2hhZWwsDQoNCnRoYW5rcyBmb3IgYSBkcmFzdGljIHBvaW50IG9mIHZpZXcgY29uY2VybmluZyA2 NTUwYmlzIHdpdGggcmVtb3ZhbCBvZiBzdG9yaW5nIG1vZGUuV2hhdCB3aWxsIHJlbW92aW5nIFNN IG1lYW4gZm9yIGV4aXN0aW5nIGluc3RhbGxhdGlvbnM/Lg0KUmVtb3ZpbmcgU00gbWVhbnMgYXQg bGVhc3QgYSA2NTUwYmlzIFJGQyBhbmQgbm8gdXBkYXRlIGRvY3VtZW50cy4NCg0KUGVyc29uYWxs eSBJIGFtIGluIGZhdm9yIG9mIFJQTCAxLjIgc3VjaCB0aGF0IGxlZ2FjeSBjYW4gYmUgbWFuYWdl ZC4NCg0KQlRXIGFyZSB0aGVyZSB2b2x1bnRlZXJzIGZvciB0aGUgd3JpdGluZz8NCg0KUGV0ZXIN Cg0KDQoNCk1pY2hhZWwgUmljaGFyZHNvbiBzY2hyZWVmIG9wIDIwMTgtMDctMzAgMjE6NTk6DQoN CntiZWVuIHdhdGNoaW5nIHRoZSB5b3V0dWJlIHZpZGVvIG9mIHRoZSBST0xMIHNlc3Npb259DQoN CjEpIEkgdGhpbmsgdGhhdCB0aGUgd29yayBpbiByb2xsLXJwbC1vYnNlcnZhdGlvbnMgaXMgcmVh bGx5IGltcG9ydGFudC4NCiAgIC0+IHRoYXQncyB3aHkgd2Ugc2hvdWxkIGFkb3B0IHRoZSBkb2N1 bWVudCBzbyB0aGF0IGl0IGNhbiBoYXZlIHByaW9yaXR5DQogICAgICBvdmVyIG90aGVyIG5vbi1X RyBkb2N1bWVudHMgaW4gdGhlIGFnZW5kYS4NCiAgIEFzIG91ciBBRCBwb2ludGVkIG91dCwgd2Ug ZG9uJ3QgaGF2ZSB0byBwdWJsaXNoIGl0Lg0KDQoyKSBTdGFydGluZyByZmM2NTUwYmlzIG9yIHJm YzY1NTB1cGRhdGVzIGlzIHZlcnkgaW1wb3J0YW50ISEhDQogICBXZSBoYXZlIHNvbWUgb3B0aW9u cyBvbiBob3cgdG8gZG8gdGhpcywgb25lIG9mIHdoaWNoIGlzIHRvIHB1Ymxpc2ggYSBidW5jaA0K ICAgb2YgdmVyeSBzbWFsbCB1cGRhdGVzLiAgVGhhdCdzIHByb2JhYmx5IHRoZSBsb3dlc3QgbGF0 ZW5jeSB3YXksIGJ1dCBpdA0KICAgZG9lcyBjYXVzZSBtb3JlIElFU0cgYW5kIFJGQy1FRElUT1Ig d29yay4NCiAgIFNvIEkgdGhpbmsgdGhhdCB3ZSB3aWxsIGJlIGZvcmNlZCB0byBwdWJsaXNoIGEg fjYwLXBhZ2UgdXBkYXRlIGRvY3VtZW50DQogICB0aGF0IGNvbGxlY3RzIGFsbCBzb3J0cyBvZiB0 aGluZ3MuDQoNCjMpIEknZCBsaWtlIHRvIG1vdmUgdG8gb2Jzb2xldGUgKG1hcmsgYXMgImhpc3Rv cmljYWwiKSBzdG9yaW5nIG1vZGUgaW4gZmF2b3VyDQogICBvZiBkYW8tcHJvamVjdGlvbiBtb2Rl LiAgSSB0aGluayB0aGF0IHRoaXMgaXMgbW9zdGx5IG9ydGhvZ29uYWwgdG8gdGhlIHVwZGF0ZXMg d29yaywgYnV0DQogICBpZiB3ZSBhZ3JlZSB0aGF0IHdlIGFyZSBnb2luZyBpbiB0aGF0IGRpcmVj dGlvbiwgdGhlcmUgbWlnaHQgYmUgdXBkYXRlcw0KICAgdGhhdCB3ZSBkb24ndCBuZWVkIHRvIGRv Lg0KDQo0KSBXZSBuZWVkIGEgbmV3IG5vZGUgY2FwYWJpbGl0aWVzIG1lY2hhbmlzbS4gIEl0IGNv dWxkIGJlIHF1aXRlDQogICBjb250cm92ZXJzaWFsIGFzIHRoZXJlIGFyZSBhIGxvdCBvZiBkZXNp Z24gY2hvaWNlcyBoZXJlLiAgbWF5YmUgd2Ugc2hvdWxkDQogICBwcm9iYWJseSBlbmNvdXJhZ2Ug aW1wbGVtZW50YXRpb25zLCBhbmQgdGhlbiBleHBlcmltZW50YWwgUkZDcy4NCg0KX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NClJvbGwgbWFpbGluZyBsaXN0 DQpSb2xsQGlldGYub3JnPG1haWx0bzpSb2xsQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5v cmcvbWFpbG1hbi9saXN0aW5mby9yb2xsDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0KUm9sbCBtYWlsaW5nIGxpc3QNClJvbGxAaWV0Zi5vcmc8bWFpbHRv OlJvbGxAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Jv bGwNCg== --_000_2881390500C94720B20E25B43DAAF394ciscocom_ Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: base64 PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IGRpcj0iYXV0byI+DQpI ZWxsbyBhbGwNCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkkgYWdyZWUgd2l0aCBwcmV0dHkgbXVj aCBldmVyeXRoaW5nIHRoYXQgTWljaGFlbCBzdWdnZXN0ZWQgYnV0IHRoZSByZW1vdmFsIG9mIHN0 b3Jpbmcgbm9kZS4gUGxlYXNlIHJlbWVtYmVyIHRoYXQgUlBMIGlzIGEgcm91dGluZyBwcm90b2Nv bCBhbmQgdGhhdCBpdCBjYW4gYmUgdXNlZCBpbiB2YXJpb3VzIGVudmlyb25tZW50cy4mbmJzcDs8 L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PlN0b3JpbmcgbW9kZSBoYXMgYW4gYW5jZXN0 b3IgdGhhdCBkaWQgd2VsbCBpbiBNYW5ldCB0eXBlIG9mIG5ldHdvcmtzLiBJdCBjYW4gYmUgdXNl ZCBpbiBob21lIGFuZCBpbiBzbWFydGdyaWQgbmV0d29ya2luZyB3aGVyZSBtZW1vcnkgaXMgbm90 IG5lY2Vzc2FyaWx5IGEgY29uc3RyYWludC4gSXQgaXMgdXNlZCBiZXR3ZWVuIOKAnG5vcm1hbOKA nSByb3V0ZXJzIHRvIGJvb3RzdHJhcCBhIGZhYnJpYyBpbiBBTklNQS4gRXZlbiBpZiBpdCBpbXBs aWVzDQogc3RhdGVzLCBpdCBpcyBzdGlsbCBhIGxvdCBsZXNzIHRoYW4gZm9yIGEgY2xhc3NpY2Fs IElHUC48YnI+DQo8YnI+DQo8ZGl2Pg0KPGRpdj5XZSBjYW5ub3QgZXZlbiBjb25zaWRlciBtYWtp bmcgaXQgaGlzdG9yaWMuIEl0IGp1c3QgaGFzIGFuIGFwcGxpY2FiaWxpdHkgdGhhdCBkb2VzIG5v dCBpbmNsdWRlIGxhcmdlIGRvZGFncyBvZiBtZW1vcnkgY29uc3RyYWluZWQgZGV2aWNlcy48L2Rp dj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PkkgYWdyZWUgdGhvdWdoIHdpdGggdGhlIHNwaXJp dCBpbiBNaWNoYWVs4oCZcyBtYWlsIHdoZXJlYnkgcm91dGUgcHJvamVjdGlvbiBwcm92aWRlcyBh biBoeWJyaWRhdGlvbiBvZiBhIG5vbiBzdG9yaW5nIGluZnJhc3RydWN0dXJlIHdpdGggcGFydGlj dWxhciBzdG9yaW5nIG1vZGUgcHJvamVjdGVkIHJvdXRlcyB0aGF0IG1ha2Ugc3RvcmluZyBhcHBs aWNhYmxlIHRvIG1lbW9yeSBjb25zdHJhaW5lZCBub2RlcywgYW5kIHRoYXQgd2UgbmVlZCBhDQog bmV3IHNwZWMgdG8gYWR2ZXJ0aXNlIG5laWdoYm9yaG9vZCAocGVlcnMgYW5kIGRlbHRhIFJhbmsp IGFuZCBjYXBhYmlsaXRpZXMgKGVnIGFtb3VudCBvciBzdG9yaW5nIG1vZGUgcm91dGVzIHRoYXQg Y2FuIGJlIGhlbGQpIHRvIHRoZSByb290LjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+ Q2hlZXJzJm5ic3A7PC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5QYXNjYWw8L2Rpdj4N CjwvZGl2Pg0KPGRpdj48YnI+DQpMZSAzMSBqdWlsLiAyMDE4IMOgIDA5OjAyLCBQZXRlciB2YW4g ZGVyIFN0b2sgJmx0OzxhIGhyZWY9Im1haWx0bzpzdG9rY29uc0BiYmhtYWlsLm5sIj5zdG9rY29u c0BiYmhtYWlsLm5sPC9hPiZndDsgYSDDqWNyaXQmbmJzcDs6PGJyPg0KPGJyPg0KPC9kaXY+DQo8 YmxvY2txdW90ZSB0eXBlPSJjaXRlIj4NCjxkaXY+SGkgTWljaGFlbCw8YnI+DQo8YnI+DQp0aGFu a3MgZm9yIGEgZHJhc3RpYyBwb2ludCBvZiB2aWV3IGNvbmNlcm5pbmcgNjU1MGJpcyB3aXRoIHJl bW92YWwgb2Ygc3RvcmluZyBtb2RlLldoYXQgd2lsbCByZW1vdmluZyBTTSBtZWFuIGZvciBleGlz dGluZyBpbnN0YWxsYXRpb25zPy48YnI+DQpSZW1vdmluZyBTTSBtZWFucyBhdCBsZWFzdCBhIDY1 NTBiaXMgUkZDIGFuZCBubyB1cGRhdGUgZG9jdW1lbnRzLjxicj4NCjxicj4NClBlcnNvbmFsbHkg SSBhbSBpbiBmYXZvciBvZiBSUEwgMS4yIHN1Y2ggdGhhdCBsZWdhY3kgY2FuIGJlIG1hbmFnZWQu PGJyPg0KPGJyPg0KQlRXIGFyZSB0aGVyZSB2b2x1bnRlZXJzIGZvciB0aGUgd3JpdGluZz88YnI+ DQo8YnI+DQpQZXRlcjxicj4NCjxicj4NCjxicj4NCjxwPk1pY2hhZWwgUmljaGFyZHNvbiBzY2hy ZWVmIG9wIDIwMTgtMDctMzAgMjE6NTk6PC9wPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSIgc3R5 bGU9InBhZGRpbmc6IDAgMC40ZW07IGJvcmRlci1sZWZ0OiAjMTAxMGZmIDJweCBzb2xpZDsgbWFy Z2luOiAwIj4NCjwhLS0gaHRtbCBpZ25vcmVkIC0tPjwhLS0gaGVhZCBpZ25vcmVkIC0tPjwhLS0g bWV0YSBpZ25vcmVkIC0tPg0KPGRpdiBjbGFzcz0icHJlIiBzdHlsZT0ibWFyZ2luOiAwOyBwYWRk aW5nOiAwOyBmb250LWZhbWlseTogbW9ub3NwYWNlIj48YnI+DQp7YmVlbiB3YXRjaGluZyB0aGUg eW91dHViZSB2aWRlbyBvZiB0aGUgUk9MTCBzZXNzaW9ufTxicj4NCjxicj4NCjEpIEkgdGhpbmsg dGhhdCB0aGUgd29yayBpbiByb2xsLXJwbC1vYnNlcnZhdGlvbnMgaXMgcmVhbGx5IGltcG9ydGFu dC48YnI+DQombmJzcDsmbmJzcDsmbmJzcDstJmd0OyB0aGF0J3Mgd2h5IHdlIHNob3VsZCBhZG9w dCB0aGUgZG9jdW1lbnQgc28gdGhhdCBpdCBjYW4gaGF2ZSBwcmlvcml0eTxicj4NCiZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO292ZXIgb3RoZXIgbm9uLVdHIGRvY3VtZW50cyBp biB0aGUgYWdlbmRhLjxicj4NCiZuYnNwOyZuYnNwOyZuYnNwO0FzIG91ciBBRCBwb2ludGVkIG91 dCwgd2UgZG9uJ3QgaGF2ZSB0byBwdWJsaXNoIGl0Ljxicj4NCjxicj4NCjIpIFN0YXJ0aW5nIHJm YzY1NTBiaXMgb3IgcmZjNjU1MHVwZGF0ZXMgaXMgdmVyeSBpbXBvcnRhbnQhISE8YnI+DQombmJz cDsmbmJzcDsmbmJzcDtXZSBoYXZlIHNvbWUgb3B0aW9ucyBvbiBob3cgdG8gZG8gdGhpcywgb25l IG9mIHdoaWNoIGlzIHRvIHB1Ymxpc2ggYSBidW5jaDxicj4NCiZuYnNwOyZuYnNwOyZuYnNwO29m IHZlcnkgc21hbGwgdXBkYXRlcy4gJm5ic3A7VGhhdCdzIHByb2JhYmx5IHRoZSBsb3dlc3QgbGF0 ZW5jeSB3YXksIGJ1dCBpdDxicj4NCiZuYnNwOyZuYnNwOyZuYnNwO2RvZXMgY2F1c2UgbW9yZSBJ RVNHIGFuZCBSRkMtRURJVE9SIHdvcmsuPGJyPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7U28gSSB0aGlu ayB0aGF0IHdlIHdpbGwgYmUgZm9yY2VkIHRvIHB1Ymxpc2ggYSB+NjAtcGFnZSB1cGRhdGUgZG9j dW1lbnQ8YnI+DQombmJzcDsmbmJzcDsmbmJzcDt0aGF0IGNvbGxlY3RzIGFsbCBzb3J0cyBvZiB0 aGluZ3MuPGJyPg0KPGJyPg0KMykgSSdkIGxpa2UgdG8gbW92ZSB0byBvYnNvbGV0ZSAobWFyayBh cyAmcXVvdDtoaXN0b3JpY2FsJnF1b3Q7KSBzdG9yaW5nIG1vZGUgaW4gZmF2b3VyPGJyPg0KJm5i c3A7Jm5ic3A7Jm5ic3A7b2YgZGFvLXByb2plY3Rpb24gbW9kZS4gJm5ic3A7SSB0aGluayB0aGF0 IHRoaXMgaXMgbW9zdGx5IG9ydGhvZ29uYWwgdG8gdGhlIHVwZGF0ZXMgd29yaywgYnV0PGJyPg0K Jm5ic3A7Jm5ic3A7Jm5ic3A7aWYgd2UgYWdyZWUgdGhhdCB3ZSBhcmUgZ29pbmcgaW4gdGhhdCBk aXJlY3Rpb24sIHRoZXJlIG1pZ2h0IGJlIHVwZGF0ZXM8YnI+DQombmJzcDsmbmJzcDsmbmJzcDt0 aGF0IHdlIGRvbid0IG5lZWQgdG8gZG8uPGJyPg0KPGJyPg0KNCkgV2UgbmVlZCBhIG5ldyBub2Rl IGNhcGFiaWxpdGllcyBtZWNoYW5pc20uICZuYnNwO0l0IGNvdWxkIGJlIHF1aXRlPGJyPg0KJm5i c3A7Jm5ic3A7Jm5ic3A7Y29udHJvdmVyc2lhbCBhcyB0aGVyZSBhcmUgYSBsb3Qgb2YgZGVzaWdu IGNob2ljZXMgaGVyZS4gJm5ic3A7bWF5YmUgd2Ugc2hvdWxkIDxicj4NCiZuYnNwOyZuYnNwOyZu YnNwO3Byb2JhYmx5IGVuY291cmFnZSBpbXBsZW1lbnRhdGlvbnMsIGFuZCB0aGVuIGV4cGVyaW1l bnRhbCBSRkNzLjwvZGl2Pg0KPGJyPg0KPGRpdiBjbGFzcz0icHJlIiBzdHlsZT0ibWFyZ2luOiAw OyBwYWRkaW5nOiAwOyBmb250LWZhbWlseTogbW9ub3NwYWNlIj5fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NClJvbGwgbWFpbGluZyBsaXN0PGJyPg0K PGEgaHJlZj0ibWFpbHRvOlJvbGxAaWV0Zi5vcmciIHJlbD0ibm9yZWZlcnJlciI+Um9sbEBpZXRm Lm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp bmZvL3JvbGwiIHRhcmdldD0iX2JsYW5rIiByZWw9Im5vcmVmZXJyZXIiPmh0dHBzOi8vd3d3Lmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vcm9sbDwvYT48L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwv ZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+DQo8ZGl2PjxzcGFu Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPC9zcGFuPjxi cj4NCjxzcGFuPlJvbGwgbWFpbGluZyBsaXN0PC9zcGFuPjxicj4NCjxzcGFuPjxhIGhyZWY9Im1h aWx0bzpSb2xsQGlldGYub3JnIj5Sb2xsQGlldGYub3JnPC9hPjwvc3Bhbj48YnI+DQo8c3Bhbj48 YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JvbGwiPmh0dHBz Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcm9sbDwvYT48L3NwYW4+PGJyPg0KPC9k aXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_2881390500C94720B20E25B43DAAF394ciscocom_--