[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RRG] Loc/id split using the data link layer
- To: "RRG Mailing List" <rrg@psg.com>
- Subject: [RRG] Loc/id split using the data link layer
- From: "Victor Grishchenko" <victor.grishchenko@gmail.com>
- Date: Tue, 4 Mar 2008 15:19:37 +0500
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=P7cVpVgcOKiMQNAT/S73kcE4WjtFCKGiZ9kRkKm9Noec1RJChBwgaPX5MCNCaucf7NbWrbPn5kKPrPO5guACdm11+J4DRxEndWFYiREB8Wgy8ttgKu1bSffLlPZrB94+QzVWraOLkpbPaB+4jKVrC1ZggLtDLkPCClqyGNhw8Q4=
I think I found a way to perform loc/id split using 2 layer
(ethernet), albeit I am not sure how practical it is. Namely, by
redefining MAC address to be a MAN-wide topology-dependent locator and
using a prefix-bunch addressing scheme (yes, it is possible).
What surprised me most is the possibility of dumb-dumb-dumb Ethernet
switching logic employing no routing/MAC tables, associative memory or
longest prefix matches.
This is not a proposal for RRG as (1) it does not need to be (2) it
can't solve the 3rd layer scalability problems, just ease them a bit.
It might be interesting from the standpoint of Metro Ethernet
technologies or general curiousness.
The paper is very compressed (2 pages), so don't hesitate to ask.
http://oc-co.org/articles/MAC-loc.pdf
--
Victor
--
to unsubscribe send a message to rrg-request@psg.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg