Sending of Delegated-IPv6-Prefix from the DHCPv6 Local Server to SRC Client Overview

You can configure a DHCPv6 local server to send the Delegated-IPv6-Prefix with a PPPv6 interface name to an SRC client after delegating IPv6 prefixes to a CPE. The SRC client sends the Delegated-IPv6-Prefix to an SRC server. The SRC server uses the Delegated-IPv6-prefix to authenticate DHCPv6 subscribers logging in to the website for service activation. The SRC server authenticates the DHCPv6 subscribers by comparing their IPv6 prefixes with the set of IPv6 prefixes stored in the SRC server. After authentication, the DHCPv6 subscriber activates a service. On service activation, the SRC server pushes the respective service classifiers to the PPPv6 interface.


  • Because an interface supports only 512 classifiers per direction (ingress or egress), there is a possibility to have subscribers without any service.
  • For all subscribers, the SRC server sends the Acct-Stop message to the RADIUS server only on CPE termination or DHCPv6 prefix release, but not when the subscriber is terminated.
  • The DHCPv6 local server sends the Delegated-IPv6-prefix allocation or removal notifications to an SRC client only when the DHCP subscribers are in bound state.

You can enable the DHCPv6 local server to send the Delegated-IPv6-Prefix with the PPPv6 interface name to the SRC client by using the ipv6 dhcpv6-local sscc command. Before you enable this feature, you must enable the SRC client’s COPS support by using the sscc enable command, the policy and QoS configuration support for IPv6 interfaces by using the sscc protocol ipv6 command, and the DHCPv6 local server by using the service dhcpv6-local command.

This feature does not support the following:

The COPS-PR Policy Information Base (PIB) is modified with a new class junoseIpv6DhcpAddressClasses and two new objects such as JunoseIpv6AddressRequestEntry and JunoseIpv6DhcpDecisionEntry for the following:

Related Documentation