>From: Keith Moore <[EMAIL PROTECTED]> > >> Or seperate the end system identifer from the routing goop. This >> solves lots of problems (while introducing others). > >even if you do this the end system identifier needs to be globally >scoped, and you need to be able to use the end system identifier >from anywhere in the net, as a means to reach that end system. > DNS is a bright and successfull example of such deal. It could be better to use domain names as system IDs but today there is too much software which assume IP as system ID (network ID of system in real). >otherwise you're in about the same shape as with a NATted network. - Leonid Yegoshin.
- Re: multihoming (was Re:draft-ietf-nat-pro... Steve Deering
- Re: multihoming (was Re: draft-ietf-na... Paul Francis
- Re: multihoming (was Re: draft-ietf-nat-pr... Thomas Narten
- Re: multihoming (was Re: draft-ietf-na... Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Pyda Srisuresh
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Daniel Senie
- Re: draft-ietf-nat-protocol-complications-02.txt Sean Doran
- Re: draft-ietf-nat-protocol-complications-02.txt Leonid Yegoshin
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.t... Bill Manning
- Re: draft-ietf-nat-protocol-complications-... Valdis . Kletnieks
- Re: draft-ietf-nat-protocol-complicati... Bill Manning
- Re: draft-ietf-nat-protocol-compl... Eliot Lear
- Re: draft-ietf-nat-protocol-complications-... Keith Moore
- Re: draft-ietf-nat-protocol-complicati... Bill Manning
- Re: draft-ietf-nat-protocol-compl... Keith Moore
- Re: draft-ietf-nat-protocol-complicati... David R. Conrad
- Re: draft-ietf-nat-protocol-compl... Keith Moore