Re: interop problems with getaddrinfo() address selection

Tony Finch <dot@dotat.at> Tue, 11 December 2007 10:40 UTC

Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J22Ww-0004yB-4H; Tue, 11 Dec 2007 05:40:02 -0500
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1J22Wv-0004xu-Mw for discuss-confirm+ok@megatron.ietf.org; Tue, 11 Dec 2007 05:40:01 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J22Wv-0004xg-DA for discuss@apps.ietf.org; Tue, 11 Dec 2007 05:40:01 -0500
Received: from ppsw-7.csi.cam.ac.uk ([131.111.8.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J22Wu-00054p-Sa for discuss@apps.ietf.org; Tue, 11 Dec 2007 05:40:01 -0500
X-Cam-SpamDetails: Not scanned
X-Cam-AntiVirus: No virus found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:35006) by ppsw-7.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1J22Wr-0001Ad-P4 (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 11 Dec 2007 10:39:57 +0000
Received: from fanf2 (helo=localhost) by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1J22Wr-0001GC-OO (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 11 Dec 2007 10:39:57 +0000
Date: Tue, 11 Dec 2007 10:39:57 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
Subject: Re: interop problems with getaddrinfo() address selection
In-Reply-To: <200712102311.SAA01012@Sparkle.Rodents.Montreal.QC.CA>
Message-ID: <Pine.LNX.4.64.0712111037500.27891@hermes-1.csi.cam.ac.uk>
References: <Pine.LNX.4.64.0712061901020.24448@hermes-1.csi.cam.ac.uk> <200712062020.PAA16213@Sparkle.Rodents.Montreal.QC.CA> <Pine.LNX.4.64.0712071735070.24448@hermes-1.csi.cam.ac.uk> <475B0ABC.5090806@cs.utk.edu> <Pine.LNX.4.64.0712092000150.29087@hermes-1.csi.cam.ac.uk> <475C5047.3010807@cs.utk.edu> <Pine.LNX.4.64.0712100739410.29087@hermes-1.csi.cam.ac.uk> <200712101815.NAA27674@Sparkle.Rodents.Montreal.QC.CA> <Pine.LNX.4.64.0712101935070.24448@hermes-1.csi.cam.ac.uk> <200712102311.SAA01012@Sparkle.Rodents.Montreal.QC.CA>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: discuss@apps.ietf.org
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols <discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>, <mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org

On Mon, 10 Dec 2007, der Mouse wrote:
>
> It appears we're talking about differnet things.  To me, DNS round-robin
> refers to the sort of thing the NTP pool project does: rotating the
> answer(s) returned in response to a query through a larger (usually much
> larger) set of possible answers.

That's incompatible with RFC 2181 section 5 and DNSSEC.

> It sounds as though you're talking about simply returning all the
> answers and hoping that, somewhere along the line, someone will end up
> choosing one in a way that looks random with respect to the property you
> care about.

Right.

Tony.
-- 
f.a.n.finch  <dot@dotat.at>  http://dotat.at/
VIKING NORTH UTSIRE SOUTH UTSIRE FORTIES: NORTHWEST 5 OR 6, BECOMING VARIABLE
3 OR 4, THEN BECOMING SOUTH 5 TO 7, PERHAPS GALE 8 LATER IN VIKING. MODERATE
OR ROUGH. SHOWERS. GOOD.