<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1972979570;
mso-list-template-ids:-1;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Ashlesh</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you for stating your requirements. I’ll consider your suggestion when I decide to add PIT logging.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I disagree with putting PIT logging at TRACE just because “PIT can generate a lot of logs”. Operator is not supposed to specify default logging level below INFO. Instead, the default logging level should stay at INFO or above, and DEBUG or TRACE should be enabled on specific modules only.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Yours, Junxiao</p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:agawande@memphis.edu">Ashlesh Gawande (agawande)</a><br><b>Sent: </b>Monday, August 22, 2016 09:26<br><b>To: </b><a href="mailto:shijunxiao@email.arizona.edu">Junxiao Shi</a><br><b>Cc: </b><a href="mailto:lanwang@memphis.edu">Lan Wang (lanwang)</a>; <a href="mailto:nfd-dev@lists.cs.ucla.edu">nfd-dev@lists.cs.ucla.edu</a><br><b>Subject: </b>Re: [Nfd-dev] Help needed with debugging duplicate Nonce</p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>I am not sure but your points make sense. I was just logging the insertion and deletion of PIT entries and in records and out records in the strategy.<o:p></o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>It maybe better to put majority of the PIT logging in TRACE as PIT can generate a lot of logs.<o:p></o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'><o:p> </o:p></span></p><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>Ashlesh<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><img border=0 width=694 height=2 style='width:7.2291in;height:.0208in' id="Horizontal_x0020_Line_x0020_1" src="cid:image001.png@01D1FC57.B1BCA6A0"></span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p></o:p></span></p><div id=divRplyFwdMsg><p class=MsoNormal><b><span style='color:black'>From:</span></b><span style='color:black'> Junxiao Shi <shijunxiao@email.arizona.edu><br><b>Sent:</b> Monday, August 22, 2016 11:18:05 AM<br><b>To:</b> Ashlesh Gawande (agawande)<br><b>Cc:</b> Lan Wang (lanwang); nfd-dev@lists.cs.ucla.edu<br><b>Subject:</b> Re: [Nfd-dev] Help needed with debugging duplicate Nonce</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <o:p></o:p></span></p></div></div><div><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Ashlesh, I'm still waiting for you to answer about what PIT logging you are looking for.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>For others on nfd-dev, if you have a need for PIT logging, please let me know the requirements so I can design properly.<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>I can see a few levels of PIT logging:<o:p></o:p></span></p></div><div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>track the insertion and deletion of PIT entries: although PIT has no logging, this can be inferred from Forwarder logging at DEBUG level; however, having logging from PIT makes this easier<o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>track the PIT timers: they are currently controlled by Forwarder (not PIT), and can be inferred from Forwarder logging at DEBUG level<o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>track the in/out records: although PIT has no logging, this can be inferred from Forwarder logging at DEBUG level; however, having logging from PIT makes this easier<o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>track changes in StrategyInfo: this is controlled by specific strategy and should be implemented by strategy<o:p></o:p></span></li></ul></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Yours, Junxiao<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>On Wed, Aug 10, 2016 at 8:27 AM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>> wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Hi Ashlesh<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>You can't. FIB/PIT/Measurements has no logging. If this is a popular demand, I may consider adding it. <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>You can let me know what kind of PIT logging you are looking for, so that if I decide to work on this, I can have a better idea on the use cases.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Currently you can use a debugger, or add </span><span style='font-size:12.0pt;font-family:"Courier New"'>printf</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>s at where matters.<o:p></o:p></span></p><div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>Yours, Junxiao<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'>On Wed, Aug 10, 2016 at 8:19 AM, Ashlesh Gawande (agawande) <<a href="mailto:agawande@memphis.edu" target="_blank">agawande@memphis.edu</a>> wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p style='background:white'><span style='font-family:"Calibri",sans-serif;color:black'>Can you please tell me how to deduce PIT entry contents by looking at the NFD log?<o:p></o:p></span></p></div></div></blockquote></div></div></div></div></div></blockquote></div></div></div></div></div></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>