NCSG-DISCUSS Archives

NCSG-Discuss

NCSG-DISCUSS@LISTSERV.SYR.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
NCSG-Discuss <[log in to unmask]>
X-To:
Niels ten Oever <[log in to unmask]>
Date:
Fri, 27 May 2016 07:29:41 +0000
Reply-To:
"Mueller, Milton L" <[log in to unmask]>
Message-ID:
Subject:
From:
"Mueller, Milton L" <[log in to unmask]>
MIME-Version:
1.0
In-Reply-To:
Content-Transfer-Encoding:
base64
Content-Type:
text/plain; charset="utf-8"
Parts/Attachments:
text/plain (1 lines)




> -----Original Message-----

> The story that I keep on hearing is that even the most experienced engineers

> have issues with understanding the configuration of the KSK and Zone signing

> keys and the key rollover, inconsistencies in documentation and therefore

> lack of adoption, because in case of a mistake this might seriously impact the

> production environment.



I can confirm (from the RIPE meeting where they have a DNS WG) that these concerns are widespread. DNSSEC is brittle and key rollover is a very complicated. 



One thing I heard (do not know this deeply) is that a lot about DNSSEC key management depends on the registrar and every registrar does it differently. 




ATOM RSS1 RSS2