i am told that the following session has been accepted for the nanog agenda. A Comparison of Approaches to Loc/ID, Routing Scaling, and the Universe Abstract: This session looks at and contrasts: LISP (Dino Farinacci) ILNP (Saleem Bhatti) RFC 6296 (Fred Baker) Where each is explained at an architectural level in some detail with a predetermined list of questions such as "how does this address loc/id separation, routing table scaling, incremental deployment, state of implementation/testing, ..." And then a half hour where we all sum up the similarities and differences. Maybe it will be worth writing up. The goal is education and understanding, not a contest. These are all good and interesting approaches. Weapons are not allowed, we all work for the Internet. as you can see, i am interested in o loc/id separation o rounting table scaling o deployability on the internet o current state of development what did i miss? what major attributes interest you? randy
On Sat, Aug 20, 2011 at 01:57:36PM -0700, Randy Bush wrote:
as you can see, i am interested in o loc/id separation o rounting table scaling o deployability on the internet o current state of development
what did i miss? what major attributes interest you?
o Trust model (how much trust is put in whom so that connectivity works) o How much state where o Security implications (where are the weak links, vectors for attack) o Traffic engineering (ingress and egress) features o Session survivability on rerouting (manual and due to outages) Best regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
On Sat, Aug 20, 2011 at 2:37 PM, Daniel Roesen <dr@cluenet.de> wrote:
On Sat, Aug 20, 2011 at 01:57:36PM -0700, Randy Bush wrote:
as you can see, i am interested in o loc/id separation o rounting table scaling o deployability on the internet o current state of development
what did i miss? what major attributes interest you?
o Trust model (how much trust is put in whom so that connectivity works) o How much state where o Security implications (where are the weak links, vectors for attack) o Traffic engineering (ingress and egress) features o Session survivability on rerouting (manual and due to outages)
- complexity (define a metric [eek!] ...) - overhead (who, what, where, why..[closely tied with the "state" question]) - who benefits and who pays? endpoints? backbones ISPs in the DFZ? SMB? Enterprises? Router companies? ... it's like Lenin said, you look for the person who will benefit and...
>> o Trust model (how much trust is put in whom so that connectivity works) >> o How much state where >> o Security implications (where are the weak links, vectors for attack) >> o Traffic engineering (ingress and egress) features >> o Session survivability on rerouting (manual and due to outages) > - complexity (define a metric [eek!] ...) good luck with that one > - overhead (who, what, where, why..[closely tied with the "state" > question]) > - who benefits and who pays? endpoints? backbones ISPs in the DFZ? > SMB? Enterprises? Router companies? ... it's like Lenin said, you > look for the person who will benefit and... i think of this as 'economic model.' what will change from the current model? privacy has also been suggested as an issue. randy
participants (3)
-
Cameron Byrne -
Daniel Roesen -
Randy Bush