Fw: KHALED Routing Protocol (KRP).

Khaled Omar <eng.khaled.omar@hotmail.com> Fri, 28 April 2017 12:11 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 AE1501205F0 for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 05:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.146
X-Spam-Level:
X-Spam-Status: No, score=-1.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_HOTMAIL_RCVD2=0.874, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no 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 wmRG07pjhSxJ for <ietf@ietfa.amsl.com>; Fri, 28 Apr 2017 05:11:52 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-oln040092066050.outbound.protection.outlook.com [40.92.66.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95CFF127342 for <ietf@ietf.org>; Fri, 28 Apr 2017 05:08:58 -0700 (PDT)
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=gjP106Z9nfeFVaT2aj/IXMj8KKW318Qp/Bh55IyTadE=; b=ebleEc/jPDh3xnm7WUk2QSHnLKn5ye6R6FkUdo98guN7R/q/g7rI/WhvldzoQONHGh/sAgJVjbpQatcA+qWsHDfzv4ONRpW+Ap20TOKPF0Nt9yOtkO4k+Z9TaPjSG/ZGzV9+uitIHYXOQVj5j8Bay8WdDu14mABM6d14MGwY2bqVuIUYyykiSvFBv+LtNvrRnvGEPUO6QaDu74wE9XMLf0CCQCQKP2220inwHpDExSbI31OK39CUBoO5utq9882UCd2yaK4/vmZ1mKcL57qESExTyWs8GlcLdMjwxNL0lFCSCHqc5+XM9EaKqRZxU9ik19ulNdYBFGi2qdA8x1mkCg==
Received: from VE1EUR01FT042.eop-EUR01.prod.protection.outlook.com (10.152.2.56) by VE1EUR01HT033.eop-EUR01.prod.protection.outlook.com (10.152.3.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1047.9; Fri, 28 Apr 2017 12:08:56 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com (10.152.2.58) by VE1EUR01FT042.mail.protection.outlook.com (10.152.3.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1047.9 via Frontend Transport; Fri, 28 Apr 2017 12:08:56 +0000
Received: from AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5]) by AM4PR0401MB2241.eurprd04.prod.outlook.com ([fe80::167:4fb:cc08:25a5%19]) with mapi id 15.01.1047.021; Fri, 28 Apr 2017 12:08:56 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: ietf <ietf@ietf.org>
Subject: Fw: KHALED Routing Protocol (KRP).
Thread-Topic: KHALED Routing Protocol (KRP).
Thread-Index: AdK+G23caKcCxRD+Rv6ktBX4ggsYAQ==
Date: Fri, 28 Apr 2017 12:08:56 +0000
Message-ID: <AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130@AM4PR0401MB2241.eurprd04.prod.outlook.com>
References: <CAKHUCzxK9-McSigoCn-4MvWM-ZPjTzQ+xUj8eB9U1yrA8otGKA@mail.gmail.com> null
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:A819C04D7D511B140811F92DA2978D662A7634AC8678DD5E381B4FFA7CAF3AE1; UpperCasedChecksum:360AFA9D1E18DCF41B5ABA5786BB50FBC885507AADDE3D221EFC04B272696D94; SizeAsReceived:7832; Count:38
x-ms-exchange-messagesentrepresentingtype: 1
x-microsoft-exchange-diagnostics: 1; VE1EUR01HT033; 5:0fOpyHJN6t1gb9gl1CG6UW1qjSPgLx4Owqc1hn425wJ0XU809lyp/pvb4fUj6s1KjTFdOuBNiaHa11qZH5yYj7d2XvdaKx8oJVCkF1RX++WFI8SlG/DBIpZ1nCpD7n1xwUY/FIDZ1Kj95UzD7mRGhw==; 24:BrgVRT6BPiVQZ+5deOeGepeDQqCLPQpHwZLtjYsqDMz9ekPig0QewZgAUFJMtO2WwyvS92bp0Bk6PWOEs64n8dfhcNYP7o0Yeb84nRnM7T0=; 7:dZbdw/5JrXyedFSwoZsn/vgdva6okmVOliqEsNNv5fH+118utVJrQ1pwW7IeUwu5zbU8ItD2Cx6Qdga52hb4L4Ziw7z8xjXpHWhPPX7GCfzvhr1whQJB20XPYJW2K5pVr3iQHT9ZtocIJkKhGC1xjCgSBg+ZbZcWxTbxnd+41jkc72K+be0lzrpOQ5hKiOevO59Gb3fXRqTQqaaVmack4hAvtUkD7mL9oc3emo6ymH4yUtp4SwoJZHTCmzYab/He7QPRS72qRBEW83FIgn4L+4C5cg0U92OAl1xW06X9wRnEKBKi3/scut1ZVVFG29c7
x-incomingheadercount: 38
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:VE1EUR01HT033; H:AM4PR0401MB2241.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en;
x-ms-office365-filtering-correlation-id: dcab916d-7069-4278-6188-08d48e2f57be
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045); SRVR:VE1EUR01HT033;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:VE1EUR01HT033; BCL:0; PCL:0; RULEID:; SRVR:VE1EUR01HT033;
x-forefront-prvs: 029174C036
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM4PR0401MB2241DFDF2E27B9208F37B0D1BD130AM4PR0401MB2241_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Apr 2017 12:08:56.1021 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT033
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O9koaB7gqkIcOQ-th92u4QlGFQ0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 28 Apr 2017 12:11:54 -0000


-------- Original Message --------
Subject: Re: KHALED Routing Protocol (KRP).
From: Khaled Omar
To: Dave Cridland
CC:


Dave,

Regarding the difference between tables, KRP within each region uses a table of only RBRs and RRs, the table is not listing prefixes because KRP uses the information stored on every single IP address and the IGP routing table, also, the Forwarding table details of one region is not advertised to other regions because they don't need to know it, enough to know how to reach the RBR and then it can deliver the packet faster and correctly.

KRP will not require renumbering (reallocation) of IP addresses after the modification made to the 1st version of the draft that used the 1st two groups of IPv6 addresses as the KRP ASN, but the 2nd version used the middle two groups, and that will make the usage of KRP easier.

Finally, don't stop on what you think is not applicable, share your thoughts to add a solution to make things applicable thats the aim of the discussion, because KRP can route packets successfully from the source to the destination using the Best best route and with the lowest table entries for faster routing decisions.


-------- Original Message --------
Subject: Re: KHALED Routing Protocol (KRP).
From: Dave Cridland
To: Khaled Omar
CC: ietf@ietf.org


On 26 April 2017 at 00:27, Khaled Omar wrote:
> https://datatracker.ietf.org/doc/draft-omar-krp/

I like this idea, but I think it's sufficiently similar to the
original aim of EGP/BGP that it's already been proven impractical, and
moving to it would also be impractical. I am not a routing expert, so
I'll cheerfully wait being shot down by others, but this is my
rationale:

The reason why we have large routing tables within BGP routers is
mostly that ASNs now consist of many more prefixes than were
originally expected, and so the prefixes do not aggregate well enough.

This proposal involves, essentially, renumbering the entire internet
(which is very difficult in practical terms), such that aggregation
then works more efficiently. However, history has shown that while
this would work for the short term, it would require continuous
renumbering in response to many factors (new addresses, corporate
mergers, etc) in order to maintain its efficiency.

Since we have not solved renumbering very effectively in the first
place, I feel that this is not worth working on.

I would, however, suggest that addressing renumbering would be an
excellent use of your time. A viable solution to renumbering large
public networks would mean that the BGP table would shrink, by the
same logic as above.

That is, if we had a method for renumbering continuously, then it
would improve the efficiency of BGP as well, to almost the same
extent, without incurring the initial internet-wide renumbering
effort.

Finally, I would note that while routing tables are large, the
internet still functions - this may not be the best use of your time
therefore.

Dave.