<html 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)"><style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@SimSun";
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;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-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;}
--></style></head><body lang=EN-US><div class=WordSection1><p>Hi Ray</p><p><o:p> </o:p></p><p>No, NFD does not allow distinct “remote endpoint” among Ethernet multicast faces.</p><p><o:p> </o:p></p><p>The rationale of using the same “remote endpoint” for all Ethernet multicast faces is: this address is a well-known address, so that every node can join the same multicast group.</p><p>It’s expected that all nodes are configured to use the same Ethernet multicast address, known as ALL-NDN-SYSTEMS. In the long term, this multicast address would be registered with IANA, and then become hard-coded.</p><p>Having a single ALL-NDN-SYSTEMS multicast address allows a network to work out-of-box without requiring an administrator to manually configure a distinct multicast address for each link, and without any negotiation or discovery.</p><p>If all nodes on a link are NDN nodes, this multicast group is effectively broadcast. We use the ALL-NDN-SYSTEMS multicast group so that NDN nodes can co-exist with non-NDN nodes, and non-NDN nodes don’t have to receive NDN traffic.</p><p>The discussion above is also applicable to UDP multicast faces.</p><p><o:p> </o:p></p><p>NFD does not require “remote endpoint” of faces to be distinct.</p><p>From an application, you may use FaceId to identify individual faces; to search for a face, run Face query operation with both “remote endpoint” and “local endpoint” conditions.</p><p><o:p> </o:p></p><p>Yours, Junxiao</p><p><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p style='border:none;padding:0in'><br><b>From: </b>Brandenburg, R. (Ray) van<br><b>Sent: </b>Wednesday, August 19, 2015 11:12<br><b>To: </b>ndn-interest@lists.cs.ucla.edu<br><b>Cc: </b>shijunxiao@email.arizona.edu<br><b>Subject: </b>Multiple Ethernet faces</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>1) If I have a machine with multiple NICs, NFD will list them as separate faces (since they have different local endpoints). However, they will have the same remote endpoint, i.e the ethernet multicast address listed in nfd.conf. Is there anyway to make sure each Ethernet face has it's own distinct multicast address?</p></div></body></html>