Re: [eppext] New Version Notification for draft-gould-eppext-verificationcode-00.txt

"Gould, James" <JGould@verisign.com> Sat, 10 October 2015 12:44 UTC

Return-Path: <JGould@verisign.com>
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 E5D4D1B3622 for <eppext@ietfa.amsl.com>; Sat, 10 Oct 2015 05:44:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 ncqSFsc6KThR for <eppext@ietfa.amsl.com>; Sat, 10 Oct 2015 05:44:38 -0700 (PDT)
Received: from mail-oi0-f97.google.com (mail-oi0-f97.google.com [209.85.218.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E70951B3620 for <eppext@ietf.org>; Sat, 10 Oct 2015 05:44:37 -0700 (PDT)
Received: by oibv129 with SMTP id v129so326162oib.2 for <eppext@ietf.org>; Sat, 10 Oct 2015 05:44:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=cQ8T8bV5+mPv2bZv6JJULXh1wNvKh3S9qyiOxKAlOtY=; b=ClX7trF9hVSH/vnJUJsYNLoNGjRB02EgzKw7NWwDbsn/a083JcqlygGVcvj7zztThb G4WPgM27EGunmt9LKDnNIZzjxSpCOkZNp8WsDNpKu5QXkuluV6ngTUQwXZyTwYfPz9Kh EQERefp1N/SeOqNWsACy82uQHQgrLQM5Pp4Gx2IUW+st0jFyJvtN0WNbsmzmXnsHsq4r P7+IZjskNljTTMlIuaH2PHw/1MrcRtdBZj9x689OBllNE+bcitTCerrXEqIZaQAzI7yy 2Nvhyn6C1/FJvH0SD/jczUlQyngdieLemSAykcWcMDoIEWNva6nn7OMGg2qDHsRIf/fL f6gA==
X-Gm-Message-State: ALoCoQkEw+n/eslpy9VZ55CMJCK3zGei2DMYanarerc6zf5sb92ZeO4alnTXwMfq0s6BDmTC3BUJkPwyj+KLAvZXYAzJVgmtjQ==
X-Received: by 10.55.22.162 with SMTP id 34mr22107265qkw.3.1444481077102; Sat, 10 Oct 2015 05:44:37 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id p63sm767761qkl.10.2015.10.10.05.44.36 for <eppext@ietf.org> (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 10 Oct 2015 05:44:37 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t9ACiaoi026893 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <eppext@ietf.org>; Sat, 10 Oct 2015 08:44:36 -0400
Received: from BRN1WNEXMBX02.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Sat, 10 Oct 2015 08:44:36 -0400
From: "Gould, James" <JGould@verisign.com>
To: "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: New Version Notification for draft-gould-eppext-verificationcode-00.txt
Thread-Index: AQHQ+vvhOUu+iQbPrEyRJrZ5Sxmctp5k/+6A
Date: Sat, 10 Oct 2015 12:44:35 +0000
Message-ID: <24207ECE-99D4-4AAF-ADCE-ECAA60B6B92C@verisign.com>
References: <20150929211447.28402.10500.idtracker@ietfa.amsl.com> <AAF5AAE0-0744-406B-91C1-D59AF505FD93@verisign.com>
In-Reply-To: <AAF5AAE0-0744-406B-91C1-D59AF505FD93@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_24207ECE99D44AAFADCEECAA60B6B92Cverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/K5RcDhis_5_W8OG9B0qeRlbizPk>
Subject: Re: [eppext] New Version Notification for draft-gould-eppext-verificationcode-00.txt
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: Sat, 10 Oct 2015 12:44:41 -0000

As a followup, my co-authors and I published the China Name Verification Mapping with the information below.  I request that both the Verification Code EPP Extension ( draft-gould-eppext-verificationcode ) and the China Name Verification EPP Mapping ( draft-xie-eppext-nv-mapping ) be taken up by the EPPEXT Working Group.  There is an agenda item to discuss these drafts at the EPPEXT meeting at IETF 94.  Please review the drafts and provide feedback.


A new version of I-D, draft-xie-eppext-nv-mapping-00.txt
has been successfully submitted by Xie Jiagui and posted to the
IETF repository.

Name: draft-xie-eppext-nv-mapping
Revision: 00
Title: Extensible Provisioning Protocol (EPP) China Name Verification Mapping
Document date: 2015-10-09
Group: Individual Submission
Pages: 36
URL:            https://www.ietf.org/internet-drafts/draft-xie-eppext-nv-mapping-00.txt
Status:         https://datatracker.ietf.org/doc/draft-xie-eppext-nv-mapping/
Htmlized:       https://tools.ietf.org/html/draft-xie-eppext-nv-mapping-00


Abstract:
  This document describes an Extensible Provisioning Protocol (EPP) for
  the provisioning and management of Name Verification (NV) stored in a
  shared central repository in China.  Specified in XML, the mapping
  defines EPP command syntax and semantics as applied to name
  verification.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat

ā€”


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Oct 1, 2015, at 5:17 PM, Gould, James <JGould@verisign.com<mailto:JGould@verisign.com>> wrote:

I published draft-gould-eppext-verificationcode as a mechanism for including a verification code for making the data for a transform command as being verified by a 3rd party, which is referred to as a Verification Service Provider (VSP).  A subsequent EPP mapping, currently named the China Name Verification Mapping, will be published defining the interface for a China VSP to implement the verification and generate verification codes that work with draft-gould-eppext-verificationcode.  I request that this draft and the subsequent draft be taken up by the EPPEXT Working Group.  There is an agenda item to discuss these drafts at the EPPEXT meeting at IETF 94.

Thanks,

ā€”

JG


<BF09FAA4-32D8-46E0-BED0-CD72F43BD6E0[81].png>

James Gould
Distinguished Engineer
jgould@Verisign.com<x-msg://18/jgould@Verisign.com>

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://verisigninc.com/>

Begin forwarded message:

From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Subject: New Version Notification for draft-gould-eppext-verificationcode-00.txt
Date: September 29, 2015 at 5:14:47 PM EDT
To: James Gould <jgould@verisign.com<mailto:jgould@verisign.com>>, James Gould <jgould@verisign.com<mailto:jgould@verisign.com>>


A new version of I-D, draft-gould-eppext-verificationcode-00.txt
has been successfully submitted by James Gould and posted to the
IETF repository.

Name: draft-gould-eppext-verificationcode
Revision: 00
Title: Verification Code Extension for the Extensible Provisioning Protocol (EPP)
Document date: 2015-09-29
Group: Individual Submission
Pages: 33
URL:            https://www.ietf.org/internet-drafts/draft-gould-eppext-verificationcode-00.txt
Status:         https://datatracker.ietf.org/doc/draft-gould-eppext-verificationcode/
Htmlized:       https://tools.ietf.org/html/draft-gould-eppext-verificationcode-00


Abstract:
  This document describes an Extensible Provisioning Protocol (EPP)
  extension for including a verification code for marking the data for
  a transform command as being verified by a 3rd party, which is
  referred to as the Verification Service Provider (VSP).  The
  verification code is digitally signed by the VSP using XML Signature
  and is "base64" encoded.  The XML Signature includes the VSP signer
  certificate, so the server can verify that the verification code
  originated from the VSP.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org/>g/>.

The IETF Secretariat