Re: [Roll] Intend for draft-tripathi-roll-reactive-applicability

"JP Vasseur (jvasseur)" <jvasseur@cisco.com> Mon, 06 January 2014 18:24 UTC

Return-Path: <jvasseur@cisco.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75D311AE15A for <roll@ietfa.amsl.com>; Mon, 6 Jan 2014 10:24:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level:
X-Spam-Status: No, score=-10.038 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, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 ryUo7V4NKaoz for <roll@ietfa.amsl.com>; Mon, 6 Jan 2014 10:24:53 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 5F7B91AE159 for <roll@ietf.org>; Mon, 6 Jan 2014 10:24:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5230; q=dns/txt; s=iport; t=1389032685; x=1390242285; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tNd+l3+slH1il8u769uGEHtqu4UoormqUmURzD3blko=; b=Xa/6T9z7M2MsVEzMdPpbmRUHtrDsesaduoq3/I3qCkLC1ty9kYf6DiQd TwtinjRtgdvsoqQIDfz1bIgdOY2lvH02ALhLs/UybHKAaNfOx1wLaiG59 qjBjRr/qiAWgnSNNe80g7JnfVK3P6FI80RX5m8LxEavHMuIFR4LalGzup A=;
X-IronPort-AV: E=Sophos; i="4.95,614,1384300800"; d="scan'208,217"; a="10854813"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-1.cisco.com with ESMTP; 06 Jan 2014 18:24:45 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s06IOijH009836 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Jan 2014 18:24:44 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.29]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0123.003; Mon, 6 Jan 2014 12:24:44 -0600
From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
To: Ines Robles <mariainesrobles@googlemail.com>
Thread-Topic: Intend for draft-tripathi-roll-reactive-applicability
Thread-Index: AQHPCwySkaJmD9RduUaGNYAD4XxD5w==
Date: Mon, 06 Jan 2014 18:24:44 +0000
Message-ID: <E9B58E97-B9C8-4BCF-8B48-8EF6E0B8CDBD@cisco.com>
References: <CAP+sJUfBoD_L1o2W4viAdn4DayfbksbZPNB5ezujDbEtojps=A@mail.gmail.com>
In-Reply-To: <CAP+sJUfBoD_L1o2W4viAdn4DayfbksbZPNB5ezujDbEtojps=A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.60.114.226]
Content-Type: multipart/alternative; boundary="_000_E9B58E97B9C84BCF8B488EF6E0B8CDBDciscocom_"
MIME-Version: 1.0
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, roll <roll@ietf.org>, Joydeep Tripathi <jt369@drexel.edu>, "Jaudelice C. de Oliveira" <jau@coe.drexel.edu>
Subject: Re: [Roll] Intend for draft-tripathi-roll-reactive-applicability
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Mon, 06 Jan 2014 18:24:55 -0000

I can see two paths: (1) ROLL WG ID (not the easiest though, although this could be seen as an applicability
ID) or (2) AD sponsored ?

On Jan 6, 2014, at 7:10 PM, Ines Robles <mariainesrobles@googlemail.com<mailto:mariainesrobles@googlemail.com>> wrote:

Hi,

Thanks for this draft, https://ietf.org/doc/draft-tripathi-roll-reactive-applicability/

Abstract

This document describes serious issues and shortcomings regarding the use of reactive routing protocols in low power and lossy networks(LLNs). Routing requirements for various LLN deployments are discussed in order to judge how reactive routing may or may notadhere to the necessary criteria.

We would like to know please,  how is the intend for this document? how this draft would be aligned with roll charter?, should we re-chartering?

Thank you in advance,

Ines Robles