Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


OnePopPrefixIp Scenario


This section describes the NIC functionality required to support the IPv6 feature. Subscribers are identified by a set of IPv6 prefixes defined by the device. These IPv6 prefixes are made available to the NIC through SAE IPv6 plug-in attributes (framedIpv6Prefix and delegatedIpv6Prefix) and these attributes can be present for the same subscriber session. The SAE reports the IPv6 plug-in attributes to the NIC and any IP address starting with one of these IPv6 prefixes identifies the user session in the SAE.

The OnePopPrefixIp scenario supports the IPv6 feature. This scenario enables applications to identify subscribers based on their IP addresses and obtain a reference to the SAE managing these subscribers.

The OnePopPrefixIp configuration scenario is very similar to the OnePop scenario. In the OnePopPrefixIp scenario, the IP pool information is provided by the SAE (through NIC SAE plug-in agents) instead of being read from the directory.


The OnePopPrefixIp scenario can be used in IPv4 or IPv6 dual-stack configuration. See SAE Support for Dual-Stack Configuration for more information.

The following agents collect information for resolvers:

  • SAE plug-in agent DelegatedIpVr (using the PA_DELEGATED_IPV6_PREFIX attribute) collects information about the mappings of IP pools to VRs.

  • SAE plug-in agent FramedIpVr (using the PA_FRAMED_IPV6_PREFIX attribute) collects information about the mappings of IP pools to VRs.

  • SAE plug-in agent InetAddressVr (using the PA_USER_INET_ADDRESS and PA_USER_IP_MASK attributes) collects information about the mappings of IP pools to the VRs.

  • Consolidator agent IpPool collects information from DelegatedIpVr, FramedIpVr, and InetAddressVr agents and publishes the list of known IP pools.

  • Directory agent VrSaeId collects and publishes information about the mappings of VRs to the SAE.

In this configuration, the single host DemoHost supports all agents and resolvers. When the NIC proxy sends a subscriber’s IP address to the host, the following sequence of events occurs:

  1. The host passes the subscriber’s IP address to resolver A1.

  2. Resolver A1 returns the IP pool that best matches the IP address. This is synonymous with the longest or most specific match. For example, an IP address of 2001:db8:1:1:0:1:2:3 matches Pool1 (2001:db8:1:1::/64) and Pool2 (2001:db8:1:1::/32). In this case, the resolver returns Pool2 because it has the most specific match.

  3. Resolver B1 obtains a VR name for the IP pool name and returns the VR name to resolver A1.

  4. Resolver A1 forwards the VR name to resolver C1.

  5. Resolver C1 obtains an SAE reference for the VR and returns the VR identity to resolver A1.

  6. Resolver A1 passes the SAE reference to its host.

  7. The host returns the SAE reference to the NIC proxy.

Figure 55 shows the interactions of the NIC components for this realm.

Figure 55: OnePopPrefixIp Configuration
OnePopPrefixIp Configuration