IETF Logo Mail Archive

Re: [6tsch] terminology draft: quick questions

Maria Rita PALATTELLA <maria-rita.palattella@uni.lu> Fri, 12 July 2013 14:54 UTC

Return-Path: <maria-rita.palattella@uni.lu>
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 B56E521E80A8 for <6tsch@ietfa.amsl.com>; Fri, 12 Jul 2013 07:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.948
X-Spam-Level:
X-Spam-Status: No, score=-5.948 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 1G-rrv1ifog4 for <6tsch@ietfa.amsl.com>; Fri, 12 Jul 2013 07:54:53 -0700 (PDT)
Received: from hercules.uni.lu (hercules.uni.lu [158.64.76.33]) by ietfa.amsl.com (Postfix) with ESMTP id 5124921E80A5 for <6tsch@ietf.org>; Fri, 12 Jul 2013 07:54:44 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.89,653,1367964000"; d="scan'208,217"; a="25381237"
Received: from unknown (HELO REED.uni.lux) ([10.21.2.9]) by hercules.uni.lu with ESMTP; 12 Jul 2013 16:54:43 +0200
Received: from HOSHI.uni.lux ([fe80::499:a33:4e68:4af9]) by REED.uni.lux ([fe80::31bb:b7a3:7abb:813e%10]) with mapi id 14.03.0123.003; Fri, 12 Jul 2013 16:54:42 +0200
From: Maria Rita PALATTELLA <maria-rita.palattella@uni.lu>
To: Thomas Watteyne <watteyne@eecs.berkeley.edu>, 6TSCH <6tsch@ietf.org>
Thread-Topic: [6tsch] terminology draft: quick questions
Thread-Index: AQHOfwVnZ2cJxruSjE+72feIVYU8uZlhGJNw
Date: Fri, 12 Jul 2013 14:54:42 +0000
Message-ID: <F085911F642A6847987ADA23E611780D18589773@hoshi.uni.lux>
References: <CADJ9OA8YUqyFSefpgxd7iurL-mk3sm0EEkNfmaZVkcP+jRUBNg@mail.gmail.com>
In-Reply-To: <CADJ9OA8YUqyFSefpgxd7iurL-mk3sm0EEkNfmaZVkcP+jRUBNg@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.34.0.9]
Content-Type: multipart/alternative; boundary="_000_F085911F642A6847987ADA23E611780D18589773hoshiunilux_"
MIME-Version: 1.0
Subject: Re: [6tsch] terminology draft: quick questions
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, 12 Jul 2013 14:54:57 -0000

Thomas,
Thanks for having pointed this out.
Yes, you are right. Maybe it is better we do not use link at all, for avoiding any kind of conflict.
Anyway, in the current definition, with p-to-p and multi-point I meant  respectively, a connection between node A and node B, and a connection between node A and several 1-hop neighbor (nodes B, C, D).
Maria Rita

From: 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org] On Behalf Of Thomas Watteyne
Sent: Friday, July 12, 2013 3:40 PM
To: 6TSCH
Subject: [6tsch] terminology draft: quick questions

Maria Rita,

I'm going over the (draft) terminology draft at https://bitbucket.org/6tsch/draft-palattella-6tsch-terminology/<https://bitbucket.org/6tsch/draft-palattella-6tsch-terminology/wiki/Home> , and see that the term "link" is defined as

"Single-hop connection between two or more devices. It can be dedicated (point-to-point), multi-point, broadcast."

Quick questions:
- do we want to use the term link at all. This raised some conflicts with IETF and IEEE802.15.4e terminology, and we went for "bundle" and "cell". Maybe this "link" refers to a different element?
- in the current definition, what do p-to-p and multi-point mean?

Thanks,
Thomas

v2.23.0 | Report a Bug | By Email