Side_1_360

(Dana P.) #1

The associate subnetwork with subnetwork
action associates a composite subnetwork with
one or more component subnetworks in a sub-
network partitioning hierarchy. The caller shall
provide the identifiers of the composite subnet-
work and the component subnetwork(s) to be
associated. The action request is rejected if the
specified component subnetworks do not belong
to the same partitioning level.


The disassociate subnetwork from subnetwork
action disassociates a composite subnetwork
from one or more component subnetworks in a
subnetwork partitioning hierarchy. The caller
shall provide the identifiers of the composite
subnetwork and the component subnetwork(s) to
be disassociated. The action request is rejected if
any of the specified component subnetworks are
not associated with the composite subnetwork.


The report subnetwork creationaction reports
the creation of a subnetwork instance to a notifi-
cation receiver. The identifier of the created sub-
network is included in the report. The report
subnetwork deletion action reports the deletion
of a subnetwork instance to a notification re-
ceiver. The identifier of the deleted subnetwork
is included in the report.


The report association of subnetwork with sub-
networkaction reports the association of a com-
posite subnetwork with one or more component
subnetworks to a notification receiver. The iden-
tifiers of the involved subnetworks are included
in the report. The report disassociation of sub-
network from subnetwork action reports the dis-
association of a composite subnetwork from one
or more component subnetworks to a notifica-
tion receiver. The identifiers of the involved sub-
networks are included in the report.


4.2.2 Actions Related to Links
The create linkaction creates a link between two
connection termination point groups. The caller
shall provide the two link endpoints in the action
request. The provided endpoints must both be
associated with subnetworks. If the provided
endpoints are not acceptable, the action request
will be rejected by the provider. The caller may
define constraints on the directionality of the
requested link. The caller may provide a unique
identifier to be applied to the created link. If the
provided identifier is not unique within the layer
network domain, the action request will be
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 link has been created, the
provider returns a link identifier.


The delete linkaction deletes a link inside a
layer network domain. A request for link dele-


tion will be rejected if the specified link contains
link connections.

The report link creationaction reports the cre-
ation of a link instance to a notification receiver.
The identifier of the created link is included in
the report. The report link deletionaction reports
the deletion of a link instance to a notification
receiver. The identifier of the deleted link is
included in the report.

4.2.3 Actions Related to
Topological Links
The create topological linkaction creates a topo-
logical link between two connection termination
point groups. The caller shall provide the two
topological link endpoint in the action request.
The provided endpoints must both be associated
with subnetworks. If the provided endpoints are
not acceptable, the action request will be re-
jected by the provider. The caller may define
constraints on the directionality of the requested
topological link. The caller may provide a
unique identifier to be applied to the created
topological link. If the provided identifier is not
unique within the layer network domain, the
action request will be 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 topological
link has been created, the provider returns a
topological link identifier.

The delete topological linkaction deletes a topo-
logical link inside a layer network domain. A
request for topological link deletion will be
rejected if the specified topological link is asso-
ciated with a server trail.

The report topological link creationaction
reports the creation of a topological link instance
to a notification receiver. The identifier of the
created topological link is included in the report.
The report topological link deletionaction
reports the deletion of a topological link instance
to a notification receiver. The identifier of the
deleted topological link is included in the report.

4.2.4 Actions Related to Connection
Termination Points and Connection
Termination Point Groups
The create connection termination point group
action creates a connection termination point
group inside a layer network domain. The caller
may define constraints on the directionality of
the connection termination points that may be
associated with the requested connection termi-
nation point group. The caller may provide a
unique identifier to be applied to the created
connection termination point group. If the pro-
vided identifier is not unique within the layer
network domain, the action request will be
Free download pdf