> 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. otherwise you're in about the same shape as with a NATted network. Keith
- 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 Steve Deering
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt John Stracke
- Re: draft-ietf-nat-protocol-complications-02... Theodore Y. Ts'o
- Re: draft-ietf-nat-protocol-complications-02.txt Masataka Ohta
- Re: draft-ietf-nat-protocol-complications-02.txt Andrew Partan
- Re: draft-ietf-nat-protocol-complications-02.txt Paul Ferguson
- Re: draft-ietf-nat-protocol-complications-02.txt Keith Moore
- Re: draft-ietf-nat-protocol-complications-02.txt Thomas Narten
- Re: draft-ietf-nat-protocol-complications-02.txt Bill Manning
- Re: draft-ietf-nat-protocol-complications-02... Steve Deering
- Re: draft-ietf-nat-protocol-complication... Bill Manning
- Re: draft-ietf-nat-protocol-complic... Steve Deering
- Re: draft-ietf-nat-protocol-com... Bill Manning
- Re: draft-ietf-nat-protocol-com... Steve Deering
- Re: draft-ietf-nat-protocol-complication... David R. Conrad
- Re: draft-ietf-nat-protocol-complic... Steve Deering
- Re: draft-ietf-nat-protocol-com... David R. Conrad