Hi, Some comments as shepherd.
> Minor issues: > > 4.2.2, 2nd to last paragraph: "It is up to implementations to ensure > that such > a reset does not go undetected, for example by requesting operator > acknowledgment when a reset is performed upon reboot." > > Does this imply a normative requirement? > > <ALEX> > No, this is not a normative requirement - how to deal with this issue > will be implementation specific. > We discussed this on the mailing list using a printer as an example. > The WG consensus was that a printer would likely signal to an > operator via a text message on the display, a blinking light, or > perhaps by some other means. Since we don't want the printer to > not function while waiting for any response from an operator, it's > just a suggestion. > </ALEX> I agree this sounds normative. It might be better to say "Implementations SHOULD ensure that such a reset does not go undetected." > -- Section 10, working group mail list: > > Is this address sufficiently long-lived to be a contact point in an The guidance can be found in <http://www.ietf.org/id-info/guidelines.html> http://www.ietf.org/id-info/guidelines.html Note the the recharetr is only for about six months, so that's not a good basis for assuming a long-lived adddress. I expect we will keep the list open even after the WG closes, to accommodate comments and questions, per the guidance. dbh
_______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
