SEP/SIP Semantics Differences

[italobusi]

TAPI 1.0 ServiceEndPoint (SEP) has been renamed as ServiceInterfacePoint (SIP) in TAPI 2.0

This Information Model change not only affects the name of the object but also its semantics and therefore could cause interoperability issues with some possible implementations of TAPI 1.0 SEPs.

SEP was indented to allow support multi-destination service requests (see attached slides):

• One SEP can map with one or more NEPs (Node Edge Points)

SIP is intended to model access/inter-domain links and provide information to the client controller to glue access/inter-domain links together

• One SIP can only map with one NEP (at least within a given topology), otherwise it will not provide sufficient information to glue together access/inter-domain links

sep-sip-differences.pptx

[amazzini]

This issue has been closed due to the lack of activity for more than one year. Please reopen it if follow up is necessary.