Hi,
On 12/5/2019 5:17 PM, Tengfei Chang wrote:
Does anyone know other way to make the SF not adapt to unsecured traffic
without knowing upper layer field?
I have no idea...
Why can't the "join rate" avoid such undesired cell allocations? If the
join rate is properly configured, incoming join requests don't cause
such allocations, do they?
https://tools.ietf.org/html/draft-ietf-6tisch-minimal-security-14#section-8.4
o join rate: Average data rate (in units of bytes/second) of join
traffic forwarded into the network that should not be exceeded
when a joined node operates as a JP, encoded as an unsigned
integer.
https://tools.ietf.org/html/draft-ietf-6tisch-minimal-security-14#section-7.2
The PROBING_RATE value at the JP is controlled by the join rate
parameter, see Section 8.4.2. Following [RFC7252], the average data
rate in sending to the JRC must not exceed PROBING_RATE. For
security reasons, the average data rate SHOULD be measured over a
rather short window, e.g. ACK_TIMEOUT, see Section 9.
The recommended PROBING_RATE is 1 byte/second. I'm not sure how to
interpret this value, though.... The time window to calculate the "rate"
should be small enough, I believe.
Best,
Yatch
_______________________________________________
6tisch mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6tisch
