Re: Adding IPv10 I-D to the IETF 119 meeting agenda

Scott Bradner <sob@sobco.com> Sat, 24 February 2024 19:43 UTC

Return-Path: <sob@sobco.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 3EC94C14F691 for <ietf@ietfa.amsl.com>; Sat, 24 Feb 2024 11:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.315
X-Spam-Level:
X-Spam-Status: No, score=-1.315 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sobco.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctFlXEswCFev for <ietf@ietfa.amsl.com>; Sat, 24 Feb 2024 11:43:13 -0800 (PST)
Received: from sobco.sobco.com (unknown [173.166.5.71]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE08C14F5E3 for <IETF@ietf.org>; Sat, 24 Feb 2024 11:43:11 -0800 (PST)
Received: from smtpclient.apple (golem.sobco.com [199.204.155.34]) by sobco.sobco.com (Postfix) with ESMTPSA id B600E287D2C5; Sat, 24 Feb 2024 14:43:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=sobco.com; s=mail; t=1708803790; bh=0of6UF7Q17Kiq8K61jLqtqNiV2Y=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=qk23NHbPIvgHm8fg1woKfuP12QpThdEJKo1HGWsPo6SPVOKVCtMLG20OLAVT81uAt JfqvfpiCQ39DS16Sp39XF2MOGrSVk0FNO2jED6rKPkbjyghUqy6rP5Y0h2DR+s5rgM k1WKQGSWXJg1hdfOR5BjV+Svu9BhDA2zlTx8754UWzxCXQa0Um1Ov8O8GByjxZJ2Zb 0sIHW1GKJA50w88QZAYmJBMVjddib21EqzWrcCwnt3kVq3kWJovU5zGZPbyMWOgNmP psqGlCz8MFQ0KUeundSFne2RNdEnwJ+H9Fv4PCEOh2G1iJsudpi7JxTgLqeDiWt2Ol 7vM/hTt2WMTLQ==
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.400.31\))
Subject: Re: Adding IPv10 I-D to the IETF 119 meeting agenda
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <AS4PR02MB7829EB0492D5655DA780C7FCAE542@AS4PR02MB7829.eurprd02.prod.outlook.com>
Date: Sat, 24 Feb 2024 14:43:00 -0500
Cc: David Lake <d.lake@surrey.ac.uk>, ietf <IETF@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5057BD65-AD63-41E8-BFCE-79EE39FC625D@sobco.com>
References: <AS4PR02MB7829F472585A06B1A14D085CAE552@AS4PR02MB7829.eurprd02.prod.outlook.com> <B4D4A380-EC31-4D80-82BA-4ED1D3B18389@akamai.com> <AS4PR02MB782923A79C689EACC1E8B59FAE542@AS4PR02MB7829.eurprd02.prod.outlook.com> <A5852292-1A6D-44DF-9EE0-B99B60B74F13@sobco.com> <AS4PR02MB7829170BE41F1CB6599FDDB0AE542@AS4PR02MB7829.eurprd02.prod.outlook.com> <2C4910DC-423F-4706-A23D-C1055C76161D@sobco.com> <AS4PR02MB7829BCAE26C9790E09DFDCB3AE542@AS4PR02MB7829.eurprd02.prod.outlook.com> <4DBB7E7B-31E5-4052-854A-2054BD3BD750@sobco.com> <DBAPR06MB6855439CE2345009011D6DEBB5542@DBAPR06MB6855.eurprd06.prod.outlook.com> <AS4PR02MB7829EB0492D5655DA780C7FCAE542@AS4PR02MB7829.eurprd02.prod.outlook.com>
To: Khaled Omar <eng.khaled.omar@outlook.com>
X-Mailer: Apple Mail (2.3774.400.31)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mJPm0FMFoQoslqm4ZCrbLmqwYkM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Sat, 24 Feb 2024 19:43:19 -0000

there are at least 7 billion computers in the world that support IPv6
	1.4B windows PCs
	3.6B android phones 
	1.5B iPhones
	.5B iPads

many, but (as David pointed out not all) big ISPs & carriers support IPv6

none of the computers are blocked from reaching a website or other Internet 
service just because they can support IPv6 or because they are using IPv6

there are political reasons we do not have just one Internet but supporting IPv6
is not 

hard to see that there is a problem that needs solving by introducing a new protocol that would take a long time, if ever, to get to the level of use that IPv6 has now

Scott

> On Feb 24, 2024, at 2:33 PM, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> 
> Let’s do our part and focus and we will see?
> 
> Get Outlook for iOS
> From: David Lake <d.lake@surrey.ac.uk>
> Sent: Saturday, February 24, 2024 9:29:57 PM
> To: Scott Bradner <sob@sobco.com>; Khaled Omar <eng.khaled.omar@outlook.com>
> Cc: ietf <IETF@ietf.org>
> Subject: Re: Adding IPv10 I-D to the IETF 119 meeting agenda   Many mobile networks don’t support IPv6 and I have yet to find a website I can’t get to.   Also most MNOs use CGNAT with private IPs on the PGW/UPF anyway.
> 
> The last thing we need is a migration to another addressing scheme IMvvvHO.  V4 and v6 are more than enough.
> 
> David
> 
> Sent from Outlook for iOS
> From: ietf <ietf-bounces@ietf.org> on behalf of Scott Bradner <sob@sobco.com>
> Sent: Saturday, February 24, 2024 7:24:57 PM
> To: Khaled Omar <eng.khaled.omar@outlook.com>
> Cc: ietf <IETF@ietf.org>
> Subject: Re: Adding IPv10 I-D to the IETF 119 meeting agenda   how many websites can you not get to on your smartphone (assuming you have one)?
> 
> Scott
> 
> > On Feb 24, 2024, at 2:23 PM, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> > 
> > White or black is not the same, IPv10 and IPv6 also not the same, if you think IPv6 is the solution, then we tried it since 1995 and it didn’t fully work, now the internet is broken into two pieces.
> > 
> > Get Outlook for iOS
> > From: Scott Bradner <sob@sobco.com>
> > Sent: Saturday, February 24, 2024 9:20:02 PM
> > To: Khaled Omar <eng.khaled.omar@outlook.com>
> > Cc: Salz, Rich <rsalz@akamai.com>; ietf <IETF@ietf.org>
> > Subject: Re: Adding IPv10 I-D to the IETF 119 meeting agenda   as you have been told many times - IPv6
> > 
> > > On Feb 24, 2024, at 2:10 PM, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> > > 
> > > Excuse me, what is other solution you already deployed?
> > > 
> > > Get Outlook for iOS
> > > From: Scott Bradner <sob@sobco.com>
> > > Sent: Saturday, February 24, 2024 7:42:13 PM
> > > To: Khaled Omar <eng.khaled.omar@outlook.com>
> > > Cc: Salz, Rich <rsalz@akamai.com>; ietf <IETF@ietf.org>
> > > Subject: Re: Adding IPv10 I-D to the IETF 119 meeting agenda   Khaled
> > > 
> > >         the IETF has a deployed solution that, if you have a smartphone on most cellular phone networks in the US, you have been using
> > > 
> > > Scott
> > > 
> > > (I know this is feeding the troll but sometimes it just feels necessary )
> > > 
> > > > On Feb 24, 2024, at 11:55 AM, Khaled Omar <eng.khaled.omar@outlook.com> wrote:
> > > > 
> > > > Rich,
> > > > 
> > > > I’m still waiting for an official announcement regarding whether the IETF had a solution or my solution can be used, it means disrespectful to say what are you doing at DELL, this is a large organization and they are confident about what they are doing, and they support innovation and I’m honored to work for them heer, if you cannot do the same. “ support innovation”, then why are you working there, anyway, let’s find a way to talk in-person and discuss the technical solution together.
> > > > 
> > > > Kind regards,
> > > > Khaled Omar
> > > > Senior Servuce Deliver Engineer
> > > > DELL Technology, Egypt
> > > > 
> > > > Get Outlook for iOS
> > > > From: Salz, Rich <rsalz@akamai.com>
> > > > Sent: Saturday, February 24, 2024 6:16:32 PM
> > > > To: Khaled Omar <eng.khaled.omar@outlook.com>; ietf <IETF@ietf.org>
> > > > Subject: Re: Adding IPv10 I-D to the IETF 119 meeting agenda   <!-- @font-face {font-family:Wingdings} @font-face {font-family:"Cambria Math"} @font-face {font-family:Calibri} @font-face {font-family:Aptos} p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal {margin:0in; font-size:12.0pt; font-family:"Aptos",sans-serif} a:link, span.x_MsoHyperlink {color:blue; text-decoration:underline} p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph {margin-top:0in; margin-right:0in; margin-bottom:0in; margin-left:.5in; font-size:12.0pt; font-family:"Aptos",sans-serif} span.x_EmailStyle18 {font-family:"Aptos",sans-serif; color:windowtext} .x_MsoChpDefault {font-size:10.0pt} @page WordSection1 {margin:1.0in 1.0in 1.0in 1.0in} div.x_WordSection1 {} ol {margin-bottom:0in} ul {margin-bottom:0in} --> We have been down this road with you before. Previous attempts did not end well, with you insisting the document that you submitted and granted rights for be withdrawn, and threatening legal action.
> > > >  
> > > > You think you have a good solution to what you see as a large problem, and you have been unable to convince anyone here.
> > > >  
> > > > Could you please give the green light to the IPv10 I-D to be discussed during the next IETF meeting.
> > > >  
> > > > Unless you find a second person that is willing to work on this, I do not believe the IETF should allocate any time to it. I do not know what you do at DELL, but I assume you have some industry colleagues. Talk to them and see if you can get them to work with you on this. You and I exchanged a few emails privately, and this is what I suggested a month ago.
> > > >  
> > > >     • You can guide me to the correct Work Group, if IntArea still fits, then please confirm.
> > > >  
> > > > Perhaps this is just because you wrote a casual email, but an Area is different from a Work*ing* Group. Look at https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fstandards%2Fprocess%2Fnew-work%2F&data=05%7C02%7Cd.lake%40surrey.ac.uk%7C36e877e84eb9461e43e208dc356e87a1%7C6b902693107440aa9e21d89446a2ebb5%7C0%7C0%7C638443996077669279%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=q0sjncu08AYAw%2BbH72lyWXtvq%2FiwrLiKZB4dx9WicI0%3D&reserved=0 for some information.
> > > >  
> > > 
> > 
>