Thanks a bunch for clarifying, Dave :
Rev_17 just flew with:
In order to deploy this, network administrators MUST ensure that 6LR/6LBRs
in their network support the number and type of devices that can register to
them, based on the number of IPv6 addresses that those devices require and
their address renewal rate and behavior.
I understand, then, that we are all OK with this : )
Take care,;
pascal
From: 6lo <[email protected]> On Behalf Of Dave Thaler
Sent: mardi 3 avril 2018 19:03
To: Pascal Thubert (pthubert) <[email protected]>; Warren Kumari
<[email protected]>; The IESG <[email protected]>
Cc: [email protected]; Gabriel Montenegro <[email protected]>;
[email protected]; [email protected]
Subject: Re: [6lo] Warren Kumari's No Objection on
draft-ietf-6lo-rfc6775-update-16: (with COMMENT)
> I'm somewhat uncomfortable with the uppercase MUST in:
> "A network administrator MUST deploy updated 6LR/6LBRs to support the
> number and type of devices in their network, ..." Having an uppercase
> MUST driving operators' design decisions stuff feels weird. I'd be
> perfectly fine with something like "In order to deploy this, network
> administrators MUST..." or "Network Administrators need to ensure that
> 6LR/6LBRs support the number and..."
>
[PT>] This MUST comes from rev-14, based on Dave Thaler's review
(https://www.microsoft.com/en-us/research/uploads/prod/2017/05/draft-ietf-6lo-rfc6775-update-11.pdf)
I'm not too keen on rolling back the uppercase, cc'ing Dave to validate.
My comment was about the use of lower case “should” which was ambiguous. I
asked if you meant SHOULD or MUST.
I’m fine with any unambiguous answer. Warren’s wordings above are fine, as is
the one you ask about below.
What about:
"
In order to deploy this, network administrators MUST ensure that 6LR/6LBRs
in their network support the number and type of devices that can register
to them,
based on the number of IPv6 addresses that those devices require and their
address renewal rate and behavior.
"
Dave
_______________________________________________
6lo mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/6lo
