HTTP/2 302 date: Mon, 14 Jul 2025 09:09:56 GMT content-type: text/html content-length: 143 location: https://get.ietf.org/implementation-report/report-rfc2421.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: 95efe256bf79a9b7-BLR alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Mon, 14 Jul 2025 09:09:57 GMT content-type: text/plain etag: W/"a1884a389671d6aca2d0d38e3e87a990" vary: Accept-Encoding server: cloudflare cf-ray: 95efe256f90fc190-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 VPIM v2 ? Interoperability Testing Results ------------------------------------------ by Glenn Parsons November 2001 Numerous vendors have claimed to support VPIM v2 (RFC 2421) and completed interoperability testing with other vendors? products. This is recorded in detail in the ?Conformance? section of the VPIM website (https://www.vpim.org or https://www.ema.org/vpim). The current list of vendors is available on the VPIM website at https://www.ema.org/vpim/conformance/declarations.html As of November 2001, the products that claimed to support VPIM are as follows: Number Vendor Product ------ ------------------------ -------------------------------- 98-001 Nortel Networks Meridian Mail Net Gateway (MMNG) 98-002 Nortel Networks Norstar Voice Mail (NVM) 98-003 Centigram Centigram series 6 Model 120S 98-004 AVT Corporation CallXpress 99-001 MJL Korea Ltd. Lark Series 10 99-002 Lucent Technologies MessagingLink 1.6.2 99-003 Nortel Networks CallPilot 1.0 99-004 Comverse Network Systems TRILOGUE INfinity 99-005 Comverse Network Systems Access NP 99-006 Unisys Corporation VPIM 1.0 Networking 99-007 Baypoint Innovations NuPoint Messenger Model 120S 00-001 Microsoft Corporation Exchange 2000 Server 00-002 Lucent Technologies Messaging Link 2.2 00-003 Nortel Networks Business Communications Manager 00-004 Glenayre MVP 01-001 Alcatel Alcatel 4635 The conformance information is separated into two sets of information. The first is a list of all the VPIM features supported by each. The current version is available on the VPIM website at https://www.ema.org/vpim/conformance/features.html The list of supported features, as of November 2001, is in the attached file (DOC.html). This indicates that all VPIM v2 features have been claimed to be implemented. The second set of information is a summary of the interoperability testing between the products. The majority of this testing was completed at an interop events hosted by the EMA, the last one was held in August 2000. Note that not all products listed have tested with each other. The current version is available on the VPIM website at https://www.ema.org/vpim/conformance/results/test_results.html The list of completed tests and results, as of November 2001, is in the attached file (DOI.html). This indicates that all VPIM v2 features have been proven to interwork with only a few noted exceptions. Some of these exceptions were the result of incorrect implementations, while a couple resulted in modifications to the VPIM v2 Draft Standard candidate. Besides numerous wording clarifications, the notable modifications were: * Removal of vCard due to incompatible implementations * Clarification of text handling based on implementations (do not send, but accept and maybe render)