Re: DNSSECbis Q-17: typecode change and TKEY

Jakob Schlyter <jakob@rfc.se> Thu, 09 October 2003 14:40 UTC

From: Jakob Schlyter <jakob@rfc.se>
Subject: Re: DNSSECbis Q-17: typecode change and TKEY
Date: Thu, 09 Oct 2003 16:40:26 +0200
Lines: 16
Sender: owner-namedroppers@ops.ietf.org
References: <Pine.LNX.4.58.0310090922070.2350@elektron.atoom.net>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Cc: namedroppers@ops.ietf.org
To: Roy Arends <roy@logmess.com>
In-Reply-To: <Pine.LNX.4.58.0310090922070.2350@elektron.atoom.net>
Precedence: bulk
Message-ID: <20140418071750.2560.83187.ARCHIVE@ietfa.amsl.com>

On Thu, 9 Oct 2003, Roy Arends wrote:

> 1) retain KEY, SIG RR for the use of TKEY as well as SIG(0).
> 2) Have draft-ietf-dnsext-dnssec-2535typecode-change update RFC 2930 as
>    well.

I'd would go for (1) since signing transactions and rr sets have different
usages, separating the keys makes sense.

	jakob

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>

DNSSECbis Q-17: typecode change and TKEY Roy Arends
Re: DNSSECbis Q-17: typecode change and TKEY Scott Rose
Re: DNSSECbis Q-17: typecode change and TKEY Jakob Schlyter
Re: DNSSECbis Q-17: typecode change and TKEY Rob Austein