1 / 3

Terminology Definition Discussions

In the quest for effective routing scalability, it's essential to define and address various problems. This involves developing solutions and comparing them to foster a meaningful discussion. A common set of terminology is crucial to articulate these issues effectively. We explore key concepts like addresses in the Default Free Zone (DFZ) routing table, those outside it, and terms like "EID" and "Stack ID." This discourse aims to clarify identifiers necessary in higher-layer networking, beyond the transport layer. We invite collaboration to refine our understanding and solutions.

saki
Télécharger la présentation

Terminology Definition Discussions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Terminology Definition Discussions

  2. Why Need This • We define problems • We develop solutions • We discuss and compare different solutions • We need a common set of terminology for all the above • What presented below meant to be input to discussion

  3. How many different things That need to be described in the context of routing scalability? • Addresses that are in the DFZ routing table • Addresses that are not in the DFZ • Example: this thing that LISP called “EID”, but really not an end point identifier • “endpoint” identifier • Debates going on whether call it “Stack ID” • Identifiers needed at higher layer • Above transport layer?

More Related