IPv4 Outage at Next IETF in Chicago.

Khaled Omar <eng.khaled.omar@hotmail.com> Wed, 25 January 2017 07:28 UTC

Return-Path: <eng.khaled.omar@hotmail.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 C5CF912985C for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 23:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.055
X-Spam-Level:
X-Spam-Status: No, score=-7.055 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
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 KIipUiQrZkZQ for <ietf@ietfa.amsl.com>; Tue, 24 Jan 2017 23:28:06 -0800 (PST)
Received: from BLU004-OMC2S1.hotmail.com (blu004-omc2s1.hotmail.com [65.55.111.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EA51129842 for <ietf@ietf.org>; Tue, 24 Jan 2017 23:28:06 -0800 (PST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com ([65.55.111.73]) by BLU004-OMC2S1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 24 Jan 2017 23:28:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=noS0yEDZ1/y12JdI3ENV2fzOhUZWKThCTGHy5ajkQBw=; b=kmX5VgLa/i379v3Er7w+vBeMd6areUXW6EyR2ZtutI8/S9FnBnHMdeK7d0pIlhhxS9cC1t6c2exRxHSSYetp7Np5AbcS30YfUfY9VPmnfG+J7wz4bisHtPdJQHnXaOY/bzGyocLENlqloIXuQ2JAPmIQt/Wogc+Ic2eQA1NFAQ9gItLIU+fwQUIGYa5bcJdRJPvLgcHU0gaQWTHvPF6ugqE0Z1a/Fv9z3s/NQR0almmeHjNFW7rhpTxC0Ns+A3Iqr8mHUHxOiAZ1WDTFrdz9ST4EmICV/XDAMBy02U4gZZaI1Ie/AynwmNFSKjx8IiT6PhKzeuvX/5h/A0VoTY62pQ==
Received: from VE1EUR02FT003.eop-EUR02.prod.protection.outlook.com (10.152.12.53) by VE1EUR02HT066.eop-EUR02.prod.protection.outlook.com (10.152.13.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.803.8; Wed, 25 Jan 2017 07:28:03 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com (10.152.12.51) by VE1EUR02FT003.mail.protection.outlook.com (10.152.12.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.803.8 via Frontend Transport; Wed, 25 Jan 2017 07:28:03 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) by HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) with mapi id 15.01.0860.021; Wed, 25 Jan 2017 07:28:03 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: IPv4 Outage at Next IETF in Chicago.
Thread-Topic: IPv4 Outage at Next IETF in Chicago.
Thread-Index: AQHSdtyQV8jxFR94fEuFDIkB+r093Q==
Date: Wed, 25 Jan 2017 07:28:03 +0000
Message-ID: <HE1PR04MB144997FEA541BF6BC570A85ABD740@HE1PR04MB1449.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:2A009D4EF6652FF532EBE204CD376151F72260DEABF4D9699326FB63ACC665FB; UpperCasedChecksum:5830843BB3B7DE988BCA13EE9A1548BD0CFDF698FE201D4CE3E50EC2C02B95AA; SizeAsReceived:7286; Count:34
x-ms-exchange-messagesentrepresentingtype: 1
x-incomingheadercount: 34
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; VE1EUR02HT066; 7:Geju9YXN+ZRPh/J3+klqK2ng5/bF35jd8+Ws/5wLBMBg8q4crPC6LqXFMEH/RrPqTOBG9X1k4W5JxFmqqkpEk+zs9DfzlgGvG1Id/y5mdp4Dht8+HazCb6qP1gD0BueFuZcJP8tDK1YzjIR1nofWTqtyWdwvb+ZAZyf6IULHR240EiDSioo8UTKF+ztJDVY1kX1azxWehn3F5w6IzwnEotw4BvmUUZVfeKaQfLQq920XMZDBzRBHHXm28+LQzgJ0GjPqEu3dtESPpDZlMayEJTK6MhC70Q7mhQ+k7ZxlI8to/UMlnJ/NwXaMI5Zl6Sec1jkL8fWXSjevHrF+YEK3Za9iSXDkAyuqPATyCWTzEIv5IBxEVzl1KRxN+Z3x4ZJm3rZsnT1GrjG2zFV2o2rqkQU0+P0XvTQvtowZpoB7WstukjAE6IVUALLFWkXVtc0zdNgGFAEUDmrQ3jPg20gV3A==
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900005); DIR:OUT; SFP:1102; SCL:1; SRVR:VE1EUR02HT066; H:HE1PR04MB1449.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: e65bd6d7-f62a-46c8-f5de-08d444f3b222
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(1601124038)(5061506365)(5061507293)(1603103113)(1601125060)(1701031023); SRVR:VE1EUR02HT066;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444111334)(444112120)(432015012)(82015046); SRVR:VE1EUR02HT066; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR02HT066;
x-forefront-prvs: 01986AE76B
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <81C0982569EE22488ED2F39BF4E9D7EB@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jan 2017 07:28:03.2908 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR02HT066
X-OriginalArrivalTime: 25 Jan 2017 07:28:05.0609 (UTC) FILETIME=[91AD1D90:01D276DC]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7S_cgIWD1-2FOVSXwcdNT6M1NmM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 25 Jan 2017 07:28:08 -0000

Hi all,

It is good that the IETF is discussing and will discuss this topic in the next meeting, hoping to see more realistic solutions that can be applied.

On the other hand, as I can see, IPv10 is not in the IETF plan of discussion, so will be great if more applicable solutions will be introduced that can solve the IPv4 outage problem and help the new IPv6 only networks globally.

Best Regards,

Khaled Omar