NFD » NDN Specifications

As discussed on 20190130 NFD call, a range of TLV-TYPE numbers indicates of the start of digest computation area for ParametersSha256DigestComponent.
I'd suggest renumbering Parameters to 0x30 instead of 0x24, so that bitwise expression (tlvType & 0xF0) == 0x30 identifies this range.

Junxiao Shi wrote:

I'd suggest renumbering Parameters to 0x30 instead of 0x24, so that bitwise expression (tlvType & 0xF0) == 0x30 identifies this range.

err... why? [48-63] or [36-51], what's the difference? both intervals are currently unassigned.

Bitwise operator is better than inequal comparison operator, at least in hardware implementation (think electric circuits where it needs less gates).
Although the need for hardware implementation at this level may be sparse, there’s no harm in assigning a hardware-friendly number.

Shouldn't ParametersSha256DigestComponent also be non-critical? What's the point of having one critical but not the other?

Shouldn't ParametersSha256DigestComponent also be non-critical? What's the point of having one critical but not the other?

Evolvability rules do not apply to name component types.

And where is that written?