Lines Matching refs:IA
219 addresses, we must have multiple IP logical interfaces per IA
223 IP logical interfaces) per IA and multiple IAs per client/server
244 single identity association (IA), we should not store all of the
262 address (LIF) and IA groupings with shared T1/T2 timers. To
270 support other IA types.)
283 For DHCPv6, we need to track multiple LIFs per lease (IA), but we
301 of that LIF (it was created because of a DHCPv6 IA), and disposal
359 IA structure) points to a separate set of LIFs that are created just
360 for the leased addresses (one per IA address in an IAADDR option).
574 or rebinding state, based on the T1/T2 timers for each IA, and many
599 - When we reach T2 on any IA and we're in BOUND or RENEWING state,
613 lifetime, remove them from the system. When an IA (lease)
622 on one IA, the server will suddenly start responding when we attempt
623 to renew some other IA. We rationalize this behavior by using a
1074 status code only makes sense within an IA, as it refers to the
1075 GUID:IAID binding, which doesn't exist outside an IA. We must