MCMC MTSFB TC T013 :2019  
TECHNICAL  CODE  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
INTERNET  PROTOCOL  VERSION  6 (IPv6)  - 
EQUIPMENT  COMPLIANCE  
(FIRST REVISION)  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Developed by   Registered by  
  
 
 
 
Registered date:  
 
10 July 2019  
 
 
© Copyright 201 9 
MCMC MTSFB TC T013:2019  
    
iii  Development  of technical  codes  
 
 
The Communications  and Multimedia  Act 1998  (‘the Act’) provides  for Technical  Standards  Forum  
designated  under  section  184 of the Act or the Malaysian  Communications  and Multimedia  
Commission  (‘the Commission’)  to prepare  a technical  code.  The technical  code prepared pursuan t to 
section  185 of the Act shall consist  of, at least,  the requirement  for network  functionality,  network  
interoperability  and the promotion  of safety  of network  facilities.  
 
Section  96 of the Act also provides  for the Commission  to determine  a technical  code  in accordance  
with section  55 of the Act if the technical  code  is not developed  under  an applicable  provision  of the 
Act and it is unlikely  to be developed  by the Technical  Standards  Forum within  a reasonable  time.  
 
In exercise  of the power  conferred  by section  184 of the Act, the Commission  has designated  the 
Malaysian  Technical  Standards  Forum  Bhd (‘MTSFB’)  as a Technical  Standards  Forum  which  is 
obligated,  among  others,  to prepare  the technical  code  under  section  185 of the Act. 
 
A technical  code  prepared  in accordance  with section  185 shall not be effective  until it is registered  by 
the Commission  pursuant  to section  95 of the Act. 
 
For further  information  on the technical  code,  please  contact:  
 
Malaysian  Communications  and Multimedia  Commission  (MCMC) 
MCMC  Tower  1 
Jalan  Impact   
Cyber  6 
63000  Cyberjaya   
Selangor  Darul  Ehsan   
MALAYSIA  
 
Tel: +60 3 8688  8000  
Fax: +60 3 8688  1000  
http://www.mcmc.gov.my  
 
 
OR 
 
 
Malaysian  Technical  Standards  Forum  Bhd (MTSFB)  
Malaysian Communications & Multimedia Commission  (MCMC)  
Off Persiaran Multimedia  
Jalan Impact  
Cyber 6  
63000  Cyberjaya   
Selangor  Darul  Ehsan   
MALAYSIA  
 
Tel: +60 3 8320 0300  
Fax: +60 3 8322  0115  
http://www.mtsfb.org.my  
 
 
 
 
 MCMC MTSFB TC T013:2019  
i Contents  
Page  
 
Committee representation  ................................ ................................ ................................ .......................  ii 
Foreword  ................................ ................................ ................................ ................................ .................  iii 
 
1. Scope  ................................ ................................ ................................ ................................ .................  1 
2. Normative  references  ................................ ................................ ................................ .........................  1 
3. Abbreviations  ................................ ................................ ................................ ................................ ...... 2 
4. Terms and definitions  ................................ ................................ ................................ .........................  2 
4.1 Closed  Circuit  Television (CCTV)  ................................ ................................ ............................  2 
4.2 Internet Protocol Television Set Top Box (IPTV STB)  ................................ .............................  2 
4.3 Network Element (NE)  ................................ ................................ ................................ .............  2 
4.4 Network Service Element (NSE)  ................................ ................................ .............................  2 
4.5 Terminal/Host  ................................ ................................ ................................ ..........................  2 
4.6 White box switch  ................................ ................................ ................................ ......................  2 
5. General requirements  ................................ ................................ ................................ ........................  2 
5.1 Power supply requirements  ................................ ................................ ................................ ..... 2 
5.2 Power supply cord and main plu gs requirements  ................................ ................................ ... 3 
5.3 Electromagnetic compatibility requirements  ................................ ................................ ............  3 
5.4 Electrical safety requirements  ................................ ................................ ................................ . 3 
5.5 Marking requirements  ................................ ................................ ................................ ..............  3 
5.6 Language  ................................ ................................ ................................ ................................ . 3 
6. Equipment categories  ................................ ................................ ................................ .........................  4 
7. Segments  ................................ ................................ ................................ ................................ ...........  5 
8. Functional requirements  ................................ ................................ ................................ ....................  6 
9. IPv6 compliance requirement  ................................ ................................ ................................ ............  7 
10. Sample test report  ................................ ................................ ................................ ..............................  7 
 
Annex A     Abbreviation  ................................ ................................ ................................ ...........................  8 
Annex B     IPv6 functions  ................................ ................................ ................................ ......................  11 
Annex C     Request for Comments (RFC)  ................................ ................................ ............................  27 
Annex D     IPv6 com pliance requirement  ................................ ................................ ..............................  32 
Annex E     Sample of test report format  ................................ ................................ ................................  38 
 
Bibliography  ................................ ................................ ................................ ................................ ..........  39 
 
 
  MCMC MTSFB TC T013:2019  
ii Committee representation  
 
 
Numbering and Electronic Addressing Working Group  under  the Malaysian  Technical  Standards  
Forum  Bhd (MTSFB),  which  developed  this technical  code  consists  of representatives  from the 
following  organi sations:  
 
American M alaysian Chamber of Commerce   
Apple Inc  
Cisco  Systems  Malaysia  
Digi Telecommunications  Sdn Bhd 
Hewlett Packard Enterprise  
My6 Initiat ive Berhad  
Panasonic AVC Networks  
Persatuan Industri Komputer dan Multimedia Malaysia  
SIRIM QAS International Sdn Bhd  
Sony EMCS (M) Sdn Bhd  
Telekom  Malaysia  Berhad  
webe  digital sdn bhd 
 
  MCMC MTSFB TC T013:2019 
iii  Foreword  
 
 
This technical  code  for Internet  Protocol  version  6 (IPv6)  - Equipment  Compliance (First Revision)  
(‘this  Technical  Code’)  was developed  pursuant  to section  185 of the Act 588 by the Malaysian  
Technical  Standard  Forum  Bhd (MTSFB)  via its Internet  Protocol  version  6 Working  Group . 
 
This Technical  Code  was developed  for the purpose  of certifying  communications  equipment  under  
the Communications  and Multimedia  (Technical  Standards)  Regulations  2000.  
 
Major modifications in this revision are as follows:  
 
a) revision of normative references that are not applicable ; 
 
b) revised list and updated obsolete Request for Comments (RFC ); 
 
c) refined the category of equipment as non -exhaustive examples of  equipment which are subjected 
to this Technical Code ; 
 
d) 5-core compliance requirements for the categories of equipment as minimum specifications for 
compliance purposes ; and  
 
e) IPv6 Forum’s IPv6 Ready Test plans such as UNH -IOL Test Specification Core Protoc ol v4.0.7 is 
referred to for IPv6 Compliance Requirement.  
 
This Technical  Code  cancels and replaces  the MCMC MTSFB TC T013:2016, Specifications for Internet 
Protocol version 6 (IPv6) Compliant Equipment.  
 
This Technical  Code  shall continue  to be valid and effective  until reviewed  or cancelle d.MCMC MTSFB TC T 013:2019  
iv 
MCMC MTSFB TC T013:2019 
1  INTERNET  PROTOCOL  VERSION  6 (IPv6)  – EQUIPMENT  COMPLIANCE   
(FIRST REVISION)  
 
 
1. Scope  
 
This Technical Code defines the core technical functions , the category  of equipment  and compliance 
requirement for Internet  Protoc ol version  6 (IPv6). It is aims to assist various stakeholders f rom 
government and non -government bodies, agencies, organi sations as well as from the industry in 
ensuring  that any products with internet functionality to be used in Malaysia meets the minimu m 
capabilities to support an IPv6 ecosystem.  
 
This would be  in line with the national aspiration to accelerate the adoption of IPv6 services in Malaysia 
and to allow consumers access to application or services using IPv6.  
 
 
2. Normative  references  
 
The following  normative  references  are indispensable  for the application  of this Technical  Code . For 
dated  references,  only the edition  cited  applies.  For undated  references,  the latest  edition  of the 
normative  reference  (including  any amendments)  applies.  
 
MS 406 , Specification for voltages and frequency for alternating current transmission and distribution 
systems  
 
MS 589 -1, 13 A plugs, socket -outlets, adaptors and connection units - Part 1: Specification for rewirable 
and non -rewirable 13 A fused plugs  
 
MS 1578 , Specification for flat non -rewirable two -pole plugs , 2.5 A, 250 V with cord, for the connection 
of Class I I - Equipment for household and similar purpose s 
 
MS 2127,  Rubber insulated cables of rated voltages up to and including 450/750 V  
 
MS IEC 60038, IEC standard voltages  
 
MS IEC 60950 -1, Information technology equipment - Safety - Part 1: General requirements  
 
MS CISPR 22 , Information technology e quipment - Radio disturbance characteristics - Limits and 
methods of measurement  
 
IEC 60227 -5, Polyvinyl ch loride insulated cables of rated voltages up to and including 450/750 V - Part 
5: Flexible cables (cords)  
 
IEC 60245 -4, Rubber insulated cables - Rated voltages up to and including 450/750 V - Part 4: Cords 
and flexible cables  
 
BS 1363, Plug and socket -outlet 
 
BS EN 50075 , Specification for flat non -wirable two -pole plug s, 2,5 A 250 V, with cord, for the 
connection of Class II  - Equipment for household and similar purposes  
 
BS EN 50525 , Cable  
 
IPv6 Ready, Test Specification Core Protocols  
 
NIST SP500 -267, A Profile for IPv6 in the U.S. Government  MCMC MTSFB TC T013:2019  
2 3. Abbreviations  
 
For the purposes  of this Technical  Code,  the following  abbreviation s apply . 
 
See Annex A. 
 
 
4. Terms and definitions  
 
For the purpose of this Technical Code, the following terms and definitions apply.  
 
4.1 Closed  Circuit  Television  (CCTV)  
 
Known as video surveillance is the use of video cameras to transmit a signal to a specific place on a 
limited set of monitors.  
 
4.2 Internet Protocol Television  Set Top Box  (IPTV STB)  
 
An information appliance device th at provides Internet Protocol ( IP) network service from the service  
provider. Internet Protocol Television Set Top Box ( IPTV STB) is sold or leased directly by the service  
provider.  
 
4.3 Network Element (NE)  
 
Provide  network  connectivity,  control  IP protoc ols, packet  routing  and forwarding  from source/origin  
to a specific  destination.  
 
4.4 Network Se curity  Element (NSE)  
 
The primary  function s of Network Se curity  Element ( NSE) are to permit,  deny  and/or  monitor  traffic  
between  interface s in order  to detect  or prevent  potential  malicious  activity . 
 
4.5 Terminal/Host  
 
Devices  or elements,  which  are, network  participant  that sends  and receives  packets  but does  
not forward  them  on behalf  of others.  The primary  purpose  is to support  application  protocols  that 
are the source  and/or  destination  of IP layer  communication.  
 
4.6 White box  switch  
 
A network switch that is assembled from standard ised commodity parts. A white box switch may come 
pre-loaded with minimal software or it may be sold as a bare metal device.  
 
 
5. General requirements  
 
5.1 Power supply requirements  
 
Alternating Current (AC) adaptor shall not affect the capability of the equipment to meet this 
specification. The operating voltage shall be as follows : 
 
a) 240 V +  5 %, - 10 % and frequency 50  Hz ± 1  % as according to MS 406 ; or  
 
b) 230 V ±  10 % and frequency 50 Hz ±  1 % as according to MS IEC 60038  whichever  is current . 
 
Where external power supply is used, e.g. AC adaptor or battery, it shall not affect the capability of the MCMC MTSFB TC T013:2019 
3  equipment to meet this specificat ion. 
 
Adaptor shall be pre -approved by the relevant regulatory body before it can be used with the equipment.  
 
5.2 Power supply cord and main plugs requirements  
 
The equipment shall be fitted with a suitable and appropriate approved power supply cord and m ains 
plug. Both are regulated products and shall be pre -approved by the relevant regulatory body before it 
can be used with the equipment.  
 
The power supply cord shall be certified according to:  
 
a) MS 2127 ; or 
 
b) BS EN 50525 ; or 
 
c) IEC 60227 -5; or 
 
d) IEC 60245 -4. 
 
The main plug shall be certified according to:  
 
a) MS 589 -1 or BS 1363 for 13 A fused plugs; or  
 
b) MS 1578 or BS EN 50075 for 2.5 A, 250 V, flat non -rewireable  two-pole plugs . 
 
5.3 Electromagnetic compatibility requirements  
 
The equipment shall comply with the  limits for conducted disturbance at the mains terminals and 
telecommunication ports, and the limits for radiated disturbance defined in the MS CISPR 22  or 
equivalent.  
 
5.4 Electrical safety requirements  
 
The electrical safety of equipment shall comply wit h the MS IEC 60950 -1. The requirements in 
MS IEC 60950 -1 that are applicable to the equipment e.g. class of equipment, type of 
Telecommunication Network Voltage (TNV) circuit and types of components shall be identified and 
complied with.  
 
5.5 Marking requi rements  
 
The equipment shall be marked with the following information:  
 
a) supplier/manufacturer’s name or identification mark;  
 
b) supplier/manufacturer’s model or type reference; and  
 
c) other markings as required by the relevant standards . 
 
The markings shall be  legible, indelible and readily visible.  
 
5.6 Language  
 
All markings, software and related documents shall be in Bahasa Melayu or English language.  
 
 
 MCMC MTSFB TC T013:2019  
4 6. Equipment categories  
 
This Technical  Code  defines  the technical  requirements  for equipment  to be IPv6 compliant with the 
following functions:  
 
a) Terminal/Host ; 
 
b) Network Element (NE) ; and   
 
c) NSE.  
 
Any directly connected equipment to the service provider shall be qualified and undergo IPv6 
compliance certification.  
 
For the purpose of this Technical Code , ‘direct ly connected ’ means  equipment  that are assigned with 
IP address directly by an Internet service provider or cellular provider,  for clarity:  
  
a) Equipment that is assigned with IPv6 prefixes directly by an Internet service provider or cellular 
provider  are co nsidered ‘directly connected ’. The IPv6 prefixes could be assigned as dual -stack or 
native.   
 
b) Equipment that are assigned  with IPv6 prefixes directly by a service provider for  use within private 
network are considered ‘directly connected ’.  
 
c) Equipment that  does  not get IPv6 prefixes assigned directly by a service provider, instead from an 
NE or NSE with in a home or office local network  are considered not directly connected.  Please refer 
to the illustration in Figure 1.  
 
 
 
Figure 1 . Directly connected equi pment  
 
Annex B provides a  recommendation  of the RFC specifications which sh ould be fulfilled where 
applicable according to the primary function  of the equipment .  
 
NOTE: The list of RFCs for reference are listed in Annex C.  
 
MCMC MTSFB TC T013:2019 
5  However, f or compliance certif ication,  an equipment shall be declared based on its highest function and 
shall comply with the requirements in Annex D. As an example, if an equipment has a host and NSE as 
primary functions, then NSE shall be its primary function.  
  
An example (non -exhau stive) of equipment or elements which are subject to this Technical Code are 
as defined in Table 1.  
 
Table  1. Example of equipment  
 
Category  Equipment  
Terminal / 
Host a) Any other user terminals, User Equipment (UE) requiring IP connectivity  
b) Closed Circuit Te levision (CCTV)  
c) Internet of Things (IoT) devices that required  IP connectivity  
d) Internet Protocol Television Set Top Box ( IPTV STB)  
e) IP Camera  
f) Layer 2 switch and WiFi Access Point (AP)  
NE a) Broadband Remote Access Server (BRAS)  
b) Gateway GPRS Support Node (GGSN ) 
c) Internet Protocol Public  Automatic Branch Exchange ( IP PABX ) 
d) Layer 3 switch/router  
e) Load Balancer (LB)  
f) Mobility Management Entity (MME)  
g) Packet Data Network Gateway (P -GW) 
h) Radio Access Network (NodeB, eNodeB)  
i) Residential Gateway (RG)  
j) Serving Gateway (S -GW) 
k) Serving GPRS Support Node (SGSN)  
NSE a) Application Firewall (APFW)  
b) Firewall (FW)  
c) Intrusion Detection System (IDS)  
d) Intrusion Protection System (IPS)  
 
NOTES : 
 
1. Equipment  may apply  for multiple  categories.  
 
2. Equipment  may function  as Terminal /Host,  NE and/or  NSE. 
 
3. For equipment that are sharing the same  Operating System ( OS), testing report on one representative model 
is acceptable, per  equipment  type.  
 
4. IPv6 is also mandated for  cellular equipment (under Terminal/ Host) . However,  3rd Generation Partnership 
Project ( 3GPP ) standards shall take precedence over the requirements in Annex D  for cellular interfaces.   
 
 
7. Segments  
 
Segments refer to classes or categories in which IPv6 compliant equipment shall be deployed wherever 
applicable. For any given function o f an IPv6 compliant equipment, the model of equipment to cater for 
each segment shall be different as each segment has specific needs and specifications. Thus, it is 
important to be able to determine, for any IPv6 compliant equipment; its intended segment of 
deployment  prior to deliberating on the specifications listed in this Technical Code .  
 
 MCMC MTSFB TC T013:2019  
6 3 segments ar e as described below:  
 
a) Consumer  
 
The c onsumer  is referring  to the retail  end users as follows:  
 
i) fixed (wired or wireless broadband ); and 
 
ii) mobile cellular (3G/4G/5G).  
 
b) Enterprise  
 
i) Enterprise ; and  
 
ii) government  agencies . 
 
c) Service  providers  
 
i) Telcos  and celcos ; 
 
ii) network  service  provide r; and 
 
iii) internet  service  provider . 
 
 
8. Functional  requirements  
 
IPv6 functional  requireme nts are categori sed as Table 2 below.  
 
Table 2. IPv6 functional  requirements  
 
No IPv6 functional  Description  
1 IPv6 basic capabilities  Fundamental operation and configuration of the IP layer  
2 Addressing  Technical requirement for IPv6 address architectur e and 
Cryptographically Generated Addresses (CGAs)  
3 Transition mechanisms  Technical  requirement to adopt IPv6 in existing Internet Protocol 
version 4  (IPv4) infrastructure  
4 Link specific  Technical requirement for different link layer technologies  
5 Routing protocols  Technical requirement for interior and exterior gateway protocol  
6 Multicasting  Technical requirement for generalised multicast and configures  
options for Single Source Multicast (SSM) capabilities  
7 Network management  Technical requireme nt for Simple Network Management Protocol 
(SNMP) and its Management Information Bases (MIBs)  
8 Application requirement  Technical requirement for network services such as:  
a)  Domain Name System (DNS);  
b)  Dynamic Host Configuration Protocol (DHCP); and  
c)  Socket Application Programming Interface (API).  
9 Mobility  Technical requirement for Mobile IP (MIP) and configures options for 
Network Mobility (NEMO)  
 MCMC MTSFB TC T013:2019 
7  Table 2. IPv6 functional  requirements  (continued)  
 
No IPv6 Functional  Description  
10 Quality of se rvice  Technical requirement for Differentiated Service (DS) mechanisms 
in the router  
11 IP security  Technical requirement for IP Security  (IPSec ) and its key 
management protocol  
12 Network protection 
device  Technical requirement:  
a)  FW; 
b)  APFW ; 
c)  IDS; 
d)  IPS; and  
e)  Session Border Controller (SBC).  
 
The details  of its function s are shown  in Table B.1 of Annex  B.  
 
 
9. IPv6 compliance requirement  
 
Annex  D describes the  5-core compliance requirement across the 3 categories  of equipment in all 
segmen ts outlined in Clause 6 . There are 2 levels of compliance requirement  as follows:  
 
a) M is a mandatory  test case where the industry shall comply ; and  
 
b) O is an  optional  test case where the industry shall comply if the option is implemented . 
 
These requirement s are the minimum specifications for compliance purposes. The core compliance 
requirement for equipment in enterprise and service providers segments are the same thus have been 
combined for simplicity.  
 
 
10. Sample test report  
 
As IPv6 standards are still  evolving, exceptions shall be granted and/or test cases shall be updated  or 
invalidated based on  the development of global standards.  The latest version of the Test Specification 
Document from IPv6 Forum shall be accepted . 
 
Refer to IPv6 Forum’s IPv6 Read y Test plans such as UNH -IOL Test Specification Core Protocols 
v4.0.7 or higher for the detailed testing steps. The device shall comply  with and pass all the mandatory 
IPv6 tests as specified in Annex D . 
 
A sample of test report format is shown in Annex E  as an indication to interested stakeholders on 
information that should be presented for certification.  MCMC MTSFB TC T013:2019  
8 Annex A 
(informative ) 
 
 
Abbreviation  
 
 
3GPP  3rd Generation Partnership Project  
6PE IPv6 Provider Edge  
6VPE  IPv6 VPN Provider Edge Router  
AC Alternati ng Current  
AES Advanced Encryption Standard  
AH Authentication Header  
AP Access Point  
APFW  Application Firewall  
API Application Programming Interface  
ARP Address Resolution Protocol  
BGP  Border Gateway Protocol  
BGP -4 Border Gateway Protocol version 4  
BRAS  Broadband Remote Access Server  
CBC  Cipher Block Chaining  
CCM  Counter with CBC -MAC  
CCTV  Closed Circuit Television  
CGA  Cryptographically Generated Address  
DHCP  Dynamic Host Configuration Protocol  
DHCPv4  Dynamic Host Configuration Protocol versio n 4 
DHCPv6  Dynamic Host Configuration Protocol version 6  
DNS  Domain Name System  
DNSSEC  Domain Name System Security Extensions  
DS Differentiated Services  
ECN  Explicit Congestion Notification  
ESP Encapsulating Security Payload  
FDDI  Fibre  Distributed D ata Interface  
FW Firewall  
GCM  Galois/Counter Mode  
GGSN  Gateway GPRS Support Node  
GMAC  Galois Message Authentication Code  
GPRS  General Packet Radio Service  
GRE  Generic Routing Encapsulation  
HMAC  Hash Message Authentication Code  MCMC MTSFB TC T013:2019 
9  ICMP  Internet Contro l Message Protocol  
ICMPv6  Internet Control Message Protocol for IPv6  
IDS Intrusion Detection System  
IGMPv3  Internet Group Management Protocol version 3  
IGP Interior Gateway Protocol  
IKE Internet Key Exchange  
IoT Internet of Things  
IP Internet Protoc ol 
IPS Intrusion Protection System  
IPSec  IP Security  
IPSec -v3 IP Security  version 3  
IPTV STB  IPTV Set Top Box  
IPv4 Internet Protocol version 4  
IPv6 Internet Protocol version 6  
IP PABX  Internet Protocol Public Automatic Branch Exchange  
IS - IS Intermediate System to Intermediate System  
LB Load Balancer  
MAPOS  Multiple Access Protocol Over SONET/SDH  
MIB Management Information Base  
MIP Mobile Internet Protocol  
MIPv6  Mobile IPv6  
MLDv2  Multicast Listener Discovery version 2  
MME  Mobility Management Entity  
MODP  More Modular Exponential  
MPLS  Multi -Protocol Label Switching  
MTU  Multicast Listener Discovery  
NE Network Element  
NEMO  Network Mobility  
NSE Network Security  Element  
OSI Open Systems Interconnection  
OSPF  Open Shortest Path First  
OSPFv3  Open Shortest Path First version 3  
PHB Per Hop Behaviour  
PIM-SM Protocol Independent Multicast - Sparse Mode  
PKI Public Key Infrastructure  
PMTU  Path Maximum Transmission Unit  
PPP Point -to-Point Protocol  
P-GW Packet Data Network Gateway  MCMC MTSFB TC T013:2019  
10 RG Residentia l Gateway  
SBC Section Border Controller  
SEND  SEcure Neighbour Discovery  
SGSN  Serving GPRS Support Node  
SLAAC Stateless Address Autoconfiguration  
SNMP  Simple Network Management Protocol  
SNMPv3  Simple Network Management Protocol version 3  
SSM  Single S ource Multicast  
S-GW Serving Gateway  
TNV Telecommunication Network Voltage  
UDP  User Datagram Protocol  
UE User Equipment  
URI Uniform Resource Identifier  
WiFi Wireless Fidelity  
 
  MCMC MTSFB TC T013:2019 
11  Annex B 
(informative)  
 
 
IPv6 functions  
 
 
The following legends are appl ied for  the IPv6 functions as stipulated in Tables B.1 until B.11:  
 
a) M is mandatory ; 
 
b) O is optional ; 
 
c) MS is managed services ; 
 
d) c(M) is conditional mandatory (for specific reason or element) ; 
 
e) SLAAC is Stateless Address Autoconfiguration ; 
 
f) DHCP is Dynamic Ho st Configuration Protocol (for client) ; 
 
g) IPv4 is Internet Protocol version 4;  
 
h) MPLS is Multi -Protocol Label Switching;  
 
i) SSM is Single Source Multicast;  
 
j) SNMP is Simple Network Management Protocol;  
 
k) IPSec is IP Security;  
 
l) IPSec -v3 is IP Security version 3 ; 
 
m) MIP is Mobile IP;  
 
n) DS is Differentiated Services;  
 
o) FW is Firewall;  
 
p) APFW is Application Firewall;  
 
q) IDS is Intrusion Detection System; and  
 
r) IPS is Intrusion Protection System.  
 
 
 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
12 Table B.1. Basic IPv6 functions  
 
IETF 
specifica tion IPv6 basic func tions  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 8200  IPv6 specification  - M M - - M M - - M M M 
IPv6 packets: send, 
receive  - M M - - M M - - M M M 
IPv6 packet forwarding  - - M - - - M - - - M M 
Extension headers: 
processing  - M M - - M M - - M M M 
Hop-by-hop and 
unrecognised options  - M M - - M M - - M M M 
Fragment headers: 
send, receive, process  - M M - - M M - - M M M 
Destination options 
extensions  - M M - - M M - - M M M 
RFC 5 095 Deprecation of Type 0 
routing headers  MS - M - - M M - - M M M 
RFC 4443  Internet Control 
Message Protocol for 
IPv6 (ICMPv6 ) - M M - - M M - - M M M 
RFC 4884  Extended Internet 
Control Message 
Protocol  (ICMP ) for 
multi -part messages  MS - c(M) - - - - - - - - - 
RFC 8201  Path Maximum 
Transmission Unit 
(PMTU ) discovery for 
IPv6 - M M - - M M - - M M M 
Discovery protocol 
requirements  - M M - - M M - - M M M 
RFC 2675  IPv6 Jumbograms  - O O - - - - - - - - - 
RFC 4861  Neighbour discovery for 
IPv6 - M M - - M M - - M M M 
Router discovery  - M M - - M M - - M M M 
Prefix discovery  - M M - - M M - - M M M 
Address resolution  - M M - - M M - - M M M 
RFC 4861  NA and NS processing  - M M - - M M - - M M M 
RFC 4862  Duplicate address 
detection  - M M - - M M - - M M M 
Neighbour 
unreachability detection  - M M - - M M - - M M M 
Redirect functionality  - - M - - M M - - M M M 
RFC 5175  IPv6 router 
advertisement flags 
option  - M M - - - - - - - - - 
RFC 4191  Default router 
preference  - M M M - - - - - - - M MCMC MTSFB TC T013:2019 
13  Table  B.1. Basic IPv6 functions  (continued)  
 
IETF 
specification  IPv6 basic functions  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 3971  SEcure neighbour 
discovery  (SEND)  - O O - - M M - - M M M 
RFC 4 862 IPv6 SLAAC  
SLAAC  
M M M 
SLAAC  
M M M 
SLAAC  
M M M 
Creation of link local 
addresses  
SLAAC  
M M - 
SLAAC  
M M - 
SLAAC  
M M M 
RFC 4861  Duplicate address 
detection  
SLAAC  
M M - 
SLAAC  
M M - 
SLAAC  
M M M 
Creation of global 
addresses  
SLAAC  
M M - 
SLAAC  
M M - 
SLAAC  
M M M 
Ability to disable 
creation of global addrs  
SLAAC  
M M - 
SLAAC  
M M - 
SLAAC  
M M M 
RFC 4941  Privacy extensions for 
IPv6 SLAAC  
SLAAC  
M - - 
SLAAC  
M - - 
SLAAC  
M - - 
2nd context for MIP 
mobile node  - O - - - M - - - M - - 
RFC 3736  Stateless DHCP 
service for IPv6  
SLAAC  
M M - 
SLAAC  
M M - 
SLAAC  
M M M 
Dynamic Host 
Configuration Protocol 
version 6  (DHCPv6 ) 
DHCP  
M - - 
DHCP  
M - - 
DHCP  
M - - 
Ability to 
administratively disable  
DHCP  
M - - 
DHCP  
M - - 
DHCP  
M - - 
DHCP client functions  
DHCP  
M - - 
DHCP  
M - - 
DHCP  
M - - 
RFC 4361  Node -specific client IDs 
for Dynamic Host 
Configuration Protocol 
version 4  (DHCPv4 ) 
DHCP  
M - - 
DHCP  
M - - 
DHCP  
M - - 
 
 
 MCMC MTSFB TC T013:2019  
14 Table B.1. Basic IPv6 functions  (concluded ) 
 
IETF 
specification  IPv6 basic functions  Mass  Enterprise  Service provi der Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 3633  Prefix delegation  
DHCP  
M M - 
DHCP  
M M - 
DHCP  
M M M 
 
Table B.2.  IPv6 addressing  requirement  
 
IETF 
specification  IPv6 addressing  Mass  Enterprise  Service provider  Conditio n 
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 4291  IPv6 addressing 
architecture  - M M - - M M - - M M - 
RFC 4007  IPv6 scoped 
address 
architecture  - M M - - M M - - M M - 
Ability to manually 
configure 
addresses  - M M - - M M - - M M - 
RFC 4193  Unique local IPv6 
unicast address  - O O - - O O - - O O - 
RFC 3879  Deprecating site 
local addresses  - M M - - M M - - M M - 
RFC 6724  Default address 
selection for IPv6  - M M - - M M - - M M - 
Configurable 
selection policies  - M M - - M M - - M M - 
RFC 2526  Reserved IPv6 
subnet anycast 
addresses  - O O - - O O - - O O - 
RFC 3972  CGA  
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
RFC 4581  CGA extension 
field format  
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
RFC 4982  CGA support for 
multiple hash 
algos  
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
 
 MCMC MTSFB TC T013:2019 
15  Table B.2.  IPv6 addressing  requirement (continued)  
 
IETF 
specification  IPv6 addressing  Mass  Enterprise  Service provider  Condition  
Host 
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 5952  A 
recommendation 
for IPv6 address 
text - O O - - O O - - O O - 
RFC 6052  IPv6 addressing of 
IPv4/IPv6 
translators  - O O - - O O - - O O - 
RFC 6085  Address   
mapping   of   
IPv6   multicast 
packets on 
ethernet  - O O - - O O - - O O - 
NOTE : Condition is referred when VPN or other encryption protocol (e.g SEND) initiate from the specific devices 
is required. For protection devices such as firewall. It should able to work with CGA . 
 
Table B.3.  Transition  mechanism  requirements  
 
IETF 
specification  Transition 
mechanism  Mass network  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 4213  Basic transition 
mechanisms for 
IPv6 hosts and 
routers  
IPv4 
M M - 
IPv4 
M M - 
IPv4 
M M - 
RFC 4798  Connecting IPv6 
islands over IPv4 
MPLS  using IPv6 
Provider Edge 
(6PE) Routers  - - - - 
IPv4, 
MPLS  
- M - 
IPv4, 
MPLS  
- M - 
RFC 4659  IPv6 VPN 
Provider Edge 
Router (6VPE)  - - - - 
IPv4, 
MPLS  
- M - 
IPv4, 
MPLS  
- M - 
RFC 6146  NAT64  
IPv4 
- M M 
IPv4 
- M M 
IPv4 
- M M 
RFC 2784  Generic Routing 
Encapsulation  
(GRE ) - - O - - - O - - - O - 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
16 Table B.4.  Link specific  requirements  
 
IETF 
specification  Link specific  Mass network  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 2464  IPv6 over ethernet  
Condition  
M M M - M M M - M M M 
RFC 2467  IPv6 over Fibre 
Distributed Data 
Interface (FDDI ) - M M M - M M M - M M M 
RFC 3572  IPv6 over Multiple 
Access Protocol 
Over SONET/SDH  
(MAPOS ) - - M M - - M M - - M M 
RFC 4338  IPv6 IPv4 and 
Address 
Resolution 
Protocol ( ARP) 
packets over fibre 
channel  - M M M - M M M - M M M 
RFC 4944  IPv6 over IEEE 
802.15.4 
Networks  - - - - - - - - - - - - 
RFC 5072  IPv6 over Point -to-
Point Protocol  
(PPP) - M M M - M M M - M M M 
NOTE : Condition is applicable when the specified link technology is chosen as preferred choice . 
 
Table B.5.  Routing  protocol  
 
IETF 
specification  Routing protocol  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 5340  Open Shortest 
Path First (OSPF ) 
for IPv6  - - - - 
Condition  
- M M 
Condition  
- M M 
RFC 4552  Authentication/con
fidentiality for 
Open Shortest 
Path First version 
3 (OSPFv3 ) - - - - 
Condition  
- M - 
Condition  
- M - 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019 
17  Table B.5.  Routing  protocol  (continued)  
 
IETF 
specification  Routing protocol  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 1195  Use of Open 
Systems 
Interconnection 
(OSI) Intermediate 
System to 
Intermediate 
System (IS - IS) 
for routing in 
TCP/IP and dual 
environments  - - - - - - - - 
Condition  
- M - 
RFC 5187  OSPFv3 graceful 
restart  - - - - - - - - - - M - 
RIPng protocol 
applicability 
statement  - - - - 
Condition  
- 
c(M) 
- 
Condition  
- M - 
RFC 4271  Border Gateway 
Protocol version 4  
(BGP -4) - - - - 
Condition  
- 
c(M) 
- 
Condition  
- M - 
RFC 1772  Border Gateway 
Protocol  (BGP ) 
application in the 
Internet  - - - - 
Condition  
- M - 
Condition  
- M - 
RFC 4760  BGP multi -
protocol 
extensions  - - - - 
Condition  
- M - 
Condition  
- M - 
RFC 2545  BGP multi -
protocol 
extensions for 
IPv6 IDR  - - - - 
Condition  
- M - 
Condition  
- M - 
RRC 4659  BGP MPLS IP 
VPN extension for 
IPv6 VPN  - - - - - - - - - - M - 
NOTE : Condition for the Interior Gateway Protocol  (IGP) and hardware FW . 
 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
18 Table  B.6. Multicast  
 
IETF 
specification  Multicast  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 3810  Multicast Listener 
Discovery version 
2 (MLDv2) for 
IPv6 
SSM  
M M - 
SSM  
M M - 
SSM  
M M - 
RFC 3306  Unicast -prefix -
based IPv6 
multicast address  
Multicast  
M M - 
Multicast  
M M - 
Multicast  
M M - 
RFC 3307  Allocation 
guidelines for IPv6 
multicast addrs  
Multicast   
M M - 
Multicast  
M M - 
Multicast  
M M - 
RFC 4607  Source -specific 
multicast for I P 
SSM  
- - - 
SSM  
- - - 
SSM  
- - - 
RFC 4604  MLDv2 for source 
specific multicast  
SSM  
- - - 
SSM  
- - - 
SSM  
- - - 
RFC 7761  Protocol 
Independent 
Multicast - Sparse 
Mode (PIM-SM) 
Multicast -
Routing  
- - - 
Multicast -
Routing  
- - - 
Multicast -
Routing  
- - - 
NOTE : Condition when group management capability is required – IGMP . 
 
Table  B.7. Network  management   
 
IETF 
specification  Network 
management  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Network management r equirements  
RFC 3411  Simple Network 
Management 
Protocol version 3  
(SNMPv3 ) 
management 
framework  MS - - - 
SNMP  
M M M 
SNMP  
M M M 
RFC 3412  SNMP message 
process and 
dispatch  - - - - 
SNMP  
M M M 
SNMP  
M M M 
RFC 3413  SNMP 
applications  MS - - - 
SNMP  
M M M 
SNMP  
M M M 
 MCMC MTSFB TC T013:2019 
19  Table  B.7. Network  management  (continued)  
 
IETF 
specification  Network 
management  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 3413  Command 
responder  - - - - 
SNMP  
M M M 
SNMP  
M M M 
Notifi cation 
generator  - - - - 
SNMP  
- M - 
SNMP  
M M - 
RFC 3414  User -based 
security model for 
SNMPv3  - - - - 
SNMP  
M M - 
SNMP  
M M - 
Management information bases  
RFC 4293  MIB for the IP  - - - - 
SNMP  
M M - 
SNMP  
M M - 
RFC 4292  MIB for the IP 
forwarding table  - - - - 
SNMP  
 M - 
SNMP  
- M - 
RFC 4087  MIB for IP tunnels  - - - - 
SNMP 
& IPv4  
- M - 
SNMP 
& IPv4  
- M - 
RFC 4807  MIB or IPSec 
policy database 
configuration  - - - - 
SNMP &  
IPSec -v3 
- M - 
SNMP &  
IPSec -v3 
- M - 
RFC 4295  MIB for Mobile 
IPv6 (MIPv6 ) - - - - 
SNMP 
& MIP 
- M - 
SNMP 
& MIP  
- M - 
RFC 3289  MIB for DiffServ  - - - - 
SNMP 
& DS  
- M - 
SNMP 
& DS  
- M - 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
20 Table B.8. Application  
 
IETF 
specification  Application  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host 
NE 
NSE 
RFC 3596  DNS extensions 
for IPv6  
Condition  
M M M 
Condition  
M M M 
Condition  
M M M 
RFC 6891  Extension 
mechanisms for 
DNS (EDNS0)  
Condition  
M M M 
Condition  
M M M 
Condition  
M M M 
RFC 3226  Domain Name 
System Security 
Extensions 
(DNSSEC ) and 
IPv6 DN S MSG  
Condition  
M M M 
Condition  
M M M 
Condition  
M M M 
Size Reqs  
Condition  
M M M 
Condition  
M M M 
Condition  
M M M 
RFC 3986  Uniform Resource 
Identifier  (URI): 
generic syntax  
Condition  
M M M 
Condition  
M M M 
Condition  
M M M 
RFC 3493  Basic socket API 
for IPv 6 
Condition  
M - - 
Condition  
M - - 
Condition  
M - - 
RFC 3315  DHCPv6 functions 
(If host supports 
DHCP, it should 
also support 
DHCPv6)  
Condition  
O O O 
Condition  
O O O 
Condition  
O O O 
NOTES:  
 
1. Condition for the RFC 3596 and RFC 6891 is when the device suppo rts DNS.  
 
2. Condition for the RFC 3226 is when the device supports DNSSEC.  
 
3. Condition for the RFC 3986 is when the device supports URIs.  
 
4.  Condition for the RFC 3493 is when the device has exposed to APIs.  
 
5. Condition for the RFC 3315 is when the device supports DHCP.  
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019 
21  Table B.9. Quality of service  
 
IETF 
specification  Quality of 
Service  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 2474 
(PS) DiffServ Header 
Field  
Condition  
M M - DS M M - DS M M - 
RFC 3140 
(PS) Per Hop 
Behaviour (PHB) 
Encoding – 
DiffServ  
Condition  
M M - DS M M - DS M M - 
RFC 3168 
(PS) Explicit 
Congestion 
Notification  (ECN ) - - - - - - - - - - - - 
RFC 2597 
(PS) Assured 
forwarding  - - - - - - - - - - - - 
RFC 3246 
(PS) Expedited 
forwarding  - - - - - - - - - - - - 
RFC 3247 
(INF)  Supplementary EF 
PHB - - - - - - - - - - - - 
RFC 2475 
(INF)  DiffServ 
architecture  - - - - - - - - - - - - 
RFC 3260 
(INF)  New term and 
clarification - 
DiffServ  - - - - - - - - - - - - 
RFC 2 983 
(INF)  DiffServ and 
tunnels  - - - - - - - - - - - - 
RFC 4594 
(INF)  Config guidelines 
DiffServ  - - - - - - - - - - - - 
RFC 3086 
(INF)  DiffServ per 
domain behaviour  - - - - - - - - - - - - 
NOTES:  
 
1. Condition is DS and managed service.  
 
2. PS – Propos ed Standard .  
 
3. INF – Information . 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
22 Table  B.10. IPv6 security  
 
IETF 
specification  IPv6 security  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 2451  Encapsulating 
Security Payload  
(ESP) Cipher 
Block Chaining  
(CBC ) mode 
algorithms  - - - - - - - - - - - - 
RFC 3602  Advanced 
Encryption 
Standard  (AES) - 
CBC - - - - - - - - - - - - 
RFC 3686  AES-CTR - - - - - - - - - - - - 
RFC 4309  AES - Counter 
with CBC -MAC 
(CCM ) - - - - - - - - - - - - 
RFC 4106  AES- 
Galois/Counter 
Mode (GCM ) - - - - - - - - - - - - 
RFC 4543  AES- Galois 
Message 
Authentication 
Code (GMAC ) - - - - - - - - - - - - 
RFC 2404  Hash Message 
Authentication 
Code (HMAC ) -
SHA-1-96 - - - - - - - - - - - - 
RFC 4868  HMAC -SHA-256 - - - - - - - - - - - - 
RFC 3566  AES-XCBC -MAC -
96 - - - - - - - - - - - - 
RFC 4434  AES-XCBC -PRF-
128 - - - - - - - - - - - - 
Transition mechanisms requirements  
RFC 8247  Algorithm 
implementation 
requirements and 
usage guidance 
for the  IKEv2  - M M M - M M M - M M M 
RFC 4213  Transition 
mechanise for 
hosts and routers  - M M - - M M - - M M - 
RFC 4891  Using   IPsec   to   
secure   IPv6 -in   
IPv4 tunnels  
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
RFC 2473  Generic packet 
tunnelling in IPv6  
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- 
Condition  
c(M) 
c(M) 
- MCMC MTSFB TC T013:2019 
23  Table  B.10. IPv6 security  (continued)  
 
IETF 
specification  IPv6 security  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
RFC 4798  Connect ing IPv6 
islands over IPv4 
MPLS 6PE  
MPLS  
M M - 
MPLS  
M M - 
MPLS  
M M - 
ICMP  
RFC 4890  Recommendation
s for filtering 
ICMPv6 
messages in FW  - - - M - - - M - - - M 
IPSec -v3 
RFC 4301/ 
RFC 6040  Security 
architecture for 
the IP/ tunnelling 
of explicit 
congesti on 
notification  - O - - - - - - - - - - 
RFC 4303  ESP - O - - - - - - - - - - 
RFC 4302  Authentication 
Header (AH) - O - - - - - - - - - - 
RFC 3948  UDP 
encapsulation of 
ESP packets  - - - - - - - - - - - - 
RFC 8221  Cryptographic 
algorithms for 
ESP and AH  - O - - - - - - - - - - 
RFC 4308  Cryptographic  
suites  for IPSec  - - - - - - - - - - - - 
RFC 6379  Suite  B 
cryptographic  
suites  for IPSec  - - - - - - - - - - - - 
RFC 4809  Requirements  for 
an IPSec  cert 
management  
profile  - - - - - - - - - - - - 
 
 
 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
24 Table  B.10. IPv6 security  (concluded)  
 
IETF 
specification  IPv6 security  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
IKEv2  
RFC 7296  IKEv2  protocol  - M M M - M M M - M M M 
RFC 8247  Algorithm 
implementation 
requirements and 
usage guidance 
for the IKEv2  - M M M - M M M - M M M 
RFC 3526  More Modular 
Exponential 
(MODP ) DH 
groups  for Internet 
Key Exchange  
(IKE) - - - - - - - - - - - - 
RFC 5114  Additional  DH 
groups  for use 
with IETF  Stds - - - - - - - - - - - - 
RFC 4945  Internet  IPsec 
Public Key 
Infrastructure 
(PKI) Profile  of 
IKEv1,  IKEv2  & 
PKIX  - - - - - - - - - - - - 
Uses of cryptographic algorithms  
RFC 2410  NULL  encryption  - M M M - M M M - M M M 
RFC 8221  Cryptographic  
algorithms  for ESP 
and AH - M M M - M M M - M M M 
NOTE : Condition is tunnelling transition.  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019 
25  Table  B.11. Network  security  equipment  
 
NIST  
SP500 - 267 Network security  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
6.12.3.1  IPv6 connectivity  - - - M - - - M - - - M 
6.12.3.2  Dual stack  - - - M - - - M - - - M 
6.12.3.3  Administrative 
functionality  - - - M - - - M - - - M 
6.12.3.4  Authentication and 
authorisation  - - - M - - - M - - - M 
6.12.3.5  Security of  control 
and 
communications  - - - - - - - M - - - M 
6.12.3.6  Persistence  - - - M - - - M - - - M 
6.12.3.7  Logging and alerts  - - - M - - - M - - - M 
6.12.3.8  Fragmented 
packet handling  - - - M - - - M - - - M 
6.12.3.9  Tunnelled traffic 
handling  - - - M - - - M - - - M 
6.12.4.1.1  Port/protocol/addr
ess blocking  
FW or 
APFW  
- - M 
FW or 
APFW  
- - M 
FW or 
APFW  
- - M 
6.12.4.1.2  Asymmetrical 
blocking  
FW or 
APFW  
- - M 
FW or 
APFW  
- - M 
FW or 
APFW  
- - M 
6.12.4.1.3  IPSec traffic 
handling  
FW or 
APFW  
- - - 
FW or 
APFW 
- - M 
FW or 
APFW  
- - M 
6.12.4.1.4  Performance 
under load, fail -
safe 
FW or 
APFW  
- - M 
FW or 
APFW  
- - M 
FW or 
APFW  
- - M 
6.12.4.2.1  No violation of 
trust barriers  
APFW  
- - M 
APFW  
- - M 
APFW  
- - M 
6.12.4.2.2  Session traffic 
Auth 
APFW  
- - M 
APFW  
- - M 
APFW 
- - M 
6.12.4.2.3  Email, file filtering  
APFW  
- - M 
APFW  
- - M 
APFW  
- - M 
6.12.5.1.1  Known attack 
detection  
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
 MCMC MTSFB TC T013:2019  
26 Table  B.11. Network  security  equipment  (continued)  
 
NIST  
SP500 - 267 Network security  Mass  Enterprise  Service provider  Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
Condition  
Host  
NE 
NSE 
6.12.5.1.2  Malformed 
packets detection  
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
6.12.5.1.3  Port scan 
detection  
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
6.12.5.1.4  Tunnelled traffic 
detection  
IDS or 
IPS 
- - O 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
6.12.5.1.5  Logging and alerts  
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
6.12.5.1.6  Performance 
under load, fail -
safe 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
IDS or 
IPS 
- - M 
6.12.5.2.1  Intrusion 
prevention  
IPS 
- - M 
IPS 
- - M 
IPS 
- - M MCMC MTSFB TC T013:2019  
27 
 Annex C  
(informative)  
 
 
Request for Comments (RFC)  
 
 
Table C.1. Request for Comments (RFC) list  
 
RFC Number  Title 
RFC 1195  Use of OSI IS -IS for routing in TCP/IP a nd dual environments  
RFC 1772  Application of the Border Gateway Protocol in the Internet  
RFC 2404  The Use of HMAC -SHA-1-96 within ESP and AH  
RFC 2410  The NULL Encryption Algorithm and Its Use With IPsec  
RFC 2451  The ESP CBC -Mode Cipher Algorithms  
RFC 2464  Transmission of IPv6 Packets over Ethernet Networks  
RFC 2467  Transmission of IPv6 Packets over FDDI Networks  
RFC 2473  Generic Packet Tunneling in IPv6 Specification  
RFC 2474  Definition of the Differentiated Services Field (DS Field) in the IPv4 and  IPv6 
Headers  
RFC 2475  An Architecture for Differentiated Services  
RFC 2491  IPv6 over Non -Broadcast Multiple Access (NBMA) networks  
RFC 2507  IP Header Compression  
RFC 2508  Compressing IP/UDP/RTP Headers for Low -Speed Serial Links  
RFC 2526  Reserved IPv 6 Subnet Anycast Addresses  
RFC 2545  Use of BGP -4 Multiprotocol Extensions for IPv6 Inter -Domain Routing  
RFC 2597  Assured Forwarding PHB Group  
RFC 2675  IPv6 Jumbograms  
RFC 2710  Multicast Listener Discovery (MLD) for IPv6  
RFC 2711  IPv6 Router Alert Opti on 
RFC 2784  Generic Routing Encapsulation (GRE)  
RFC 2983  Differentiated Services and Tunnels  
RFC 3056  Connection of IPv6 Domains via IPv4 Clouds  
RFC 3086  Definition of Differentiated Services Per Domain Behaviors and Rules for their 
Specification  
RFC 3095  RObust Header Compression (ROHC): Framework and four profiles: RTP, UDP, 
ESP, and uncompressed  
RFC 3140  Per Hop Behavior Identification Codes  
RFC 3146  Transmission of IPv6 Packets over IEEE 1394 Networks  
RFC 3168  The Addition of Explicit Congestion  Notification (ECN) to IP  
RFC 3173  IP Payload Compression Protocol (IPComp)  
RFC 3226  DNSSEC and IPv6 A6 aware server/resolver message size requirements  MCMC MTSFB TC T013:2019 
28 Table C.1. Request for Comment (RFC) list (continued)  
 
RFC Number  Title 
RFC 3241  Robust Header Compr ession (ROHC) over PPP  
RFC 3246  An Expedited Forwarding PHB (Per -Hop Behavior)  
RFC 3247  Supplemental Information for the New Definition of the EF PHB (Expedited 
Forwarding Per -Hop Behavior)  
RFC 3260  New Terminology and Clarifications for Diffserv  
RFC 3 289 Management Information Base for the Differentiated Services Architecture  
RFC 3306  Unicast -Prefix -based IPv6 Multicast Addresses  
RFC 3307  Allocation Guidelines for IPv6 Multicast Addresses  
RFC 3315  Dynamic Host Configuration Protocol for IPv6 (DHCPv6 ) 
RFC 3411  An Architecture for Describing Simple Network Management Protocol (SNMP) 
Management Frameworks  
RFC 3412  Message Processing and Dispatching for the Simple Network Management 
Protocol (SNMP)  
RFC 3413  Simple Network Management Protocol (SNMP) Ap plications  
RFC 3414  User -based Security Model (USM) for version 3 of the Simple Network 
Management Protocol (SNMPv3)  
RFC 3493  Basic Socket Interface Extensions for IPv6  
RFC 3526  More Modular Exponential (MODP) Diffie -Hellman groups for Internet Key 
Exch ange (IKE)  
RFC 3542  Advanced Sockets Application Program Interface (API) for IPv6  
RFC 3566  The AES -XCBC -MAC -96 algorithm and its use with IPsec  
RFC 3572  Internet Protocol Version 6 over MAPOS (Multiple Access Protocol Over 
SONET/SDH)  
RFC 3590  Source Ad dress Selection for the Multicast Listener Discovery (MLD) Protocol  
RFC 3596  DNS Extensions to Support IP Version 6  
RFC 3602  The AES -CBC Cipher Algorithm and Its Use with IPsec  
RFC 3633  IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6  
RFC 3678  Socket Interface Extensions for Multicast Source Filters  
RFC 3686  Using Advanced Encryption Standard (AES) Counter Mode With IPsec 
Encapsulating Security Payload (ESP)  
RFC 3736  Stateless Dynamic Host Configuration Protocol (DHCP) Serv ice for IPv6  
RFC 3810  Multicast Listener Discovery Version 2 (MLDv2) for IPv6  
RFC 3843  RObust Header Compression (ROHC): A Compression Profile for IP  
RFC 3879  Deprecating Site Local Addresses  
RFC 3948  UDP Encapsulation of IPsec ESP Packets  
RFC 3956  Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address  
RFC 3963  Network Mobility (NEMO) Basic Support Protocol  
RFC 3971  SEcure Neighbor Discovery (SEND)  
 MCMC MTSFB TC T013:2019  
29 
 Table C.1. Request for Comment (RFC) list (continued)  
 
RFC Number  Title 
RFC 3972  Cryptographically Generated Addresses (CGA)  
RFC 3986  Uniform Resource Identifier (URI): Generic Syntax  
RFC 4007  IPv6 Scoped Address Architecture  
RFC 4022  Management Information Base for the Transmission Control Protocol (TCP)  
RFC 4038  Application Aspect s of IPv6 Transition  
RFC 4087  IP Tunnel MIB  
RFC 4106  The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload 
(ESP)   
RFC 4113  Management Information Base for the User Datagram Protocol (UDP)  
RFC 4191  Default Router Preferences and M ore-Specific Routes  
RFC 4193  Unique Local IPv6 Unicast Addresses  
RFC 4213  Basic Transition Mechanisms for IPv6 Hosts and Routers  
RFC 4271  A Border Gateway Protocol 4 (BGP -4) 
RFC 4283  Mobile Node Identifier Option for Mobile IPv6 (MIPv6)  
RFC 4291  IP Ve rsion 6 Addressing Architecture  
RFC 4292  IP Forwarding Table MIB  
RFC 4293  Management Information Base for the Internet Protocol (IP)  
RFC 4295  Mobile IPv6 Management Information Base  
RFC 4301  Security Architecture for the Internet Protocol  
RFC 4302  IP Authentication Header   
RFC 4303  IP Encapsulating Security Payload (ESP)  
RFC 4308  Cryptographic Suites for IPsec  
RFC 4309  Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating 
Security Payload (ESP)  
RFC 4338  Transmission of IPv6, IP v4, and Address Resolution Protocol (ARP) Packets over 
Fibre Channel  
RFC 4361  Node -specific Client Identifiers for Dynamic Host Configuration Protocol Version 
Four (DHCPv4)  
RFC 4362  RObust Header Compression (ROHC): A Link -Layer Assisted Profile for 
IP/UDP/RTP  
RFC 4380  Teredo: Tunneling IPv6 over UDP through Network Address Translations (NATs)  
RFC 4434  The AES -XCBC -PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)   
RFC 4443  Internet Control Message Protocol (ICMPv6) for the Internet Protoc ol Version 6 
(IPv6) Specification  
RFC 4489  A Method for Generating Link -Scoped IPv6 Multicast Addresses  
RFC 4543  The Use of Galois Message Authentication Code (GMAC) in IPsec ESP and AH   
RFC 4552  Authentication/Confidentiality for OSPFv3  
RFC 4581  Crypt ographically Generated Addresses (CGA) Extension Field Format  
RFC 4584  Extension to Sockets API for Mobile IPv6  MCMC MTSFB TC T013:2019 
30 Table C.1. Request for Comment (RFC) list (continued)  
 
RFC Number  Title 
RFC 4594  Configuration Guidelines for DiffServ Service Classes  
RFC 4 604 Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast 
Listener Discovery Protocol Version 2 (MLDv2) for Source -Specific Multicast  
RFC 4607  Source -Specific Multicast for IP  
RFC 4609  Protocol Independent Multicast - Sparse Mode (PIM -SM) Multicast Routing 
Security Issues and Enhancements  
RFC 4659  BGP -MPLS IP Virtual Private Network (VPN) Extension for IPv6 VPN  
RFC 4760  Multiprotocol Extensions for BGP -4 
RFC 4798  Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Router s 
(6PE)  
RFC 4807  IPsec Security Policy Database Configuration MIB  
RFC 4809  Requirements for an IPsec Certificate Management Profile  
RFC 4815  RObust Header Compression (ROHC): Corrections and Clarifications to RFC 
3095  
RFC 4861  Neighbor Discovery for IP  version 6 (IPv6)  
RFC 4862  IPv6 Stateless Address Autoconfiguration  
RFC 4868  Using HMAC -SHA-256, HMAC -SHA-384, and HMAC -SHA-512 with IPsec  
RFC 4877  Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture  
RFC 4884  Extended ICMP to Support Mu lti-Part Messages  
RFC 4890  Recommendations for Filtering ICMPv6 Messages in Firewalls  
RFC 4891  Using IPsec to Secure IPv6 -in-IPv4 Tunnels  
RFC 4941  Privacy Extensions for Stateless Address Autoconfiguration in IPv6  
RFC 4944  Transmission of IPv6 Packets over IEEE 802.15.4 Networks  
RFC 4945  The Internet IP Security PKI Profile of IKEv1/ISAKMP, IKEv2, and PKIX  
RFC 4982  Support for Multiple Hash Algorithms in Cryptographically Generated Addresses 
(CGAs)  
RFC 5014  IPv6 Socket API for Source Address Selectio n 
RFC 5015  Bidirectional Protocol Independent Multicast (BIDIR -PIM)  
RFC 5059  Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)  
RFC 5072  IP Version 6 over PPP  
RFC 5095  Deprecation of Type 0 Routing Headers in IPv6  
RFC 5114  Addit ional Diffie -Hellman Groups for Use with IETF Standards  
RFC 5121  Transmission of IPv6 via the IPv6 Convergence Sublayer over IEEE 802.16 
Networks  
RFC 5175  IPv6 Router Advertisement Flags Option  
RFC 5187  OSPFv3 Graceful Restart  
RFC 5213  Proxy Mobile IPv 6  
RFC 5214  Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)  MCMC MTSFB TC T013:2019  
31 
 Table C.1. Request for Comment (RFC) list (concluded ) 
 
RFC Number  Title 
RFC 5329  Traffic Engineering Extensions to OSPF Version 3  
RFC 5340  OSPF for IPv6  
RFC 5380  Hierarchical Mobile IPv6 (HMIPv6) Mobility Management  
RFC 5555  Mobile IPv6 Support for Dual Stack Hosts and Routers  
RFC 5569  IPv6 Rapid Deployment on IPv4 Infrastructures (6rd)  
RFC 5701  IPv6 Address Specific BGP Extended Community Attribute  
RFC 5795  The RObust Header Comp ression (ROHC) Framework  
RFC 5838  Support of Address Families in OSPFv3  
RFC 5844  IPv4 Support for Proxy Mobile IPv6  
RFC 5952  A Recommendation for IPv6 Address Text Representation  
RFC 5969  IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification  
RFC 6040  Tunnelling of Explicit Congestion Notification  
RFC 6052  IPv6 Addressing of IPv4/IPv6 Translators  
RFC 6085  Address Mapping of IPv6 Multicast Packets on Ethernet  
RFC 6146  Stateful NAT64: Network Address and Protocol Translation fro m IPv6 Clients to 
IPv4 Servers  
RFC 6275  Mobility Support in IPv6  
RFC 6333  Stateful NAT64: Network Address and Protocol Translation from IPv6 Clients to 
IPv4 Servers  
RFC 6379  Suite B Cryptographic Suites for IPsec  
RFC 6724  Default Address Selection for Internet Protocol Version 6 (IPv6)  
RFC 6846  RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC -TCP)  
RFC 6891  Extension Mechanisms for DNS (EDNS(0))  
RFC 7296  Internet Key Exchange Protocol Version 2 (IKEv2)  
RFC 7542  The Network Access Identifi er 
RFC 7761  Protocol Independent Multicast - Sparse Mode (PIM -SM): Protocol Specification 
(Revised)  
RFC 7915  IP/ICMP Translation Algorithm  
RFC 8200  Internet Protocol, Version 6 (IPv6) Specification  
RFC 8201  Path MTU Discovery for IP version 6   
RFC 8221 Cryptographic Algorithm Implementation Requirements and Usage Guidance for 
Encapsulating Security Payload (ESP) and Authentication Header (AH)  
RFC 8247  Algorithm Implementation Requirements and Usage Guidance for the Internet Key 
Exchange Protocol Vers ion 2 (IKEv2)  
 
 
 
 MCMC MTSFB TC T013:2019 
32 Annex D  
(normative)  
 
 
IPv6 compliance requirement  
 
 
Table D.1. Section 1 - RFC 8200 IPv6 specification  
 
RFC 8200  Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Group 1:  
IPv6 header  v6LC.1.1.1: Version field  M M M M M M 
v6LC.1.1.2: Traffic class non -zero - end node  M M M M M M 
v6LC.1.1.3: Traffic class non -zero - 
intermediate node (routers only)  - M M - M M 
v6LC.1.1.4: Flow label non -zero M M M M M M 
v6LC.1.1.5: Payload length  M M M M M M 
v6LC.1.1.6: N o next header after IPv6 
header  M M M M M M 
v6LC.1.1.7: Unrecognised next header  M M M M M M 
v6LC.1.1.8: Hop limit zero - end node  M M M M M M 
v6LC.1.1.9: Hop limit decrement - 
intermediate node (routers only)  - M M - M M 
v6LC.1.1.10: IP Forwarding  - source and 
destination address - intermediate node 
(routers only)  - M M - M M 
Group 2:  
Extension 
headers and 
options  v6LC.1.2.1: Next header zero  M M M M M M 
v6LC.1.2.2: No next header after extension 
header  M M M M M M 
v6LC.1.2.3: Unrecognised nex t header in 
extension header - end node  M M M M M M 
v6LC.1.2.4: Extension header processing 
order  M M M M M M 
v6LC.1.2.5: Option processing order  M M M M M M 
v6LC.1.2.6: Options processing, hop -by-hop 
options header - end node  M M M M M M 
v6LC.1.2. 7: Options processing, hop -by-hop 
options header - intermediate node  
(routers only)  - M M - M M 
v6LC.1.2.8: Option processing, destination 
options header  M M M M M M 
v6LC.1.2.9: Unrecognised routing type - end 
node  M M M M M M 
v6LC.1.2.10: Unrecogni sed routing type - 
intermediate node  M M M M M M 
Group 3:  
Fragmentation  v6LC.1.3.1: Fragment reassembly  M M M M M M 
v6LC.1.3.2: Reassembly time exceeded  M M M M M M 
v6LC.1.3.3: Fragment header M -bit set, 
payload length invalid  M M M M M M 
v6LC.1.3.4 : Stub fragment header  M M M M M M 
 MCMC MTSFB TC T013:2019  
33 
 Table D. 2. Section 2 - RFC 4861 neighbour  discovery for IP v6 
 
RFC 4861  Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Group 1: 
Address 
resolution and 
neighbour 
unreachability 
detection  Test v 6LC.2.1.1: On -link determination  - - - - M O 
Test v6LC.2.1.2: Resolution wait queue  - - - - M O 
Test v6LC.2.1.3: Prefix information option 
processing, on -link flag (hosts only)  - - - M O O 
Test v6LC.2.1.4: Host prefix list (hosts only)  - - - M O O 
Test v6LC.2.1.5: Neighbour solicitation 
origination, address resolution  - - - - M O 
Test v6LC.2.1.6: Neighbour solicitation 
origination, reachability confirmation  - - - - M O 
Test v6LC.2.1.7: Invalid neighbour 
solicitation handling  - - - - M O 
Test v6LC.2.1.8: Neighbour solicitation 
processing, no NCE  - - - - M O 
Test v6LC.2.1.9: Neighbour solicitation 
processing, NCE state INCOMPLETE  - - - - M O 
Test v6LC.2.1.10: Neighbour solicitation 
processing, NCE state REACHABLE  - - - - M O 
Test v6LC.2.1. 11: Neighbour solicitation 
processing, NCE state STALE  - - - - M O 
Test v6LC.2.1.12 Neighbour solicitation 
processing, NCE state PROBE  - - - - M O 
Test v6LC.2.1.13: Neighbour solicitation 
processing, IsRouterFlag (host only)  - - - M O O 
Test v6LC.2.1 .14: Neighbour solicitation 
processing, anycast (routers only)  - - - - M O 
Test v6LC.2.1.15: Invalid neighbour 
advertisement handling  - - - - O O 
Test v6LC.2.1.16: Neighbour advertisement 
processing, no NCE  - - - - O O 
Test v6LC.2.1.17: Neighbour adv ertisement 
processing, NCE state INCOMPLETE  - - - - O O 
Test v6LC.2.1.18: Neighbour advertisement 
processing, NCE state REACHABLE  - - - - O O 
Test v6LC.2.1.19: Neighbour advertisement 
processing, NCE state STALE  - - - - O O 
Test v6LC.2.1.20: Neighbo ur advertisement 
processing, NCE state PROBE  - - - - O O 
Test v6LC.2.1.21: Neighbour advertisement 
processing, R -bit change (hosts only)  - - - M O O 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019 
34 Table D. 2. Section 2 - RFC 4861 neighbour  discovery for IP v6 (continued)  
 
RFC 4861  Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Group 2: 
Router and 
prefix 
discovery  Test v6LC.2.2.1: Router solicitations (hosts 
only)  - - - M O O 
Test v6LC.2.2.2: Router solicitations, 
solicited router advertisement (hosts only)  - - - M O O 
Test v6LC.2.2.3: Host ignores router 
solicitations (hosts only)  - - - M O O 
Test v6LC.2.2.4: Router ignores invalid 
router solicitations (routers only)  - - - - M O 
Test v6LC.2.2.5: Router sends valid router 
advertisement (routers only)  - - - - M O 
Test v6LC.2.2.6: Router does not send 
router advertisements on non -advertising 
interface  
(routers only)  - - - - M O 
Test v6LC.2.2.7: Sending unsolicited router 
advertisements (routers only)  - - - - M O 
Test v6LC.2.2.8: Ceasing to be an 
advertising interface (routers only)  - - - - M O 
Test v6LC.2.2.9: Processing router 
solicitations (routers only)  - - - - M O 
Test v6LC.2.2.10: Router solicitation 
processing, neighbour cache (routers only)  - - - - M O 
Test v6LC.2.2.11: Default router switch 
(hosts only)  - - - M O O 
Test v6LC.2.2.12: Router advertisement 
processing, validity (hosts only)  - - - M O O 
Test v6LC.2.2.13: Router advertisement 
processing, cur hop limit  - - - M M O 
Test v6LC.2.2.14: Router advertisement 
processing, router lifetime (hosts only)  - - - M O O 
Test v6LC.2.2.15: Router advertisement 
processing, reachable time  - - - - O O 
Test v6LC.2.2.16: Router advertisement 
processing neighbour cache (hosts only)  - - - M O O 
Test v6LC.2.2.17: Router advertisement 
processing, IsRou ter flag (hosts only)  - - - M O O 
Test v6LC.2.2.18: Router advertisement 
processing, reachable time  - - - M O O 
Test v6LC.2.2.19: Router advertisement 
processing, on -link determination (hosts 
only)  - - - M O O 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
35 
 Table D. 2. Section 2 - RFC 4861 neighbour  discovery for IP v6 (concluded ) 
 
RFC 4861  Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Group 3: 
Redirect 
function  Test v6LC.2.3.1: Redirected on -link: valid 
(hosts only)  - - - M O O 
Test v6LC.2.3.2: Redirected on -link: 
suspicious (hosts only)  - - - M O O 
Test v6LC.2.3.3: Redirected on -link: invalid 
(hosts only)  - - - M O O 
Test v6LC.2.3.4: Redirected to alternate 
router: valid (hosts only)  - - - M O O 
Test v6LC.2.3.5: Redirected to alternate 
router: suspicious (h osts only)  - - - M O O 
Test v6LC.2.3.6: Redirected to alternate 
router: invalid (hosts only)  - - - M O O 
Test v6LC.2.3.7: Redirected twice (hosts 
only)  - - - M O O 
Test v6LC.2.3.8: Invalid option (hosts only)  - - - M O O 
Test v6LC.2.3.9: No destina tion cache entry 
(hosts only)  - - - M O O 
Test v6LC.2.3.10: Neighbour cache updated, 
no neighbour cache entry (hosts only)  - - - M O O 
Test v6LC.2.3.11: Neighbour cache updated 
from state INCOMPLETE (hosts only)  - - - M O O 
Test v6LC.2.3.12: Neighbou r cache updated 
from state REACHABLE (hosts only)  - - - M O O 
Test v6LC.2.3.13: Neighbour cache updated 
from state STALE (hosts only)  - - - M O O 
Test v6LC.2.3.14: Neighbour cache updated 
from state PROBE (hosts only)  - - - M O O 
Test v6LC.2.3.15: In valid redirect does not 
update neighbour cache (hosts only)  - - - M O O 
Test v6LC.2.3.16: Redirect - transmit 
(routers only)  - - - - M O 
Test v6LC.2.3.17: Redirect - receive (routers 
only)  - - - - M O 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019 
36 Table D. 3. Section 3 - RFC 4862  IPv6 stateless address autoconfiguration  
 
RFC 4862  Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Group 1: 
Address auto 
configuration 
and duplicate 
address 
detection  Test v6LC.3.1.1: Address autoconfiguration 
and test  - - - M M M 
Test v6LC.3.1.2: Receiving DAD neighbour 
solicitations and advertisements  - - - M M M 
Test v6LC.3.1.3: Validation of DAD 
neighbour solicitations  - - - M M M 
Test v6LC.3.1.4: Validation of DAD 
neighbour advertisements  - - - M M M 
Test v6LC.3.1.5: R eceiving neighbour 
solicitations for address resolution  - - - M M M 
Group 2: 
Router 
advertisement 
processing and 
address 
lifetime  Test v6LC.3.2.1: Global address 
autoconfiguration and DAD  - - - M O O 
Test v6LC.3.2.2: Address lifetime expiry 
(hosts only)  - - - M O O 
Test v6LC.3.2.3: Multiple prefixes and 
network renumbering (hosts only)  - - - M O O 
Test v6LC.3.2.4: Prefix -information option 
processing (hosts only)  - - - M O O 
Test v6LC.3.2.5: Prefix -information option 
processing, lifetime (hosts onl y) - - - M O O 
 
Table D. 4. Section 4 - RFC 8201  Path MTU  Discovery for IP v6 
 
Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Test v6LC.4.1.1: Confirm Ping  - - - M M M 
Test v6LC.4.1.2: Stored PMTU  - - - M M M 
Test v6LC.4.1.3: No n-zero ICMPv6 code  - - - M M M 
Test v6LC.4.1.4: Reduce PMTU on -link - - - M M M 
Test v6LC.4.1.5: Reduce PMTU off -link - - - M M M 
Test v6LC.4.1.6: Receiving Multicast Listener Discovery ( MTU ) 
below IPv6 minimum link MTU  - - - M M M 
Test v6LC.4.1.7: Inc rease estimate  - - - M M M 
Test v6LC.4.1.8: Router advertisement with MTU option (hosts 
only)  - - - M O O 
Test v6LC.4.1.9: Checking for increase in PMTU  - - - M M M 
Test v6LC.4.1.10: Multicast destination - one router  - - - M M M 
Test v6LC.4.1.11: Mult icast destination - two routers  - - - M M M 
 
 
 
 
 
 
 MCMC MTSFB TC T013:2019  
37 
 Table D. 5. Section 5 - RFC 4443 Internet Control Message Protocol ( ICMPv 6) 
 
Test Case  Consumer  Enterprise/Service 
Provider  
Host  NE NSE Host  NE NSE 
Test v6LC.5.1.1: Transmitting echo requests  - - - M M M 
Test v6LC.5.1.2: Replying echo requests  - - - M M M 
Test v6LC.5.1.3: Destination unreachable message generation  - - - M M M 
Test v6LC.5.1.4: Packet too big message generation (routers 
only)  - - - - M M 
Test v6LC.5.1.5: Hop limit exceeded (time exceed ed generation) 
(routers only)  - - - - M M 
Test v6LC.5.1.6: Erroneous header field (parameter problem 
generation)  - - - M M M 
Test v6LC.5.1.7: Unrecognised next header (parameter problem 
generation)  - - - M M M 
Test v6LC.5.1.8: Unknown informational mess age type  - - - M M M 
Test v6LC.5.1.9: Error condition with ICMPv6 error message 
(routers only)  - - - - M M 
Test v6LC.5.1.10: Error condition with multicast destination  - - - M M M 
Test v6LC.5.1.11: Error condition with non -unique source - 
unspecified  - - - M M M 
Test v6LC.5.1.12: Error condition with non -unique source - 
multicast  - - - M M M 
Test v6LC.5.1.13: Error condition with non -unique source - 
anycast  - - - M M M 
  
  
Annex E  
(informative ) 
 
 
Sample of test report format  
 
 
IPv6 Conformance Test R eport  
          
Evaluation Details  
Device Model    Firmware ver.    
Model Series   optional  Device Chassis  optional   
Tested By    
Checked By         
Evaluation Result Summary  
Section 1,  
Group  Test Category  Result  Remarks  
1.0 IPv6 Header  Not Tested    
2.0 Extension Headers and Options  Not Tested    
3.0 Fragmentation  Not Tested    
  
     
Test Approved by  Stamp and Date  Signature  
Name / Company / Title      
 
 
 
38 
MCMC MTSFB TC T013:2019 MCMC MTSFB TC T 013:2019  
39 
 Bibliography  
 
 
[1] 3rd Generation  Partnership  Project  (3GPP)  standard   
 
[2] Network Computing  
 https://www.networkcomputing.com/networking/white -box-switches -are-you-ready/1465296666  
 
[3] SDxCentral  
https://www.sdxcentral.com/cloud -converged -datacenter -whitebox -definitions -what -is-white -
box-networking/  
 
[4] Singapore  Internet  Protocol  version  6 (IPv6)  Profile  - IDA RS IPv6 Issue  1Rev  2, Jan 2012   
 USG  V6 
 
[5] TechTarget  
 https://searchsdn.techtarget.com/definition/white -box-switch  
 
[6] Transport Information Service  
 http://www.tis -gdv.de/tis_e/ware/maschinen/haushalt/haushaltsger aete.htm  
 
 
 MCMC MTSFB TC T 013:2019  
 Acknowledgement  
 
 
Members of the Numbering and Electronic Addressing Working Group  
 
Ms Azura Mat Salim ( Chairman ) Telekom Malaysia Berhad  
Mr Yan Kim Fui (Vice Chairman)  Cisco Systems Malaysia  
Ms Norkhadhra Nawawi (Secretariat)  Malaysian Tech nical Standards Forum Bhd  
Mr Lewis Walmesl ey-Browne  American Malaysian Chamber of Commerce  
Mr Eng Wee Chun  Apple Inc  
Mr Hanaffy Geoffrey Ramli  Digi Telecommunication Sdn Bhd  
Mr Chew Kian Kheong/  
Mr Isaac Chan/  
Mr Salim Mohamad Ghani  Hewlett Packard Ent erprise  
Mr Adil Hidayat R osli My6 Initiative Berhad  
Mr T. Vemalrajah  Panasonic AVC Networks  
Dr Dzaharudin Mansor  Persatuan Industri Komputer dan Multimedia Malaysia  
Mr Ahmad Faizan Pardi/  
Mr Wan Mohd Iidil/  
Ms Khairunnisa Ab. Halim  SIRIM QAS Internatio nal Sdn Bhd  
Dr Mun Wai Yuen  Sony EMCS (M) Sdn Bhd  
Mr Arief Khalid  Telekom Malaysia Berhad  
Mr Rosli Abdullah  webe digital sdn bhd