[core] draft-thubert-6lo-routing-dispatch-06
peter van der Stok <stokcons@xs4all.nl> Mon, 21 September 2015 08:19 UTC
Return-Path: <stokcons@xs4all.nl>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE8B1A8969 for <core@ietfa.amsl.com>; Mon, 21 Sep 2015 01:19:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.449
X-Spam-Level:
X-Spam-Status: No, score=0.449 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35, 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 DEXY2LVllcja for <core@ietfa.amsl.com>; Mon, 21 Sep 2015 01:19:36 -0700 (PDT)
Received: from lb1-smtp-cloud3.xs4all.net (lb1-smtp-cloud3.xs4all.net [194.109.24.22]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3960A1A8940 for <core@ietf.org>; Mon, 21 Sep 2015 01:19:36 -0700 (PDT)
Received: from webmail.xs4all.nl ([194.109.20.204]) by smtp-cloud3.xs4all.net with ESMTP id KkKZ1r00E4QBLo201kKZ7K; Mon, 21 Sep 2015 10:19:34 +0200
Received: from AMontpellier-654-1-72-200.w90-0.abo.wanadoo.fr ([90.0.47.200]) by webmail.xs4all.nl with HTTP (HTTP/1.1 POST); Mon, 21 Sep 2015 10:19:33 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Date: Mon, 21 Sep 2015 10:19:33 +0200
From: peter van der Stok <stokcons@xs4all.nl>
To: Pthubert <pthubert@cisco.com>, Core <core@ietf.org>
Organization: vanderstok consultancy
Mail-Reply-To: consultancy@vanderstok.org
Message-ID: <fbc936d126a03001ac3f3a58b47a6f40@xs4all.nl>
X-Sender: stokcons@xs4all.nl (d6CUrwhRG7oKZ495fOjExNb5jjekmPyp)
User-Agent: XS4ALL Webmail
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/-VheMrxxeLqMEh5ZT6SO40QHbmg>
Subject: [core] draft-thubert-6lo-routing-dispatch-06
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: consultancy@vanderstok.org
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Sep 2015 08:19:38 -0000
Hi Pascal, I read your draft, and was pleased to see that I seem to understand much better what is going on. However, I got confused by your use of dispatch. In RFC 4944, dispatch represents the last 6 bits of the dispatch header. In the routing-dispatch draft, dispatch seems to refer to whole dispatch header (pattern). Is that correct, or do I miss something? Or am I nit-picking the obvious? In addition, the note just before section 3.1 did not help me much. Other NIT: end of page 3: 19 bits -> 19 bytes Greetings, Peter -- Peter van der Stok mailto: consultancy@vanderstok.org www: www.vanderstok.org tel NL: +31(0)492474673 F: +33(0)966015248
- [core] draft-thubert-6lo-routing-dispatch-06 peter van der Stok
- Re: [core] draft-thubert-6lo-routing-dispatch-06 Carsten Bormann
- Re: [core] draft-thubert-6lo-routing-dispatch-06 Robert Cragie