[Ndn-interest] Reflexive Forwarding for NDN and CCNx
David R. Oran
daveoran at orandom.net
Thu Apr 2 08:59:00 PDT 2020
Dirk Kutscher and I have formalized the reflexive forwarding scheme we
developed for RICE
expanded it to cover more use cases (e.g. IoT sensors) and spelled out
the whole scheme in detail including algorithms and encoding in the
Internet Draft we just submitted.
It should work equally well for both CCNx and NDN and has concrete
encoding for CCNx, although we need some help from the NDN team on what
the best packet encoding ought to be in NDN for the new TLV we define.
Since this is a fairly major change/enhancement to the NDN and CCNx
forwarding model, it really needs a close review to help us figure out:
- Are we crazy?
- Is the complexity/functionality tradeoff appropriate?
- Did we miss anything, particularly any corner cases we should have
- Which of the alternative approaches to backward/forward compatibility
we describe seems the right one?
- Are there more use cases that we ought to document? We were hoping to
have one or two to include for state synchronization, but have deferred
that for now in the interest of getting the spec out for review.
We’d like to talk about this at the ICNRG Interim meeting on April 20,
so p[lease sets aside some time to read/eview/think about between now
Dirk & DaveO.
> From: internet-drafts at ietf.org
> To: Dave Oran <daveoran at orandom.net>, David Oran
> <daveoran at orandom.net>, Dirk Kutscher <ietf at dkutscher.net>
> Subject: New Version Notification for
> Date: Thu, 02 Apr 2020 07:37:32 -0700
> A new version of I-D, draft-oran-icnrg-reflexive-forwarding-00.txt
> has been successfully submitted by Dave Oran and posted to the
> IETF repository.
> Name: draft-oran-icnrg-reflexive-forwarding
> Revision: 00
> Title: Reflexive Forwarding for CCNx and NDN Protocols
> Document date: 2020-04-02
> Group: Individual Submission
> Pages: 30
> Current Information-Centric Networking protocols such as CCNx and
> have a wide range of useful applications in content retrieval and
> other scenarios that depend only on a robust two-way exchange in
> form of a request and response (represented by an _Interest-Data
> exchange_ in the case of the two protocols noted above). A number
> important applications however, require placing large amounts of
> in the Interest message, and/or more than one two-way handshake.
> While these can be accomplished using independent Interest-Data
> exchanges by reversing the roles of consumer and producer, such
> approaches can be both clumsy for applications and problematic from
> state management, congestion control, or security standpoint. This
> specification proposes a _Reflexive Forwarding_ extension to the
> and NDN protocol architectures that eliminates the problems
> in using independent Interest-Data exchanges for such applications.
> It updates RFC8569 and RFC8609.
> Please note that it may take a couple of minutes from the time of
> until the htmlized version and diff are available at tools.ietf.org.
> The IETF Secretariat
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest