Re: [Detnet] WG Last Call: draft-ietf-detnet-bounded-latency-02

Dear All,
I've read the current version of the draft and support progressing it to
the publication as the Informational RFC.
I have several non-blocking comments and questions for the author's
consideration:

   - In Abstract and Introduction "server" and "central server" referenced.
   Could it be used to identify an SDN controller or orchestrator? If that is
   the case or close, perhaps a more direct terminology can be used.
   - Perhaps s/un-provisioning/de-provisioning/?
   - It's been quite a long time since I've seen a network device being
   referenced as "bridge". If there's no difference modeling different types
   of networking devices in Section 3.2, perhaps "typically, bridges or
   routers" can be omitted.
   - And in the same sentence, a part of the reference model is described
   as "a wired link". Could that be some other media, e.g., wireless?
   - you may choose to use a single term from "DetNet unaware", "DetNet
   non-aware", and "non-DetNet"
   - the statement in the second paragraph's  first sentence appears very
   assertive:

   In general, when passing through a non-DetNet island, the island
   causes delay variation in excess of what would be caused by DetNet
   nodes.

I agree that under some conditions such a domain might cause higher delay
variation but I am not sure that is always the case.

   - Further in that paragraph, is stated that "... can still be calculated
   and met if and only if the following are true" though the second bullet
   appears as a conditional "An ingress conditioning function (Section 4.3)
   may be required ...". I am not sure it is clear when that second bullet is
   true - if the conditioning function is required or if it is not needed.

Regards,
Greg

On Fri, Feb 5, 2021 at 5:30 AM Lou Berger <lberger@labn.net> wrote:

> All,
>
> This starts working group last call on draft-ietf-detnet-bounded-latency-02
> https://datatracker.ietf.org/doc/draft-ietf-detnet-bounded-latency/
>
> The working group last call ends on February 19th.
> Please send your comments to the working group mailing list.
>
> Please note, there was an IPR disclosure against this document
> submitted on January 14, 2021, see https://datatracker.ietf.org/ipr/4581/
> While this disclosure came very late in the document life cycle,
> it appears the filing was also relatively recent (2019-10-16) and
> after the pre adoption IP call:
> https://mailarchive.ietf.org/arch/msg/detnet/1mwYdadDzTLudcuH5T5O7R_KlDs
>
> Positive comments, e.g., "I've reviewed this document
> and believe it is ready for publication", are welcome!
> This is useful and important, even from authors.
>
> Thank you,
> Lou (DetNet Co-Chair & doc Shepherd)
>
>
>
> _______________________________________________
> detnet mailing list
> detnet@ietf.org
> https://www.ietf.org/mailman/listinfo/detnet
>