Tero Kivinen wrote:
> > 3.2 ADDITIONAL_ADDRESS notification payload
> >
> > Both initiator and responder can include
> > ADDITIONAL_ADDRESS payloads in the IKE_AUTH exchange and
> > INFORMATIONAL exchange request messages; see Section 2.2
> > and Section 2.4 for more detailed description.
> >
> > The Notify Message Type for ADDITIONAL_ADDRESS is
> > TBD-BY-IANA (16396..40959). The Protocol ID field is set
> > to one (1), and SPI Size is set to zero. The data
> > associated with this Notify type is either an IPv4
> > address or an IPv6 address; the type is determined by the
> > payload length.
>
> I think it is better to take 2 different notification types
> for IPv4 and IPv6. Checking the lenght is bad, as then we
> cannot extend the structure later by adding more information
> to the notification data. The design draft asks this in the
> section 5.11, i.e. make the format so we can extend in the
> future it with new data, like load balancing weight (currently
> out of scope, but one of the possible future works).
Sounds OK to me; I'll change that to ADDITIONAL_IP4_ADDRESS
and ADDITIONAL_IP6_ADDRESS in -01.
Best regards,
Pasi
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.