Method and system for verifying renamed content using manifests in a content centric network

Information

  • Patent Grant
  • 9536059
  • Patent Number
    9,536,059
  • Date Filed
    Monday, December 15, 2014
    9 years ago
  • Date Issued
    Tuesday, January 3, 2017
    7 years ago
Abstract
One embodiment provides a system that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information. During operation, the system determines, by a content producing device, an original manifest which indicates at least an original name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level. The system renames the content object with a new name. The system also creates a new manifest which indicates the new name, wherein the new manifest includes original authentication information associated with the original manifest.
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”); and
    • U.S. patent application Ser. No. 14/231,515, entitled “AGGREGATE SIGNING OF DATA IN CONTENT CENTRIC NETWORKING,” by inventors Ersin Uzun, Marc E. Mosko, Michael F. Plass, and Glenn C. Scott, filed 31 Mar. 2014 (hereinafter “U.S. patent application Ser. No. 14/231,515”);


      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 verifying the original producer of content in a content centric network (CCN) by using manifests that rename objects and include authentication information for the original producer.


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.


In addition to the identifying name and a payload, CCN content objects can include a signature for the content producer. The signature binds the name, payload, and identity of the signer (e.g., the producer). The name is used to match, route, and forward the content. In order to move or redistribute the content to serve the content from a location that is not reachable by the same name (e.g., from a web-cache location other than the one corresponding to the name), a system can either update the routing information or rename the content. However, updating the routing information can result in computational overhead due to modifying the routing tables (e.g., Forwarding Information Bases) at intermediate routers within a CCN. Furthermore, renaming the content breaks the binding security association between the unique name of the content and the authentication information of the producer (e.g., the signature and the identity), leaving a receiving CCN entity with no way to authenticate the original producer of the content.


SUMMARY

One embodiment provides a system that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information. During operation, the system determines, by a content producing device, an original manifest which indicates at least an original name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level. The system renames the content object with a new name. The system also creates a new manifest which indicates the new name, wherein the new manifest includes original authentication information associated with the original manifest.


In some embodiments, the original authentication information indicates one or more of: an identity of a producer of the original manifest; and a digital signature of the producer of the original manifest.


In some embodiments, the original authentication information is one or more of: information embedded in the new manifest; information derived from the original manifest; and a linked object that is derived from the original manifest, wherein the linked object is an object which is distinct from the original manifest.


In some embodiments, renaming the content object involves one or more of: adding a prefix to the original name; replacing a part of the original name with a part of the new name; and any function that creates a one-to-one mapping of the new name to the original name.


In some embodiments, the original authentication information indicates a self-certifying name based on the original name, wherein the self-certifying name uniquely identifies the content object.


In some embodiments, the self-certifying name includes a cryptographic digest of the content object.


In some embodiments, the new manifest indicates a self-certifying name based on the new name, wherein the self-certifying name uniquely identifies the content object.


In some embodiments, the system receives, by a content consuming device, a new manifest which indicates at least a new name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level, and wherein the new manifest includes original authentication information associated with an original manifest which indicates an original name associated with the content object. The system retrieves the content object based on the new name. The system also verifies the retrieved content object by: replacing the new name with the original name; and authenticating the content object with the original name using the original authentication information, thereby facilitating redistribution of content objects with a different name without requiring re-computation of the original authentication information.


In some embodiments, the system retrieves the original manifest, wherein the original authentication information indicates a self-certifying name based on the original name, and wherein the self-certifying name uniquely identifies the content object.


In some embodiments, the system verifies the original manifest by authenticating a digital signature of a producer of the original manifest based on a public key of the producer.


In some embodiments, verifying the obtained content object further comprises: calculating a self-certifying name for the content object based on the original name; comparing the calculated self-certifying name with the self-certifying name indicated in the original authentication information; and responsive to determining that the calculated self-certifying name matches the self-certifying name indicated in the original authentication information, authenticating the obtained content object.





BRIEF DESCRIPTION OF THE FIGURES


FIG. 1 illustrates an exemplary computing environment that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information, in accordance with an embodiment of the present invention.



FIG. 2 presents a flow chart illustrating a method performed by a content publisher for creating a new manifest based on an original manifest created by a content producer, in accordance with an embodiment of the present invention.



FIG. 3 presents a flow chart illustrating a method performed by a content consumer for retrieving content based on a new manifest, verifying the original producer of the content, and verifying the content, in accordance with an embodiment of the present invention.



FIG. 4 presents tables depicting a format of an original manifest, an exemplary original manifest, a format of a new manifest, and an exemplary new manifest, in accordance with an embodiment of the present invention.



FIG. 5 presents tables depicting a format of an original content object, an exemplary original content object, a format of a new content object, and an exemplary new content object, in accordance with an embodiment of the present invention.



FIG. 6 presents tables depicting a format of an encapsulated original manifest and an exemplary encapsulated original manifest, in accordance with an embodiment of the present invention.



FIG. 7 illustrates an exemplary computer and communication system that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information, 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 that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information. This redistribution is achieved through the use of manifests and self-certifying content objects. A manifest is a content object that describes a collection of content objects and can include a name, a signature, and the identity of the signer (e.g., the content producer). A signed manifest can provide trust to a requesting application for the content objects described by the manifest. Signing and verifying aggregates of content objects through the use of a secure content catalog (e.g., a manifest) is described in U.S. patent application Ser. No. 14/231,515. A manifest can include a self-certifying name for each content object described in its collection. Upon receiving and verifying the manifest, a requesting application can trust the individual content objects by simply verifying the self-certifying name. A self-certifying name is a name that uniquely identifies the content, and can include a cryptographic hash of the content, a key/name combination, and a digest that is a last name component of the name. Because trust in the manifest has been established, the requesting application can verify a content object described in the manifest by verifying the self-certifying name (e.g., by calculating the hash value of the received content object) and comparing it to the self-certifying name included in the manifest. Because content objects are verified and authenticated through the manifest based on their self-certifying names (e.g., the content object hash), the content objects do not require a signature, though the manifest can contain a signature in some embodiments.


When a content re-publisher (e.g., a content caching service such as Akamai) wishes to re-publish content that has been previously published by the original content producer (e.g., a producer such as Netflix), the re-publisher can assign a new name to the content and, at the same time, preserve the security binding of the original content producer. For example, an original content producer publishes content and creates an original manifest that describes the content objects by original names. The original manifest can include a digital signature for all the content names, and each content name can include a hash for the corresponding content object. A content cache service wishes to re-publish the same content under a new name, so the content cache service encapsulates the original manifest under a new name. In addition, the content cache service renames each content object of the original manifest with a new name. As a result, each renamed content object has a new name, the same payload, and a different content object hash as the original content object hash. The content cache service also creates a new manifest that describes the content objects by their new names.


A user (e.g., a content consumer who wishes to view the content) can retrieve the content from the content cache service by first retrieving the new manifest and then retrieving the content objects described in the new manifest (by the new name). As discussed above, the content consumer can verify the content objects described in the new manifest by calculating the self-certifying name (e.g., by calculating a hash for the content object) and comparing it to the self-certifying name included in the manifest (e.g., the hash value included in the original name as indicated in the original manifest). In order to verify the original producer, the content consumer retrieves the encapsulated original manifest, verifies the original manifest by authenticating the digital signature of the original producer, and subsequently verifies each of the content objects described in the new manifest based on the hash included in each name. To verify each of the content objects described in the new manifest, the consumer renames each of the content objects by replacing the new name (as described in the new manifest) with the original name (as described in the original manifest). The consumer then authenticates the content object with the original name by calculating a hash for the content object and comparing that hash to the hash included in the original name indicated in the original manifest. Thus, the system redistributes the content objects under a new name without the computational overhead required to re-compute the original authentication information.


In addition to providing direct trust based on a digital signature by the producer, a manifest can provide indirect trust when the original link to the manifest is a self-certifying name (e.g., a hash-based name). A manifest can link to other manifests, thus creating a hierarchical structure of manifests through which trust can be chained and established. In some embodiments, the original producer manifest (e.g., the original manifest produced by the original content producer) is linked from the new publisher manifest (e.g., the new manifest published by the content cache service). The original manifest can be embedded in the new manifest. In some embodiments, the manifest contains a hash of the payload rather than a hash of the content object. In this case, the name is not a part of the data being hashed, so the name does not need to be re-written.


The original producer can sign a link (with a hash-based name) to a manifest, rather than sign the entire manifest itself. Thus, the new publisher manifest can include the link and the signature. Similarly, the content objects described in a manifest may or may not include signature information. If the signature information is included in the content objects with the original names, the signature information will not be valid under the new name. Note that the hash will still be valid, as the content of the payload itself does not change. If the signature information is not included in the content objects with the original names, the re-publisher can include signature information on the content objects with the new names. The re-publisher indicates accordingly to the content consumer that in order for the content consumer to verify the original producer (based on the self-certifying names in the original producer manifest) the included publisher signature information is to be stripped. In addition, if the re-publisher signs the content objects under the new names, the re-publisher can include in the new manifest keyId based links to the content objects, rather than the self-certifying name links. For example, the new manifest can include links to the content objects, and the re-publisher can include a private keyID for the links to the content objects that the content consumer can use to authenticate the content objects.


In examples described in this disclosure, each piece of content is individually named, and each piece of data is bound to a unique name that distinguishes the data from any other piece of data, such as other versions of the same data or data from other sources. This unique name allows a network device to request the data by disseminating a request or an Interest that indicates the unique name, and can obtain the data independent from the data's storage location, network location, application, and means of transportation. The following terms are used to describe the CCN architecture:


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. 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:


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.


Network Architecture and Overview of Manifests



FIG. 1 illustrates an exemplary computing environment 100 that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information, in accordance with an embodiment of the present invention. Computing environment 100 can include a content producer 104 and a content publisher 106, both of which can include any content producing device that can publish or produce content and fulfill a request for content via a network 102. Computing environment 100 can also include a content consumer 108, which can include any content consuming device that can determine a request for content via a network 102. For example, client device 108 can include a smartphone 108.1, a tablet computer 108.2, and/or a personal computing device 108.p (e.g., a laptop). Computing environment 100 can also include network 102 which can be, for example, a content-centric network (CCN), a named data network (NDN), or an information-centric network (ICN). The term “content producer” is used herein to describe a content producer of original content, while the term “content publisher” is used herein to describe a content producer that publishes previously produced or previously published content (e.g., original content produced by a content producer).


During operation, content producer 104 produces original content and creates original manifest 120 to describe the original content. Original manifest 120 contains a manifest name 122 and a list of content objects by an original name 130.1-130.n. Original manifest 120 can also contain an original hash value 132.1-132.n associated with each content object. In some embodiments, the hash value 132.1-132.n can be part of a self-certifying name which, when hashed, is a name which uniquely identifies the content object. In addition, original manifest 120 can contain an identity of a producer 134 and a producer signature 136.


In order to republish the original content under a different name and at the same time maintain the security binding of the original content to content producer 104, content publisher 106 renames the content objects with new names and creates a new manifest 140 which contains a manifest name 142 and a list of content objects by a new name 150.1-150.n. New manifest 140 can also contain new hash values 152.1-152.n associated with each content object. Similar to original hash values 132.1-132.n of original manifest 120, new hash values 152.1-152.n can be part of a self-certifying name which, when hashed, is a name which uniquely identifies the content object. The content objects with new names 150.1-150.n have different names than the original names 130.1-130.n, result in new hash values 152.1-152.n that are different from original hash values 130.1-130.n, but each contain the same data or payload as the corresponding content objects with original names 130.1-130.n. Additionally, new manifest 140 can contain an identity of a publisher 154, a publisher signature 156, and original authentication information 160 which indicates information relating to original manifest 120.


Content Publisher Creates New Manifest



FIG. 2 presents a flow chart 200 illustrating a method performed by a content publisher for creating a new manifest based on an original manifest created by a content producer, in accordance with an embodiment of the present invention. During operation, the system creates, by a content producer, an original manifest that indicates content objects which are each associated with an original name (operation 202). The content producer authenticates the original manifest by including original authentication information for the original manifest (“original authentication information”) (operation 202). In some embodiments, the original authentication information includes the identity of the original content producer and a signature of the producer. A content publisher encapsulates the original manifest, including the original authentication information, under a new encapsulated original manifest name (operation 204). The content publisher renames the content objects with a new name, such that the content objects are associated with a name that is different from the original name, produce a different content object hash value, but contain the same payload data (operation 206). In some embodiments, the system derives the new name from the original name. The system can rename the content objects based on a one-to-one mapping function such as adding a prefix to the original name or replacing a part of the original name with a part of the new name. Finally, the content publisher creates a new manifest under a new manifest name, where the new manifest indicates content objects which are each associated with a new name (operation 208). The new manifest also includes the original authentication information from the original manifest.


Consumer Retrieves Content, Verifies Producer, and Verifies Content



FIG. 3 presents a flow chart 300 illustrating a method performed by a content consumer for retrieving content based on a new manifest, verifying the original producer of the content, and verifying the content, in accordance with an embodiment of the present invention. During operation, a content consumer retrieves a new manifest using the new manifest name (operation 302). The new manifest indicates content objects which are each associated with a new name. The content consumer retrieves the content objects by the new names as indicated in the new manifest (operation 304). The content consumer retrieves the encapsulated original manifest under the new encapsulated original manifest name in order to obtain a copy of the original manifest (operation 306). The content consumer then extracts the original authentication information from the original manifest (operation 308). As discussed above, the original authentication information can include the identity of the producer and a signature of the producer. The original authentication information can also include a self-certifying name for the content objects. For example, the self-certifying name can be a name that includes a hash of the content (e.g., a cryptographic digest), a key/name combination, and a digest that is a last name component of the name. As described above, because the manifest itself is signed and because the content objects can be verified through their self-certifying names, the content objects do not require an individual signature, though in some embodiments, the content objects can contain an individual signature.


Subsequently, the content consumer verifies the original manifest based on the original authentication information, which includes the identity and signature of the original producer (operation 310). For example, the content consumer can use a known signature verification function and a public key of the identified original producer to authenticate the original manifest. In some embodiments, the content consumer does not require verification of the original producer, and therefore does not perform the step described by operation 310.


The content consumer then verifies the retrieved content objects, which are each associated with a new name. First, the content consumer replaces the new name of each content object with the original name as indicated in the original manifest (operation 312). In some embodiments, the system replaces the new name based on a one-to-one mapping function, such as replacing a part of the new name with a part of the original name or removing a part of the new name to obtain the original name. For example, when creating the new name, the content publisher can add a prefix to the old name, such that when the consumer checks for trust (e.g., verifies the original producer, the original manifest, and each content object described in the new manifest), the consumer needs only remove the prefix in order to convert the content object name back to the original name. Second, the content consumer calculates the self-certifying name for the content objects associated with names that have been converted back to the original name (operation 314). In some embodiments, the system performs a hash function on the content object associated with the original name. Finally, the content consumer compares the calculated self-certifying name with the self-certifying name indicated in the original authentication information (as described in the original manifest) (operation 316). In some embodiments, the system compares the calculated hash value (from operation 314) of the content object associated with the original name and compares that to the hash value of the originally named content object as described in the original manifest. If there is a match (decision 318), the method returns, indicating that the retrieved content objects have been properly authenticated. If there is not a match, the system will discard or ignore the content objects (operation 320).


Exemplary Format of Original and New Manifests



FIG. 4 presents tables depicting a format of an original manifest 420, a format of a new manifest 440, an exemplary original manifest 460, and an exemplary new manifest 480, in accordance with an embodiment of the present invention. The content objects described in a manifest can be represented by various schemes. One scheme is to list the name of each content object and the corresponding hash value. Another scheme is to use a common naming or link root (e.g., a content base name) and a list of final segment names along with their corresponding hash values. Another scheme is to use a predictable name, such as a counter. The tables in FIG. 4 depict the use of a content base name and a list of final segment names. Original manifest 420 can contain a manifest name 422, an original content base name 424, content link items 430, an identity of a producer 434, and a producer signature 436. Content link items 430 can include a final segment 430.1-430.n and an original hash value 432.1-432.n. Exemplary original manifest 460 depicts a manifest that includes: a manifest name of “/netflix/frozen/manifest”; an original content base name of “/netflix/frozen/content”; content links items number 1-n, where the name of the final segment of the content object numbered 1 is “c_1” with a corresponding hash value of “hash(CO/netflix/frozen/content/c_1)”; an identity of the producer with a value of “Netflix”; and a producer signature with a value of “Netflix_Sig.”


Similarly, new manifest 440 can contain a manifest name 442, a new content base name 444, content link items 450, an identity of the publisher 454, and a publisher signature 456. Content link items 450 can include a final segment 450.1-450.n and a new hash value 452.1-452.n. New manifest 440 can also include original authentication information 460, which can include a new encapsulated original manifest name 462 and an original manifest hash value 464. Exemplary original manifest 480 depicts a manifest that includes: a manifest name of “/akamai/frozen/manifest”; an original content base name of “/akamai/frozen/content”; content link items numbered 1-n, where the name of the final segment of the content object numbered 1 is “c_1” with a corresponding hash value of “hash(CO/akamai/frozen/content/c_1)”; an identity of the publisher with a value of “Akamai”; and a publisher signature with a value of “Akamai_Sig.” Exemplary original manifest 480 can also include original authentication information which includes: a new encapsulated original manifest name of “/akamai/frozen/original-manifest”; and an original manifest hash value of “hash(CO/netflix/frozen/manifest).”


In FIG. 4, the original authentication information is depicted as including the new encapsulated original manifest name and the hash of the original manifest (e.g., the original authentication information is information embedded in the new manifest). In some embodiments, the original authentication information is information derived from the original manifest. The original authentication information can also be a linked object that is derived from the original manifest, where the linked object is an object which is distinct from the original manifest (e.g., a pointer to a separate object). In other embodiments, the original authentication information indicates the hash of the content objects described by the manifest, which are depicted in original manifest 420 and new manifest 440 of FIG. 4 as part of content link items 430 and 450, respectively (e.g., a self-certifying name).


Exemplary Format of Other Objects



FIG. 5 presents tables depicting a format of an original content object 510, an exemplary original content object 520, a format of a new content object 530, and an exemplary new content object 540, in accordance with an embodiment of the present invention. Original content object 510 includes an original name 512 and a payload 514. Exemplary original content object 520 includes an original name with a value of “/netflix/frozen/content/c1” and a payload with a value of “data1.” New content object 530 includes a new name 532 and a payload 534. Exemplary new content object 540 includes a new name with a value of “/akamai/frozen/content/c1” and a payload with a value of “data1.” Note that while the new name and the original name are different, the payload data for both exemplary original content object 520 and exemplary new content object 540 are the same (e.g., “data1”). Furthermore, a self-certifying name (not illustrated) that includes a hash value of the content object based on the name (e.g., the new name for exemplary new content object 540 and the original name for exemplary original content object 520) is different for each of exemplary original content object 520 and exemplary new content object 540.



FIG. 6 presents tables depicting a format of an encapsulated original manifest 610 and an exemplary encapsulated original manifest 620, in accordance with an embodiment of the present invention. Encapsulated original manifest 610 includes a new encapsulated manifest name 462 and a payload 614. Exemplary encapsulated original manifest 620 includes a new encapsulated original manifest name with a value of “/akamai/frozen/original-manifest” and a payload with a value equal to the original manifest (e.g., exemplary original manifest 460 as depicted in FIG. 4).


Use Case Based on Exemplary Manifests and Other Objects


The use case below is based on the exemplary tables presented and described in relation to FIGS. 4-6 and the methods disclosed herein. A content producer (e.g., Netflix) creates exemplary original manifest 460 that describes content objects associated with original names. The original names include an original content base name 424 and a final segment 430.1-430.n (e.g., “/netflix/frozen/content/c_1”). Original manifest 460 includes original authentication information which can indicate corresponding hash values for each content object (e.g., “hash(CO/netflix/frozen/content/c_1)”). Netflix, as the content producer, authenticates original manifest 460 by including its identity 434 and signature 436, “Netflix” and “Netflix_Sig,” respectively. A content publisher (e.g., Akamai) encapsulates original manifest 460 by creating exemplary encapsulated original manifest 620, with a new encapsulated original manifest name 462 of “/akamai/frozen/original-manifest.” Akamai renames the content objects with new names comprised of a new content base name 444 and a final segment 450.1-450.n (e.g., “/akamai/frozen/content/c_1”). Akamai creates exemplary new manifest 480 with a manifest name 442 of “/akamai/frozen/manifest” where new manifest 480 describes content objects by the new names and includes original authentication information from original manifest 460.


A consumer retrieves new manifest 480 under new manifest name 442 of “/akamai/frozen/manifest”, where new manifest 480 includes original authentication information 460. The consumer retrieves the content objects described in new manifest 480 (e.g., content objects under the new name of “/akamai/frozen/content/c_1”, etc.). The consumer then retrieves encapsulated original manifest 620 based on new encapsulated original manifest name 462 (e.g., “/akamai/frozen/original-manifest”) included in original authentication information 460. The consumer now has a copy of original manifest 460 and new manifest 480.


The consumer verifies original manifest 460 based on the original authentication information. For example, the consumer uses a regular signature verification based on a public key of identified original producer 434. The consumer then verifies the retrieved content objects described in new manifest 480. First, for each retrieved content object, the consumer replaces the new name that includes new content base name 444 and final segment 450.1 (e.g., “/akamai/frozen/content/c_1”) with the original name that includes original content base name 424 and final segment 430.1, as indicated in the original manifest (e.g., “/netflix/frozen/content/c_1”). Next, the consumer calculates the self-certifying name for the content object based on the original name as derived from the new name (e.g., “hash(CO/netflix/frozen/content/c_1)”). Finally, the consumer compares the calculated self-certifying name with the self-certifying name indicated in the original authentication information (e.g., original hash value 432.1 of “hash_1=hash(CO/netflix/frozen/content/c_1)”). A match authenticates the retrieved content object by confirming that the renamed content object contains the same data as the originally named content object. If there is no match, the retrieved content object is not authenticated and the system can discard or ignore the content object.


Exemplary Computer and Communication System



FIG. 7 illustrates an exemplary computer and communication system 702 that facilitates redistribution of content objects with a different name without requiring re-computation of the original authentication information, in accordance with an embodiment of the present invention. Computer and communication 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 and communication 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 732.


Content-processing system 718 can include instructions, which when executed by computer and communication system 702, can cause computer and communication system 702 to perform methods and/or processes described in this disclosure. Specifically, content-processing system 718 may include instructions for determining, by a content producing device, an original manifest which indicates at least an original name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level (communication mechanism 720). Content-processing system 718 can include instructions for renaming the content object with a new name (renaming mechanism 722). Content-processing system 718 can also include instructions for creating a new manifest which indicates the new name, where the new manifest includes original authentication information associated with the original manifest (manifest creation mechanism 724).


Content-processing system 718 can further include instructions for renaming the content object, which involves one or more of: adding a prefix to the original name; replacing a part of the original name with a part of the new name; and any function that creates a one-to-one mapping of the new name to the original name (renaming mechanism 722).


Content-processing system 718 can additionally include instructions for receiving, by a content consuming device, a new manifest which indicates at least a new name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level, and wherein the new manifest includes original authentication information associated with an original manifest which indicates an original name associated with the content object (communication mechanism 720). Content-processing system 718 can include instructions for retrieving the content object based on the new name (communication mechanism 720). Content-processing system 718 can include instructions for verifying the obtained content object by: replacing the new name with the original name; and authenticating the content object with the original name using the original authentication information (content verification mechanism 726). Content-processing system 718 can also include instructions for calculating a self-certifying name for the content object based on the original name (content verification mechanism 728), comparing the calculated self-certifying name with the self-certifying name indicated in the original authentication information (content verification mechanism 728), and, responsive to determining that the calculated self-certifying name matches the self-certifying name indicated in the original authentication information, authenticating the obtained content object (authentication mechanism 730).


Content-processing system 718 can include instructions for retrieving the original manifest, wherein the original authentication information indicates a self-certifying name based on the original name, and wherein the self-certifying name uniquely identifies the content object (communication mechanism 720). Content-processing system 718 can also include instructions for verifying the original manifest by authenticating a digital signature of a producer of the original manifest based on a public key of producer (manifest verification mechanism 726).


Data 732 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 732 can store at least: an original manifest which indicates at least an original name associated with a content object, wherein the name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level; a new manifest which indicates at least a new name associated with a content object; an original name; a new name; a content object associated with the original name; a content object associated with the new name; an encapsulated original manifest; an encapsulated original manifest name; a manifest name; a content base name; a content link item; a final segment name; original authentication information associated with the original manifest; an identity of a producer of the original manifest; a digital signature of the producer of the original manifest; a self-certifying name based on the original name, wherein the self-certifying name uniquely identifies the content object; a hash of the content object; and a calculated self-certifying name based on the original name as obtained from the original manifest.


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 or apparatus. The hardware modules or apparatus can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs), dedicated or shared processors that execute a particular software module or a piece of code at a particular time, and other programmable-logic devices now known or later developed. When the hardware modules or apparatus are activated, they perform the methods and processes included within them.


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 computer-implemented method for authenticating content, comprising: determining, by a content publishing device, an original manifest which includes an original manifest name and indicates at least an original content name associated with a content object, wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level;encapsulating the original manifest based on an encapsulation name for the original manifest;renaming the content object with a new content name; andcreating a new manifest which includes a new manifest name and indicates the new content name, wherein the new manifest further includes original authentication information associated with the original manifest, wherein the original authentication information includes the encapsulation name for the original manifest, thereby facilitating redistribution of content objects with a different name without requiring re-computation of the original authentication information.
  • 2. The method of claim 1, wherein the original authentication information indicates one or more of: an identity of a producer of the original manifest; anda digital signature of the producer of the original manifest.
  • 3. The method of claim 1, wherein the original authentication information is one or more of: information embedded in the new manifest;information derived from the original manifest; anda linked object that is derived from the original manifest, wherein the linked object is an object which is distinct from the original manifest.
  • 4. The method of claim 1, wherein renaming the content object involves one or more of: adding a prefix to the original content name;replacing a part of the original content name with a part of the new content name; andany function that creates a one-to-one mapping of the new content name to the original content name.
  • 5. The method of claim 1, wherein the original authentication information indicates a self-certifying name based on the original content name, wherein the self-certifying name uniquely identifies the content object.
  • 6. The method of claim 5, wherein the self-certifying name includes a cryptographic digest of the content object.
  • 7. The method of claim 1, wherein the new manifest indicates a self-certifying name based on the new content name, and wherein the self-certifying name uniquely identifies the content object.
  • 8. A computer-implemented method comprising: receiving, by a content consuming device, a new manifest which includes a new manifest name and indicates at least a new content name associated with a content object, wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level, wherein the new manifest further includes original authentication information associated with an original manifest which indicates an original content name associated with the content object, and wherein the original authentication information includes an encapsulation name for the original manifest;retrieving the content object based on the new content name;retrieving the original manifest based on the encapsulation name; andverifying the retrieved content object by: replacing the new content name with the original content name; andauthenticating the retrieved content object with the original content name based on the original authentication information from the retrieved original manifest, thereby facilitating redistribution of content objects with different names without requiring re-computation of the original authentication information.
  • 9. The method of claim 8, wherein the original authentication information indicates one or more of: an identity of a producer of the original manifest; anda digital signature of the producer of the original manifest.
  • 10. The method of claim 8, wherein the original authentication information is one or more of: information embedded in the new manifest;information derived from the original manifest; anda linked object that is derived from the original manifest, wherein the linked object is an object which is separate from the original manifest.
  • 11. The method of claim 8, wherein the original authentication information indicates a self-certifying name based on the original content name, and wherein the self-certifying name uniquely identifies the content object.
  • 12. The method of claim 8, further comprising: verifying the original manifest by authenticating a digital signature of a producer of the original manifest based on a public key of the producer.
  • 13. The method of claim 8, wherein verifying the retrieved content object further comprises: calculating a self-certifying name for the content object based on the original content name;comparing the calculated self-certifying name with a self-certifying name indicated in the original authentication information; andresponsive to determining that the calculated self-certifying name matches the self-certifying name indicated in the original authentication information, authenticating the retrieved content object.
  • 14. A computer system for authenticating content, the computer system comprising: a processor; anda storage device coupled to the processor and storing instructions that when executed by the processor cause the computer system to perform a method, the method comprising: determining, by a content publishing device, an original manifest which includes an original manifest name and indicates at least an original content name associated with a content object, wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level;encapsulating the original manifest based on an encapsulation name for the original manifest;renaming the content object with a new content name; andcreating a new manifest which includes a new manifest name and indicates the new content name, wherein the new manifest further includes original authentication information associated with the original manifest, wherein the original authentication information includes the encapsulation name for the original manifest, thereby facilitating redistribution of content objects with a different name without requiring re-computation of the original authentication information.
  • 15. The computer system of claim 14, wherein the original authentication information indicates one or more of: an identity of a producer of the original manifest; anda digital signature of the producer of the original manifest.
  • 16. The computer system of claim 14, wherein the original authentication information is one or more of: information embedded in the new manifest;information derived from the original manifest; anda linked object that is derived from the original manifest, wherein the linked object is an object which is distinct from the original manifest.
  • 17. The computer system of claim 14, wherein renaming the content object involves one or more of: adding a prefix to the original content name;replacing a part of the original content name with a part of the new content name; andany function that creates a one-to-one mapping of the new content name to the original content name.
  • 18. The computer system of claim 14, wherein the original authentication information indicates a self-certifying name based on the original content name, wherein the self-certifying name includes a cryptographic digest of the content object.
  • 19. The computer system of claim 14, wherein the new manifest indicates a self-certifying name based on the new content name, and wherein the self-certifying name uniquely identifies the content object.
  • 20. A computer system for authenticating content, the computer system comprising: a processor; anda storage device coupled to the processor and storing instructions that when executed by the processor cause the computer system to perform a method, the method comprising: receiving, by a content consuming device, a new manifest which includes a new manifest name and indicates at least a new content name associated with a content object, wherein a name is a hierarchically structured variable length identifier (HSVLI) which comprises contiguous name components ordered from a most general level to a most specific level, wherein the new manifest further includes original authentication information associated with an original manifest which indicates an original content name associated with the content object, and wherein the original authentication information includes an encapsulation name for the original manifest;retrieving the content object based on the new content name;retrieving the original manifest based on the encapsulation name; andverifying the retrieved content object by: replacing the new content name with the original content name; andauthenticating the retrieved content object with the original content name based on the original authentication information from the retrieved original manifest, thereby facilitating redistribution of content objects with different names without requiring re-computation of the original authentication information.
  • 21. The computer system of claim 20, wherein the original authentication information indicates one or more of: an identity of a producer of the original manifest; anda digital signature of the producer of the original manifest.
  • 22. The computer system of claim 20, wherein the original authentication information is one or more of: information embedded in the new manifest;information derived from the original manifest; anda linked object that is derived from the original manifest, wherein the linked object is an object which is separate from the original manifest.
  • 23. The computer system of claim 20, wherein the original authentication information indicates a self-certifying name based on the original content name, and wherein the self-certifying name uniquely identifies the content object.
  • 24. The computer system of claim 20, wherein the method further comprises: verifying the original manifest by authenticating a digital signature of a producer of the original manifest based on a public key of the producer.
  • 25. The computer system of claim 20, wherein verifying the retrieved content object further comprises: calculating a self-certifying name for the content object based on the original content name;comparing the calculated self-certifying name with a self-certifying name indicated in the original authentication information; andresponsive to determining that the calculated self-certifying name matches the self-certifying name indicated in the original authentication information, authenticating the retrieved content object.
US Referenced Citations (398)
Number Name Date Kind
817441 Niesz Apr 1906 A
4309569 Merkle Jan 1982 A
4921898 Lenney May 1990 A
5070134 Oyamada Dec 1991 A
5110856 Oyamada May 1992 A
5506844 Rao Apr 1996 A
5629370 Freidzon May 1997 A
5870605 Bracho Feb 1999 A
6052683 Irwin Apr 2000 A
6091724 Chandra Jul 2000 A
6173364 Zenchelsky Jan 2001 B1
6226618 Downs May 2001 B1
6233646 Hahm May 2001 B1
6332158 Risley Dec 2001 B1
6366988 Skiba Apr 2002 B1
6574377 Cahill Jun 2003 B1
6629150 Huded Sep 2003 B1
6654792 Verma Nov 2003 B1
6667957 Corson Dec 2003 B1
6681220 Kaplan Jan 2004 B1
6681326 Son Jan 2004 B2
6769066 Botros Jul 2004 B1
6772333 Brendel Aug 2004 B1
6862280 Bertagna Mar 2005 B1
6901452 Bertagna May 2005 B1
6917985 Madruga Jul 2005 B2
6968393 Chen Nov 2005 B1
6981029 Menditto Dec 2005 B1
7013389 Srivastava Mar 2006 B1
7031308 Garcia-Luna-Aceves Apr 2006 B2
7061877 Gummalla Jun 2006 B1
7206860 Murakami Apr 2007 B2
7257837 Xu Aug 2007 B2
7287275 Moskowitz Oct 2007 B2
7315541 Housel Jan 2008 B1
7339929 Zelig Mar 2008 B2
7350229 Lander Mar 2008 B1
7382787 Barnes Jun 2008 B1
7406597 Iyengar Jul 2008 B2
7444251 Nikovski Oct 2008 B2
7466703 Arunachalam Dec 2008 B1
7472422 Agbabian Dec 2008 B1
7496668 Hawkinson Feb 2009 B2
7509425 Rosenberg Mar 2009 B1
7523016 Surdulescu Apr 2009 B1
7543064 Juncker Jun 2009 B2
7552233 Raju Jun 2009 B2
7555482 Korkus Jun 2009 B2
7555563 Ott Jun 2009 B2
7567547 Mosko Jul 2009 B2
7567946 Andreoli Jul 2009 B2
7580971 Gollapudi Aug 2009 B1
7623535 Guichard Nov 2009 B2
7647507 Feng Jan 2010 B1
7660324 Oguchi Feb 2010 B2
7685290 Satapati Mar 2010 B2
7698463 Ogier Apr 2010 B2
7769887 Bhattacharyya Aug 2010 B1
7779467 Choi Aug 2010 B2
7801177 Luss Sep 2010 B2
7816441 Elizalde Oct 2010 B2
7831733 Sultan Nov 2010 B2
7908337 Garcia-Luna-Aceves Mar 2011 B2
7924837 Shabtay Apr 2011 B1
7953885 Devireddy May 2011 B1
7974221 Tamassia Jul 2011 B2
8000267 Solis Aug 2011 B2
8010691 Kollmansberger Aug 2011 B2
8074289 Carpentier Dec 2011 B1
8117441 Kurien Feb 2012 B2
8127134 Iyengar Feb 2012 B2
8160069 Jacobson Apr 2012 B2
8204060 Jacobson Jun 2012 B2
8214364 Bigus Jul 2012 B2
8224985 Takeda Jul 2012 B2
8225057 Zheng Jul 2012 B1
8271578 Sheffi Sep 2012 B2
8312064 Gauvin Nov 2012 B1
8386622 Jacobson Feb 2013 B2
8467297 Liu Jun 2013 B2
8553562 Allan Oct 2013 B2
8572049 Cheung Oct 2013 B2
8572214 Garcia-Luna-Aceves Oct 2013 B2
8645702 Zhang Feb 2014 B2
8654649 Vasseur Feb 2014 B2
8665757 Kling Mar 2014 B2
8667172 Ravindran Mar 2014 B2
8688619 Ezick Apr 2014 B1
8699350 Kumar Apr 2014 B1
8750820 Allan Jun 2014 B2
8761022 Chiabaut Jun 2014 B2
8762477 Xie Jun 2014 B2
8762570 Qian Jun 2014 B2
8762707 Killian Jun 2014 B2
8767627 Ezure Jul 2014 B2
8817594 Gero Aug 2014 B2
8826381 Kim Sep 2014 B2
8832302 Bradford Sep 2014 B1
8836536 Marwah Sep 2014 B2
8862774 Vasseur Oct 2014 B2
8869235 Qureshi Oct 2014 B2
8869298 Kamperman Oct 2014 B2
8886925 Qureshi Nov 2014 B2
8903756 Zhao Dec 2014 B2
8937865 Kumar Jan 2015 B1
9071498 Beser Jun 2015 B2
9112895 Lin Aug 2015 B1
20020010795 Brown Jan 2002 A1
20020048269 Hong Apr 2002 A1
20020054593 Morohashi May 2002 A1
20020077988 Sasaki Jun 2002 A1
20020078066 Robinson Jun 2002 A1
20020138551 Erickson Sep 2002 A1
20020176404 Girard Nov 2002 A1
20020188605 Adya Dec 2002 A1
20020199014 Yang Dec 2002 A1
20030009365 Tynan Jan 2003 A1
20030046437 Eytchison Mar 2003 A1
20030048793 Pochon Mar 2003 A1
20030051100 Patel Mar 2003 A1
20030074472 Lucco Apr 2003 A1
20030097447 Johnston May 2003 A1
20030140257 Paterka Jul 2003 A1
20040024879 Dingman Feb 2004 A1
20040030602 Rosenquist Feb 2004 A1
20040073715 Folkes Apr 2004 A1
20040139230 Kim Jul 2004 A1
20040221047 Grover Nov 2004 A1
20040225627 Botros Nov 2004 A1
20040252683 Kennedy Dec 2004 A1
20050003832 Osafune Jan 2005 A1
20050028156 Hammond Feb 2005 A1
20050038787 Cheung Feb 2005 A1
20050043060 Brandenberg Feb 2005 A1
20050050211 Kaul Mar 2005 A1
20050074001 Mattes Apr 2005 A1
20050149508 Deshpande Jul 2005 A1
20050159823 Hayes Jul 2005 A1
20050198351 Nog Sep 2005 A1
20050249196 Ansari Nov 2005 A1
20050259637 Chu Nov 2005 A1
20050262217 Nonaka Nov 2005 A1
20050289222 Sahim Dec 2005 A1
20060010249 Sabesan Jan 2006 A1
20060029102 Abe Feb 2006 A1
20060039379 Abe Feb 2006 A1
20060051055 Ohkawa Mar 2006 A1
20060072523 Richardson Apr 2006 A1
20060095763 Iyengar May 2006 A1
20060099973 Nair May 2006 A1
20060129514 Watanabe Jun 2006 A1
20060133343 Huang Jun 2006 A1
20060173831 Basso Aug 2006 A1
20060193295 White Aug 2006 A1
20060206445 Andreoli Sep 2006 A1
20060215684 Capone Sep 2006 A1
20060223504 Ishak Oct 2006 A1
20060256767 Suzuki Nov 2006 A1
20060268792 Belcea Nov 2006 A1
20070019619 Foster Jan 2007 A1
20070073888 Madhok Mar 2007 A1
20070094265 Korkus Apr 2007 A1
20070112880 Yang May 2007 A1
20070124412 Narayanaswami May 2007 A1
20070127457 Mirtorabi Jun 2007 A1
20070160062 Morishita Jul 2007 A1
20070162394 Zager Jul 2007 A1
20070189284 Kecskemeti Aug 2007 A1
20070195765 Heissenbuttel Aug 2007 A1
20070204011 Shaver Aug 2007 A1
20070209067 Fogel Sep 2007 A1
20070239892 Ott Oct 2007 A1
20070240207 Belakhdar Oct 2007 A1
20070245034 Retana Oct 2007 A1
20070253418 Shiri Nov 2007 A1
20070255699 Sreenivas Nov 2007 A1
20070255781 Li Nov 2007 A1
20070274504 Maes Nov 2007 A1
20070276907 Maes Nov 2007 A1
20070294187 Scherrer Dec 2007 A1
20080005056 Stelzig Jan 2008 A1
20080010366 Duggan Jan 2008 A1
20080037420 Tang Feb 2008 A1
20080043989 Furutono Feb 2008 A1
20080046340 Brown Feb 2008 A1
20080059631 Bergstrom Mar 2008 A1
20080080440 Yarvis Apr 2008 A1
20080101357 Iovanna May 2008 A1
20080107034 Jetcheva May 2008 A1
20080123862 Rowley May 2008 A1
20080133583 Artan Jun 2008 A1
20080133755 Pollack Jun 2008 A1
20080151755 Nishioka Jun 2008 A1
20080159271 Kutt Jul 2008 A1
20080186901 Itagaki Aug 2008 A1
20080200153 Fitzpatrick Aug 2008 A1
20080215669 Gaddy Sep 2008 A1
20080216086 Tanaka Sep 2008 A1
20080243992 Jardetzky Oct 2008 A1
20080256359 Kahn Oct 2008 A1
20080270618 Rosenberg Oct 2008 A1
20080271143 Stephens Oct 2008 A1
20080287142 Keighran Nov 2008 A1
20080288580 Wang Nov 2008 A1
20080320148 Capuozzo Dec 2008 A1
20090006659 Collins Jan 2009 A1
20090013324 Gobara Jan 2009 A1
20090019520 Iyengar Jan 2009 A1
20090022154 Kiribe Jan 2009 A1
20090024641 Quigley Jan 2009 A1
20090030978 Johnson Jan 2009 A1
20090037763 Adhya Feb 2009 A1
20090052660 Chen Feb 2009 A1
20090067429 Nagai Mar 2009 A1
20090077184 Brewer Mar 2009 A1
20090092043 Lapuh Apr 2009 A1
20090097631 Gisby Apr 2009 A1
20090103515 Pointer Apr 2009 A1
20090113068 Fujihira Apr 2009 A1
20090144300 Chatley Jun 2009 A1
20090157887 Froment Jun 2009 A1
20090185745 Momosaki Jul 2009 A1
20090193101 Munetsugu Jul 2009 A1
20090222344 Greene Sep 2009 A1
20090228593 Takeda Sep 2009 A1
20090254572 Redlich Oct 2009 A1
20090268905 Matsushima Oct 2009 A1
20090285209 Stewart Nov 2009 A1
20090287835 Jacobson Nov 2009 A1
20090288163 Jacobson Nov 2009 A1
20090292743 Bigus Nov 2009 A1
20090293121 Bigus Nov 2009 A1
20090300079 Shitomi Dec 2009 A1
20090300407 Kamath Dec 2009 A1
20090307333 Welingkar Dec 2009 A1
20090323632 Nix Dec 2009 A1
20100005061 Basco Jan 2010 A1
20100027539 Beverly Feb 2010 A1
20100046546 Ram Feb 2010 A1
20100057929 Merat Mar 2010 A1
20100088370 Wu Apr 2010 A1
20100094767 Miltonberger Apr 2010 A1
20100098093 Ejzak Apr 2010 A1
20100100465 Cooke Apr 2010 A1
20100103870 Garcia-Luna-Aceves Apr 2010 A1
20100110935 Tamassia May 2010 A1
20100124191 Vos May 2010 A1
20100125911 Bhaskaran May 2010 A1
20100131660 Dec May 2010 A1
20100150155 Napierala Jun 2010 A1
20100165976 Khan Jul 2010 A1
20100169478 Saha Jul 2010 A1
20100169503 Kollmansberger Jul 2010 A1
20100178033 Kamperman Jul 2010 A1
20100180332 Ben-Yochanan Jul 2010 A1
20100182995 Hwang Jul 2010 A1
20100185753 Liu Jul 2010 A1
20100195653 Jacobson Aug 2010 A1
20100195654 Jacobson Aug 2010 A1
20100195655 Jacobson Aug 2010 A1
20100217874 Anantharaman Aug 2010 A1
20100232402 Przybysz Sep 2010 A1
20100232439 Dham Sep 2010 A1
20100235516 Nakamura Sep 2010 A1
20100246549 Zhang Sep 2010 A1
20100250497 Redlich Sep 2010 A1
20100250939 Adams Sep 2010 A1
20100268782 Zombek Oct 2010 A1
20100272107 Papp Oct 2010 A1
20100284309 Allan Nov 2010 A1
20100284404 Gopinath Nov 2010 A1
20100293293 Beser Nov 2010 A1
20100322249 Thathapudi Dec 2010 A1
20110013637 Xue Jan 2011 A1
20110022812 vanderLinden Jan 2011 A1
20110055392 Shen Mar 2011 A1
20110055921 Narayanaswamy Mar 2011 A1
20110090908 Jacobson Apr 2011 A1
20110106755 Hao May 2011 A1
20110145597 Yamaguchi Jun 2011 A1
20110145858 Philpott Jun 2011 A1
20110153840 Narayana Jun 2011 A1
20110161408 Kim Jun 2011 A1
20110202609 Chaturvedi Aug 2011 A1
20110231578 Nagappan Sep 2011 A1
20110239256 Gholmieh Sep 2011 A1
20110258049 Ramer Oct 2011 A1
20110264824 Venkata Subramanian Oct 2011 A1
20110265174 Thornton Oct 2011 A1
20110271007 Wang Nov 2011 A1
20110286457 Ee Nov 2011 A1
20110286459 Rembarz Nov 2011 A1
20110295783 Zhao Dec 2011 A1
20110299454 Krishnaswamy Dec 2011 A1
20120011170 Elad Jan 2012 A1
20120011551 Levy Jan 2012 A1
20120036180 Thornton Feb 2012 A1
20120047361 Erdmann Feb 2012 A1
20120066727 Nozoe Mar 2012 A1
20120106339 Mishra May 2012 A1
20120114313 Phillips May 2012 A1
20120120803 Farkas May 2012 A1
20120136676 Goodall May 2012 A1
20120136936 Quintuna May 2012 A1
20120136945 Lee May 2012 A1
20120137367 Dupont May 2012 A1
20120141093 Yamaguchi Jun 2012 A1
20120155464 Kim Jun 2012 A1
20120158973 Jacobson Jun 2012 A1
20120163373 Lo Jun 2012 A1
20120166806 Zhang Jun 2012 A1
20120179653 Araki Jul 2012 A1
20120197690 Agulnek Aug 2012 A1
20120198048 Ioffe Aug 2012 A1
20120221150 Arensmeier Aug 2012 A1
20120224487 Hui Sep 2012 A1
20120257500 Lynch Oct 2012 A1
20120284791 Miller Nov 2012 A1
20120290669 Parks Nov 2012 A1
20120290919 Melnyk Nov 2012 A1
20120291102 Cohen Nov 2012 A1
20120314580 Hong Dec 2012 A1
20120317307 Ravindran Dec 2012 A1
20120331112 Chatani Dec 2012 A1
20130041982 Shi Feb 2013 A1
20130051392 Filsfils Feb 2013 A1
20130060962 Wang Mar 2013 A1
20130073552 Rangwala Mar 2013 A1
20130074155 Huh Mar 2013 A1
20130091539 Khurana Apr 2013 A1
20130110987 Kim May 2013 A1
20130111063 Lee May 2013 A1
20130151584 Westphal Jun 2013 A1
20130163426 Beliveau Jun 2013 A1
20130166668 Byun Jun 2013 A1
20130173822 Hong Jul 2013 A1
20130182568 Lee Jul 2013 A1
20130185406 Choi Jul 2013 A1
20130197698 Shah Aug 2013 A1
20130198119 Eberhardt, III Aug 2013 A1
20130219038 Lee Aug 2013 A1
20130219081 Qian Aug 2013 A1
20130219478 Mahamuni Aug 2013 A1
20130223237 Hui Aug 2013 A1
20130227166 Ravindran Aug 2013 A1
20130242996 Varvello Sep 2013 A1
20130250809 Hui Sep 2013 A1
20130282854 Jang Oct 2013 A1
20130282860 Zhang Oct 2013 A1
20130282920 Zhang Oct 2013 A1
20130304937 Lee Nov 2013 A1
20130329696 Xu Dec 2013 A1
20130336323 Srinivasan Dec 2013 A1
20130343408 Cook Dec 2013 A1
20140003232 Guichard Jan 2014 A1
20140006565 Muscariello Jan 2014 A1
20140029445 Hui Jan 2014 A1
20140032714 Liu Jan 2014 A1
20140040505 Barton Feb 2014 A1
20140074730 Arensmeier Mar 2014 A1
20140075567 Raleigh Mar 2014 A1
20140082135 Jung Mar 2014 A1
20140089454 Jeon Mar 2014 A1
20140096249 Dupont Apr 2014 A1
20140129736 Yu May 2014 A1
20140136814 Stark May 2014 A1
20140140348 Perlman May 2014 A1
20140143370 Vilenski May 2014 A1
20140146819 Bae May 2014 A1
20140149733 Kim May 2014 A1
20140156396 deKozan Jun 2014 A1
20140165207 Engel Jun 2014 A1
20140172783 Suzuki Jun 2014 A1
20140172981 Kim Jun 2014 A1
20140173034 Liu Jun 2014 A1
20140192717 Liu Jul 2014 A1
20140195328 Ferens Jul 2014 A1
20140195666 Dumitriu Jul 2014 A1
20140233575 Xie Aug 2014 A1
20140237085 Park Aug 2014 A1
20140280823 Varvello Sep 2014 A1
20140281489 Peterka Sep 2014 A1
20140281505 Zhang Sep 2014 A1
20140282816 Xie Sep 2014 A1
20140289325 Solis Sep 2014 A1
20140289790 Wilson Sep 2014 A1
20140314093 You Oct 2014 A1
20140365550 Jang Dec 2014 A1
20150006896 Franck Jan 2015 A1
20150018770 Baran Jan 2015 A1
20150032892 Narayanan Jan 2015 A1
20150063802 Bahadur Mar 2015 A1
20150095481 Ohnishi Apr 2015 A1
20150095514 Yu Apr 2015 A1
20150188770 Naiksatam Jul 2015 A1
20150347553 Aizman Dec 2015 A1
20160205190 Bestler Jul 2016 A1
20160224638 Bestler Aug 2016 A1
Foreign Referenced Citations (15)
Number Date Country
1720277 Jun 1967 DE
19620817 Nov 1997 DE
0295727 Dec 1988 EP
0757065 Jul 1996 EP
1077422 Feb 2001 EP
1384729 Jan 2004 EP
2124415 Nov 2009 EP
2214357 Aug 2010 EP
03005288 Jan 2003 WO
03042254 May 2003 WO
03049369 Jun 2003 WO
03091297 Nov 2003 WO
2007113180 Oct 2007 WO
2007144388 Dec 2007 WO
2011049890 Apr 2011 WO
Non-Patent Literature Citations (150)
Entry
Jacobson, V. et al., “Networking Named Content”, CoNEXT'09 Dec. 1-4, 2009, Rome, Italy. ACM 2009.
Baugher, M. et al., “Self-Verifying Names for Read-Only Named Data”, INFOCOM Workshops, vol. 12, 2012.
Xie et al. “Collaborative Forwarding and Caching in Content Centric Networks”, Networking 2012.
Jacobson, Van et al., “Content-Centric Networking, Whitepaper Describing Future Assurable Global Networks”, Palo Alto Research Center, Inc., Jan. 30, 2007, pp. 1-9.
Koponen, Teemu et al., “A Data-Oriented (and Beyond) Network Architecture”, SIGCOMM '07, Aug. 27-31, 2007, Kyoto, Japan, XP-002579021, p. 181-192.
Jacobson, Van et al. ‘VoCCN: Voice Over Content-Centric Networks.’ Dec. 1, 2009. ACM ReArch'09.
Rosenberg, J. “Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols”, Apr. 2010, pp. 1-117.
Shih, Eugene et al., ‘Wake on Wireless: An Event Driven Energy Saving Strategy for Battery Operated Devices’, Sep. 23, 2002, pp. 160-171.
Fall, K. et al., “DTN: an architectural retrospective”, Selected areas in communications, IEEE Journal on, vol. 28, No. 5, Jun. 1, 2008, pp. 828-835.
Gritter, M. et al., ‘An Architecture for content routing support in the Internet’, Proceedings of 3rd Usenix Symposium on Internet Technologies and Systems, 2001, pp. 37-48.
“CCNx,” http://ccnx.org/. downloaded Mar. 11, 2015.
“Content Delivery Network”, Wikipedia, Dec. 10, 2011, http://en.wikipedia.org/w/index.php?title=Content—delivery—network&oldid=465077460.
“Digital Signature” archived on Aug. 31, 2009 at http://web.archive.org/web/20090831170721/http://en.wikipedia.org/wiki/Digital—signature.
Heinemeier, Kristin, et al. “Uncertainties in Achieving Energy Savings from HVAC Maintenance Measures in the Field.” ASHRAE Transactions 118.Part 2 {2012).
Herlich, Matthias et al., “Optimizing Energy Efficiency for Bulk Transfer Networks”, Apr. 13, 2010, pp. 1-3, retrieved for the Internet: URL:http://www.cs.uni-paderborn.de/fileadmin/informationik/ag-karl/publications/miscellaneous/optimizing.pdf (retrieved on Mar. 9, 2012).
Hoque et al., ‘NLSR: Named-data Link State Routing Protocol’, Aug. 12, 2013, ICN 2013, pp. 15-20.
https://code.google.com/p/ccnx-trace/.
I. Psaras, R.G. Clegg, R. Landa, W.K. Chai, and G. Pavlou, “Modelling and evaluation of CCN-caching trees,” in Proc. IFIP Networking 2011, Valencia, Spain, May 2011, pp. 78-91.
Intanagonwiwat, Chalermek, Ramesh Govindan, and Deborah Estrin. ‘Directed diffusion: a scalable and robust communication paradigm for sensor networks.’ Proceedings of the 6th annual international conference on Mobile computing and networking. ACM, 2000.
J. Aumasson and D. Bernstein, “SipHash: a fast short-input PRF”, Sep. 18, 2012.
J. Bethencourt, A, Sahai, and B. Waters, ‘Ciphertext-policy attribute-based encryption,’ in Proc. IEEE Security & Privacy 2007, Berkeley, CA, USA, May 2007, pp. 321-334.
J. Hur, “Improving security and efficiency in attribute-based data sharing,” IEEE Trans. Knowledge Data Eng., vol. 25, No. 10, pp. 2271-2282, Oct. 2013.
J. Shao and Z. Cao. CCA-Secure Proxy Re-Encryption without Pairings. Public Key Cryptography. Springer Lecture Notes in Computer Sciencevol. 5443 (2009).
V. Jacobson et al., ‘Networking Named Content,’ Proc. IEEE CoNEXT '09, Dec. 2009.
Jacobson et al., “Custodian-Based Information Sharing,” Jul. 2012, IEEE Communications Magazine: vol. 50 Issue 7 (p. 3843).
Ji, Kun, et al. “Prognostics enabled resilient control for model-based building automation systems.” Proceedings of the 12th Conference of International Building Performance Simulation Association. 2011.
K. Liang, L. Fang, W. Susilo, and D.S. Wong, “A Ciphertext-policy attribute-based proxy re-encryption with chosen-ciphertext security,” in Proc. INCoS 2013, Xian, China, Sep. 2013, pp. 552-559.
Katipamula, Srinivas, and Michael R. Brambley. “Review article: methods for fault detection, diagnostics, and prognostics for building systemsa review, Part I.” HVAC&R Research 11.1 (2005): 3-25.
Katipamula, Srinivas, and Michael R. Brambley. “Review article: methods for fault detection, diagnostics, and prognostics for building systemsa review, Part II.” HVAC&R Research 11.2 (2005): 169-187.
L. Wang et al., ‘OSPFN: An OSPF Based Routing Protocol for Named Data Networking,’ Technical Report NDN-0003, 2012.
L. Zhou, V. Varadharajan, and M. Hitchens, “Achieving secure role-based access control on encrypted data in cloud storage,” IEEE Trans. Inf. Forensics Security, vol. 8, No. 12, pp. 1947-1960, Dec. 2013.
Li, Wenjia, Anupam Joshi, and Tim Finin. “Coping with node misbehaviors in ad hoc networks: A multi-dimensional trust management approach.” Mobile Data Management (MDM), 2010 Eleventh International Conference on. IEEE, 2010.
Lopez, Javier, et al. “Trust management systems for wireless sensor networks: Best practices.” Computer Communications 33.9 (2010): 1086-1093.
M. Blaze, G. Bleumer, and M. Strauss, ‘Divertible protocols and atomic prosy cryptography,’ in Proc. Eurocrypt 1998, Espoo, Finland, May-Jun. 1998, pp. 127-144.
M. Green and G. Ateniese, “Identity-based proxy re-encryption,” in Proc. ACNS 2007, Zhuhai, China, Jun. 2007, pp. 288-306.
M. Ion, J. Zhang, and E.M. Schooler, “Toward content-centric privacy in ICN: Attribute-based encryption and routing,” in Proc. ACM SIGCOMM ICN 2013, Hong Kong, China, Aug. 2013, pp. 39-40.
M. Naor and B. Pinkas “Efficient trace and revoke schemes,” in Proc. FC 2000, Anguilla, British West Indies, Feb. 2000, pp. 1-20.
M. Nystrom, S. Parkinson, A. Rusch, and M. Scott, “PKCS#12: Personal information exchange syntax v. 1.1,” IETF RFC 7292, K. Moriarty, Ed., Jul. 2014.
M. Parsa and J.J. Garcia-Luna-Aceves, “A Protocol for Scalable Loop-free Multicast Routing.” IEEE JSAC, Apr. 1997.
M. Walfish, H. Balakrishnan, and S. Shenker, “Untangling the web from DNS,” in Proc. USENIX NSDI 2004, Oct. 2010, pp. 735-737.
Mahadevan, Priya, et al. “Orbis: rescaling degree correlations to generate annotated internet topologies.” ACM SIGCOMM Computer Communication Review. vol. 37. No. 4. ACM, 2007.
Mahadevan, Priya, et al. “Systematic topology analysis and generation using degree correlations.” ACM SIGCOMM Computer Communication Review. vol. 36. No. 4. ACM, 2006.
Matocha, Jeff, and Tracy Camp. ‘A taxonomy of distributed termination detection algorithms.’ Journal of Systems and Software 43.3 (1998): 207-221.
Matteo Varvello et al., “Caesar: A Content Router for High Speed Forwarding”, ICN 2012, Second Edition on Information-Centric Networking, New York, Aug. 2012.
McWilliams, Jennifer A., and Iain S. Walker. “Home Energy Article: A Systems Approach to Retrofitting Residential HVAC Systems.” Lawrence Berkeley National Laboratory (2005).
Merindol et al., “An efficient algorithm to enable path diversity in link state routing networks”, Jan. 10, Computer Networks 55 (2011), pp. 1132-1140.
Mobility First Project [online], http://mobilityfirst.winlab.rutgers.edu/, Downloaded Mar. 9, 2015.
Narasimhan, Sriram, and Lee Brownston. “HyDE-A General Framework for Stochastic and Hybrid Modelbased Diagnosis.” Proc. DX 7 (2007): 162-169.
NDN Project [online], http://www.named-data.net/, Downloaded Mar. 9, 2015.
Omar, Mawloud, Yacine Challal, and Abdelmadjid Bouabdallah. “Certification-based trust models in mobile ad hoc networks: A survey and taxonomy.” Journal of Network and Computer Applications 35.1 (2012): 268-286.
P. Mahadevan, E.Uzun, S. Sevilla, and J. Garcia-Luna-Aceves, “CCN-krs: A key resolution service for ccn,” in Proceedings of the 1st International Conference on Information-centric Networking, Ser. INC 14 New York, NY, USA: ACM, 2014, pp. 97-106. [Online]. Available: http://doi.acm.org/10.1145/2660129.2660154.
R. H. Deng, J. Weng, S. Liu, and K. Chen. Chosen-Ciphertext Secure Proxy Re-Encryption without Pairings. CANS. Spring Lecture Notes in Computer Science vol. 5339 (2008).
S. Chow, J. Weng, Y. Yang, and R. Deng. Efficient Unidirectional Proxy Re-Encryption. Progress in Cryptology—AFRICACRYPT 2010. Springer Berlin Heidelberg (2010).
S. Deering, “Multicast Routing in Internetworks and Extended LANs,” Proc. ACM SIGCOMM '88, Aug. 1988.
S. Deering et al., “The PIM architecture for wide-area multicast routing,” IEEE/ACM Trans, on Networking, vol. 4, No. 2, Apr. 1996.
S. Jahid, P. Mittal, and N. Borisov, “EASiER: Encryption-based access control in social network with efficient revocation,” in Proc. ACM ASIACCS 2011, Hong Kong, China, Mar. 2011, pp. 411-415.
S. Kamara and K. Lauter, “Cryptographic cloud storage,” in Proc. FC 2010, Tenerife, Canary Islands, Spain, Jan. 2010, pp. 136-149.
S. Kumar et al. “Peacock Hashing: Deterministic and Updatable Hashing for High Performance Networking,” 2008, pp. 556-564.
S. Misra, R. Tourani, and N.E. Majd, “Secure content delivery in information-centric networks: Design, implementation, and analyses,” in Proc. ACM SIGCOMM ICN 2013, Hong Kong, China, Aug. 2013, pp. 73-78.
S. Yu, C. Wang, K. Ren, and W. Lou, “Achieving secure, scalable, and fine-grained data access control in cloud computing,” in Proc. IEEE INFOCOM 2010, San Diego, CA, USA, Mar. 2010, pp. 1-9.
S.J. Lee, M. Gerla, and C. Chiang, “On-demand Multicast Routing Protocol in Multihop Wireless Mobile Networks,” Mobile Networks and Applications, vol. 7, No. 6, 2002.
Sandvine, Global Internet Phenomena Report—Spring 2012. Located online at http://www.sandvine.com/downloads/ documents/Phenomenal H 2012/Sandvine Global Internet Phenomena Report 1H 2012.pdf.
Scalable and Adaptive Internet Solutions (SAIL) Project [online], http://sail-project.eu/ Downloaded Mar. 9, 2015.
Schein, Jeffrey, and Steven T. Bushby. A Simulation Study of a Hierarchical, Rule-Based Method for System-Level Fault Detection and Diagnostics in HVAC Systems. US Department of Commerce,[Technology Administration], National Institute of Standards and Technology, 2005.
Shani, Guy, Joelle Pineau, and Robert Kaplow. “A survey of point-based POMDP solvers.” Autonomous Agents and Multi-Agent Systems 27.1 (2013): 1-51.
Sheppard, John W., and Stephyn GW Butcher. “A formal analysis of fault diagnosis with d-matrices.” Journal of Electronic Testing 23.4 (2007): 309-322.
Shneyderman, Alex et al., ‘Mobile VPN: Delivering Advanced Services in Next Generation Wireless Systems’, Jan. 1, 2003, pp. 3-29.
Solis, Ignacio, and J. J. Garcia-Luna-Aceves. ‘Robust content dissemination in disrupted environments.’ proceedings of the third ACM workshop on Challenged networks. ACM, 2008.
Sun, Ying, and Daniel S. Weld. “A framework for model-based repair.” AAAI. 1993.
T. Ballardie, P. Francis, and J. Crowcroft, “Core Based Trees (CBT),” Proc. ACM SIGCOMM '88, Aug. 1988.
T. Dierts, “The transport layer security (TLS) protocol version 1.2,” IETF RFC 5246, 2008.
T. Koponen, M. Chawla, B.-G. Chun, A. Ermolinskiy, K.H. Kim, S. Shenker, and I. Stoica, ‘A data-oriented (and beyond) network architecture,’ ACM SIGCOMM Computer Communication Review, vol. 37, No. 4, pp. 181-192, Oct. 2007.
The Despotify Project (2012). Available online at http://despotify.sourceforge.net/.
V. Goyal, 0. Pandey, A. Sahai, and B. Waters, “Attribute-based encryption for fine-grained access control of encrypted data,” in Proc. ACM CCS 2006, Alexandria, VA, USA, Oct.-Nov. 2006, pp. 89-98.
V. Jacobson, D.K. Smetters, J.D. Thornton, M.F. Plass, N.H. Briggs, and R.L. Braynard, ‘Networking named content,’ in Proc. ACM CoNEXT 2009, Rome, Italy, Dec. 2009, pp. 1-12.
V. K. Adhikari, S. Jain, Y. Chen, and Z.-L. Zhang. Vivisecting Youtube:An Active Measurement Study. In INFOCOM12 Mini-conference (2012).
Verma, Vandi, Joquin Fernandez, and Reid Simmons. “Probabilistic models for monitoring and fault diagnosis.” The Second IARP and IEEE/RAS Joint Workshop on Technical Challenges for Dependable Robots in Human Environments. Ed. Raja Chatila. Oct. 2002.
Vijay Kumar Adhikari, Yang Guo, Fang Hao, Matteo Varvello, Volker Hilt, Moritz Steiner, and Zhi-Li Zhang. Unreeling Netflix: Understanding and Improving Multi-CDN Movie Delivery. In the Proceedings of IEEE INFOCOM 2012 (2012).
Vutukury, Srinivas, and J. J. Garcia-Luna-Aceves. A simple approximation to minimum-delay routing. vol. 29. No. 4. ACM, 1999.
W.-G. Tzeng and Z.-J. Tzeng, “A public-key traitor tracing scheme with revocation using dynamic shares,” in Proc. PKC 2001, Cheju Island, Korea, Feb. 2001, pp. 207-224.
Waldvogel, Marcel “Fast Longest Prefix Matching: Algorithms, Analysis, and Applications”, A dissertation submitted to the Swiss Federal Institute of Technology Zurich, 2002.
Walker, Iain S. Best practices guide for residential HVAC Retrofits. No. LBNL-53592. Ernest Orlando Lawrence Berkeley National Laboratory, Berkeley, CA (US), 2003.
Wang, Jiangzhe et al., “DMND: Collecting Data from Mobiles Using Named Data”, Vehicular Networking Conference, 2010 IEEE, pp. 49-56.
Xylomenos, George, et al. “A survey of information-centric networking research.” Communications Surveys & Tutorials, IEEE 16.2 (2014): 1024-1049.
Yi, Cheng, et al. ‘A case for stateful forwarding plane.’ Computer Communications 36.7 (2013): 779-791.
Yi, Cheng, et al. ‘Adaptive forwarding in named data networking.’ ACM SIGCOMM computer communication review 42.3 (2012): 62-67.
Zahariadis, Theodore, et al. “Trust management in wireless sensor networks.” European Transactions on Telecommunications 21.4 (2010): 386-395.
Zhang, et al., “Named Data Networking (NDN) Project”, http://www.parc.com/publication/2709/named-data-networking-ndn-project.html, Oct. 2010, NDN-0001, PARC Tech Report.
Zhang, Lixia, et al. ‘Named data networking.’ ACM SIGCOMM Computer Communication Review 44.3 {2014): 66-73.
Soh et al., “Efficient Prefix Updates for IP Router Using Lexicographic Ordering and Updateable Address Set”, Jan. 2008, IEEE Transactions on Computers, vol. 57, No. 1.
Beben et al., “Content Aware Network based on Virtual Infrastructure”, 2012 13th ACIS International Conference on Software Engineering.
Biradar et al., “Review of multicast routing mechanisms in mobile ad hoc networks”, Aug. 16, Journal of Network$.
D. Trossen and G. Parisis, “Designing and realizing and information-centric internet,” IEEE Communications Magazing, vol. 50, No. 7, pp. 60-67, Jul. 2012.
Garcia-Luna-Aceves et al., “Automatic Routing Using Multiple Prefix Labels”, 2012, IEEE, Ad Hoc and Sensor Networking Symposium.
Gasti, Paolo et al., ‘DoS & DDoS in Named Data Networking’, 2013 22nd International Conference on Computer Communications and Networks (ICCCN), Aug. 2013, pp. 1-7.
Ishiyama, “On the Effectiveness of Diffusive Content Caching in Content-Centric Networking”, Nov. 5, 2012, IEEE, Information and Telecommunication Technologies (APSITT), 2012 9th Asia-Pacific Symposium.
J. Hur and D.K. Noh, “Attribute-based access control with efficient revocation in data outsourcing systers,” IEEE Trans. Parallel Distrib. Syst, vol. 22, No. 7, pp. 1214-1221, Jul. 2011.
J. Lotspiech, S. Nusser, and F. Pestoni. Anonymous Trust: Digital Rights Management using Broadcast Encryption. Proceedings of the IEEE 92.6 (2004).
Kaya et al., “A Low Power Lookup Technique for Multi-Hashing Network Applications”, 2006 IEEE Computer Society Annual Symposium on Emerging VLSI Technologies and Architectures, Mar. 2006.
S. Kamara and K. Lauter. Cryptographic Cloud Storage. Financial Cryptography and Data Security. Springer Berlin Heidelberg (2010).
RTMP (2009). Available online at http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/rtmp/ pdf/rtmp specification 1.0.pdf.
Hoque et al., “NLSR: Named-data Link State Routing Protocol”, Aug. 12, 2013, ICN'13.
Nadeem Javaid, “Analysis and design of quality link metrics for routing protocols in Wireless Networks”, PhD Thesis Defense, Dec. 15, 2010, Universete Paris-Est.
Wetherall, David, “Active Network vision and reality: Lessons form a capsule-based system”, ACM Symposium on Operating Systems Principles, Dec. 1, 1999. pp. 64-79.
Kulkarni A.B. et al., “Implementation of a prototype active network”, IEEE, Open Architectures and Network Programming, Apr. 3, 1998, pp. 130-142.
“Introducing JSON,” http://www.json.org/. downloaded Mar. 11, 2015.
“Microsoft PlayReady,” http://www.microsoft.com/playready/.downloaded Mar. 11, 2015.
“Pursuing a pub/sub internet (PURSUIT),” http://www.fp7-pursuit.ew/PursuitWeb/. downloaded Mar. 11, 2015.
“The FP7 4WARD project,” http://www.4ward-project.eu/. downloaded Mar. 11, 2015.
A. Broder and A. Karlin, “Multilevel Adaptive Hashing”, Jan. 1990, pp. 43-53.
Detti, Andrea, et al. “CONET: a content centric inter-networking architecture.” Proceedings of the ACM SIGCOMM workshop on Information-centric networking. ACM, 2011.
A. Wolman, M. Voelker, N. Sharma N. Cardwell, A. Karlin, and H.M. Levy, “On the scale and performance of cooperative web proxy caching,” ACM SIGHOPS Operating Systems Review, vol. 33, No. 5, pp. 16-31, Dec. 1999.
Afanasyev, Alexander, et al. “Interest flooding attack and countermeasures in Named Data Networking.” IFIP Networking Conference, 2013. IEEE, 2013.
Ao-Jan Su, David R. Choffnes, Aleksandar Kuzmanovic, and Fabian E. Bustamante. Drafting Behind Akamai: Inferring Network Conditions Based on CDN Redirections. IEEE/ACM Transactions on Networking {Feb. 2009).
B. Ahlgren et al., ‘A Survey of Information-centric Networking’ IEEE Commun. Magazine, Jul. 2012, pp. 26-36.
B. Lynn, “The Pairing-Based Cryptography Library”, <http://crypto.stanford.edu/pbc/>, retrieved Apr. 27, 2015.
Bari, MdFaizul, et al. ‘A survey of naming and routing in information-centric networks.’ Communications Magazine, IEEE 50.12 (2012): 44-53.
Baugher, Mark et al., “Self-Verifying Names for Read-Only Named Data”, 2012 IEEE Conference on Computer Communications Workshops (INFOCOM WKSHPS), Mar. 2012, pp. 274-279.
Brambley, Michael, A novel, low-cost, reduced-sensor approach for providing smart remote monitoring and diagnostics for packaged air conditioners and heat pumps. Pacific Northwest National Laboratory, 2009.
C. Gentry and A. Silverberg. Hierarchical ID-Based Cryptography. Advances in Cryptology—ASIACRYPT 2002. Springer Berlin Heidelberg (2002).
C.A. Wood and E. Uzun, “Flexible end-to-end content security in CCN,” in Proc. IEEE CCNC 2014, Las Vegas, CA, USA, Jan. 2014.
Carzaniga, Antonio, Matthew J. Rutherford, and Alexander L. Wolf. ‘A routing scheme for content-based networking.’ INFOCOM 2004, Twenty-third Annual Joint Conference of the IEEE Computer and Communications Societies. vol. 2. IEEE, 2004.
Cho, Jin-Hee, Ananthram Swami, and Ray Chen. “A survey on trust management for mobile ad hoc networks.” Communications Surveys & Tutorials, IEEE 13.4 (2011): 562-583.
Compagno, Alberto, et al. “Poseidon: Mitigating interest flooding DDoS attacks in named data networking.” Local Computer Networks (LCN), 2013 IEEE 38th Conference on. IEEE, 2013.
Conner, William, et al. “A trust management framework for service-oriented environments.” Proceedings of the 18th international conference on World wide web. ACM, 2009.
Content Centric Networking Project (CCN) [online], http://ccnx.org/releases/latest/doc/technical/, Downloaded Mar. 9, 2015.
Content Mediator Architecture for Content-aware Networks (COMET) Project [online], http://www.comet-project.org/, Downloaded Mar. 9, 2015.
D. Boneh, C. Gentry, and B. Waters, “Collusion Resistant Broadcast Encryption With Short Ciphertexts and Private Keys”, Annual International Cryptology Conference (pp. 258-275), Springer Berlin Heidelberg, 2005.
D. Boneh and M. Franklin. Identity-Based Encryption from the Weil Pairing. Advances in Cryptology—CRYPTO 2001, vol. 2139, Springer Berlin Heidelberg (2001).
D.K. Smetters, P. Golle, and J.D. Thornton, “CCNx access control specifications,” PARC, Tech. Rep., Jul. 2010.
Dabirmoghaddam, Ali, Maziar Mirzazad Barijough, and J. J. Garcia-Luna-Aceves. ‘Understanding optimal caching and opportunistic caching at the edge of information-centric networks,’ Proceedings of the 1st international conference on Information-centric networking. ACM, 2014.
Detti et al., “Supporting the Web with an information centric network that routes by name”, Aug. 2012, Computer Networks 56, pp. 3705-3702.
Dijkstra, Edsger W., and Carel S. Scholten. ‘Termination detection for diffusing computations.’ Information Processing Letters 11.1 (1980): 1-4.
Dijkstra, Edsger W., Wim HJ Feijen, and A—J M. Van Gasteren. “Derivation of a termination detection algorithm for distributed computations.” Control Flow and Data Flow: concepts of distributed programming. Springer Berlin Heidelberg, 1986. 507-512.
E. Rescorla and N. Modadugu, “Datagram transport layer security,” IETF RFC 4347, Apr. 2006.
E.W. Dijkstra, W. Feijen, and A.J.M. Van Gasteren, “Derivation of a Termination Detection Algorithm for Distributed Computations,” Information Processing Letter, vol. 16, No. 5, 1983.
Fayazbakhsh, S. K., Lin, Y., Tootoonchian, A., Ghodsi, A., Koponen, T., Maggs, B., & Shenker, S. (Aug. 2013). Less pain, most of the gain: Incrementally deployable ICN. In ACM SIGCOMM Computer Communication Review (vol. 43, No. 4, pp. 147-158). ACM.
G. Ateniese, K. Fu, M. Green, and S. Hohenberger. Improved Proxy Reencryption Schemes with Applications to Secure Distributed Storage. In the 12th Annual Network and Distributed System Security Sympo.
G. Tyson, S. Kaune, S. Miles, Y. El-Khatib, A. Mauthe, and A. Taweel, “A trace-driven analysis of caching in content-centric networks,” in Proc. IEEE ICCCN 2012, Munich, Germany, Jul.-Aug. 2012, pp. 1-7.
G. Wang, Q. Liu, and J. Wu, “Hierarchical attribute-based encryption for fine-grained access control in cloud storage services,” in Proc. ACM CCS 2010, Chicago, IL, USA, Oct. 2010, pp. 735-737.
G. Xylomenos et al., “A Survey of Information-centric Networking Research,” IEEE Communication Surveys and Tutorials, Jul. 2013.
Garcia, Humberto E., Wen-Chiao Lin, and Semyon M. Meerkov. “A resilient condition assessment monitoring system.” Resilient Control Systems (ISRCS), 2012 5th International Symposium on. IEEE, 2012.
Garcia-Luna-Aceves, Jose J. ‘A unified approach to loop-free routing using distance vectors or link states.’ ACM SIGCOMM Computer Communication Review. vol. 19. No. 4. ACM, 1989.
Garcia-Luna-Aceves, Jose J. ‘Name-Based Content Routing in Information Centric Networks Using Distance Information’ Proc ACM ICN 2014, Sep. 2014.
Ghali, Cesar, GeneTsudik, and Ersin Uzun. “Needle in a Haystack: Mitigating Content Poisoning in Named-Data Networking.” Proceedings of NDSS Workshop on Security of Emerging Networking Technologies (SENT). 2014.
Ghodsi, Ali, et al. “Information-centric networking: seeing the forest for the trees.” Proceedings of the 10th ACM Workshop on Hot Topics in Networks. ACM, 2011.
Ghodsi, Ali, et al. “Naming in content-oriented architectures.” Proceedings of the ACM SIGCOMM workshop on Information-centric networking. ACM, 2011.
Gupta, Anjali, Barbara Liskov, and Rodrigo Rodrigues. “Efficient Routing for Peer-to-Peer to-Peer Overlays.” NSDI. vol. 4. 2004.
H. Xiong, X. Zhang, W. Zhu, and D. Yao. “CloudSeal: End-to-End Content Protection in Cloud-based Storage and Delivery Services”, International Conference on Security and Privacy in Communication Systems (pp. 491-500), Springer Berlin Heidelberg, 2011.
Heckerman, David, John S. Breese, and Koos Rommelse. “Decision-Theoretic Troubleshooting.” Communications of the ACM. 1995.
Related Publications (1)
Number Date Country
20160171184 A1 Jun 2016 US