Return-Path: <rik.ribbers@sidn.nl>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id E6F171A01A5
 for <eppext@ietfa.amsl.com>; Fri, 27 Feb 2015 07:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.485
X-Spam-Level: *
X-Spam-Status: No, score=1.485 tagged_above=-999 required=5
 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545,
 HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]
 autolearn=no
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id tpx98sqsFtDJ for <eppext@ietfa.amsl.com>;
 Fri, 27 Feb 2015 07:31:18 -0800 (PST)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl
 [IPv6:2a00:d78:0:147:94:198:152:69])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id E751E1A00FB
 for <eppext@ietf.org>; Fri, 27 Feb 2015 07:31:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn-nl;
 c=relaxed/relaxed; 
 h=from:to:subject:thread-topic:thread-index:date:message-id:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-originating-ip:content-type:mime-version;
 bh=NH/LYArXmG+gIr0i2vF/7p12nUw+WsGX+DftqOyMMYU=;
 b=5ROPoVJTiEjtwz59gw4asH2/KIACUFfEGDu7D7vAmdvUZPHdYz5Ll+WwPNFXw01PSaSVb+UVALLfqlRK81VBy5DMSRAgsPg9GwPpt9sjGVJqZb4P6rsmYNStAUJOEj+ePIbiFaAhBEkLF8NTCzwh2NteqEBCrgZvboZtEhx6lUr/jcvVRC5xlsisb2zcUTKr7BnCLX2joTeAKQ47ROEbGbd3yZrOIvh5Ss8maR9oql5h4bO8uqmyt4mpOAn7FRo4FY9LaphCYynqG0glZ9KDPXhaR1B+tIn975slAjbAAff+O2jM2hY4/7E5uREicdGAa4A0PLBpxY3i0U9+kjBCyg==
Received: from kahubcasn02.SIDN.local ([192.168.2.74])
 by arn2-kamx.sidn.nl  with ESMTP id t1RFVGUC029683-t1RFVGUE029683
 (version=TLSv1.0 cipher=AES128-SHA bits=128 verify=CAFAIL)
 for <eppext@ietf.org>; Fri, 27 Feb 2015 16:31:16 +0100
Received: from KAMBX2.SIDN.local ([fe80::b1fd:88d9:e136:9655]) by kahubcasn02
 ([192.168.2.74]) with mapi id 14.03.0224.002;
 Fri, 27 Feb 2015 16:31:12 +0100
From: Rik Ribbers <rik.ribbers@sidn.nl>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: keyrelay
Thread-Index: AdBSnx272/YvP91BSD+PPZAC0ramcw==
Date: Fri, 27 Feb 2015 15:31:11 +0000
Message-ID: <C80127C588F8F2409E2B535AF968B768B9351218@kambx2.SIDN.local>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.153]
Content-Type: multipart/alternative;
 boundary="_000_C80127C588F8F2409E2B535AF968B768B9351218kambx2SIDNlocal_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/TU_4GGOugba4EpVZZfNRFv39VZY>
Subject: [eppext] keyrelay
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>,
 <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>,
 <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Feb 2015 15:31:20 -0000

--_000_C80127C588F8F2409E2B535AF968B768B9351218kambx2SIDNlocal_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

All,

I'd like to inform you that we had a lot of off mailing list discussion on =
how to proceed with the keyrelay draft. The short version is that we wish t=
o proceed with the standards track and that we accept the advice of the WG =
to go with Jim Gould's proposal on the xml structure for keyrelay.

However given the time constraint on our daily activities we cannot update =
the document before the next IETF meeting. We have planned  to publish a ne=
w version by the end of April.

Kind regards,
Rik Ribbers



--_000_C80127C588F8F2409E2B535AF968B768B9351218kambx2SIDNlocal_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"NL" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I&#8217;d like to inform you th=
at we had a lot of off mailing list discussion on how to proceed with the k=
eyrelay draft. The short version is that we wish to proceed with the standa=
rds track and that we accept the advice of
 the WG to go with Jim Gould&#8217;s proposal on the xml structure for keyr=
elay.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">However given the time constrai=
nt on our daily activities we cannot update the document before the next IE=
TF meeting. We have planned &nbsp;to publish a new version by the end of Ap=
ril.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Kind regards,<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Rik Ribbers <o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_C80127C588F8F2409E2B535AF968B768B9351218kambx2SIDNlocal_--

