I had originally thought the same until we went through the service definition exercise. The service schema included is related to the service being offered, but does not uniquely define it. For example, we may have multiple independent service definitions reusing the p2p schema for their service even though they are different technologies. This was why I did not use the service element name to uniquely identify the service description. The serviceType identifies the service description that tells you which elements are present in the request (and yes there can be more than one element). John On 2013-09-25, at 7:06 AM, Henrik Thostrup Jensen <htj@nordu.net> wrote:
Hi
Right now we have a construction in the reserve request (and confirmations), like hits:
<serviceType>http://services.ogf.org/nsi/2013/07/descriptions/EVTS.A-GOLE</serviceType> <p2psrv:evts> <capacity>200</capacity> <directionality>Bidirectional</directionality> <sourceSTP> <networkId>urn:ogf:network:nordu.net:2013</networkId> <localId>urn:ogf:network:nordu.net:2013:ps</localId> </sourceSTP> <destSTP> <networkId>urn:ogf:network:nordu.net:2013</networkId> <localId>urn:ogf:network:nordu.net:2013:uvalight</localId> </destSTP> <mtu>1500</mtu> <burstsize>5000000</burstsize> <sourceVLAN>1780</sourceVLAN> <destVLAN>1780</destVLAN> </p2psrv:evts>
AFAICT the serviceType and element name of the service (<p2psrv:evts>) has the exact same purpose: To tell the NSA which type of service is requested. Having serviceType specific to A-GOLE seems a bit weird. It is still an EVTS service. For getting endpoints in the A-GOLE one should just select the right STPs. AFAICT the serviceType field is completely redundant.
Best regards, Henrik
Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet
_______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg