Your SlideShare is downloading. ×
CCNxCon2012: Session 5: HTTP/CCN Gateway and Cooperative Caching Demonstrator
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

CCNxCon2012: Session 5: HTTP/CCN Gateway and Cooperative Caching Demonstrator

366

Published on

HTTP/CCN Gateway and Cooperative Caching Demonstrator …

HTTP/CCN Gateway and Cooperative Caching Demonstrator
Dariusz Bursztynowski, Mateusz Dzida, Tomasz Janaszka (Telekomunikacja Polska, Orange Labs Poland), Adam Dubiel (Warsaw University of Technology, Poland), Michal Rowicki (Warsaw University of Technology and Telekomunikacja Polska, Poland)

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
366
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. CCNx Comm. Meeting, Sophia-Antipolis, Sept. 12-13, 2012Client/server HTTP/CCN gateway in CCN environment with cooperative caching CCN client / CCN server + IP client/IP server/CCN tunelling 1. Motivation File HTTP• Experiment with caching schemes using real traffic server (HTTP dominates) IP• Hands-on on application level => universal HTTP/CCN Server gateway (able to operate in different settings: inbound/outbound proxy, HTTP tunelling) 2. Naming and mapping of messages Registered namesRequirements• 100% HTTP compatibility CCN• easy to implement CCN• future-proof to the changes of CCNx protocol HTTP clientTwo basic rules adopted:• Request header – mapped onto content name using command markers IP IP• Entity Body always conveyed in Data packets (sequences of Interest/Data may be required) HTTP clientExamples:GET ccnx://http/<request_method_name>/<URL>/<abs_path>... .../%C1.http.<header_field_name>~Eb64(field_value)/%C1.http... 4. Actual setupPOST    Need to upload a file using the POST  method Interest (can I send ?)   name:    grid cluster statistics   your request) Data [OK] (wait for the Interest that prompts you to specify HTTP/CCN local content    name:  content: OK  CCNx   Interest (specify your POST request) network monitoring   Data (well, I’m posting this) name:     content:  send a server OK response to me) Interest (please,   Data (here goes the OK to the POST)  HTTP/CCN   name:  + body content: OK browser 3. Architecture – functional settings 6. Demo use casesCCN client / IP server • CCN client / IP server • CCN client / CCN server Watch the demo for more details HTTP server HTTP client Orange Labs

×