Re: [IPsec] INTERNAL_IP6_ADDRESS for link local address assignment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [IPsec] INTERNAL_IP6_ADDRESS for link local address assignment
On Wednesday 17 September 2008, Dan McDonald wrote:
> > Since the Interface Identifier is only used to form an IPv6
> > link-local address (non-link-local addresses can be configured from
> > the assigned prefixes and any interface identifier) it would be
> > simpler that the client's IPv6 link-local address is assigned via
> > the existing configuration attribute INTERNAL_IP6_ADDRESS,
>
> Agreed. (And isn't this what I mentioned earlier on this list?)
Yes, this is one of the things you mentioned.
> > while the INTERNAL_IP6_LINK would contain the Link Identifier only.
> >
> > What do you think?
> >
> > > 7.1. INTERNAL_IP6_LINK Configuration Attribute
> > >
> > > The INTERNAL_IP6_LINK configuration attribute is formatted as
> > > follows:
> > >
> > > 1 2 3
> > > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0
> > > 1
> > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > !R| Attribute Type ! Length |
> > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> NUKE> | Link-Local |
> NUKE> | Interface ID |
> NUKE> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> > > ~ IKEv2 Link ID ~
> > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> So INTERNAL_IP6_LINK would remove the bits I have prefixed with NUKE>
> ?
Right. And probably INTERNAL_IP6_LINK would become INTERNAL_IP6_LINKID.
> I have another question, but I suspect reading the draft will answer
> it.
All right then.
--julien
_______________________________________________
IPsec mailing list
IPsec at ietf.org
https://www.ietf.org/mailman/listinfo/ipsec
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.