Re: issue #16
Joe Touch <[email protected]>
| Newsgroups | gmane.ietf.mobike |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jari Arkko wrote: | Joe Touch wrote: | |> Internet paths that are silent aren't problems, IMO. They're just idle |> network paths. | | Yes. | |> This sounds like a job for a link layer, and I don't think mobike needs |> to be a link layer. | | The link layer certainly has its own mechanisms, as does IP on | top of it (e.g. IPv6 NUD). But these are for a link, what we are | talking about here is a path through the Internet. More specifically, | the question is what to do if IKEv2 DPD tells us that its not getting | through. Should we (a) kill the connection or (b) switch to another | address we have? I think the latter... Links already react to things coming up and down. Routing already moves things around links that disappear. The key question is whether IKE should be doing something directly involving different addresses. That starts sounding like a routing or link management protocol, and can (and will) interact with link or routing adjustments. While I appreciate that IKE should retry, or allow reconecting, which could involve different addresses (i.e., different source address used on retry/restart), managing the addresses seems like it should be a side-effect of the restart (leave the source address blank, let it be filled in on exit) rather than explicitly managed. The latter is asking for interaction with link/routing reconfiguration, in a bad way, IMO. Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBvz9xE5f5cImnZrsRAqF7AJ40E7yWW3vb5SmPQbjrHWeVj9BwnACgkjww +EStuPmCkyvSJ5UIzZJfr2w= =dvur -----END PGP SIGNATURE-----