ndn-lite

ndn-lite copied to clipboard

Space-efficient packet encoding using RFC9139

1

Certain IoT connectivity technologies, such as 802.15.4 and NFC, offer lower-than-usual MTU. [Information-Centric Networking (ICN) Adaptation to Low-Power Wireless Personal Area Networks (LoWPANs)](https://datatracker.ietf.org/doc/html/rfc9139) section 5 specifies a space-efficient encoding format...

yoursunny

After two PRs (#75 and #82), I was wondering if there is any styling/formatting guidelines? This would massively simplify our efforts in submitting code that conform to your guidelines. For...

yan-foto

Currently, `ndn_sig_verifier_verify_data` can only accept key name in KeyLocator.Name field. https://github.com/named-data-iot/ndn-lite/blob/d60a114a4c4e8422577ab8ae3817f79eed948254/app-support/ndn-sig-verifier.c#L292 It should be changed to accept either key name or certificate name. See #72.

yoursunny

ndn_gen_encrypted_payload used_size differs from ndn_probe_encrypted_payload_length

1

In `ndn_gen_encrypted_payload`, the `used_size` output parameter is calculated as: https://github.com/named-data-iot/ndn-lite/blob/d60a114a4c4e8422577ab8ae3817f79eed948254/encode/encrypted-payload.c#L38-L42 However, `ndn_probe_encrypted_payload_length` calculates its result differently: https://github.com/named-data-iot/ndn-lite/blob/d60a114a4c4e8422577ab8ae3817f79eed948254/encode/encrypted-payload.c#L28-L30 They differ in ` + NDN_AES_BLOCK_SIZE` on the last line. Please explain why...

yoursunny

Use pub/sub for user-defined policy delivery

1

In the current (6d433ac) ndn-lite, user-defined policies are distributed through signed Interest sent by the controller directly to a device. We may want to change this direct Interest notification to...

Zhiyi-Zhang

Override certificate name parts in KeyLocator

1

Since #72, KeyLocator can contain either a key name or a certificate name. When the validator operates in a network environment that uses a distinct certificate chain than what appears...

yoursunny

Include certificate name in KeyLocator

1

Currently, KeyLocator in Interest/Data signature carries the key name only. When there are multiple certificates issued to the same key, including when the certificate has been renewed on the same...

yoursunny

The function writes into a global variable `m_userdata`. Consequently, if the application invokes `ndn_sig_verifier_verify_data` with a new Data packet before the previous validation has completed, undefined behavior may occur. https://github.com/named-data-iot/ndn-lite/blob/6d433acd9b32f6116670ca720025490c38a3e2f8/app-support/ndn-sig-verifier.c#L30-L32...

yoursunny

Add checks for return values of all nested function calls in library

1

Currently, many functions in the library (such as ndn_interest_from_block) do not check the return values of functions they call; after this issue is will resolved, all nested function calls' return...

peurpdapeurp

According to [libtool documentation](https://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Reserved-Names.html) and [POSIX.1 standard section 2.2.2](https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html), some classes of identifier names are reserved for future extensions to the C language or the POSIX.1 environment. While using these...

yoursunny