<!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>RE: [Ndn-interest] Parameter, argument passing in Interest name</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Oops .I'm sorry. I hadn't seen the other answers. Yes. That could be a solution in cases like passing a parameter. Also there could be some encryption policies for applications, so that sent parameters wouldn't be clear text.<BR>
<BR>
Thanks,<BR>
Sabet<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Ndn-interest on behalf of Tai-Lin Chu<BR>
Sent: Mon 5/11/2015 11:23 PM<BR>
To: Gusev, Peter<BR>
Cc: ndn-interest@lists.cs.ucla.edu<BR>
Subject: Re: [Ndn-interest] Parameter, argument passing in Interest name<BR>
<BR>
There is discussion about markedComponent, which will be a<BR>
better/standardized way to do this.<BR>
<BR>
I think Peter's method is the "current" best practice, but the<BR>
application should figure out the canonical form of those params.<BR>
<BR>
On Mon, May 11, 2015 at 11:38 AM, Gusev, Peter <peter@remap.ucla.edu> wrote:<BR>
> No, I meant producer.<BR>
> As your producer registers only prefix<BR>
> /ndn/edu/ucla/remap/some_app/something it will inevitably receive any<BR>
> interests that have this prefix AND any kind of suffix<BR>
> /ndn/edu/ucla/remap/some_app/something/<could_be_anything_here> in the<BR>
> interests' name.<BR>
><BR>
> Thus, producer should carefully filter unwanted interests and check whether<BR>
> interest name it received has a meaningful components after the base prefix<BR>
> (i.e. for the previous example - check whether it has 6 components with<BR>
> names arg1 arg2 arg3 and values accordingly).<BR>
><BR>
> As far as I know, there's no such thing as REST-like arguments supported by<BR>
> the protocol right now.<BR>
><BR>
> Thanks,<BR>
><BR>
> --<BR>
> Peter Gusev<BR>
> Programmer/Analyst @ REMAP, UCLA<BR>
><BR>
> peter@remap.ucla.edu<BR>
> +1 213 5872748<BR>
> peetonn_ (skype)<BR>
><BR>
> On May 11, 2015, at 11:27 AM, Anil Jangam <anilj.mailing@gmail.com> wrote:<BR>
><BR>
> Thanks Peter.. just to clarify.. when you said 1. "parse it on the producer<BR>
> side " and 2. "your producer should be aware of that" you actually meant to<BR>
> say Consumer, right? This basically means, I will have to design my<BR>
> application namespace carefully to accommodate such extensions, and its<BR>
> completely application level details.<BR>
><BR>
> I was curious if protocol itself offers anything (so I just use an API) to<BR>
> set any user specific data into Interest, which ideally does the same thing<BR>
> as you mentioned.<BR>
><BR>
> /anil.<BR>
><BR>
><BR>
> On Mon, May 11, 2015 at 11:13 AM, Gusev, Peter <peter@remap.ucla.edu> wrote:<BR>
>><BR>
>> Hi Anil,<BR>
>><BR>
>> I believe you can pass anything you like after the prefix your producer<BR>
>> has registered. Though you have to parse it on the producer side if it's<BR>
>> something more than just another few name components.<BR>
>><BR>
>> I.e. your producer has registered prefix<BR>
>> /ndn/edu/ucla/remap/some_app/something that will make it receiving any<BR>
>> interests with this prefix, so you can send out interests like that<BR>
>> /ndn/edu/ucla/remap/some_app/something/arg1/10/arg2/20/arg3/30 and your<BR>
>> producer should be aware of that and treat name components that come after<BR>
>> the registered prefix accordingly.<BR>
>><BR>
>> Thanks,<BR>
>><BR>
>> --<BR>
>> Peter Gusev<BR>
>> Programmer/Analyst @ REMAP, UCLA<BR>
>><BR>
>> peter@remap.ucla.edu<BR>
>> +1 213 5872748<BR>
>> peetonn_ (skype)<BR>
>><BR>
>> On May 11, 2015, at 11:05 AM, Muhammad Hosain Abdollahi Sabet<BR>
>> <M.AbdollahiSabet@mail.sbu.ac.ir> wrote:<BR>
>><BR>
>> Hi Anil,<BR>
>> The only way that I'm aware of, is kind of tricky. The parameter<BR>
>> sender(active producer?) sends an interest to a receiver(passive consumer).<BR>
>> The receiver responds to the interest and sends another interest. Finally<BR>
>> the sender pass parameter in a data packet in response to the latter.<BR>
>><BR>
>> Thanks,<BR>
>> Sabet<BR>
>><BR>
>><BR>
>> -----Original Message-----<BR>
>> From: Ndn-interest on behalf of Anil Jangam<BR>
>> Sent: Mon 5/11/2015 10:23 PM<BR>
>> To: ndn-interest@lists.cs.ucla.edu<BR>
>> Subject: [Ndn-interest] Parameter, argument passing in Interest name<BR>
>><BR>
>> Hi,<BR>
>><BR>
>> I am trying to understand how I can pass a parameter using Interest<BR>
>> message<BR>
>> as a carrier. I want to exchange an application specific data between<BR>
>> producer and consumer.<BR>
>><BR>
>> I believe some mechanism exist to pass argument in strategy URL using<BR>
>> '?id=1254' convention. Does something similar possible within Interest<BR>
>> name?<BR>
>><BR>
>> /anil.<BR>
>><BR>
>> _______________________________________________<BR>
>> Ndn-interest mailing list<BR>
>> Ndn-interest@lists.cs.ucla.edu<BR>
>> <A HREF="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</A><BR>
>><BR>
>><BR>
><BR>
><BR>
><BR>
> _______________________________________________<BR>
> Ndn-interest mailing list<BR>
> Ndn-interest@lists.cs.ucla.edu<BR>
> <A HREF="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</A><BR>
><BR>
<BR>
_______________________________________________<BR>
Ndn-interest mailing list<BR>
Ndn-interest@lists.cs.ucla.edu<BR>
<A HREF="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest">http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest</A><BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>