Re: [6lowpan] [Roll] draft-bormann-ghc

Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp> Wed, 05 September 2012 23:39 UTC

Return-Path: <yoshihiro.ohba@toshiba.co.jp>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E355621F86D5 for <6lowpan@ietfa.amsl.com>; Wed, 5 Sep 2012 16:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.089
X-Spam-Level:
X-Spam-Status: No, score=-7.089 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91VZYSC8+ign for <6lowpan@ietfa.amsl.com>; Wed, 5 Sep 2012 16:39:14 -0700 (PDT)
Received: from imx12.toshiba.co.jp (imx12.toshiba.co.jp [61.202.160.132]) by ietfa.amsl.com (Postfix) with ESMTP id D725D21F86C3 for <6lowpan@ietf.org>; Wed, 5 Sep 2012 16:39:13 -0700 (PDT)
Received: from arc11.toshiba.co.jp ([133.199.90.127]) by imx12.toshiba.co.jp with ESMTP id q85Nd9UL029900; Thu, 6 Sep 2012 08:39:09 +0900 (JST)
Received: (from root@localhost) by arc11.toshiba.co.jp id q85Nd9cC023054; Thu, 6 Sep 2012 08:39:09 +0900 (JST)
Received: from ovp11.toshiba.co.jp [133.199.90.148] by arc11.toshiba.co.jp with ESMTP id JAA23053; Thu, 6 Sep 2012 08:39:09 +0900
Received: from mx.toshiba.co.jp (localhost [127.0.0.1]) by ovp11.toshiba.co.jp with ESMTP id q85Nd9gQ002108; Thu, 6 Sep 2012 08:39:09 +0900 (JST)
Received: from tsbpoa.po.toshiba.co.jp by toshiba.co.jp id q85Nd8aS009467; Thu, 6 Sep 2012 08:39:08 +0900 (JST)
Received: from [133.196.20.88] by mail.po.toshiba.co.jp (Sun Java System Messaging Server 6.1 HotFix 0.05 (built Oct 21 2004)) with ESMTPA id <0M9W003IKHP8T510@mail.po.toshiba.co.jp>; Thu, 06 Sep 2012 08:39:08 +0900 (JST)
Date: Thu, 06 Sep 2012 08:39:12 +0900
From: Yoshihiro Ohba <yoshihiro.ohba@toshiba.co.jp>
In-reply-to: <4AD1F4B9-4CBB-4A7A-927B-B99D67A3AE2E@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
Message-id: <5047E2A0.8070302@toshiba.co.jp>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 8BIT
References: <18113.1339529290@marajade.sandelman.ca> <FA27D934-E3D9-4D1D-A110-DE7B47F82B2A@yahoo.fr> <CABONVQb5G=9RhpStqa-E6ohz1SLUsxAhvVytBN7emvXXjLU8hA@mail.gmail.com> <87AC724B-DC1F-41C2-9F1F-4357FA7B45A3@tzi.org> <31218.1345834358@sandelman.ca> <94E510D0-CFD3-45D5-BB4B-081A27D6AA4E@tzi.org> <5046E036.1070704@toshiba.co.jp> <4DF53A33-9BAE-4344-8108-4F789D54CCA6@tzi.org> <504707DF.4090504@toshiba.co.jp> <4AD1F4B9-4CBB-4A7A-927B-B99D67A3AE2E@tzi.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:14.0) Gecko/20120713 Thunderbird/14.0
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] [Roll] draft-bormann-ghc
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Sep 2012 23:39:15 -0000

Hi Carsten,

(2012/09/05 17:13), Carsten Bormann wrote:
> because 11nnnkkk turns into 11****** -- this loses visual access to the bit allocation.
>
> Again, this is all about the exposition, not about the technical content of the proposal, so I'm not sure we need good consensus on what is the best style (we only need to make sure there is no potential for misinterpretation).
>

I don't care if this is technical and editorial, but I do care the 
quality of IETF specification.  Honestly I think the current 
representation is too loose, and I am afraid you would get the same 
comment from others.  If you think *** representation loses visual 
access to the bit allocation, there can be other ways of 
representation such as "| 1| 1|n0|n1|n2|k0|k1|k2|".

This is something to think about for general readers..

Thanks you,
Yoshihiro Ohba


> Grüße, Carsten