Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei?

Carsten Bormann <cabo@tzi.org> Wed, 28 September 2011 19:31 UTC

Return-Path: <cabo@tzi.org>
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 9735E1F0CDA for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 12:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocNov2SmHs0z for <6lowpan@ietfa.amsl.com>; Wed, 28 Sep 2011 12:31:25 -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 A1DBA1F0CF8 for <6lowpan@ietf.org>; Wed, 28 Sep 2011 12:31:24 -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 [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id p8SJY3xv005578; Wed, 28 Sep 2011 21:34:03 +0200 (CEST)
Received: from [192.168.217.112] (p5489B8D1.dip.t-dialin.net [84.137.184.209]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2A0994AF; Wed, 28 Sep 2011 21:34:03 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1244.3)
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <01A021EBB03D534AB5CE4B620B5F82D10439ED23@XMB-RCD-208.cisco.com>
Date: Wed, 28 Sep 2011 21:34:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D95370E-8D44-4A79-AF0E-80FE4905E163@tzi.org>
References: <01A021EBB03D534AB5CE4B620B5F82D10439EB0F@XMB-RCD-208.cisco.com> <5DAE3E80-0372-424F-83D9-FB8F79BA9D38@tzi.org> <01A021EBB03D534AB5CE4B620B5F82D10439ED23@XMB-RCD-208.cisco.com>
To: "Chao Zhou (czhou)" <czhou@cisco.com>
X-Mailer: Apple Mail (2.1244.3)
Cc: 6lowpan@ietf.org
Subject: Re: [6lowpan] How to ask a presentation time slot in coming IETF conf in Taipei?
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, 28 Sep 2011 19:31:25 -0000

On Sep 28, 2011, at 20:25, Chao Zhou (czhou) wrote:

> Thank you for your info. We do have a draft which is "draft-wang-6lowpan-scheduling-requirements-00". We're hoping to bring interest in this area through the presentation in the coming conference. We're planning to submit the second version soon. In this case, is that possible to make a slot?

Chao,

thanks for the pointer.
Leafing through this draft, I have two questions:

1) What is the ultimate disposition you envision for this document?
What kind of standards activity will be influenced by this set of requirements?
Or, more specifically, what is the IETF activity you envision that would have this document as its requirements set?

2) What would be the objective of a face-to-face discussion at this point?
(We don't schedule meeting slots to present things, but to achieve something.)
Given that I'm not aware of an existing IETF activity where this document would fit, a natural first step would be to first gather interest in setting up a new activity and then start work on the pertinent requirements document.

A random observation about the I-D: 
I'm not sure about the purpose of the references.

Gruesse, Carsten