Hi,
On Wed, Sep 26, 2018 at 03:28:24PM +1000, George Michaelson wrote:
> run a race, but bias the race towards the one you like? oky.. But
> once we're beyond a world where the V6 needs the bias, for anyone
> stuck on the vestigial 4-is-better space, this means they incurred
> *additional* con
Hi George,
Actually the idea of NHE is inspired partially by CDN stuff, which involve
lots of measurments
and route users to visit a best path against network dynamics. It proves
to be a good practice
for morden Internet. No doubt. I'm wondering CDN is also breaking DNSSEC to
stub-resolver, right
Davey,
If we’re discussing host based versus network based happy eyeballs, would it be
naive to think that the network based HE would interfere with the client’s HE?
A router knows very little about end to end properties of a connection. It
could of course do those measurements by looking deepl
Having a predictable bias seems better than an unpredictable one.
> On Sep 25, 2018, at 22:28, George Michaelson wrote:
>
> I'm not speaking for Owen. I'm speaking for myself. I asked a
> question. Is this really a long-term defensible thing to do? Do we
> want HE forever?
>
> run a race? thats f
I'm not speaking for Owen. I'm speaking for myself. I asked a
question. Is this really a long-term defensible thing to do? Do we
want HE forever?
run a race? thats fine. But, as the thread here notes, the
second-by-second conditions which leads one TCP to return SYN-ACK
before another can be volat
What better idea did you mean?
Being able to select a protocol based on what works best for the
end-user does not seem like a terrible end-state for the end-user,
short- or long-term.
> On Sep 25, 2018, at 21:25, Owen DeLong wrote:
>
> It was never a good idea. It was a necessary evil (kind of l
It was never a good idea. It was a necessary evil (kind of like NAT in that
regard) to expeditiously deal with a somewhat tenacious (at the time) problem
which has since been given a significantly better solution, but so long as the
workaround appears to be working, people are loathe to put in t
I have said before, but don't know if I still adhere to it, but
anyways, here's a question: How *long* do people think a biassing
mechanism like HE is a good idea?
* is it a good idea *forever*
* or is it a transition path mechanism which has an end-of-life?
* how do we know, when its at end-
>
> But in the general case the network cannot.
> Think host multi-homing.
>
Yes or no.
Generally speaking the races of IPv6 and IPv4 connections on both network
and client are going to be suffered by netowrk dynamics, including
Multi-homing, route flaps, roaming, or other network falilures. Ext
Adam Roach has entered the following ballot position for
draft-ietf-dnsop-isp-ip6rdns-06: No Objection
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please refer to h
> This hints at a general misunderstanding on how "The Internet" works.
>
> Talking to the local ISP on "what would you recommend, IPv4 or IPv6?"
> can give an indication, but if the server you're trying to talk to
> is on the other side of the world, the local ISP's preference for
> IPv4-vs-IPv
>
> This hints at a general misunderstanding on how "The Internet" works.
>
> Talking to the local ISP on "what would you recommend, IPv4 or IPv6?"
> can give an indication, but if the server you're trying to talk to
> is on the other side of the world, the local ISP's preference for
> IPv4-vs-IPv6
To get to know the current status of HE , I did a simple test on my handy
devices visit top 20 website or open existing apps (currently only DNS). I
captured &A DNS query pairs (intervel less than 10s) and count HE query
pairs whoes interval less than 100ms. There is a prelimiary result:
1) My
Hi,
On Tue, Sep 25, 2018 at 10:30:05AM +0800, Davey Song wrote:
> Before I put down this draft, I talked with some CPs (content/app
> providers) and ISPs, they have motivations and requirement on this. One
> example is Tencent, they are planning to deploy a complicated measurement
> network to in
14 matches
Mail list logo