Cell Relay Archive

[manfredi@arl.bna.boeing.com]

In article <674j17$f2a@milo.mcs.anl.gov>,
  curtis@anl.gov (Jeffrey S. Curtis) wrote:
>
> Paul Koning  <pkoning@xedia.com> writes:
> }RFC 1483 is (in practice) nothing more than the IP over ATM
> }encapsulation
> }spec.  (In theory it applies to other protocols too.)
> } [...]
> }(But note that only with LANE can you use IP multicast.)
>
> I run an RFC 1483 backbone over which I run IP, IPX, AppleTalk, DECnet,
> bridging, and IP Multicast.  I wouldn't touch LANE with a borrowed
> ten-foot pole, but that's beside the point.

Hmmm. While I can share your dislike of LANE on emotional grounds, you
must be doing something more than just RFC 1483, no? Or maybe you're only
using ATM PVCs in your ATM net? I agree that you don't need LANE to do IP
multicast. But you would need RFC 1577 + RFC 2022 (Classical IP over ATM
+ MARS).

> The original poster's comments from his vendor didn't seem *too* out
> of line (other than the comments about PNNI, which, as you correctly
> pointed out, is entirely unrelated to 1483/1577/LANE/etc.).  It comes
> down to semantics, really.  Perhaps by "legacy LANs could communicate
> over the ATM backbone" using RFC 1483, he was really saying, "your
> legacy LANs can connect to a router which has an ATM interface on an
> RFC 1483 backbone".  That seems like a reasonable statement for the
> vendor to make.

If I understand what you're saying here, I guess you're using ATM in a
sense, but it's basically being used only as dedicated links between
routers. I wonder if what you're doing couldn't be done with SONET pipes
alone?

Bert
manfredi@arl.bna.boeing.com

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet