<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1487964732332_2614">Hi all,</div><div id="yui_3_16_0_1_1487964732332_8578"><br></div><div id="yui_3_16_0_1_1487964732332_11554">Thanks for accepting my request.<br></div><div id="yui_3_16_0_1_1487964732332_2613"><br></div><div id="yui_3_16_0_1_1487964732332_2612" dir="ltr">I am working on a NDN forwarding strategy and consumer/producer applications on ndnSIM. Assuming that there are multiple paths from the consumer to a data source, the goal is to improve data delivery based on cross-layer information from the network, so the consumer can select the best face to send the following Interest packets based on number of hops, node ID, throughput, round-trip delay, and geographical location.<br></div><div dir="ltr" id="yui_3_16_0_1_1487964732332_6860"><br></div>I see two possible ways to implement that:<br><div dir="ltr" id="yui_3_16_0_1_1487964732332_4926">1. Insert the cross layer information direct in the packet payload<br></div><div dir="ltr" id="yui_3_16_0_1_1487964732332_6384"> Every node along the path would have to update the packet payload or meta data accordingly, and the producer would insert its coordinates.</div><div dir="ltr" id="yui_3_16_0_1_1487964732332_11444"> The consumer can then select which face to send the following Interests based on throughput, or distance to content source, or path with less hops, etc.</div><div dir="ltr" id="yui_3_16_0_1_1487964732332_11443"> Since the NDN architecture doesn't allow the payload to be modified, intermediate nodes would have to create a copy of the packets. Can I use MetaInfo field? <br></div><div dir="ltr" id="yui_3_16_0_1_1487964732332_5948"><br></div><div dir="ltr" id="yui_3_16_0_1_1487964732332_6330">2. Design a naming scheme (more common in the literature)<br></div><div id="yui_3_16_0_1_1487964732332_2638"> Use a naming scheme to accomodate that. For instance the Interest packet would be /<desired_content>/<hop_count>/<+node_id> and the data packet would be something like /<content>/<hop_count>/<lat_long>/<node_id1 + node_id2 + ... + node_idN>, where node_id1-N refers to the nodes along the path.<br></div><div id="yui_3_16_0_1_1487964732332_11175"><br></div><div id="yui_3_16_0_1_1487964732332_11727">Are the two implementations feasible? Could you comment on the recommended way to use information from the network in the forwarding decision?</div><div id="yui_3_16_0_1_1487964732332_11733"><br></div><div id="yui_3_16_0_1_1487964732332_11734">Thank you!<br></div></div></body></html>