Re: [Roll] I-D Action:draft-ietf-roll-building-routing-reqs-04.txt
JP Vasseur <jvasseur@cisco.com> Wed, 04 February 2009 12:03 UTC
Return-Path: <jvasseur@cisco.com>
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 1236F28C1F6 for <roll@core3.amsl.com>; Wed, 4 Feb 2009 04:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.385
X-Spam-Level:
X-Spam-Status: No, score=-10.385 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, 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 ZqoDukJgEqWX for <roll@core3.amsl.com>; Wed, 4 Feb 2009 04:03:06 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id BFECC28C24A for <roll@ietf.org>; Wed, 4 Feb 2009 04:01:44 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.37,378,1231113600"; d="scan'208,217"; a="32813489"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 04 Feb 2009 12:01:24 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n14C1OKB017062; Wed, 4 Feb 2009 13:01:24 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n14C1OJa027478; Wed, 4 Feb 2009 12:01:24 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Feb 2009 13:01:24 +0100
Received: from ams-jvasseur-8715.cisco.com ([10.55.201.134]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 4 Feb 2009 13:01:23 +0100
Message-Id: <EBF7EF8A-9320-487B-B389-97229C19BD96@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: Jerald.P.Martocci@jci.com
In-Reply-To: <OF7D7F7635.EA31AECE-ON86257552.007CB020-86257552.007D394C@jci.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-70--108871349"
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Wed, 04 Feb 2009 13:01:22 +0100
References: <OF7D7F7635.EA31AECE-ON86257552.007CB020-86257552.007D394C@jci.com>
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 04 Feb 2009 12:01:23.0563 (UTC) FILETIME=[4CB653B0:01C986C0]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=9946; t=1233748884; x=1234612884; c=relaxed/simple; s=amsdkim1002; 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]=20I-D=20Action=3Adraft-ietf-roll -building-routing-reqs-04.txt |Sender:=20; bh=oD8J6kF9Op9uBamjLDgGRB8Rh2seYUSQ89jCpp6MJZg=; b=r/9csAKnaGx9sFbAetuUBAdMIz7t1dxGmAdBD7QQyQv5nzWxYO33H5K4GD 6DjoMqcsXL+15ECKgA/QOx1ZkmgKLHgQ5euLUXDpcgiTKIN96eDvuJ5w8Hoh wBZHeKRAal;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Cc: ROLL WG <roll@ietf.org>
Subject: Re: [Roll] I-D Action:draft-ietf-roll-building-routing-reqs-04.txt
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/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: Wed, 04 Feb 2009 12:03:08 -0000
Hi Jerry et all, Thanks for having addressed all comments from various people during LC. I made a very final pass and fixed a few minor issues found during IDNits (used references, SHOULD not => SHOULD NOT ...), thus this revision 05 that I just posted, now ready for publication. This closes our series of ROLL routing requirements documents. Thanks. JP. On Feb 3, 2009, at 11:47 PM, Jerald.P.Martocci@jci.com wrote: > > All, > > The -04 version of the Building Requirements document has just been > posted. The -04 document incorporates only three minor changes from > -03 ... > > 1) The 'Parallel Download' requirement has been moved from the > requirements section of the draft body to Appendix A. JP had > requested this change. I agreed in that this requirement is not a > routing requirement. > > 2) The 'Security' section of the draft was reworded to discuss > network security requirements as they relate to routing. The prior > draft was not clear which of the security requirements were related > to routing. > > 3) I reread the entire draft and cleaned up a few remaining > grammatical errors. I also reordered the requirements in Appendix A > in what I believe is a priority order. they had been in > chronological order in the -03 draft. > > Jerry > > > > > > > Internet-Drafts@ietf.org > Sent by: roll-bounces@ietf.org > 02/03/2009 04:29 PM > > To > i-d-announce@ietf.org > cc > roll@ietf.org > Subject > [Roll] I-D Action:draft-ietf-roll-building-routing-reqs-04.txt > > > > > > 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 Working Group of the IETF. > > > Title : Building Automation Routing > Requirements in Low Power and Lossy Networks > Author(s) : J. Martocci, et al. > Filename : draft-ietf-roll-building-routing- > reqs-04.txt > Pages : 29 > Date : 2009-02-03 > > The Routing Over Low power and Lossy network (ROLL) Working Group has > been chartered to work on routing solutions for Low Power and Lossy > networks (LLN) in various markets: Industrial, Commercial (Building), > Home and Urban. Pursuant to this effort, this document defines the > routing requirements for building automation. > > Requirements Language > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this > document are to be interpreted as described in RFC-2119. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-roll-building-routing-reqs-04.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft. > ftp://anonymous@ftp.ietf.org/internet-drafts/draft-ietf-roll-building-routing-reqs-04.txt_______________________________________________ > 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
- [Roll] I-D Action:draft-ietf-roll-building-routin… Internet-Drafts
- Re: [Roll] I-D Action:draft-ietf-roll-building-ro… Jerald.P.Martocci
- Re: [Roll] I-D Action:draft-ietf-roll-building-ro… JP Vasseur