IETF Logo Mail Archive

Re: [6tisch] CoAP resource management - draft-ietf-6tisch-coap-02

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 11 November 2014 20:31 UTC

Return-Path: <mcr@sandelman.ca>
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 460771A2119 for <6tisch@ietfa.amsl.com>; Tue, 11 Nov 2014 12:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.495
X-Spam-Level:
X-Spam-Status: No, score=-2.495 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.594, 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 5rOhUpZDXnyG for <6tisch@ietfa.amsl.com>; Tue, 11 Nov 2014 12:31:09 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4271A1AB7 for <6tisch@ietf.org>; Tue, 11 Nov 2014 12:31:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 94A6120098; Tue, 11 Nov 2014 15:33:12 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 44AD9637F4; Tue, 11 Nov 2014 15:31:08 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 2C857637EA; Tue, 11 Nov 2014 15:31:08 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Raghuram Sudhaakar (rsudhaak)" <rsudhaak@cisco.com>, "6tisch@ietf.org" <6tisch@ietf.org>
In-Reply-To: <D0876D12.C03C%rsudhaak@cisco.com>
References: <D0876D12.C03C%rsudhaak@cisco.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 11 Nov 2014 15:31:08 -0500
Message-ID: <32412.1415737868@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/6tisch/MnJyjm8AFhafQkDLLn86GizbU1M
Subject: Re: [6tisch] CoAP resource management - draft-ietf-6tisch-coap-02
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, 11 Nov 2014 20:31:10 -0000

Raghuram Sudhaakar (rsudhaak) <rsudhaak@cisco.com> wrote:
    > The third and most important discussion was - 3. How do nodes exchange
    > the version data (with PCE and other nodes) of nodes so a network of
    > heterogenous nodes (w.r.t version) can interoperate.  1. Proposal - use
    > the joining flows defined in draft-richardson-6tisch--security-6top-03

    > Comments and suggestions on this proposal are requested.

I don't understand why you talk about "version data"?
How are the nodes heterogenous?  I suspect that I might be suffering from
unshared terminology here.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email