HTTP/2 302 date: Mon, 14 Jul 2025 18:04:53 GMT content-type: text/html content-length: 143 location: https://get.ietf.org/implementation-report/report-rfc1490.txt cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT vary: Accept-Encoding server: cloudflare cf-ray: 95f2f1f5393cc143-BLR alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Mon, 14 Jul 2025 18:04:54 GMT content-type: text/plain etag: W/"2de4a3da678eb87ffa4135e3db589b2d" vary: Accept-Encoding server: cloudflare cf-ray: 95f2f1f56e4fc17c-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 The following was reported by Andy Malis Eleven companies responded to the call for RFC 1293 and 1490 implementation experience. Of the eleven, three asked that their information not be made public, and their responses have been summarized for informational purposes only. I will first list the RFC 1293 responses, and then the RFC 1490 responses. Thanks to all those that sent in responses. Companies are listed in alphabetical order. RFC 1490: Note that almost no companies implemented fragmentation, which is one of the reasons that it is being removed from the next revision. Another reason is that the Frame Relay Forum has a new (and greatly improved) separate fragmentation specification, FRF.12. Ascend Missing features: XID negotiation, fragmentation Interworked with: Cisco, Bay, 3Com Assured Access Missing features: none Interworked with: Cisco Bay Networks Missing features: fragmentation Interworked with: Cisco, 3Com Cabletron Systems Inc Missing features: XID is not complete Interworked with: Cisco, Motorola, AT&T, Newbridge Networks Cisco Missing features: fragmentation Interworked with: "quite a few" Note: Cisco reported past interoperability problems for non-IP protocols such as bridging, Appletalk, and IPX over Frame Relay with some other vendors. However, there are no currently open trouble reports on this, and the correspondent believes the problems have been resolved. Motorola Missing features: fragmentation, I-frames Interworked with: Cisco, Bay, 3Com, IBM Sync Research Missing features: fragmentation Interworked with: Sync, Cisco, IBM, 3Com, Bay, Xyplex, "and others" Xylan Missing features: 802.6 SMDS, source route bridging Interworked with: IBM (2210), Cisco (2500, 7000 series and other routers), Bay (Access Node and other routers), NSC (Borderguard), ACC (Nile) Of the other three respondents, two of the implementations were missing fragmentation, two were missing bridging, and the third incompletely implemented it, and one was missing I-frames. All three reported interoperating with Cisco, and two reported Bay, and one reported Newbridge and ACC as well.