Nimrod - Revision history

Jnc: Two main foundation stones

2025-09-20T15:14:50Z

Two main foundation stones

Jnc: A few words about mechanisms

2024-02-29T08:07:43Z

A few words about mechanisms

Jnc: Stubby; mostly a place to hold links

2022-07-05T19:25:44Z

Stubby; mostly a place to hold links

New page

'''Nimrod''' was a proposed [[routing architecture]] for the [[Internet]]; intended to provide a very powerful routing system, one that would also scale indefinitely as the Internet grew (like [[Domain Name System|DNS]] does).

It covers a lot more than just [[path selection]]. That's because the [[architecture]] embodied in [[IPv4]] was missing lots of things which one would need to do the [[internetworking layer|internet layer]] 'right' in a global-scale Internet (e.g. variable length '[[address]]es' - for which Nimrod was forced to invent the term 'locator' because many people in the [[Internet Engineering Task Force|IETF]] couldn't wrap their minds around 'addresses' which weren't in every [[packet header]]). And separation of location and identity; and the introduction of traffic aggregates as first-class objects at the internet layer. Etc, etc, etc.

Nimrod's main focus was really on i) providing a path-selection system which allowed things like letting users have more input to selecting the path their traffic took (just as when one gets into a car, one gets to pick the path one's going to use), and ii) controlling the overhead of the routing.

{{semi-stub}}

==External links==

* [https://www.rfc-editor.org/rfc/rfc1992.txt The Nimrod Routing Architecture]
* [https://www.rfc-editor.org/rfc/rfc1753.txt IPng Technical Requirements of the Nimrod Routing and Addressing Architecture]

[[Category: Internet]]

@@ Line 1: / Line 1: @@
-'''Nimrod''' was a proposed [[routing architecture]] for the [[Internet]]; intended to provide a very powerful routing system, one that would also scale indefinitely as the Internet grew (like [[Domain Name System|DNS]] does).
+'''Nimrod''' was a proposed [[routing architecture]] for the [[Internet]]; intended to provide a very powerful routing system, one that would also scale indefinitely as the Internet grew (like [[Domain Name System|DNS]] does). It has two main foundation stones:
-It covers a lot more than just [[path selection]]. That's because the [[architecture]] embodied in [[IPv4]] was missing lots of things which one would need to do the [[internetworking layer|internet layer]] 'right' in a global-scale Internet (e.g. variable length '[[address]]es' - for which Nimrod was forced to invent the term 'locator' because many people in the [[Internet Engineering Task Force|IETF]] couldn't wrap their minds around 'addresses' which weren't in every [[packet header]]). And separation of location and identity; and the introduction of traffic aggregates as first-class objects at the internet layer. Etc, etc, etc.
+It covers a lot more than just [[path selection]], though; that's because the [[architecture]] embodied in [[IPv4]] was missing lots of things which one would need to do the [[internetworking layer|internet layer]] 'right' in a global-scale Internet (e.g. variable length '[[address]]es' - for which Nimrod was forced to invent the term 'locator' because many people in the [[Internet Engineering Task Force|IETF]] couldn't wrap their minds around 'addresses' which weren't in every [[packet header]]). And separation of location and identity; and the introduction of traffic aggregates as first-class objects at the internet layer. Etc, etc, etc.
 Nimrod's main focus was really on i) providing a path-selection system which allowed things like letting users have more input to selecting the path their traffic took (just as when one gets into a car, one gets to pick the path one is going to use), and ii) controlling the overhead of the routing.

@@ Line 3: / Line 3: @@
 It covers a lot more than just [[path selection]]. That's because the [[architecture]] embodied in [[IPv4]] was missing lots of things which one would need to do the [[internetworking layer|internet layer]] 'right' in a global-scale Internet (e.g. variable length '[[address]]es' - for which Nimrod was forced to invent the term 'locator' because many people in the [[Internet Engineering Task Force|IETF]] couldn't wrap their minds around 'addresses' which weren't in every [[packet header]]). And separation of location and identity; and the introduction of traffic aggregates as first-class objects at the internet layer. Etc, etc, etc.
-Nimrod's main focus was really on i) providing a path-selection system which allowed things like letting users have more input to selecting the path their traffic took (just as when one gets into a car, one gets to pick the path one's going to use), and ii) controlling the overhead of the routing.
+Nimrod's main focus was really on i) providing a path-selection system which allowed things like letting users have more input to selecting the path their traffic took (just as when one gets into a car, one gets to pick the path one is going to use), and ii) controlling the overhead of the routing.
 {{semi-stub}}