Re: [6tisch] 6tisch join requirements for 6top

Kris Pister <ksjp@berkeley.edu> Tue, 25 November 2014 22:51 UTC

Return-Path: <ksjp@berkeley.edu>
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 942551A1AAB for <6tisch@ietfa.amsl.com>; Tue, 25 Nov 2014 14:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 obULFoLwOsOh for <6tisch@ietfa.amsl.com>; Tue, 25 Nov 2014 14:51:54 -0800 (PST)
Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com [209.85.192.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE4981A1AA3 for <6tisch@ietf.org>; Tue, 25 Nov 2014 14:51:53 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id w10so1464784pde.33 for <6tisch@ietf.org>; Tue, 25 Nov 2014 14:51:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+BtpmSNlE3Wz24TXBkg34p5isSypcQfvy7tClpTherw=; b=YJ9zLcpjWBKRlcxtjNV2JvtnM814Aq00CbYRnnP13euhCyya/gQzwm6f6DjCoiDaTq nu5Y4K/P/EQfIWGm+hLGapUXzqO4qBqjDM/9x8Rst/FcYegHm2RZM4YsRhakPrDrKp2B JTzEeT3CK0+4AGgT6jMhVuj26WDrVQt0RvFG3gBBx02muZD/h9NgkrSXGlFQcPYv9CY/ wgjdfWYvu5cz6SnTGtAuECPs0+bSuVR2UtMS+0WS0ZWEkrjmXwB9chxpmbD8KFnHORU8 +BviAIEdgjRdQjn9dzHHQhobVbjGkNk8hrLluLAxCtZoydNADNCjbIa0OrU//mgB2kyI 26cw==
X-Gm-Message-State: ALoCoQmE78S9g82jm0DaKkzeMxqocWKLWu2ElGN4ifE7kLg1JOTeZfGdQmh8d7jd0pja66EAibEr
X-Received: by 10.66.140.102 with SMTP id rf6mr8523301pab.1.1416955913560; Tue, 25 Nov 2014 14:51:53 -0800 (PST)
Received: from [128.32.32.89] (dhcp-32-89.EECS.Berkeley.EDU. [128.32.32.89]) by mx.google.com with ESMTPSA id yp8sm2447704pab.48.2014.11.25.14.51.52 for <6tisch@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Nov 2014 14:51:52 -0800 (PST)
Message-ID: <54750807.9070901@berkeley.edu>
Date: Tue, 25 Nov 2014 14:51:51 -0800
From: Kris Pister <ksjp@berkeley.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: 6tisch@ietf.org
References: <D0876D12.C03C%rsudhaak@cisco.com> <32412.1415737868@sandelman.ca> <D087B62D.C081%rsudhaak@cisco.com> <10653.1415740821@sandelman.ca> <CADJ9OA_LFkGDuyG_0bf=07d7cvC9FNRr5cMGTmYw2PR=g9XQHA@mail.gmail.com> <8193.1416253349@sandelman.ca> <21619.12717.53454.214321@fireball.kivinen.iki.fi> <E045AECD98228444A58C61C200AE1BD848A77CB5@xmb-rcd-x01.cisco.com> <21620.25926.119766.130028@fireball.kivinen.iki.fi>
In-Reply-To: <21620.25926.119766.130028@fireball.kivinen.iki.fi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/6tisch/Bh8FFPPckMfGmmF1g7spFvitCmk
Subject: Re: [6tisch] 6tisch join requirements for 6top
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: Tue, 25 Nov 2014 22:51:55 -0000

No, when someone defines protocol B that is not compatible with protocol 
A then
they will pick a different well-known key.  That is the whole idea.

ksjp

On 11/25/2014 3:17 AM, Tero Kivinen wrote:
> So when someone is running the protocol A and B both over the same
> default well-known key then you still have the problem...