Re: [Int-area] PPP-to-ethernet
Mark Townsley <[email protected]> Sat, 16 Feb 2008 13:21:01 +0100
| Newsgroups | gmane.ietf.pppext |
|---|---|
| Message-ID | <[email protected]> |
Taking this to the pppext mailing list. - Mark Derick Winkworth wrote: > > All: > > > > Mulitple router vendors have a feature in which you can essentially > "bridge" a PPP link to an ethernet link. Cisco calls this feature > "local-switching." Juniper calls it "translational cross-connects." > > > > I find that both of these vendors implementations have their > shortcomings, and I think there could be some benefit to creating a > standard for accomplishing this. I am not aware of any standard for > doing this. > > > > My thought was essentially using the address field as defined in RFC > 1662. Differing addresses in this field would be used by the > translating router to forward traffic to differing neighboring routers > on the ethernet segment. So there would effectively be a > PPP-address-TO-Ethernet-MAC table. Neighboring routers would be > discovered via IGMP or IRDP (as Cisco kind of does it today, but "not > really") on the ethernet segment. Routers responding would have PPP > addresses created for them in a state-table, which is link-scoped. So > there would be a different table for every PPP link. > > > > At the IP layer, the remote-end PPP device would obviously have an > address that is native to the IP subnet of the ethernet link. > > Anyway, anyone have any thoughts on this? > > > > Derick > > > > > > > > > > > ------------------------------------------------------------------------ > Looking for last minute shopping deals? Find them fast with Yahoo! > Search. > <http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping> > > ------------------------------------------------------------------------ > > _______________________________________________ > Int-area mailing list > [email protected] > http://www.ietf.org/mailman/listinfo/int-area > _______________________________________________ Pppext mailing list [email protected] http://www.ietf.org/mailman/listinfo/pppext