| < draft-ietf-dnsop-edns-tcp-keepalive-00.txt | draft-ietf-dnsop-edns-tcp-keepalive-01.txt > | |||
|---|---|---|---|---|
| dnsop P. Wouters | dnsop P. Wouters | |||
| Internet-Draft Red Hat | Internet-Draft Red Hat | |||
| Intended status: Standards Track J. Abley | Intended status: Standards Track J. Abley | |||
| Expires: October 13, 2014 Dyn, Inc. | Expires: April 30, 2015 Dyn, Inc. | |||
| April 11, 2014 | October 27, 2014 | |||
| The edns-tcp-keepalive EDNS0 Option | The edns-tcp-keepalive EDNS0 Option | |||
| draft-ietf-dnsop-edns-tcp-keepalive-00 | draft-ietf-dnsop-edns-tcp-keepalive-01 | |||
| Abstract | Abstract | |||
| DNS messages between clients and servers may be received over either | DNS messages between clients and servers may be received over either | |||
| UDP or TCP. UDP transport involves keeping less state on a busy | UDP or TCP. UDP transport involves keeping less state on a busy | |||
| server, but can cause truncation and retries over TCP. Additionally, | server, but can cause truncation and retries over TCP. Additionally, | |||
| UDP can be exploited for reflection attacks. Using TCP would reduce | UDP can be exploited for reflection attacks. Using TCP would reduce | |||
| retransmits and amplification. However, clients are currently | retransmits and amplification. However, clients are currently | |||
| limited in their use of the TCP transport as RFC 5966 suggests | limited in their use of the TCP transport as RFC 5966 suggests | |||
| closing idle TCP sessions "in the order of seconds", making use of | closing idle TCP sessions "in the order of seconds", making use of | |||
| skipping to change at page 1, line 48 ¶ | skipping to change at page 1, line 48 ¶ | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at http://datatracker.ietf.org/drafts/current/. | Drafts is at http://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on October 13, 2014. | This Internet-Draft will expire on April 30, 2015. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2014 IETF Trust and the persons identified as the | Copyright (c) 2014 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (http://trustee.ietf.org/license-info) in effect on the date of | (http://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 44 ¶ | skipping to change at page 2, line 44 ¶ | |||
| 3.6. Anycast Considerations . . . . . . . . . . . . . . . . . 7 | 3.6. Anycast Considerations . . . . . . . . . . . . . . . . . 7 | |||
| 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 | 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 | |||
| 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 | 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 | 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 | |||
| 7.1. Normative References . . . . . . . . . . . . . . . . . . 8 | 7.1. Normative References . . . . . . . . . . . . . . . . . . 8 | |||
| 7.2. Informative References . . . . . . . . . . . . . . . . . 9 | 7.2. Informative References . . . . . . . . . . . . . . . . . 9 | |||
| Appendix A. Editors' Notes . . . . . . . . . . . . . . . . . . . 9 | Appendix A. Editors' Notes . . . . . . . . . . . . . . . . . . . 9 | |||
| A.1. Venue . . . . . . . . . . . . . . . . . . . . . . . . . . 9 | A.1. Venue . . . . . . . . . . . . . . . . . . . . . . . . . . 9 | |||
| A.2. Abridged Change History . . . . . . . . . . . . . . . . . 9 | A.2. Abridged Change History . . . . . . . . . . . . . . . . . 9 | |||
| A.2.1. draft-ietf-dnsop-edns-tcp-keepalive-00 . . . . . . . 9 | A.2.1. draft-ietf-dnsop-edns-tcp-keepalive-01 . . . . . . . 9 | |||
| A.2.2. draft-wouters-edns-tcp-keepalive-01 . . . . . . . . . 9 | A.2.2. draft-ietf-dnsop-edns-tcp-keepalive-00 . . . . . . . 9 | |||
| A.2.3. draft-wouters-edns-tcp-keepalive-00 . . . . . . . . . 9 | A.2.3. draft-wouters-edns-tcp-keepalive-01 . . . . . . . . . 9 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 | A.2.4. draft-wouters-edns-tcp-keepalive-00 . . . . . . . . . 9 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 | ||||
| 1. Introduction | 1. Introduction | |||
| DNS messages between clients and servers may be received over either | DNS messages between clients and servers may be received over either | |||
| UDP or TCP [RFC1035]. Historically, DNS clients used API's that only | UDP or TCP [RFC1035]. Historically, DNS clients used API's that only | |||
| facilitated sending and receiving a single query over either UDP or | facilitated sending and receiving a single query over either UDP or | |||
| TCP. New APIs and deployment of DNSSEC validating resolvers on hosts | TCP. New APIs and deployment of DNSSEC validating resolvers on hosts | |||
| that in the past were using stub resolving only is increasing the DNS | that in the past were using stub resolving only is increasing the DNS | |||
| client base that prefer using long lived TCP connections. Long-lived | client base that prefer using long lived TCP connections. Long-lived | |||
| TCP connections can result in lower request latency than the case | TCP connections can result in lower request latency than the case | |||
| where UDP transport is used and truncated responses are received, | where UDP transport is used and truncated responses are received, | |||
| since clients that have fallen back to TCP transport in response to a | since clients that have fallen back to TCP transport in response to a | |||
| truncated response typically only uses the TCP session for a single | truncated response typically only uses the TCP session for a single | |||
| skipping to change at page 8, line 42 ¶ | skipping to change at page 8, line 42 ¶ | |||
| The authors acknowledge the contributions of Ray Bellis, Jinmei | The authors acknowledge the contributions of Ray Bellis, Jinmei | |||
| TATUYA and Mark Andrews. | TATUYA and Mark Andrews. | |||
| 7. References | 7. References | |||
| 7.1. Normative References | 7.1. Normative References | |||
| [CHAIN-QUERY] | [CHAIN-QUERY] | |||
| Wouters, P., "chain Query requests in DNS", draft-ietf- | Wouters, P., "chain Query requests in DNS", draft-ietf- | |||
| dnsop-edns-chain-query (work in progress), April 2014. | dnsop-edns-chain-query (work in progress), October 2014. | |||
| [RFC1035] Mockapetris, P., "Domain names - implementation and | [RFC1035] Mockapetris, P., "Domain names - implementation and | |||
| specification", STD 13, RFC 1035, November 1987. | specification", STD 13, RFC 1035, November 1987. | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. | [RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S. | |||
| Rose, "DNS Security Introduction and Requirements", RFC | Rose, "DNS Security Introduction and Requirements", RFC | |||
| 4033, March 2005. | 4033, March 2005. | |||
| skipping to change at page 9, line 36 ¶ | skipping to change at page 9, line 36 ¶ | |||
| Appendix A. Editors' Notes | Appendix A. Editors' Notes | |||
| A.1. Venue | A.1. Venue | |||
| An appropriate venue for discussion of this document is | An appropriate venue for discussion of this document is | |||
| dnsop@ietf.org. | dnsop@ietf.org. | |||
| A.2. Abridged Change History | A.2. Abridged Change History | |||
| A.2.1. draft-ietf-dnsop-edns-tcp-keepalive-00 | A.2.1. draft-ietf-dnsop-edns-tcp-keepalive-01 | |||
| Version bump with no changes | ||||
| A.2.2. draft-ietf-dnsop-edns-tcp-keepalive-00 | ||||
| Clarifications, working group adoption. | Clarifications, working group adoption. | |||
| A.2.2. draft-wouters-edns-tcp-keepalive-01 | A.2.3. draft-wouters-edns-tcp-keepalive-01 | |||
| Also allow clients to specify KEEPALIVE timeout values, clarify | Also allow clients to specify KEEPALIVE timeout values, clarify | |||
| motivation of document. | motivation of document. | |||
| A.2.3. draft-wouters-edns-tcp-keepalive-00 | A.2.4. draft-wouters-edns-tcp-keepalive-00 | |||
| Initial draft. | Initial draft. | |||
| Authors' Addresses | Authors' Addresses | |||
| Paul Wouters | Paul Wouters | |||
| Red Hat | Red Hat | |||
| Email: pwouters@redhat.com | Email: pwouters@redhat.com | |||
| Joe Abley | Joe Abley | |||
| Dyn, Inc. | Dyn, Inc. | |||
| 470 Moore Street | 470 Moore Street | |||
| London, ON N6C 2C2 | London, ON N6C 2C2 | |||
| Canada | Canada | |||
| End of changes. 10 change blocks. | ||||
| 13 lines changed or deleted | 18 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||