Esko Dijk <[email protected]> wrote:
    > 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?)

Yes.
I'm about to post -44 which arguably, I should have done after WGLC to rename,
and before IETF LC.   I include CDDL for the voucher status.

    > 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.

You are suggesting that "reason" should be optional.
My code puts something into reason in the success case, but I agree that it
does not need to be there.

    > 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.

Do you mean the enrollstatus should be identical wording to the voucher
status, which says:
   "In the case of a SUCCESS the Reason string is omitted."

I agree that they should be consistent.
So would you like me to write:
   The version and status fields MUST be present.  The Reason field SHOULD be 
present
   whenever the status field is false.
   In the case of a SUCCESS the Reason string MAY be omitted.

This will require an AD blessing, officially.

    > 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.

I've done that.

--
Michael Richardson <[email protected]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




Attachment: signature.asc
Description: PGP signature

_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima

Reply via email to