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