| Hi Will, Thanks for your comments and my apologies for the length of time that it’s taken me to reply. Regarding your suggestion for running the server on specific interfaces or IP addresses and making an assignment decisions based on that, the way that the example YANG modules would handle this is as follows. Interface / listener address & port is configured via the following portion of example-dhcpv6-server-conf.yang: leaf ipv6-listen-port { type uint16; default 547; description "UDP port that the server will listen on."; } choice listening-interfaces { default all-interfaces; description "Configures which interface or addresses the server will listen for incoming messages on."; case all-interfaces { container all-interfaces { presence true; description "Configures the server to listen for incoming messages on all IPv6 addresses (unicast and multicast) on all of its network interfaces."; } } case interface-list { leaf-list interfaces { type if:interface-ref; description "List of interfaces on which the server will listen for incoming messages. Messages addressed to any valid IPv6 address (unicast and multicast) will be received."; } } case address-list { leaf-list address-list { type inet:ipv6-address; description "List of IPv6 address(es) on which the server will listen for incoming DHCPv6 messages."; } } } leaf-list interfaces-config { type if:interface-ref; default "if:interfaces/if:interface/if:name"; description "A leaf list of interfaces on which the server should listen."; } Making address/prefix assignments based on the interface/address that a request is received on is treated as a class-selection function (along with other address/prefix selection criteria). The following portion of Example-dhcpv6-class-select.yang would do this: case received-interface-id { description "Client class selection based on the incoming interface of the DHCPv6 message."; leaf received-interface { type if:interface-ref; description "Reference to the interface entry for the incoming DHCPv6 message."; } } case packet-source-address-id { description "Client class selection based on the source address of the DHCPv6 message."; leaf packet-source-address { type inet:ipv6-address; mandatory true; description "Source address of the DHCPv6 message."; } } case packet-destination-address-id { description "Client class selection based on the destination address of the DHCPv6 message."; leaf packet-destination-address { type inet:ipv6-address; mandatory true; description "Destination address of the DHCPv6 message."; } } Does this address your comment? Thanks, Ian
|
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
