Re: [Doh] HTTP/2 and constrained environmentsRe: [Doh] HTTP/2 and constrained environments
Martin Thomson
2018-05-23
doh
/arch/msg/doh/orneZVqi9hTIoY1M6rodw3HacTE/
2586383
1786221
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Patrick McManus
2018-05-23
doh
/arch/msg/doh/uy02Xm6rgezxlXkEzDi3aEi-_i4/
2586371
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Tom Pusateri
2018-05-23
doh
/arch/msg/doh/NcRW_CRsiTKmm1lfSWSJBqW06Ws/
2586355
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Patrick McManus
2018-05-23
doh
/arch/msg/doh/QVPnfF13WVO0-wsqJfZxUPgANw4/
2586342
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Patrick McManus
2018-05-23
doh
/arch/msg/doh/vDk0QtZsvB6KIXcvrjWmLSQqN7s/
2586338
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Tom Pusateri
2018-05-23
doh
/arch/msg/doh/7ZYYUpyGdYLpnL9ya4iN8Hki-GQ/
2586337
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Patrick McManus
2018-05-23
doh
/arch/msg/doh/39f6wvSRvjy0Rz60CSNKLdNMFOo/
2586332
1785618
Re: [Doh] HTTP/2 and constrained environmentsRe: [Doh] HTTP/2 and constrained environments
Patrick McManus
2018-05-23
doh
/arch/msg/doh/CtjsdKA1lIsnD-6c2G1PiCkfaFs/
2586312
1786221
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Hewitt, Rory
2018-05-23
doh
/arch/msg/doh/qZgOS6kIutnL858g6DTHVsVmLpw/
2586112
1785618
[Doh] HTTP/2 and constrained environments[Doh] HTTP/2 and constrained environments
Mateusz Jończyk
2018-05-23
doh
/arch/msg/doh/Y5TizWEkwqNImSd7rjVvX8gkkls/
2585948
1786221
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Mateusz Jończyk
2018-05-23
doh
/arch/msg/doh/uJqzYmkY2Bz01zF6Dv7IPghCdJk/
2585911
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Mateusz Jończyk
2018-05-22
doh
/arch/msg/doh/eT3R4qtROJVKQzd8U_HZHbsaqlc/
2585575
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Sara Dickinson
2018-05-22
doh
/arch/msg/doh/E174hErNLYngEeBobm7Y_Tc5zLU/
2585532
1785618
[Doh] "Selection of DNS API Server": make it a copy of "Security Considerations"[Doh] "Selection of DNS API Server": make it a copy of "Security Considerations"
Mateusz Jończyk
2018-05-22
doh
/arch/msg/doh/smfjNuX1p8o7Y369-DcUf7Am_OQ/
2585394
1785618
Re: [Doh] WGLC #2Re: [Doh] WGLC #2
Hewitt, Rory
2018-05-21
doh
/arch/msg/doh/5R8q61gL_F67s-kvn_58EDiibEA/
2585180
1785618
[Doh] WGLC #2[Doh] WGLC #2
Ben Schwartz
2018-05-19
doh
/arch/msg/doh/TxuF1112nuORRGBP4V2xXS05zv4/
2584683
1785618
[Doh] I-D Action: draft-ietf-doh-dns-over-https-08.txt[Doh] I-D Action: draft-ietf-doh-dns-over-https-08.txt
internet-drafts
2018-05-16
doh
/arch/msg/doh/pm5Hqzcuj_ARgjc6LTlZWl0LjR0/
2583712
1785223
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Tony Finch
2018-05-14
doh
/arch/msg/doh/GAIRgW47vJD45Ljj9qwD7ZQmRRc/
2582585
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Paul Hoffman
2018-05-14
doh
/arch/msg/doh/XYFaRq7z2EsBvIWJWH3eYCU9DlE/
2582582
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Tony Finch
2018-05-14
doh
/arch/msg/doh/eHQQWckc-6EcPol1-9ns_ESf17s/
2582546
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Mark Nottingham
2018-05-14
doh
/arch/msg/doh/3hKsD49wtbLV2PyXSYKGG-6HNRI/
2582453
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Paul Hoffman
2018-05-12
doh
/arch/msg/doh/Q1BGZDCXk-3hy5GzG_UMsGS55gQ/
2582320
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Paul Hoffman
2018-05-12
doh
/arch/msg/doh/OImf5DIXxnaZ20tGqNeuRYSChIo/
2582319
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Paul Hoffman
2018-05-12
doh
/arch/msg/doh/Ua00xa_cQIGO04bcpMnbTJs836c/
2582318
1783139
Re: [Doh] Subsection Server Push: unclear wordingRe: [Doh] Subsection Server Push: unclear wording
Patrick McManus
2018-05-11
doh
/arch/msg/doh/iSgPjvRqd-_X6EkBAeY-6ZauMuk/
2582015
1784560
Re: [Doh] DNS API server trustRe: [Doh] DNS API server trust
Hewitt, Rory
2018-05-11
doh
/arch/msg/doh/2g6KJFtSRyBNU_fvLJTw9d2PtxY/
2582010
1784550
Re: [Doh] Subsection Server Push: unclear wordingRe: [Doh] Subsection Server Push: unclear wording
Ben Schwartz
2018-05-11
doh
/arch/msg/doh/HpFjouxMNaeYqpE29iYSsnIIuAQ/
2581961
1784560
[Doh] Subsection Server Push: unclear wording[Doh] Subsection Server Push: unclear wording
Mateusz Jończyk
2018-05-11
doh
/arch/msg/doh/VBuRxhaM46YLFs5o498-p3or7WI/
2581917
1784560
[Doh] DNS API server trust[Doh] DNS API server trust
Mateusz Jończyk
2018-05-11
doh
/arch/msg/doh/7oA6xrVVYIdtSp6DF6OAJzdwAqw/
2581885
1784550
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Martin Thomson
2018-05-09
doh
/arch/msg/doh/8dBhJuFQw2jy8RkhkUw4UkJY3ks/
2580612
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Ted Hardie
2018-05-09
doh
/arch/msg/doh/gvN1oEJNtEQEcPCARfBjZvQ2CvE/
2580607
1783139
Re: [Doh] WGLC on draft-ietf-doh-dns-over-httpsRe: [Doh] WGLC on draft-ietf-doh-dns-over-https
Sara Dickinson
2018-05-08
doh
/arch/msg/doh/nEJB_Hm67d8M_t8CcXBtGp-QnHk/
2580410
1781468
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Ben Schwartz
2018-05-08
doh
/arch/msg/doh/tpxngdWcFuai60K9TyTQJ9a6Ltk/
2580393
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Patrick McManus
2018-05-08
doh
/arch/msg/doh/73LXDuDPRUQf5frVNJiceUAdslc/
2580382
1783139
[Doh] DNS Resolver Identification and Use (DRIU) BoF.[Doh] DNS Resolver Identification and Use (DRIU) BoF.
Warren Kumari
2018-05-08
doh
/arch/msg/doh/LbZZeiIwlgVKBvm0r9grc-84Emo/
2580290
1783990
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Mark Nottingham
2018-05-08
doh
/arch/msg/doh/389q5blDGFXEuRAq2BDjYjDQtvo/
2580285
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Patrick McManus
2018-05-08
doh
/arch/msg/doh/ZH-lwwN_6n1IZsebZy7he_vqw3c/
2580277
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Tony Finch
2018-05-08
doh
/arch/msg/doh/tCDnaYbzEiS8w69zSruqzScr9ME/
2580276
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Miek Gieben
2018-05-08
doh
/arch/msg/doh/MfOsOUeyjZ-JEbsxCwaCowax6-c/
2580263
1783139
Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?Re: [Doh] [Ext] Does the HTTP freshness lifetime need to match the TTL?
Mark Nottingham
2018-05-08
doh
/arch/msg/doh/eL977NfBS5K3zIukJ5408-yNS_E/
2580149
1783139
40 Messages