Re: [Last-Call] Opsdir last call review of draft-ietf-6man-comp-rtg-hdr-05

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Sue,

All good catches! Thanks for the review.

                                          Ron


Juniper Business Use Only


From: Susan Hares via Datatracker <noreply@xxxxxxxx>
Sent: Tuesday, April 30, 2024 9:39 AM
To: ops-dir@xxxxxxxx <ops-dir@xxxxxxxx>
Cc: draft-ietf-6man-comp-rtg-hdr.all@xxxxxxxx <draft-ietf-6man-comp-rtg-hdr.all@xxxxxxxx>; ipv6@xxxxxxxx <ipv6@xxxxxxxx>; last-call@xxxxxxxx <last-call@xxxxxxxx>
Subject: Opsdir last call review of draft-ietf-6man-comp-rtg-hdr-05
 
[External Email. Be cautious of content]


Reviewer: Susan Hares
Review result: Has Nits

This is an OPS-DIR Last Call review.

This review should be considered as one of the Last Call comments

Status: Ready with Nits

General Comment: I commend the authors for writing up the requirements for this
experiment with compressed routing headers. I look forward for reports on this
experiment.

NITs:
1.  Abstract:
Why: English Grammar - Clarity of sentence

Current text:/
   Another purpose is
   to demonstrate that the security considerations, described in this
   document, can be addressed with access control lists. /

Suggested alternate text:/
    Another purpose is to demonstrate that access control lists can address
    security considerations described in this
   document. /

#2. Section 1, paragraph 3.
Why: Grammar, Sentence punctuation and clarity

Old text:/
   This document describes an experiment whose purposes are:
   *  To demonstrate that the CRH can be implemented and deployed.
   *  To demonstrate that the security considerations, described in this
      document, can be addressed with access control lists.
   *  To encourage replication of the experiment./

New text:/
   This document describes an experiment whose purposes are:
   *  To demonstrate that the CRH can be implemented and deployed,
   *  to demonstrate that access control lists can address the
      security considerations described in this document, and
   *  To encourage replication of the experiment. /

#NIT 3: Section 10, Textual Representation

Description of problem: This section does not inform the reader why the textual
representation description is needed.

Possible text to be added to section 9 or 10:/
    PING and TRACEROUTE report 16-bit SIDS for CRH-16, and
    32-bit SIDS for CRH-32.  It is recommended that the
    experimental reports use the text representations
    described below./


-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux