Changes between Version 6 and Version 7 of GENIEducation/SampleAssignments/CCNAssignment/ForInstructors

06/03/13 14:50:48 (6 years ago)



  • GENIEducation/SampleAssignments/CCNAssignment/ForInstructors

    v6 v7  
    171171  Now fetch 1902/01/25 to 1902/01/31 from ''researcher2''. How does this transfer differ from the previous two? why?
    173  - '''3.2 Choosing Content Names''' [[BR]] -- Files to download: [ naming.rspec], [ ccnx-atmos.tar.gz]
     173 - '''3.2 Choosing Content Names'''  -- Files to download: [ naming.rspec], [ ccnx-atmos.tar.gz] [[BR]]
    174174 This exercise will demonstrate the importance of naming in named data networking. As the term suggests, and as you saw in Task 1.1, routing in named data networking is performed based on content names. This means that content naming has a large impact on how consumers fetch the data they require, and naming structure can heavily influence how simple and efficient data requests may be. [[BR]]
    175175 The ''Atmos'' package uses content names in the namespace ''/ndn/'' to serve NetCDF data. The data is sliced by time, with the suffix pr_<year>/<month>/<day>/00 added to represent data for the specified date. Thus, clients can request precipitation data for a given day in history, or a range of days, by issuing an interest for the dates in question. The complete path for data relating to January 3, 1902 would be: ''/ndn/''
    193193  Which URI scheme is more efficient in time and network resources if the user only wants a few days of data? What if the user wants a full calendar month of data? [[BR]]
    195  - '''3.3 Exploring the Impact of Caching''' [[BR]] -- Files to download: [ cache.rspec]
     195 - '''3.3 Exploring the Impact of Caching''' -- Files to download: [ cache.rspec]  [[BR]]
    196196 For this exercise you will manipulate various caching parameters for the ccnd daemon and observe the effects on network efficiency. [[BR]]
    197197 A property of named data networking is that multiple requests for the same names may return the same data. This allows intermediate nodes to cache data from one request for a given name and return it for future requests of the same name, from the same client or even a different client. When multiple clients located near each other but far from the server in the network want the same data, a node near the clients may be able to service some clients without contacting the server. [[BR]]