On Mon, Sep 28, 2015 at 12:01 PM, Richard Barnes <[email protected]> wrote:
> Dear WG, > <https://github.com/ietf-wg-acme/acme/pull/7> > * "Add explicit versioning to challenges" - > https://github.com/ietf-wg-acme/acme/pull/8 > > I'm not sure this quite right. If I understand the proposal correctly, when a client sees http-01 but understands only http-00, the idea that one is related to the other has no meaning, as the client can only respond to challenges when type and version match what it has code for, right? I think if we want that behavior, we'll need to specify whether a single array can have array entries with different versions of the same challenge type and we'll need to ensure that the same challenge type with different versions isn't used to create full coverage. That is, if it's okay for a challenge to be something like "Fulfil HTTP challenge version 0 and DNS challenge version 1 OR HTTP challenge version 1 and DNS challenge version 0"", then we should say so. I also think we need to explicitly rule out things like "Fulfil HTTP challenge version 0 and HTTP challenge version 1". (If the latter is okay, we shouldn't call them versions, but treat each iteration as fully semantically distinct). regards, Ted Wearing no hats
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
