<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>… Right now, both ndn-cxx and ndn-cpp treat ".." as a illegal encoding for a component and drop it. So, "/a/b/../c" simply becomes "/a/b/c". But ndnx (ndnd-tlv) treat ".." as "up one level" and it becomes "/a/c". </div>
<div><br>
</div>
<div>The question is whether the TLV specification should spell out the correct behavior.</div>
<div><br>
</div>
<div>- Jeff T</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Thompson>, Jeff Thompson <<a href="mailto:jefft0@remap.ucla.edu">jefft0@remap.ucla.edu</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, August 5, 2014 2:51 AM<br>
<span style="font-weight:bold">To: </span>nfd-dev <<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>><br>
<span style="font-weight:bold">Subject: </span>How to treat ".." in an NDN URI?<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>The TLV specification for the NDN URI scheme says "To unambiguously represent name components that would collide with the use of . and .. for relative URIs, any component that consists solely of one or more periods is encoded using three additional periods.".</div>
<div><a href="http://named-data.net/doc/ndn-tlv/name.html#ndn-uri-scheme">http://named-data.net/doc/ndn-tlv/name.html#ndn-uri-scheme</a></div>
<div><br>
</div>
<div>If an NDN URI uses the "relative" value of "..", how should the URI be decoded. Specifically, should it be treated as "up one level" like in a Unix path? For example, should the URI "/a/b/../c" be decoded as the name "/a/c"?</div>
<div><br>
</div>
<div>(This question comes from an issue on the ndn-js Redmine: <a href="http://redmine.named-data.net/issues/1818">http://redmine.named-data.net/issues/1818</a> ).</div>
<div><br>
</div>
<div>Thanks,</div>
<div>- Jeff T</div>
</div>
</div>
</span>
</body>
</html>