Re: [Roll] Request for Comments for ROLL Charter

"Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl> Tue, 28 June 2016 16:02 UTC

Return-Path: <diego.dujovne@mail.udp.cl>
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 52C7312D590 for <roll@ietfa.amsl.com>; Tue, 28 Jun 2016 09:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 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_LOW=-0.7] 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 9cZ--f5QnKoB for <roll@ietfa.amsl.com>; Tue, 28 Jun 2016 09:02:22 -0700 (PDT)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 AB4A212D58A for <roll@ietf.org>; Tue, 28 Jun 2016 09:02:21 -0700 (PDT)
Received: by mail-wm0-x22e.google.com with SMTP id f126so146444365wma.1 for <roll@ietf.org>; Tue, 28 Jun 2016 09:02:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mail-udp-cl.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=sUbRoht4IRrsk948dnNe76jnLsOvkMrv6bUa/ETyn6o=; b=0D9FOzWFpHm3lYR9seHR1J7ZSLDLlbVbCu0OIJikNW53hEe/SaGUHrrvwQnjPZb5H8 QXysTt4aJHS7+hZJVMx1Vx9xCye3MnWeZMInWCW7SiMtrUq35SA7h+mcaZpD8gyhkPF5 uckhVLhIayRv9R5R+cCOFJ+QRbvCc94EpRkqjOt3sRGb41GmZyCYVAYWOy2ANG5wAjZ8 xL8nsDK1nIbnAdK85kf6fv0UC2t9mHM6XaHy+7z3rme8KSIMWxFyksVuni35n8x9NYJN mCqa++Pq0OVyyZn1F+ZYUYKKrykxd+oGNHiKsDdpVJ39d6RO+89ho9JoxV5kXTPuLNHC tCbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=sUbRoht4IRrsk948dnNe76jnLsOvkMrv6bUa/ETyn6o=; b=iAlVWWP17m/xJzymWSMIm67P/b90BN30sz8tAXWItCVmd6wFjMgRmV1fhVlcfdzCY6 AdiXstLtoqS7EXsPLHXFa4pxNLCHoWTNK21fOffJWO0CiqQhM7894ZeFgcvkvKQocRto kTs+4cgPLjAdmwitUDdUfKIyXy8iHSvhngyNHZDzPlL+i5YsGltrGc5Wq3w5EkFxYcAe T1ZAtdtF1IYYKj26Mnlk7bcp2tQAYOlUACAAkVOqNfG9jtNvE01DzL3H+v65vuZ8Z6li Gg7uc2PuRpp8+l8VSiK7x0m8EVAU3SdMPGgjhS7eTeG1vgVXcSS70ha7GbpHWq1JIlKh jlMA==
X-Gm-Message-State: ALyK8tKysV/IPvypt8vG13qgIL8ojMTLW262stBzvbIPq+lF0fg2o5GgLr7kGrQSAwYIQoLp5+ILtvvz4xl65g==
X-Received: by 10.194.246.4 with SMTP id xs4mr4019647wjc.96.1467129739932; Tue, 28 Jun 2016 09:02:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.68.10 with HTTP; Tue, 28 Jun 2016 09:02:18 -0700 (PDT)
In-Reply-To: <231ea84926a546bfa4a520ef378464a0@XCH-RCD-001.cisco.com>
References: <CAP+sJUdRQHJhuszRLmMLoObVVELTGKAboPZpjHRV1M1t3T1BpA@mail.gmail.com> <962ecd511f1b4629bcf329790509bb0c@XCH-RCD-001.cisco.com> <17987.1467118035@obiwan.sandelman.ca> <7887a2c930bd4eb3b90da72e2bbe914b@XCH-RCD-001.cisco.com> <ec28f1cd-5f5e-43d9-bfc6-706a8b3116f2@gmail.com> <CAH7SZV-yuc8Zx6NBi_vMHZMFqEwZuKb25hewE2w1CC48yNyZ6Q@mail.gmail.com> <4B5E9AF4-CC70-4ABA-A637-A0F8585EAEDF@landisgyr.com> <231ea84926a546bfa4a520ef378464a0@XCH-RCD-001.cisco.com>
From: "Prof. Diego Dujovne" <diego.dujovne@mail.udp.cl>
Date: Tue, 28 Jun 2016 13:02:18 -0300
Message-ID: <CAH7SZV9VjHyBObXzOd-gM+ZUXJvGeCaRE73+ptVLRUw7ur+HWA@mail.gmail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3af2efd0a19053658c21c
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/76TgHDMO_60sbRHZGuwLQz2OSL8>
Subject: Re: [Roll] Request for Comments for ROLL Charter
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jun 2016 16:02:26 -0000

I vote for that text. I like multicast included in the
charter too.
Regards,

                                Diego

2016-06-28 11:53 GMT-04:00 Pascal Thubert (pthubert) <pthubert@cisco.com>;:

> So leave it at “improvements to the RPL routing protocol” ? It already has
> some multicast, so that much would be in as well.
>
>
>
> Pascal
>
>
>
> *From:* Roll [mailto:roll-bounces@ietf.org] *On Behalf Of *Turner, Randy
> *Sent:* mardi 28 juin 2016 17:12
> *To:* Routing Over Low power and Lossy networks <roll@ietf.org>;
> *Subject:* Re: [Roll] Request for Comments for ROLL Charter
>
>
>
> +1 just a generalization of my earlier suggestion
>
> R.
>
>
> On Jun 28, 2016, at 10:46 AM, Prof. Diego Dujovne <
> diego.dujovne@mail.udp.cl>; wrote:
>
> Pascal, Michael:
>
>                          I agree with Cenk. I think we need some room for
>
> other ideas. Is it too general to use that phrase?
>
> Regards,
>
>                                           Diego
>
>
>
> 2016-06-28 10:31 GMT-04:00 Cenk Gündogan <cnkgndgn@gmail.com>;:
>
> Hello Pascal, Michael,
>
> Isn't it too restrictive if we limit the text to the non-storing and
> storing modes only?
> IMO other modes, like the "P2P Route Discovery" mode as defined inRFC6997
> and future modes (if planned) could also benefit from those improvements.
>
> How about:
> Additional protocol elements to reduce bytes over the air and/or the
> amount of accumulated routing states.
>
>
>
> On 06/28/2016 03:49 PM, Pascal Thubert (pthubert) wrote:
>
> Pascal Thubert (pthubert) <pthubert@cisco.com>; wrote:
>
>     > Additional protocol elements to reduce source route headers in
>     > non-storing mode and/or memory consumption in storing mode such as
>     > route projection and BIER.
> It sounds too prescriptive, as if we have limited ourselves in the charter
> to those two methods.  I don't think that this is your intention.
>
> Agreed, Michael. We can bar from " such as ..." on.
>
> Cheers,
>
> Pascal
>
> -----Original Message-----
> From: Roll [mailto:roll-bounces@ietf.org] On Behalf Of Michael Richardson
> Sent: mardi 28 juin 2016 14:47
> To: Routing Over Low power and Lossy networks <roll@ietf.org>;
> Cc: peter van der Stok <stokcons@xs4all.nl>;
> Subject: Re: [Roll] Request for Comments for ROLL Charter
>
>
> Pascal Thubert (pthubert) <pthubert@cisco.com>; wrote:
>      > Additional protocol elements to reduce source route headers in
>      > non-storing mode and/or memory consumption in storing mode such as
>      > route projection and BIER.
>
> It sounds too prescriptive, as if we have limited ourselves in the charter
> to those
> two methods.  I don't think that this is your intention.
>
> If you wrote:
>
>      > Additional protocol elements to reduce source route headers in
>      > non-storing mode and/or memory consumption in storing mode.
>      > These elements may leverage mechanisms such as route projection and
> BIER.
>
> would be clearer that these are not the only two admissible methods.
> I'm not sure that we need to say what the methods are *at all*
>
>      > There is a wide scope of application areas for LLNs, including
>      > industrial monitoring, building automation (HVAC, lighting, access
>      > control, fire), connected homes, health care, environmental
> monitoring,
>      > urban sensor networks (e.g. Smart Grid), asset tracking.  The
> Working
>      > Group focuses on routing solutions for a subset of these: connected
>      > home, building and urban sensor networks for which routing
> requirements
>      > have been specified. These application-specific routing requirement
>      > documents were used for protocol design.
>
>      > The Working Group focuses on IPv6 routing architectural framework
> for
>      > these application scenarios. The Framework will take into
> consideration
>      > various aspects including high reliability in the presence of time
>      > varying loss characteristics and connectivity while permitting
>      > low-power operation with very modest memory and CPU pressure in
>      > networks potentially comprising a very large number (several
> thousands)
>      > of nodes.
>
> I'd like these two paragraphs removed as being ancient motherhood text.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works  -=
> IPv6 IoT consulting =-
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>
>
>
> --
>
> DIEGO DUJOVNE
> Profesor Asociado
> Escuela de Informática y Telecomunicaciones
> Facultad de Ingeniería - Universidad Diego Portales - Chile
> www.ingenieria.udp.cl
> (56 2) 676 8125
>
> _______________________________________________
> 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
>
>


-- 
DIEGO DUJOVNE
Profesor Asociado
Escuela de Informática y Telecomunicaciones
Facultad de Ingeniería - Universidad Diego Portales - Chile
www.ingenieria.udp.cl
(56 2) 676 8125