From: Khaled Omar <[email protected]<mailto:[email protected]>> Date: Saturday, December 9, 2017 at 6:03 PM To: Acee Lindem <[email protected]<mailto:[email protected]>>, Christopher Morrow <[email protected]<mailto:[email protected]>> Cc: Routing WG <[email protected]<mailto:[email protected]>> 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 <[email protected]<mailto:[email protected]>> on behalf of Khaled Omar <[email protected]<mailto:[email protected]>> Date: Saturday, December 9, 2017 at 3:40 PM To: Christopher Morrow <[email protected]<mailto:[email protected]>> Cc: Routing WG <[email protected]<mailto:[email protected]>> 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: [email protected]<mailto:[email protected]>,ietf what problem were you trying to solve? On Sat, Dec 9, 2017 at 11:32 AM, Khaled Omar <[email protected]<mailto:[email protected]>> 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: [email protected]<mailto:[email protected]> CC: [email protected]<mailto:[email protected]> 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
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
