Re: IETF Last Call review: changes suggested

Julian Reschke schrieb:
>>> - similarly, if it changes its mind and decided to not create the
>>>   resource, it needs to use DELETE instead of UNLOCK
> 
> No, it doesn't.

I was misreading "DELETE instead of UNLOCK". Of course UNLOCK can be 
used, but it will leave the newly created resource there. Yes, that's a 
change, and to completely get rid of the resource an additional DELETE 
(or a DELETE instead of UNLOCK) is needed.

But that's an edge case. Do we really need additional spec text for that?

Best regards, Julian