[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
NEMO and draft-tsirtsis-dsmip-problem-03
Hi Hesham and George
Thanks a lot for this great piece of work.
"
- it should be possible to create IPv4 extensions to Mobile IPv6 so
that a dual stack mobile node can register its IPv4 and IPv6 HoAs to
a dual stack Home Agent using MIPv6 signaling only.
"
NEMO angle here: NEMO could but would not necessarily need to register
an IPv4 home address. This would be useful only if returning home is a
constraint, otherwise HoA is but a correlator and a single IPv6 address
should be enough for both.
OTOH, support for address families to register IPv4 prefixes could be
very useful. Sri and I will submit something soon to NEMO for this.
IMHO, mentioning AF in your draft would basically extend its scope to
encompass NEMO as well. If that's fine with you, I would suggest
something like:
'
- it should be possible to add Address Family to NEMO Basic Support
so
that a dual stack mobile router can register its IPv4 and IPv6
prefixes to
a dual stack Home Agent using MIPv6 signalling only.
'
"
- it should also be possible to extend MIPv4 and MIPv6 so that a
mobile can register a single CoA (IPv4 or IPv6) to which IPv4 and/or
IPv6 packets can be diverted to.
"
Agreed. Note that this does not necessarily means changing the
signalling to the HA. As you know, doors hides the v4 address in a v6
pseudo coa and the MIP/NEMO protocol is left unchanged; and so is the HA
if the doors gateway is remote. I think there's value to that and we'll
discuss that at the requirement time. For the time being, I think the
text here is open enough and I'm not suggesting changing it.
Pascal