Re: [v6ops] draft-xie-v6ops-network-happyeyeballs

Yes, the running code and data-based analysis is important. As we met in
IETF103, the authors plan to setup a open source repo in Github doing the
following steps :

#1 To develop a methord (packets capturing and analysis) to measure and
collect the data on the delay of IPv4-fallback issue in dualstack network.
We would like to invite network operators to test in their network. This
step is helpful for us to understand how severe the problem is. It may vary
for different ISPs.

#2 if #1 proves it a valid problem to solve, then we are going to develop a
active monitoring tool based on NHE draft. We would like to ask volunteers
to try and implement in some ISPs network to study the impact and gains.

#3 We will see later the result of #1 and #2, and decide how to proceed any
document in IETF.

For each step, peer review and comments from IETF are helpful.

Best regards,
Davey

On Sat, 1 Dec 2018 at 00:55, Lencse Gábor <lencse@hit.bme.hu> wrote:

>
>
> 11/29/2018 11:53 PM keltezéssel, Tommy Pauly írta:
> >
> >> On Nov 27, 2018, at 7:52 AM, JORDI PALET MARTINEZ <jordi.palet=
> 40consulintel.es@dmarc.ietf.org> wrote:
> >>
> >> In the previous related work, I was told otherwise: let's the ISPs do
> it, not the O/S vendors ...
> > I think the point being made here is that open source software can be
> created and distributed to ISPs to run in their networks; it doesn't
> necessarily require any standard or draft to do it.
>
> I think you are completely right that the software can be written
> without an I-D, however, I think that its specification would benefit
> from a matured draft.
>
> Gábor
>
> > Thanks,
> > Tommy
> >> Regards,
> >> Jordi
> >>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>