Re: [DNSOP] DS transfer requirements

2013-04-24 Thread Wes Hardaker
Antoin Verschuren writes: > Op 24-04-13 15:18, Wes Hardaker schreef: > >> + operate on a single record at a time (publish this DS, don't >> touch the rest) > > I don't understand the rationale behind this one. > Can someone please explain to me? > > I would think a child knows what "the rest" is

Re: [DNSOP] DS transfer requirements

2013-04-24 Thread Joe Abley
Hi Wes, On 2013-04-24, at 09:18, Wes Hardaker wrote: > I > think part of the problem has been we don't have a good list of > requirements to compare any given solution to and we're talking around > them all because they're not written down (at least in one place). I like your list. I think it's

Re: [DNSOP] DS transfer requirements

2013-04-24 Thread Antoin Verschuren
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 24-04-13 15:18, Wes Hardaker schreef: > + operate on a single record at a time (publish this DS, don't > touch the rest) I don't understand the rationale behind this one. Can someone please explain to me? I would think a child knows what "the res

[DNSOP] DS transfer requirements

2013-04-24 Thread Wes Hardaker
Ed pointed me to a message he wrote [1] and some of the text there triggered my "oh yeah; we need to start with the requirements" bell. I think part of the problem has been we don't have a good list of requirements to compare any given solution to and we're talking around them all because they're

Re: [DNSOP] Thoughts on CDS

2013-04-24 Thread Antoin Verschuren
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Op 23-04-13 17:18, Edward Lewis schreef: > > For zones that operate under a mandate of the ICANN-style shared > registry model, you can't bypass the registrar. I think this is the essence of why previous attempts to automate technical DNS maintenanc