Re: [6tsch] renaming 6tus to 6top
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 05 July 2013 17:39 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 7AF4E21F9E9D for <6tsch@ietfa.amsl.com>;
Fri, 5 Jul 2013 10:39:13 -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=[AWL=-0.000,
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 tZsHebDZR2EN for
<6tsch@ietfa.amsl.com>; Fri, 5 Jul 2013 10:39:07 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72])
by ietfa.amsl.com (Postfix) with ESMTP id C410C21F9E90 for <6tsch@ietf.org>;
Fri, 5 Jul 2013 10:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com;
l=5794; q=dns/txt; s=iport; t=1373045946; x=1374255546;
h=from:to:subject:date:message-id:references:in-reply-to: mime-version;
bh=sIe0irMBK9xVMz6KihmTJi1SnJ86FixUMNw/YiPndvo=;
b=j/pGUzwZJGRuEiIJagCcvV1CCdRklOrErY2ziGTCYOtAJHECohNnHue8
pl6VB12HHgt5urwOWnfVwb+zF1mJ01T81SNmYxo2dy+7QKvJcL87Y5qgM
hQzpMDnickcsudghjwkfyaoSm18iHr0pv2v/dkjq7TN/L9J17BN61vKR1 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAOAD11GtJXG//2dsb2JhbABaDoI3RDJJwESBARZ0giMBAQEELVwCAQgRBAEBCx0HMhQJCAIEARIIiAe5HI86NwGDBGkDhUCjToJTPoIo
X-IronPort-AV: E=Sophos; i="4.87,1003,1363132800"; d="scan'208,217";
a="231198553"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by
rcdn-iport-1.cisco.com with ESMTP; 05 Jul 2013 17:39:04 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75])
by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r65Hd48T022299
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Fri, 5 Jul 2013 17:39:04 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.9]) by xhc-rcd-x01.cisco.com
([173.37.183.75]) with mapi id 14.02.0318.004; Fri, 5 Jul 2013 12:39:03 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "xvilajosana@eecs.berkeley.edu" <xvilajosana@eecs.berkeley.edu>,
"6tsch@ietf.org" <6tsch@ietf.org>
Thread-Topic: [6tsch] renaming 6tus to 6top
Thread-Index: AQHOeaSvuMNZSvoYMUCurMnyKZbIC5lWWT0A
Date: Fri, 5 Jul 2013 17:39:03 +0000
Deferred-Delivery: Fri, 5 Jul 2013 17:39:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD841352A28@xmb-rcd-x01.cisco.com>
References: <CALEMV4YY+ZpWCyyYSpbGNKU8FT1Z+arvfwpnmd2T5tEf=CJBFA@mail.gmail.com>
In-Reply-To: <CALEMV4YY+ZpWCyyYSpbGNKU8FT1Z+arvfwpnmd2T5tEf=CJBFA@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.87.211]
Content-Type: multipart/alternative;
boundary="_000_E045AECD98228444A58C61C200AE1BD841352A28xmbrcdx01ciscoc_"
MIME-Version: 1.0
Subject: Re: [6tsch] renaming 6tus to 6top
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, 05 Jul 2013 17:39:13 -0000
I do love the TOP, Xavi. But do we need the 6? I do not see that TOP has really anything to do with IPv6. It is actually a multiprotocol switching entity. OTOH, from the TSCH perpective, it is actually the top layer ; ) Pascal From: 6tsch-bounces@ietf.org [mailto:6tsch-bounces@ietf.org] On Behalf Of Xavier Vilajosana Guillen Sent: vendredi 5 juillet 2013 19:26 To: 6tsch@ietf.org Subject: [6tsch] renaming 6tus to 6top Dear all, after some discussion we propose to rename 6tus sublayer to 6top as "6TSCH Operation sub-layer". is there any concern on that? we would like to have an agreement asap so we can publish new revision before the 15th of July, so please let us now and if there are no concerns we will rename the draft by next Tuesday. regards, Xavi
- [6tsch] renaming 6tus to 6top Xavier Vilajosana Guillen
- Re: [6tsch] renaming 6tus to 6top Pascal Thubert (pthubert)
- Re: [6tsch] renaming 6tus to 6top Thomas Watteyne
- Re: [6tsch] renaming 6tus to 6top Abdussalam Baryun