Hi. Just wanted to follow up on one point from yesterday’s EoH presentation in REGEXT. When comparing EoH with DoH, it was noted that both use GET and POST. But there is one important distinction when it comes to BCP 56. DoH correctly falls back to POST if an equivalent GET query gets too large, per BCP 56 (4th para in [1]). In contrast, EoH seems to overload the POST use for PUT and DELETE scenarios, violating BCP 56. IMHO, it does not help to compare EoH with DoH. Guess that’s why the HTTPDIR review [2] recommended HTTP CONNECT instead to avoid the BCP 56 violation.
Not questioning that EoH is a sincere effort to leverage HTTP and already in use, but the BCP 56 violation should give us a pause to re-consider if EoH is a good technical design per What Makes for a Successful Protocol? [3]. Thanks, Jasdip [1] https://www.rfc-editor.org/rfc/rfc9205.html#name-get [2] https://datatracker.ietf.org/doc/review-ietf-regext-epp-https-02-httpdir-early-nottingham-2025-11-30/ [3] https://www.rfc-editor.org/rfc/rfc5218.html#page-11
_______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
