Re: question on RDNSS, RFC 6106 part 5.1

2012-05-15 Thread Pavel Simerda
On Tue, 2012-05-15 at 09:47 +0200, Dan Luedtke wrote: Since then, router solicitations would be issued regularly until client recieves RA with RDNSS, connection is cancelled by user or: We have a setup here were we have 50+ clients on some access points with about 100 access points

Re: question on RDNSS, RFC 6106 part 5.1

2012-05-15 Thread Pavel Simerda
it be enough to discuss and agree an errata for the RFC? Doing full RFC6106bis might be overkill. Chairs? Best regards, Teemu 2012/4/27 Pavel Simerda pav...@pavlix.net Hello, my proposition is the same as Teemu's or very similar. 1) I propose

Re: question on RDNSS, RFC 6106 part 5.1

2012-04-27 Thread Pavel Simerda
is quite new. There is an open question, when to consider RDNSS information lost. It could be: 1) Last RDNSS from RAs expired. 2) Last IPv6 RDNSS expired (RDNSS or DHCPv6) 3) Last RDNSS lost (IPv6 or IPv4) Pavel Simerda On Thu, 2012-04-26 at 14:00 +0200, Ole Trøan wrote: Pavel, I concur with your

Re: question on RDNSS, RFC 6106 part 5.1

2012-04-27 Thread Pavel Simerda
is quite new. There is an open question, when to consider RDNSS information lost. It could be: 1) Last RDNSS from RAs expired. 2) Last IPv6 RDNSS expired (RDNSS or DHCPv6) 3) Last RDNSS lost (IPv6 or IPv4) Pavel Simerda On Thu, 2012-04-26 at 14:00 +0200, Ole Trøan wrote: Pavel, I concur with your