Re: [Ieprep] Question about the IEPREP Recharting Proposal

Hannes Tschofenig <Hannes.Tschofenig@gmx.net> Sat, 29 July 2006 19:40 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6uft-0007W9-KF; Sat, 29 Jul 2006 15:40:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6ufr-0007W4-Vf for ieprep@ietf.org; Sat, 29 Jul 2006 15:40:35 -0400
Received: from mail.gmx.net ([213.165.64.21]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G6ufq-0003t0-IS for ieprep@ietf.org; Sat, 29 Jul 2006 15:40:35 -0400
Received: (qmail invoked by alias); 29 Jul 2006 19:40:33 -0000
Received: from p54987724.dip.t-dialin.net (EHLO [192.168.2.33]) [84.152.119.36] by mail.gmx.net (mp042) with SMTP; 29 Jul 2006 21:40:33 +0200
X-Authenticated: #29516787
Message-ID: <44CBB9BD.5040104@gmx.net>
Date: Sat, 29 Jul 2006 21:40:45 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Ieprep] Question about the IEPREP Recharting Proposal
References: <44B4F17B.70105@jhuapl.edu> <80703C4C-C585-4601-9518-270A3A6A49CC@cisco.com> <44C9089E.3050802@jhuapl.edu> <B8C892A4-F711-4928-8EDA-FD7E717B702F@cisco.com> <44C9160F.1060001@jhuapl.edu> <DBC1A7C7-9F3C-4557-A7BC-E081C482A5C3@cisco.com> <44C9BDAD.7020004@gmx.net> <B3DEB407-0572-438E-84F8-493F5080F239@g11.org.uk>
In-Reply-To: <B3DEB407-0572-438E-84F8-493F5080F239@g11.org.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Errors-To: ieprep-bounces@ietf.org

Rechartering is a lot simpler if first document versions are available 
and the group can look at them in order to decide whether it makes sense 
to extend the charter in a particular way.

Ciao
Hannes

ken carlberg wrote:
> Hannes,
> 
> in a nutshell, the intent of the re-charter was to go beyond  
> requirements and in some form consider solutions that do not fall  
> within the charter of other working groups.
> 
> I believe that there are some other interested parties that have been  
> working on drafts that go beyond previous work done by the group, but  
> that they are awaiting the results of the proposed rechartering  
> discussions.  However, others should probably speak up on that matter.
> 
> -ken
> 
> On Jul 28, 2006, at 3:33 AM, Hannes Tschofenig wrote:
> 
>> Hi all,
>>
>> I haven't follwed the IEPREP working group too closely in the past.  
>> This week I read through all the documents and I also went through  
>> the rechartering proposal.
>>
>> As an "outsider" I was not quite sure what exactly you would like  
>> todo? (i.e., what should the new documents cover that is not  
>> addressed in previous docs).
>> Do you have some documents that could tell me what you guys plan todo?
>> How do these documents relate to the new charter items?
>>
>> Sorry, if I appear a little bit lost...
>>
>> Ciao
>> Hannes
>>
>> _______________________________________________
>> Ieprep mailing list
>> Ieprep@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ieprep
> 
> 
> 


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep