Could someone in operations from Consolidated Communications in Vermont please
contact me off list, if possible?
Thanks,
Matt
--
Matt Larson, VP of Research
ICANN Office of the CTO
mailing
lists, including this one, so please reply here with any issues or concerns.
Matt
--
Matt Larson, VP of Research
ICANN Office of the CTO
inued confidence in
the security of KSK-2010.
We appreciate the community's understanding and we look forward to your
assistance in gathering the information necessary to move forward with the root
KSK roll.
Matt
--
Matt Larson, VP of Research
ICANN Office of the CTO
signature.asc
Description: Message signed with OpenPGP
validation, is available at
https://icann.org/kskroll.
For the root zone management partners,
Matt Larson
VP of Research, ICANN
Duane Wessels
Distinguished Engineer, Verisign
signature.asc
Description: Message signed with OpenPGP
Could someone from Verizon Wireless please contact me off-list?
Thanks,
Matt
--
Matt Larson
VP of Research
Office of the CTO, ICANN
+1 240 459-9562 (mobile)
ing DNSSEC validation, you should care. If you're not the
DNS person in your organization, please pass this notice on to that person. If
the topic interests you, more information is below.
Matt
--
Matt Larson
VP of Research
Office of the CTO, ICANN
> Begin forwarded message:
>
records.
If you have any questions or comments, please send email to
info@verisignâgrs.com or reply to this message.
Matt Larson
signature.asc
Description: Message signed with OpenPGP using GPGMail
oyment was publishing the .com zone's DS
record in the root zone.
I am pleased to report that the root zone including a DS record for
.com was published at approximately 1500 UTC today, March 31.
Matt Larson, on behalf of the many people at Verisign who made this
deployment possible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Over the next several weeks, Verisign will deploy DNSSEC in the .com
zone. This message contains operational information related to the
deployment that might be of interest to the Internet operational
community.
The .com DNSSEC deployment consists of
On Thu, 23 Dec 2010, Jay Ashworth wrote:
> > From: "Matt Larson"
>
> > The new KSK will not be published in an authenticated manner outside
> > DNS (e.g., on an SSL-protected web page). Rather, the intended
> > mechanism for trusting the new KSK is via
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A KSK roll for the .gov zone will occur at the end of January, 2011.
This key change is necessitated by a registry operator transition:
VeriSign has been selected by the U.S. General Services Administration
(GSA) to operate the domain name registry for
VeriSign is in the process of deploying DNSSEC in the .net and .com
zones. This message contains operational information related to the
.net DNSSEC deployment that might be of interest to the Internet
operational community.
The .net DNSSEC deployment is underway.
On September 25, 2010, the .net
Over the next several months, VeriSign will deploy DNSSEC in the .net
and .com zones. This message contains operational information related
to the deployment that might be of interest to the Internet
operational community.
The .net DNSSEC deployment consists of the following major milestones:
Se
With Becky Granger's permission, I'm pleased to share the announcement
below.
Matt
- Forwarded message from Becky Granger -
From: Becky Granger
Subject: [Dnssec-deployment] DNSSEC Launched Today by EDUCAUSE and VeriSign
To: dnssec-deploym...@dnssec-deployment.org, dns...@internet2.edu
On Thu, 15 Jul 2010, Matt Larson wrote:
> On Thu, 15 Jul 2010, Matt Larson wrote:
> > [...] was published and began rolling out to the root servers at 1625 UTC.
>
> Make that 1650 UTC...
>
> (The perils of staging email.)
Make that 2050 UTC (1650 EDT).
(The perils of a str
On Thu, 15 Jul 2010, Matt Larson wrote:
> [...] was published and began rolling out to the root servers at 1625 UTC.
Make that 1650 UTC...
(The perils of staging email.)
I am pleased to report that the first fully validatable production
signed root zone, with SOA serial number 2010071501, was published and
began rolling out to the root servers at 1625 UTC.
More details to follow in a formal update.
Matt
...on behalf of the root DNSSEC design team
cords promoted to
authoritative data would have to be signed, resulting in increased
complexity for the overall registry system. This change in business
logic (where the removal of a domain on hold also affects name servers
below that domain) is consistent with the behavior of other top-level
domai
u can reach the entire team
at roots...@icann.org.
On behalf of the root zone DNSSEC deployment team,
Matt Larson
--
Status Update, December, 2009
This is the first of a series of technical status updates intended to
inform a technical audience on the progress of deploying DNSSEC in the
root zo
19 matches
Mail list logo