RE: [HICCUP] IEPREP Relationship

"King, Kimberly S." <ksking@mitre.org> Wed, 21 March 2007 09:04 UTC

Return-path: <hiccup-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTwkK-0008Q6-Gw; Wed, 21 Mar 2007 05:04:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HTwkI-0008Q0-IG for hiccup@ietf.org; Wed, 21 Mar 2007 05:04:38 -0400
Received: from smtpproxy1.mitre.org ([192.160.51.76] helo=smtp-bedford.mitre.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HTwkE-0003oF-6t for hiccup@ietf.org; Wed, 21 Mar 2007 05:04:38 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with SMTP id l2L94VZQ019673 for <hiccup@ietf.org>; Wed, 21 Mar 2007 05:04:31 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (Postfix) with ESMTP id BAE18BEFB for <hiccup@ietf.org>; Wed, 21 Mar 2007 05:04:31 -0400 (EDT)
Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id l2L94Vgu019664; Wed, 21 Mar 2007 05:04:31 -0400
Received: from IMCSRV4.MITRE.ORG ([129.83.20.161]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Wed, 21 Mar 2007 05:04:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [HICCUP] IEPREP Relationship
Date: Wed, 21 Mar 2007 05:04:29 -0400
Message-ID: <1DBEE96549590F4EA69B769AEE46AAD5013E74DA@IMCSRV4.MITRE.ORG>
In-Reply-To: <45FFFB16.8070707@sri.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [HICCUP] IEPREP Relationship
Thread-Index: AcdrAuxW72B2KeksTcyEl9sVrDJ58gAk2jOQ
References: <45FFD633.3080905@gmx.net> <1DBEE96549590F4EA69B769AEE46AAD5013E737D@IMCSRV4.MITRE.ORG> <45FFFB16.8070707@sri.com>
From: "King, Kimberly S." <ksking@mitre.org>
To: "Ed Jankiewicz" <edward.jankiewicz@sri.com>, <hiccup@ietf.org>
X-OriginalArrivalTime: 21 Mar 2007 09:04:31.0369 (UTC) FILETIME=[EFF98790:01C76B97]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc:
X-BeenThere: hiccup@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Harnessing IP for Critical Communications Using Precedence \(HICCUP\) list" <hiccup.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hiccup>, <mailto:hiccup-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hiccup>
List-Post: <mailto:hiccup@ietf.org>
List-Help: <mailto:hiccup-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hiccup>, <mailto:hiccup-request@ietf.org?subject=subscribe>
Errors-To: hiccup-bounces@ietf.org

Ed,

My view of lessons learned and pitfalls include:

Do not argue about solutions before defining the problem to be solved.

Document that problem to be solved in an internet draft, not just in
email on the list.  Also document the assumptions.

Document any relevant constraints.  If different yet relevant
environments have different constraints, document that too.  

For the work done, see the RFC's produced by checking the ieprep
charter page.  There are other related RfCs and the eventual charter
will have these references.

Kimberly


-----Original Message-----
From: Ed Jankiewicz [mailto:edward.jankiewicz@sri.com] 
Sent: Tuesday, March 20, 2007 4:18 PM
To: hiccup@ietf.org
Cc: King, Kimberly S.; Hannes Tschofenig; ieprep@ietf.org
Subject: Re: [HICCUP] IEPREP Relationship

I am interested in contributing to this effort, however I don't want to

take up time rehashing the history if it can be avoided.  Other than 
reading back through the IEPREP list, is there anywhere a summary of
the 
lessons learned there?  What goals should and should not be carried
over 
to the new effort?  Any contributions, notes, incipient drafts, etc. 
that are worth developing further?   Pits to avoid falling into?

thanks
Ed J.

King, Kimberly S. wrote:
> Hannes,
>
> IEPREP did useful work in this area but did not achieve the
re-charter
> process.  
> The IESG had some concerns. See 
> http://www1.ietf.org/mail-archive/web/ieprep/current/msg02572.html
and
> hence
> a BOF is needed in order to further the work incorporating the IESG
> feedback.   
>
> My understanding is that ieprep will officially be shut-down. We are
> discussing holding a HICCUP BOF in Chicago will provide the starting
> point.
>
> Kimberly
>  
>
> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net] 
> Sent: Tuesday, March 20, 2007 1:40 PM
> To: hiccup@ietf.org
> Subject: [HICCUP] IEPREP Relationship
>
> Hi all,
>
> I would like to understand what the relationship to IEPREP is.
> Is there more information available regarding the scope and purpose
of 
> the work (other than what's written at 
> https://www1.ietf.org/mailman/listinfo/hiccup)
>
> Ciao
> Hannes
>
>
> _______________________________________________
> HICCUP mailing list
> HICCUP@ietf.org
> https://www1.ietf.org/mailman/listinfo/hiccup
>
> _______________________________________________
> HICCUP mailing list
> HICCUP@ietf.org
> https://www1.ietf.org/mailman/listinfo/hiccup
>   


_______________________________________________
HICCUP mailing list
HICCUP@ietf.org
https://www1.ietf.org/mailman/listinfo/hiccup