> > > > > > > > WT-146 provided by DSLF is all about "IP sessions." So, > I presume > > > non-IP > > > > traffic is out of scope. > > > [...] > > > > > > Yes I think that's a fundamental problem. They're not > considering > > > the larger issues, and as a result some are asking for a poor > > > solution. > > > > While theoretically other protocols may be possible, practically DSL
> > service operators support only IP traffic for residential > users, and a > > majority of business L3 services too. As such the solution requested > for > > this space is precisely for that, no more, no less. > > I think there is some confusion here, perhaps on my part > (which is why I was asking the questions). > > Since we agree that there can be two machines of the same > subscriber on the same link, in at least one of the models > supported by WT-146 and IPAuth-18, what _prevents_ those two > machines from using a protocol other than IP? > > And since we agree that there can be two subscribers on the > same shared link, in at least one of the models supported by > WT-146 and IPAuth-18, what _prevents_ those two subscribers > from using a protocol other than IP? Ah, I get you now. Guess that this deserves some more explanation. Both of the scenarios you describe above would involve moving of traffic over what's considered as the "home" network segment, and forwarding restrictions are not in place on that. The subscriber line and/or DSL CPE is the demarcation point between trusted and non-trusted network segments, with an SP operator most often not desiring to control or restrict traffic on the non-trusted side (where one can presumably run IPX, Netbeui, etc). It is in the case of sending traffic to the trusted part that the operator wants to authenticate the senders, or only one of the senders (eg authenticate a video STB, but not a users PC device) that connect to the operators network using an L2 CPE. -Woj. > > -Dave > _______________________________________________ Int-area mailing list [email protected] https://www1.ietf.org/mailman/listinfo/int-area
