To:
EPP Provreg <ietf-provreg@cafax.se>
From:
Howard Eland <heland@afilias.info>
Date:
Thu, 29 Oct 2009 12:05:57 -0500
In-Reply-To:
<F7731082-3D07-4C47-BF21-83034B5F204B@afilias.info>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: [ietf-provreg] Anyone working on 4310-bis?
One thing that does make using all four elements easier: it's consistent with both the add and chg operators, which may make it easier for implementors to code (well, a tiny bit, anyway). James, I'm not sure if this is to your point or not. Codifying the edge cases is important, however, and it appears that we'll have to lose some of this compatibility to do so (regardless if we use just the hash on the rem, or the entire dsData). By requiring anything other than just the keyTag itself, it will not be backwards compatible for implementors - today, the keytag submission is sufficient, tomorrow, it will not be (going strictly by the RFC, not by registry policy). I am no longer particular to either method - they both would be fine. -Howard On Oct 29, 2009, at 10:57 AM, Howard Eland wrote: > This is what I was saying. The digest is unique (specially when > we're talking across only the same keytag), so the rest of the > information is superfluous. > > -Howard > > On Oct 29, 2009, at 10:32 AM, Andrew Sullivan wrote: > >> On Wed, Oct 28, 2009 at 10:32:19AM -0400, James Gould wrote: >> >>> still behaves like a replace, which again is backward compatible. >>> The only >>> difference is that all four elements need to be provided (keyTag, >>> alg, >>> digestType, digest) with a rem, which I donšt believe should be a >>> big issue. >>> Does anyone see an issue with having to specify either the keyTag >>> or all >>> four elements on a rem? >> >> Can you say why you prefer to use all four elements instead of just >> the digest? The digest actually is unique, so adding the other >> elements doesn't make it easier, I don't think, does it? >> >> A >> >> >> -- >> Andrew Sullivan >> ajs@shinkuro.com >> Shinkuro, Inc. >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> =-=-=-=- >> List run by majordomo software. For (Un-)subscription and similar >> details >> send "help" to ietf-provreg-request@cafax.se >> > > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > =-=-=- > List run by majordomo software. For (Un-)subscription and similar > details > send "help" to ietf-provreg-request@cafax.se > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- List run by majordomo software. For (Un-)subscription and similar details send "help" to ietf-provreg-request@cafax.se