<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>Hi,</div>
<div>Comments below.</div>
<div>Thanks,</div>
<div>Jeff</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>Lixia Zhang <<a href="mailto:lixia@cs.ucla.edu">lixia@cs.ucla.edu</a>><br>
<span style="font-weight:bold">Date: </span>Sat, 22 Mar 2014 13:13:49 -0700<br>
<span style="font-weight:bold">To: </span>Jeff Burke <<a href="mailto:jburke@remap.ucla.edu">jburke@remap.ucla.edu</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>" <<a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a>><br>
<span style="font-weight:bold">Subject: </span>Re: Name component format<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br>
<div>
<div>On Mar 22, 2014, at 10:58 AM, "Burke, Jeff" <<a href="mailto:jburke@remap.ucla.edu">jburke@remap.ucla.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Hi,</div>
<div><br>
</div>
<div>There are a few changes to the representation of names in the TLV spec (<a href="http://named-data.net/doc/NDN-TLV/0.2/name.html">http://named-data.net/doc/NDN-TLV/0.2/name.html</a>) that I am not sure have been widely discussed. In particular, the introduction
of types (beyond distinguishing the implicit digest), an updated URI representation, and the inability to specify empty name components. </div>
<div><br>
</div>
<div>Are these considered "baked"? Would it be possible to discuss these at some point in more detail? </div>
</div>
</blockquote>
<div><br>
</div>
Hi Jeff,</div>
<div><br>
</div>
<div>the changes were made after some discussions among the NFD team, then with Van. </div>
<div>Not sure what you meant by "considered baked". . .</div>
<div>- I do not think the changes made to the NFD release-1.</div>
<div>- we are doing explorative research, right?</div>
</div>
</div>
</span>
<div><br>
</div>
<div>[jb] Sorry, I just meant whether they were locked and incorporated into NFD release 1. </div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>Of course all naming issues can benefit from more discussions. </div>
<div>- wonder if you would like to propose a specific time frame (i.e. next week, or longer term)?</div>
</div>
</div>
</span><span id="OLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>- it would be helpful if there are some inputs/reading/considerations over email before the call, so that people can think through first.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>[jb] I don't know that it is urgent – I know that the NFD people have a lot going on. :) Perhaps the next meeting with IRL we can talk about it first, or on the NFD call on 4/4. </div>
<div><br>
</div>
<div>The main question I have is about the introduction of the number type? What motivates it? Doesn't this start a slippery slope away from opaque names. </div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div><br>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Among other things, typing components unless required by the protocol (as seems to be the case with the implicit hash) seems to run counter to the notion of name opaqueness, and there are some conflicts in the URI representation that need to be resolved.</div>
</div>
</blockquote>
<br>
</div>
<div>For any URI issues: Please let Alex and Junxiao know.</div>
</div>
</div>
</span>
<div><br>
</div>
<div>[jb] JeffT had mentioned some concerns with the conflict with the allowable hex encoding... I'll ask him to talk with Alex and Junxiao. </div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>for component typing: are you saying that we should allow name component typing?</div>
</div>
</div>
</span>
<div><br>
</div>
<div>[jb] No, I don't think so. There might be some value to applications, but I found the notion of name opaqueness to be very powerful so am wondering about the motivation. (I understand it for the implicit hash.) </div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>In any case, as soon as we can collect a list of technical questions, I can try scheduling a discussion.</div>
<div><br>
</div>
<div>Lixia</div>
</div>
</div>
</span>
</body>
</html>