Malaysia MTSFB IPv6 Technical Code: Comment by 7 Nov
Malaysia MTSFB IPv6 Technical Code Revision Opens for Comment Alongside Analogue Terminal Equipment Update
The Malaysia MTSFB IPv6 technical code is up for its second revision. The Malaysian Technical Standards Forum Bhd (MTSFB) has published two draft Technical Codes for public comment: MTSFB2607R2, "Internet Protocol version 6 (IPv6) – Equipment Compliance (Second Revision)", and MTSFB2612R2, "Specification for Analogue Terminal Equipment Connected to the Telecommunications Network (Second Revision)". Comments on both are open from 8 October to 7 November 2026.
Background: Technical Codes and equipment certification in Malaysia
In Malaysia, communications equipment is certified against Technical Codes developed by MTSFB and registered by the Malaysian Communications and Multimedia Commission (MCMC) under Section 95 of the Communications and Multimedia Act 1998. The two drafts say they were developed for equipment compliance under the Communications and Multimedia (Technical Standards) Regulations 2000, and a code only takes effect once MCMC registers it.
The IPv6 draft would cancel and replace MCMC MTSFB TC T013:2019, the first revision of the IPv6 code. The analogue terminal draft would replace SKMM MTSFB TC T001:2013, which covered terminal equipment connecting to the public switched telephone network (PSTN). Both drafts move general requirements out of the product codes and point instead to MCMC MTSFB TC T022, the baseline requirements code for communications equipment.
This follows the MTSFB consultation GMA Labs reported on 5 October 2026, which covered revised 5G codes and a new IoT interoperability code.
Key Changes in the Malaysia MTSFB IPv6 Technical Code
The draft applies to equipment with direct internet-facing functionality, whether it's hardware, a virtualised network function or software only. It sorts equipment into three groups, with examples in Annex B:
Terminal and host equipment, such as smartphones, cellular tablets, wearables, IoT devices, CCTV, POS terminals, smart meters, set-top boxes and satellite broadband equipment
Network elements, such as routers, Layer 3 switches, residential gateways, fixed wireless access gateways, wireless access points and SD-WAN edge devices
Network security elements, such as firewalls, VPN gateways, IDS/IPS and DDoS protection appliances
Interfaces that face the public internet must support native IPv6-only access, while still supporting IPv4-only and dual-stack access where that applies. Equipment directly connected to the public internet "shall be subjected to IPv6 compliance certification". Equipment used only inside a private network, with no public internet access, is excluded from both the IPv6-only and the certification requirements.
Technically, the draft rests on five core RFCs (8200, 4861, 4862, 8201 and 4443), with each test marked mandatory or optional. Testing follows the IPv6 Ready Core Protocols Test Specification, and devices must pass all mandatory tests. Transition mechanisms for IPv4 continuity, such as NAT64, DNS64 and 464XLAT, are covered too. Power supply, EMC, electrical safety, marking and language requirements are removed from the IPv6 code and now sit in TC T022.
Key Changes in the Analogue Terminal Equipment Code
The analogue draft widens the title and scope from PSTN equipment to analogue terminal equipment on networks that carry voice and data over circuit-switched or IP-based technologies, including VoIP, SIP and IMS. It adds connection through an optical network terminal (ONT) with an RJ11 interface, alongside direct connection to legacy analogue networks.
Requirements cover line polarity, ringing, impedance and DC characteristics, return loss, sending levels, DTMF and pulse dialling, automatic dialling and answering, and handset loudness ratings. The power fail and insulation resistance requirements are removed. Marking, interoperability, EMC and electrical safety move to TC T022, and equipment with analogue caller ID presentation (A-CLIP) must also meet TC T002.
What This Means for Manufacturers
Smartphones, routers, gateways, IoT devices and security appliances sold in Malaysia with public internet access will be tested against a refreshed IPv6 test set once the code is registered.
Test plans based on T013:2019 should be compared with the new RFC list and the latest IPv6 Ready test plans.
Products that only work inside private networks may fall outside IPv6 certification, so it's worth documenting how each product connects.
Analogue phones and similar terminals connected through fibre ONTs will be clearly in scope of the revised analogue code.
Baseline items such as EMC, safety and marking will be assessed under TC T022 rather than the product codes.
The drafts don't yet say how existing certificates will be treated, which is a useful point to raise in comments.
Certification Impact Summary
Area | Before | After | Impact level |
IPv6 code | MCMC MTSFB TC T013:2019 (first revision) | Second revision replaces it on registration | High |
IPv6 technical basis | First revision requirements | Five core RFCs, IPv6 Ready Core Protocols tests, mandatory tests must pass | High |
IPv6 scope | Internet-facing equipment | Terminal/host, network and security elements, incl. software-only and VNFs; private-only excluded | Medium |
Analogue code | SKMM MTSFB TC T001:2013 (PSTN terminals) | Analogue terminals on circuit-switched and IP-based networks, incl. ONT via RJ11 | Medium |
Analogue tests | Included power fail and insulation resistance | Both removed; A-CLIP equipment must meet TC T002 | Low |
EMC, safety, marking | Inside each product code | Moved to TC T022 baseline requirements | Medium |
Existing certificates | Valid under current codes | Not addressed in the drafts; to be confirmed | Medium |
Timeline and Required Actions
Key Dates
Date | Milestone |
8 October 2026 | Public comment opens on MTSFB2607R2 and MTSFB2612R2 |
7 November 2026 | Public comment closes for both drafts |
To be confirmed | MCMC registration under Section 95; the new codes take effect |
Required Actions for Manufacturers
List the products you sell in Malaysia that face the public internet or connect as analogue terminals.
Read both drafts on the MTSFB Technical Code page.
Compare your current IPv6 test results with the draft RFC list and IPv6 Ready test plans.
Check whether any products are private-network-only and record why.
Send comments through the MTSFB public comment form before 7 November 2026, including questions on existing certificates.
Plan for TC T022 baseline testing alongside the product codes.
Conclusion
The Malaysia MTSFB IPv6 technical code revision brings Malaysia's IPv6 certification in line with current RFCs and test plans, and the analogue terminal update reflects how phones now connect over fibre and IP networks. Neither has a registration date yet, so this is the window to comment and to check test plans. Contact our team for support with Malaysian equipment certification.
