[Nsi-wg] Query request

[michalb]

Hello Hans,

I wanted to point out a little bit of protocol inconsistance. In the NSI 
Connection Service Protocol_20_v1 doc one can read (regarding 'replyTo' 
field):

"If no endpoint value is provided in a operation request, then it is assumed 
the requester is not interested in a response and will use alternative 
mechanism to determine the result."

So for some GUI purposes which surely will be behind firewall/NAT, I 
reserve, provison, etc with no 'replyTo' provided and now I'd like to "use 
alternative mechanism to determine the result" (which is query) and because 
query is async only the whole thing gets defeated. Would be nice to have a 
simple query that returns basic query result so the feature of not setting 
'replyTo' would have more sense.

br
michal

-----Oryginalna wiadomość----- 
From: Hans Trompert
Sent: Wednesday, October 31, 2012 1:01 PM
To: michalb
Cc: nsi-wg at ogf.org
Subject: Re: [Nsi-wg] Query request

Hi Michal,

The NSI WG is well aware of the fact that the asynchronous behavior of
the protocol isn't working for those behind a firewall or NAT. A couple
of organizations that are connected to SURFnet started to implement NSI
to provision paths through our network and they all run into this
problem. To help them out SURFnet offered to come up with a `user NSI CS
protocol'  that is firewall and NAT save. You are invited to help define
how this should look like :)

    HansT.

On 10/31/12 11:24 AM, michalb wrote:
> Hello,
>
> This is for reservation query - will there be a synchronous version of
> that operation (basic query at least)? It is not always possible to
> listen on query responses and polling would help under such
> circumstances.
>
> br
> michal
>
>
> -----Oryginalna wiadomość----- From: Jeroen van der Ham
> Sent: Tuesday, September 18, 2012 4:37 PM
> To: nsi-wg at ogf.org Group
> Subject: [Nsi-wg] Query request
>
> Hi,
>
> While thinking about a demonstration scenario for SC, we came upon an
> interesting use-case for the query command. We are trying to plan
> workflows on the infrastructure, depending on availability. For that
> it would actually be useful to know not only if a certain resource is
> in use, but also when it could become available again.
>
> Would it be possible to add capabilities for the query command to
> provide something like that?
>
> Jeroen.
>
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg