Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cf-dev] PR for Issue #1 
Simon,

Thanks for your reply. As always your input is very substantial and reasonable :-)

> 1) I mean this will make the "DTLS session" clustering necessary to implement the "observe" clustering.[1] And that was not the case before.

However, we will still need to re-factor Californium to be able to share (some of) the Exchange, right?

> 2) Finally with my current knowledge of the TLS spec, I think there is no way to have the same sessionID and a different cipher, am I wrong ?

Since the session ID is created by the server and is unique I tend to agree with you :-)

> 3) Maybe the "permissive" mode should only be based on peer Identity
> (Principal) (+ eventually the cipher), this probably safer than just using the token and this allow to start implementing "observe clustering" without "DTLS > session" clustering.

So, you are assuming that a client will use the same credentials and cipher suite to re-connect to the new DTLS node after the original one has crashed, right? That seems to be a fair assumption and I cannot immediately see why a client should do otherwise.



Le 19/02/2016 17:04, Hudalla Kai (INST/ESY1) a écrit :
> No problem, I just wanted to wake you guys up ;-)
>
> Yes, the new matching should go into 1.1.0 and is thus on master only. Master currently serves as "1.1.x" until we need to branch off explicitly because we want to start to work on 2.0 (API breaking) features on master. If we need a 1.0.3 we can do that on the existing 1.0.x branch.
>
> Regards,
> Kai
>
>
> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] 
> On Behalf Of Kovatsch Matthias
> Sent: Friday, February 19, 2016 4:38 PM
> To: Californium (Cf) developer discussions
> Subject: Re: [cf-dev] PR for Issue #1
>
> I am also thrown behind schedule by a cold. Thus, I did not have the time to check the mechanism.
>
> Connected with the merging: I assume the master is now the effective "master-1.1.x" and we only start renaming and branching once there is need for a 1.0.3 hotfix or we start 2.x work? This new matching should definitely go into 1.1.x.
>
> Ciao
> Matthias
>
>   
>> -----Original Message-----
>> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of Simon Bernard
>> Sent: Freitag, 19. Februar 2016 15:12
>> To: Californium (Cf) developer discussions <cf-dev@xxxxxxxxxxx>
>> Subject: Re: [cf-dev] PR for Issue #1
>>
>> I planned to take a look as soon as I finish my current tasks. (Sry I 
>> guess I should said that earlier) Simon
>>
>> Le 19/02/2016 14:22, Hudalla Kai (INST/ESY1) a écrit :
>>> Obviously nobody has any comments nor concerns. I will thus merge 
>>> the PR
>> now ...
>>> Kai
>>>
>>> -----Original Message-----
>>> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
>>> On Behalf Of Hudalla Kai (INST/ESY1)
>>> Sent: Monday, February 15, 2016 5:39 PM
>>> To: Californium (Cf) developer discussions
>>> Subject: [cf-dev] PR for Issue #1
>>>
>>> Hi,
>>>
>>> I have created a PR [1] addressing issue #1 [2] (Request/Response
>> matching considering DTLS session/epoch).
>>> We recently had a discussion about this issue and how we could 
>>> address it on the mailing list so I'd be glad if you could take a 
>>> look and provide some feedback ... (that also includes you, Matthias
>>> :-))
>>>
>>> [1] https://github.com/eclipse/californium/pull/10
>>> [2] https://github.com/eclipse/californium/issues/1
>>>
>>> Regards,
>>> Kai
>>>
>>> _______________________________________________
>>> cf-dev mailing list
>>> cf-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or 
>>> unsubscribe from this list, visit 
>>> https://dev.eclipse.org/mailman/listinfo/cf-dev
>>> _______________________________________________
>>> cf-dev mailing list
>>> cf-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or 
>>> unsubscribe from this list, visit 
>>> https://dev.eclipse.org/mailman/listinfo/cf-dev
>> _______________________________________________
>> cf-dev mailing list
>> cf-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or 
>> unsubscribe from this list, visit 
>> https://dev.eclipse.org/mailman/listinfo/cf-dev
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/cf-dev
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or 
> unsubscribe from this list, visit 
> https://dev.eclipse.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev

Back to the top