I am guessing the thread on synchronous vs future availability services got merged. There seems to be support for the synchronous basic query, but not much discussion on what will be needed to support a basic query structure to query a potential reservation in the future. <div>
<br></div><div>To start the discussion on the second topic, I support NSA&#39;s providing that functionality, this is a post 2.0 discussion IMHO, and am wondering if this will give an end-to-end path information or just the first domain (i.e. is this detailed vs summary query?)</div>
<div><br></div><div>Inder</div><div><br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 18, 2012 at 7:37 AM, Jeroen van der Ham <span dir="ltr">&lt;<a href="mailto:vdham@uva.nl" target="_blank">vdham@uva.nl</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
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.<br>

<br>
Would it be possible to add capabilities for the query command to provide something like that?<br>
<br>
Jeroen.<br>
<br>
_______________________________________________<br>
nsi-wg mailing list<br>
<a href="mailto:nsi-wg@ogf.org">nsi-wg@ogf.org</a><br>
<a href="https://www.ogf.org/mailman/listinfo/nsi-wg" target="_blank">https://www.ogf.org/mailman/listinfo/nsi-wg</a><br>
</blockquote></div><br></div>