[eppext] New version of the Keyrelay draft
Rik Ribbers <rik.ribbers@sidn.nl> Mon, 29 June 2015 11:26 UTC
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 926401A8BC1 for <eppext@ietfa.amsl.com>; Mon, 29 Jun 2015 04:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.785
X-Spam-Level: **
X-Spam-Status: No, score=2.785 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 HCJVQsEmv3vl for <eppext@ietfa.amsl.com>; Mon, 29 Jun 2015 04:26:01 -0700 (PDT)
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 C61911A8FD3 for <eppext@ietf.org>; Mon, 29 Jun 2015 04:26:00 -0700 (PDT)
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=q73i0jrGk2gnssKEcbptjLfACqpWXH8bjyRqNjYO2h4=; b=wLXXTKoNErfQhF6G6UsTyfaBGDOI3aG58rJtBU0hEqTiD+zNWWTUp3tv12RqUXk5ZXhJ3rt868JjfA+rzyZvCihITPzvyEVTZdF/GxznyZluEWNeAv0fsg0O6nDQknH8BbbBOD2cWGyZLIM+bUZH0FZkOHEIdMJUJNktR2yr7px0oZMlr/H5CsMYoUcRDTWRf6TavkMwlK0i18gJwEZbYGEm8DTzXgBKGJIFTwnaQ4P7206yko3OTIweivm/wUGng9Oxm+IrNhGdaXtFZYsB76NbbNILbR/y9Z+9KeiLpatWoX8+mEy6LUnnLiojIQPm0TyFmSUdyb5edMVIub9dzQ==
Received: from ka-mbx03.SIDN.local ([192.168.2.179]) by arn2-kamx.sidn.nl with ESMTP id t5TBPwPm022909-t5TBPwPo022909 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=CAFAIL) for <eppext@ietf.org>; Mon, 29 Jun 2015 13:25:58 +0200
Received: from KAHUBCASN02.SIDN.local (192.168.2.76) by ka-mbx03.SIDN.local (192.168.2.179) with Microsoft SMTP Server (TLS) id 15.0.1076.9; Mon, 29 Jun 2015 13:25:59 +0200
Received: from KAMBX2.SIDN.local ([fe80::b1fd:88d9:e136:9655]) by kahubcasn02 ([192.168.2.74]) with mapi id 14.03.0224.002; Mon, 29 Jun 2015 13:25:55 +0200
From: Rik Ribbers <rik.ribbers@sidn.nl>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: New version of the Keyrelay draft
Thread-Index: AdCyW+AV1EhRFNMlQ+CBqSI14lxMFQ==
Date: Mon, 29 Jun 2015 11:25:55 +0000
Message-ID: <C80127C588F8F2409E2B535AF968B768BA1DDF13@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.172]
Content-Type: multipart/alternative; boundary="_000_C80127C588F8F2409E2B535AF968B768BA1DDF13kambx2SIDNlocal_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/BKkO7Q7u-AD0dgmBHXWzkNrmk68>
Subject: [eppext] New version of the Keyrelay draft
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 29 Jun 2015 11:26:02 -0000
All, I have uploaded a new version of the keyrelay draft, which currently awaits manual posting (https://datatracker.ietf.org/submit/status/70089/ ). Major changes are the input provided by our board of Registrars. There are certain scenarios when one may want to either revoke or extend the previously sent key material. I have added some wording on how to achieve this. A special thanks to Kees Monshouwer, a member of our Board of registrar, for his valuable input on this issue. We also change the xsd and examples a little with support for multiple keys in one keyrelay create. Feedback is much appreciated! Gr, Rik
- [eppext] New version of the Keyrelay draft Rik Ribbers