IETF Logo Mail Archive

[6lowapp] BOF proposal: update

Carsten Bormann <cabo@tzi.org> Thu, 24 September 2009 07:38 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: 6lowapp@core3.amsl.com
Delivered-To: 6lowapp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E40723A6955 for <6lowapp@core3.amsl.com>; Thu, 24 Sep 2009 00:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.114
X-Spam-Level:
X-Spam-Status: No, score=-6.114 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3eaybV8Xfhcr for <6lowapp@core3.amsl.com>; Thu, 24 Sep 2009 00:38:06 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id 1F3013A699C for <6lowapp@ietf.org>; Thu, 24 Sep 2009 00:38:05 -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 n8O7d4vP014710 for <6lowapp@ietf.org>; Thu, 24 Sep 2009 09:39:04 +0200 (CEST)
Received: from [192.168.217.101] (p5489ED79.dip.t-dialin.net [84.137.237.121]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id D8BA5BD68; Thu, 24 Sep 2009 09:39:03 +0200 (CEST)
Message-Id: <334E7C18-7C0B-4BC3-ADE9-9D30FBA0F7D7@tzi.org>
From: Carsten Bormann <cabo@tzi.org>
To: 6lowapp@ietf.org
In-Reply-To: <D9BF98E0-72D4-49BA-9542-3264EE96F8E8@tzi.org>
Content-Type: multipart/mixed; boundary="Apple-Mail-6-592835932"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 24 Sep 2009 09:39:02 +0200
References: <D9BF98E0-72D4-49BA-9542-3264EE96F8E8@tzi.org>
X-Mailer: Apple Mail (2.936)
Subject: [6lowapp] BOF proposal: update
X-BeenThere: 6lowapp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Application protocols for constrained nodes and networks <6lowapp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowapp>
List-Post: <mailto:6lowapp@ietf.org>
List-Help: <mailto:6lowapp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowapp>, <mailto:6lowapp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Sep 2009 07:38:08 -0000

We used the last week to discuss the BOF proposal with our responsible
AD and with people from other standards groups.

The result is a revised BOF proposal, that already provides an outline
for the charter of the new WG.  This charter now defines a more
specific focus for the WG til the end of 2010.  I think that is good
because the IETF is much better in handling focused, specific work
items than in grand, boil-the-ocean efforts.  If we succeed, we can
always recharter to attack additional items.

A bit more background: The goal of this BOF proposal is to get a BOF
going in Hiroshima, the week of Nov 9.  The goal of the BOF is to
demonstrate that we have enough interest ("energy") and enough focus
to solve a credible problem in a defined amount of time; this will
enable us to charter a WG following the BOF.  Not all of you will be
physically present in Hiroshima; that's another reason why it is
important to hear your opinions on this mailing list.  The charter
proposal can and will change until Hiroshima, and now is the time to
influence it and to express your support.  Also, the IETF is generally
driven by Internet-Draft documents, so it would be good to hear on the
list what you will be able to contribute.

I'm looking forward to your feedback.

Gruesse, Carsten





      
    

    

 




             


      

        
      

          
    
 

    


 

    



    






    

    


    
  
    
  

      
v2.23.0 | Report a Bug | By Email