[6lowpan] Does the 6lowpan WG want to close?

Ines Robles <mariainesrobles@googlemail.com> Sat, 16 June 2012 21:28 UTC

Return-Path: <mariainesrobles@googlemail.com>
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 4B60521F85D0 for <6lowpan@ietfa.amsl.com>; Sat, 16 Jun 2012 14:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id kBuJ3aMuNC5g for <6lowpan@ietfa.amsl.com>; Sat, 16 Jun 2012 14:28:31 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 4E75621F85CF for <6lowpan@ietf.org>; Sat, 16 Jun 2012 14:28:31 -0700 (PDT)
Received: by obbwc20 with SMTP id wc20so5471951obb.31 for <6lowpan@ietf.org>; Sat, 16 Jun 2012 14:28:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=df7t2A41rfdEBZ3ceg+NhFeYLwB6sKOGvST/cgF7cFw=; b=WNoJvUi6XY7zpz4ok/mdUSLZTFaeDClYjqKeHiZ+8TDzvoAKOQapCoqhhbFwhogpfY i7mrNPvt+/x1ZE4C1U+KKDiKzcU4lEBd4HqE8YE76k2wyBV4q0xGgYILhUFpnm42z56M I/Um1UmXu40QsDYoPxT4bcQnd7a1CUyTX4Kuj+uDQGrOieuY1ZrFXjdmiQOz5sAKZjcE Prwb4WghHnMhd5bLTUSijNzA0B1XPZCXn9qW1ZVyXfyHUVjh0sZTHuTElPXdZUGLn2Kl nbu/+B4tjyML64Jz0c3WoYRadF/YfbIBlyU7nsABi5Ji3xDQI3pYqZq2HLTeHkv2eB3g mIiQ==
MIME-Version: 1.0
Received: by with SMTP id q7mr10486447oef.50.1339882110926; Sat, 16 Jun 2012 14:28:30 -0700 (PDT)
Received: by with HTTP; Sat, 16 Jun 2012 14:28:30 -0700 (PDT)
Date: Sat, 16 Jun 2012 18:28:30 -0300
Message-ID: <CAP+sJUdhZPXx9SxcrzSTovG85FuGh2WB=V1faUzyhyFs+Dw8Kg@mail.gmail.com>
From: Ines Robles <mariainesrobles@googlemail.com>
To: 6lowpan@ietf.org
Content-Type: multipart/alternative; boundary=e89a8ff1c4e6433f4504c29d9d70
Subject: [6lowpan] Does the 6lowpan WG want to close?
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: Sat, 16 Jun 2012 21:28:32 -0000


I am just thinking that  a new  Milestone or Goal  would be:   802.15.7
(Li-Fi)  +  6lowPAN.

What do you think about it?

Thanks and Regards,

Ines Robles.

> Hi Carsten,
> I agree that it was good to complete the tasks and solve the specific
> issues, and it may be a good reason for close, but I also think the working
> group can decide if they want to bring more tasks in and continue (I don't
> see a role in IETF to MUST close WG if completes the specific problems,
> if I am wrong please refer me to a page reference?), and if they want to
> solve other problems related to the group purpose. I think that the
> community drives works/inputs in IETF WGs.
> IMO, the IESG is only to decide to requests of open or close, after they
> get an input with reason. I don't think they are prerogative to decide the
> input and decide the output as well. IMO IESG are prerogative to decide the
> outcome. The inputs are decided by the WG, and the WG may not decide the
> outcome-result of such input. So I think if we want to request for
> continue/close we see the community input for 6Lowpan WG, then if they
> wanted to continue we input to IESG for their approval, if they want to
> close then it will be without an input request.
> There is a possibility that I don't know how the IETF works, but I read the
> IETF procedures, and see that there is no good reason for close without the
> WG consensus or input of this issue.
> Regards