Project

General

Profile

Feature #1840

Make ndn URI resolution RFC3986-compliant

Added by Junxiao Shi almost 6 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Base
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
3.00 h

Description

Relative Resolution procedure should be used to resolve ndn: URIs.


Related issues

Related to NDN Specifications - Bug #1818: Shouldn't [new Name("/a/b/../c").toUri() == "/a/c"]?Closed08/04/2014

Actions
Related to ndn-cxx - Bug #2725: Potential name construction errorsClosed04/03/2015

Actions

History

#1

Updated by Junxiao Shi almost 6 years ago

A correct implementation should test the following URIs as equivalent:

/A/B/C
ndn:/A/B/C
ndn:///A/B/C
ndn://authority/A/B/C
/A/./B/C
/A/D/../B/C
/../A/B/C
/./A/B/C
#2

Updated by Junxiao Shi over 5 years ago

  • Tracker changed from Task to Feature
  • Target version changed from v0.3 to Unsupported

http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2014-August/000313.html

My opinion is that this feature should be implemented only when somebody actually needs it. Until then, there is no point of spending time on it.

Therefore I'm setting Target Version to Unsupported.

#3

Updated by Junxiao Shi over 5 years ago

  • Related to Bug #1818: Shouldn't [new Name("/a/b/../c").toUri() == "/a/c"]? added
#4

Updated by Junxiao Shi about 5 years ago

  • Related to Bug #2725: Potential name construction errors added
#5

Updated by Davide Pesavento over 2 years ago

  • Subject changed from Make URI resolution RFC3986 compliant to Make ndn URI resolution RFC3986-compliant
  • Description updated (diff)

Also available in: Atom PDF