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] NTIA and RIPE
- Previous message (by thread): [dns-wg] NTIA and RIPE
- Next message (by thread): [dns-wg] NTIA and RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andrei Robachevsky
andrei at ripe.net
Thu Oct 30 08:52:58 CET 2008
Patrik Fältström wrote on 30-10-2008 07:34: [...]> Now, we had this bullet: > > K - Changes to the entities and roles in the signing process must not > require a change of keys. > > Then I thought about changing it to the following: > > K - Changes to the entities and roles in the signing process should > minimize issues related to potential changes in keys when the entities > changes. > > Now, I am a bit confused... :-) > > Jakob, Ed, others...do you have any suggestion on text? > I was under the impression that point K essentially said that implementation should not cast the current root zone management setup (with regards to the entities) in stone. If this is so, how about the following: K - Changes of the entities representing roles in the signing process must be possible and have minimum effect on the keys. > Patrik > Andrei
- Previous message (by thread): [dns-wg] NTIA and RIPE
- Next message (by thread): [dns-wg] NTIA and RIPE
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]