[DNSOP] I-D Action: draft-ietf-dnsop-svcb-httpssvc-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Service binding and parameter specification via the DNS (DNS SVCB and HTTPSSVC) Authors : Ben Schwartz Mike Bishop Erik Nygren Filename: draft-ietf-dnsop-svcb-httpssvc-01.txt Pages : 35 Date: 2019-11-04 Abstract: This document specifies the "SVCB" and "HTTPSSVC" DNS resource record types to facilitate the lookup of information needed to make connections for origin resources, such as for HTTPS URLs. SVCB records allow an origin to be served from multiple network locations, each with associated parameters (such as transport protocol configuration and keying material for encrypting TLS SNI). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPSSVC DNS RR is a variation of SVCB for HTTPS and HTTP origins. By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy. TO BE REMOVED: This proposal is inspired by and based on recent DNS usage proposals such as ALTSVC, ANAME, and ESNIKEYS (as well as long standing desires to have SRV or a functional equivalent implemented for HTTP). These proposals each provide an important function but are potentially incompatible with each other, such as when an origin is load-balanced across multiple hosting providers (multi-CDN). Furthermore, these each add potential cases for adding additional record lookups in-addition to /A lookups. This design attempts to provide a unified framework that encompasses the key functionality of these proposals, as well as providing some extensibility for addressing similar future challenges. TO BE REMOVED: The specific name for this RR type is an open topic for discussion. "SVCB" and "HTTPSSVC" are meant as placeholders as they are easy to replace. Other names might include "B", "SRV2", "SVCHTTPS", "HTTPS", and "ALTSVC". The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-httpssvc/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dnsop-svcb-httpssvc-01 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-svcb-httpssvc-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-svcb-httpssvc-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] I-D Action: draft-ietf-dnsop-server-cookies-01.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : Interoperable Domain Name System (DNS) Server Cookies Authors : Ondrej Sury Willem Toorop Donald E. Eastlake 3rd Mark Andrews Filename: draft-ietf-dnsop-server-cookies-01.txt Pages : 15 Date: 2019-11-04 Abstract: DNS cookies, as specified in RFC 7873, are a lightweight DNS transaction security mechanism that provides limited protection to DNS servers and clients against a variety of denial-of-service and amplification, forgery, or cache poisoning attacks by off-path attackers. This document provides precise directions for creating Server Cookies so that an anycast server set including diverse implementations will interoperate with standard clients. This document updates [RFC7873] The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-server-cookies/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dnsop-server-cookies-01 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-server-cookies-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-server-cookies-01 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] I-D Action: draft-ietf-dnsop-no-response-issue-14.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain Name System Operations WG of the IETF. Title : A Common Operational Problem in DNS Servers - Failure To Communicate. Authors : M. Andrews Ray Bellis Filename: draft-ietf-dnsop-no-response-issue-14.txt Pages : 26 Date: 2019-11-04 Abstract: The DNS is a query / response protocol. Failing to respond to queries, or responding incorrectly, causes both immediate operational problems and long term problems with protocol development. This document identifies a number of common kinds of queries to which some servers either fail to respond or else respond incorrectly. This document also suggests procedures for zone operators to apply to identify and remediate the problem. The document does not look at the DNS data itself, just the structure of the responses. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-no-response-issue/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-dnsop-no-response-issue-14 https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-no-response-issue-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dnsop-no-response-issue-14 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] Fwd: New Version Notification for draft-pusateri-dnsop-update-timeout-04.txt
Tim and I have updated the TIMEOUT RR draft to reflect the feedback we’ve received on this list and added some more description and usage patterns, including interaction with the EDNS(0) Update Lease option, and a discussion of absolute vs. relative timeout values. Thanks, Tom & Tim Begin forwarded message: > From: internet-dra...@ietf.org > Date: November 4, 2019 at 11:27:25 AM EST > To: Tim Wattenberg , Tom Pusateri > Subject: New Version Notification for > draft-pusateri-dnsop-update-timeout-04.txt > > > A new version of I-D, draft-pusateri-dnsop-update-timeout-04.txt > has been successfully submitted by Tim Wattenberg and posted to the > IETF repository. > > Name:draft-pusateri-dnsop-update-timeout > Revision:04 > Title:DNS TIMEOUT Resource Record > Document date:2019-11-04 > Group:Individual Submission > Pages:17 > URL: > https://www.ietf.org/internet-drafts/draft-pusateri-dnsop-update-timeout-04.txt > Status: > https://datatracker.ietf.org/doc/draft-pusateri-dnsop-update-timeout/ > Htmlized: > https://tools.ietf.org/html/draft-pusateri-dnsop-update-timeout-04 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout > Diff: > https://www.ietf.org/rfcdiff?url2=draft-pusateri-dnsop-update-timeout-04 > > Abstract: > This specification defines a new DNS TIMEOUT resource record (RR) > that associates a lifetime with one or more zone resource records. > It is intended to be used to transfer resource record lifetime state > between a zone's primary and secondary servers and to store lifetime > state during server software restarts. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
[DNSOP] Protocol Action: 'Moving DNSSEC Lookaside Validation (DLV) to Historic Status' to Proposed Standard (draft-ietf-dnsop-obsolete-dlv-02.txt)
The IESG has approved the following document: - 'Moving DNSSEC Lookaside Validation (DLV) to Historic Status' (draft-ietf-dnsop-obsolete-dlv-02.txt) as Proposed Standard This document is the product of the Domain Name System Operations Working Group. The IESG contact persons are Warren Kumari and Ignas Bagdonas. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-dnsop-obsolete-dlv/ Technical Summary This document obsoletes DNSSEC lookaside validation (DLV) and reclassifies RFCs 4431 and 5074 as Historic. It is a supporting document for https://datatracker.ietf.org/doc/status-change-dlv-to-historic/status-change/last-call/ Working Group Summary WG consensus was strong. Document Quality This document is in support of https://datatracker.ietf.org/doc/status-change-dlv-to-historic/ Personnel Document Shepherd: Tim Wicinski Area Director: Warren Kumari ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
