<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>topology-independent and autoconfiguration service assigned temporary namespaces in NDNFit.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
There are some summarized explanations about NDNFit in annual progress report 2015 which I'm not sure if I've understood well. I've seen<BR>
<A HREF="https://github.com/remap/ndn-netenv-techreports/blob/master/Open_mHealth/ndn-netenv-Open_mHealth.pdf">https://github.com/remap/ndn-netenv-techreports/blob/master/Open_mHealth/ndn-netenv-Open_mHealth.pdf</A><BR>
too, but that is an older version.<BR>
There is this notion of _topology-independent namespace_ in 2.6 which is a mean to allow mobile producers to publish contents without the need for changing prefixes. According to Fig.2.6 b this namespace would be􀀗􀀄 _org/openmhealth_. In 2.2.1 there is a mention of _autoconfiguration support_, the NDN equivalent for DHCP. Fig. 2.7 says it's going to _provide temporary namespace and key for publishing while roaming._<BR>
First, what is the difference between topology independent and this temporary namespaces? Second, Is this service going to be an application specific and how to find the correspondent server would be preconfigured?<BR>
<BR>
There are some other questions which are dependent to answers of the ones above.<BR>
<BR>
Thanks,<BR>
Sabet<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>