Re: [6tisch] plugfest synchronization point 1

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Sat, 08 February 2014 08:26 UTC

Return-Path: <pthubert@cisco.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 C30BD1ADF26 for <6tisch@ietfa.amsl.com>; Sat, 8 Feb 2014 00:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.435
X-Spam-Level:
X-Spam-Status: No, score=-14.435 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, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, 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 HM4d6u0Ogkwt for <6tisch@ietfa.amsl.com>; Sat, 8 Feb 2014 00:26:12 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id C7CAB1ADF23 for <6tisch@ietf.org>; Sat, 8 Feb 2014 00:26:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23856; q=dns/txt; s=iport; t=1391847972; x=1393057572; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=eC5mOcscf7mwGCR1lImna0P2sIaURgawlFdqUgmgT2s=; b=Md7DCCKqT197KQ+KdaI8Q31RtKUVWRNReE/wNOX610CCJX6NyYdyaeC4 o8KFZPQSwSOEfnoSDCMpsjyulBgHOtFQvB1MoAB9XFkVPTEHNrzqD36Xn 2AYlvxt9Bifx2nEHs+DhUYLGkkFW+D0rOlEQyEpBEFPcZqcllbn/6KpsL I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAGAG3p9VKtJXG8/2dsb2JhbABZDoI6RDhXtl2IFE+BCRZ0giUBAQEEAQEBKkELEAIBCA4DAQMBAQsWBwchBgsUAwYIAgQBDQUIAYdoAxENw2sNiEYXjGaBPwodLQQGAYMkgRQEiRGLMYF9gx6LLIVDgm4/gWhC
X-IronPort-AV: E=Sophos; i="4.95,805,1384300800"; d="scan'208,217"; a="302728668"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 08 Feb 2014 08:26:10 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s188QAci011003 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 8 Feb 2014 08:26:10 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.57]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Sat, 8 Feb 2014 02:26:09 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Xavier Vilajosana <xvilajosana@eecs.berkeley.edu>, Thomas Watteyne <watteyne@eecs.berkeley.edu>
Thread-Topic: [6tisch] plugfest synchronization point 1
Thread-Index: AQHPJJn8HzZDHVUTCUuD+IyEK0LfdJqq+x1Q
Date: Sat, 08 Feb 2014 08:26:08 +0000
Deferred-Delivery: Sat, 8 Feb 2014 08:25:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD841704295@xmb-rcd-x01.cisco.com>
References: <CALEMV4Yr9GOn7JrhA0eQ6aRbxmq_8GuSpQ-mimFN8hHT3JhyMQ@mail.gmail.com> <E045AECD98228444A58C61C200AE1BD8416FFBA0@xmb-rcd-x01.cisco.com> <CADJ9OA-izdiy6rH4u1rr=P9UcGeQpnadbJifv=4tB0-ERT_Pbg@mail.gmail.com> <CAMsDxWTcUmEPMkTYV6i0vAAwHSvWLoAVA=fc3w7V7wLy-ZhCKA@mail.gmail.com>
In-Reply-To: <CAMsDxWTcUmEPMkTYV6i0vAAwHSvWLoAVA=fc3w7V7wLy-ZhCKA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.219.199]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD841704295xmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: Christian Huitema <huitema@microsoft.com>, "6tisch@ietf.org" <6tisch@ietf.org>, "dthaler@microsoft.com" <dthaler@microsoft.com>
Subject: Re: [6tisch] plugfest synchronization point 1
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: Sat, 08 Feb 2014 08:26:16 -0000

Hello Xavi:

As you figured correctly, the data plane will be standard L2 forwarding between any PC connected to the switch and, in this case, the SBC(s).

The demo shows how pure control plane operations based on IPv6 ND ( RFC 6775 and proxy RFC 4861) can be used to enable a multilink subnet operation regardless of the details of the wireless IPv6 route-over mesh that is connected to the switch, and which in this demo will be based on Linear's SmartMesh IP. This characteristic is key to enable a smooth integration of existing and deployed technologies with upcoming 6TiSCH systems.

One good side item would be to document point by point why the objections in RFC 4903 do not apply in the 6TiSCH use case, and to most IoT use cases for that matter.

Another would be to revive http://tools.ietf.org/html/draft-thaler-ipngwg-multilink-subnet, explaining why and how we can build an hybrid of the two methods that are specified in the draft to form huge ML subnets for IoT applications such as described in http://www.ietf.org/id/draft-ietf-roll-rpl-industrial-applicability-02.txt .

Cheers,

Pascal

From: xvilajosana@gmail.com [mailto:xvilajosana@gmail.com] On Behalf Of Xavier Vilajosana
Sent: samedi 8 février 2014 07:50
To: Thomas Watteyne
Cc: Pascal Thubert (pthubert); 6tisch@ietf.org
Subject: Re: [6tisch] plugfest synchronization point 1

Hi Thomas,

that would be really impressive. As far as I understand the SBC will handle NS management and 6LoWPAN compaction and will be connected through ethernet to the Cisco router on one side and to one Smart Mesh IP manager in the other. Right?

thanks for the update!
X

2014-02-07 19:04 GMT+01:00 Thomas Watteyne <watteyne@eecs.berkeley.edu<mailto:watteyne@eecs.berkeley.edu>>:
Xavi,

As discussed during the call today, the contribution to the plugfest of Linear Technology's (through its Dust Networks product group) will be to demonstrate end-to-end connectivity between an Internet host and a low-power node based running a protocol stack based on IEEE802.15.4e and 6LoWPAN.

This demonstration is in collaboration with Cisco. Specifically, we will interconnect a low-power mesh (based on Linear's SmartMesh IP product line) to the 6LoWPAN-ND-capable Cisco switch described by Pascal. Interconnection will be done through an SBC in charge of 6LoWPAN compaction.

Data coming "down" from the Internet will go through the switch which handles ND, the SBC taking care of 6LoWPAN compaction, and into the SmartMesh IP low-power mesh. Data going "up" takes the inverse route.

As discussed during the call, time permitting, we can put together 1-2 slides with an overview of the architecture and technology demonstrated for the next call.

Thomas

On Thu, Feb 6, 2014 at 11:53 PM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Xavi:

Cisco's contribution to the plugfest will be a demo of the backbone router functionality as presented at IETF 86 in Orlando, limited to the 6LoWPAN ND registration (RFC 6775).
I will have a sneak preview of efficient ND support (WiND) for those interested. The code will run on an IE3K industrial switch. The idea is to interface with one or more 6TiSCH root node(s) over Ethernet.

In order to connect to the switch acting as backbone router, the root node will need to implement RFC 6775 or WiND to advertise (towards the switch) any device that it learns (e.g. through RPL DAO) from the 15.4e TSCH side.

The root will use its own MAC address (the address on the Ethernet connection to the switch) as SLLA in the registration, but present a real unique identifier for each device in the 64-bit unique ID that it will need to infer in some fashion (sadly RPL is missing the unique ID, but if all the addresses are based on EUI 64 then that can be done in a trivial fashion). The dependency is that a same device claiming a same address must always appear with the same unique ID, otherwise the registration may be rejected as duplicate if it happens within lifetime.

The IE3K switch will act as 6LR on its SVI interface, and register the device. It will also defend the IPv6 address of the device on the Ethernet side using the root MAC address (the SLLA in the NS(ARO)).
As such, the demo will implement http://tools.ietf.org/html/draft-thubert-6lowpan-backbone-router-03#section-5.2 "ND Proxy Operations" and will enable a PC connected over Ethernet to ping a 6TiSCH device effectively forming a single heterogeneous multilink subnet.

So far, we are in line with the plan. Anyone interested to connect is certainly welcome!

Cheers,

Pascal

From: 6tisch [mailto:6tisch-bounces@ietf.org<mailto:6tisch-bounces@ietf.org>] On Behalf Of Xavier Vilajosana Guillen
Sent: jeudi 6 février 2014 21:34
To: 6tisch@ietf.org<mailto:6tisch@ietf.org>
Subject: [6tisch] plugfest synchronization point 1

Dear all,

we reached the first synchronization point. I would like to call to plugfest participants to provide a very quick status update and raise any possible problem during the 6TiSCH call tomorrow. We will have some minutes during the call to talk about that and start some planning.

regards,
Xavi

_______________________________________________
6tisch mailing list
6tisch@ietf.org<mailto:6tisch@ietf.org>
https://www.ietf.org/mailman/listinfo/6tisch