
datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/12
Preview meta tags from the datatracker.ietf.org website.
Linked Hostnames
11- 101 links todatatracker.ietf.org
- 9 links towww.ietf.org
- 3 links togithub.com
- 2 links tomailarchive.ietf.org
- 1 link toauthor-tools.ietf.org
- 1 link tostatus.ietf.org
- 1 link totrustee.ietf.org
- 1 link towww.iab.org
Thumbnail

Search Engine Appearance
https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/12
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Bing
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/12
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
DuckDuckGo

Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
General Meta Tags
11- titledraft-ietf-dnsop-svcb-https-12 - Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
- charsetutf-8
- X-UA-CompatibleIE=edge
- viewportwidth=device-width, initial-scale=1
- article:sectionIETF - Internet Engineering Task Force
Open Graph Meta Tags
10- og:titleService Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
- og:urlhttps://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/12/
- og:site_nameIETF Datatracker
- og:descriptionThis document specifies the "SVCB" ("Service Binding") and "HTTPS" DNS resource record (RR) types to facilitate the lookup of information needed to make connections to network services, such as for HTTP origins. SVCB records allow a service to be provided from multiple alternative endpoints, each with associated parameters (such as transport protocol configuration), and are extensible to support future uses (such as keys for encrypting the TLS ClientHello). They also enable aliasing of apex domains, which is not possible with CNAME. The HTTPS RR is a variation of SVCB for use with HTTP (see RFC 9110, "HTTP Semantics"). By providing more information to the client before it attempts to establish a connection, these records offer potential benefits to both performance and privacy.
- og:typearticle
Twitter Meta Tags
1- twitter:cardsummary_large_image
Link Tags
13- alternate/feed/document-changes/draft-ietf-dnsop-svcb-https/
- apple-touch-iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-180.png
- canonicalhttps://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/12/
- iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-32.png
- iconhttps://static.ietf.org/dt/12.44.0/ietf/images/ietf-logo-nor-16.png
Emails
9- ietf%40bemasc.net
- mbishop%40evequefou.be
- erik%2Bietf%40nygren.org
- tjw.ietf%40gmail.com
- warren%40kumari.net
Links
122- https://author-tools.ietf.org/api/idnits?url=https://www.ietf.org/archive/id/draft-ietf-dnsop-svcb-https-12.txt
- https://datatracker.ietf.org
- https://datatracker.ietf.org/accounts/create
- https://datatracker.ietf.org/accounts/login/?next=/doc/draft-ietf-dnsop-svcb-https/12
- https://datatracker.ietf.org/accounts/reset