idnits 2.17.1 draft-kuehlewind-quic-proxy-discovery-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC2606-compliant FQDNs in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 169: '...he proxy addresses SHOULD no longer be...' RFC 2119 keyword, line 203: '... means that the proxy addresses SHOULD...' RFC 2119 keyword, line 243: '... means that the proxy addresses SHOULD...' RFC 2119 keyword, line 358: '...erved: 8 bits. MUST be set to 0 on t...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 04, 2019) is 1627 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-11) exists of draft-ietf-intarea-provisioning-domains-08 == Outdated reference: A later version (-02) exists of draft-kuehlewind-quic-substrate-01 Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Kuehlewind 3 Internet-Draft Z. Sarker 4 Intended status: Informational Ericsson 5 Expires: May 7, 2020 November 04, 2019 7 Discovery Mechanism for QUIC-based, Non-transparent Proxy Services 8 draft-kuehlewind-quic-proxy-discovery-00 10 Abstract 12 Often an intermediate instance (such as a proxy server) is used to 13 connect to a web server or a communicating peer if a direct end-to- 14 end IP connectivity is not possible or the proxy can provide a 15 support service like, e.g., address anonymisation. To use a non- 16 transparent proxy a client explicitly connects to it and requests 17 forwarding to the final target server. The client either knows the 18 proxy address as preconfigured in the application or can dynamically 19 learn about available proxy services. This document describes 20 different discovery mechanisms for non-transparent proxies that are 21 either located in the local network, e.g. home or enterprise network, 22 in the access network, or somewhere else on the Internet usually 23 close to the target server or even in the same network as the target 24 server. 26 This document assumes that the non-transparent proxy server is 27 connected via QUIC and discusses potential discovery mechanisms for 28 such a QUIC-based, non-transparent proxy. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at https://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on May 7, 2020. 47 Copyright Notice 49 Copyright (c) 2019 IETF Trust and the persons identified as the 50 document authors. All rights reserved. 52 This document is subject to BCP 78 and the IETF Trust's Legal 53 Provisions Relating to IETF Documents 54 (https://trustee.ietf.org/license-info) in effect on the date of 55 publication of this document. Please review these documents 56 carefully, as they describe your rights and restrictions with respect 57 to this document. Code Components extracted from this document must 58 include Simplified BSD License text as described in Section 4.e of 59 the Trust Legal Provisions and are provided without warranty as 60 described in the Simplified BSD License. 62 Table of Contents 64 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 65 2. Using DHCP for Local Discovery . . . . . . . . . . . . . . . 3 66 3. Using IPv6 Neighbor Discovery for Local Discovery . . . . . . 5 67 3.1. Using PVDs . . . . . . . . . . . . . . . . . . . . . . . 6 68 4. DNS Service Discovery (DNS-SD) . . . . . . . . . . . . . . . 7 69 4.1. Local discovery using mDNS . . . . . . . . . . . . . . . 7 70 4.2. Discovery for Remote Domains . . . . . . . . . . . . . . 8 71 5. Using PCP options . . . . . . . . . . . . . . . . . . . . . . 8 72 6. Using Anycast address . . . . . . . . . . . . . . . . . . . . 9 73 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 74 8. Security Consideration . . . . . . . . . . . . . . . . . . . 10 75 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 10 76 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 77 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 78 11.1. Normative References . . . . . . . . . . . . . . . . . . 10 79 11.2. Informative References . . . . . . . . . . . . . . . . . 11 80 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 82 1. Introduction 84 QUIC is a new transport protocol that was initially developed as a 85 way to optimize HTTP traffic by supporting multiplexing without head- 86 of-line-blocking and integrating security directly into the 87 transport. This tight integration of security allows the transport 88 and security handshakes to be combined into a single round-trip 89 exchange, after which both the transport connection and authenticated 90 encryption keys are ready. 92 Often an intermediate instance (such as a proxy server) is used to 93 connect to a web server or a communicating peer if a direct end-to- 94 end IP connectivity is not possible or the proxy can provide a 95 support service like, e.g., address anonymisation. QUIC's ability to 96 multiplex, encrypt data, and migrate between network paths makes it 97 ideal for solutions that need to tunnel or proxy traffic. 99 Existing proxies that are based on TCP and HTTP are often 100 transparent. That is, they do not require the cooperation of the 101 ultimate connection endpoints, and are often not visible to one or 102 both of the endpoints. If QUIC provides the basis for future 103 tunneling and proxying solutions, it is expected that this 104 relationship will change. At least one of the endpoints will be 105 aware of the proxy, explicitly connect to it, and coordinate with it. 106 This makes the proxy and tunneling non-transparent to at least most 107 often the client. This allows client hosts to make explicit 108 decisions about the services they request from proxies (for example, 109 simple forwarding or more advance performance-optimizing services), 110 and to do so using a secure communication channel between itself and 111 the proxy. [I-D.kuehlewind-quic-substrate] describes some of the use 112 cases for using QUIC for proxying and tunneling. 114 To use a non-transparent proxy service, a client explicitly connects 115 to it and requests forwarding to the final target server. The client 116 either knows the proxy address as preconfigured in the application or 117 can dynamically learn about available proxy servers. This document 118 describes different discovery mechanisms for proxies that are either 119 located in the local network, e.g. home or enterprise network, in the 120 access network, or somewhere else on the Internet usually close to 121 the traget server or even in the same network as the target server. 122 For the rest of the document the work "proxy" referes to a non- 123 transparent proxy. 125 The discovery mechanisms proposed in this document cover a range of 126 approaches based on IETF protocols and commonly used mechanims, 127 however, other mechanims in more specialized networks are possible as 128 well. For 5G networks, the 3GPP specifies an extended exposure 129 framework that potentially can also be used for proxy discovery and 130 routing support. 132 2. Using DHCP for Local Discovery 134 DHCP [RFC2131] can be used to announce the IP address of local proxy 135 server in IPv4 networks, as well DHCPv6 [RFC8415] in IPv6 networks. 136 New options for both protocols are specified below. The option can 137 contain one or more IP addresses of QUIC-based proxy servers. All of 138 the addresses share the same Lifetime value. If it is desirable to 139 have different Lifetime values, multiple options can be used. 141 0 1 142 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 143 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 144 | Code | Len | 145 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 146 | Reserved |Q | 147 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 148 | Lifetime | 149 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 150 | | 151 : IPv4 Addresses of QUIC-based Proxy Servers : 152 | | 153 +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ 155 Figure 1: IPv4 Proxy Discovery DHCP option format 157 Code: Proxy Discovery option code (TDB) (8 bit) 159 Len: length of the option (without the Code and Len fields) in units 160 of octets. The minimum value is 6 if one IPv4 address is 161 contained in the option. Every additional IPv4 address increases 162 the length by 4. (8-bit unsigned integer) 164 Q: is set to one if proxy supports QUIC on port 443 (1 bit) 166 Lifetime: maximum time in seconds (relative to the time the packet 167 is received) over which these IP4 addresses can be used for proxy 168 discovery. A value of all one bits (0xffff) represents infinity. 169 A value of zero means that the proxy addresses SHOULD no longer be 170 used. (16-bit unsigned integer) 172 IPv4 Addresses of QUIC-based Proxy Servers: one or more 64-bit IPv4 173 addresses of QUIC-based proxy servers. The number of addresses is 174 determined by the Length field. That is, the number of addresses 175 is equal to (Length - 2) / 4. 177 0 1 2 3 178 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 179 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 180 | option-code | option-len | 181 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 182 | Reserved |Q| Lifetime | 183 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 184 | | 185 : IPv6 Addresses of QUIC-based Proxy Servers : 186 | | 187 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 189 Figure 2: IPv4 Proxy Discovery DHCP option format 191 option-code: Proxy Discovery option code (TDB) (16 bit) 193 option-len: length of the option (without the Type and Length 194 fields) in units of 8 octets. The minimum value is 20 if one IPv6 195 address is contained in the option. Every additional IPv6 address 196 increases the length by 16. (8-bit unsigned integer) 198 Q: is set to one if proxy supports QUIC on port 443 (1 bit) 200 Lifetime: maximum time in seconds (relative to the time the packet 201 is received) over which these IPv6 addresses can be used for proxy 202 discovery. A value of all one bits (0xffffffff) represents 203 infinity. A value of zero means that the proxy addresses SHOULD 204 no longer be used. (16-bit unsigned integer) 206 IPv6 Addresses of QUIC-based Proxy Servers: one or more 128-bit IPv6 207 addresses of QUIC-based proxy servers. The number of addresses is 208 determined by the Length field. That is, the number of addresses 209 is equal to (Length - 1) / 2. 211 3. Using IPv6 Neighbor Discovery for Local Discovery 213 If a proxy is located in the local network, information to discover a 214 proxy service can be provided in a new Router Advertisement (RA) 215 Option [RFC4861], the Proxy Discovery option. 217 0 1 2 3 218 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 219 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 220 | Type | Length | Reserved |Q| 221 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 222 | Lifetime | 223 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 | | 225 : IPv6 Addresses of QUIC-based Proxy Servers : 226 | | 227 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 229 Figure 3: Proxy Discovery RA option format 231 Type: Proxy Discovery option type (TDB) (8 bit) 233 Length: length of the option (including the Type and Length fields) 234 in units of 8 octets. The minimum value is 3 if one IPv6 address 235 is contained in the option. Every additional IPv6 address 236 increases the length by 2. (8-bit unsigned integer) 238 Q: is set to one if proxy supports QUIC on port 443 (1 bit) 240 Lifetime: maximum time in seconds (relative to the time the packet 241 is received) over which these IPv6 addresses can be used for proxy 242 discovery. A value of all one bits (0xffffffff) represents 243 infinity. A value of zero means that the proxy addresses SHOULD 244 no longer be used. (32-bit unsigned integer) 246 IPv6 Addresses of QUIC-based Proxy Servers: one or more 128-bit IPv6 247 addresses of QUIC-based proxy servers. The number of addresses is 248 determined by the Length field. That is, the number of addresses 249 is equal to (Length - 1) / 2. 251 3.1. Using PVDs 253 If the local network provides configuration with an Explicit 254 Provisioning Domain (PvD) [I-D.ietf-intarea-provisioning-domains], 255 the RA defined above can be used with the PvD Option or alternatively 256 proxy information can be retrieved in the additional information JSON 257 files associated with the PvD ID. The endhost resolves the URL 258 provided in the PvD ID into an IP address using the local DNS server 259 that is associated with the corresponding PvD (see also section 260 3.4.4. [I-D.ietf-intarea-provisioning-domains]). If a QUIC-based 261 proxy services is provided the additional information JSON file 262 contains the key "QuicProxyIP". It can then optionally also contain 263 more information about the specific proxy services offered using the 264 "ProxyService" key. Or the client can connect directly to the proxy 265 over QUIC on port 443 and request information about the proxy service 266 directly from the proxy server. 268 For remote network a Web PvD might be available that contains proxy 269 information. If provided, the PvD JSON configuration file 270 retrievable at the URI with the format: 272 https:///.well-known/pvd" 274 4. DNS Service Discovery (DNS-SD) 276 [RFC6763] describes the use of SRV records to discover the available 277 instances of a type of service. To get a list of names of the 278 available instance for a certain service a client requests records of 279 type "PTR" (pointer from one name to another in the DNS namespace 280 [RFC1035] for a name containing the service and domain. 282 As specified in [RFC6763] the client can perform a PTR query for a 283 list of available proxy instance in following way: 285 _quicproxy._udp. 287 here the portion is the domain name where the service is 288 registered. The domain name can be obtained via DHCP options or 289 preconfigured. 291 The result of this PTR lookup is a set of zero or more PTR records 292 giving Service Instance names. Then to contact a particular service, 293 the client can query for the SRV [RFC2782] and TXT records of the 294 selected service instance name. The SRV record contains the IP 295 address of the proxy service instance as well as the port number. 296 The port number of QUIC-based proxy is usually expected to be 443 but 297 may differ. The TXT can contain additional information describing 298 the kind of proxy services that is offered. 300 4.1. Local discovery using mDNS 302 [RFC6762] defines the use of ".local." for performing DNS like 303 operations on the local link. Any DNS query for a name ending 304 "local." will be send to predefined IPv4 or IPv6 link local multicast 305 address. 307 To discovery QUIC-based proxy services locally, the client request 308 the PTR record for the name: 310 _quicproxy._udp.local. 312 The result of this PTR lookup is a set of zero or more PTR records 313 giving Service Instance Names of the form: 315 ._quicproxy._udp.local. 317 Editors' Note: Or _masque._udp ? Or _proxy._quic._udp or 318 _quicproxy._http._udp ...? However in the later case the proxy 319 should probably also actually offer a webpage... 321 4.2. Discovery for Remote Domains 323 If a client wants to discover a QUIC-based proxy server for a remote 324 domain, this domain has to be known by the client, e.g. being 325 preconfigured in the application. 327 5. Using PCP options 329 Port Control Protocol (PCP), described in [RFC6887], defines 330 mechanism to do packet forwarding for different types of IPv4/Ipv6 331 Network Address Translators (NAT) or firewall. The usual deployment 332 on PCP include Carrier-Grade NAT (CGN), Customer Permisis Equipment 333 (CPE) and as well as residential NATs. Hence, the discovery of QUIC- 334 based proxy can also be realized via PCP implementations. 336 PCP allows options to be included in the PCP request and response 337 header. The QUIC-based proxy information can be included in the 338 response header as options. As [RFC6887] describes, the client will 339 ignore any options that it does not understand. 341 A PCP option with QUIC-based proxy information is speficied below. 343 0 1 2 3 344 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 346 |