[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RRG] Six/One Router Design Clarifications



a quick reply to specifics:


On Jul 17, 2008, at 6:42 PM, Brian E Carpenter wrote:

On Jul 16, 2008, at 8:27 PM, Brian E Carpenter wrote:


PS: FWIW, I understand issue (c) as being of less grave nature than issues (a) and (b). Issue (c) is an implementation
issue, NOT an architectural issue like issues (a) and (b).

Absolutely not. It's an architectural issue in the session layer, when session IDs have no universality.

let me understand this better: my understanding is that six/one router (it ought to be renamed to just IPv6 Address translator, or 6AT) performs a one to one matching. So although the exact value of the "ID" may not be exactly the same before or after an 6AT, nonetheless the session is uniquely identified -- would that be considered as having universality?

In my opinion, not if the two ends have a different opinion
about the addresses being used, because we use addresses as
identifiers.

this issue may become moot, in lieu of next point below:

Lixia PS: in the above I used Brian's terminology, but my personal view is that, in the long run, session layer should move
away from using IP address entirely.

I completely agree, but the problem is that this isn't how the
Internet has been constructed. I'm very pessimistic about changing
this (and it surely isn't the routing community that can change all
the applications).

    Brian

I think we should always separate the two issues:
1/ what's out there today
2/ where we want to go
in order to progress forward.
I agree that changes are challenging and cannot happen quickly (physics says that the inertia is linearly proportional to the mass; for us it's probably not linear). But another fact is that IETF is busy developing new protocols:)
The world evolves, protocols and architectures should too accordingly.

Lixia

--
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