Re: [dnssd] Hybrid Proxy SOA records

Markus Stenberg <markus.stenberg@iki.fi> Wed, 03 September 2014 13:08 UTC

Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <65F4CC0B-B0BD-42C4-B944-A49438AAF6BC@bangj.com>
Date: Wed, 03 Sep 2014 16:08:19 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <0DDB5E45-AA96-41FF-9F65-E9F00F705749@iki.fi>
References: <65F4CC0B-B0BD-42C4-B944-A49438AAF6BC@bangj.com>
To: Tom Pusateri <pusateri@bangj.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/wahdpKWV-sqnNJiWnpF6NtYpnd8
Cc: dnssd@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [dnssd] Hybrid Proxy SOA records
Precedence: list

For the record, I’m not that convinced SOA is that useful - I don’t implement LLQ and also no SOA for zones currently.

That said..

On 3.9.2014, at 15.48, Tom Pusateri <pusateri@bangj.com> wrote:
> There are many recommendations out there for SOA response values but I was wondering if the Hybrid Proxy is in a unique enough position that the draft should provide guidance on the SOA response values.
> 
> Ripe has some recommendations here:
> 
> http://www.ripe.net/ripe/docs/ripe-203

These figures are way off the mark for what hybrid proxy provides - for example, mdns maximum TTL is hour or two, and the recommendation has minimum TTL of 2 days.. :-p

> But when does the serial number change in a dynamic proxy? The recommendations from Ripe seem too long for the hybrid proxy case.

Constantly? Just calculate it as function of time? 

If you want to be fancy, it could be incremented every time you see mdns probe+announce steps occur, but someone may silently join or leave anyway so it wouldn’t be correct always at any rate. 

Cheers,

-Markus

[dnssd] Hybrid Proxy SOA records Tom Pusateri
Re: [dnssd] Hybrid Proxy SOA records Markus Stenberg
Re: [dnssd] Hybrid Proxy SOA records Tom Pusateri