Device Reset Characterization
RFC 6201
Yes
No Objection
Note: This ballot was opened for revision 06 and is now closed.
Lars Eggert No Objection
(Ron Bonica; former steering group member) Yes
(Adrian Farrel; former steering group member) (was Discuss) No Objection
"BMWG" is used without expansion. --- Section 3 In order to provide consistent and fairness s/constistent/consistence/
(Dan Romascanu; former steering group member) No Objection
(Gonzalo Camarillo; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
I have no issues with this document, but Ari Keränen found some small
problems in his review:
2.2. Recovery Time Measurement Methods
There are two accepted methods to measure the 'recovery time':
Is the meaning of "accepted" as in "no other method SHOULD be used" or
as in "currently widely used" (or something else)?
4.2. Software Reset Test
A software reset is initiated for example from the DUT's Command
Line Interface (CLI).
The CLI abbreviation is used already in Section 4.1. Would make sense to
move the expanded form there.
The second part of the test "Procedure" (6 lines of text) seems to be
identical for all the test cases. Perhaps this text could be in the
draft just once and have that single instance referenced in the test
case descriptions.
(Peter Saint-Andre; former steering group member) No Objection
(Ralph Droms; former steering group member) No Objection
(Robert Sparks; former steering group member) No Objection
(Russ Housley; former steering group member) (was Discuss) No Objection
(Sean Turner; former steering group member) No Objection
(Stewart Bryant; former steering group member) (was Discuss) No Objection
(Tim Polk; former steering group member) No Objection