[Ndn-interest] ChronoChat and its default RIB entries

[Alex Afanasyev]

> On Feb 27, 2015, at 4:29 PM, Anil Jangam <anilj.mailing at gmail.com> wrote:
> 
> Thanks Alex. Pls see inline.
> 
> On Fri, Feb 27, 2015 at 3:41 PM, Alex Afanasyev <alexander.afanasyev at ucla.edu <mailto:alexander.afanasyev at ucla.edu>> wrote:
> Hi Anil,
> 
> I think you’re mixing a couple of things.  The face that ChronoChat application uses is just a channel between the application and NFD.  It is normally unix socket face, but it doesn’t really matter, as it is not related to you being able to chat with other people.
> 
> Besides having a face that points to a remote chat node, you need to instruct NFD (RIB manager specifically) that specific data can be reached through this face.
> 
> So basically I need to register the name prefix of the remote user using faceId=257 so that when local chat application sends the Interest to fetch the messages (after ChronoSync update) from remote end, it is forwarded on face 257, correct?

Yes. Exactly.  The only correction I’ll make is that ChronoChat app just wants to fetch messages.  It is not aware local or remote.  It just issues interest for data and NFD will figure out using the registered RIB entries.

> I tried to add user and its details through "Add contact" sub menu, but it did not succeed. This is the place where we configure the name Identity of the remote user, right?

I don’t know the extent this feature is implemented/working :)  Yingdi or Qiuhan can help me with answering this question.

I also don’t have answers to the following questions.  Yingdi/Qiuhan, pls help :)

—
Alex

> Also since this is decentralized system, it is not required to know what chat room the remote user is connected to, correct? How does this function?
> 
> Do you have any document which will guide through various steps to establish a two-party chat session?
> 
> In your specific face, you may start by registering /ndn/broadcast prefix for your multicast udp face:
> 
>     nfdc register /ndn/broadcast 294
> 
> This will tell NFD that data packets with prefix /ndn/broadcast can be retrieved if interest send out through face 294.   You can also register / prefix, which will essentially mean that NFD can try this face to fetch all kind of data packets.
> 
> —
> Alex
> 
>> On Feb 27, 2015, at 1:22 PM, Anil Jangam <anilj.mailing at gmail.com <mailto:anilj.mailing at gmail.com>> wrote:
>> 
>> Hi,
>> 
>> When I start the ChronoChat client, it creates certain default entries into the RIB as follows.
>> 
>> /ndn/broadcast/chronochat/chatroom-list route={faceid=294 (origin=0 cost=0 ChildInherit)}
>> /ndn/broadcast/ChronoChat/chatroom-e8745dec route={faceid=294 (origin=0 cost=0 ChildInherit)}
>> /ndn/broadcast/%F0./chronochat-tmp-identity/f4e4ea96/CHRONOCHAT-INVITATION route={faceid=294 (origin=0 cost=0 ChildInherit)}
>> 
>> I checked the faceId 294, and it is a non udp/tcp type of face.
>> 
>> faceid=294 remote=fd://23 <> local=unix:///run/nfd.sock <> counters={in={70i 6d 16223B} out={0i 6d 5145B}} local on-demand point-to-point
>> 
>> In what way I can program the ChronoChat client to use the specific face? may be through some configuration file or so?
>> 
>> I have configured a face which points to the remote user in the Chat. I guess this local client should be using this interface (257) instead of 294, correct?
>> 
>> faceid=257 remote=udp4://224.0.23.170:56363 <http://224.0.23.170:56363/> local=udp4://133.164.60.154:56363 <http://133.164.60.154:56363/> counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point
>> 
>> /anil.
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150227/a5e1b466/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150227/a5e1b466/attachment.bin>