Project

General

Profile

Actions

Task #3680

closed

NameComponent of type 19 would conflict with Exclude Any

Added by Anonymous over 8 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Start date:
07/19/2016
Due date:
% Done:

0%

Estimated time:

Description

This is a low priority issue in case we officially allow flexible type codes for a NameComponent. (Right now we have Generic and ImplicitSha256DigestComponent.) If an application uses a name component with code 19, it won't be able to put it in an Exclude because this is the same type code as Any.
https://github.com/named-data/NDN-TLV/blob/master/interest.rst#exclude

In this possible future scenario, it might be necessary to prohibit type code 19, or say that an application won't be able to exclude it, or modify the definition of Exclude so that the NameComponent is wrapped inside another TLV, as we do for MetaInfo FinalBlockId.
https://github.com/named-data/NDN-TLV/blob/master/data.rst#finalblockid

Anyway, if we definitively decide never to support flexible name component types, we can abandon this issue.


Related issues 1 (0 open1 closed)

Related to NDN Specifications - Feature #4440: Typed name componentsClosedAlex Afanasyev

Actions
Actions #1

Updated by Junxiao Shi almost 7 years ago

Actions #2

Updated by Junxiao Shi over 6 years ago

  • Status changed from New to Rejected

Any element is gone in #4444.

Actions

Also available in: Atom PDF