rejected. The caller may also provide a user-
friendly label for his own use. This user label
need not be unique within the layer network
domain. When the connection termination point
group has been created, the provider returns a
connection termination point group identifier.
The delete connection termination point group
action deletes a connection termination point
group inside a layer network domain. The action
request will be rejected if the specified connec-
tion termination point group is associated with
any connection termination points, or if it termi-
nates a link or topological link.
The associate connection termination point with
connection termination point groupaction cre-
ates an association between a connection termi-
nation point and a connection termination point
group. The caller shall identify the entities to be
associated in the action request. The provider
will reject the action request if the specified con-
nection termination point is already associated
with a connection termination point group, or if
the directionality of the specified entities is not
compatible.
The disassociate connection termination point
from connection termination point groupaction
deletes an association between a connection ter-
mination point and a connection termination
point group. The caller shall identify the entities
to be disassociated in the action request.
The associate connection termination point
group with subnetworkaction creates an asso-
ciation between a connection termination point
group and a subnetwork. A connection termina-
tion point group may be associated with one or
more subnetworks, depending on the levels of
partitioning supported. This action makes the
connection termination point group available for
routing across the subnetwork. The caller shall
identify the entities to be associated in the action
request. The provider will reject the action
request if the specified connection termination
point group is already associated with the speci-
fied subnetwork.
The disassociate connection termination point
group from subnetworkaction deletes an associ-
ation between a connection termination point
group and a subnetwork. The caller shall identify
the entities to be disassociated in the action re-
quest. The provider will reject the action request
if the specified connection termination point
group is not associated with the specified sub-
network, or if the specified connection termina-
tion point group terminates a link or topological
link.
All the actions described above have a corre-
sponding reportaction that reports the event in
question to a notification receiver. In all cases,
the identifiers of all involved entities are
included in the report.5 Example: Delete
Topological Link
This chapter presents the enterprise, information
and computational viewpoints for the delete
topological linkaction as an example of the
modelling methodology. As pointed out in Sec-
tion 2.3, a topological link is a link supported
by a single trail in the server layer. In an MPLS
domain, for example, this implies that for an IP
link like the one in Figure 3 to be classified as a
topological link, it has to be supported by a sin-
gle LSP.The delete topological linkaction deletes a topo-
logical link inside a layer network domain. A
topological link may not be deleted if a server
trail is assigned to it.5.1 Enterprise Viewpoint
The enterprise viewpoint defines the policy of
the delete topological linkaction in terms of four
OBLIGATIONS. The model text is as follows:Delete topological link
“This action deletes a topological link inside a
layer network domain. No other resource is
deleted by this action.”ACTION_POLICYOBLIGATION inputTopologicalLinkId
“The caller shall provide the identifier of the
topological link to be deleted.”OBLIGATION noExistingTopologicalLink
“This action will fail if the topological link spec-
ified does not exist within the layer network
domain. In the case of failure, the provider shall
return the identifier in error.”OBLIGATION noServerTrail
“This action will fail if a server trail is still
assigned to the topological link specified.”OBLIGATION successTopologicalLinkDeleted
“When the action is successful, the provider
shall indicate this to the caller.”As stated by the action policy, the caller shall
provide the identifier of the topological link he
wants to delete (OBLIGATION inputTopologi-
calLinkId). The provider will of course reject the
action request if the specified link does not exist
(OBLIGATION noExistingTopologicalLink).
Additionally, the action request will be rejected
if the topological link in question has a server