IETF Logo Mail Archive

Re: [6tisch] New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-05.txt

"Brett, Patricia (PA62)" <patricia.brett@honeywell.com> Tue, 28 October 2014 12:01 UTC

Return-Path: <patricia.brett@honeywell.com>
X-Original-To: 6tisch@ietfa.amsl.com
Delivered-To: 6tisch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4D41A86FB; Tue, 28 Oct 2014 05:01:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 Qnjj10o5am-Y; Tue, 28 Oct 2014 05:01:40 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0142.outbound.protection.outlook.com [65.55.169.142]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C4801A6FCF; Tue, 28 Oct 2014 05:00:01 -0700 (PDT)
Received: from BN1PR07CA0061.namprd07.prod.outlook.com (10.255.193.36) by CO2PR0701MB709.namprd07.prod.outlook.com (10.141.245.148) with Microsoft SMTP Server (TLS) id 15.1.6.9; Tue, 28 Oct 2014 11:59:58 +0000
Received: from BN1AFFO11FD040.protection.gbl (2a01:111:f400:7c10::140) by BN1PR07CA0061.outlook.office365.com (2a01:111:e400:45::36) with Microsoft SMTP Server (TLS) id 15.1.6.9 via Frontend Transport; Tue, 28 Oct 2014 11:59:57 +0000
Received: from DE08W1027.honeywell.com (199.61.26.155) by BN1AFFO11FD040.mail.protection.outlook.com (10.58.52.251) with Microsoft SMTP Server (TLS) id 15.0.1049.20 via Frontend Transport; Tue, 28 Oct 2014 11:59:57 +0000
Received: from de08ex5003.global.ds.honeywell.com (10.216.34.42) by DE08W1027.honeywell.com (10.221.248.38) with Microsoft SMTP Server id 14.3.210.2; Tue, 28 Oct 2014 05:02:37 -0700
Received: from DE08EX3001.global.ds.honeywell.com ([169.254.1.176]) by de08ex5003.global.ds.honeywell.com ([10.216.14.76]) with mapi id 14.03.0210.002; Tue, 28 Oct 2014 07:59:54 -0400
From: "Brett, Patricia (PA62)" <patricia.brett@honeywell.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Carsten Bormann <cabo@tzi.org>
Thread-Topic: [6tisch] New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-05.txt
Thread-Index: AQHP8gMrAV2gakhP90atgtUiqheORZxEIl2wgABiY/CAAEZ3AIAAAf6ggACFbwCAABLfgIAAA8iQ
Date: Tue, 28 Oct 2014 11:59:54 +0000
Message-ID: <861C280A4EB34046A0D9A4324E4E822401490B29@de08ex3001.global.ds.honeywell.com>
References: <20141027162913.19095.85860.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD848A22B96@xmb-rcd-x01.cisco.com> <861C280A4EB34046A0D9A4324E4E82240148D6B8@de08ex3001.global.ds.honeywell.com> <097025FF-6076-45F0-8A2E-0FDA08335CB0@tzi.org> <861C280A4EB34046A0D9A4324E4E82240148D7EB@de08ex3001.global.ds.honeywell.com>, <12467F5C-9C5E-40F0-8D6C-0CEB8978DCC3@tzi.org> <8B945CD1-B841-4753-9CCE-BFC6FCEFE7E7@cisco.com>
In-Reply-To: <8B945CD1-B841-4753-9CCE-BFC6FCEFE7E7@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.29.148.7]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Forwarded
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:199.61.26.155; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(6009001)(51704005)(377454003)(13464003)(189002)(199003)(105586002)(106466001)(81156004)(92726001)(2656002)(21056001)(50986999)(54356999)(4396001)(76176999)(86362001)(93886004)(92566001)(47776003)(77096002)(85852003)(95666004)(20776003)(85306004)(64706001)(50466002)(31966008)(16796002)(55846006)(19580395003)(44976005)(69596002)(19580405001)(33656002)(107046002)(6806004)(46102003)(80022003)(97736003)(87936001)(120916001)(230783001)(68736004)(106116001)(76482002)(23756003)(84676001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR0701MB709; H:DE08W1027.honeywell.com; FPR:; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:CO2PR0701MB709;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Forefront-PRVS: 0378F1E47A
Received-SPF: Neutral (protection.outlook.com: 199.61.26.155 is neither permitted nor denied by domain of honeywell.com)
Authentication-Results: spf=neutral (sender IP is 199.61.26.155) smtp.mailfrom=patricia.brett@honeywell.com;
X-OriginatorOrg: Honeywell.com
Archived-At: http://mailarchive.ietf.org/arch/msg/6tisch/-kuJQriUI0sEv8BUIFkAi2-s_QY
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, "Brett, Patricia (PA62)" <patricia.brett@honeywell.com>, "6lo@ietf.org" <6lo@ietf.org>
Subject: Re: [6tisch] New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-05.txt
X-BeenThere: 6tisch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discuss link layer model for Deterministic IPv6 over the TSCH mode of IEEE 802.15.4e, and impacts on RPL and 6LoWPAN such as resource allocation" <6tisch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tisch>, <mailto:6tisch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tisch/>
List-Post: <mailto:6tisch@ietf.org>
List-Help: <mailto:6tisch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tisch>, <mailto:6tisch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Oct 2014 12:01:44 -0000

Hi Pascal,
I understood from Pat Kinney that 802 is considering taking up some work w.r.t. mesh under.
Regards,
Pat

-----Original Message-----
From: Pascal Thubert (pthubert) [mailto:pthubert@cisco.com] 
Sent: Tuesday, October 28, 2014 3:46 AM
To: Carsten Bormann
Cc: Brett, Patricia (PA62); 6lo@ietf.org; 6tisch@ietf.org
Subject: Re: [6tisch] New Version Notification for draft-thubert-6lo-rfc6775-update-reqs-05.txt

Same here, Pat. There is no anti-mesh-under intention. From the L3 perspective the mesh under looks like one hop and we must cover that case, certainly!

We already have requirements that apply to one L3 hop like the capability to proxy on the backbone, but nothing that is specific to a multi L2 hops mesh under.

If you are aware of requirements that we missed please let us know... Now is the time !

Pascal

Le 28 oct. 2014 à 07:38, Carsten Bormann <cabo@tzi.org> a écrit :

>> Mesh under been in use and working for years in an IEC wireless standard for a low power network. 
>> As such it should be an option.
> 
> Certainly.  RFC 6775 was designed to be applicable to both mesh-under and route-over routing.
> 
> E.g., it starts out saying:
> 
>> 1.3.  Goals and Assumptions
>> 
>>   The document has the following main goals and assumptions.
>> 
>>   Goals:
>> 
>>   o  Optimize Neighbor Discovery with a mechanism that is minimal yet
>>      sufficient for the operation in both mesh-under and route-over
>>      configurations.
>> [.]
> 
> 
> Now, if there is something amiss about the mesh-under support in RFC 6775, that would be good to know.
> 
> Grüße, Carsten
>

v2.23.0 | Report a Bug | By Email