I don’t see why the voucher actually has to be expired before obtaining a refresh. The creation time would of course be updated.
Michael’s point that a Registrar could use this to force the MASA to perform crypto operations is valid. As implied the fix is to allow the MASA to simply return a current voucher (database lookup but less crypto) if that is more expedient. I suggest we leave that up to the MASA implementors. - max > On Oct 23, 2017, at 8:18 AM, Michael Richardson <[email protected]> wrote: > > > Kent Watsen <[email protected]> wrote: >> i don’t see why not, but wouldn’t the creation time be different? > > Yes, the creation time ought to be different, but I think it's okay if it's > the same. If the voucher has no expiry time, then this can be done for as > long as the nonce is the same. > > I think that if the expiry time is <6hr then probably a new voucher needs to > be issued. The goal here is to mitigate against crypto-intensive DoS > attacks, while still dealing with situations where a transfer may have > aborted, or something bad happened to a registrar and it has to retry. > > -- > Michael Richardson <[email protected]>, Sandelman Software Works > -= IPv6 IoT consulting =- > > > _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
