[6tsch] Recording of WebEx 8 March 2013
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 08 March 2013 18:00 UTC
Return-Path: <pthubert@cisco.com>
X-Original-To: 6tsch@ietfa.amsl.com
Delivered-To: 6tsch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB3E421F8751 for <6tsch@ietfa.amsl.com>; Fri, 8 Mar 2013 10:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.265
X-Spam-Level:
X-Spam-Status: No, score=-11.265 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3N6Y2n5B1d7q for <6tsch@ietfa.amsl.com>; Fri, 8 Mar 2013 10:00:39 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id C294D21F862A for <6tsch@ietf.org>; Fri, 8 Mar 2013 10:00:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=39354; q=dns/txt; s=iport; t=1362765638; x=1363975238; h=from:to:subject:date:message-id:mime-version; bh=7AqpD/DX/7WRyAu/yk9ZA71vjr08T3fnsIVi1p2r2tw=; b=KjcPhJ0fvm9Lg0L8jFMGk1s/XIt3iZj7Q1MNON2n0Qfe+t0HUXEpmOlM b/F1aBuZc1mmlmub/KxM22NDK7jyR9M+ZADvekMuDUIIq2ay8ySK+9ank ZiSGBdLKoDIul+wxyTCNxjHin3ORKMog5vhuH+WqsdqTYTUX3BuPHXZY4 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQFAL0mOlGtJV2Y/2dsb2JhbAApGg6EBa5oiSYBiCyBWxZ0giwBAQEELUEdARkBAwEBCxYBBjkUAwYJAQQBEggTh3gMLrpnjlsmBwqCYGEDl3GPVIJLP4In
X-IronPort-AV: E=Sophos; i="4.84,809,1355097600"; d="scan'208,217"; a="182418691"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-9.cisco.com with ESMTP; 08 Mar 2013 18:00:38 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r28I0bpV001365 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 8 Mar 2013 18:00:37 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.152]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Fri, 8 Mar 2013 12:00:37 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>, IETF 6TSCH <6tsch@ietf.org>
Thread-Topic: Recording of WebEx 8 March 2013
Thread-Index: Ac4cJqoHrr0o9aCGQV6RNiA9Xw+CqA==
Date: Fri, 08 Mar 2013 18:00:36 +0000
Deferred-Delivery: Fri, 8 Mar 2013 18:00:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD835CF1F81@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.84.15]
Content-Type: multipart/alternative; boundary="_000_E045AECD98228444A58C61C200AE1BD835CF1F81xmbrcdx01ciscoc_"
MIME-Version: 1.0
Subject: [6tsch] Recording of WebEx 8 March 2013
X-BeenThere: 6tsch@ietf.org
X-Mailman-Version: 2.1.12
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" <6tsch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6tsch>, <mailto:6tsch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6tsch>
List-Post: <mailto:6tsch@ietf.org>
List-Help: <mailto:6tsch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6tsch>, <mailto:6tsch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Mar 2013 18:00:45 -0000
Thanks Thomas: I had an error coming from the recording so I stopped it and retried. The initial 10 minutes are thus missing but it appears that most of the meeting is available: https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=66584037&rKey=04f7d34938f3bce6 Cheers, Pascal From: 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org] On Behalf Of Thomas Watteyne Sent: vendredi 8 mars 2013 18:40 To: IETF 6TSCH Subject: [6tsch] minutes WebEx 8 March 2013 All, Notes of today's meeting below. Please correct inline and reply. Thomas --- *** Timestamps in PST. *** Present: - Herman Storey - Maria Rita Palattella - Norman Finn - Pascal Thubert - Qin Wang - Shitanshu Shah - Thomas Watteyne - Tina Tsou - Tom Phinney - Xavi Vilajosana Agenda: - Introduction to the terminology draft [10min] [Maria Rita] - Diffserv Recommendations for LLN class of traffic [5min] [Shitanshu] - http://datatracker.ietf.org/doc/draft-svshah-tsvwg-lln-diffserv-recommendations/ - Agenda for new week meetings [10min] [Pascal] - Changes in other drafts [10min] - draft-watteyne-6tsch-tsch-lln-context [Thomas] - draft-wang-6tsch-6tus [Qin] - draft-thubert-6tsch-architecture [Pascal] - Mailing list discussions [30min] - DSCPs and priorities [Thomas] - imux/mux [Qin] Minutes: - [08.04] meeting starts - [08.05] Introduction to the new terminology draft [Maria Rita] - [Pascal] This draft extends ROLL and autoconf terminology, which are included as references. - [Maria Rita] Presents slides. - [Maria Rita] draft was triggered by the fact that "link" and "path" have different meaning in TSCH and IETF parlance. - [Maria Rita] "Cell": Single element in the TSCH schedule. Replaces "link" term in TSCH. - [Maria Rita] "Bundle": A group of equivalent scheduled cells. Replaces (although not exactly) "path" term in TSCH. - [Maria Rita] Draft there to avoid confusion, we will include other terms as work progresses. - [Maria Rita] Draft will be published on Monday. - [08.14] Diffserv Recommendations for LLN class of traffic [Shitanshu] - draft at http://datatracker.ietf.org/doc/draft-svshah-tsvwg-lln-diffserv-recommendations/ - Shitanshu presents slides. - Context: this draft was presented at the last IETF meeting in Atlanta. - Goal: using Diffserv in context of LLN - Motivation: RFC4594 is well documented recommendation for traditional classes of traffic. Yet, does not cover LLN. What this draft does it: - categorize LLN - lists explicit recommendations for LLN - always keeping RFC4594 as a reference - source points to mark appropriate DSCP code point - LLN Traffic Classes identified from ROLL requirement drafts - 6 categories: alerts/alarms, control signals, deterministic control signals, Video Monitoring/feed, Query-based data, Periodic Reporting/log & software downloads. - each class characterized in terms of loss, delay and jitter. Some classes are different from RFC4594, justifying the need for this new draft. Example: deterministic control signals. - [Tom] Alerts/Alarms traffic are bursty because multiple network elements can signal the same physical events (e.g. explosion). - [Herman] You don't want to loose any alert/alarm packets - [Shitanshu] Agreed, will update draft. - [Herman] Is there a class for network management? - [Pascal] In some cases, network control needs to be the highest priority since network falls apart when no network control packets can be transmitted. - [Pascal] DSCP will play key role in packet priority. There is no DSCP for flow priority. - [Pascal] PHB means "per hop behavior" - [Shitanshu] Draft proposed code-point EF - [Herman] Why are emergency action outside of IP networks? - [Shitanshu] Other techniques are used which are not IP. - [Herman] There are IP-based solutions. Operate as dedicated network, not connected to complete Internet (non routable subnet), but use IP address. - [Shitanshu] We can remove the term IP. - [08.35] Agenda for new week meetings [Pascal] - Tuesday (Caribbean 2): - admin - we will have 5-10min during the ROLL meeting to present 6tsch - 6tsch meeting follows ROLL meeting, same room - we need to leave 15min before end to set up next meeting, so we will really only have one hour. - we will have projector, not clear whether we will be able to provide live online feed. - Goal: prepare for successful BoF in Berlin - Scope: the backbone with PCE (Path Computation Entity) and one or more LLN running 6LoWPAN, 6TSCH, RPL. - we use draft-phinney-roll-rpl-industrial-applicability as a starting point. - goals and deliverables: - informational: LLN context, architecture, terminology - new: 6tus, protocol for reserving track - adapt existing: OF for RPL, fragment forwarding (problems because don't have DSCP) - extern docs: backbone router (from 6MAN), PCE (is a WG, need to coordinate) - dependencies and liaison: - IEEE 802.1TSN (Norman) - ISA100.20 are defining arbstraction for management layer to manage the managers (e.g. blacklist channels). We could use same formats. - IoT6. European project. They use very similar architecture as ours. - Wednesday (Boca 2) - admin: - in Boca 2, which we can stay in past 1pm. - we will go over different drafts - draft-phinney-roll-rpl-industrial-applicability. - published at http://tools.ietf.org/html/draft-phinney-roll-rpl-industrial-applicability-02 - [Tom] Analysis of classifications of types of communications that occur. Applies to all automation systems, worked out over years by many people. - [Pascal] Good source of inspiration. - draft-watteyne-6tsch-tsch-lln-context - published at http://tools.ietf.org/html/draft-watteyne-6tsch-tsch-lln-context-01 - [Thomas] do not expect -02 for Orlando, but will need rewording for new terminology. - draft-wang-6tsch-6tus - [Pascal] Caution, we cannot reinvent MPLS. - [Xavi] will be published on Monday. - draft-palattella-6tsch-terminology - see presentation above - will be published on Monday. - draft-thubert-6tsch-architecture - [Pascal] will be work-in-progress for a long time, since incorporates changes/concepts from other drafts. - [Pascal] More text to follow: network synchronization, 6tus, management, etc. - [Thomas] Can be seen a index for other drafts, could serve as first draft to read when familiarizing with 6tsch. - [08.55] Priority discussion - [Thomas] We don't have much time left, so instead of starting discussion, will prepare slides for Wednesday meeting. - [Pascal] Will add slot for Wednesday meeting. - [Pascal] Pascal will meet with Shitanshu on Monday morning, Thomas will meet with Pascal on Monday evening and Tuesday. - [10.00] - [Thomas] Will be meeting stay at this time? - [Tom,Pascal] For the moment yes - [Pascal] There is not call next week because of IETF meeting. - [10.05] Meeting ends.
- [6tsch] Recording of WebEx 8 March 2013 Pascal Thubert (pthubert)