Re: [6tisch] Observe for rekeying (was: Updates to minimal-security-06)

(I just realized that I forgot to CC the 6tisch ML for the previous exchanges.) See below. On Thu, Apr 19, 2018 at 10:55 AM Christian M. Amsüss wrote: > Hi Mališa, > > On Thu, Apr 19, 2018 at 08:24:57AM +, Mališa Vučinić wrote: > > I agree that sending the path

Re: [6tisch] Observe for rekeying (was: Updates to minimal-security-06)

Christian, See inline. Mališa On Thu, Apr 12, 2018 at 3:15 PM Christian M. Amsüss wrote: > > > What would be the advantage of establishing a dynlink over specifying in > > the minimal-security draft that once the pledge joins, it needs to > expose a > > /j resource

Re: [6tisch] Observe for rekeying (was: Updates to minimal-security-06)

On Tue, Apr 10, 2018 at 09:13:23AM +, Mališa Vučinić wrote: > > * Don't observe through the proxy, but establish an observation after > > the address has been assigned. > > > This incurs cost of two additional packages, but is conceptually > > simple and straightforward. > > Yep, so

[6tisch] Observe for rekeying (was: Updates to minimal-security-06)

Hello Mališa, On Fri, Mar 23, 2018 at 10:12:16AM +, Mališa Vučinić wrote: > I am tempted to say that this does not prevent us from updating the client > endpoint (but not the token) based on implicit knowledge at JRC. Do you > agree? observation is fundamentally a hop-to-hop thing