Re: question on RDNSS, RFC 6106 part 5.1

2012-05-15 Thread Dan Luedtke
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 distributed over the campus, all merged into one network. Let's

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
I believe Fernando will forgive me. For the curious, an *unofficial* version of our work can be found here: http://git.pavlix.net/gitweb/?p=rdnss.git;a=summary Cheers, Pavel On Mon, 2012-05-14 at 15:37 +0300, Teemu Savolainen wrote: Hi, So how do we proceed from here? Would it be

Re: question on RDNSS, RFC 6106 part 5.1

2012-05-14 Thread Teemu Savolainen
Hi, So how do we proceed from here? Would 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
Hello, my proposition is the same as Teemu's or very similar. 1) I propose to change the default Lifetime from [MaxRtrAdvInterval, 2*MaxRtrAdvInterva] to a single agreed-upon recommended default value. Almost nobody would need to change this default value. 5*MaxRtrAdvInterval is IMO a good

Re: question on RDNSS, RFC 6106 part 5.1

2012-04-27 Thread Pavel Simerda
Hello, my proposition is the same as Teemu's or very similar. 1) I propose to change the default Lifetime from [MaxRtrAdvInterval, 2*MaxRtrAdvInterva] to a single agreed-upon recommended default value. Almost nobody would need to change this default value. 5*MaxRtrAdvInterval is IMO a good

Re: question on RDNSS, RFC 6106 part 5.1

2012-04-26 Thread Teemu Savolainen
Hi, We have seen this same problem as well. Does anyone have any idea why the lifetime is bound with SHOULD to this very short time period? For example, if the Lifetime == MaxRtrAdvInterval, a host often would effectively be forced to send RS to refresh the RDNSS information before RDNSS

Re: question on RDNSS, RFC 6106 part 5.1

2012-04-26 Thread Ole Trøan
Pavel, I concur with your description of the problem. do you have a proposal for how it can be solved? Best regards, Ole On Apr 19, 2012, at 23:32 , Pavel Šimerda wrote: Hello, I'm starting my work on linux NetworkManager. I've been following several bugreports during the recent months

question on RDNSS, RFC 6106 part 5.1

2012-04-19 Thread Pavel Šimerda
Hello, I'm starting my work on linux NetworkManager. I've been following several bugreports during the recent months that all lead to problems with maintaining the list of recursive nameservers. I've already spent quite some time analyzing RDNSS problems and I came to a conclusion that the