[6lowpan] 6LoWPAN roadmap updated

Carsten Bormann <cabo@tzi.org> Mon, 26 March 2012 08:57 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B0F8721F84E2 for <6lowpan@ietfa.amsl.com>; Mon, 26 Mar 2012 01:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id znvw7P9jQaYv for <6lowpan@ietfa.amsl.com>; Mon, 26 Mar 2012 01:57:40 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id CA64F21F84B6 for <6lowpan@ietf.org>; Mon, 26 Mar 2012 01:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de []) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q2Q8vVrZ007254 for <6lowpan@ietf.org>; Mon, 26 Mar 2012 10:57:31 +0200 (CEST)
Received: from dhcp-9069.meeting.ietf.org (dhcp-9069.meeting.ietf.org []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 66DDE2A9; Mon, 26 Mar 2012 10:57:31 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
From: Carsten Bormann <cabo@tzi.org>
Date: Mon, 26 Mar 2012 10:52:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7AAFD95-5B2A-44E4-B90A-60A02E8B3F41@tzi.org>
References: <20120326083549.10700.80057.idtracker@ietfa.amsl.com>
To: 6lowpan@ietf.org
X-Mailer: Apple Mail (2.1257)
Subject: [6lowpan] 6LoWPAN roadmap updated
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: Mon, 26 Mar 2012 08:57:40 -0000


I have updated the 6LoWPAN roadmap document.
While the WG is still busy completing 6LoWPAN-ND and IPv6 over BT-LE, this document is intended to provide an overview over the set of "6LoWPAN" standards, how they fit together, and what rough edges must be filed off to fit them together.  Please review again at:


This document is not intended for immediate publication, but as a running working document that keeps the threads together while the specifications are being deployed.
If you have any comments or updates, I'll update it as quickly as possible.

Grüße, Carsten

> 	Title           : 6LoWPAN Roadmap and Implementation Guide
> 	Author(s)       : Carsten Bormann
> 	Filename        : draft-bormann-6lowpan-roadmap-01.txt
> 	Pages           : 14
> 	Date            : 2012-03-26
>   6LoWPAN is defined in RFC 4944 in conjunction with a number of
>   specifications that are currently nearing completion.  The entirety
>   of these specifications may be hard to understand, pose specific
>   implementation problems, or be simply inconsistent.
>   The present guide aims to provide a roadmap to these documents as
>   well as provide specific advice how to use these specifications in
>   combination.  In certain cases, it may provide clarifications or even
>   corrections to the specifications referenced.
>   This guide is intended as a continued work-in-progress, i.e. a long-
>   lived Internet-Draft, to be updated whenever new information becomes
>   available and new consensus on how to handle issues is formed.
>   Similar to the ROHC implementation guide, RFC 4815, it might be
>   published as an RFC at some future time later in the acceptance curve
>   of the specifications.
>   This document does not describe a new protocol or attempts to set a
>   new standard of any kind - it mostly describes good practice in using
>   the existing specifications, but it may also document emerging
>   consensus where a correction needs to be made.
>   The current version -01 of this document is an early draft that is
>   intended to spark the further collection of relevant information.