[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: edlewis@arin.net (Edward Lewis)
Cc: scottr@antd.nist.gov, dnssec@cafax.se
From: Bill Manning <bmanning@isi.edu>
Date: Fri, 2 Aug 2002 06:41:24 -0700 (PDT)
In-Reply-To: <a05111b01b9703579c95e@[192.149.252.231]> from Edward Lewis at "Aug 2, 2 09:18:27 am"
Sender: owner-dnssec@cafax.se
Subject: Re: November dates

% As far as goals, here is an all encompassing list I can think up.  I 
% don't mean to say that we should do all of this.  I am hoping to get 
% some ideas from folks about what we might want to try.
% 
%     1) Testing key exchange protocols
%     2) Interop of implementations (assuming there are multiples)
%     3) Code shakeout (in case we have nothing but snapshots/alphas/betas/rcs
%     4) Spec shakeout (DS and other aspects)
%     5) "Other" like OE IPsec testing (as a sideshow)
% 

	Key exchange protocols? Is that the classical definition of
	protocol or the (much narrower) IETF definition?

	I expect that each site will have its own ideas on how
	keys are generated, published, destroyed.  Linking these
	ideas into a working heirarchy is what I would like to see
	accomplished.

	Interop of implementations presumes this has not already
	been done. Besides, are we going to have more than one
	working resolver?

	3) and 4) are bound to occur... :)

	5 kind of depends on having a working heirarchy.  Icing
	on the cake if you will. For OE to have a verifiable 
	set of delegations gives higher confidence that the "right"
	endpoint is being talked to.

	I'd like to explore the relative value in having signed
	data, even if it is not used for "chain of custody" verification.

	
--bill

Home | Date list | Subject list