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

RE: to be draft-ohta-multi6-8plus8-00.txt



> How can transport layer protocols detect that an end or its peer
> is capable of M6?

As far as i understand, in order to support 8+8 you have to change transport
protocols, right?
So just add an option that means that you supprt address agile version of
the transport protocol.

>
> How can you make IDs survive ISP changes?

Well, this is a plus but it is not the problem that we are trying to solve
here, right?

this is a problem about changing isps, so we could have a multihoming
solution that don't provide this (though i agree that i would be good to
solve this problem too)

>
> How can you be sure to rewrite addresses at the IP layer, if
> you are not sure that all the transport layer protocols can
> still identify an end?

No, i was thinking in something like TCP-MH

>
> > In other words, as your architectural draft explains, your solutions is
> > completelly end to end, so the ends can have the information about what
> > locators are linked to an identifier and which is the
> identifier to be used
> > for each connection, so why is required to reflect this loc/id
> split in the
> > address itself?
>
> There are elegant and not so elegant ways to implement an
> architecture.
>
> Have I answered your question?

I think so, thanks, marcelo

>
> 							Masataka Ohta
>
>
>