协议开发

[RFC7258] Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, May 2014, [https://www.rfc-editor.org/info/rfc7258](https://www.rfc-editor.org/info/rfc7258).

[RFC7413] Cheng, Y., Chu, J., Radhakrishnan, S., and A. Jain, "TCP Fast Open", RFC 7413, DOI 10.17487/RFC7413, December 2014, [https://www.rfc-editor.org/info/rfc7413](https://www.rfc-editor.org/info/rfc7413).

[RFC7828] Wouters, P., Abley, J., Dickinson, S., and R. Bellis, "The edns-tcp-keepalive EDNS0 Option", RFC 7828, DOI 10.17487/RFC7828, April 2016, [https://www.rfc-editor.org/info/rfc7828](https://www.rfc-editor.org/info/rfc7828).

[RFC7830] Mayrhofer, A., "The EDNS(0) Padding Option", RFC 7830, DOI 10.17487/RFC7830, May 2016, [https://www.rfc-editor.org/info/rfc7830](https://www.rfc-editor.org/info/rfc7830).

[RFC7858] Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., and P. Hoffman, "Specification for DNS over Transport Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, May 2016, [https://www.rfc-editor.org/info/rfc7858](https://www.rfc-editor.org/info/rfc7858).

[RFC8467] Mayrhofer, A., "Padding Policies for Extension Mechanisms for DNS (EDNS(0))", RFC 8467, DOI 10.17487/RFC8467, October 2018, [https://www.rfc-editor.org/info/rfc8467](https://www.rfc-editor.org/info/rfc8467).



Appendix A. Protocol Development

This appendix describes the requirements used to design DoH. These requirements are listed here to help readers understand the current protocol, not to limit how the protocol might be developed in the future. This appendix is non-normative.

The protocol described in this document based its design on the following protocol requirements: