Re: [L2CP] ANCP Next Steps

stefaan.de_cnodder@alcatel.be Fri, 19 May 2006 14:22 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh5sE-0002t2-ES; Fri, 19 May 2006 10:22:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh5sE-0002sx-0G for l2cp@ietf.org; Fri, 19 May 2006 10:22:38 -0400
Received: from smail.alcatel.fr ([62.23.212.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh5sB-0002cQ-Gd for l2cp@ietf.org; Fri, 19 May 2006 10:22:37 -0400
Received: from bemail06.netfr.alcatel.fr (bemail06.netfr.alcatel.fr [155.132.251.30]) by smail.alcatel.fr (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k4JEMWLw023195; Fri, 19 May 2006 16:22:32 +0200
Received: from [192.168.2.72] ([172.17.249.224]) by bemail06.netfr.alcatel.fr (Lotus Domino Release 5.0.12HF868) with ESMTP id 2006051916223039:4573 ; Fri, 19 May 2006 16:22:30 +0200
Message-ID: <446DD4A4.9010306@alcatel.be>
Date: Fri, 19 May 2006 16:22:28 +0200
From: stefaan.de_cnodder@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Haag, T" <Thomas.Haag@t-systems.com>
Subject: Re: [L2CP] ANCP Next Steps
References: <6439282641581441A36F7F6F83ED2ED20EA027@S4DE8PSAAFQ.mitte.t-com.de>
In-Reply-To: <6439282641581441A36F7F6F83ED2ED20EA027@S4DE8PSAAFQ.mitte.t-com.de>
X-MIMETrack: Itemize by SMTP Server on BEMAIL06/BE/ALCATEL(Release 5.0.12HF868 | May 16, 2005) at 05/19/2006 16:22:30, Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.12HF868 | May 16, 2005) at 05/19/2006 16:22:31, Serialize complete at 05/19/2006 16:22:31
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: l2cp@ietf.org
X-BeenThere: l2cp@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Layer 2 Control Protocol Discussion List <l2cp.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/l2cp>
List-Post: <mailto:l2cp@ietf.org>
List-Help: <mailto:l2cp-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l2cp>, <mailto:l2cp-request@ietf.org?subject=subscribe>
Errors-To: l2cp-bounces@ietf.org


Haag, T wrote:

> Mathew, Woj, Sanjay, all,
> 
> Having the outcome of the BoF session in mind we had several to do's:
> 
> 1.      To find a working group name                                    
> done
> 2.      To update and upload "Wadhwa draft"  to IETF                    
> done
> 3.      To update the charter for WG                                    
> done
> 4.      Area director's and the IESG's decision how to proceed          
> open
> 
> Facing the upcoming 66.IETF meeting and not losing to much time I think 
> we should become more concrete who (person + contact details) will 
> actively join and support the working group. DT is going to support.
> 

...and me as well!


> Revising the current version of "wahdwa draft" we need also to do some 
> editorial work. How to organize this work?
> 

I believe it was the intention to make split it up in framework and 
protocol, right?

regards,
Stefaan


> Regards
> 
> Thomas
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> L2cp mailing list
> L2cp@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2cp

_______________________________________________
L2cp mailing list
L2cp@ietf.org
https://www1.ietf.org/mailman/listinfo/l2cp