From a797090f3687821ddec642cf1f2dc0d9d16f14f8 Mon Sep 17 00:00:00 2001 From: Ludovico Gerardi Date: Wed, 6 Nov 2024 21:22:20 +0100 Subject: [PATCH] Fix example of virtual circuit switching --- internetworking/switching.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/internetworking/switching.rst b/internetworking/switching.rst index 516ee00..90e576c 100644 --- a/internetworking/switching.rst +++ b/internetworking/switching.rst @@ -372,11 +372,11 @@ for this new connection. This entry is exactly the same as shown previously in :numref:`Table %s `. The main difference is that now the task of assigning an unused VCI value on the interface is performed by the switch for that port. In this example, the switch -picks the value 5. The virtual circuit table now has the following +picks the value 11. The virtual circuit table now has the following information: “When packets arrive on port 2 with identifier 5, send -them out on port 1.” Another issue is that, somehow, host A will need -to learn that it should put the VCI value of 5 in packets that it -wants to send to B; we will see how that happens below. +them out on port 1 with identifier 11.” Another issue is that, somehow, +host A will need to learn that it should put the VCI value of 5 in packets +that it wants to send to B; we will see how that happens below. When switch 2 receives the setup message, it performs a similar process; in this example, it picks the value 11 as the incoming VCI value.