Re: [v6ops] IPv10 Discussion in v6ops

[Nick Hilliard <[e-mail]>]

Khaled Omar wrote on 14/09/2020 17:45:
> I don’t know why people are still lazy and preferring the easy way which 
> is to keep waiting and see maybe something new will happen, IMHP enough 
> time to wait and we should work on something already existing to solve 
> the problem completely.

Khaled,

There have been hundreds of emails over the last couple of years written 
by people who've looked at your proposals and who have unanimously come 
to the same conclusion:

	None of your proposals are going to work.

So when you ask an IETF working group to work on your proposals, you're 
asking people to spend time on something they think is not going to work.

If you want the IETF to take your ideas seriously, then you need to 
prove to people that they're going to work.

A good way to start would be to listen to what people are saying, and 
fix some of the more serious problems that people have patiently taken 
time to comment on.

Here are some ideas:

1. write a working implementation of "ipv10".  Or even a proof of 
concept which allows a single application to make a single connection 
over "ipv10" to another ipv4 or ipv6 host on another network.

2. update the specifications for other protocols to support "ipv10", 
e.g. routing protocols: BGP, mpls, OSPFv2, OSPFv3, ISIS, etc.  There are 
at least 500 RFCs for these protocols alone, so why not take just a 
small selection and update them to support "ipv10".  If you wrote a 
working implementation, then that would be even better.

3. write an API specification for host applications to handle dual 
addressing.

4. write an implementation of your "routing protocol" which allows one 
network to exchange routing information with another network.  Pro tip: 
make sure it works over "ipv10".

It's no use to say that you're not a programmer and that it's someone 
else's job to write the code for your ideas. People have made it clear 
that they think your ideas won't work, so if you want your ideas to be 
taken seriously, then it's your responsibility to prove them wrong.

It's also useless to argue endlessly that people should take your ideas 
seriously.  People won't take them seriously unless you can show that 
they actually work in real life.

When you've written code to show that your ideas work then come back to 
the IETF and maybe at that stage people will take your ideas more seriously.

Nick