A Cisco view
This was sent to me by a Cisco employee:-
This article is not accurate on a number of fronts. TRILL is not needed for FCoE. the reason is simple: Spanning Tree (STP) is NOT used for FCoE. at all, ever.
Storage (FC) traffic (aka a VSAN) is mapped to a VLAN in the ethernet world (FCoE). VLAN(s) used for FCoE don't run STP at all. The FCoE switches themselves run a FC stack - just as they would if they were a FC switch - so provide all the typical FC services such as domain controller, FLOGI server, FC Nameserver etc. Among the things they run is FSPF - just as they would in a FC world - which provides the 'routing' topology for FC and any FCoE hops.
IEEE DCB switches which provide both LAN (Ethernet) and SAN (FCoE) transport will typically run STP (or Cisco FabricPath or whatever) on 'LAN' VLANs, and FSPF on 'SAN' VLANs.
Certainly there are possible advantages to running something 'newer' than Spanning Tree with blocked links - and this is what one can do in an evolutionary way today (e.g. Cisco virtual Port Channel aka vPC) and in a revolutionary manner in future (and this is the intent of what Cisco FabricPath is today and TRILL/Rbridges will be in future.)
But to say "you can't do FCoE without TRILL" is wrong. To say that 'storage people need to know ethernet' is equally wrong as all that has actually changed is that the frame format is FCoE, but the storage protocols and concepts are identical to what they are today (E_Ports, ISLs, zoning, NPV etc)