From hiccup-bounces@ietf.org Tue Mar 20 08:40:26 2007
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 1HTdda-0004S8-04; Tue, 20 Mar 2007 08:40:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTddZ-0004S3-AN
	for hiccup@ietf.org; Tue, 20 Mar 2007 08:40:25 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTddY-0000ei-0r
	for hiccup@ietf.org; Tue, 20 Mar 2007 08:40:25 -0400
Received: (qmail invoked by alias); 20 Mar 2007 12:40:22 -0000
Received: from dhcp-1453.ietf68.org (EHLO [130.129.20.83]) [130.129.20.83]
	by mail.gmx.net (mp002) with SMTP; 20 Mar 2007 13:40:22 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+UTmtPDUSUni/uJaBQ7bfQccuvVJ6jR9b+HlDhfU
	QQrDVPiG39IF7Y
Message-ID: <45FFD633.3080905@gmx.net>
Date: Tue, 20 Mar 2007 13:40:19 +0100
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: hiccup@ietf.org
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: 7bac9cb154eb5790ae3b2913587a40de
Subject: [HICCUP] IEPREP Relationship
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

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



From hiccup-bounces@ietf.org Tue Mar 20 10:53:54 2007
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 1HTfiU-0000N4-4T; Tue, 20 Mar 2007 10:53:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTfiS-0000My-DD
	for hiccup@ietf.org; Tue, 20 Mar 2007 10:53:36 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HTfiN-0008JP-Jn
	for hiccup@ietf.org; Tue, 20 Mar 2007 10:53:36 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 20 Mar 2007 07:53:31 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l2KErVQw018875
	for <hiccup@ietf.org>; Tue, 20 Mar 2007 07:53:31 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com
	[128.107.191.100])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l2KErVMF005609
	for <hiccup@ietf.org>; Tue, 20 Mar 2007 14:53:31 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 07:53:30 -0700
Received: from jmpolk-wxp.cisco.com ([10.21.117.159]) by
	xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 20 Mar 2007 07:53:29 -0700
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 20 Mar 2007 09:53:26 -0500
To: hiccup@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <XFE-SJC-212BBsQwY6Y00002b5c@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 20 Mar 2007 14:53:30.0643 (UTC)
	FILETIME=[86576E30:01C76AFF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2; t=1174402411; x=1175266411;
	c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jmpolk@cisco.com;
	z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com>
	|Subject:=20test=20-=20please=20ignore |Sender:=20;
	bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=;
	b=KqwABrL4NrN+Lr3LGI95k6ZHjEJYrUWm58y2E6Ka/zTAL0TsSym6oL/6l5Ie2w4kePe04dZq
	4J3h5x56Kv665VV6ohjgDFBhdpRwY3ZZuqYhmaSRs3UVCQ4/RiLaW0WS;
Authentication-Results: sj-dkim-4; header.From=jmpolk@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2eba37fe9c77781b0ecb0a74d8c65128
Subject: [HICCUP] test - please ignore
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


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



From hiccup-bounces@ietf.org Tue Mar 20 10:59:32 2007
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 1HTfoC-0002ns-75; Tue, 20 Mar 2007 10:59:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTfoA-0002nO-Ec; Tue, 20 Mar 2007 10:59:30 -0400
Received: from smtp-bedford.mitre.org ([192.160.51.76])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HTfo5-0000c7-TY; Tue, 20 Mar 2007 10:59:30 -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
	l2KExJJL003215; Tue, 20 Mar 2007 10:59:19 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (Postfix) with ESMTP
	id 02A77BF01; Tue, 20 Mar 2007 10:59:19 -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
	l2KExIBi003201; Tue, 20 Mar 2007 10:59:18 -0400
Received: from IMCSRV4.MITRE.ORG ([129.83.20.161]) by imcfe2.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 20 Mar 2007 10:59:18 -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: Tue, 20 Mar 2007 10:59:16 -0400
Message-ID: <1DBEE96549590F4EA69B769AEE46AAD5013E737D@IMCSRV4.MITRE.ORG>
In-Reply-To: <45FFD633.3080905@gmx.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [HICCUP] IEPREP Relationship
Thread-Index: Acdq7O/wIdzV1xoCTrexDm5kfMfP5gAEZq1A
References: <45FFD633.3080905@gmx.net>
From: "King, Kimberly S." <ksking@mitre.org>
To: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>, <hiccup@ietf.org>
X-OriginalArrivalTime: 20 Mar 2007 14:59:18.0548 (UTC)
	FILETIME=[55B58540:01C76B00]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ieprep@ietf.org
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

Hannes,

IEPREP did useful work in this area but did not achieve the re-charter
process. =20
The IESG had some concerns. See=20
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.  =20

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
=20

-----Original Message-----
From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20
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=20
the work (other than what's written at=20
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



From hiccup-bounces@ietf.org Tue Mar 20 11:17:53 2007
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 1HTg5x-00025t-Oa; Tue, 20 Mar 2007 11:17:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTg5v-00024A-TE
	for hiccup@ietf.org; Tue, 20 Mar 2007 11:17:51 -0400
Received: from mailgate-internal2.sri.com ([128.18.84.104])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTg5t-0003WT-6G
	for hiccup@ietf.org; Tue, 20 Mar 2007 11:17:51 -0400
Received: from localhost (HELO mailgate-internal2.SRI.COM) (127.0.0.1)
	by mailgate-internal2.sri.com with SMTP; 20 Mar 2007 15:17:46 -0000
Received: from srimail1.sri.com ([128.18.30.11])
	by mailgate-internal2.SRI.COM (SMSSMTP 4.1.11.41) with SMTP id
	M2007032008174606860 ; Tue, 20 Mar 2007 08:17:46 -0700
Received: from [127.0.0.1] (dhcp-144f.ietf68.org [130.129.20.79])
	by mail.sri.com
	(Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with
	ESMTPA id
	<0JF700M0YJTI97H3@mail.sri.com>; Tue, 20 Mar 2007 08:17:46 -0700 (PDT)
Date: Tue, 20 Mar 2007 16:17:42 +0100
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
Subject: Re: [HICCUP] IEPREP Relationship
In-reply-to: <1DBEE96549590F4EA69B769AEE46AAD5013E737D@IMCSRV4.MITRE.ORG>
To: hiccup@ietf.org
Message-id: <45FFFB16.8070707@sri.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
References: <45FFD633.3080905@gmx.net>
	<1DBEE96549590F4EA69B769AEE46AAD5013E737D@IMCSRV4.MITRE.ORG>
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: ieprep@ietf.org
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

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



From hiccup-bounces@ietf.org Tue Mar 20 11:23:35 2007
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 1HTgBT-00040E-Jp; Tue, 20 Mar 2007 11:23:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HTgBS-000404-7a; Tue, 20 Mar 2007 11:23:34 -0400
Received: from mclniron02-ext.bah.com ([156.80.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HTgBO-0004Lp-1z; Tue, 20 Mar 2007 11:23:34 -0400
Received: from bahmail.bah.com (HELO mclnexbh02.resource.ds.bah.com)
	([156.80.7.152])
	by mclniron02-ext.bah.com with ESMTP; 20 Mar 2007 11:22:40 -0400
x-SBRS: None
X-REMOTE-IP: 156.80.7.152
X-IronPort-AV: i="4.14,304,1170651600"; 
	d="scan'208,217"; a="151217480:sNHT3276486912"
Received: from MCLNEXVS12.resource.ds.bah.com ([156.80.7.214]) by
	mclnexbh02.resource.ds.bah.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 20 Mar 2007 11:22:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [HICCUP] IEPREP Relationship
Date: Tue, 20 Mar 2007 11:21:22 -0400
Message-ID: <46E7B21EF4A45749B2432ABDCDE6FEA1018C6869@MCLNEXVS12.resource.ds.bah.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [HICCUP] IEPREP Relationship
Thread-Index: AcdrA0DFxyExdqfERQq9BFo42dLbfAAACowN
References: <45FFD633.3080905@gmx.net><1DBEE96549590F4EA69B769AEE46AAD5013E737D@IMCSRV4.MITRE.ORG>
	<45FFFB16.8070707@sri.com>
From: "Christou, Christos" <christou_chris@bah.com>
To: "Ed Jankiewicz" <edward.jankiewicz@sri.com>,
	<hiccup@ietf.org>
X-OriginalArrivalTime: 20 Mar 2007 15:22:37.0606 (UTC)
	FILETIME=[979CD460:01C76B03]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: ieprep@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============0420066203=="
Errors-To: hiccup-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0420066203==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C76B03.9764B0E3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C76B03.9764B0E3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I do not have a reference for what you describe.
However, I think the intention of today's discussion was to gauge where =
to head from here since the IEPREP did not achieve the re-charter.

________________________________

From: Ed Jankiewicz [mailto:edward.jankiewicz@sri.com]
Sent: Tue 3/20/2007 11:17 AM
To: hiccup@ietf.org
Cc: 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.=20
> 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. =20
>
> 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
>=20
>
> -----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
> =20


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



------_=_NextPart_001_01C76B03.9764B0E3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: [HICCUP] IEPREP Relationship</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.2769" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText8572 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>I do not have =
a reference for what you describe.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>However, I =
think the intention of today's discussion was to gauge where to head =
from here since the IEPREP did not achieve the =
re-charter.</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Ed Jankiewicz =
[mailto:edward.jankiewicz@sri.com]<BR><B>Sent:</B> Tue 3/20/2007 11:17 =
AM<BR><B>To:</B> hiccup@ietf.org<BR><B>Cc:</B> =
ieprep@ietf.org<BR><B>Subject:</B> Re: [HICCUP] IEPREP =
Relationship<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>I am interested in contributing to this effort, =
however I don't want to<BR>take up time rehashing the history if it can =
be avoided.&nbsp; Other than<BR>reading back through the IEPREP list, is =
there anywhere a summary of the<BR>lessons learned there?&nbsp; What =
goals should and should not be carried over<BR>to the new effort?&nbsp; =
Any contributions, notes, incipient drafts, etc.<BR>that are worth =
developing further?&nbsp;&nbsp; Pits to avoid falling =
into?<BR><BR>thanks<BR>Ed J.<BR><BR>King, Kimberly S. wrote:<BR>&gt; =
Hannes,<BR>&gt;<BR>&gt; IEPREP did useful work in this area but did not =
achieve the re-charter<BR>&gt; process.&nbsp;<BR>&gt; The IESG had some =
concerns. See<BR>&gt; <A =
href=3D"http://www1.ietf.org/mail-archive/web/ieprep/current/msg02572.htm=
l">http://www1.ietf.org/mail-archive/web/ieprep/current/msg02572.html</A>=
 and<BR>&gt; hence<BR>&gt; a BOF is needed in order to further the work =
incorporating the IESG<BR>&gt; feedback.&nbsp;&nbsp;<BR>&gt;<BR>&gt; My =
understanding is that ieprep will officially be shut-down. We =
are<BR>&gt; discussing holding a HICCUP BOF in Chicago will provide the =
starting<BR>&gt; point.<BR>&gt;<BR>&gt; =
Kimberly<BR>&gt;&nbsp;<BR>&gt;<BR>&gt; -----Original =
Message-----<BR>&gt; From: Hannes Tschofenig [<A =
href=3D"mailto:Hannes.Tschofenig@gmx.net">mailto:Hannes.Tschofenig@gmx.ne=
t</A>]<BR>&gt; Sent: Tuesday, March 20, 2007 1:40 PM<BR>&gt; To: =
hiccup@ietf.org<BR>&gt; Subject: [HICCUP] IEPREP =
Relationship<BR>&gt;<BR>&gt; Hi all,<BR>&gt;<BR>&gt; I would like to =
understand what the relationship to IEPREP is.<BR>&gt; Is there more =
information available regarding the scope and purpose of<BR>&gt; the =
work (other than what's written at<BR>&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/hiccup">https://www1.ietf.=
org/mailman/listinfo/hiccup</A>)<BR>&gt;<BR>&gt; Ciao<BR>&gt; =
Hannes<BR>&gt;<BR>&gt;<BR>&gt; =
_______________________________________________<BR>&gt; HICCUP mailing =
list<BR>&gt; HICCUP@ietf.org<BR>&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/hiccup">https://www1.ietf.=
org/mailman/listinfo/hiccup</A><BR>&gt;<BR>&gt; =
_______________________________________________<BR>&gt; HICCUP mailing =
list<BR>&gt; HICCUP@ietf.org<BR>&gt; <A =
href=3D"https://www1.ietf.org/mailman/listinfo/hiccup">https://www1.ietf.=
org/mailman/listinfo/hiccup</A><BR>&gt;&nbsp;&nbsp;<BR><BR><BR>__________=
_____________________________________<BR>HICCUP mailing =
list<BR>HICCUP@ietf.org<BR><A =
href=3D"https://www1.ietf.org/mailman/listinfo/hiccup">https://www1.ietf.=
org/mailman/listinfo/hiccup</A><BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C76B03.9764B0E3--


--===============0420066203==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0420066203==--




From hiccup-bounces@ietf.org Wed Mar 21 03:35:35 2007
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 1HTvM4-0006qz-89; Wed, 21 Mar 2007 03:35:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HTvM3-0006qm-4C
	for hiccup@ietf.org; Wed, 21 Mar 2007 03:35:31 -0400
Received: from mailgate-internal2.sri.com ([128.18.84.104])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HTvM1-0004Av-I8
	for hiccup@ietf.org; Wed, 21 Mar 2007 03:35:30 -0400
Received: from localhost (HELO mailgate-internal2.SRI.COM) (127.0.0.1)
	by mailgate-internal2.sri.com with SMTP; 21 Mar 2007 07:35:26 -0000
Received: from srimail1.sri.com ([128.18.30.11])
	by mailgate-internal2.SRI.COM (SMSSMTP 4.1.11.41) with SMTP id
	M2007032100352500061
	for <hiccup@ietf.org>; Wed, 21 Mar 2007 00:35:25 -0700
Received: from [127.0.0.1] (dhcp-4009.ietf68.org [130.129.64.9])
	by mail.sri.com
	(Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with
	ESMTPA id <0JF800MF0T2Z97U3@mail.sri.com> for hiccup@ietf.org; Wed,
	21 Mar 2007 00:35:26 -0700 (PDT)
Date: Wed, 21 Mar 2007 08:35:20 +0100
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
To: hiccup@ietf.org
Message-id: <4600E038.8020003@sri.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Thunderbird 1.5.0.10 (Windows/20070221)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [HICCUP] IPv6 saves lives
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

We hope.  If you think there is no awareness in the general public of 
this real-world need (and the arcane networking technology that may help 
meet it) check out this local (DC) news feature on "The IPv6".  Some of 
our colleagues are making a living by commercializing and promoting IPv6 
as a real-world problem solver.

http://www.myfoxdc.com/myfox/MyFox/pages/sidebar_video.jsp?contentId=2719015&version=1&locale=EN-US 



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



From hiccup-bounces@ietf.org Wed Mar 21 05:04:45 2007
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. =20

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]=20
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=20
reading back through the IEPREP list, is there anywhere a summary of
the=20
lessons learned there?  What goals should and should not be carried
over=20
to the new effort?  Any contributions, notes, incipient drafts, etc.=20
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. =20
> The IESG had some concerns. See=20
> 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.  =20
>
> 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
> =20
>
> -----Original Message-----
> From: Hannes Tschofenig [mailto:Hannes.Tschofenig@gmx.net]=20
> 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=20
> the work (other than what's written at=20
> 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
>  =20


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



From hiccup-bounces@ietf.org Wed Mar 28 16:24:43 2007
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 1HWehF-0007Oz-Vu; Wed, 28 Mar 2007 16:24:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HWehD-0007Nk-VS
	for hiccup@ietf.org; Wed, 28 Mar 2007 16:24:39 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HWeh9-0000Z7-NJ
	for hiccup@ietf.org; Wed, 28 Mar 2007 16:24:39 -0400
Received: (qmail invoked by alias); 28 Mar 2007 19:57:53 -0000
Received: from ip-90-186-88-144.web.vodafone.de (EHLO [90.186.88.144])
	[90.186.88.144]
	by mail.gmx.net (mp031) with SMTP; 28 Mar 2007 21:57:53 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19OuowgVNROnlcLyJ65pHjRA/ASKnRle6zwckkvI6
	ivV1vVQNjLulYk
Message-ID: <460AC8C0.2040505@gmx.net>
Date: Wed, 28 Mar 2007 21:57:52 +0200
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
User-Agent: Thunderbird 2.0b2 (Windows/20070116)
MIME-Version: 1.0
To: hiccup@ietf.org,  ieprep@ietf.org
References: <1DBEE96549590F4EA69B769AEE46AAD5013E72D2@IMCSRV4.MITRE.ORG>
In-Reply-To: <1DBEE96549590F4EA69B769AEE46AAD5013E72D2@IMCSRV4.MITRE.ORG>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: 
Subject: [HICCUP] SDO Emergency Service Workshop 2007
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

Hi all,

some of you might be interested in this workshop about 
citizen-to-authority emergency services:
http://www.emergency-services-coordination.info/2007/

Ciao
Hannes


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



