This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] revised text for NTIA response - v4
- Previous message (by thread): [dns-wg] revised text for NTIA response - v4
- Next message (by thread): [dns-wg] revised text for NTIA response - v4
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
bmanning at vacation.karoshi.com
bmanning at vacation.karoshi.com
Mon Nov 3 17:05:07 CET 2008
> Anyway, now it's time for comments. It would be helpful if you > contribute alternate text along with any clarifications or remarks. ie > Please don't just say "Point X is unclear/confusing". Please say why > it's confusing and suggest better wording. If we are to reach > consensus by this weekend, the discussion needs to be focused and > direct. > > # > # $Id: ntia-draft,v 1.4 2008/11/03 10:25:25 jim Exp $ > # > > 10. The organisation that generates the root zone file must hold the > private part of the zone signing key. > the imperative in this point is made with zero justification. why the "must hold"? I think a more pragmatic reply (if the previous points are to be respected) would be something along these lines: 10. The organization that generates the root zone file must sign the file and therefore must hold the private part of the zone signing key. or 10. The organization that generates the root zone file must have unfettered access to the zone signing key components. I have a slight inclination towards the second. --bill
- Previous message (by thread): [dns-wg] revised text for NTIA response - v4
- Next message (by thread): [dns-wg] revised text for NTIA response - v4
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]