thomas-fossati / draft-tls13-iot

Other
0 stars 1 forks source link

RRC timer considerations #18

Closed thomas-fossati closed 4 months ago

thomas-fossati commented 2 years ago

RRC defines a timer value associated with the path validation algorithm with a default value of 1s. This may not be OK in certain IoT settings - for example, observed RTTs in NB-IoT are ~2.5s. We need to work out whether there is any guidance we can provide in this area.

OR13 commented 1 year ago

Perhaps a case analysis?

When is this timing issue a problem, when is it not?

hannestschofenig commented 4 months ago

Thomas and I will chat with Achim. Will use RRC implementation on NBIOT for some numbers

thomas-fossati commented 4 months ago

Thomas and I will chat with Achim. Will use RRC implementation on NBIOT for some numbers

@boaks you have been summoned :-)

boaks commented 4 months ago

When is this timing issue a problem, when is it not?

There are usually also other timers, which are also not negotiated. And depending on the transmission layer (since a couple of days a had the chance to get some very first impression for NB-IoT via satellite) even those 2.5s are much to less (10-15s). So FMPOV, it will require anyway a "configuration" for a lot of cases. The "default" seems for me to be therefore not that important.

thomas-fossati commented 4 months ago

Thanks Achim! We'll work on incorporating your suggestions.