IETF Logo Mail Archive

Re: [6tisch] [6tisch-security] proposed security text for architecture draft

<yoshihiro.ohba@toshiba.co.jp> Tue, 18 November 2014 07:08 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
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 96A671A014E; Mon, 17 Nov 2014 23:08:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.986
X-Spam-Level:
X-Spam-Status: No, score=-4.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 UnBgjcEk9pBu; Mon, 17 Nov 2014 23:08:05 -0800 (PST)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F3BB1AD35E; Mon, 17 Nov 2014 23:08:04 -0800 (PST)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id sAI77v6w000264; Tue, 18 Nov 2014 16:07:57 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp id sAI77uYO001918; Tue, 18 Nov 2014 16:07:56 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id SAA01914; Tue, 18 Nov 2014 16:07:56 +0900
Received: from mx12.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id sAI77u9b027279; Tue, 18 Nov 2014 16:07:56 +0900 (JST)
Received: from TGXML207.toshiba.local by toshiba.co.jp id sAI77tkc026364; Tue, 18 Nov 2014 16:07:55 +0900 (JST)
Received: from TGXML210.toshiba.local ([169.254.4.146]) by TGXML207.toshiba.local ([133.199.70.16]) with mapi id 14.03.0195.001; Tue, 18 Nov 2014 16:07:56 +0900
From: yoshihiro.ohba@toshiba.co.jp
To: mcr+ietf@sandelman.ca
Thread-Topic: [6tisch-security] [6tisch] proposed security text for architecture draft
Thread-Index: AQHP/9Hsmv4jLXPqmkGCw6POgAr77Jxf0IxwgACgdYWAABePkIABiM6AgAHRfJCAAVWTAIAAxDIw
Date: Tue, 18 Nov 2014 07:07:55 +0000
Message-ID: <674F70E5F2BE564CB06B6901FD3DD78B272B89D9@TGXML210.toshiba.local>
References: <20507.1415811045@sandelman.ca> <674F70E5F2BE564CB06B6901FD3DD78B272A8EFA@TGXML210.toshiba.local> <5854.1415835364@sandelman.ca> <674F70E5F2BE564CB06B6901FD3DD78B272A9108@TGXML210.toshiba.local> <29465.1415934436@sandelman.ca> <674F70E5F2BE564CB06B6901FD3DD78B272A988F@TGXML210.toshiba.local> <2187.1415945515@sandelman.ca>, <674F70E5F2BE564CB06B6901FD3DD78B272A9AFF@TGXML210.toshiba.local> <976D1F6A-3A48-4BBB-8297-58071788A04E@cisco.com> <674F70E5F2BE564CB06B6901FD3DD78B272A9CEA@TGXML210.toshiba.local> <8608.1416111323@sandelman.ca> <674F70E5F2BE564CB06B6901FD3DD78B272B22DF@TGXML210.toshiba.local> <10985.1416284638@sandelman.ca>
In-Reply-To: <10985.1416284638@sandelman.ca>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
x-originating-ip: [133.196.20.218]
msscp.transfermailtomossagent: 103
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/6tisch/iuXq1ktFY7VDKMUMSl3e9iuLisE
Cc: pthubert@cisco.com, 6tisch@ietf.org, 6tisch-security@ietf.org
Subject: Re: [6tisch] [6tisch-security] proposed security text for architecture draft
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, 18 Nov 2014 07:08:09 -0000


-----Original Message-----
From: 6tisch-security [mailto:6tisch-security-bounces@ietf.org] On Behalf Of Michael Richardson
Sent: Tuesday, November 18, 2014 1:24 PM
To: ohba yoshihiro(大場 義洋 ○ＲＤＣ□ＮＳＬ)
Cc: pthubert@cisco.com; 6tisch@ietf.org; 6tisch-security@ietf.org
Subject: Re: [6tisch-security] [6tisch] proposed security text for architecture draft


<yoshihiro.ohba@toshiba.co.jp> wrote:
    > I am not sure if Ethernet and loopback should be considered as LLN
    > interface where mesh routing is needed.  Let's focus on a case with
    > multiple LLN radio interfaces (though such a case seems not very
    > common). 

Take two constrained devices with a generous power supply, wire ethernet between them so that the "signal" can get through that metal door/wall. 
That's the whole point of doing this all at layer 3.

[YO] OK.

    > Is a distinct routable IP address allocated to each of the multiple LLN
    > radio interfaces on a JA?  If so, relay can still work even if there
    > are multiple JNs having the same link-local address accessing via
    > different LLN radio interfaces. 

Assuming that your source route references the correct outgoing link-local address, I agree; I think we can make it work. It might be not to spec, but maybe running code should trump the spec.

[YO] Yes, that's what I meant.

Thanks,
Yoshihiro Ohba


-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email