Project

General

Profile

Feature #2012

MarkedComponent

Added by Junxiao Shi over 6 years ago. Updated over 3 years ago.

Status:
Rejected
Priority:
Normal
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Define MarkedComponent as one Name component type.

Reference: http://www.lists.cs.ucla.edu/pipermail/ndn-interest/2014-September/000085.html


Related issues

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

Actions
#1

Updated by Junxiao Shi over 6 years ago

This Task is discussed at 20140929 conference call, but not yet approved.

The following questions are discussed:

  • Should any other type be allowed as Name component types, in addition to NameComponent, ImplicitSha256DigestComponent (#2011), and MarkedComponent?
    • The current idea is NO, because forwarding plane need not understand these, and current applications do not need extra types.
  • In canonical ordering, where should MarkedComponent be placed?
#2

Updated by Junxiao Shi over 6 years ago

  • Assignee set to Alex Afanasyev
#3

Updated by Junxiao Shi about 6 years ago

  • Tracker changed from Task to Feature
#4

Updated by Junxiao Shi almost 6 years ago

From @Alex on 20150713 email:

You can consider this approved by me

However, @Alex has agreed to work on this issue during 20141017 conference call, and hence the assignment in note-2.

An "approved by me" is not what I'm looking for.

#5

Updated by Junxiao Shi over 3 years ago

  • Status changed from New to Rejected

MarkedComponent is no longer necessary after typed components (#4440).

#6

Updated by Junxiao Shi over 3 years ago

Also available in: Atom PDF