Subscriber Services: Forward-only action for DHCP relayed traffic with unknown DHCP server address

Forward-only action for DHCP relayed traffic is supported with unknown DHCP server address. Administrator is able to configure for which servers (clients are binding) they need to have relay subscriber entry, apply dynamic profile, policies and more, and for whom they want to forward only. This feature also introduces configuration for processing destination address, option-54 and option-2 on DHCP relay. DHCP relay agent entry will be useful for authentication, authorization, accounting, applying filtering, QoS to client, processing of options specified in the packet. Customer networks can contain non-customer controlled bindings for which the customer does not want these relay agent entry functionalities. Hence relay agent subscriber entries are not created for non-customer controlled bindings. Subscriber entry creation constituted of Junos OS DHCPD (DHCP daemon) memory resources, session database resources, authentication procedure, accounting, dynamic profile instantiation, dynamic interface creation, firewall, CoS association, and more. if a customer network has some non-customer controlled traffic for which a relay agent entry is created then it would be an unnecessary utilization of resources, and an incorrect association of profiles.