This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Proposal 2011-02 moving to Last Call
- Previous message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
- Next message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Michel Py
michel at arneill-py.sacramento.ca.us
Sun Oct 2 06:02:15 CEST 2011
>> Michel Py wrote: >> As of ID/LOC schemes, there is this myth that the table is >> small but in practice large environments will have to >> maintain a very large ID/LOC map which brings us back to >> the size of the DFZ again. > David Conrad wrote: > The timescales within which lookups in an ID/LOC map > must occur are a bit different than those in a FIB. This is true, but put it back in prospective: the ID/LOC map may gain another order of magnitude. So may Moore's law over a few years, and we're back to square one. Think about it as the TCP sliding window: ID/LOC skews the window a bit, but the gain obtained is questionable compared to the loss due to the increased complexity. How good does it do to you to optimize 100Mbit Ethernet when it is cheaper to build GigE? I'm not saying I like it, but that's the way it is. Simplicity is priceless. Michel.
- Previous message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
- Next message (by thread): [address-policy-wg] Proposal 2011-02 moving to Last Call
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]