Patrick,
You are right and I share your surprise and doubts, about both update and
transfer. update has been removed, transfer is still in the draft.
This should not come as a surprise to anyone since it has been discussed on the
list and there was no request or agreement to remove it. The two messages that
you reference were formally responded to and any agreed upon changes to the
draft were incorporated. This included removing support for use of the
allocation token as an extension to the empty update.
My response to Alex's message:
https://mailarchive.ietf.org/arch/msg/regext/li8PEBXddEWE-OfbC1ViK4TBzTk
My response to your message:
https://mailarchive.ietf.org/arch/msg/regext/uS8L-1DC4eQskcSPI-Bs4aSMp0Y
I certainly don't recommend allocation via the transfer, but I'm aware of use
cases where it has been done. It is not the place for the protocol to dictate
the policy. If you feel that it must be removed, please make a formal request
to the list for it's removal and the list can discuss it.
Thanks,
—
JG
James Gould
Distinguished Engineer
jgo...@verisign.com
703-948-3271
12061 Bluemont Way
Reston, VA 20190
Verisign.com <http://verisigninc.com/>
On 4/13/18, 10:50 PM, "regext on behalf of Patrick Mevzek"
<regext-boun...@ietf.org on behalf of p...@dotandco.com> wrote:
On Fri, Apr 13, 2018, at 11:05, Pieter Vandepitte wrote:
> Short question: what's the purpose of an allocation token within a
> transfer command (and what's the difference with authInfo code)? I
> understand the purpose in case of create and I can imagine some use
> cases for update, but even for update, I have my doubts.
You are right and I share your surprise and doubts, about both update and
transfer. update has been removed, transfer is still in the draft.
> I'm sorry if this question has been asked in the past, but Google
> doesn't appear to be my friend today ;-)
The same area of concerns were raised at least by Alexander Mayrhofer here:
https://mailarchive.ietf.org/arch/msg/regext/HgPkOGl0rVNwVZ9L8_37U1uS76o
and previously by myself here:
https://mailarchive.ietf.org/arch/msg/regext/LnvUUbjWzdez1MyHKDbPwkoywt0
and the threads following them.
--
Patrick Mevzek
p...@dotandco.com
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
