On October 23rd, 2014, we updated our
By continuing to use LinkedIn’s SlideShare service, you agree to the revised terms, so please take a few minutes to review them.
CCNx Update Van Jacobson CCNxCon Inria Soﬁa Antipolis 11 September 2012
PARC Core Team• Michael Plass (architect)• Nick Briggs• Rebecca Braynard• David Kordsmeier (repo master)• Alexander Afanasyev (summer intern)
Environment• Master repo hosted on github: https://github.com/ProjectCCNx/ccnx• Issue tracker (redmine) at: http://redmine.ccnx.org/projects/ccn• Nightly build / regression testing via Jenkins
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
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 ﬁxes • 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)
Things in progress• Transient repo storage• Refactored ‘sync’ (decoupled from repo)• Apps: Medical device interface, serverless XMPP, automatic photo sharing
On the radar• Opportunistic caching support• CDN-quality transaction logging framework• Generic link level encap with hybrid ARQ
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.
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)