I assume you don't need an RCC to instruct, remote control or jump into a drone
Correct. RCC is not needed. You can do all the above even if you access the matrix via another device, like a commlink.
But IF you access the matrix via a RCC instead of for example a commlink then you can instruct multiple drones with the same instruction and you can jump between drones without first jumping out of them and you can share autosofts with them and you can reduce noise within your PAN etc.
However, I suppose that you still need to slave the drone to one of your devices.
No.
Drones and vehicles can be unlinked. They don't need to be specifically be part of your personal area network.
You can still instruct the autopilot of drones you own (or spoof commands to drones you don't own) no matter if they are part of your network or unlinked (or part of someone else's network).
But IF you are accessing the matrix via a RCC and if your drones are slaved to your RCC then you can instruct multiple drones at once with the same minor action and when your drones are executing your instruction it can utilize autosofts you are sharing to them from your RCC.You can still jump into drones (as long as you are connected to the matrix and have a control rig implant) you own no matter if they are part of your network or unlinked (and you can also do it with drones you are not the owner of as long as you have Admin access on the network the drone is part of or the drone itself in case it is unlinked - and if you are not the owner you also need to successfully take the Jump into Rigged Device action).
But IF you are accessing the matrix via a RCC and your drones are slaved to your RCC then you can jump between them without first taking an action to first jump out.So let's say I have a Rating 6 Cyberjack with D/F of 9/8. With Data Processing 9, I can slave 9 drones to it and all 9 drones benefit from my Data Processing 9, Firewall 8 (or however I rearrange my matrix attributes) as well as my mental Attributes for defense.
Right... So, in this edition the enemy hacker is typically not really targeting your specific drone. An enemy hacker that is trying to gain access on your drone will actually be brute forcing or probing your entire network. Your entire network including all devices within it will defend with your mental attributes and whatever firewall you have available in your network.
Now, this is where it gets weird
I guess this depend on your reading.
I read it as if you are accessing the matrix via your RCC (and control rig) the number of drones you get to slave is equal to the RCC's device rating x 3. Number of program slots you can load/run at the same time is equal to the Data Processing rating of the RCC.
I read it as if you are accessing the matrix via your Cyberdeck (and cyberjack) the number of drones you get to slave is equal to the Datajacks Data Processing rating. Number of program slots you can load/run at the same time is equal to the deck's Active Program Slots ratin.
I read it as if you are accessing the matrix via your commlink (and datajack) the number of drones you get to slave is equal to the Commlink's Data Processing rating. Number of program slots you can load/run at the same time is equal to the link's Active Program Slots ratin.
It does seem as if one of the advantages of accessing the matrix via a RCC is that you get to potentially slave more drones. The intention does not seem to be that you should be able to slave hundreds of drones at the same time ;-)
but otherwise it seems like a relatively cheap way to circumvent the Device Limit.
This was one of the ideas that was discussed at an earlier stage, but as we started to discuss the "networked" idea more in detail it was considered the overall more solid solution (as it still respect the overall slave limit on number of drones) so the daisy chain solution (within your own PAN) was mostly discarded and thus not included in the Matrix FAQ.
I.m.h.o., it would be simpler to say that the Device Limit only applies to the very specific case of drones/vehicles ...
The limit also applies to smart firing platforms and perhaps some other "smart" devices out there.... and it also applies to 'regular' devices that you might wish to protect but are perhaps too far away from the device you used to access the matrix with in order to be 'networked' ('Slaved' typically have better reach than 'Networked').
Maybe this is already the intention behind Banshee's rule, but in that case the wording could be clarified.
I can tell you that several wordings were clarified quite a lot compared to the first draft of the Matrix FAQ ;-)