On Sep 11, 2012, at 2:36 AM, Brian E Carpenter wrote: >> What's that rule called? TAANSTAAFL, as I recall. Pretending won't make it >> otherwise. Either the service providers deal with the complexities of the >> IPv4 route table, or the edge networks deal with the complexities of >> managing prefixes from each of multiple upstream PA prefixes, or DNS >> advertises inside and outside addresses somehow. Pick one. > > This being the Internet, I expect we'll pick several. But indeed, we have > to deal with current reality and also try to influence long term trends > in a desirable way. I think that getting the problem area well described > is the first step.
I'll suggest that you and I collaborate on a note describing the issue, and why having applications know anything about network layer addresses in the first place is unwise. Sometimes necessary, perhaps, but implies the design decision to make this issue hard for that application, and to be avoided or mitigated when possible. We can refer to RFC 3439's section 2.2.2. _______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
