[Roll] FW: New Non-WG Mailing List: 6lo -- Mailing list for discussion of a WG for Internet Area issues in IPv6 over constrained node networks

"Adrian Farrel" <adrian@olddog.co.uk> Fri, 24 May 2013 20:44 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B0411E8123 for <roll@ietfa.amsl.com>; Fri, 24 May 2013 13:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.318
X-Spam-Level:
X-Spam-Status: No, score=-2.318 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyHTzeJcpc2x for <roll@ietfa.amsl.com>; Fri, 24 May 2013 13:44:13 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 2E28211E811F for <roll@ietf.org>; Fri, 24 May 2013 13:44:13 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4OKiBAc031520 for <roll@ietf.org>; Fri, 24 May 2013 21:44:11 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4OKiB9W031514 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <roll@ietf.org>; Fri, 24 May 2013 21:44:11 +0100
From: Adrian Farrel <adrian@olddog.co.uk>
To: roll@ietf.org
References: <20130524181840.1900.71091.idtracker@ietfa.amsl.com>
In-Reply-To: <20130524181840.1900.71091.idtracker@ietfa.amsl.com>
Date: Fri, 24 May 2013 21:44:10 +0100
Message-ID: <076801ce58bf$71a3ef90$54ebceb0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHfMyEURbVWo19YoVjJssmeULhbWZjzF8Gw
Content-Language: en-gb
Subject: [Roll] FW: New Non-WG Mailing List: 6lo -- Mailing list for discussion of a WG for Internet Area issues in IPv6 over constrained node networks
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk, Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 20:44:18 -0000

FYI

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of IETF Secretariat
> Sent: 24 May 2013 19:19
> To: IETF Announcement List
> Cc: cabo@tzi.org; rdroms.ietf@gmail.com; 6lo@ietf.org
> Subject: New Non-WG Mailing List: 6lo -- Mailing list for discussion of a WG for
> Internet Area issues in IPv6 over constrained node networks
> 
> 
> A new IETF non-working group email list has been created.
> 
> List address: 6lo@ietf.org
> Archive: http://www.ietf.org/mail-archive/web/6lo/
> To subscribe: https://www.ietf.org/mailman/listinfo/6lo
> 
> Purpose: Since it was set up in 2005, the 6LoWPAN WG has created specifications
> for building IPv6 networks out of devices that use the IEEE 802.15.4
> wireless network standard. This work has culminated in the recent
> publication of RFC 6775, 6LoWPAN-ND, and the 6LoWPAN WG is shutting down.
> 
> This does not mean the work in this space is done. Indeed, 6LoWPAN
> produced one more document that isn't even about 802.15.4:
> draft-ietf-6lowpan-btle-12.txt, the equivalent of 6LoWPAN for the low
> energy mode of the Bluetooth 4.0 specification, is now in IESG
> processing, waiting for the assignment of a number from the Bluetooth
> SIG. A number of related drafts want to apply 6LoWPAN technology to
> other constrained node network layer 2 specifications:
> 
> -- draft-brandt-6man-lowpanz-00.txt
> -- draft-ietf-6man-6lobac-01.txt
> -- draft-mariager-6lowpan-v6over-dect-ule-02.txt
> 
> Also, some additional specifications are generally regarded as useful
> complements of the existing 6LoWPAN work:
> 
> -- draft-schoenw-6lowpan-mib-03.txt
> -- draft-bormann-6lowpan-ghc-05.txt
> -- draft-kelsey-intarea-mesh-link-establishment-05.txt
> -- draft-bormann-6lowpan-roadmap-03.txt
> 
> Beyond that, some older proposals that the 6LoWPAN WG has not picked
> up are receiving new attention:
> 
> -- draft-thubert-6lowpan-backbone-router-03.txt
> -- draft-thubert-roll-forwarding-frags-01.txt
> 
> Finally, there are some architectural issues raised by 6LoWPAN's use
> of adaptation layer fragmentation on top of a lossy radio:
> 
> -- draft-bormann-intarea-alfi-02.txt
> 
> As can be seen, these drafts have been addressed to a zoo of working
> groups, including the sunsetting 6LoWPAN WG, the 6MAN WG, INTAREA, and
> even ROLL, with the addressed WG often changing over the lifetime of a
> draft. It is probably more productive to focus most of this closely
> related work on a specific WG.
> 
> One clear candidate is the 6man WG. However, that WG has a number of
> other duties in maintaining IPv6 that make it subscribing to its
> mailing list too onerous to the group of experts interested in
> constrained node networking. It is probably worth separating out the
> 6man-related work that focuses on constrained node networks. There
> are, however, architectural aspects that are indeed best left in 6man
> or even INTAREA. The 6Lo mailing list has been set up to organize the
> discussion of a charter for a potential working group that focuses on
> IP-over-foo standardization (adaptation layers) for constrained node
> networks, working closely with the INT area working groups and other
> IETF WGs focused on constrained node networks.
> 
> For additional information, please contact the list administrators.