Re: [Roll] Adoption of draft-brandt-roll-home-routing-reqs as a ROLL WG document ?

JP Vasseur <jvasseur@cisco.com> Thu, 15 May 2008 22:46 UTC

Return-Path: <roll-bounces@ietf.org>
X-Original-To: roll-archive@ietf.org
Delivered-To: ietfarch-roll-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A2143A6821; Thu, 15 May 2008 15:46:52 -0700 (PDT)
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344D03A6821 for <roll@core3.amsl.com>; Thu, 15 May 2008 15:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.222
X-Spam-Level:
X-Spam-Status: No, score=-5.222 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5eOmCEF8puEL for <roll@core3.amsl.com>; Thu, 15 May 2008 15:46:50 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id CA95D3A67A3 for <roll@ietf.org>; Thu, 15 May 2008 15:46:49 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,493,1204520400"; d="scan'208,217";a="8386466"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 15 May 2008 18:46:44 -0400
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m4FMki7a019263; Thu, 15 May 2008 18:46:44 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m4FMkiCO015935; Thu, 15 May 2008 22:46:44 GMT
Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 15 May 2008 18:46:44 -0400
Received: from 10.86.104.179 ([10.86.104.179]) by xmb-rtp-213.amer.cisco.com ([64.102.31.112]) with Microsoft Exchange Server HTTP-DAV ; Thu, 15 May 2008 22:46:43 +0000
User-Agent: Microsoft-Entourage/12.1.0.080305
Date: Thu, 15 May 2008 18:46:40 -0400
From: JP Vasseur <jvasseur@cisco.com>
To: Zachary Smith <zsmith@daintree.net>
Message-ID: <C4523590.3CAF8%jvasseur@cisco.com>
Thread-Topic: [Roll] Adoption of draft-brandt-roll-home-routing-reqs as a ROLL WG document ?
Thread-Index: Aci23YoKjgog+RtsLky7lRE3k3mh4g==
In-Reply-To: <2AB78622-C686-4431-A794-6EF5A28CB561@daintree.net>
Mime-version: 1.0
X-OriginalArrivalTime: 15 May 2008 22:46:44.0486 (UTC) FILETIME=[8CB68A60:01C8B6DD]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4642; t=1210891604; x=1211755604; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20<jvasseur@cisco.com> |Subject:=20Re=3A=20[Roll]=20Adoption=20of=20draft-brandt-r oll-home-routing-reqs=20as=20a=20ROLL=0A=20WG=20document=20? |Sender:=20 |To:=20Zachary=20Smith=20<zsmith@daintree.net>; bh=OGAKesqo++mE4WCkKCxBCkVT4Vlo+I37Usj4W3vdiQk=; b=dzSwi1xdwFZpQ5dc9c6I7UCAvmY6OpKWB2liZO3Hi+KZiOr0iS3m5GlpUG jmzqN8L47swIbp6ukn91X7Js2B4D1uC4ysnveAd+kW7JzPykOtHfI7VXdPiV 7Y0NAWsZbV;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
Cc: roll@ietf.org
Subject: Re: [Roll] Adoption of draft-brandt-roll-home-routing-reqs as a ROLL WG document ?
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: multipart/mixed; boundary="===============0634226460=="
Sender: roll-bounces@ietf.org
Errors-To: roll-bounces@ietf.org

Thanks for your reply.

ps: that gives me the opportunity to clarify one thing though: by all means,
adopting a document as a WG document does not mean that the document is
ready for publication ! It just means that the WG agrees to take it as the
base document to address a WG item.

Thanks.

JP.


On 5/15/08 6:22 PM, "Zachary Smith" <zsmith@daintree.net> wrote:

> Yes,
> 
> Although there is a point that probably bears discussion. In a
> multi-application network with sleeping end devices and resource-constrained
> routers, there is an end device management problem that is related to routing
> and might be considered as part of the routing solution. In short, it doesn't
> really make sense to rely on nearby routers to buffer arbitrary traffic for
> sleeping end devices. There are a number of possible solutions to this problem
> and not all of them involve the network layer but, if we are talking about
> "resource aware" routing then we might want to put in a requirement or two
> around this.
> 
> My $0.02US,
> 
>   z
> 
> On May 15, 2008, at 1:41 PM, JP Vasseur wrote:
> 
>>  Dear WG,
>>  
>>  Do you support the adoption of
>> http://www.ietf.org/internet-drafts/draft-brandt-roll-home-routing-reqs-01.tx
>> t as a ROLL WG document ?
>>  
>>  Thanks.
>>  
>>  JP. 
>>   _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>> 
>>  
>> Zachary Smith - CTO
>> http://www.daintree.net/
>> zsmith@daintree.net
>> 
>> 
>>  
>> 
>> 

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