[Dots] Signal Channel 4.5.3 Configuration Freshness and Notifications

["Jon Shallow" <[e-mail]>]

Hi there,

 

I think that a GET request needs to be added into the following (OLD) text
to support a DOTS server configuration change getting to the DOTS client
when Max-Age expires, otherwise the DOTS client will override the DOTS
server configuration with the PUT of the old (pre configuration change)
values.

 

OLD

4.5.3.  Configuration Freshness and Notifications

 

   Max-Age Option (Section 5.10.5 of [RFC7252]) SHOULD be returned by a

   DOTS server to associate a validity time with a configuration it

   sends.  This feature allows the update of the configuration data if a

   change occurs at the DOTS server side.  For example, the new

   configuration may instruct a DOTS client to cease heartbeats or

   reduce heartbeat frequency.

..

   If a non-zero value of Max-Age Option is received by a DOTS client,

   it MUST issue a PUT request to refresh the configuration parameters

   for the signal channel before the expiry of the value enclosed in the

   Max-Age option.  When a DDoS attack is active, refresh requests MUST

   NOT be sent by DOTS clients and the DOTS server MUST NOT terminate

   the (D)TLS session after the expiry of the value returned in Max-Age

   Option.

 

NEW

4.5.3.  Configuration Freshness and Notifications

 

   Max-Age Option (Section 5.10.5 of [RFC7252]) SHOULD be returned by a

   DOTS server to associate a validity time with a configuration it

   sends.  This feature allows the update of the configuration data if a

   change occurs at the DOTS server side.  For example, the new

   configuration may instruct a DOTS client to cease heartbeats or

   reduce heartbeat frequency.

..

   If a non-zero value of Max-Age Option is received by a DOTS client,

   it first MUST do a GET to retrieve the current notion of the DOTS
server's configuration, and then 

   it MUST issue a PUT request to refresh the configuration parameters

   for the signal channel before the expiry of the value enclosed in the

   Max-Age option.  When a DDoS attack is active, refresh requests MUST

   NOT be sent by DOTS clients and the DOTS server MUST NOT terminate

   the (D)TLS session after the expiry of the value returned in Max-Age

   Option.

 

 

Or should it be that a GET causes the DOTS server to refresh its internal
remaining lifetime of the signal configuration and there is no need to do
the PUT refresh?

[This would be akin to requesting the time of a clock, it returns the
current time with a Max-Age of 1 (second), so the next time GET would be
have to be done a second later to get the new values.]

 

Regards

 

Jon