<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 31, 2017, at 10:18 AM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" class="">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Dear folks<div class=""><br class=""></div><div class=""><div class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word" class="">I do not support this proposal. This creates inter-commmand dependency for basic operations as registering prefix to a new face. We should not create more obstacles for users for the sake of having consistent interface with IP tools.</div></blockquote><div class=""> </div></div></div></div></div><div class="">Let's rewarm the original rationale of introducing <b class="">implicit face creation</b>: what we needed is not implicit face creation, but the ability to write FaceUri into <font face="monospace, monospace" class="">nfdc register</font> command in place of FaceId.</div><div class="gmail_extra">Before #1515, <font face="monospace, monospace" class="">nfdc register</font> command only accepts FaceId. A caller must first invoke <font face="monospace, monospace" class="">nfdc create</font>, scrape its output (or <font face="monospace, monospace" class="">nfd-status -f</font> output), and then invoke <span style="font-family:monospace,monospace" class="">nfdc register</span>. This is the "inter-command dependency".</div><div class=""><br class=""></div><div class="">At that time, there were no <font face="monospace, monospace" class="">faces/query</font> operation, so that the easiest way to obtain FaceId from FaceUri is to execute <font face="monospace, monospace" class="">faces/create</font> command. It has caused a long list of concerns in #<a href="https://redmine.named-data.net/issues/1515" target="_blank" class="">1515</a>.</div><div class="">When <font face="monospace, monospace" class="">faces/query</font> operation was later introduced, some of the concerns are solved, but it's too late the change the semantics of <font face="monospace, monospace" class="">nfdc register</font> subcommand.</div><div class=""><br class=""></div><div class="gmail_extra">Under the new proposal, <font face="monospace, monospace" class="">nfdc route add</font> command accepts FaceUri and uses that to query an existing face. This should not be considered "inter-command dependency", because the operator can simply run "<font face="monospace, monospace" class="">nfdc face create udp://<a href="http://hobo.cs.arizona.edu/" target="_blank" class="">hobo.cs.arizona.edu</a> && nfdc route add / udp://<a href="http://hobo.cs.arizona.edu/" target="_blank" class="">hobo.cs.arizona.edu</a></font>" without scraping the output of the first subcommand.<br class=""></div></div></div></blockquote><br class=""></div><div>I that case, I don't understand what the question/proposal is really about. Remove faceUri handling for unregister? unregister doesn't support faceUri (per man page) already.</div><div><br class=""></div><div>--</div><div>Alex</div><div><br class=""></div><br class=""></body></html>