[155621] in North American Network Operators' Group
Re: Return two locations or low TTL [was: DNS caches that support
daemon@ATHENA.MIT.EDU (Shumon Huque)
Mon Aug 20 10:27:39 2012
Date: Mon, 20 Aug 2012 10:26:55 -0400
From: Shumon Huque <shuque@upenn.edu>
To: nanog@nanog.org
In-Reply-To: <alpine.LSU.2.00.1208201509240.9973@hermes-1.csi.cam.ac.uk>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 8/20/12 10:11 AM, Tony Finch wrote:
> Patrick W. Gilmore <patrick@ianai.net> wrote:
>> On Aug 20, 2012, at 08:47 , Chris Adams <cmadams@hiwaay.net> wrote:
>>>
>>> Most anything that supports IPv6 should handle this correctly, since
>>> getaddrinfo() will return a list of addresses to try.
>>
>> Ah, the amazing new call which destroys any possibility of randomness or
>> round robin or other ways of load balancing between A / AAAA records.
>> Yes, all of us returning more than one A / AAAA record are hoping that
>> gets widely deployed instantly. Or not.
>
> The problem is RFC 3484 address selection; getaddrinfo is just the usual
> place this is implemented. I had believed that there was work in progress
> to fix this problem with the specs but it seems to have stalled.
> http://tools.ietf.org/html/draft-ietf-6man-rfc3484-revise-05
>
> Tony.
>
It's in the RFC editor queue actually:
http://datatracker.ietf.org/doc/draft-ietf-6man-rfc3484bis/?include_text=1
http://datatracker.ietf.org/doc/draft-ietf-6man-rfc3484bis/history/
--Shumon.
