Re: [6lo] Fwd: [Technical Errata Reported] RFC4944 (4359)

Jonathan Hui <jonhui@nestlabs.com> Sat, 30 May 2015 00:59 UTC

Return-Path: <jonhui@nestlabs.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50CCD1A9091 for <6lo@ietfa.amsl.com>; Fri, 29 May 2015 17:59:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 7zbwMKPmnL96 for <6lo@ietfa.amsl.com>; Fri, 29 May 2015 17:59:23 -0700 (PDT)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27FB61ACE10 for <6lo@ietf.org>; Fri, 29 May 2015 17:59:19 -0700 (PDT)
Received: by qcbhb1 with SMTP id hb1so32756974qcb.1 for <6lo@ietf.org>; Fri, 29 May 2015 17:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nestlabs.com; s=google; h=mime-version:date:message-id:subject:from:to:content-type; bh=Zi0QZEZc7sJ3RI+C4EBIj+iRhyi3ZgcQCKjaCzQew8A=; b=PEuVQb3ofma50aTA04T8AiK5KCuEmn+qcvqOguPf5WZ/L30BIkPy55Y6SIHXVkxnUu +Zbi9obgQShXIfLnis7Z8Y4haMSSs71FMdxW43YLUffx9eNSxPNF7FXBA7XGqJ+zqkzz H+FXeEKaOrFD43b49P+NM0ge6TvssylmD43Dc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=Zi0QZEZc7sJ3RI+C4EBIj+iRhyi3ZgcQCKjaCzQew8A=; b=RgHGHLnMx8f0fk69xmJiMQBQFK7NT34LXhN1VF9kmDGX5PRGJ5slfKF4+hiNnAnJNS iqU4PeaJ1qpkz0l+GH2ajZyKD43eXT1Kjn8qVWw78RGji+2ayIKP39q9Sk/tbbJvqFyf +QfsLJKgd7fHqVu4vD/A2dnjVHIAp4mte5ChUQwRAIN2CCfpYD9pQ3Pkip+K1/jAohvu YqWtv5Pqjf514jIN4xbnju01sbifL+6YU67cuVpyW5bxTTErMXk0RVYmXKsGeQtDO02t 5mQVvxDMaZwwUdHxEOZdVjcd6q4aPRI9jqQX5cVm+EYMq/Hsn7sYHiMRg3p2zo4CCA5p TFeg==
X-Gm-Message-State: ALoCoQkRVe0PCIQq+BLawDWr7K+ql2A7nu+rXl1G+bVR26XwiorM/9+gh1vTqJYVnyCfD78xItxZ
MIME-Version: 1.0
X-Received: by 10.140.150.198 with SMTP id 189mr13550621qhw.88.1432947558274; Fri, 29 May 2015 17:59:18 -0700 (PDT)
Received: by 10.96.73.195 with HTTP; Fri, 29 May 2015 17:59:18 -0700 (PDT)
Date: Fri, 29 May 2015 17:59:18 -0700
Message-ID: <CAO6tK45jVMp=fC_RL6jZoQ=F4fL3GKuXOcG9u036Xsc0smVMDA@mail.gmail.com>
From: Jonathan Hui <jonhui@nestlabs.com>
To: "6lo@ietf.org" <6lo@ietf.org>
Content-Type: multipart/alternative; boundary="001a113569e23179b80517421a44"
Archived-At: <http://mailarchive.ietf.org/arch/msg/6lo/D86yXWPuSRIKpLMzyP8aAZNBsHE>
Subject: Re: [6lo] Fwd: [Technical Errata Reported] RFC4944 (4359)
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 May 2015 01:00:58 -0000

I believe the Erratum under discussion is correct and should be marked as
Verified.

The original intent of "Dispatch value" was:
1) To refer to the Dispatch field in the Dispatch Header - note the
capitalization in "Allows support for Dispatch values larger than 127."
2) To identify a namespace that *excludes* the Mesh Addressing and
Fragmentation headers.

The original draft text (draft-ietf-6lowpan-format-07) was less ambiguous
about the original intent.  Referring to that draft:

1) The draft separated the concept of "Header Type" from "Dispatch Value".
The draft defined Header Types: Dispatch, Mesh Delivery, and Fragmentation,
and Dispatch Values: NALP, IPv6, LOWPAN_HC1, LOWPAN_BC0, and ESC.  The
draft also includes the following text that indicates the Mesh Addressing
and Fragmentation headers are not included in the dispatch value namespace:

   The definition of headers, other than mesh addressing and
   fragmentation, in LoWPAN consists of the dispatch value, the
   definition of the header fields that follow

Note that the text above still lives in RFC 4944.

2) The bit pattern figure was titled "Dispatch Type Bit Pattern", not
"Dispatch Value Bit Pattern", with the intent that the table only included
the initial allocations within the Dispatch Header and did *not* include
any mention of Mesh Delivery and Fragmentation headers.

--
Jonathan Hui