[Nsi-wg] The NSA type and securityAttr elements.

[John MacAuley]

For example, would we better with something like the following simplified definition:

   <!-- A common set of parameters for all NSI operations. -->
   <xsd:complexType name="CommonParametersType">
      <xsd:sequence>
         <!-- NSA that requested the NSI operation (Requestor Agent). -->
         <xsd:element name="requesterNSA" type="xsd:anyURI" />
         
         <!-- NSA that services the NSI operation (Provider Agent). -->
         <xsd:element name="providerNSA" type="xsd:anyURI" />
         
         <!-- A transaction identifier provided by the requesting NSA used to correlate to an asynchronous response. -->
         <xsd:element name="transactionID" type="xsd:string" />
         
         <!-- Security attributes for the NSI operation. -->
         <xsd:element name="securityAttr" type="tns:AttributeSequenceType"/>
      </xsd:sequence>
   </xsd:complexType>

On 2011-03-13, at 12:54 PM, John MacAuley wrote:

> Peoples,
> 
> Based on the section "1.1 NSI message common attributes" of the Connection Services Architecture document I created the following common parameters structure in XML.  I dropped the NSIversion since the WSDL name space will identify the version, and I also dropped the ServiceType since the WSDL service endpoint definition will cover this value.  My question is with respect to the securityAttr element against each of the  requesterNSA and providerNSA elements.  What exactly will be contained in the securityAttr elements?  Should this instead be against the entire message?  I would like to understand the usefulness of these elements before committing them to the protocol specification.
> 
>    <!-- A common set of parameters for all NSI operations. -->
>    <xsd:complexType name="CommonParametersType">
>       <xsd:sequence>
>          <!-- NSA that requested the NSI operation (Requestor Agent). -->
>          <xsd:element name="requesterNSA" type="tns:NsaType" />
>          
>          <!-- NSA that services the NSI operation (Provider Agent). -->
>          <xsd:element name="providerNSA" type="tns:NsaType" />
>          
>          <!-- A transaction identifier provided by the requesting NSA used to correlate to an asynchronous response. -->
>          <xsd:element name="transactionID" type="xsd:string" />
>       </xsd:sequence>
>    </xsd:complexType>
> 
>    <xsd:complexType name="NsaType">
>       <xsd:sequence>
>          <xsd:element name="nsaAddress" type="xsd:anyURI"/>
>          <xsd:element name="securityAttr" type="tns:AttributeSequenceType"/>
>       </xsd:sequence>
>    </xsd:complexType>
> 
> Thank you,
> John.
> 
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/nsi-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/nsi-wg/attachments/20110313/e6afda5a/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1791 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/nsi-wg/attachments/20110313/e6afda5a/attachment.bin