The draft -43 Section 5.7 (Voucher status telemetry) does not have a CDDL description, nor a reference to it. (Am I looking at the right version?)
In Section 5.9.4 in the CDDL (Fig 18) , was the "reason" field intended to be optional ? It is currently not optional but mandatory so the reason field then must be present also in success cases. In this case please ignore my comment that the example (Fig 19) has the 'reason' field. What is confusing is that in Section 5.7 the reason field looks OPTIONAL for the voucher status telemetry. (Text: " The version and status fields MUST be present. The Reason field SHOULD be present whenever the status field is false." ) Why not have the same / similar CDDL for Section 5.7 and thus make the Reason field mandatory? That would avoid needless variation here and reduce future confusion of implementers. Could you please reopen issue #144 ? ( It looks like I can't do that.) Not all the issues we're discussing are currently addressed by the Github commit. Esko -----Original Message----- From: Michael Richardson <[email protected]> Sent: Friday, September 18, 2020 23:44 To: Esko Dijk <[email protected]> Cc: Fries, Steffen <[email protected]>; [email protected] Subject: Re: [Anima] about moving /.well-known/est/enrollstatus ?? Esko Dijk <[email protected]> wrote: > Note: There are some issues in the current payload definition in BRSKI voucher status and enrollment status, I've created > https://github.com/anima-wg/anima-bootstrap/issues/144 > for these. I think that the "1" -> 1, can be fixed in AUTH48. https://github.com/anima-wg/anima-bootstrap/commit/0830f26eee796624f40e0a0387933e608ebee063 You also complain about successful should not have reasons. That seems like a bigger change, and am not sure it matters. I thought that we have CDDL for both telemetry. > Is any help needed to author these updates? (Or does this need to be > taken up in the errata once we publish as RFC...? I remember that > people want to rather have it published than polished.) -- Michael Richardson <[email protected]>, Sandelman Software Works -= IPv6 IoT consulting =- _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
