[Nfd-dev] Question about packet format v0.3 transition

[Junxiao Shi]

Hi Lixia

> Within the next few months, ndn-cxx must remain compatible with Packet
> Format 0.2 endpoints. Therefore, new fields such as Parameters are
> unavailable.
>
> I can't recall the exact results from NFD discussion, but my vague memory
> does not match Junxiao's above statement.
>
> Compatibility means supporting the old protocol format.
> Compatibility does mean no support for new protocol field.
>

As indicated on
https://redmine.named-data.net/projects/nfd/wiki/Packet03Transition ,
Packet Format 0.3's new fields will become available when reaching "2-to-3
Interpretation" step.
Sadly, development work for Packet Format 0.3 has been dormant in past two
months, so we are nowhere near that step.

> Few people has any idea on how Interest Parameters *should* be used.
>
> what does this statement mean ???
>
As evidenced by not seeing any protocols designed to use Interest
Parameters.
This could be a chicken-egg problem, as the implementation has no support
for Interest Parameters, so that application developers would be unwilling
to depend on a protocol feature that isn't yet available..


> > Some protocol issues related to Interest Parameters adoption are:
> > https://redmine.named-data.net/issues/4599 Signed Interest and Command
> Interest
>
> as I looked this up: I believe your proposed implementation needs to go
> through a thorough discussion (I am not sure I'd agree with your suggestion
> there)
>
Everyone, please post your comments on Redmine.


>
> > https://redmine.named-data.net/issues/4600 NFD Management protocol
> the next issue is about management protocol, which is not directly related
> to other apps use of Interest parameter field.

NFD Management protocol serves as an example on how to design a
command-response protocol. So far, repo-ng and NLSR has adopted similar
protocols.

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20180706/a3cc6409/attachment.html>