6MAN WG Last Call:

2012-04-26 Thread Bob Hinden
All, This message starts a two week 6MAN Working Group last call on advancing: Title : Duplicate Address Detection Proxy Author(s) : Fabio Costa Xavier Pougnard Hongyu Li Jean-Michel Comb

Re: 6MAN Minutes, Actions, and Document Status

2012-04-26 Thread Fernando Gont
Hi, Ole, On 04/26/2012 08:50 AM, Ole Trøan wrote: >> I think that draft-gont-6man-predictable-fragment-id is also ready >> for wg call for adoption as wg document -- I've rev'ed the >> document since IETF 83 in response to the feedback received during >> my presentation (i.e., just require the Fr

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 month

Re: 6MAN Minutes, Actions, and Document Status

2012-04-26 Thread Ole Trøan
Fernando, [...] > Some errata for the minutes: > > The current text says: > cut here > Ole asked about how this was different from an unknown L4 header? > > > cut here > > There was an answer, so "" should probably be replaced with > something along the lines of "Fernando

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 expirati