On Tuesday, August 13, 2013 11:07:07 AM Adam Vitkovsky wrote: > I'd like the BGP-LS to take over that role, with BGP-LS > as IGP you would not need to worry about scalability, so > you could still have a separate area (AS in case of > BGP-LS) per each aggregation island for administrative > purposes, however you could pass full SR information > into core AS and other aggregation island. So there > would be no need for yet another level of abstraction > i.e. RFC3017 and/or Opt.C. > > Also as we had the discussion about MPLS on the CPE > devices, in case of BGP-LS in the role of IGP&LDP you > could control specifically which prefixes and labels you > accept into your LSDB.
I don't dispute that BGP as a potential IGP will scale (look at iBGP today), but will it be quick? That's my concern. Then again, the BGP-LS draft is looking at extending the domain for TE, but who knows how quickly this will morph. Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
