Khaled, excuse me if I am too much tutorial-like. It is in my nature, sorry. It does not mean I am right.

I will only post this idea once.

Le 28/09/2017 à 21:19, Khaled Omar a écrit :
We can call the mailing list any name that describes the solution but the contents remains the same.

That is quite a strong requirement. It's hard to assume one brings work at IETF and that initial work stays the same. People would work on it, there would be suggestions, changes.

As for the email list, here is what happens usually: One requests an email list, and provides reasons; then email list is created.

But then a very important step happens: the person who requested the email list waits to see how many people subscribe. It's like when one creates a web site and waits to see how many people look at it. One can not forcefully subscribe people to email lists - it is a practice little appreciated.

If one closes the topic very much (MUST be IPv10), then it is likely that few people will subscribe. If one opens it a lot (MUST be something about migration and compatibility between IP versions), then there may be many people who join.

Given that, how many subscribers would you expect to be on your list? 10? 500?

The industry for sure will understand the new version as it is described in details what is IPv10 and why number 10.

I am not sure. When someone here invokes industry it's because s/he knows something about it, so better listen.

Alex



-------- Original Message --------
Subject: Re: [Int-area] IP-not-v10
From: Ron Bonica
To: [email protected]
CC:


    Maybe the mailing list should be named after the problem that it
    purports to solve, as opposed the solution that Khaled hopes it will
    generate.

    After all, we have no idea whether the mailing list will generate a
    new version of IP at all.

    Furthermore, giving the mailing list a name that suggests that there
    will be yet another version of IP may confuse the industry.

    Ron

    _______________________________________________
    Int-area mailing list
    [email protected]
    https://www.ietf.org/mailman/listinfo/int-area



_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area


_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to