Re: Numbering Exchange Protocol (NEP) ID.

"Acee Lindem (acee)" <acee@cisco.com> Thu, 14 December 2017 15:27 UTC

Return-Path: <acee@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D719127868 for <rtgwg@ietfa.amsl.com>; Thu, 14 Dec 2017 07:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qzBuPnYs_xln for <rtgwg@ietfa.amsl.com>; Thu, 14 Dec 2017 07:27:41 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BFDB126DED for <rtgwg@ietf.org>; Thu, 14 Dec 2017 07:27:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=35571; q=dns/txt; s=iport; t=1513265260; x=1514474860; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=H4qzv7XQOeYwhVQ46nLFkI2bI1V0pcFYEwkYrzUsij8=; b=dJ3sK7qjgtjr6WHMasdm5CaXY4C3Zge+wyysS4+uofiiXAFRDxjh0zxu smWb+Gr+fbL1/WRq/gFFFaER7TV15Rbq4zU2cAb3uwp1Ccwdkc1OC9ZGw VTSOULdpc22ZtdDWnPiD7ZpaF5GjyagYgZCz+KbzSHktT0qCX5XRPdNay I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DcAACnlzJa/4cNJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYJKRS9mdCcHg3uKIY8GgX1+gWWGGY4aFIF+AwoYAQqFGAIahF0/GAEBAQEBAQEBAWsohSMBAQEBAwEiCkELDAQCAQgOAwMBAQEhAQYDAgICHwcKFAkIAQEEDgWJRkwDFRCoa4InhzYNgxsBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYNggg6DPoJ2NoJqRAEBgTJbBhCCX4JjBaJoPQKHe4cbgRQBhH2CFoYShBCHNI0VPohtAhEZAYE6AR85gU5vFTqCKYRWeAGJNYEVAQEB
X-IronPort-AV: E=Sophos;i="5.45,400,1508803200"; d="scan'208,217";a="321975654"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Dec 2017 15:27:39 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vBEFRdbO001907 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Dec 2017 15:27:39 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 14 Dec 2017 10:27:38 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1320.000; Thu, 14 Dec 2017 10:27:38 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Khaled Omar <eng.khaled.omar@hotmail.com>
CC: "rtgwg@ietf.org" <rtgwg@ietf.org>
Subject: Re: Numbering Exchange Protocol (NEP) ID.
Thread-Topic: Numbering Exchange Protocol (NEP) ID.
Thread-Index: AdNwPTnVfbkDNjHfSz2d3iUoZdzQRgBBpRcAAOq+SZAAAFFfAA==
Date: Thu, 14 Dec 2017 15:27:38 +0000
Message-ID: <D658018E.E17C9%acee@cisco.com>
References: <D651D080.E0BD9%acee@cisco.com> <AM4PR0401MB22416985A093D9B863B8A58CBD310@AM4PR0401MB2241.eurprd04.prod.outlook.com> <D651D8D2.E0BE5%acee@cisco.com> <AM4PR0401MB22412996258EBAB683979CAABD0A0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
In-Reply-To: <AM4PR0401MB22412996258EBAB683979CAABD0A0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.198]
Content-Type: multipart/alternative; boundary="_000_D658018EE17C9aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/Egt6rsiS2Uy7WDJhTVqWa4ut3ik>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 15:27:44 -0000


From: Khaled Omar <eng.khaled.omar@hotmail.com<mailto:eng.khaled.omar@hotmail.com>>
Date: Thursday, December 14, 2017 at 10:22 AM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>
Cc: Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: RE: Numbering Exchange Protocol (NEP) ID.

Acee,

Every working IGP has its own way of metric calculations, they cannot be variables based on the network,

Please read https://www.ietf.org/id/draft-hegdeppsenak-isis-sr-flex-algo-01.txt. There will be similar extensions to OSPF.

the most important is that how many factors can affect choosing the best route simultaneously.

If you read the above draft, you will see that these are covered.

Thanks,
Acee

I encourage more participation to work on NEP as there is more to add.

Best Regards,

K. O.


From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Sunday, December 10, 2017 1:17 AM
To: Khaled Omar; Christopher Morrow
Cc: rtgwg
Subject: Re: Numbering Exchange Protocol (NEP) ID.

From: Khaled Omar <eng.khaled.omar@hotmail.com<mailto:eng.khaled.omar@hotmail.com>>
Date: Saturday, December 9, 2017 at 6:03 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Christopher Morrow <morrowc.lists@gmail.com<mailto:morrowc.lists@gmail.com>>
Cc: Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: Numbering Exchange Protocol (NEP) ID.

Hi Acee,

The NEP metric is unique, there is no other protocol uses this composite metric, the link in your e-mail has no metric as I read, also it is newer than NEP as I wrote the ID before this suggested protocol, hope the copyright is protected.

Any composite metric can be used – it doesn’t even need to be standardized.

Thanks,
Acee


-------- Original Message --------
Subject: Re: Numbering Exchange Protocol (NEP) ID.
From: "Acee Lindem (acee)"
To: Khaled Omar ,Christopher Morrow
CC: rtgwg


Khaled,

The existing IGPs will allow for alternate metrics, we don’t need a new protocol. In fact, it will be supported at the per-prefix granularity.

https://datatracker.ietf.org/doc/draft-hegdeppsenak-isis-sr-flex-algo/

No time in my agenda for NEP…

Thanks,
Acee

From: rtgwg <rtgwg-bounces@ietf.org<mailto:rtgwg-bounces@ietf.org>> on behalf of Khaled Omar <eng.khaled.omar@hotmail.com<mailto:eng.khaled.omar@hotmail.com>>
Date: Saturday, December 9, 2017 at 3:40 PM
To: Christopher Morrow <morrowc.lists@gmail.com<mailto:morrowc.lists@gmail.com>>
Cc: Routing WG <rtgwg@ietf.org<mailto:rtgwg@ietf.org>>
Subject: Re: Numbering Exchange Protocol (NEP) ID.

Hi Christopher,

The problem is how to choose the best route based on the metric.

RIP uses only the number of hops.
OSPF uses only the cost (bandwidth).
EIGRP uses the least bandwidth and total delay.
IS-IS uses a default metric of 10 for all links.
NEP uses the total bandwidth, total delay, and the number of hops.

So, the challenge is to find the best metric that will chose the best route.

The ID lists the equation of how to calculate the metric.






-------- Original Message --------
Subject: Re: Numbering Exchange Protocol (NEP) ID.
From: Christopher Morrow
To: Khaled Omar
CC: rtgwg@ietf.org<mailto:rtgwg@ietf.org>,ietf


what problem were you trying to solve?

On Sat, Dec 9, 2017 at 11:32 AM, Khaled Omar <eng.khaled.omar@hotmail.com<mailto:eng.khaled.omar@hotmail.com>> wrote:
Hi everyone,

Please let me have the opportunity to ask all of you to reserve some time in your agenda for the discussion of NEP and give it a priority on the kist of your discussion as it will not take long time looking for something more to add.

I have confidence that this ID has more to add but the contents is just the start of the new protocol.

I hope I'm not bothering you by my question but I'm sure everyone of you has something on mind to add to make the ID take the best shape and please do not be afraid of posting any comment regarding the contents of the 2nd version of the I-D.

This long e-mail is to encourage you to participate and I'm sure the discussion will be exciting and please do not understand as i'm pushing you to participate, eventually it is up to you.

P.S. After finding the appropriate area or wg for the discussion I will stop sending e-mails to the ietf mailing list.

Thanks,

Khaled Omar


-------- Original Message --------
Subject: Numbering Exchange Protocol (NEP) ID.
From: Khaled Omar
To: rtgwg@ietf.org<mailto:rtgwg@ietf.org>
CC: ietf@ietf.org<mailto:ietf@ietf.org>


Hi everyone,

Below is one of the IDs that I uploaded to the IETF and looking for discussing it with the appropriate people and the appropriate area of discussion.

https://datatracker.ietf.org/doc/draft-omar-nep/

I tried to make it not so long so it can be read quickly and still clear for everyone.

Regards,

Khaled Omar