Summary (from Erik Nordmark): > I still think the document should say "MUST prevent loops; > SHOULD run IEEE 802.1D to prevent loops" and then talk about > cases when the protocol is not needed. The one example we have > is the case of PPP (e.g. to a GGSN) where the probability of a > loop would be very small, so in that particular case there is no > need for 802.1D (and there might be other examples, but the 802.11 > scenario in the document isn't one of them).
Discussion so far: http://www.icir.org/dthaler/NDProxyIssues.htm#Issue 16 The problematic text in section 6 is: > Loop prevention can be done done by having the proxy implement the > Spanning Tree Algorithm and Protocol as defined in [BRIDGE] on all > proxy interfaces. Loop prevention is OPTIONAL, and is useful only > if the proxy can be deployed in an environment where physical loops > are possible. For example, in a cell phone which proxies between a > PPP dialup link and a local Ethernet interface, it is typically safe > to assume that physical loops are not possible and hence there is > no need to support the Spanning Tree Protocol (STP). > > If loop prevention is implemented, it is done as follows. Proposed replacement text: > An implementation MUST have some means of preventing loops. > Loop prevention SHOULD be done by having the proxy implement the > Spanning Tree Algorithm and Protocol as defined in [BRIDGE] on all > proxy interfaces, as described below. This mechanism is required > only if the proxy can be deployed in an environment where physical > loops are possible. For example, in a cell phone which proxies > between a PPP dialup link and a local Ethernet interface, it is > typically safe to assume that physical loops are not possible and > hence there is no need to support the Spanning Tree Protocol (STP). > > Loop prevention using STP is done as follows. -Dave -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
