Patent Application
20200186349
The present disclosure generally relates to secured protection of advertisement parameters in a zero trust low power and lossy network.
This section describes approaches that could be employed, but are not necessarily approaches that have been previously conceived or employed. Hence, unless explicitly specified otherwise, any approaches described in this section are not prior art to the claims in this application, and any approaches described in this section are not admitted to be prior art by inclusion in this section.
A Low-power and Lossy Network (LLN) is a network that can include dozens or thousands of low-power router devices configured for routing data packets according to a routing protocol designed for such low power and lossy networks (RPL): such low-power router devices can be referred to as “RPL nodes”. Each RPL node in the LLN typically is constrained by processing power, memory, and energy (e.g., battery power); interconnecting links between the RPL nodes typically are constrained by high loss rates, low data rates, and instability with relatively low packet delivery rates. A network topology (a “RPL instance”) can be established based on creating routes in the form of a directed acyclic graph (DAG) toward a single “root” network device, also referred to as a “DAG root” or a “DAG destination”. Hence, the DAG also is referred to as a Destination Oriented DAG (DODAG). Network traffic moves either “up” towards the DODAG root or “down” towards the DODAG leaf nodes.
The DODAG can be formed based on a DODAG information object (DIO) advertised by the DAG root, where a “child” network device detecting the DIO can select the DAG root as a parent in the identified DODAG based on comparing network topology metrics (advertised in the DIO) to a prescribed objective function of the RPL instance. The “child” network device, upon attaching to its parent, can output its own DIO with updated network topology metrics that enable other network devices to discover the DODAG, learn the updated network topology metrics, and select a DODAG parent.
Downward routes (i.e., away from the DAG root) can be created based on Destination Advertisement Object (DAO) messages that are created by a RPL node and propagated toward the DAG root. The RPL instance implements downward routes in the DAG of the LLN in either a storing mode only (fully stateful), or a non-storing mode only (fully source routed by the DAG root). In storing mode, a RPL node unicasts its DAO message to its parent node, such that RPL nodes store downward routing table entries for their “sub-DAG” (the “child” nodes connected to the RPL node). In non-storing mode the RPL nodes do not store downward routing tables, hence a RPL node unicasts its DAO message to the DAG root, such that all data packets are sent to the DAG root and routed downward with source routes inserted by the DAG root.
Existing proposals for securing a RPL network fail to address scenarios where an attacking network device is able to gain access to the secured RPL network, for example in cases where the attacking network device obtains a security key used within the RPL network.
Reference is made to the attached drawings, wherein elements having the same reference numeral designations represent like elements throughout and wherein:
In one embodiment, a method comprises receiving, by a parent network device providing at least at portion of a directed acyclic graph (DAG) according to a prescribed routing protocol in a low power and lossy network, a destination advertisement object (DAO) message, the DAO message specifying a target Internet Protocol (IP) address claimed by an advertising network device in the DAG and the DAO message further specifying a secure token associated with the target IP address; and selectively issuing a cryptographic challenge to the DAO message to validate whether the advertising network device generated the secure token.
In another embodiment, an apparatus is implemented as a physical machine and comprises non-transitory machine readable media configured for storing executable machine readable code, a device interface circuit, and a processor circuit. The device interface circuit is configured for receiving a destination advertisement object (DAO) message in a low power and lossy network, the apparatus implemented as a parent network device providing at least at portion of a directed acyclic graph (DAG) according to a prescribed routing protocol in the low power and lossy network. The processor circuit is configured for executing the machine readable code. The processor circuit, when executing the machine readable code is operable for: determining the DAO message specifies a target Internet Protocol (IP) address claimed by an advertising network device in the DAG, and that the DAO message further specifies a secure token associated with the target IP address; and selectively issuing a cryptographic challenge to the DAO message to validate whether the advertising network device generated the secure token.
In another embodiment, one or more non-transitory tangible media encoded with logic for execution by a machine and when executed by the machine operable for: receiving, by the machine implemented as a parent network device providing at least at portion of a directed acyclic graph (DAG) according to a prescribed routing protocol in a low power and lossy network, a destination advertisement object (DAO) message, the DAO message specifying a target Internet Protocol (IP) address claimed by an advertising network device in the DAG and the DAO message further specifying a secure token associated with the target IP address; and selectively issuing a cryptographic challenge to the DAO message to validate whether the advertising network device generated the secure token.
Particular embodiments provide a scalable protection of RPL nodes in a RPL network from unauthorized network devices or attacking network devices that attempt to gain access within the RPL network, or that attempt to claim RPL network parameters of other RPL network devices. The particular embodiments provide scalable protection of the RPL nodes based on utilizing secure tokens generated using private cryptographic keys owned by the respective RPL nodes, without the reliance of computation-intensive encryption techniques that are not suitable for constrained low power and lossy network devices.
In one example embodiment, a RPL root network device (and/or a common parent in the DAG, described below), can selectively issue a cryptographic challenge to a DAO message associated with an advertising network device, regardless of whether the DAO message was already originated by a RPL parent device providing an attachment to the advertising network device for communications within the DAG. The DAO message propagated within the DAG also can include a secure token associated with the target IP address claimed by the advertising network device in the DAG: any RPL parent device can validate whether the advertising network device owns the secure token based on the RPL parent device obtaining one or more parameters used to build the secure token (including, for example, a public cryptographic key), and receiving a cryptographic data structure (“signature”) responsive to the cryptographic challenge that proves the advertising network device owns the private cryptographic key that corresponds to the public cryptographic key used to build the secure token.
As described in further detail below, the above-described example embodiment can protect the target IP address in the DAO message in a scalable manner that can be implemented by constrained low-power RPL nodes, even without the necessity of securing the DAO message by encrypting the target IP address as described in the Internet Engineering Task Force (IETF) Request for Comments (RFC) 6550, and without the reliance on the computationally-expensive operation of generating cryptographic addresses (as described in RFC 3971, entitled “Secure Neighbor Discovery (SEND)”).
Moreover, since the above-described example embodiment can protect the target IP address in the DAO message without encrypting the target IP address as described in RFC 6550, the above-described example embodiment can protect the target IP address in the DAO message without the necessity of sharing any link-local cryptographic key, or without the necessity of sharing any network-wide cryptographic key that could risk exposing the LLN (e.g., a CG-Mesh based electric grid) to an unauthorized network device (e.g., a consumer intelligent washing machine at a subscriber premises); further, the above-described embodiment can still protect the target IP address, even if an unauthorized network device were to gain access to the link-local cryptographic key or any network-wide cryptographic key, because the example embodiments can protect the target IP address based on issuing a challenge that requires an advertising device to prove it owns the associated secure token.
As described in further detail below, the above-described example embodiment also enables the secure token to be associated with a plurality of network addresses that can be used by the advertising network device, since a parent network device (e.g., the root network device) can store and maintain a state of network addresses (e.g., from multiple DAO messages) utilized by the advertising network device and associated with the same secure token, where the advertising network device can prove (if requested) that it owns each address associated with the secure token.
Hence, the above-described example provides a scalable and effective secured protection of the target address using a secure token in a DAG message, where the secure token is associated with the target IP address, and based on selective issuance of a cryptographic challenge to the DAO message to prove that the advertising network device owns the private cryptographic key associated with generating the secure token.
In another embodiment, a RPL root network device can execute protected DODAG information object (DIO) messages based on generating cryptographic signatures of DIO parameters, according to an example embodiment. The RPL root network device generates a unique cryptographic signature for each DIO message that is transmitted in the RPL network, ensuring that no network device gaining link layer access to the RPL network can attack the RPL network by advertising an unauthorized rank.
Each of the network devices (e.g., “N1 through “N14”) 12 can be attached to at least one of another network device 12 or a root network device “ROOT” 12 via wireless data links 16 that form a link layer mesh topology. Although only the network devices “ROOT”, “N1”, “N2”, and “N3” are labeled with the reference numeral “12” in the Figures to avoid cluttering in the Figures, it should be apparent that all the network devices “N1” through “N14” are allocated the reference numeral “12” for purposes of the description herein. Further, it should be apparent that all the network devices “N1” through “N14” 12 can be configured for establishing wireless data links 16 (illustrated as curved lines radiating from each device 12), even though only the wireless data links for the network device “N1” 12 and the root network device “ROOT” 12 are labeled with the reference numeral “16” to avoid cluttering in the Figures. Any one of the network devices 12 also can be attached to one or more root network devices (not shown), for example where a plurality of root network devices can be connected via a wired data link 18 to form a “backbone” network 20 comprising one or more backbone routers 22 for the data network 10.
Each attachment in the DAG topology 14 is illustrated by an one-way arrow “→” where the corresponding child network device is positioned at the tail end of the arrow, and the corresponding parent network device is positioned at the arrowhead end of the arrow, such that the root network device “ROOT” 12 is the parent for the directly-attached child network devices “N1” and “N2”, the network device “N1” is the parent for the directly-attached child network devices “N4” and “N5”, etc.
As described previously, the DAG topology 14 can be established by the network devices 12 overlying a link layer mesh based on the network devices 12 exchanges routing protocol messages according to a prescribed routing protocol, for example RFC 6550, entitled “RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks”. A child network device (e.g., “N13”) 12 can attach to a potential parent device (e.g., “N12”) 12 in response to detecting a DIO message advertised by the potential parent device (e.g., “N12”) and specifying updated network topology metrics relative to a DIO message originated by the root network device “ROOT” 12. A Destination Advertisement Object (DAO) message can be created by an advertising RPL node (e.g., “N13”) 12 in response to attaching as a child to a parent network device (e.g., “N12”): the DAO message generated by the advertising RPL network device can be propagated via its parent network device (e.g., “N12”) toward the DAG root network device “ROOT” 12; as described in RFC 6550, the DAO message can specify a “target” IP address or prefix (e.g., an IPv6 address or prefix utilized by the child RPL node “N13”), enabling the root network device “ROOT” 12 to establish a downward path for reaching the advertising network device.
A fundamental problem is that existing proposals for securing a RPL network fail to provide a scalable solution where constrained network devices 12 operating as RPL parents can execute a routing protocol within the DAG topology 14 that can protect against attacks by an unauthorized or attacking network device (e.g., “N14”) that has improperly acquired a link-layer cryptographic key or a network-wide cryptographic key. In particular, RFC 6550 specifies at Section 6.1 that any secure RPL control message (e.g., a secure DIO, a secure DAO, etc.) (
Hence, the deployment of a secure RPL control message as proposed in RFC 6550 is not scalable and not practical for deployment in a LLN because it requires a RPL device attempting to process a secure RPL control message (e.g., a secure DAO message, secure DIO message, etc.) to decrypt each and every secure RPL control message: such processing requirements for secure RPL control messages can greatly overwhelm the processing capacity of network devices 12, especially in the case of the root network device “ROOT” 12 or parent network devices near the network device 12 (e.g., “N1”, “N2”, “N5”) that are near the root network device “ROOT” 12 in the DAG topology 14 and that may need to process a large number of RPL control messages.
Further, the deployment of a secure RPL control message as proposed in RFC 6550 assumes that a node wishing to join a secured network has been pre-configured with a shared key for communicating with neighbors and the RPL root (see, e.g., Sec. 9.2); hence, the secured RPL network as proposed in RFC 6550 can be compromised if an unauthorized/attacking network device “N14” 12 is able to acquire the shared key.
Hence, the proposed secure RPL network control message as proposed in RFC 6550 is not scalable for providing a secured protection of advertisement messages for a routing protocol used to establish a network layer routing topology (e.g., the DAG topology 14) in a low power and lossy network, where “zero trust” is desired to prevent an unauthorized/attacking network device “N14” 12 from improperly gaining access to the DAG topology 14.
Neighbor discovery protocols are separate and distinct from routing protocols, in that neighbor discovery protocols enable a host network device to claim a valid network address for communication with a neighboring network device in a data network; however, neighbor discovery protocols have no involvement in the establishment of a network layer routing topology beyond the link layer connection between the neighboring network devices, as the network discovery protocols are confined to registration of an IP address between a host network device (e.g., a leaf network device) and its neighboring network device (e.g., a router attached within a network layer topology in a data network according to a prescribed routing protocol). For example, RFC 6775, entitled “Neighbor Discovery Optimization for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs),” describes addressing mechanisms (e.g., neighbor discovery, duplicate address detection, address registration) for low-power wireless personal area networks, for example between a 6LoWPAN device at an edge of a 6LoWPAN network and a new network device attempting to join the 6LoWPAN network; the Internet Draft by Thubert et al., “Address Protected Neighbor Discovery for Low-power and Lossy Networks” (hereinafter “AP-ND Draft”) extended 6LoWPAN Neighbor Discovery (ND) as described in RFC 6775 by enabling a 6LowPAN Node (6LN) to protect its address by generating a crypto identifier, and permitting the neighboring 6LoWPAN Router (6LR) at the edge of a 6LoWPAN network and providing a link layer connection with the 6LN to issue a challenge to have the 6LN verify it is the owner of the crypto identifier associated with the address; the Internet Draft by Thubert, “Routing for RPL Leaves” enables a RPL-unaware leaf device (e.g., 6LN) to request its neighboring RPL-enabled router to register the AP-ND protected address of the of the RPL-unware leaf device on behalf of the RPL-unaware leaf device, eliminating the necessity that the leaf device be aware of the RPL protocol; and RFC 8505, entitled “Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery”, supports the registration of the RPL-unaware leaf device using registration verification between the RPL-unaware leaf device and the RPL-enabled router providing the link layer connection to the RPL-unaware leaf device.
Hence, existing routing protocols such as RFC 6550 are directed to creating a network topology for constrained devices, whereas the above-described neighbor discovery protocols are confined to registering address of leaf network device that are joining an existing network topology.
As described previously, RPL routers in a RPL-based DAG topology were assumed (e.g., according to RFC 6550) to have a shared level of trust, and therefore cannot provide the desired “zero trust” level of security to counter the risk that an unauthorized/attacking network device “N14” 12 obtaining a shared network-cryptographic key could risk exposing the data network (e.g., a CG-Mesh grid). Further, the existing neighbor discovery protocols in combination with routing protocols (e.g., RFC 6550), as illustrated in RFC 8505, do not provide a sufficient balance between security and flexibility. In particular, the above proposals fail to address a problem in preventing a first case where two separate leaf network devices (e.g., “6LN1” and “6LN2”) each securely connect to different RPL routers (e.g., “6LN1” connected to “N6” and “6LN2” connected to “N12”) at separate and distinct locally-administered domains (e.g., “N6” at subscriber premises “Family X” and “N12” at separate and distinct subscriber premises “Family Y”), and the two separate leaf network devices attempt to securely claim the same IP address. The above proposals also fail to address permitting a second case where a single leaf network device “6LN1” having first securely registered its IP address via the RPL router “N12” at premises “Family Y” can later securely update its registration via the RPL router “N6” after the leaf network device “6LN” having moved to the subscriber premises “Family X”.
According to example embodiments, the routing protocol described herein enables protection of a target IP address in a DAO message without encrypting the target IP address as described in RFC 6550, based on relying on the DAO specifying a secure token associated with the target IP address claimed by the advertising network device. Any RPL parent network device in the DAG topology 14 (e.g., in storing mode) can selectively issue a cryptographic challenge to the DAO message, for example in response to determining the target IP address claimed by the advertising network device is already in use, requiring the advertising network device having generated the secure token to prove that it owns the private key associated with generation of the secure token.
Hence, the example embodiments can guarantee protection of the target IP address associated with the secure token, even if the unauthorized/attacking network device “N14” 12 is able to detect the DAO message and the target IP address and associated secure token in the DAO message, since any RPL parent network device issuing the cryptographic challenge (including, for example, a nonce value chosen by the RPL parent network device) can require that the cryptographic challenge (e.g., the nonce value) be signed using the private key, enabling the RPL parent network device to determine whether any cryptographic key is validated (e.g., using a public key associated with the private key used to generate the secure token).
The example embodiments also provide scalable protection, since the advertising network device (and not the RPL parent network device) is required to respond to the cryptographic challenge. Further, a RPL parent device can discard a public key once the response to the cryptographic challenge and/or the secure token has been validated by the RPL parent device. Further, the same secure token can be used for multiple IP addresses used by the same advertising network device, enabling a storing RPL parent network device (or the root network device “ROOT” 12) to store in its route table entries the secure token and the one or more IP addresses validated as associated with the secure token.
Each apparatus 12, 22 can include a device interface circuit 24, a processor circuit 26, and a memory circuit 28. The device interface circuit 24 can include one or more distinct physical layer transceivers for communication with any one of the other devices 12, 22; the device interface circuit 24 also can include an IEEE based Ethernet transceiver for communications with the devices of
Any of the disclosed circuits of the devices 12, 22 (including the device interface circuit 24, the processor circuit 26, the memory circuit 28, and their associated components) can be implemented in multiple forms. Example implementations of the disclosed circuits include hardware logic that is implemented in a logic array such as a programmable logic array (PLA), a field programmable gate array (FPGA), or by mask programming of integrated circuits such as an application-specific integrated circuit (ASIC). Any of these circuits also can be implemented using a software-based executable resource that is executed by a corresponding internal processor circuit such as a microprocessor circuit (not shown) and implemented using one or more integrated circuits, where execution of executable code stored in an internal memory circuit (e.g., within the memory circuit 28) causes the integrated circuit(s) implementing the processor circuit to store application state variables in processor memory, creating an executable application resource (e.g., an application instance) that performs the operations of the circuit as described herein. Hence, use of the term “circuit” in this specification refers to both a hardware-based circuit implemented using one or more integrated circuits and that includes logic for performing the described operations, or a software-based circuit that includes a processor circuit (implemented using one or more integrated circuits), the processor circuit including a reserved portion of processor memory for storage of application state data and application variables that are modified by execution of the executable code by a processor circuit. The memory circuit 28 can be implemented, for example, using a non-volatile memory such as a programmable read only memory (PROM) or an EPROM, and/or a volatile memory such as a DRAM, etc.
Further, any reference to “outputting a message” or “outputting a packet” (or the like) can be implemented based on creating the message/packet in the form of a data structure and storing that data structure in a non-transitory tangible memory medium in the disclosed apparatus (e.g., in a transmit buffer). Any reference to “outputting a message” or “outputting a packet” (or the like) also can include electrically transmitting (e.g., via wired electric current or wireless electric field, as appropriate) the message/packet stored in the non-transitory tangible memory medium to another network node via a communications medium (e.g., a wired or wireless link, as appropriate) (optical transmission also can be used, as appropriate). Similarly, any reference to “receiving a message” or “receiving a packet” (or the like) can be implemented based on the disclosed apparatus detecting the electrical (or optical) transmission of the message/packet on the communications medium, and storing the detected transmission as a data structure in a non-transitory tangible memory medium in the disclosed apparatus (e.g., in a receive buffer). Also note that the memory circuit 28 can be implemented dynamically by the processor circuit 26, for example based on memory address assignment and partitioning executed by the processor circuit 26.
The operations described with respect to any of the Figures can be implemented as executable code stored on a computer or machine readable non-transitory tangible storage medium (i.e., one or more physical storage media such as a floppy disk, hard disk, ROM, EEPROM, nonvolatile RAM, CD-ROM, etc.) that are completed based on execution of the code by a processor circuit implemented using one or more integrated circuits; the operations described herein also can be implemented as executable logic that is encoded in one or more non-transitory tangible media for execution (e.g., programmable logic arrays or devices, field programmable gate arrays, programmable array logic, application specific integrated circuits, etc.). Hence, one or more non-transitory tangible media can be encoded with logic for execution by a machine, and when executed by the machine operable for the operations described herein.
In addition, the operations described with respect to any of the Figures can be performed in any suitable order, or at least some of the operations can be performed in parallel. Execution of the operations as described herein is by way of illustration only; as such, the operations do not necessarily need to be executed by the machine-based hardware components as described herein; to the contrary, other machine-based hardware components can be used to execute the disclosed operations in any appropriate order, or execute at least some of the operations in parallel.
Referring to
As illustrated in
Referring to operation 30a of
If the advertising network device “N13” 12 is implemented as a RPL-enabled device, the processor circuit 26 of the advertising network device “N13” 12 can generate in operation 30b a protected DAO message “DAO(RPL-ROVR-RO)” 50, illustrated in
The device interface circuit 24 of the RPL parent network device “N12” 12 that provides a connection to the leaf network device, i.e., the advertising network device “N13” 12, in operation 66 can receive a secure registration message either in the form of a “NS(EARO)” message from a non-RPL device (e.g., a “6LN”) device, or in the form of the above-described protected DAO message “DAO(RPL-ROVR-RO)” 50. Depending on configuration of the RPL parent network device “N12” 12, the processor circuit 26 of the RPL parent network device “N12” 12 can decide in operation 68 whether it needs to request validation of the received secure registration message: in one embodiment, the RPL parent network device “N12” 12 can decide that no validation or cryptographic challenge is needed if the IP address claimed by the advertising network device “N13” 12 in the “NS(EARO)” message or the protected DAO message “DAO(RPL-ROVR-RO)” 50 is a new address that is not previously registered.
Assuming in operation 68 that the processor circuit 26 of the parent network device “N12” 12 determines no registration is needed (e.g., the IP address claimed in the secure registration message has not yet been registered), the processor circuit 26 of the parent network device “N12” 12 in operation 70 can process the received secure registration message, as appropriate. In one example, the processor circuit 26 of the parent network device “N12” 12 in operation 70a can respond to a received “NS(EARO)” message from a non-RPL device by storing the IPv6 address (or prefix) and associated ROVR value in a neighbor cache entry (NCE); the processor circuit 26 of the parent network device “N12” 12 in operation 70a also can respond to the “NS(EARO)” message by sending a secured neighbor advertisement message “NA(EARO)” to the non-RPL leaf network device.
In another example, the processor circuit 26 of the parent network device “N12” 12 in operation 70b in storing mode can respond to a received protected DAO message “DAO(RPL-ROVR-RO)” 50 by creating in its memory circuit 28 a child entry that specifies the IPv6 address 60 specified in the RPL Target Option 58, the “ROVR” secure token 32, and the corresponding reachability information (e.g., link layer identifier, attachment address, etc.).
The processor circuit 26 of the parent network device “N12” 12 in operation 70c can generate the protected DAO message “DAO(RPL-ROVR-RO)” 50 on behalf of a non-RPL leaf node, if necessary, based on extracting the “ROVR” secure token 32, the TID, and the IP address from the “NS(EARO)” message, inserting the extracted IP address into the target IP address field 60 of the RPL Target Option 58, inserting the extracted TID into the transaction identifier (TID) field 64 of the ROVR registration option 62, and inserting the extracted “ROVR” secure token 32 into the ROVR registration option 62. The device interface circuit 24 of the parent network device “N12” 12 in operation 70c can output the protected DAO message “DAO(RPL-ROVR-RO)” 50 (generated by the parent network device “N12” 12 on behalf of a non-RPL leaf device or forwarded based on reception thereof from a RPL-enabled advertising network device “N13” 12) to its corresponding parent network device “N9” 12. As illustrated in
The next RPL parent device (e.g., “N9”) 12 can respond to receiving in operation 72 the protected DAO message “DAO(RPL-ROVR-RO)” 50: since the next RPL parent device (e.g., “N9”) is not the root network device “ROOT” 12 (operation 76), the next RPL parent device can successively repeat operations 68, 70b (optional) and 70c, until the protected DAO message “DAO(RPL-ROVR-RO)” 50 reaches the root network device “ROOT” 12 via the successive parent RPL network devices “N5” and “N1”.
In response to the device interface circuit 24 of the root network device “ROOT” 12 receiving in operation 72 and 76 the protected DAO message “DAO(RPL-ROVR-RO)” 50, the processor circuit 26 of the root network device “ROOT” 12 in operation 78 determines whether validation of the protected DAO message “DAO(RPL-ROVR-RO)” 50 is needed: as described previously, the processor circuit 26 of the root network device “ROOT” 12 can be configured for deciding in operation 78 that validation of the protected DAO message “DAO(RPL-ROVR-RO)” 50 is required only if the IPv6 address 60 specified in the RPL Target Option 58 is already registered in a child entry in the memory circuit 28 of the root network device “ROOT” 12 (alternatively, the processor circuit 26 can decide that validation is required for each and every received protected DAO message “DAO(RPL-ROVR-RO)” 50 from any child network device). Assuming no validation is needed, the processor circuit 26 of the root network device “ROOT” 12 in operation 80 can register the IPv6 address 60 specified in the Target field of the protected DAO message “DAO(RPL-ROVR-RO)” 50, the “ROVR” secure token 32, and the corresponding reachability information (e.g., link-local address, child IP attachment address, etc.) in a child entry in the memory circuit 28. The processor circuit 26 of the root network device “ROOT” 12 in operation 80 also can output a corresponding secured DAO acknowledgement message (DAO-ACK) 74 to its child network device “N1” having forwarded the protected DAO message “DAO(RPL-ROVR-RO)” 50 to the root network device “ROOT” 12.
Hence, the protected DAO message “DAO(RPL-ROVR-RO)” 50 generated and output by a RPL-enabled advertising network device “N13” 12 (or a RPL-enabled parent “N12” on behalf of a non-RPL enabled leaf node) is sent with the secure token 32 that is cryptographically generated by the advertising network device and associated with the target IP address 60 specified in the protected DAO message “DAO(RPL-ROVR-RO)” 50. If desired, the RPL-enabled advertising network device “N13” 12 also can add to the protected DAO message “DAO(RPL-ROVR-RO)” 50 a RPL-based Crypto-ID Parameters Option (RPL-CIPO) 82, illustrated in
As noted previously and as illustrated in
According to the example embodiments, any parent network device in the DAG topology 14 (or at least the root network device “ROOT” 12), operating in storing mode or nonstoring mode, can be configured for requiring validation of any DAO message (e.g., in operations 68 or 78 of
The example embodiments can operate in storing mode, nonstoring mode, and/or a hybrid of storing mode and non-storing mode. Referring to
The processor circuit 26 of the common parent (e.g., “N5” 12) (in storing mode) and/or the root network device “ROOT” 12 (e.g., if the DAG topology 14 is operating in nonstoring mode) that initiates the DAO verification request (DAO-REQ) message 88 in operation 90 also can selectively set in its memory circuit 28 a corresponding child entry indicating the pending cryptographic challenge, for example based on storing in the child entry the target IPv6 address 60 and the “ROVR” secure token 32 specified in the received spoofed DAO message 84, the corresponding child reachability information, and a “VALIDATION REQUESTED” status to indicate that the advertising unauthorized/attacking network device “N14” 12 claiming ownership of the target IPv6 address 60 and the “ROVR” secure token 32 must validate its RPL-based Crypto-ID Parameters Option (RPL-CIPO) 82. The common parent (and/or root network device “ROOT” 12) initiating the DAO verification request (DAO-REQ) message 88 also can store in the child entry the corresponding nonce value that is specified in the DAO verification request (DAO-REQ) message 88: for example, the root network device “ROOT” 12 initiating the DAO verification request (DAO-REQ) message 88 can store in its child entry the corresponding root-generated nonce value “NONCE_ROOT”; if the common parent network device “N5” 12 (in storing mode) is the first network device to initiate the DAO verification request (DAO-REQ) message 88, the common parent network device “N5” 12 can store in its child entry the corresponding generated value “NONCE_N5” (each nonce value generated by a parent network device is used only once for validation to avoid a replay attack).
As illustrated in
If the unauthorized/attacking network device “N14” 12 is not RPL-enabled (illustrated in
As described previously, the unauthorized/attacking network device “N14” 12 is unable to provide a valid response to the DAO verification request (DAO-REQ) message 88 because the unauthorized/attacking network device “N14” 12 does not own the private key “Kprv” 34 that was used to generate the “ROVR” secure token 32. In contrast, if the advertising network device “N13” 12 has actually moved from its initial parent network device “N12” to a new parent network device “N6” 12, the “moved” advertising network device “N13” 12 can generate a successful response to the DAO verification request (DAO-REQ) message 88 because the moved advertising network device “N13” 12 owns the private key “Kprv” 34 used to generate the “ROVR” secure token 32.
Hence, the moved advertising network device “N13” 12 (and/or the unauthorized/attacking network device “N14” 12) in operation 96 can generate a response to the cryptographic challenge 88 or 94 by signing the nonce(s) specified in the DAO verification request (DAO-REQ) message 88 or 94, and sending a challenge response back to the RPL parent “N6”. In one embodiment, the moved advertising network device “N13” 12 (and/or the unauthorized/attacking network device “N14” 12) can generate a response based on adding its own nonce (e.g., “NONCE_LEAF”) to the supplied nonce(s) resulting in a string of nonces, and then signing the string of nonces using its private key “Kprv” 34 to generate a signed string of nonces.
If the advertising network device “N13” 12 (and/or the unauthorized/attacking network device “N14” 12) is non-RPL enabled (as in
If the advertising network device “N13” 12 (and/or the unauthorized/attacking network device “N14” 12) is a RPL enabled device (as in
In response to the parent network device “N6” 12 receiving in operation 102 the challenge response (98 of
The processor circuit 26 of the parent network device “N6” 12 in operation 102 can attempt validation based on determining whether the public key “Kpub” 36 verifies the cryptographic signature relative to the signed string of nonces: if the public key “Kpub” 36 obtained by the parent network device “N6” 12 corresponds to the private key “Kprv” 34 used to generate the “ROVR” secure token 32 (as would be the case for the advertising network device “N13” 12), then the parent network device “N6” 12 should be able to use the public key “Kpub” 36 to verify the cryptographic signature is a valid signature of the signed string of nonces specified in the challenge response because the corresponding private key “Kprv” 34 was used to cryptographically sign the signed string of nonces; in contrast, if the public key “Kpub” 36 obtained by the parent network device “N6” does not correspond to the private key “Kprv” 34 used to generate the “ROVR” secure token 32 (as would be the case for the unauthorized/attacking network device “N14” 12), then the parent network device “N6” 12 would apply the public key “Kpub” 36 and determine the cryptographic signature is not a valid signature of the signed string of nonces because a different private key “Kprv” 34 (i.e., that of the unauthorized/attacking network device “N14” 12) was used to cryptographically sign the string of nonces, indicating the “ROVR” secure token 32 was generated by a different network device 12 having a different private key “Kprv” 34. As apparent from the foregoing, the processor circuit 26 of the parent network device “N6” also can provide additional security by providing its own nonce (“NONCE_N6”) in the challenge request message 88, and verify its own nonce within the signed string of nonces.
Hence, the processor circuit 26 of the advertising network device (e.g., the moved advertising network device “N13”) 12 can generate a signature based on applying the private key “Kprv” 34 to signing the string of nonces (e.g., “NONCE_ROOT-NONCE_N1-NONCE_N5-NONCE_N6-NONCE_N13”), and supply in the challenge response 100 the signed string of nonces comprising the signature and the (unencrypted) string of nonces (e.g., “NONCE_ROOT-NONCE_N5-NONCE_N5-NONCE_N6-NONCE_N13”). Hence, the parent network device “N6” 12 can determine whether the public key “Kpub” 36 validates the signature relative to the signed string of nonces (e.g., “NONCE_ROOT-NONCE_N1-NONCE_N5-NONCE_N6-NONCE_N13”), based on verifying its corresponding nonce “NONCE_N6” is in the signature. The string of nonces remain in the challenge response 100 to ensure each subsequent parent toward and including the root network device “ROOT” 12 can verify the signature based on the signed string of nonces (e.g., “NONCE_ROOT-NONCE_N1-NONCE_N5-NONCE_N6-NONCE_N13”).
Hence, if in operation 102a the parent network device “N6” 12 determines that the challenge response fails (as would be the case if the challenge response was attempted by the unauthorized/attacking network device “N14” 12), the processor circuit 26 of the parent network device “N6” 12 in operation 102a can update the child entry status to “VALIDATION FAILED” and delete the entry from active use.
In contrast, if in operation 102b the parent network device “N6” 12 determines that the challenge response is successful, i.e., that the public key “Kpub” 36 verifies the signature of the signed string of nonces, then the parent network device “N6” 12 can verify the challenge response, and accordingly clear the status in its child entry by removing the “VALIDATION REQUESTED” status and clearing the stored timer. The parent network device “N6” 12 also can send in operation 102b a secured DAO acknowledgement message 74 to the validated RPL-aware advertising network device “N13” 12, or a “NA(EARO)” message to the validated non-RPL aware advertising network device “N13” 12. If the challenge response was a NS(EARO, CIPO, NDPSO, Nonce(s)) challenge response message 98 from a non-RPL aware leaf device, the parent network device in operation 102c also can convert the received NS(EARO, CIPO, NDPSO, Nonce(s)) challenge response message 98 into a protected DAO with RPL Signature Option (RPLSO) message 100 for forwarding to the next parent network device (e.g., the common parent “N5”).
Regardless of success or failure, the processor circuit 26 of the parent network device “N6” 12 in operation 104 can forward the protected DAO with RPL Signature Option (RPLSO) message 100 (including the signed string of nonces) to its next-hop parent to enable each hop toward the path to the originator of the DAO verification request (DAO-REQ) message 88 to verify whether the challenge response was successful or failed.
Referring to
Assuming the root network device “ROOT” 12 originated the DAO verification request (DAO-REQ) message 88, the RPL parents (e.g., “N6”-“N5”-“N1” and/or “N6”-“N2”) can verify the signature and that their respective nonce(s) are in the signed string of nonces (if added into the challenge request message 88) and forward the protected DAO with RPL Signature Option (RPLSO) message 100 to the root network device “ROOT” 12, enabling the processor circuit 26 of the root network device “ROOT” 12 in operation 108 to effectively execute operations 102a or 102b, as appropriate, depending on whether the challenge response succeeds or fails based on the signed string of nonces in the received protected DAO with RPL Signature Option (RPLSO) message 100. If the processor circuit 26 of the root network device “ROOT” 12 can verify the received protected DAO with RPL Signature Option (RPLSO) message 100 is a valid response (e.g., by the advertising network device “N13” 12) to the cryptographic challenge specified in the DAO verification request (DAO-REQ) message 88, the root network device “ROOT” 12 can clear the status in its child entry by removing the “VALIDATION REQUESTED” status and clearing the stored timer, and storing at least the IPv6 address 60, the associated “ROVR” secure token 32, and reachability information for the advertising network device “N13” 12; the public key “Kpub” 36 of the advertising network device “N13” 12 also can be stored in the child entry, if desired. In contrast, if the processor circuit 26 of the root network device “ROOT” 12 determines the received protected DAO with RPL Signature Option (RPLSO) message 100 is not a valid response (e.g., by the unauthorized/attacking network device “N14” 12) to the cryptographic challenge specified in the DAO verification request (DAO-REQ) message 88, the processor circuit 26 of the root network device “ROOT” 12 in operation 108 can delete the child entry having the “ROVR” secure token 32 and the associated “VALIDATION REQUESTED” status. As apparent from the foregoing, the child entry also can be deleted by the root network device “ROOT” 12 and/or any parent RPL device operating in storing mode if the challenge response is not received before expiration of the timer value in the child entry (i.e., by the “timeout” value).
According to example embodiments, scalable protection of DAO message parameters such as a target IP address can be provided based on selectively issuing a cryptographic challenge that requires an advertising network device claiming the target IP address to provide a cryptographic response that proves the advertising network device owns a private key required to generate a secure token associated with the target IP address.
The RPL root network device 12 of
In particular, each DIO message generated and output by the root network device “ROOT” 12 can include a certificate that is cryptographically signed by the root network device
“ROOT” 12 using its corresponding private key “Kprv” 34: the processor circuit 26 of the root network device “ROOT” 12 in operation 120 can generate a root certificate based on cryptographically signing a RPL Instance identifier 54 (set by the root network device “ROOT” 12) with the corresponding private key “Kprv” 34 of the root network device “ROOT” 12; the root network device “ROOT” 12 can add to the root-initiated DIO message the root certificate and root public key “Kpub” 36, as well as any other required parameters as described in RFC 6550. The root network device “ROOT” 12 can output in operation 120 the root-initiated protected DIO message (comprising the root certificate and the corresponding public key “Kpub” 36 of the root network device “ROOT” 12) for creation of the DAG topology 14.
In response to first-hop network devices (e.g., “N1” and “N2” of
In response to validating the root-initiated protected DIO message, a child network device (e.g., “N1” and “N2” of
The root network device “ROOT” 12 can respond to the received DAO message by selecting in operation 126 an allocated rank for the child network device (i.e., the DAO originator), for example based on whether the proposed rank is acceptable, or whether the root network device “ROOT” 12 determines an alternative rank should be advertised by the DAO originator. For example, the root network device “ROOT” 12 in operation 126 can allocate the proposed rank identification if it has a value greater than a corresponding parent rank identification; the root network device “ROOT” 12 also can reject the rank identification if the corresponding value is less than the corresponding parent rank identification, and allocate a different rank for the DAO originator.
The root network device “ROOT” 12 in operation 128 can generate a cryptographic signature of the allocated rank identification having been allocated by the root network device: the root network device “ROOT” 12 can use its private key “Kprv” 34 to create the cryptographic signature, based on signing a concatenated data structure comprising the allocated rank identification for DAO originator, the RPL Instance identifier 54, and the IPv6 address 60 specified in the RPL Target Option 58.
The root network device “ROOT” 12 in operation 130 can output (via unicast transmission to the DAO originator) a DAO acknowledgement message that specifies the allocated rank identification and the cryptographic signature (and optionally the public key “Kpub” 36 of the root network device “ROOT” 12). Hence, the DAO originator 12 can generate and output in operation 132 a new protected DIO message that includes the allocated rank identification that was allocated by the root network device “ROOT” 12, the cryptographic signature signed by the root network device “ROOT” 12, and the public key “Kpub” 36 of the root network device “ROOT” 12.
Hence, additional child network devices 12 in operation 134 can validate the new protected DIO message output by the DAO originator (e.g., “N1”) based on the cryptographic signature and the root public key. Each child network device that receives a protected DIO message can validate the rank of the advertising parent associated with its address, using the public key in the certificate to validate the signature in the new option.
Each child network device joining the DAG topology 14 can recursively execute the operations of
Also note that the root network device “ROOT” 12 may allocate a different rank for different reasons, for example based on determining a depleted battery level (specified in an optional DAO field) relative to neighboring RPL network devices, in which case the root network device “ROOT” 12 may allocate an artificially high rank to discourage potential children from attaching to the DAO originator having the depleted battery level.
The root network device “ROOT” 12 also can form a new iteration of the DODAG by changing (incrementing) the RPL Instance identifier 54, requiring each network device 12 in the DAG topology 14 to revalidate its certificate with the root network device “ROOT” 12.
While the example embodiments in the present disclosure have been described in connection with what is presently considered to be the best mode for carrying out the subject matter specified in the appended claims, it is to be understood that the example embodiments are only illustrative, and are not to restrict the subject matter specified in the appended claims.
