Trying to understand the ³marginal link² definition as well: Seems like ³marginal link² is associated with the IGP behavior (static, DV, link state)
I¹m assuming: If the L2 domain signals to the IGP that the link is ³down², the link is down. Even if it does it a lot. You need to ³hide² it from the IGP to create a ³marginal link². ³marginal link² does not say anything about user QOE, throughput or packet loss directly. A link that can hold an adjacency, but is dropping user traffic, would not be a ³marginal link² in this case. Good Link - Link that can form an IGP adjacency and hold it consistently in the absence of a L2 domain down state. Bad Link - Link that cannot form an IGP adjacency. It can be because of a L2 domain down state, or other cause. Marginal Link - Link that can form but not hold an IGP adjacency consistently in the absence of a L2 domain down state. So for a ³marginal link²: Hide L2 UP/DOWN state from the IGP (if desired) Form an adjacency Exchange any routing info Don¹t send any Hello¹s to actively take down the adjacency Break adjacency only if routing info updates can¹t be sent or DOWN state received Is this close to what a ³marginal link² is? John On 2/19/15, 12:04 PM, "Mikael Abrahamsson" <swm...@swm.pp.se> wrote: >On Thu, 19 Feb 2015, Juliusz Chroboczek wrote: > >> Babel solves this particular issue by a combination of three mechanisms: >> (1) automatically assigning a high metric to a marginal link, (2) using > >How is a "marginal link" defined/detected? > >-- >Mikael Abrahamsson email: swm...@swm.pp.se > >_______________________________________________ >homenet mailing list >homenet@ietf.org >https://www.ietf.org/mailman/listinfo/homenet > _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
