Lines Matching refs:IA
217 addresses, we must have multiple IP logical interfaces per IA
221 IP logical interfaces) per IA and multiple IAs per client/server
242 single identity association (IA), we should not store all of the
260 address (LIF) and IA groupings with shared T1/T2 timers. To
268 support other IA types.)
281 For DHCPv6, we need to track multiple LIFs per lease (IA), but we
299 of that LIF (it was created because of a DHCPv6 IA), and disposal
357 IA structure) points to a separate set of LIFs that are created just
358 for the leased addresses (one per IA address in an IAADDR option).
572 or rebinding state, based on the T1/T2 timers for each IA, and many
597 - When we reach T2 on any IA and we're in BOUND or RENEWING state,
611 lifetime, remove them from the system. When an IA (lease)
620 on one IA, the server will suddenly start responding when we attempt
621 to renew some other IA. We rationalize this behavior by using a
1072 status code only makes sense within an IA, as it refers to the
1073 GUID:IAID binding, which doesn't exist outside an IA. We must