Encrypted CCNx

Abstract

One embodiment provides a system that facilitates selective encryption of bit groups of a message. During operation, the system determines, by a content requesting device or content producing device, a message that includes a plurality of bit groups, each corresponding to a type, a length, and a set of values, wherein one or more bit groups are marked for encryption, and wherein the message indicates a name that is a hierarchically structured variable-length identifier comprising contiguous name components ordered from a most general level to a most specific level. The system computes a plurality of cipher blocks for the message based on an authenticated encryption protocol. The system encrypts the one or more bit groups marked for encryption based on one or more symmetric keys, wherein the marked bit groups include one or more name components. Subsequently, the system indicates the encrypted bit groups as encrypted.

Description

RELATED APPLICATION

The subject matter of this application is related to the subject matter in the following applications:

• • U.S. patent application Ser. No. 13/847,814, entitled “ORDERED-ELEMENT NAMING FOR NAME-BASED PACKET FORWARDING,” by inventor Ignacio Solis, filed 20 Mar. 2013 (hereinafter “U.S. patent application Ser. No. 13/847,814”);
  • U.S. patent application Ser. No. 12/338,175, entitled “CONTROLLING THE SPREAD OF INTERESTS AND CONTENT IN A CONTENT CENTRIC NETWORK,” by inventors Van L. Jacobson and Diana K. Smetters, filed 18 Dec. 2008 (hereinafter “U.S. patent application Ser. No. 12/338,175”);
  • U.S. Pat. No. 8,386,622, entitled “METHOD AND APPARATUS FOR FACILITATING COMMUNICATION IN A CONTENT CENTRIC NETWORK,” by inventors Van Jacobson, filed 11 Dec. 2008 (hereinafter “U.S. Pat. No. 8,386,622”);
  • U.S. Pat. No. 8,204,060, entitled “METHOD AND SYSTEM FOR FACILITATING FORWARDING A PACKET IN A CONTENT-CENTRIC NETWORK,” by inventor Van L. Jacobson and James D. Thornton, filed 17 Dec. 2009 (hereinafter “U.S. Pat. No. 8,204,060”); and
  • U.S. patent application Ser. No. 14/065,691, entitled “SYSTEM AND METHOD FOR HASH-BASED FORWARDING OF PACKETS WITH HIERARCHICALLY STRUCTURED VARIABLE-LENGTH IDENTIFIERS,” by inventors Marc E. Mosko and Michael F. Plass, filed 29 Oct. 2013 (hereinafter “U.S. patent application Ser. No. 14/065,691”);the disclosures of which are herein incorporated by reference in their entirety.

BACKGROUND

Field

This disclosure is generally related to distribution of digital content. More specifically, this disclosure is related to a system and method for selectively encrypting bit groups (such as name components) based on multiple symmetric keys in a content centric network message.

Related Art

The proliferation of the Internet and e-commerce continues to create a vast amount of digital content. Content centric network (CCN) architectures have been designed to facilitate accessing and processing such digital content. A CCN includes entities, or nodes, such as network clients, forwarders (e.g., routers), and content producers, which communicate with each other by sending interest packets for various content items and receiving content object packets in return. CCN interests and content objects are identified by their unique names, which are typically hierarchically structured variable length identifiers (HSVLI). An HSVLI can include contiguous name components ordered from a most general level to a most specific level.

Part of a CCN name can be used for routing purposes, and part of the name can contain sensitive data. For example, some name components may be used by an intermediate node to perform forwarding and caching, while other name components may contain private user information or application-specific data. Current CCN packet formats may include authentication as a primary objective, while previous CCN packet formats may include encryption functionality but are designed to encrypt only the payload while providing authentication for the entire packet. These packet formats do not allow for session-based and pair-wise encryption between two entities, nor do they provide a way to selectively encrypt portions of a CCN packet or message.

SUMMARY

One embodiment provides a system that facilitates selective encryption of bit groups of a message. During operation, the system determines, by a content requesting device or content producing device, a message that includes a plurality of bit groups, each corresponding to a type, a length, and a set of values, wherein one or more bit groups are marked for encryption, and wherein the message indicates a name that is a hierarchically structured variable-length identifier comprising contiguous name components ordered from a most general level to a most specific level. The system computes a plurality of cipher blocks for the message based on an authenticated encryption protocol. The system encrypts the one or more bit groups marked for encryption based on one or more symmetric keys, wherein the marked bit groups include one or more name components. Subsequently, the system indicates the encrypted bit groups as encrypted.

In some embodiments, the message is an interest packet or a content object packet.

In some embodiments, the system transmits the selectively encrypted message to a content producing device or a content requesting device.

In some embodiments, computing the cipher blocks is further based on beginning at byte zero of the message.

In some embodiments, computing the cipher blocks is further based on an Advanced Encryption Standard using a key with a length of 128 bits.

In some embodiments, encrypting the bit groups is further based on an exclusive disjunction operation.

In some embodiments, indicating the encrypted bit groups as encrypted comprises one or more of: setting a field associated with the bit group in the message; and setting a reserved bit associated with the bit group in the message.

In some embodiments, the system includes in a validation section for the message a nonce and a key identifier for each of the symmetric keys.

In some embodiments, the system further comprises one or more of the following: wherein a symmetric key is exchanged via a public key operation; wherein a symmetric key is encrypted based on a public key included in the message; wherein the validation section is based on a symmetric key cryptographic system with encryption; wherein a public key identifier of the content producing device is included in the message; and wherein a short symmetric key identifier is specified for use in subsequent messages between the content requesting device and the content producing device.

In some embodiments, the system further comprises one or more of the following: wherein the public key operation is based on a cryptographic system that is RSA-SHA256; and wherein the short symmetric key identifier is a random number that is not derived from the symmetric key.

In some embodiments, the system receives the selectively encrypted message. In response to verifying authentication information associated with the message, the system decrypts, for each bit group indicated as encrypted, the encrypted bit group based on a corresponding symmetric key, wherein a nonce and a key identifier for each of the symmetric keys are included in a validation section for the message. The system indicates the decrypted bit groups as decrypted.

In some embodiments, verifying the authentication information associated with the message further comprises: looking up in a storage a key identifier associated with the message; and verifying a signature or a message authentication code based on the key identifier.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates an exemplary network facilitating selective encryption of bit groups of a CCN message, in accordance with an embodiment of the present invention.

FIG. 2 presents a flow chart illustrating a method by a content requesting device or a content producing device for selectively encrypting a CCN message, in accordance with an embodiment of the present invention.

FIG. 3 presents a flow chart illustrating a method by a content requesting device or a content producing device for verifying and decrypting a selectively encrypted CCN message, in accordance with an embodiment of the present invention.

FIG. 4A illustrates an exemplary format for a selectively encrypted CCN message, in accordance with an embodiment of the present invention.

FIG. 4B illustrates an exemplary format for a selectively encrypted CCN message, in accordance with an embodiment of the present invention.

FIG. 4C illustrates an exemplary format for a selectively encrypted CCN message with nested encryption, in accordance with an embodiment of the present invention.

FIG. 4D illustrates an exemplary format for an encoding graph with a post-order traversal, corresponding to the exemplary format for the message in FIG. 4C, in accordance with an embodiment of the present invention.

FIG. 4E illustrates an exemplary format for an encoding graph with a reverse post-order traversal, corresponding to the exemplary format for the message in FIG. 4C, in accordance with an embodiment of the present invention.

FIG. 5 illustrates an exemplary format for a validation section of a selectively encrypted CCN message, in accordance with an embodiment of the present invention.

FIG. 6 illustrates an exemplary apparatus that facilitates selective encryption of bit groups of a CCN message, in accordance with an embodiment of the present invention.

FIG. 7 illustrates an exemplary computer system that facilitates selective encryption of bit groups of a CCN message, in accordance with an embodiment of the present invention.

In the figures, like reference numerals refer to the same figure elements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled in the art to make and use the embodiments, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present disclosure. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

Overview

Embodiments of the present invention provide a system which solves the problem of effectively combining authentication and encryption for a packet by facilitating two communicating entities to use multiple different and mutually known keys to encrypt selected portions of a CCN message. Assume that two entities, such as a consumer and a producer, share multiple secret keys based on a known key exchange protocol. The consumer may wish to transmit an interest packet where portions, or “bit groups,” of the packet may require encryption. For example, the name components of the interest name may contain both routable information and sensitive, application-specific information. The consumer may selectively encrypt various name components by placing a container around a name component, marking the name component as encrypted based on a specific key, and indicating the specific key in a validation section for the packet. Exemplary packet formats with encrypted containers are described below in relation to FIGS. 4A-C. The producer can receive the selectively encrypted interest, verify authentication information in the validation section based on the specific keys indicated, and subsequently decrypt each encrypted name component (or bit group) based on the indicated key. The producer can generate a responsive content object and assign the responsive content object with the same selectively encrypted name as the incoming interest. Based on the same methods used by the consumer to selectively encrypt the interest, the producer can also encrypt additional portions of the responsive content object based on other mutually known keys.

Specifically, the system uses an authenticated encryption with associated data (AEAD) scheme which simultaneously protects both the privacy and authenticity/integrity of encapsulated data. Given a TLV-formatted packet (e.g., a packet comprised of bit groups where each bit group corresponds to a type, a length, and a set of values), a consumer may use an AEAD scheme to encrypt selective bit groups (such as name components) for the packet. An example of an AEAD scheme that follows an “encrypt-then-authenticate” paradigm as used with a modified TLV-formatted CCN packet is described below in the section entitled “Exemplar Authenticated Encryption Protocol Over Encrypted Containers.”

The following terms describe elements of a CCN architecture:

• • Content Object or “content object”: A single piece of named data, which is bound to a unique name. Content Objects are “persistent,” which means that a Content Object can move around within a computing device, or across different computing devices, but does not change. If any component of the Content Object changes, the entity that made the change creates a new Content Object that includes the updated content, and binds the new Content Object to a new unique name.
  • Unique Names: A name in a CCN is typically location independent and uniquely identifies a Content Object. A data-forwarding device can use the name or name prefix to forward a packet toward a network node that generates or stores the Content Object, regardless of a network address or physical location for the Content Object. In some embodiments, the name may be a hierarchically structured variable-length identifier (HSVLI). The HSVLI can be divided into several hierarchical components, which can be structured in various ways. For example, the individual name components parc, home, ccn, and test.txt can be structured in a left-oriented prefix-major fashion to form the name “/parc/home/ccn/test.txt.” Thus, the name “/parc/home/ccn” can be a “parent” or “prefix” of “/parc/home/ccn/test.txt.” Additional components can be used to distinguish between different versions of the content item, such as a collaborative document.
  • In some embodiments, the name can include a non-hierarchical identifier, such as a hash value that is derived from the Content Object's data (e.g., a checksum value) and/or from elements of the Content Object's name. A description of a hash-based name is described in U.S. patent application Ser. No. 13/847,814, which is hereby incorporated by reference. A name can also be a flat label. Hereinafter, “name” is used to refer to any name for a piece of data in a name-data network, such as a hierarchical name or name prefix, a flat name, a fixed-length name, an arbitrary-length name, or a label (e.g., a Multiprotocol Label Switching (MPLS) label).
  • Interest or “interest”: A packet that indicates a request for a piece of data, and includes a name (or a name prefix) for the piece of data. A data consumer can disseminate a request or Interest across an information-centric network, which CCN routers can propagate toward a storage device (e.g., a cache server) or a data producer that can provide the requested data to satisfy the request or Interest.

The methods disclosed herein are not limited to CCN networks and are applicable to other architectures as well. A description of a CCN architecture is described in U.S. patent application Ser. No. 12/338,175, which is hereby incorporated by reference.

Exemplary Network and Communication

FIG. 1 illustrates an exemplary network facilitating selective encryption of bit groups of a CCN message, in accordance with an embodiment of the present invention. Network 100 can be a content centric network (CCN) and can include a client device 116, a content producing device 118, and a router or other forwarding device at nodes 102, 104, 106, 108, 110, 112, and 114. A CCN router can be a CCN forwarding device residing on top of an IP router. In other words, CCN can be implemented as an overlay on top of IP. Other CCN overlay architecture is also possible. A node can be a computer system, an end-point representing users, and/or a device that can generate interests or originate content.

A requesting entity or content consumer (such as device 116) can generate or determine an interest 130 with an original name of “/a/b/c/d/e.” Consumer 116 can selectively encrypt interest 130 via an encrypt 140 function, which results in an interest 132 with a selectively encrypted name of “/a/b/E_K2{c}/E_K3{/d/e}.” Interest 132 has two selectively encrypted name components (e.g., “containers” or “bit groups”): 1) name component “c” is encrypted using the symmetric key K2; and 2) name components “/d/e” are encrypted using the symmetric key K3. The keys K2 and K3 are mutually known to consumer 116 and producer 118. Possible key exchange protocols are described below in the section entitled “Possible Methods for Sharing Symmetric Keys.” For each symmetric key used to encrypt a name component, the encrypt 140 function can be further based on an authenticated encryption with associated data (AEAD) protocol. As described below, an AEAD scheme can generate an authenticator tag for a respective encrypted container, and consumer 116 can include the authenticator tag in a corresponding validation section for the message. Consumer 116 can transmit selectively encrypted interest 132 through the network. Interest 132 is received and forwarded by intermediate nodes 102 and 114, until it reaches content producing device or content producer 118.

Producer 118 verifies the authentication information (e.g., the authenticator tag included in the validation section for the message). Upon properly verifying the authentication information, producer 118 decrypts each encrypted name component for interest 132 via a decrypt 142 function, based on the information in the validation section. The validation section includes information to identify which symmetric key to use for each encrypted name component (or bit group), as described below in relation to FIG. 5. The decrypt 142 function results in interest 130 with the original name “/a/b/c/d/e.” Producer 118 then generates or produces a content object 131 that is responsive to interest 130. Producer 118 can selectively encrypt content object 131 (e.g., name components of content object 131) to match the name for interest 132 via an encrypt 144 function, which results in content object 133. Producer 118 can also encrypt other bit groups of content object 133 using the same encryption keys previously used by consumer 116 (e.g., K2 and K3). Producer 118 can further encrypt other bit groups of content object 133 using yet another symmetric key shared between the parties (e.g., K4, not shown). In some embodiments, producer 118 can also wrap content object 133 with an outer container, as described below in the section entitled “Wrapping Method.” Producer 118 can transmit content object 133 through the network. Content object 133 travels on a reverse path as interest 132, e.g., back through intermediate nodes 114 and 102, until it reaches consumer 116.

Upon receiving content object 133, consumer 116 performs similar steps to verify and decrypt selectively encrypted content object 133 as producer 118 performs to verify and decrypt selectively encrypted interest 132. For example, consumer 116 verifies the authentication information in content object 133, and upon verifying the authentication information, consumer 116 begins decrypting the encrypted bit groups or name components of content object 133 via a decrypt 146 function, based on the information in the validation section. The decrypt 146 function results in a content object 131 with the original name “/a/b/c/d/e.” Consumer 116 can subsequently perform a lookup and clear a corresponding entry in its pending interest table (PIT) for interest 132 and/or interest 130.

Selectively Encrypting a CCN Message

FIG. 2 presents a flow chart 200 illustrating a method by a content requesting device or a content producing device for selectively encrypting a CCN message, in accordance with an embodiment of the present invention. During operation, the system determines, by a content producing device or a content requesting device, a message that includes a plurality of bit groups, where each bit group corresponds to a type, a length, and a set of values, and where one or more bits are marked for encryption (operation 202). The message also indicates a name that is a hierarchically structured variable-length identifier comprising contiguous name components ordered from a most general level to a most specific level. The message can be an interest packet or a content object packet. The system then computes a plurality of cipher blocks for the message based on an authenticated encryption protocol (operation 204). The authenticated encryption protocol can be an “encrypt-then-authenticate” scheme that simultaneously encrypts and authenticates more data than it encrypts. One example of such an authenticated encryption with associated data (AEAD) scheme is Advanced Encryption Standard in Galois/Counter Mode (AES-GCM), as described below. The system encrypts the one or more bit groups marked for encryption based on one or more symmetric keys, where the marked bit groups include one or more name components (operation 206). The bit groups can also include the payload and any other bit groups or TLV-formatted groups that an encryptor may wish to encrypt. In addition, the encryptor can perform a nested encryption of bit groups, as described below in relation to FIG. 4C.

The system includes in a validation section for the message a nonce and a key identifier (KeyId) for each of the symmetric keys used to encrypt a bit group (operation 208). Possible symmetric key exchange protocols are discussed below in the section entitled “Possible Methods For Sharing Symmetric Keys.” Subsequently, the system transmits the selectively encrypted message to another entity (operation 210). For example, the CCN message can be an interest packet that is selectively encrypted and transmitted from a content requesting device to a content producing device. The content producing device can subsequently return to the content requesting device a responsive content object that has the same selectively encrypted name. The responsive content object can be further selectively encrypted.

Exemplar Authenticated Encryption Protocol Over Encrypted Containers

Block cipher modes of operation can simultaneously protect both the privacy and the authenticity or integrity of encapsulated data. Such authenticated encryption (AE) schemes can also authenticate more data than they encrypt, and are referred to as authenticated encryption with associated data (AEAD) schemes. One example of an AEAD scheme is the Advance Encryption Standard in Galois/Counter Mode (AES-GCM), used with block ciphers with a block size of 128 bits. AES-GCM uses the “encrypt-then-authenticate” paradigm. The scheme is based on a secret key K, a nonce (e.g., Initialization Vector or IV), and a counter per nonce. The selectively encrypted packet carries a KeyId and a nonce. As described in IETF RFC 4106, “The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)” (June 2005) (hereinafter “RFC 4106”), which disclosure is herein incorporated in its entirety, the KeyId identifies a (key, salt) pair which is created during association setup. The nonce is 1-8 bytes in size and is carried in the validation section for the packet, as described below in relation to FIG. 5. The nonce is left-padded with zeros to 8 bytes and appended to the salt to form the GCM-AES IV. Note that the nonce in the packet may also be a counter.

To encrypt the packet using the GCM-AES scheme, an encryptor uses the following inputs: the secret key K; distinct Initialization Vectors IV (typically 96 bits); plaintext P (up to 2³⁹-256 bits); and associated data A (up to 264 bits). Using these inputs, the encryptor creates the following outputs: the ciphertext C (with a length equal to P); and the authentication tag T (0-128 bits). Authentication tag T is constructed by feeding blocks of data into the GHASH function and encrypting the result. For example, the GHASH function can be defined by GHASH(H,A,C): H is the hash key, a string of 128 zero-bits encrypted using the block cipher; A is the associated data which is only authenticated but not encrypted; and C is the ciphertext. Thus, the function GHASH of GCM-AES is performed over all of C and A for each encrypted container.

The decryptor receives the outputs, C and T, along with A (which can include a plaintext header, tail, or other meta information), and can determine K and IV based on a previous key exchange protocol. The decryptor thus uses inputs K, IV, C, A, and T to determine the output, which is either the plaintext P or a “FAIL” result.

Each encrypted bit group of a CCN message is an independent key/nonce execution of the GCM-AES scheme. The encryptor can perform an exclusive disjunction (i.e., XOR) operation on the “value” of the encrypted container. Thus, the ciphertext C contains a mixture of some XOR'd bytes and some plaintext bytes. The associated data A comprises all prior validation sections as well as the current validation section. An exemplary format of a validation section is described below in relation to FIG. 5.

The byte counter can run from byte 0 of the message to the end of the message to clarify that the ciphertext C is the entire CCNx message. An encryptor does not need to compute AES blocks E(K,Y_i) for message sections that fall outside of the XOR range. In some embodiments, the encryptor can use only the “value” bytes of specific encrypted containers and perform encryption over the compacted range. While this may provide more compatibility with existing GCM-AES implementations, the encryptor may need to make all the uncovered bytes part of the associated data A, which may require additional overhead to properly encode the lengths.

Possible Methods for Sharing Symmetric Keys

Communicating entities need to exchange symmetric keys. In one method, the entities exchange symmetric keys via a public key operation. The public key operation can be based on a cryptographic system that is, e.g., RSA-SHA256. The wrapped key can be included in the message using the key, i.e., the message embeds its own decryption key under a public key operation. In another method, two communicating entities exchange a separate message with the wrapped key, then refer to it with an agreed to identifier. In another method, two communicating entities use an on-line key exchange mechanism, such as a version of Diffie Hillman key exchange.

Communicating entities need to identify the symmetric key(s) used to encrypt portions of a message. In embodiments of the present invention, the encryptor can establish one or more encryption contexts identified by a given TLV Type value. At the end of the message, in the ValidationAlgorithm section, the encryptor can associate the encryption context with a KeyId for the symmetric key. The KeyId of a symmetric key may be a small integer value agreed upon by the parties. The KeyId values may be relative to the name prefix used in the message exchanges, which allows the same KeyId value to be used in multiple communications with different name prefixes without ambiguity.

Verifying and Decrypting a Selectively Encrypted CCN Message

FIG. 3 presents a flow chart 300 illustrating a method by a content requesting device or a content producing device for verifying and decrypting a selectively encrypted CCN message, in accordance with an embodiment of the present invention. During operation, the system receives, by a content producing device or a content requesting device, a message that includes a plurality of bit groups, each corresponding to a type, a length, and a set of values, wherein one or more bit groups are indicated as encrypted (operation 302). The message also indicates a name that is a hierarchically structured variable-length identifier comprising contiguous name components ordered from a most general level to a most specific level. The system determines whether the authentication information is verified (decision 304). For example, the system can look up in a key storage the key identifier. If the key identifier is found, the system can subsequently verify the authenticator tag(s) (e.g., a CWC-MAC signature) included in the validation section. If the authentication information is not verified, the system drops or discards the message (operation 306) and the operation returns. If the authentication information is verified, the system decrypts each bit group that is indicated as encrypted based on the corresponding symmetric key (operation 308).

Exemplary Format for Selectively Encrypted CCN Messages

FIG. 4A illustrates an exemplary format for a selectively encrypted CCN message 400, in accordance with an embodiment of the present invention. Message 400 can include a fixed header 402, optional headers 404, a message type 406, a message length 408, and a message value that comprises fields 410 and 412 and the fields shown in lines 414, 426, 436, 442, 452, 458, and 462. Field 410 can be a type field with a value of “T_NAME” and field 412 can be a length field with a value equal to “Name Length.” Line 414 can include TLV values for the first and second name components of a name: “T0,” “L0,” and “V0”; and “T1,” “L1,” and “V1.” Line 426 can include an indicator that the subsequent value or bit group (e.g., the third name component) is an encrypted value based on a specific symmetric key. For example, line 426 can include a type field with a value of “TE2,” a length field with a value of “LE2=L2+4” (e.g., the length of the third name component plus four bytes for the corresponding type and length fields, with values of “T2” and “L2,” respectively), and a value field that comprises the encrypted version of the bit group for the third name component (e.g., “T2,” “L2,” and “V2”), as indicated by the patterned background. The TE values may be selected from a range of values, which link to corresponding validation sections for each TE. The authentication range for each TE is over the entire CCN message. Furthermore, each TE indicates a value that is an independent key/nonce execution of the underlying AEAD scheme, e.g., GCM-AES. A validation section for TE2 is included in the message at line 468, as described below.

Line 436 can include TLV values for the fourth name component of a name: “T3,” “L3,” and “V3.” Line 442 can include an indicator that the subsequent value or bit group (e.g., the fifth name component) is an encrypted value. For example, line 442 can include a type field with a value of “TE4,” a length field with a value of “LE4=L4+4” (e.g., the length of the fifth name component plus four bytes for the corresponding type and length fields, with values of “T4” and “L4,” respectively), and a value field that comprises the encrypted version of the bit group for the fifth name component (e.g., “T4,” “L4,” and “V4”), as indicated by the patterned background. A validation section for TE4 is included in the message at line 470.

Line 452 includes another TLV bit group that has a type of “T_EXPIRY” and a corresponding length and value. Line 458 can include an indicator that the subsequent value or bit group (e.g., the payload of the message) is an encrypted value. For example, line 458 can include a type field with a value of “TE5,” a length field with a value of “LE5=L5+4” (e.g., the length of the payload component plus four bytes for the corresponding type and length fields, with values of “T_PAYLOAD” and “L5,” respectively), and a value field that comprises the encrypted version of the bit group for the payload (e.g., “T_PAYLOAD,” “L5,” and “Value”), as indicated by the patterned background.

Message 400 can also include a validation section that corresponds to each encryption scheme used in message 400. The validation sections can be included linearly, or, in the case of nested encryption, based on a post-order traversal. Message 400 can include a line 468 that indicates the validation algorithm and validation payload corresponding to the encryption marked by “TE2” at line 426. Message 400 can also include lines 470 and 472, which indicate the validation algorithm and validation payload corresponding to the encryption marked, respectively, by “TE4” at line 442 and by “TE5” at line 458. An exemplary format of a validation section is described below in relation to FIG. 5.

Given an original name such as “/a/b/c/d/e” for an interest, the selectively encrypted version of the name based on message 400 may be “/a/b/E_K2{c}/d/E_K4{e},” where K2 is indicated as the symmetric key used to encrypt the third name component, “c,” and K4 is indicated as the symmetric key used to encrypt the fifth name component, “e.”

FIG. 4B illustrates an exemplary format for a selectively encrypted CCN message 480, in accordance with an embodiment of the present invention. Message 480 can include similar fields as message 400 of FIG. 4A (different fields are marked with a dotted circle around the corresponding label), including fixed header 402, optional headers 404, message type 406, message length 408, and a message value that comprises fields 410 and 412 and the fields shown in lines 414, 426, 474, 452, 458, and 462. Lines 414 and 426 include similar information as in FIG. 4A for the first, second, and third name components. Line 474 can include an indicator that the subsequent value or bit group (e.g., the fourth and fifth name components) is an encrypted value. For example, line 474 can include a type field with a value of “TE3,” a length field with a value of “LE3=L3+L4+8” (e.g., the length of the fourth name component plus the length of the fifth name component plus eight bytes for the respective corresponding type and length fields, with values of “T3,” “L3,” “T4,” and “L4,” respectively), and a value field that comprises the encrypted version of the bit group for the fourth and fifth name components (e.g.: “T3,” “L3,” and “V3”; and “T4,” “L4,” and “V4”), as indicated by the patterned background. Lines 452, 458, 462, 468, and 472 of message 480 include similar information as described in relation to message 400 of FIG. 4A. Message 480 does include a line 476 that indicates the validation algorithm and validation payload corresponding to the encryption marked by “TE3 in message 480 at line 474.

Given an original name such as “/a/b/c/d/e” for an interest, the selectively encrypted version of the name based on message 480 may be “/a/b/E_K2{c}/E_K3{/d/e},” where K2 is indicated as the symmetric key used to encrypt the third name component, “c,” and K3 is indicated as the symmetric key used to encrypt the fourth and fifth name components, “/d/e”.

FIG. 4C illustrates an exemplary format for a selectively encrypted CCN message 490 with nested encryption, in accordance with an embodiment of the present invention. Message 490 can include similar fields as message 400 of FIG. 4A, including fixed header 402, optional headers 404, message type 406, message length 408, and a message value that comprises fields 410 and 412 and the fields shown in lines 414, 482, 492, 452, 458, and 462. Line 414 includes similar information as in FIG. 4A for the first and second name components.

Line 482 can include an indicator that the subsequent value or bit group (e.g., the third name component, and then, in a nested encryption, the fourth and fifth name components) is an encrypted value. For example, line 482 can include a type field with a value of “TE2” and a length field with a value of “LE2=L2+4+L3+L4+12.” “LE2” is calculated based on the length of the third name component plus four bytes for the corresponding type and length fields (with values of “T2” and “L2”), plus the length of the fourth and fifth name components plus 12 bytes for the respective corresponding type and length fields (with values of “TE3,” LE3,” “T3,” “L3,” “T4,” and “L4,” respectively). Line 482 can also include a value field that comprises both the encrypted version of the bit group for the third name component (e.g., “T2,” “L2,” and “V2”), as indicated by the patterned background, and the nested encryption depicted in line 492. Line 492 indicates a nested encryption that is included in the TE2 container of line 482. Line 492 can include a type field with a value of “TE3” and a length field with a value of “LE3=L3+L4+8.” “LE3” is calculated based on the length of the fourth and fifth name components plus eight bytes for the corresponding type and length fields (with values of “T3,” “L3,” “T4,” and “L4,” respectively). Line 492 can also include a value field that comprises the encrypted version of the bit group for the fourth and fifth name components (e.g., “T3,” “L3,” “V3,” “T4,” “L4,” and “V4”), as indicated by the patterned background.

Lines 452, 458, 462, and 472 of message 490 include similar information as described in relation to message 400 of FIG. 4A. The validation sections included in message 490 are slightly different based on the nested encryption of the TE3 values (fourth and fifth name components) within the TE2 encryption container. In general, an encryptor includes a validation section for each encrypted context or container. For a nested encryption, the validation section corresponding to the nested encryption must also be encrypted under the same parent container. For example, TE3 is a nested encryption under TE2, so the validation section corresponding to TE3 is also encrypted under TE2. Message 480 includes a line 494 which depicts this scenario. Line 494 includes an indicator that the subsequent value (e.g., the TE3 validation section) is an encrypted value. Line 494 can include a type field with a value of “TE2” and a length field for a value of “L” that corresponds to the length of the validation section for TE3. Line 496 indicates the validation algorithm and validation payload corresponding to the encryption marked by “TE2,” and line 472 indicates the validation algorithm and validation payload corresponding to the encryption marked by “TE5.”

Given an original name such as “/a/b/c/d/e” for an interest, the selectively encrypted version of the name based on message 490 may be “/a/b/E_K2{c, E_K3{/d/e} },” where K2 is indicated as the symmetric key used to encrypt the third name component, “c,” and the (nested) encrypted version of the fourth and fifth name components, and K3 is indicated as the symmetric key used to encrypt the fourth and fifth name components, “/d/e”.

FIG. 4D illustrates an exemplary format for an encoding graph 498 with a post-order traversal, corresponding to the exemplary format for message 490 in FIG. 4C, in accordance with an embodiment of the present invention. Graph 498 depicts containment of bit groups as left nodes and sequential ordering of bit groups as right nodes. Functions 498.1, 498.2, and 498.3 correspond to a depth-first search post-order for encrypting the bit groups in their respective containers. For example, function 498.1 is the first function performed and corresponds to the inner TE3 container for encrypting the T3 and T4 name components (marked with a “1” in a circle). Based on the post-order traversal, the next function is function 498.2, which corresponds to the TE2 container for encrypting the T2 bit group and the encrypted T3 container (marked with a “2” in a circle). Finally, the third function is function 498.3, which corresponds to the TE5 container for encrypting the payload (marked with a “3” in a circle). In some embodiments, without nested encryption, the traversal can be performed linearly or based on an ascending TE value.

FIG. 4E illustrates an exemplary format for an encoding graph 499 with a post-order traversal, corresponding to the exemplary format for message 490 in FIG. 4C, in accordance with an embodiment of the present invention. Similar to graph 498, graph 499 depicts containment of bit groups as left nodes and sequential ordering of bit groups as right nodes. Functions 499.1, 499.2, and 499.3 correspond to a depth-first search reverse post-order for decrypting the bit groups in their respective containers. For example, the first function performed is function 499.1, which corresponds to the TE5 container for decrypting the payload (marked with a “1” in a circle). Based on the post-order traversal, the next function is function 499.2, which corresponds to the TE2 container for decrypting the T2 bit group and the encrypted T3 container (marked with a “2” in a circle). Finally, function 499.3 is the third function and corresponds to the inner TE3 container for decrypting the T3 and T4 name components (marked with a “3” in a circle). Note that decryption is performed in the reverse order of the validation sections listed in the packet. Thus, functions 499.1-499.3 are performed in a reverse post-order which corresponds to the reverse order of the validation sections listed in FIG. 4C.

Exemplary Format for Validation Section of Selectively Encrypted CCN Messages

FIG. 5 illustrates an exemplary format for a validation section 500 of a selectively encrypted CCN message, in accordance with an embodiment of the present invention. Validation section 500 can include a validation algorithm (lines 502, 506, 512, and 518) and a validation payload (lines 524 and 528). The validation algorithm section can include a nonce and a KeyId for each symmetric key used to encrypt a bit group. For example, line 502 can include a type field with a value of “T_VALALG” and a length field whose value includes the length of the fields shown in lines 506, 512, and 518. Line 506 is a TLV bit group for the KeyId and includes: a type field with a value of “T_KEYID”; a length field; and a value field of “KeyID.” Line 512 is a TLV bit group for the nonce and includes: a type field with a value of “T_NONCE”; a length field with a value of 1-8 bytes; and a value field of “Nonce(IV).” As described above, the KeyId identifies a (key, salt) pair which is created during association setup, while the nonce is 1-8 bytes in size and left-padded with 0's to 8 bytes and appended to the salt to form the GCM-AES IV.

Line 518 is a TLV bit group for the container, which is a range of encrypted container values that allows matching of keys to containers. For example, line 518 can include a type field with a value of “T_CONTAINER,” a length field with a value of “2,” and a value field that is the “TE Value” (e.g., TE2 of message 400 in FIG. 4A).

Line 524 includes a type field with a value of “T_PAYLOAD” and a length field with a value of 8, 12, or 16 bytes (as described in RFC 4106), and line 528 includes a value field that comprises an authenticator tag which is created based on the underlying AEAD scheme. For example, using AES-GCM as described above, the authenticator tag is created based on a GHASH function performed over all of the encrypted and non-encrypted data for each encrypted container.

Wrapping Solution/Method

In addition to the selective encryption of a CCN message described herein, a CCN message may also be encrypted based on a wrapping method. This method involves encapsulating an interest packet or a content object packet with a routable encapsulation name and various “wrapper” headers. To create a “wrapper” interest of an original interest, an entity creates a T_ENCAP packet, assigns an encapsulation or “wrapper” name to the wrapper interest, and places the original interest in an encrypted container after the name. The entity adds a validation section (e.g., ValidationAlg and ValidationPayload), where the ValidationAlg identifies that this specific scheme is being used and is 0-bytes of value.

To create a “wrapper” content object of an original content object, an entity creates a T_ENCAP packet, assigns the same wrapper interest name to the wrapper content object, and places the original content object in an encrypted container. The encrypted container for the original content object typically has a different TE number or encryption container indicator than the encrypted or wrapped interest. For example, if a consumer wraps the original interest in a container based on a symmetric key K1, it is likely that a responding producer wraps the responsive content object in a container based on a different symmetric key K2. Note that the consumer and the producer both possess the secret symmetric keys K1 and K2 via a key exchange protocol. Similar to wrapping the original interest, the entity that wraps the original content object adds a validation section, which includes a ValidationAlg with the (KeyID, Nonce) pair used by the encrypted container, and further includes a ValidationPayload with the authenticator tag. If there is only one encrypted container (e.g., only one TE or encrypted container), the encryptor does not need to include the TE number in the validation section. Plaintext cache control directives (or other TLVs) may be included in the T_ENCAP packet outside of the encrypted interest or content object packet.

Exemplary Apparatus and Computer System

FIG. 6 illustrates an exemplary apparatus 600 that facilitates selective encryption of bit groups of a CCN message, in accordance with an embodiment of the present invention. Apparatus 600 can comprise a plurality of modules which may communicate with one another via a wired or wireless communication channel. Apparatus 600 may be realized using one or more integrated circuits, and may include fewer or more modules than those shown in FIG. 6. Further, apparatus 600 may be integrated in a computer system, or realized as a separate device which is capable of communicating with other computer systems and/or devices. Specifically, apparatus 600 can comprise a communication module 602, a block computing module 604, a bit group encrypting module 606, a bit group decrypting module 608, and a security module 610.

In some embodiments, communication module 602 can send and/or receive data packets to/from other network nodes across a computer network, such as a content centric network, where a data packet can correspond to an interest or a content object message that includes a plurality of bit groups, each corresponding to a type, a length, and a set of values, wherein one or more bit groups are marked for encryption. Block computing module 604 can compute a plurality of cipher blocks for the message based on an authenticated encryption protocol. Bit group encrypting module 606 can encrypt the one or more bit groups marked for encryption based on one or more symmetric keys, wherein the marked bit groups include one or more name components. Bit group encrypting module 606 can also indicate the encrypted bit groups as encrypted.

Communication module 602 can transmit the selectively encrypted message to a content producing device or a content requesting device. Bit group encrypting module 606 can indicate the encrypted bit groups as encrypted by setting a field associated with the bit group in the message or by setting a reserved bit associated with the bit group in the message.

Security module 610 can include in a validation section for the message a nonce and a key identifier for each of the symmetric keys. Security module 610 can also include one of the following: wherein a symmetric key is exchanged via a public key operation; wherein a symmetric key is encrypted based on a public key included in the message; wherein the validation section is based on a symmetric key cryptographic system with encryption; wherein a public key identifier of the content producing device is included in the message; and wherein a short symmetric key identifier is specified for use in subsequent messages between the content requesting device and the content producing device. Security module 610 can verify the authentication information associated with the message by: looking up in a storage a key identifier associated with the message; and verifying a signature or a message authentication code based on the key identifier.

Communication module 602 can receive the selectively encrypted message. In response to verifying authentication information associated with the message (security module 610), bit group decrypting module 608 can decrypt, for each bit group indicated as encrypted, the encrypted bit group based on a corresponding symmetric key, wherein a nonce and a key identifier for each of the symmetric keys are included in a validation section for the message. Bit group decrypting module 608 can indicate the decrypted bit groups as decrypted.

FIG. 7 illustrates an exemplary computer system 702 that facilitates selective encryption of bit groups of a CCN message, in accordance with an embodiment of the present invention. Computer system 702 includes a processor 704, a memory 706, and a storage device 708. Memory 706 can include a volatile memory (e.g., RAM) that serves as a managed memory, and can be used to store one or more memory pools. Furthermore, computer system 702 can be coupled to a display device 710, a keyboard 712, and a pointing device 714. Storage device 708 can store an operating system 716, a content-processing system 718, and data 730.

Content-processing system 718 can include instructions, which when executed by computer system 702, can cause computer system 702 to perform methods and/or processes described in this disclosure. Specifically, content-processing system 718 may include instructions for sending and/or receiving data packets to/from other network nodes across a computer network, such as a content centric network, where a data packet can correspond to an interest or a content object message that includes a plurality of bit groups, each corresponding to a type, a length, and a set of values, wherein one or more bit groups are marked for encryption. Content-processing system 718 can include instructions for computing a plurality of cipher blocks for the message based on an authenticated encryption protocol (block computing module 722). Content-processing system 718 can also include instructions for encrypting the one or more bit groups marked for encryption based on one or more symmetric keys and for indicating the encrypted bit groups as encrypted (bit group encrypting module 724).

Content-processing system 718 can further include instructions for transmitting the selectively encrypted message to a content producing device or a content requesting device (communication module 720). Content-processing system 718 can include instructions for indicating the encrypted bit groups as encrypted by setting a field associated with the bit group in the message or by setting a reserved bit associated with the bit group in the message (bit group encrypting module 724).

Content-processing system 718 can additionally include instructions for including in a validation section for the message a nonce and a key identifier for each of the symmetric keys (security module 728). Content-processing system 718 can include instructions for including one or more of the following: wherein a symmetric key is exchanged via a public key operation; wherein a symmetric key is encrypted based on a public key included in the message; wherein the validation section is based on a symmetric key cryptographic system with encryption; wherein a public key identifier of the content producing device is included in the message; and wherein a short symmetric key identifier is specified for use in subsequent messages between the content requesting device and the content producing device (security module 728). Content-processing system 718 can also include instructions for verifying the authentication information associated with the message by: looking up in a storage a key identifier associated with the message; and verifying a signature or a message authentication code based on the key identifier (security module 728).

Content-processing system 718 can also include instructions for receiving the selectively encrypted message (communication module 720). Content-processing system 718 can include instructions for, in response to verifying authentication information associated with the message (security module 728), decrypting, for each bit group indicated as encrypted, the encrypted bit group based on a corresponding symmetric key, wherein a nonce and a key identifier for each of the symmetric keys are included in a validation section for the message (bit group decrypting module 726). Content-processing system 718 can include instructions for indicating the decrypted bit groups as decrypted (bit group decrypting module 726).

Data 830 can include any data that is required as input or that is generated as output by the methods and/or processes described in this disclosure. Specifically, data 830 can store at least: a packet or message that corresponds to an interest or a content object; a bit group that corresponds to a type, a length, and a set of values; a name that is a hierarchically structured variable-length identifier (HSVLI) comprising contiguous name components ordered from a most general level to a most specific level; a message that includes a plurality of bit groups, wherein one or more bit groups are marked for encryption, and wherein the message indicates a name that is an HSVLI; a plurality of cipher blocks; an indicator of an authenticated encryption protocol; one or more symmetric keys; a key identifier or a KeyId; a nonce; a key, salt pair; Initialization Vectors; plaintext; ciphertext; associated data; an authentication tag or an authenticator; a GHASH function; an indicator of an encrypted bit group or a decrypted bit group; a field or a reserved bit associated with a bit group; an indicator of a public key operation; a public key; an indicator of a symmetric key cryptographic system with encryption; a public key identifier or a public KeyId; a short symmetric key identifier; a key storage; and a signature or a message authentication code.

The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. The computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.

The methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above. When a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.

Furthermore, the methods and processes described above can be included in hardware modules. For example, the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed. When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.

The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.

Claims

1. A system comprising: a content requesting device configured to communicate with a content centric network (CCN) and to perform a method comprising: generating an Interest requesting a content object by a hierarchically structured variable-length name that is used to forward the Interest in the CCN, the name comprising name components arranged contiguously in an order from a most general level to a most specific level and each including a bit group comprising a type, a length, and a set of values, wherein one or more of the name components at the most specific level are marked for encryption;exchanging one or more symmetric keys via a public key operation;encrypting each name component at the most specific level marked for encryption using a respective symmetric key, to produce a selectively encrypted name having one or more encrypted name components and one or more unencrypted name components;indicating each encrypted name component as encrypted by setting a respective field associated with the bit group of the encrypted name component;including in the Interest a validation section that identifies the respective symmetric key for each encrypted name component; andtransmitting the Interest to the CCN; anda content producing device configured to receive the Interest from the CCN and responsive thereto, perform a method comprising: verifying authentication information associated with the Interest by looking up in a storage a key identifier associated with the Interest;responsive to the verifying, decrypting, for each encrypted name component indicated as encrypted, the encrypted name component based on a corresponding symmetric key, wherein a nonce and a key identifier for each of the symmetric keys are included in a validation section for the Interest;indicating the decrypted name components as decrypted; andproducing a content object that matches the name components as decrypted.

2. The system of claim 1, wherein the method further comprises: encrypting the content object using one of the symmetric keys.

3. The system of claim 1, wherein the encrypting includes computing a plurality of cipher blocks for the Interest based on an authenticated encryption protocol.

4. The system of claim 3, wherein computing the cipher blocks is further based on beginning at byte zero of the Interest.

5. The system of claim 3, wherein computing the cipher blocks is further based on an Advanced Encryption Standard using a key with a length of 128 bits.

6. The system of claim 1, wherein encrypting the bit groups of the name components marked for encryption is further based on an exclusive disjunction operation.

7. The system of claim 1, wherein indicating each encrypted name component further comprises: setting a reserved bit associated with the bit group of the encrypted name component.

8. The system of claim 1, further comprising one or more of the following: wherein a symmetric key is encrypted based on a public key included in the Interest;wherein the validation section is based on a symmetric key cryptographic system with encryption;wherein a public key identifier of the content requesting device is included in the Interest; andwherein a symmetric key identifier is specified for use in subsequent messages between the content requesting device and the content producing device.

9. The system of claim 8, further comprising one or more of the following: wherein the public key operation is based on a cryptographic system that is Rivest-Shamir-Adleman Secure Hash Algorithm 256-bit (RSA-SHA 256); andwherein the symmetric key identifier is a random number that is not derived from the symmetric key.

10. The system of claim 1, wherein the Interest is configured to be forwarded to the content producing device by CCN nodes along a path of the CCN based on the name.

11. The system of claim 10, wherein the content object packet is configured to be forwarded to the content requesting device along a path of the CCN in reverse to the Interest based on the name.

12. A computer-implemented method comprising: at a content producing device configured to communicate with a content centric network (CCN): generating a content object packet responsive to an Interest from a content requesting device that requests a content object by a hierarchically structured variable-length name, the content object packet including the content object and the name to be used to forward the content object packet in the CCN, the name comprising name components arranged contiguously in an order from a most general level to a most specific level and each including a bit group comprising a type, a length, and a set of values, wherein one or more of the name components are marked for encryption;exchanging one or more symmetric keys via a public key operation;encrypting each name component at the most specific level marked for encryption using a respective symmetric key, to produce a selectively encrypted name having one or more encrypted name components and one or more unencrypted name components;indicating each encrypted name component as encrypted by setting a respective field associated with the bit group of the encrypted name component;including in the content object packet a validation section that identifies the respective symmetric key for each encrypted name component; andtransmitting the content object packet to the CCN; andat the content requesting device, receiving the content object packet from the CCN, and responsive thereto: verifying authentication information associated with the content object packet by looking up in a storage a key identifier associated with the content object packet, and verifying a signature or a message authentication code based on the key identifier;responsive to the verifying, decrypting, for each encrypted name component indicated as encrypted, the encrypted name component based on a corresponding symmetric key, wherein a nonce and a key identifier for each of the symmetric keys are included in the validation section for the content object packet;indicating the decrypted name components as decrypted; andbased on the decrypted name components, performing a lookup, and clearing an entry, in a Pending Interest Table (PIT) corresponding to the Interest.

13. The method of claim 12, wherein the method further comprises: encrypting the content object of the content object packet using one of the symmetric keys; andstoring in the validation section an identifier of the one of the symmetric keys used to encrypt the content object.

14. The method of claim 12, wherein indicating each encrypted name component further comprises: setting a reserved bit associated with the bit group of the encrypted name component.

15. The method of claim 12, further comprising one or more of the following: wherein the validation section is based on a symmetric key cryptographic system with encryption;wherein a public key identifier of the content producing device is included in the content object packet; andwherein a symmetric key identifier is specified for use in subsequent messages between the content requesting device and the content producing device.

16. The method of claim 15, further comprising one or more of the following: wherein the public key operation is based on a cryptographic system that is Rivest-Shamir-Adleman Secure Hash Algorithm 256-bit (RSA-SHA 256); andwherein the symmetric key identifier is a random number that is not derived from the symmetric key.

17. The method of claim 12, wherein the content object packet is configured to be forwarded to the content requesting device along a path of the CCN in reverse to the Interest based on the name.

18. The method of claim 12, wherein the encrypting includes computing a plurality of cipher blocks for the content object packet based on an authenticated encryption protocol.

19. The system of claim 1, wherein the encrypting includes first encrypting the one or more of the name components marked for encryption using a first symmetric key and second encrypting results of the first encrypting using a second symmetric key to produce one or more nested encryption name components.

20. The system of claim 19, further comprising: encrypting the second symmetric key and storing the results in the validation section in correspondence with the one or more nested encryption name components.

21. The system of claim 1, wherein the Interest is configured to be forwarded to the content producing device by CCN nodes along a path of the CCN based on the name, and the content object packet is configured to be forwarded to the content requesting device along a path of the CCN in reverse to the Interest based on the name.

22. The method of claim 1, wherein the encrypting each name component at the most specific level includes encrypting at least two name components at the most specific level with at least two respective symmetric keys.

23. The method of claim 12, wherein the encrypting each name component at the most specific level includes encrypting at least two name components at the most specific level with at least two respective symmetric keys.

24. The method of claim 12, further comprising, at the content requesting device, when the authentication information is not verified, discarding the content object.