Subject: [email-masked] V|AGRA ® Official Seller -41%

From: [email-masked]
Date: Mon, 30 Aug 2010 17:17:19 -0700 (PDT)

Click here!

Return-Path:
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o7NJ1nCx025332 for ; Mon, 23 Aug 2010 21:01:49 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id o7NJ1n5C028663 for ietf-provreg-outgoing; Mon, 23 Aug 2010 21:01:49 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to [email-masked] using -f
Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o7NJ1mcX011812 for ; Mon, 23 Aug 2010 21:01:48 +0200 (MEST)
Received: by yxe42 with SMTP id 42so2986018yxe.27 for ; Mon, 23 Aug 2010 12:01:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:reply-to:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=dCClxXyPrPW+As4jZ3uEl5Uaitg1yi5qfc3f1nq5PnM=; b=lX90odFCJiyNJqIiwB6NX4cCSQbI1RH+vbVo/m683IJpRMScg1eA1ieXL+x+hliXu1 g3DSvzyjxBhSuua1y15pUYm6bSXwMxAoxcaV212jdB58ttFGM5sNA2lhXBacLHTJGeHJ TZ3sq3mHQd8oDwOLEhyZJX9nJV9ibAhJeJTtQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=FC4FZ0BC2zPIWyir8ttSYkMRptbXnG0HyARCPNe3pnrgFpr0/vII3q/1+n9Oy3lbCZ pPVmHGqS5YDynvk6r2K0hK7mycII8eleuXgLCKkWHg9vUItxQD3/7+8CPVWeMYq2xCv/ 03mzDflBzsG0Eb9WZlY2m5Grt+Zx8rUcZ41YU=
MIME-Version: 1.0
Received: by 10.100.197.4 with SMTP id u4mr5914153anf.17.1282590106994; Mon, 23 Aug 2010 12:01:46 -0700 (PDT)
Reply-To: [email-masked]
Received: by 10.231.128.213 with HTTP; Mon, 23 Aug 2010 12:01:46 -0700 (PDT)
In-Reply-To:
References: <[email-masked]>
Date: Mon, 23 Aug 2010 21:01:46 +0200
X-Google-Sender-Auth: dOq5BfU6H_65vrVG2jtxc1_BO0U
Message-ID:
Subject: Re: [ietf-provreg] RFC5910 public client implementation
From: Maarten Bosteels
To: James Gould
Cc: Ulrich Wisser , Frederico A C Neves , EPP Provreg
Content-Type: multipart/alternative; boundary=0016e645b74ab84c4b048e8247e2
Sender: [email-masked]
Precedence: bulk

--0016e645b74ab84c4b048e8247e2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello all,

We signed the .be zone on August 16 and we have a DNSSEC testbed available
for our registrars.
The EPP server on our test-system supports the Key Data interface of
RFC-5910.

We plan to go live with our implementation of RFC-5910 by October 2010.

Maarten Bosteels
Manager Software Development
http://www.dns.be

On Wed, Jul 28, 2010 at 9:26 PM, James Gould wrote:

> It=E2=80=99s great to hear that the implementations are moving forward.
>
> We=E2=80=99re including support for RFC 5910 and 4310 as part our DNSSEC =
release of
> .NET in September. We updated our Java EPP SDK to include support for bo=
th
> RFC 5910 and 4310 . The EPP SDK also includes a functional validating St=
ub
> Server that has specific test code for supporting both the DS Data Interf=
ace
> and the Key Data Interface of RFC 5910 as well as support for RFC 5910 an=
d
> 4310 in parallel. If anyone is interested, the URL below includes some
> higher level SDK information along with a link to the =E2=80=9CName Store=
/SRS
> Bundle=E2=80=9D distribution that has the RFC 5910 and 4310 support.
>
>
> http://www.verisign.com/domain-name-services/current-registrars/epp-sdk/i=
ndex.html
>
> Just curious if anyone is planning on supporting the Key Data Interface o=
f
> RFC 5910?
>
> --
>
>
> JG
>
> -------------------------------------------------------
> *James F. Gould
> **Principal Software Engineer
> *VeriSign Naming Services
> [email-masked]
> *Direct:* 703.948.3271
> *Mobile:* 703.628.7063
>
>
> 21345 Ridgetop Circle
> LS2-2-1
> Dulles, VA 20166
>
> *Notice to Recipient: **This e-mail contains confidential, proprietary
> and/or Registry Sensitive information intended solely for the recipient
> and, thus may not be retransmitted, reproduced or disclosed without the
> prior written consent of VeriSign Naming and Directory Services. If you
> have received this e-mail message in error, please notify the sender
> immediately by telephone or reply e-mail and destroy the original messag=
e
> without making a copy. Thank you.
> *
>
> ------------------------------
> *From: *Ulrich Wisser
> *Date: *Tue, 27 Jul 2010 07:51:09 -0400
> *To: *Frederico A C Neves
> *Cc: *EPP Provreg
> *Subject: *Re: [ietf-provreg] RFC5910 public client implementation
>
>
> Congrats!
>
> I'm working on the server implementation for .SE.
>
> /Ulrich
>
>
> --
> Help building the worlds most comprehensive list of judo dojos.
> Put your dojo on the list at http://JudoWorldMap.com
> -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-
> List run by majordomo software. For (Un-)subscription and similar detail=
s
> send "help" to [email-masked]
>
>
>

--0016e645b74ab84c4b048e8247e2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello all,

We signed the .be zone on August 16 and we have a DN=
SSEC testbed available for our registrars.
The EPP server on our test-sy=
stem supports the Key Data interface of RFC-5910.

We plan to go liv=
e with our implementation of RFC-5910 by October 2010.

Maarten Bosteels
Manager Software Develop=
ment

http://w=
ww.dns.be

On Wed, Jul 28, 2010 at 9:26 PM, James =
Gould <[email-masked]> wrote:

It=E2=80=99s great to hear that the implementations are moving forw=
ard. =C2=A0

We=E2=80=99re including support for RFC 5910 and 4310 as part our DNSSEC re=
lease of .NET in September. =C2=A0We updated our Java EPP SDK to include su=
pport for both RFC 5910 and 4310 . =C2=A0The EPP SDK also includes a functi=
onal validating Stub Server that has specific test code for supporting both=
the DS Data Interface and the Key Data Interface of RFC 5910 as well as su=
pport for RFC 5910 and 4310 in parallel. =C2=A0If anyone is interested, the=
URL below includes some higher level SDK information along with a link to =
the =E2=80=9CName Store/SRS Bundle=E2=80=9D distribution that has the RFC 5=
910 and 4310 support. =C2=A0

http://www.verisign.com/domain-name-s=
ervices/current-registrars/epp-sdk/index.html

Just curious if anyone is planning on supporting the Key Data Interface of =
RFC 5910?

--

JG

-------------------------------------------------------
James F. Gould

=
Principal Software Engineer

VeriSign Naming Services

[email-masked]

Direct: 703.948.3271

Mobile: 703.628.7063

=C2=A0

21345 Ridgetop Circle

LS2-2-1

Dulles, VA 20166

Notice to Recipient: =C2=A0This e-mail contains confidential, p=
roprietary and/or Registry =C2=A0Sensitive information intended solely for =
the recipient and, thus may not be =C2=A0retransmitted, reproduced or discl=
osed without the prior written consent of =C2=A0VeriSign Naming and Directo=
ry Services. =C2=A0If you have received =C2=A0this e-mail message in err=
or, please notify the sender immediately by =C2=A0telephone or reply e-mail=
and destroy the original message without making a =C2=A0copy. =C2=A0Th=
ank you.

=

From: Ulrich Wisser &l=
t;[email-masked]=
e>

Date: Tue, 27 Jul 2010 07:51:09 -0400

To: Frederico A C Neves <[email-masked]>

Cc: EPP Provreg <[email-masked]>

Subject: Re: [ietf-provreg] RFC5910 public client implementation

Congrats!

I'm working on the server implementation for .SE.

/Ulrich

--

Help building the worlds most comprehensive list of judo dojos.

Put your dojo on the list at http://JudoWorldMap.com

-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-

List run by majordomo software. =C2=A0For (Un-)subscription and similar det=
ails

send "help" to [email-masked]

--0016e645b74ab84c4b048e8247e2--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software. For (Un-)subscription and similar details
send "help" to [email-masked]

Return-Path:
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o749eGeo022373 for ; Wed, 4 Aug 2010 11:40:16 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id o749eGs4029498 for ietf-provreg-outgoing; Wed, 4 Aug 2010 11:40:16 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to [email-masked] using -f
Received: from xmrelay1-out.mrelay.net (xmrelay1-out.mrelay.net [93.190.233.28]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o749eFPD019807 for ; Wed, 4 Aug 2010 11:40:15 +0200 (MEST)
Subject: Re: [ietf-provreg] RFC5910 public client implementation
From: Jens Wagner
To: [email-masked]
Cc: James Gould , Ulrich Wisser , Frederico A C Neves , EPP Provreg
In-Reply-To: <[email-masked]>
References: <[email-masked]> <[email-masked]>
Content-Type: text/plain; charset="UTF-8"
Organization: HEXONET GmbH
Date: Wed, 04 Aug 2010 11:40:12 +0200
Message-ID: <1280914812.1840.65.camel@jwagner-eee>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 91.50.103.37
X-SA-Exim-Mail-From: [email-masked]
Sender: [email-masked]
Precedence: bulk

Hi Oliver,

Am Mittwoch, den 04.08.2010, 10:28 +0200 schrieb Oliver Peter:
> On Tue, 03 Aug 2010 16:59:27 +0200
> Jens Wagner wrote:
> > ...
> >
> > 65535
> > 1
> > 1
> > 1543C1BABEB5ECAF98774188032928B3CD18299A
> >
> > 256
> > 3
> > 1
> > AQPJ////4Q==
> >
> >
> >
> > 46089
> > 5
> > 1
> > 2A515440A8AEA13F034191AB0D35DB1DDF7968E8
> >
> > 257
> > 3
> > 5
> > AQPJ////5Q==
> >
> >
>
> Hm, that output above ( I guess?) depends on the
> elements specified by the client within the login frame, right?

That's right. I just limited the output to the element,
as it's using the same syntax in both secDNS-1.0 and secDNS-1.1 (except
for ).

Our gateway returns secDNS-1.1 compatible , if the
client included that namespace as an on login.

> In case of using Key Data Interface and specified
> urn...secDNS-1.1 within I think you have to return the
> elements and not the resulting .
>
> That's my understanding - please correct me if I'm wrong.

That is correct. We are just supporting the Key Data interface as an
input tool which autocreates DS Data, not sure if that's fully compliant
with section 4.

The one form we support accross all operations is the DS Data Interface
(this is neccessary to support the RFC 4310 in parallel). Some TLDs
require DS Data only, so don't want to force our customers to provide
Key Data if not required.

> I think we will support the Key Data Interface - but not with
> secDNS-1.0 backwards compatibility at the same time. But the decision
> hasn't been made yet.

As long as you store the Key Data, you can internally convert to
secDNS-1.0 compatible DS Data on-the-fly.

Best,
-jens

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software. For (Un-)subscription and similar details
send "help" to [email-masked]

Return-Path:
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o748Skp0007208 for ; Wed, 4 Aug 2010 10:28:46 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id o748SktY016580 for ietf-provreg-outgoing; Wed, 4 Aug 2010 10:28:46 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to [email-masked] using -f
Received: from nue-srv-1.opdns.org (nue-srv-1.opdns.de [88.198.69.202]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o748SjCM017449 for ; Wed, 4 Aug 2010 10:28:45 +0200 (MEST)
Received: from localhost (localhost [127.0.0.1]) by nue-srv-1.opdns.org (Postfix) with ESMTP id 2863756C03D; Wed, 4 Aug 2010 10:28:45 +0200 (CEST)
X-Virus-Scanned: amavisd-new at opdns.de
Received: from nue-srv-1.opdns.org ([127.0.0.1]) by localhost (nue-srv-1.opdns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sivDqZihStre; Wed, 4 Aug 2010 10:28:41 +0200 (CEST)
Received: from rgb-dev-1.opdns.de (91-66-176-33-dynip.superkabel.de [91.66.176.33]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by nue-srv-1.opdns.org (Postfix) with ESMTP id EACDE56C01C; Wed, 4 Aug 2010 10:28:40 +0200 (CEST)
Date: Wed, 4 Aug 2010 10:28:37 +0200
From: Oliver Peter
To: Jens Wagner
Cc: James Gould , Ulrich Wisser , Frederico A C Neves , EPP Provreg
Subject: Re: [ietf-provreg] RFC5910 public client implementation
Message-ID: <[email-masked]>
In-Reply-To: <[email-masked]>
References: <[email-masked]>
Reply-To: [email-masked]
Organization: mouhaha
X-Mailer: Claws Mail 3.7.4 (GTK+ 2.20.1; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: [email-masked]
Precedence: bulk

On Tue, 03 Aug 2010 16:59:27 +0200
Jens Wagner wrote:

> E.g. it accepts the following input
>
>
>
>
>
>
> secdns.org
>
>
>
>
>
> true
>
>
>
> 256
> 3
> 1
> AQPJ////4Q==
>
>
> 257
> 3
> 5
> AQPJ////5Q==
>
>
>
>
> ABC-12345
>
>
>
>
> and creates two DS data record:
>
>
> 65535
> 1
> 1
> 1543C1BABEB5ECAF98774188032928B3CD18299A
>
> 256
> 3
> 1
> AQPJ////4Q==
>
>
>
> 46089
> 5
> 1
> 2A515440A8AEA13F034191AB0D35DB1DDF7968E8
>
> 257
> 3
> 5
> AQPJ////5Q==
>
>

Hm, that output above ( I guess?) depends on the
elements specified by the client within the login frame, right?

In case of using Key Data Interface and specified
urn...secDNS-1.1 within I think you have to return the
elements and not the resulting .

That's my understanding - please correct me if I'm wrong.

I think we will support the Key Data Interface - but not with
secDNS-1.0 backwards compatibility at the same time. But the decision
hasn't been made yet.

--
Oliver PETER
opDNS Internetdienstleistung http://opdns.de
Alte Dorfstr. 17 D-93309 Kelheim-Weltenburg
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software. For (Un-)subscription and similar details
send "help" to [email-masked]

Return-Path:
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o73ExUI2011791 for ; Tue, 3 Aug 2010 16:59:30 +0200 (MEST)
Received: (from majordom@localhost) by nic.cafax.se (8.13.7/8.12.11/Submit) id o73ExUts005350 for ietf-provreg-outgoing; Tue, 3 Aug 2010 16:59:30 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to [email-masked] using -f
Received: from xmrelay1-out.mrelay.net (xmrelay1-out.mrelay.net [93.190.233.28]) by nic.cafax.se (8.13.7/8.12.11) with ESMTP id o73ExUsb012893 for ; Tue, 3 Aug 2010 16:59:30 +0200 (MEST)
Message-ID: <[email-masked]>
Date: Tue, 03 Aug 2010 16:59:27 +0200
From: Jens Wagner
Organization: HEXONET GmbH
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: James Gould
Cc: Ulrich Wisser , Frederico A C Neves , EPP Provreg
Subject: Re: [ietf-provreg] RFC5910 public client implementation
References:
In-Reply-To:
Content-Type: multipart/alternative; boundary="------------040906020008060102060505"
X-SA-Exim-Connect-IP: 188.97.237.95
X-SA-Exim-Mail-From: [email-masked]
Sender: [email-masked]
Precedence: bulk

This is a multi-part message in MIME format.
--------------040906020008060102060505
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit

Hi James,

we just implemented secDNS-1.0 and secDNS-1.1 into our EPP gateway.

It supports both Key Data and DS Data interfaces, as some tlds like .de
or .eu require Key Data anyways. For other TLDs which require DS Data,
it automatically creates it using the key data and SHA1 as digest type,
if using the Key Data interface.

E.g. it accepts the following input

secdns.org

true

256
3
1
AQPJ////4Q==

257
3
5
AQPJ////5Q==

ABC-12345

and creates two DS data record:

65535
1
1
1543C1BABEB5ECAF98774188032928B3CD18299A

256
3
1
AQPJ////4Q==

46089
5
1
2A515440A8AEA13F034191AB0D35DB1DDF7968E8

257
3
5
AQPJ////5Q==

Best,
- jens

James Gould schrieb:
> It's great to hear that the implementations are moving forward.
>
> We're including support for RFC 5910 and 4310 as part our DNSSEC
> release of .NET in September. We updated our Java EPP SDK to include
> support for both RFC 5910 and 4310 . The EPP SDK also includes a
> functional validating Stub Server that has specific test code for
> supporting both the DS Data Interface and the Key Data Interface of
> RFC 5910 as well as support for RFC 5910 and 4310 in parallel. If
> anyone is interested, the URL below includes some higher level SDK
> information along with a link to the "Name Store/SRS Bundle"
> distribution that has the RFC 5910 and 4310 support.
>
> http://www.verisign.com/domain-name-services/current-registrars/epp-sdk/index.html
>
> Just curious if anyone is planning on supporting the Key Data
> Interface of RFC 5910?
>
> --
>
>
> JG
>
> -------------------------------------------------------
> *James F. Gould
> **Principal Software Engineer
> *VeriSign Naming Services
> [email-masked]
> *Direct:* 703.948.3271
> *Mobile:* 703.628.7063
>
>
> 21345 Ridgetop Circle
> LS2-2-1
> Dulles, VA 20166
>
> */Notice to Recipient: /*/This e-mail contains confidential,
> proprietary and/or Registry Sensitive information intended solely for
> the recipient and, thus may not be retransmitted, reproduced or
> disclosed without the prior written consent of VeriSign Naming and
> Directory Services. *If you have received this e-mail message in
> error, please notify the sender immediately by telephone or reply
> e-mail and destroy the original message without making a copy.*
> Thank you.
> /
>
> ------------------------------------------------------------------------
> *From: *Ulrich Wisser
> *Date: *Tue, 27 Jul 2010 07:51:09 -0400
> *To: *Frederico A C Neves
> *Cc: *EPP Provreg
> *Subject: *Re: [ietf-provreg] RFC5910 public client implementation
>
> Congrats!
>
> I'm working on the server implementation for .SE.
>
> /Ulrich
>
>
> --
> Help building the worlds most comprehensive list of judo dojos.
> Put your dojo on the list at http://JudoWorldMap.com
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> List run by majordomo software. For (Un-)subscription and similar details
> send "help" to [email-masked]
>
>

--
Jens Wagner
Chief Executive Officer
HEXONET GmbH
Be Your Own Internet Services Provider

T: +49 6841 69 84 0
F: +49 6841 69 84 199
E: [email-masked]
W: http://www.hexonet.net

HEXONET GmbH, Talstrasse 27, 66424 Homburg, Germany. CEO & General Manager: Jens Wagner, HRB 2839 (HOM), Amtsgericht Saarbrücken, VAT-ID: DE-138316882
HEXONET Services Inc., 1100 - 1200 West 73rd Avenue, Vancouver, B.C., V6P 6G5, Canada. CSO & General Manager: Robert Birkner

This email and any files transmitted are confidential and intended only or the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.

--------------040906020008060102060505
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

Hi James,

we just implemented secDNS-1.0 and secDNS-1.1 into our EPP gateway.

It supports both Key Data and DS Data interfaces, as some tlds like .de
or .eu require Key Data anyways. For other TLDs which require DS Data,
it automatically creates it using the key data and SHA1 as digest type,
if using the Key Data interface.

E.g. it accepts the following input

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<epp xmlns="urn:ietf:params:xml:ns:epp-1.0">

<command>

<update>

<domain:update
xmlns:domain="urn:ietf:params:xml:ns:domain-1.0">

<domain:name>secdns.org</domain:name>

</domain:update>

</update>

<extension>

<secDNS:update
xmlns:secDNS="urn:ietf:params:xml:ns:secDNS-1.1">

<secDNS:rem>

<secDNS:all>true</secDNS:all>

</secDNS:rem>

<secDNS:add>

<secDNS:keyData>

<secDNS:flags>256</secDNS:flags>

<secDNS:protocol>3</secDNS:protocol>

<secDNS:alg>1</secDNS:alg>

<secDNS:pubKey>AQPJ////4Q==</secDNS:pubKey>

</secDNS:keyData>

<secDNS:keyData>

<secDNS:flags>257</secDNS:flags>

<secDNS:protocol>3</secDNS:protocol>

<secDNS:alg>5</secDNS:alg>

<secDNS:pubKey>AQPJ////5Q==</secDNS:pubKey>

</secDNS:keyData>

</secDNS:add>

</secDNS:update>

</extension>

<clTRID>ABC-12345</clTRID>

</command>

</epp>

and creates two DS data record:

<secDNS:dsData>

<secDNS:keyTag>65535</secDNS:keyTag>

<secDNS:alg>1</secDNS:alg>

<secDNS:digestType>1</secDNS:digestType>

<secDNS:digest>1543C1BABEB5ECAF98774188032928B3CD18299A</secDNS:digest>

<secDNS:keyData>

<secDNS:flags>256</secDNS:flags>

<secDNS:protocol>3</secDNS:protocol>

<secDNS:alg>1</secDNS:alg>

<secDNS:pubKey>AQPJ////4Q==</secDNS:pubKey>

</secDNS:keyData>

</secDNS:dsData>

<secDNS:dsData>

<secDNS:keyTag>46089</secDNS:keyTag>

<secDNS:alg>5</secDNS:alg>

<secDNS:digestType>1</secDNS:digestType>

<secDNS:digest>2A515440A8AEA13F034191AB0D35DB1DDF7968E8</secDNS:digest>

<secDNS:keyData>

<secDNS:flags>257</secDNS:flags>

<secDNS:protocol>3</secDNS:protocol>

<secDNS:alg>5</secDNS:alg>

<secDNS:pubKey>AQPJ////5Q==</secDNS:pubKey>

</secDNS:keyData>

</secDNS:dsData>

Best,

- jens

James Gould schrieb:

It’s great to hear that the implementations
are moving forward.

We’re including support for RFC 5910 and 4310 as part our DNSSEC
release of .NET in September.  We updated our Java EPP SDK to include
support for both RFC 5910 and 4310 .  The EPP SDK also includes a
functional validating Stub Server that has specific test code for
supporting both the DS Data Interface and the Key Data Interface of RFC
5910 as well as support for RFC 5910 and 4310 in parallel.  If anyone
is interested, the URL below includes some higher level SDK information
along with a link to the “Name Store/SRS Bundle” distribution that has
the RFC 5910 and 4310 support.

http://www.verisign.com/domain-name-services/current-registrars/epp-sdk/index.html

Just curious if anyone is planning on supporting the Key Data Interface
of RFC 5910?

--

JG

-------------------------------------------------------

James F. Gould

Principal Software Engineer

VeriSign Naming Services

[email-masked]

Direct: 703.948.3271

Mobile: 703.628.7063

21345 Ridgetop Circle

LS2-2-1

Dulles, VA 20166

Notice to Recipient:  This e-mail contains confidential, proprietary
and/or Registry  Sensitive information intended solely for the
recipient and, thus may not be  retransmitted, reproduced or disclosed
without the prior written consent of  VeriSign Naming and Directory
Services.  If you have received  this e-mail message in error,
please notify the sender immediately by  telephone or reply e-mail and
destroy the original message without making a  copy.  Thank you.

From: Ulrich Wisser
<[email-masked]>

Date: Tue, 27 Jul 2010 07:51:09 -0400

To: Frederico A C Neves <[email-masked]>

Cc: EPP Provreg <[email-masked]>

Subject: Re: [ietf-provreg] RFC5910 public client
implementation

Congrats!

I'm working on the server implementation for .SE.

/Ulrich

--

Help building the worlds most comprehensive list of judo dojos.

Put your dojo on the list at http://JudoWorldMap.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

List run by majordomo software.  For (Un-)subscription and similar
details

send "help" to [email-masked]

--
Jens Wagner
Chief Executive Officer
HEXONET GmbH
Be Your Own Internet Services Provider

T: +49 6841 69 84 0
F: +49 6841 69 84 199
E: [email-masked]
W: http://www.hexonet.net

HEXONET GmbH, Talstrasse 27, 66424 Homburg, Germany. CEO & General Manager: Jens Wagner, HRB 2839 (HOM), Amtsgericht Saarbrücken, VAT-ID: DE-138316882
HEXONET Services Inc., 1100 - 1200 West 73rd Avenue, Vancouver, B.C., V6P 6G5, Canada. CSO & General Manager: Robert Birkner

This email and any files transmitted are confidential and intended only or the person(s) directly addressed. If you are not the intended recipient, any use, copying, transmission, distribution, or other forms of dissemination is strictly prohibited. If you have received this email in error, please notify the sender immediately and permanently delete this email with any files that may be attached.

--------------040906020008060102060505--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
List run by majordomo software. For (Un-)subscription and similar details
send "help" to [email-masked]