![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Spencer,
SD> multihomed *hosts*. So, not only is ipv4 technically off-topic for SD> multi6, but things like id/loc separation impacts on transports and SD> applications should be, too.
SD> Maybe we can migrate the appropriate people over...
I would like for this to be the right venue, but please note that the charter for the list cast the issue as an addressing topic. Some of the proposals -- no surprise, this includes MAST -- solve mobility and multihoming without creating any new, long-term identification structure. They use session-internal, ephemeral identifiers, but nothing registered or public.
I read the charter as precluding this solution path.
Please tell me I'm reading it wrong (and how) or perhaps we can revise the charter wording some?
d/ -- Dave Crocker <dcrocker-at-brandenburg-dot-com> Brandenburg InternetWorking <www.brandenburg.com> Sunnyvale, CA USA <tel:+1.408.246.8253>
_______________________________________________ Saad mailing list Saad@ietf.org https://www1.ietf.org/mailman/listinfo/saad |