h3-29, h3-34" to indicate possible
support of versions 27, 29 and 34 of the draft. They would also often
propose the choice between the binary format HTTP3 and the text based
test format HTTP 09 to let servers negotiate which one was appropriate.
-- Christian Huitema
-- Christian Huitema
;default TLS" posture. RFC 6335 explains why IANA should preserve the
port-numbers resource, and we could do that by phasing out usage of the
clear-text only port, and then removing its registration.
-- Christian Huitema
___
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta
nd IMAP come to mind. Maybe XMPP as well.
-- Christian Huitema
___
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta
iplexed
server" scenario. In fact, that's a pretty natural use of MX records.
The MX record for "some-personal-server.com" would point to
"mta.example.net", the SNI would be "mta.example.net", and the IP
address in the IP header w
On 10/23/2017 10:21 AM, Viktor Dukhovni wrote:
>> On Oct 23, 2017, at 1:00 PM, Christian Huitema wrote:
>>
>> As Viktor says, the easy way for STS is to avoid the "multiplexed
>> server" scenario. In fact, that's a pretty natural use of MX records.
>>
e.
That's a lot of information. How do we balance the privacy effect of
volunteering that information versus the management benefits?
-- Christian Huitema
___
Uta mailing list
Uta@ietf.org
https://www.ietf.org/mailman/listinfo/uta
