Re: New Approach For Discussing IPv10.
Tom Beecher <beecher@beecher.cc> Mon, 19 April 2021 13:28 UTC
Return-Path: <beecher@beecher.cc>
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 9A0DC3A3193 for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 06:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.188
X-Spam-Level:
X-Spam-Status: No, score=-0.188 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=beecher.cc
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 UqCMcnLKfq7K for <ietf@ietfa.amsl.com>; Mon, 19 Apr 2021 06:27:59 -0700 (PDT)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (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 DBDB93A318B for <ietf@ietf.org>; Mon, 19 Apr 2021 06:27:58 -0700 (PDT)
Received: by mail-oi1-x232.google.com with SMTP id k18so30475189oik.1 for <ietf@ietf.org>; Mon, 19 Apr 2021 06:27:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beecher.cc; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BBiyBPKqnwzupeCtoIJRSZ56IogZ2MUqV7i9724b8Hw=; b=oI+lzWDGjpY6jZGKbCoLmgRCpyz0uypoVomV7GGbdj4Ksre+tA2evAbRCrCNuPWHCF Mhn9QCjvT/jrUXY9vb222g4E47SSg7JR42e7F8l48HPMz0VB9jeC3f6rqGcpd757mmKH 9zFJbFtpokXu62YP5A9ccczmz6mhV6ywoc6NqzzAuiMtg+Tqu5HB9P+227hj1W97u7dD WWxqRDnhi5KwSColmT7r92T9yh2bgiD/p2asLoUZyVcIt8ZBKAU2sK7hLAFpJynZ4FVs BKwaZk/yy5y17EfU/TQ1r3xkj1/jv9YLW13ttLbiaCevfBL5O/RYKc3Ft9GyzsM3nDAk 882g==
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=BBiyBPKqnwzupeCtoIJRSZ56IogZ2MUqV7i9724b8Hw=; b=g2k2xfx03HXbuyZfZ2y397c6yIRiQ2ImDFPDdAQ/s40dEI2XeZTsGJzAy/kiP17tlG XBOzuQknu0I5f1vT4QjLmBLF8Mm903M6CfSZCRTQd5ZW9rgoQE1veFALbw1uqGUOBcJE sGNklmnqxar2nAwvIHIEq6kPEGG6oH1MikkR57Y7WjnrE3PcWuLvo4cydhMpQ8Kb2dML s6wGe2nxp++guNDKU2R3DI7Yyvq43MbpNNc1b+U4yq6v4BnLMMNEpy4wnI4rrsBdpZGC HMDnllmJaS34YMoXSP+TS+qOOfpsnUHC39ArW/Gebo6wATgQwHxZVlTkm619s73/oO5j YDHw==
X-Gm-Message-State: AOAM530AvSqqOJGa1pXG+uTjMCIunwZV3Nsvmmkbc+FvgdSpLo61OHdv GAekT8HMCCNeOe+RGn4bUpx5MrHQElE2WUyQXhwGng==
X-Google-Smtp-Source: ABdhPJxj28aHFdcgY5haHfLGm1Icxjipj4ZrLx1MDi2hST8m0Fq3Bf591aUY+UsDQzCNhdkItdHpADEDC+xOUlqPk/Y=
X-Received: by 2002:aca:5fc3:: with SMTP id t186mr15160150oib.69.1618838875242; Mon, 19 Apr 2021 06:27:55 -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: Tom Beecher <beecher@beecher.cc>
Date: Mon, 19 Apr 2021 09:27:44 -0400
Message-ID: <CAL9Qcx5LdT6LrkdmC-5Oqx5Ya2cCduM0JQfHdBrhdckk1TO1aw@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="0000000000001b95bf05c0534c13"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y_m9aiMp_RqBJ6YU8EO04XyjACw>
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: Mon, 19 Apr 2021 13:28:04 -0000
I first read the IPv10 draft after the October discussions about it. I would echo what others have said. In its current form I struggle to find any technological benefits in the proposal. It is deficient as a standalone L3 addressing scheme, and really more of another V4/V6 transition mechanism, but one that requires every device on the internet to be updated to support it. 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> > > > > > >
- New Approach For Discussing IPv10. Khaled Omar
- Re: New Approach For Discussing IPv10. Lloyd W
- Re: New Approach For Discussing IPv10. Khaled Omar
- Re: New Approach For Discussing IPv10. Khaled Omar
- Re: New Approach For Discussing IPv10. Ofer Inbar
- RE: New Approach For Discussing IPv10. Khaled Omar
- Re: New Approach For Discussing IPv10. Phillip Hallam-Baker
- Re: New Approach For Discussing IPv10. Joe Touch
- RE: New Approach For Discussing IPv10. Khaled Omar
- Re: New Approach For Discussing IPv10. Phillip Hallam-Baker
- New Approach For Discussing IPng Brian E Carpenter
- RE: New Approach For Discussing IPng Vasilenko Eduard
- Protocol and format (Was: New Approach For Discus… Stephane Bortzmeyer
- Re: New Approach For Discussing IPng Stephane Bortzmeyer
- RE: New Approach For Discussing IPng Khaled Omar
- Re: New Approach For Discussing IPv10. Tom Beecher
- Re: New Approach For Discussing IPng Tom Beecher
- RE: New Approach For Discussing IPng Khaled Omar
- Re: New Approach For Discussing IPng Christopher Morrow
- RE: New Approach For Discussing IPng Khaled Omar
- Re: Protocol and format (Was: New Approach For Di… Joseph Touch
- Re: New Approach For Discussing IPv10. Joseph Touch
- Re: New Approach For Discussing IPng Phillip Hallam-Baker
- Re: Protocol and format (Was: New Approach For Di… Phillip Hallam-Baker
- Re: Protocol and format (Was: New Approach For Di… Behcet Sarikaya
- Re: Protocol and format (Was: New Approach For Di… Nick Hilliard
- Re: Protocol and format (Was: New Approach For Di… John Levine
- Re: Protocol and format (Was: New Approach For Di… Phillip Hallam-Baker