On 2 Mar 2016, at 2:05, Davey Song wrote:
For pure "Aesthetics" reason, If I was designing a toy protocol or a
custom
tool, then I might insist on GET. but I should choose POST to work
around
broken software and proxy in the networks.
Just to be clear: it's not just aesthetics. There are many other systems
that make the assumptions about GET and POST.
We talked about this in Yokohama. Your design is "I want to put the
message in the body" instead of "I can easily encode the request as a
URL". If you want this protocol to be standardized in the IETF, you
really should consider the decades of work that have gone into HTTP by a
community much larger than the DNS community, and use that community's
long-standardized semantics.
--Paul Hoffman
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
