You need to clearly distinguish and separate these technologies: PTP, PRP, HSR, and the following things related to them:
- PTP-enabled switch
- PTP-enabled node (node = terminal device)
- PRP-enabled switch
- PRP-enabled node
- PRP-related redundancy box
- HSR-enabled switch
- HSR-enabled node
- HSR-related redundancy box
PTP-enabled 8-port Ethernet switch based on KSZ8999 and KSZ8462 -- i changed KSZ8463 you mentioned above to KSZ8462 because KSZ8462 has a parallel bus interface and eight KSZ8462s could be connected to a MPU/PCU with at least one parallel bus onboard.
PTP-enabled node typically implements only one Ethernet port and therefore has a trivial design -- KSZ8462/KSZ8463 could be used here solely.
PRP-enabled switch is a set of two common IEEE 802.1-compatible bridges (switches, named A and B) working in parallel to each other: they connect the same nodes but not each other in any case.
PRP-enabled node implements two independent ports named A and B, connected respectively to two independent (i.e. isolated from each other) networks or switches. Additional attention should be made when you design a PRP-enabled node: be careful if you select a switching IC to implement two Ethernet ports in your device--that IC must have its switching engine OFF after power-up and only controlling host (MCU/MPU) shall be source/destination of the frames at the device ports. Because of KSZ8462/KSZ8463 has its switching engine ON after power-up, KSZ8462/KSZ8463 is not suitable to implement a PRP-enabled node. The best way to implement a PRP-enabled node is to use an MPU/MCU with two independent MACs.
PRP-related redundancy box, or PRP RedBox is intended to connect a conventional (non-PRP-enabled) node or switch/network to a PRP-enabled network. It presents a PRP-enabled node at the PRP side and therefore has the same design restrictions listed above.
HSR-enabled switch acts like HSR-related RedBox described below. Note that HSR uses a daisy-chain-like topology, instead of a star topology used in PRP and conventional IEEE 802.1 networks.
HSR-enabled node implements two Ethernet ports to organize a daisy-chain which could be internally "connected" before the host (MCU/MPU) starts up. Therefore, KSZ8462/KSZ8463 (having its switching engine ON after power-up) is suitable to implement an HSR-enabled node and is a good way to do so.
HSR-related redundancy box is intended to connect a conventional (non-HSR-enabled) node or switch/network to an HSR-enabled network. It presents an HSR-enabled node at the HSR side and a conventional Ethernet node at the conventional side. Because HSR and IEEE 802.1 are not compatible, the two sides must be isolated from each other before the "translating means" in between of them starts up completely.
- To connect a PRP network to an IEEE 802.1 network, use a PRP RedBox.
- To connect an HSR network to an IEEE 802.1 network, use an HSR RedBox.
- To connect a PRP network to an HSR network, use a series of PRP RedBox and HSR RedBox.
PTP is an above-MAC layer protocol with a PHY layer hardware assistance, and therefore topology neutral (however, its accuracy is still topology/networking dependent): it could be used in any of IEEE 802.1, PRP, or HSR networks (LANs).
The exception to this is PTPv2 Transparent Clock functionality which requires support from the switch. Here the switch needs to adjust the PTPv2 Sync/Follow-Up packets with the time the packet has spent inside the switch. As the specific PTP protocol data location differs in case of plain Ethernet and HSR/PRP protocols, the switch needs to support PTPv2 Transparent Clock over HSR/PRP.