Mališa Vučinić wrote:
> This text should end up in the next version of the MSF draft, as it is
> the scheduling function that triggers 6P to add/delete cells. We added
> some text on it already for the security considerations, what remains
> to be done is to align the MSF
This text should end up in the next version of the MSF draft, as it is the
scheduling function that triggers 6P to add/delete cells. We added some text on
it already for the security considerations, what remains to be done is to align
the MSF algorithm with the requirement of not adapting to
Mirja Kuehlewind wrote:
>>> I would think it
>>> either sets it to AF43 or it does nothing about it because DSCP is not
>>> really used in that network.
>>
>> In 6tisch networks, different DSCP points can be used to get different
>> behaviours, see UHM. Let me get
Mirja Kuehlewind wrote:
> Sorry for my late reply (but I guess you could have just went ahead and
> push a new version anyway…). Please see below.
My edits went into a new version which Malisa did push out.
>>
>>
>>> Further on there seems to be an implicit requirement that
Regards,
Pascal
> Le 5 déc. 2019 à 04:06, Mirja Kuehlewind a écrit :
>
> Hi Michael,
>
> Sorry for my late reply (but I guess you could have just went ahead and push
> a new version anyway…). Please see below.
>
>>> On 1. Nov 2019, at 22:15, Michael Richardson wrote:
>>>
>>>
>>>
Just a quick note on this as I am going through the mails in preparation for
the WG meeting:
The intended text was to state that the provisioning of the network identifier
is RECOMMENDED for the pledge, while it is a MUST for the *6LBR* pledge. The
distinction between 6LBR pledge and pledge is
<#secure method=pgpmime mode=sign>
Mirja Kühlewind via Datatracker wrote:
> 1) I hope this point can be resolved quickly as it seems to only need a
> bit more specifics but I think this part is not sufficient:
> Sec 6.1: "The Join Proxy implements a data cap on outgoing join
Mirja Kühlewind has entered the following ballot position for
draft-ietf-6tisch-minimal-security-13: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
