IETF Logo Mail Archive

Re: New Approach For Discussing IPv10.

Phillip Hallam-Baker <phill@hallambaker.com> Sun, 18 April 2021 04:49 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1E363A104E for <ietf@ietfa.amsl.com>; Sat, 17 Apr 2021 21:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level:
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Mi0ol8FkHdR for <ietf@ietfa.amsl.com>; Sat, 17 Apr 2021 21:49:01 -0700 (PDT)
Received: from mail-yb1-f179.google.com (mail-yb1-f179.google.com [209.85.219.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B4DC3A104B for <ietf@ietf.org>; Sat, 17 Apr 2021 21:49:00 -0700 (PDT)
Received: by mail-yb1-f179.google.com with SMTP id g38so34808224ybi.12 for <ietf@ietf.org>; Sat, 17 Apr 2021 21:49:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=78C7wU76UjaeUp2PYh9r2PZVnWGvA5890QP8c9LfrQ8=; b=ts2SbdAEPMbpvlXvv0whZwTDy7H4hSBRsMJsBvZxavLpn567gttgvwCBMxqESeDjB8 afy5ktxB7bKLKL1gejj+ptej7ySft7CupMJ2Yf40st3L20vJWUQ1d46z/chW+kGkaa+K FMxcfmqjE0J7pE5cXIf7kYrF7ir/VAH9OkW4sMXsx4Fq19XNV2H+jAyJnfS0jWHtDGsg JF1xOjDgBXLTI2Dxz9eTGcOx8LNHP2S2uaW5fMjv4+ifp80T2CyTKuGAlM7bFQ9lyldT r1eXfcKhwkL4msxVxJzz2s/1dc+SmiinHKQu28nwdA0xZ1b17qzxk8roQdV0YmVj/vQ4 l8UQ==
X-Gm-Message-State: AOAM532hWkVr1UrO4xXBw+OjTI0QNfoZzYJ48gRsvJ38N0CyKRv4K0BM wvPQUnV7z+OaZaRSgZTQDUwoG90uJg1M01FzlKk=
X-Google-Smtp-Source: ABdhPJx2gntOrrw5cn3MwRYzkVmU9JvTlqjhHs29AFoX3Zq2tvYj9iDmkRWEy4oA1fLn4TQR3bynXuH+ZNLsuW2cAcI=
X-Received: by 2002:a25:aa90:: with SMTP id t16mr8523808ybi.56.1618721339869; Sat, 17 Apr 2021 21:48:59 -0700 (PDT)
MIME-Version: 1.0
References: <AM7PR03MB6594910D55F5C0BCC42089C4AE4C9@AM7PR03MB6594.eurprd03.prod.outlook.com> <97267D70-5472-430E-8A97-B20316D96216@yahoo.co.uk> <AM7PR03MB65946BF8C6906E0F2D5FC537AE4B9@AM7PR03MB6594.eurprd03.prod.outlook.com>
In-Reply-To: <AM7PR03MB65946BF8C6906E0F2D5FC537AE4B9@AM7PR03MB6594.eurprd03.prod.outlook.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Sun, 18 Apr 2021 00:48:46 -0400
Message-ID: <CAMm+LwhV01N_uuFV8TfiyegpqDLmUYwxBcmkUAGG-HfJ7vSB+Q@mail.gmail.com>
Subject: Re: New Approach For Discussing IPv10.
To: Khaled Omar <eng.khaled.omar@outlook.com>
Cc: Lloyd W <lloyd.wood@yahoo.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000074136f05c037eefc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BxJpCdqVcIYXUcfxUTe3BvZEN7E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Apr 2021 04:49:06 -0000

IPv6 isn't actually a 'protocol' as such. It is merely a data structure. It
has a source address in a 128 bit domain and a destination address and a
few flags and counters to stop loops, etc. and an extension mechanism
allowing folk to throw pretty much anything else in.

Are you absolutely sure you can't achieve what you want inside the IPv6
regime? Because it is a ten year multi-billion dollar expense to change
stuff at that level. You have an addressing scheme that can get you to give
a unique address to every grain of sand. You have an extension scheme.

The interesting thing, the part that animates IPv6 is actually the routing
tables and the technologies that maintain those are separate. You can tweak
those without moving from IPv6.


On Sat, Apr 17, 2021 at 10:40 AM Khaled Omar <eng.khaled.omar@outlook.com>
wrote:

> >> The same IPv10 whose drafts you previously wanted removing from the
> drafts repository?
>
>
>
> And regarding this question, yes, same draft.
>
>
>
> *From:* Lloyd W [mailto:lloyd.wood@yahoo.co.uk]
> *Sent:* Saturday, April 17, 2021 12:44 AM
> *To:* Khaled Omar <eng.khaled.omar@outlook.com>
> *Cc:* ietf@ietf.org
> *Subject:* Re: New Approach For Discussing IPv10.
>
>
>
> Khaled
>
>
>
> The same IPv10 whose drafts you previously wanted removing from the drafts
> repository?
>
>
>
> https://mailarchive.ietf.org/arch/msg/ietf/7pc66r2Kf83BfaHW4ZWIK9GfcBk/
>
> that does not encourage others to look at your drafts.
>
>
>
> Lloyd Wood
>
> lloyd.wood@yahoo.co.uk
>
>
>
> On 17 Apr 2021, at 03:29, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
>
> 
>
> Dear IETFers,
>
>
>
> I hope you are all fine,
>
>
>
> I still see through my online research that the world still working on
> IPv4 and the migration to IPv6 will take longer than expected due to the
> slow movement towards IPv6.
>
>
>
> We still have the opportunity here to discuss more transitioning solutions
> and I think I suggested one (IPv10 or IPmix) to help in solving this
> migration issue under the new administration of the IETF.
>
>
>
> *Best Regards,*
>
>
>
> *Khaled Omar*
>
> Senior Network and Security Engineer
>
> Mobile ): (EGY) (+2)-01003620284
>
> E-mail *:    eng.khaled.omar@hotmail.com
>
> Connect with me:
>
> [image: Twitter] <http://www.twitter.com/eng_khaled_omar>[image:
> http://campaign.vmware.com/imgs/spacer.gif]
>
> Twitter <http://www.twitter.com/eng_khaled_omar>
>
> [image: LinkedIn] <http://www.linkedin.com/in/engkhaledomar>[image:
> http://campaign.vmware.com/imgs/spacer.gif]
>
> LinkedIn <http://www.linkedin.com/in/engkhaledomar>
>
>
>
>
>
>

v2.23.0 | Report a Bug | By Email