![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi,
"mext" <trac at tools.ietf.org> writes:
> [editorial note by Charles E. Perkins]:
> Following this, there was a discussion about how to enable
> an IKE daemon to use the care-of address. Since that seems
> out of scope for rfc3775bis, I have not included it as part
> the discussion for this issue.
Ack.
I think I started the discussion with Julien on that point, because of
the following from section 3 in RFC 5014:
Another example is the IKE
application, which requires a care-of address as its source address
for the initial security association pair with a Home Agent [RFC3775]
while the mobile node boots up at the foreign network and wants to do
the key exchange before a successful home-registration.
I have no specific problems with the changes proposed by Julien but I
don't like the idea of having a pointer in RFC 3775 leading developers
looking how to use the CoA for IKE implementation with MIPv6 to the
previous block of text. Simply because there are open issues (to say
the least): I am still waiting to be proven otherwise, but got no
response to the last mail of previous thread:
Archived-At: <http://permalink.gmane.org/gmane.ietf.mip6/7611>
As far as I can tell, the only *working* solution (i.e. *implemented*,
i.e. not just *expected* to work after paper review) is derived from
draft-sugimoto-mip6-pfkey-migrate-04.txt.
I'll post more on that before the end of July.
Cheers,
a+
Attachment:
pgpmdg2q3wgBh.pgp
Description: PGP signature
_______________________________________________ MEXT mailing list MEXT at ietf.org https://www.ietf.org/mailman/listinfo/mext