Re: DNSSEC - Signature Only vs the MX/A issue.

Mike StJohns <Mike.StJohns@nominum.com> Thu, 30 November 2006 19:34 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gprg2-0008VU-LH; Thu, 30 Nov 2006 14:34:34 -0500
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gprg1-0001qK-BS; Thu, 30 Nov 2006 14:34:34 -0500
Received: from majordom by psg.com with local (Exim 4.63 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1GprXo-0004RZ-3t for namedroppers-data@psg.com; Thu, 30 Nov 2006 19:26:04 +0000
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on psg.com
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.1.7
Received: from [81.200.64.181] (helo=shell-ng.nominum.com) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from <Mike.StJohns@nominum.com>) id 1GprWJ-0004G7-H4 for namedroppers@ops.ietf.org; Thu, 30 Nov 2006 19:25:07 +0000
Received: from STJOHNS-LAPTOP.nominum.com (shell-ng.nominum.com [81.200.64.181]) by shell-ng.nominum.com (Postfix) with ESMTP id 801B65691E; Thu, 30 Nov 2006 11:24:18 -0800 (PST) (envelope-from Mike.StJohns@nominum.com)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 30 Nov 2006 13:57:52 -0500
To: Josh Littlefield <joshl@cisco.com>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Mike StJohns <Mike.StJohns@nominum.com>
Subject: Re: DNSSEC - Signature Only vs the MX/A issue.
Cc: namedroppers@ops.ietf.org
In-Reply-To: <456CAD59.8030501@cisco.com>
References: <20061127032712.CD1FE56890@shell-ng.nominum.com> <20061128135806.GA24695@nic.fr> <20061128203532.0DC4F56890@shell-ng.nominum.com> <20061128204758.GA20253@nic.fr> <456CAD59.8030501@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Message-Id: <20061130192418.801B65691E@shell-ng.nominum.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

At 04:42 PM 11/28/2006, Josh Littlefield wrote:
>Stephane Bortzmeyer wrote:
> > On Tue, Nov 28, 2006 at 03:13:50PM -0500,
> >  Mike StJohns <Mike.StJohns@nominum.com> wrote
> >  a message of 25 lines which said:
> >
> >> Not exactly.  See my previous note to Mark.  SO still protects the
> >> atomicity of an RRSet - you can delete ALL of the SRV records or
> >> none of them.  If you delete all of them at a label, the lookup
> >> fails and you can't proceed.
> >
> > See Peter Koch's reply :-) Many protocols define a fallback outside of
> > the RRset. For instance, in
> > 
> http://mirrors.isc.org/pub/www.watersprings.org/pub/id/draft-andrews-http-srv-01.txt,
> > there is a fallback from SRV to A.
>
>Similarly, RFC 3263 defines fallback from NAPTR to SRV (at a different
>but related name), followed by fallback to A and AAAA.

*sigh* Yes.  


--
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/>