Re: [6tsch] 6TUS vs. 6TSCH

"Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com> Wed, 03 July 2013 14:09 UTC

Return-Path: <rsudhaak@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 24EE621F8793 for <6tsch@ietfa.amsl.com>; Wed, 3 Jul 2013 07:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[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 T8fxuZ6SXECI for <6tsch@ietfa.amsl.com>; Wed, 3 Jul 2013 07:09:29 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6BF21F9691 for <6tsch@ietf.org>; Wed, 3 Jul 2013 07:09:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=22425; q=dns/txt; s=iport; t=1372860569; x=1374070169; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=ZwagSV6RG4RnaUnYRpgu2sWo1h5a0S8X4xQQKKZwQPk=; b=gsbFXeF5MXL0HCupDC+dqD4LA9A/EPtGl3LegBHIsaTR9KYjmzX2oHj/ k8/9bw2goMgmMRdvazutZ0yjDljqBvB767dYmNwDzyAeLqUPph7cHQyvK Ckto9JpnLQhcxh9TxVPM3cy4LY+FVXQCzIVLKOTLBHvnVNBgQ8+DfjGBR s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFABkw1FGtJV2a/2dsb2JhbABaDoI3RDJJwDKBAhZ0giMBAQEEAQEBawsSAQgRAQIBAQELFgcuCxQDBggCBAENBQiIBwy6bwSPOiANBAYBgwRpA4VAo06CUz6CKA
X-IronPort-AV: E=Sophos; i="4.87,988,1363132800"; d="scan'208,217"; a="230509746"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 03 Jul 2013 14:09:28 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r63E9SR7016972 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Jul 2013 14:09:28 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.56]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Wed, 3 Jul 2013 09:09:27 -0500
From: "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>
To: Maria Rita PALATTELLA <maria-rita.palattella@uni.lu>, Qin Wang <qinwang@berkeley.edu>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Thread-Topic: [6tsch] 6TUS vs. 6TSCH
Thread-Index: AQHOd/btJN/hLhOriUSV9NZ1T3BFRg==
Date: Wed, 03 Jul 2013 14:09:26 +0000
Message-ID: <2C3A8CAFDCAFCA41B8BF705CD9471C5B184D6739@xmb-rcd-x04.cisco.com>
In-Reply-To: <F085911F642A6847987ADA23E611780D1858769F@hoshi.uni.lux>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.5.130515
x-originating-ip: [10.21.91.192]
Content-Type: multipart/alternative; boundary="_000_2C3A8CAFDCAFCA41B8BF705CD9471C5B184D6739xmbrcdx04ciscoc_"
MIME-Version: 1.0
Cc: "6tsch@ietf.org" <6tsch@ietf.org>, "xvilajosana@eecs.berkeley.edu" <xvilajosana@eecs.berkeley.edu>
Subject: Re: [6tsch] 6TUS vs. 6TSCH
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: Wed, 03 Jul 2013 14:09:34 -0000

I was wondering the same as Maria Rita.

I suggest retaining 6TSCH (pronounced as Sixtus).

Or

6TS – 6 TSCH Scheduling. IMO layer is obvious and 3 syllables make remembering and saying it a lot easier. It avoids the ambiguity about management.

-raghuram

From: Maria Rita PALATTELLA <maria-rita.palattella@uni.lu<mailto:maria-rita.palattella@uni.lu>>
Date: Tuesday, July 2, 2013 10:22 PM
To: Qin Wang <qinwang@berkeley.edu<mailto:qinwang@berkeley.edu>>, "Pascal Thubert (pthubert)" <pthubert@cisco.com<mailto:pthubert@cisco.com>>
Cc: "6tsch@ietf.org<mailto:6tsch@ietf.org>" <6tsch@ietf.org<mailto:6tsch@ietf.org>>, "xvilajosana@eecs.berkeley.edu<mailto:xvilajosana@eecs.berkeley.edu>" <xvilajosana@eecs.berkeley.edu<mailto:xvilajosana@eecs.berkeley.edu>>
Subject: Re: [6tsch] 6TUS vs. 6TSCH

I do agree with Qin that 6tus does more than track operation... therefore, I would go for
--Sixtus TSCH Operation Layer --

but I have a minor concern. Shouldn't we remove TSCH? because Sixtus ( = 6TSCH) already includes it. What do you think about?

Maria Rita
________________________________
From: 6tsch-bounces@ietf.org<mailto:6tsch-bounces@ietf.org> [6tsch-bounces@ietf.org<mailto:6tsch-bounces@ietf.org>] on behalf of Qin Wang [qinwang@berkeley.edu<mailto:qinwang@berkeley.edu>]
Sent: Tuesday, July 02, 2013 5:03 PM
To: Pascal Thubert (pthubert)
Cc: 6tsch@ietf.org<mailto:6tsch@ietf.org>; xvilajosana@eecs.berkeley.edu<mailto:xvilajosana@eecs.berkeley.edu>
Subject: Re: [6tsch] 6TUS vs. 6TSCH

6TOP is good, but I prefer that it stands for  Sixtus TSCH Operation Layer, because "Sixtus Track Operation Layer" is a little bit narrower than the function of this sub-layer.

Qin


On Tue, Jul 2, 2013 at 10:35 PM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Hello Xavi:

I love the TOp.

Management, OTOH, is both a bit misleading (people expect management console, CNM type of stuff)  and a bit incomplete (missing the forwarding layer).

Cheers,

Pascal

From: Xavier Vilajosana Guillen [mailto:xvilajosana@eecs.berkeley.edu<mailto:xvilajosana@eecs.berkeley.edu>]
Sent: mardi 2 juillet 2013 15:36
To: Pascal Thubert (pthubert)
Cc: 6tsch@ietf.org<mailto:6tsch@ietf.org>
Subject: Re: [6tsch] 6TUS vs. 6TSCH

what about

6TMAN (Sixtus TSCH Management layer)
6TOP   (Sixtus Track Operation Layer or Sixtus TSCH Operation Layer)
MTSCH (Management TSCH sub layer)
6SUB    (Sixtus SubLayer)

just ideas!
X
On Tue, Jul 2, 2013 at 1:59 AM, Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
Dear all:

The funniest thing I got this far is 6TSCHNTSSL, pronounced as “60 schnitzel” (for 6TSCH TimeSlotted Sub-Layer).
But seriously we need to fix this. I was thinking that the key words I’d like to see there are:
-Cell (allocation and dispatching)
-Track (switching sublayer)

So maybe 6CATS?

Pascal

From:6tsch-bounces@ietf.org<mailto:6tsch-bounces@ietf.org> [mailto:6tsch-bounces@ietf.org<mailto:6tsch-bounces@ietf.org>] On Behalf Of Pascal Thubert (pthubert)
Sent: mardi 25 juin 2013 17:35
To: 6tsch@ietf.org<mailto:6tsch@ietf.org>
Subject: [6tsch] 6TUS vs. 6TSCH

Hello Maria-Rita:

I think we can easily beat a world record of the most ugly name. For instance try pronouncing this: 6TSCHTSSL  (for TimeSlotted Sub-Layer).

We need advice from the list:

1) what do you think of the definition below for 6TSCH (I’m perfectly happy with ità)
2) Should we rename 6TUS to avoid confusion with 6TSCH that pronounces sixtus already? If so, proposal?

Cheers,

Pascal

From: Maria Rita PALATTELLA [mailto:maria-rita.palattella@uni.lu]
Sent: mardi 25 juin 2013 11:08
To: Pascal Thubert (pthubert); xvilajosana@eecs.berkeley.edu<mailto:xvilajosana@eecs.berkeley.edu>; yoshihiro.ohba@toshiba.co.jp<mailto:yoshihiro.ohba@toshiba.co.jp>
Cc: watteyne@eecs.berkeley.edu<mailto:watteyne@eecs.berkeley.edu>
Subject: RE: [6tsch] draft-ohba-6tsch-security-00

Hello Pascal,
I do agree that 6TSCH is not well defined in the terminology draft. Sorry for that.  For sure, we need to spell out the acronym. According to what you are suggesting, and what we had before, we may update it as follows:

6TSCH: IPv6 over Time Slotted Channel Hopping. It defines a set of IETF sublayers and protocols (for setting up a schedule with a centralized or distributed approach, managing the resource allocation, etc.), as well as the architecture to bind them together, for use in IPv6  TSCH based networks.

I also agree on the confusion that comes from having 6TSCH = SIXTUS and 6TUS adaptation layer. But I am worried it is a bit late for changing…somehow people got already familiar with this terms…unless, we agree to have only 6TSCH, and call 6TUS 6TSCH adaptation layer. What do you think? Maybe it is even worst :)

Maria Rita


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


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