[Nsi-wg] Open dynamicKL NSA
jeonghoon moon
otello90 at gmail.com
Mon Sep 5 20:10:39 CDT 2011
To Henrik Thostrup Jensen
SyntaxError(Cause : ProviderNSA) was not generated by URN problem.
This error was generated by the name space mismatch.
I want to show you a query message from autoBahn that was recently dumped by
our log system.
You can find out that ns2 and ns6 name spaces are defined as attributes of
the queryRequest element.
<?xml version = "1.0" ?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:queryRequest xmlns:ns2="
http://schemas.ogf.org/nsi/2011/07/connection/interface"
xmlns:ns3="http://www.w3.org/2001/04/xmlenc#"
xmlns:ns4="http://www.w3.org/2000/09/xmldsig#"
xmlns:ns5="urn:oasis:names:tc:SAML:2.0:assertion"
xmlns:ns6="
http://schemas.ogf.org/nsi/2011/07/connection/types">
<ns2:correlationId>9fa0a8ce-7d20-482a-8088-349d73c29d24</ns2:correlationId>
<ns2:replyTo>http://hemp.man.poznan.pl:9080/nsi/ConnectionRequesterPort
</ns2:replyTo>
<ns6:query>
<requesterNSA>urn:ogf:network:NSnetwork:Curacao</requesterNSA>
<providerNSA>urn:ogf:network:NSnetwork:Bonaire</providerNSA>
<operation>Summary</operation>
<queryFilter />
</ns6:query>
</ns2:queryRequest>
</soap:Body>
</soap:Envelope>
The following is a reservationRequest message generated by dynamicKL, which
has two name spaces defined as attributes of the reservationRequest element.
<ns5:reservationRequest xmlns:ns2="urn:oasis:names:tc:SAML:2.0:assertion"
xmlns:ns3="http://www.w3.org/2001/04/xmlenc#"
xmlns:ns4="http://www.w3.org/2000/09/xmldsig#"
xmlns:ns5="
http://schemas.ogf.org/nsi/2011/07/connection/interface"
xmlns:ns6="
http://schemas.ogf.org/nsi/2011/07/connection/types">
<ns5:correlationId>78729d97-8264-4a4b-ad53-8fec5ad529fb</ns5:correlationId>
<ns5:replyTo>
http://220.69.240.218:2000/kreonet/ConnectionServiceRequester</ns5:replyTo>
<ns6:reservation>
<requesterNSA>urn:ogf:network:NSnetwork:kreonet</requesterNSA>
<providerNSA>urn:ogf:network:NSnetwork:dynamicKL</providerNSA>
<reservation>
In case of your message, ns1 is defined in the Envelope element.
On the other hand, default name space("
http://schemas.ogf.org/nsi/2011/07/connection/types") is defined in the
reservation element.
Will you check out the usage of name spaces?
<SOAP-ENV:Envelope
xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/types"
xmlns:ns1="http://schemas.ogf.org/nsi/2011/07/connection/interface"
xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<ns2:Body>
<ns1:reservationRequest>
<ns1:correlationId>56561926991634759038257507539181676754</ns1:correlationId>
<ns1:replyTo>
http://orval.grid.aau.dk:7080/NSI/services/ConnectionService</ns1:replyTo>
<reservation xmlns="
http://schemas.ogf.org/nsi/2011/07/connection/types">
<requesterNSA>urn:ogf:network:nsa:OpenNSA-testclient</requesterNSA>
<providerNSA>urn:ogf:network:nsa:Martinique-DynamicKL</providerNSA>
<reservation>
Best regards, YoungWook Cha
===================================
http://ngn.andong.ac.kr
NGN Lab. Comp. Engineering Dept.
Andong National University
+82-10-2456-3237, +82-54-820-5714
===================================
----- Original Message -----
From: "Henrik Thostrup Jensen" <htj at ndgf.org>
To: "jeonghoon moon" <otello90 at gmail.com>
Cc: "Jerry Sobieski" <jerry at nordu.net>; "NSI Working Group" <nsi-wg at ogf.org>;
"JongUk Kong" <jonguk.kong at gmail.com>; "???(YoungWook Cha)" <
ywcha at andong.ac.kr>; "John MacAuley" <john.macauley at surfnet.nl>
Sent: Monday, September 05, 2011 9:29 PM
Subject: Re: [Nsi-wg] Open dynamicKL NSA
> Hi again, sorry for the spamming :-)
>
> (cc'ing John, as he is the expert and the nsi-wg mailing list appears not
> to be working currently).
>
> On Mon, 5 Sep 2011, Henrik Thostrup Jensen wrote:
>
>> This changes the error in the dynamicKL log to concern the providerNSA,
most
>> likely because I don't use the URN scheme (next on the todays todo list).
>
> I've updated my implementation to use the urn scheme, but I still get a
> ProviderNSA syntax error from the log (unfortunately there isn't any more
> information available).
>
> Here is the SOAP envelope:
>
> <SOAP-ENV:Envelope
> xmlns:ns0="http://schemas.ogf.org/nsi/2011/07/connection/types"
> xmlns:ns1="http://schemas.ogf.org/nsi/2011/07/connection/interface"
> xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
> <SOAP-ENV:Header/>
> <ns2:Body>
> <ns1:reservationRequest>
>
<ns1:correlationId>56561926991634759038257507539181676754</ns1:correlationId>
> <ns1:replyTo>
http://orval.grid.aau.dk:7080/NSI/services/ConnectionService</ns1:replyTo>
> <reservation xmlns="
http://schemas.ogf.org/nsi/2011/07/connection/types">
>
<requesterNSA>urn:ogf:network:nsa:OpenNSA-testclient</requesterNSA>
>
<providerNSA>urn:ogf:network:nsa:Martinique-DynamicKL</providerNSA>
> <reservation>
> <globalReservationId>gid-7087</globalReservationId>
> <description>Test Connection</description>
> <connectionId>conn-199</connectionId>
> <serviceParameters>
> <schedule>
> <startTime>2011-09-05T12:13:20Z</startTime>
> <endTime>2011-09-05T12:15:20Z</endTime>
> </schedule>
> [snip]
> (I still need to fix the correlationId)
>
> According to the schema, the type for NSAs is xsd:anyURI. I think
> "urn:ogf:network:nsa:Martinique-DynamicKL" should be a valid URI, but
> perhaps I am overlooking something.
>
>
> Best regards, Henrik
>
> Henrik Thostrup Jensen <htj at ndgf.org>
> NORDUnet / Nordic Data Grid Facility.
>
>
>
--
Jeonghoon Moon
Supercomputing Center
Dept.of Infrastructure Technology Development
KISTI(Korea Institute of Science and Technology Information)
Tel : +82-42-869-0578
Fax : +82-42-869-0589
H.P : +82-10-2534-6754
Skype : otello90
MSN : otellomoon at hotmail.com
"Expect Great Things from God
Attempt Great Things for God"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/nsi-wg/attachments/20110906/7aa241cf/attachment-0001.html
More information about the nsi-wg
mailing list