IETF TRILL like CISCO OTV uses an extension of IS-IS as its routing protocol and because Fabric Path is presented as a pre IETF implementation, i assume FP and OTV share the same control plane, no?
On Mon, Jul 19, 2010 at 11:42 PM, Phil Bedard <[email protected]> wrote: > >From my understanding the initial FP is proprietary and uses 802.1ah > (mac-in-mac) encapsulation which is very different from TRILL which has its > own header format which is not MAC address based (canonical nicknames > instead.) Cisco has said they will support standard TRILL at a later date. > > Phil > > On Jul 19, 2010, at 4:42 PM, Maxwell Reid wrote: > > > Fabric Path is based on an proposed IETF standard known as TRILL. > > > > ~Max > > > > > > On Mon, Jul 19, 2010 at 12:56 PM, bas <[email protected]> wrote: > > > >> On Mon, Jul 19, 2010 at 3:08 PM, Manu Chao <[email protected]> > wrote: > >>> DRILL... > >>> > >>> *Will Fabric Path* be based on OTV? > >> > >> Have you read Cisco's pages on FP? > >> _______________________________________________ > >> cisco-nsp mailing list [email protected] > >> https://puck.nether.net/mailman/listinfo/cisco-nsp > >> archive at http://puck.nether.net/pipermail/cisco-nsp/ > >> > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
