III.3.1 Introduction and Affect on Topological Restrictions
The automatic encapsulation option allows the topological rules of RFC 1195 to be broken. Automatic encapsulation effectively makes a node, or group of nodes appear to be able to forward packets that actually they cannot.
This is shown in Figure III-5.
Figure III-5
This group of nodes will now forward both IPv4 and CLNP packets, as long as the packets enter at point A or B, through one of the automatically encapsulating nodes.
The group of nodes may now safely be put into a dual area or a dual level-2 subdomain, as the pair of automatically encapsulating nodes will forward IPv4 packets by encapsulating them inside CLNP packets, so that they will be forwarded by the OSI-only NEs rather than being discarded.
A valid dual area may now look something like that shown in Figure III-6.
Figure III-6
Note that the OSI-only nodes must not be directly connected to one of the dual nodes that do not have the automatic encapsulation option. It is only the presence of the automatic encapsulating nodes that prevent IPv4 packets from being sent to an OSI-only node.
A dual node may be connected directly to an OSI-only node if it is also treated as an OSI-only node, as shown in Figure III-7.
Figure III-7
In this case the network acts as a dual network for packets going from point A to B, but IPv4 packets cannot reach the central dual node. This dual node is inside an OSI-only sub-network. This dual node will be able to forward CLNP packets only, and must be CLNS managed. There must be no other connections to the central dual node, as, if IPv4 packets were introduced at the central node, then they might be forwarded to an OSI-only node and be discarded.
III.3.2 Getting IP Traffic In and Out of the SDH Embedded Network
Share with your friends: |