4. Development process
• All git commits have to be associated with
one or more redmine issues.
• Issue cycle:
new assigned resolved closed
http://redmine.ccnx.org/projects/ccn/activity
• Release philosophy: ‘early and often’:
http://redmine.ccnx.org/projects/ccn/roadmap
7. Some of the major
changes since last meeting
• C repo w/disk-resident • local TCP for libccn
store & local-scoped connections (android
requests sandbox workaround)
• ‘Sync’ protocol • many android fixes
• new signing options • Apps: enhanced http
proxy, VLC plugin
• faster forwarding code upgrade, ccnc c-based
chat client.
w/new PIT structure
(see http://www.ccnx.org/releases/ccnx-0.6.1/NEWS)
8. Things in progress
• Transient repo storage
• Refactored ‘sync’ (decoupled from repo)
• Apps: Medical device interface, serverless
XMPP, automatic photo sharing
9. On the radar
• Opportunistic caching support
• CDN-quality transaction logging framework
• Generic link level encap with hybrid ARQ
10. Community development
• Many exciting things happening. E.g.,
‣ NDN ospf-n, python bindings, device control
& video streaming apps, ns3 simulator
‣ ANR-Connect simulator, QoS framework
‣ U. Basel CCN-lite
‣ ...
• PARC interested in setting up a clearinghouse
to promote & connect these efforts.
11. Commercialization
• Operator and vendor research interest.
• ENC (Emerging Networks Consortium)
looking at scenarios and use cases.
• Need people solving real problems to
evolve from ‘research’ to ‘advanced
development’ stage.
• Eventually standardize based on ‘rough
consensus and running code’ (the world
may not need another 3GPP IMS)