(Ipv6) Using MQX™ Real-Time Communication Suite (RTCS) FTF-SDS-F0041

Hands-On Workshop: Transition to Internet Protocol Version 6 (IPv6) Using MQX™ Real-Time Communication Suite (RTCS) FTF-SDS-F0041

Maclain Lobdell | Freescale Software Product Manager David Seymour | Freescale FAE

APR.2014

External Use Hands-On Workshop: Transition to Internet Protocol Version 6 (IPv6) Using MQX™ Real- Time Communication Suite (RTCS)

FTF-SDS-F0041 2 Hour Class Internet Protocol version 6 (IPv6) is designed to solve many of the problems of IPv4, including mobility, auto-configuration and address exhaustion. The worldwide transition to IPv6 is already in progress. This hands-on class will walk you through the capabilities of the new add-on for the MQX Real-Time Communication Suite (RTCS) that enables IPv6.

TM External Use 1 Session Introduction

The worldwide transition to IPv6 is coming. Are your embedded products going to be ready? • The number of devices connecting to the Internet is exploding. The trend cannot continue without IPv6. • The MQX RTCS (TCP/IP stack) is now ready for IPv6. In this class you will learn what is new and different about IPv6 vs IPv4, what are the benefits and challenges with IPv6 for embedded products, and how MQX RTCS with the new optional IPv6 extension can address those needs. • Mac Lobdell – MQX Product Manager • David Seymour - FAE

TM External Use 2 Session Objectives

• After completing this session you will be able to: − Understand the basics of IPv6 − Understand the IPv6 capabilities within MQX RTCS − Have experience with MQX applications and IPv6 networking See the simplicity of getting devices on IPv6 network

OR Embedded Device Laptop

Embedded Embedded Device Device

TM External Use 3 Agenda

• Quick Review of MQX Software Solutions • General Overview of IPv6 − Comparison of IPv6 to IPv4 − Special Considerations for Embedded Devices − Core Protocols of IPv6 − IPv6 Testing and Certification • Features of MQX™ Real-Time Communication Suite with new IPv6 extension − Supported Protocols − Dual Stack Capabilities − Memory Requirements − Cost and Support • Example IPv6 Applications − Hands-on with Examples • Session Summary & Additional Q/A

TM External Use 4 Agenda

TM External Use 5 Download at: www.freescale.com/mqx Freescale MQX™ Software Solutions - $Free

Product Features Commercial-grade MCU software platform at no cost • MQX™ Real Time Operating System Kernel with optional support packages • Deterministic multi-tasking preemptive scheduler • Extensive inter-task synchronization, message Enabling the development of passing, and much more connected and intelligent • MQX™ Real Time Communication Suite applications of the future Now with optional IPv6 add-on package • Broad networking protocol support (TCP,UDP, ICMP, HTTP, DHCP, FTP, Telnet, …) Customer Application • Fully re-entrant, responsive, designed for embedded systems • MQX™ File System • Embedded FAT file system compatible with

Stacks FAT-12, FAT-16, or FAT-32 file systems Specific (TCP/IP, USB) Application Middleware • MQX™ USB Host/Device Stack Libraries Operating • (DSP, Math, USB 1.0/2.0; low-/full-/high-speed Software and Hardware Evaluation & Dev Tools Encryption) System • BSP, Drivers & Board Support Packages Bootloader HAL • Pre-configured MQX Kernel, stacks, and peripheral drivers for Freescale HW MCU Hardware

TM External Use 6 High-Level RTOS Landscape Linux QNX VxWorks WinCE MQX SMX

Nucleus RTX Process-Based Integrity RTXC RTOS/OS ThreadX CMX eCOS FreeRTOS uCOS-II

(Memory Footprint) (Memory MQX Lite Full Featured Thread-Based RTOS Each “process” CMX-Tiny has own memory space. More Multi-media and sophisticated Basic Featured More features. More applications. Thread-Based RTOS integrated protocol

Potential Size stacks and middleware. Bare Metal Basic features. Some Low to high footprint. (No OS) protocol stacks and middleware. Low to medium footprint.

Features, Performance, Sophistication

TM External Use 7 Freescale MQX Growing in Popularity!

#1 Freescale MQX 3rd Most Popular MCU RTOS in #2 2013 UBM Survey #3

Freescale MQX 65K+ Downloads 19K+ Unique Users

TM External Use 8 What's New in MQX RTOS 4.1

New Board Support Package − TWR-K21F120M (Kinetis K21 Tower System Module) New Features and Updates − Enhanced tools support for CodeWarrior, IAR, Keil, ARM® DS-5™, and GNU tools for ARM® − Vybrid BSP Updates Drivers added or extended: eDMA. DSP codec, FTM Quadrature decoder, DCU, NAND flash file system driver, SAI, eSAI, ASRC, UART w/ eDMA, and FlashX w/ QuadSPI. − Extended DMA support in Kinetis and Vybrid BSPs SPI, SAI, & eSAI drivers w/ eDMA; eSDHC w/ ADMA − Other Enhancements Updated LWADC, RTC, Hardware Timer w/ Low Power Timer (LPT), Kinetis Flash Swap, NAND Flash File System (FFS) added. − Software compatibility improvement MQX custom types replaced w/ standard C99 types ARM DS-5

TM External Use 9 PLATFORM MQX 4.1 MQX 4.1 Board Support Packages VBYRID TWR‐VF65GS10 (M4&A5) √ AUTOEVB (M4&A5) √ • 24 Complimentary BSPs covering all Kinetis K, KINETIS Vybrid, and select ColdFire and Power Families TWR‐K20D50M √ TWR‐K20D72M √ • Numerous additional BSPs for legacy devices TWR‐K21D50M √ available free of charge in earlier MQX versions TWR‐K21F120M √ TWR‐K40X256 √ • Other BSPs available for purchase for other TWR‐K40D100M √ architectures TWR‐K53N512 √ TWR‐K60D100M √ • MQX Lite also available for all Kinetis K, L, & TWR‐K60F120M √ some E Series in Processor Expert TWR‐K60N512 √ TWR‐K64F120M * KWIKSTICK (K40) √ TWR‐K70120M √ COLDFIRE V1‐V4 TWR‐MCF51JF √ TWR‐MCF52259 √ * MQX 4.1-based standalone release TWR‐MCF54418 √ available separate from main installer POWER ARCHITECTURE TWR‐PXD10 √ TWR‐PXS20 √ TWR‐PXS30 √ TWR‐PXN20 √

TM External Use 10 What's New in MQX™ Real-Time TCP/IP Communication Suite (RTCS)

• New HTTP server implementation – HTTPSRV. − It is 18 times faster than old MQX 4.0 HTTPD. − Allows parallel CGI processing. − More robust User code (CGI/SSI) is run in separate task. Each CGI/SSI can run in separate task. Each connection is processed independenly. • New FTP server implementation – FTPSRV. − Allows multiple connections. − Allows multiple parallel file transfers. − Full IPv6 support (EPSV and EPRT commands). − More robust

TM External Use 11 MQX 4.1 RTCS TCP/IP Stack IPv6 Ready Get ready for the worldwide transition to the next generation of the Internet (IPv6), but retain support for the Internet of today (IPv4) New IPv6 add-on for purchase − IPv6 Ready (Phase-2) Core-Protocols Certified − Configure for single stack (IPv6) or dual stack (IPv4 + IPv6) − Supports stateless auto-configuration, network auto-discovery, and the massive address extensibility of IPv6 − Supported protocols - IPv6, ICMPv6, ND, TCP/UDPv6, Sockets, SMTP Client, HTTP Server, MLD Discover, FTP Server, FTP Client, & DNS − Protocols planned for future – DHCP, Telnet, TFTP, SNMP, PPP − Add IPv6 for about 21 KB of additional ROM code − Supports all MCU platforms supported by RTCS in MQX 4.1 − Available for download at www.freescale.com/mqx/ipv6

TM External Use 12 Freescale MQX Real-Time Communication Suite (RTCS )

*SNMP *SSH *XML SMTP *POP3 HTTP (v3) Simple and Scalable SNMP • Small, configurable size Telnet FTP TFTP DNS SNTP (v1, v2) conserves memory space for application *SSL • Allows developers to add web servers, e-mail, network Sockets DHCP management, security, and routing to their designs

Powerful and Integrated TCP UDP ICMPv4 / **ICMPv6 IGMP **ND **MLDv1 • Developed to be tightly integrated with MQX RTOS NAT IPv4 / **IPv6 CIDR Ultimate Value • Includes FTP, Telnet, DHCP, IP-E IPCP PAP CHAP CCP LCP DNS servers and clients, and SNMP client

ARP PPP * 3rd Party add-on ** FSL IPv6 add-on Ethernet Serial HDLC New Updated TM External Use 13 Agenda

• General Overview of IPv6 − Comparison of IPv6 to IPv4 − Special Considerations for Embedded Devices − Core Protocols of IPv6 − IPv6 Testing and Certification • Features of MQX™ Real Time Communication Suite with new IPv6 extension − Supported Protocols − Dual Stack Capabilities − Memory Requirements − Cost and Support • Example IPv6 Applications − Hands-on with Examples

TM External Use 14 Terminology

Nodes

Neighbors

Host Host

Host Intra-subnet Router Router

Link

Subnet

TM External Use 15 Terminology

TM External Use 16 Terminology Host/Node=Any system with an IPv6 address and interface that is configured for IPv6 support.

TM External Use 17 IPv6 router=A node that forwards Terminology IPv6 packets. At least one of the router's interfaces must be configured for IPv6 support. An IPv6 router can also advertise the registered IPv6 site prefix for the enterprise over the internal network.

TM External Use 18 Boundary router=The router at the Terminology edge of a network that provides one end of the IPv6 tunnel to an endpoint outside the local network. For the external network, the router can have an IPv6 interface or an IPv4 interface.

TM External Use 19 Terminology IPv6 host=A node with an IPv6 address. IPv6 hosts do not forward packets.

TM External Use 20 Terminology

Link=A single, contiguous network medium that is bounded on either end by a router.

TM External Use 21 Terminology Neighbor=An IPv6 host/node that is on the same link as the local node.

Neighbor=An IPv6 host/node that is on the same link as the local node.

TM External Use 22 Terminology

IPv6 subnet=IPv6 does support multilink subnets, where nodes on more than one link can be components of a single subnet. Links 2 and 3 are components of multilink Subnet 8a.

TM External Use 23 Why IPv6?

• IPv4 addresses are exhausted • Today’s Internet is much different than in the early days

“THE WORLD IS DIFFERENT NOW” “[Since] 2012, global use of IPv6 more than doubled. 2013 marked the third straight year IPv6 use on the global Internet has doubled. If current trends continue, more than half of Internet users around the world will be IPv6-connected in less than 6 years.” - World IPv6 Launch http://www.worldipv6launch.org/

TM External Use 24 IPv4 vs IPv6

IPv4 IPv6 32-bit address (232 = 4.3 Billion) 128-bit address (2128 = 3.4 x 1038) Addresses represented in 4, 8-bit Addresses represented in 8,16-bit decimal format (e.g. 192.168.0.1) hexidecimal numbers (e.g. FE80:0:0:0:0102:03FF:FE04:0506) Simplified (FE80::102:3FF:FE04:506) DHCP Stateless Address Auto-Configuration (SLAAC) Network Address Translation (NAT) to Not necessary. More ideal for peer- conserve addresses to-peer communication.

Mostly single IP address per interface Multiple IP addresses per interface (link local, global, …)

ARP Neighbor Discovery (ND)

TM External Use 25 Advantages of IPv6

• Network Address Translation (NAT) is not required for IPv6 − Reduces network latency − Simplifies cross internet communication between nodes − Enables true end-to-end connectivity at the IP layer − Peer-to-peer networks are easier to create and maintain.

• IPv6 reduces processing load on routers − Added protocol for discovery of the path's maximum transmission unit (MTU). − Fragmentation is handled by the source device, rather than the router − Checksum does not need to be recalculated at every router hop.

Both help to improve reduce latency and improve QOS

TM External Use 26 Security

• IPSec originally required… Now it is optional… Why? − Short answer: Many solutions so one just didn’t fit all use cases.

• Longer answer: − RFC-6434 IPv6 Node Requirements….December 2011 A range of security technologies and approaches proliferate today (e.g., IPsec, Transport Layer Security (TLS), Secure SHell (SSH), etc.) No one approach has emerged as an ideal technology for all needs and environments. Moreover, IPsec is not viewed as the ideal security technology in all cases and is unlikely to displace the others.

TM External Use 27 Auto-configuration & Link Local Addressing

• Devices can have multiple IP addresses − Link Local FE80::0102:03FF:FE04:0506 − Global 2001 ::0102:03FF:FE04:0506 − Multicast FF02::1:FF04:0506

TM External Use 28 IPv6 Addressing

• Unicast – one-to-one • Multicast – one-to-many • Anycast – one-to-one-of-many (nearest one)

• It is the address that determines the scope (Link Local, Unique Local, Global)

TM External Use 29 IPv6 Addressing

128-bit IPv6 Address

Subnet Identifier (64-bit) Interface Identifier (64-bit)

16-bit 16-bit 16-bit 16-bit 16-bit 16-bit 16-bit 16-bit

First few bits Next bits in top 64- Last 64-bits are the indicate type of bit section indicate individual device address: link Local, Region, ISP, Site, identifier global, etc etc

Subnets are always 64 bits in length (/64)

2^64

TM External Use 30 Global Addresses

• Global addresses are globally routable. They are equivalent to public IPv4 addresses. • Unlike link-local addresses, which are only valid within a single link, global addresses can be used to communicate across the IPv6 internet.

128-bit IPv6 Address

Subnet Identifier (64-bit) Interface Identifier (64-bit)

3 bits 61 bits 64 bits

001

TM External Use 31 Link-Local Addresses

• FE80: • Always automatically configured • Required for Neighbor Discovery • The scope of the link local address is the local link.

128-bit IPv6 Address

Subnet Identifier (64-bit) Interface Identifier (64-bit)

10 bits 54 bits 64 bits

1111 1110 10

TM External Use 32 Multicast Address

• Interface is listening for traffic on following multicast addresses: − The node-local scope all-nodes multicast address (FF01::1) − The link-local scope all-nodes multicast address (FF02::1) − The solicited-node address for each unicast address − The multicast addresses of joined groups (Davies, p. 62)

TM External Use 33 DHCPv6

• DHCP is optional with IPv6 because of stateless address auto- configuration (SLAAC) • Nodes do not have to request an IP address from a DHCP server because they can quickly auto-configure a unique IP address themselves. − Prefix Discovery: Discover the network prefix

TM External Use 34 Scope IDs

• Used when node has multiple network interfaces (PC with Wi-Fi, Ethernet, ? etc.) • If an outbound connection is to be 1 made with a link local address, the specific interface that the connected Node w/ Mulitple device is on must be specified by the Interfaces Scope ID of the interface. • If you want to ping an address, you 2 3 have to specify which interface the device should be on. This is done by ? ? using the scope ID.

TM External Use 35 Agenda

TM External Use 36 Interface Identifier details (Self assigned)

• 64-bit Interface Identifier can be assigned in several ways − Generated from the devices 48-bit MAC Address (Linux) EUI-64 implementation using interface MAC address and flipping bit 7 MSB. − Randomly generated (Windows) Similar setup as EUI-64 but insert pseudo random number; not MAC − Assigned via DHCPv6 • A Link Local address really only has to be unique on that specific subnet. − Whereas a Global IPv6 address must be unique.

TM External Use 37 EUI-64 Link Local Address Generation

Implementation using interface MAC address and flipping bit 7 MSB

TM External Use 38 Processor & Memory Requirements

• Any device that supports IPv4 can support IPv6 • MAC and PHY Layers are the same • Memory requirements of IPv6 network software stack is very similar to IPv4 • Data throughput is also similar

Application Software Requirements

• Upper layers and applications do not change

TM External Use 39 Agenda

TM External Use 40 ICMPv6

• Stateless Address Auto Configuration (ARP replacement) • Neighbor Discovery using solicitation calls to nodes and routers • Path MTU discovery – minimum path is 1280 bytes

TM External Use 41 Stateless Address Auto Configuration (SLAAC)

• Link Local Address (LLA) already determined:

− Uses Link Local generated address with multicast to get Prefix and learn Layer 2 (Ethernet) addresses of local nodes.

•DAD ensure unique LLA on segment •Multicast used to get Ethernet addresses •RS for Network Prefix, PMTU, other.

TM External Use 42 Neighbor Discovery using ICMPv6

• Used by Hosts for: − Address Resolution: Resolve link-layer address of neighbors Using Multicast address with Neighbor Solicitation (NS) message Neighbor will use message contents to unicast back Neighbor Advertisement (NA) (i.e. IPv6 and MAC returned) − Duplicate Address Detection: Using Multicast address with Neighbor Solicitation message If no NA no conflict. If NA then need to try another LLA. − Stateless Address Auto Configuration: Configure own IP Address − Router Discovery: Discover neighboring routers − Prefix Discovery: Discover the network prefix (like subnet mask in IPv4) − Parameter Discovery, Next-hop determination, neighbor unreachability detection, duplicate address detection, redirect function

− Uses Link Local generated address with multicast to get Prefix and learn Layer 2 addresses of local nodes.

TM External Use 43 Multicast Listener Discovery

• Provided: − MLDv1 provides all needed functionality required for joining and leaving IPv6 multicast groups. − MLDv1 is compatible and can work in MLDv2 networks. − MLDv1, by feature set, is analog of IGMPv2 for IPv4 and it is provided with RTCS.

• Note: − Many commercial certified IPv6 routers do not support MLDv2

TM External Use 44 Agenda

TM External Use 45 Testing and Certification

• https://www.ipv6ready.org/db/index.php/public/logo/02-C-001015/

• IPv6 Ready Logo Program is a conformance and interoperability testing program The IPv6 Ready Logo Committee mission is to define the test specifications for IPv6 conformance and interoperability testing, to provide access to self-test tools and to deliver the IPv6 Ready Logo.

• The Key objectives and benefits of the IPv6 Ready Logo Program are to: Verify protocol implementation and validate interoperability of IPv6 products. • Provide access to free self-testing tools. • Provide IPv6 Ready Logo testing laboratories across the globe dedicated to provide testing assistance or services.

TM External Use 46 IPv6 Ready

• ipv6-core-protocols − https://www.ipv6ready.org/?page=documents&tag=ipv6-core-protocols • NOTE: The IPv6 Core Interoperability test requires testing against 4 different Vendors with different IPv6 Stacks. The counter implementations must be 2 Routers and 2 Hosts.

Reference Link

TM External Use 47 Agenda

TM External Use 48 RTCS Dual Stack (IPv6&IPv4) capable

TM External Use 49 IPv6 RTCS Supported Protocols with more to come

TM External Use 50 Supported RFCs

• RTCS is compliant to: − RFC 2460 - IPv6 Specification − RFC 4861 - Neighbor Discovery for IPv6 − RFC 4862 - IPv6 Stateless Address Auto Configuration − RFC 1981 - Path MTU Discovery for IPv6 − RFC 4443 - ICMPv6

TM External Use 51 Dual Stack

• RTCS has been architected to efficiently support both IPv4 & IPv6 network interfaces at the same time, thus allowing a device to operate in a mixed network – critical in the transition period between IPv4 and IPv6.

TM External Use 52 Memory Requirements

• Typical footprint

Memory: IPv4 IPv6 IPv4 + Ipv6

ROM* 45k 44k 65k

RAM (Data) 2k 2k 2k

RAM * ROM Details (Heap) IPv4 IPv6 IPv4 + IPv6 RTCS Core 3956 5808 5994 ARP 2018 2018 IPv4/IPv6 9814 14366 21596 ICMP/ICMPv6 2172 1792 3940 TCP 13234 14008 16798 UDP 2436 2620 4416 Sockets 2920 3204 3840 DHCP 4310 4310

Other 3830 1892 2034 Total 44690 43690 64946

TM External Use 53 MQX 4.1 RTCS TCP/IP Stack IPv6 Ready Get ready for the worldwide transition to the next generation of the Internet (IPv6), but retain support for the Internet of today (IPv4) New IPv6 add-on for purchase − IPv6 Ready (Phase-2) Core-Protocols Certified − Configure for single stack (IPv6) or dual stack (IPv4 + IPv6) − Supports stateless auto-configuration, network auto-discovery, and the massive address extensibility of IPv6 − Supported protocols - IPv6, ICMPv6, ND, TCP/UDPv6, Sockets, SMTP Client, HTTP Server, MLD Discover, FTP Server, FTP Client, & DNS − Protocols planned for future – DHCPv6, Telnet, TFTP, SNMP, PPP − Add IPv6 for about 21 KB of additional ROM code − Supports all MCU platforms supported by RTCS in MQX 4.1 − Available for download at www.freescale.com/mqx/ipv6

TM External Use 54 IPv6 Licensing

• One-time license fee required Per Customer Product, No royalties • Purchased at www.freescale.com/mqx/ipv6 as digital download • MQX Level 2 Support package required*

IPv6 add-on MQX Level 2 Support Total Cost Competition Estimate License Fee Package (RTOS with IPv6 + (Covers all of MQX) Support Contract) DL-MQXIPV6-SR-PS DL-MQXLVL2-S or -P

$5,000 $3,000 $6,500 N/A $3,500 (Standard 6-mo.) $5,000 $12,000 $15,500 $30,000+ $3,500 (Premium 12-mo.)

30% off limited time * Level 2 required for initial IPv6 purchase and continued support, Use Coupon Code: and maintenance. (Level 2 support covers all of MQX Software, not MICKAVTN just IPv6.) ** IPv6 beta customers – we are waiving the license fee for a single customer product *** Not available through distribution channels at this time

TM External Use 55 IPv6 Add-on Licensing – Additional Details

• Per Product/Project restrictions: − “Customer Project” means a specific customer product using Freescale MQX in connection with a specified processor. If the Customer Project is a module that embeds into other products, it will be considered a single project if the same hardware and software is used within the modules. (MQX Support User’s Guide)

• License Options − Single Product License – Available Now − Multi-product license – Coming Soon

TM External Use 56 Software Licensing Model – Typical Commercial Model

Year 1 Year 2 Year 3

$$$ SW License Fee w/ 1-year Support Yearly Support & Yearly Support & Maintenance Fee Maintenance Fee $ ~20% $ ~20%

…

TM External Use 57 Software Licensing Model – Freescale MQX RTOS

Year 1 Year 2 Year 3

Commercial support fee to cover MQX RTOS commercial support costs Free SW License

Free Basic Support & ~Quarterly Updates

$ $ $ Commercial Support Available Commercial Support Available Commercial Support Available…

TM External Use 58 Software Licensing Model – Freescale MQX IPv6

Year 1 Year 2 Year 3

MQX RTOS Free • Commercial add-on requires upgrade to SW License commercial support if not done already. • Support covers all of MQX RTOS software. • Support fee to cover support costs.

IPv6 License $

$ $ $ Commercial Support Required Commercial Support Required Commercial Support Required (for IPv6 Support & Updates) (for IPv6 Support & Updates) …

TM External Use 59 IPv6 Purchase Process (Short Term)

1. Purchase an MQX Level 2 support package for your project − Visit www.freescale.com/mqx/support, click Buy/Specifications − See section 4 of Freescale MQX Support User’s Guide for registration instructions 2. Purchase the IPv6 license for your product − Visit www.freescale.com/mqx/ipv6/, click Buy/Specifications − Use coupon code* MICKAVTN to obtain 30% discount 3. Within 1 business day, you will receive an email with the link to download the IPv6 software

* IPv6 Beta Customers use a different coupon code for 100% discount on a single purchase. Contact us for the coupon code.

TM External Use 60 Freescale MQX Level 2 Support Accelerating MQX RTOS-based development projects

What are the benefits of MQX Level 2 Support? • Direct senior level support access • Specified response times • Support for software customizations • Troubleshooting support on custom hardware • Early access to software releases and bug fixes • Private support portal, telephone, & web conferencing support When to consider upgrading to MQX Level 2 Support? • Before next MQX RTOS-based development project starts • Tight resources or schedule, or just to insure project efficiency How to get MQX Level 2 Support? • Packages available for purchase at www.freescale.com/mqx/support • See website for complete details

TM External Use 61 Freescale MQX Support and Engineering Services

Level 1 Support Level 2 Support Engineering Services Plan Overview Basic Standard Premium Approx. once a Approx. once a Releases Available Quarter Quarter Early1 Access to MQX Online Community / Online Training Yes Yes Yes Service Requests (SW running on FSL Eval HW only) Yes Yes Yes Report bugs for fix in quarterly releases Yes Yes Yes BSP customization support ‐ Yes Yes Private Support Portal ‐ Yes Yes Software development Access to Early Beta Releases 1 ‐‐Yes services. On‐site Hot Fixes 2 ‐ Yes Yes support/training. Cost based on project Initial Response Time 3 ‐ 2 business days 1 business day definition. Max Hours of Support Engineer's Time 4 ‐ 20 hours 100 hours Web Conferencing to debug issue 5 ‐ 4 hours 10 hours Phone Support 5 ‐ Yes Yes Hands‐on Support of Customer‐Provided Hardware (shipped to Freescale Support) ‐‐Yes Support Plan Term ‐ 6 Months 12 Months Price Free $3,000 $12,000 Part Number ‐ DL‐MQXLVL2‐SDL‐MQXLVL2‐P

1 Early access to beta releases weeks/months before quarterly releases are typically available 2 Access to bug fixes on issues you report immediately when available 3 Amount of time to receive acknowledge of support request 4 Any time support engineer spends including time preparing bug fixes. 5 Hours counted in Support Engineers Time

TM External Use 62 Agenda

TM External Use 63 Example Applications Available

• All RTCS examples support both IPv6 and IPv4 examples. − Shell − HTTP Server − SNMP − Ethernet to Serial

TM External Use 64 Session Summary

• You should now − Understand the basics of IPv6 − See the simplicity of getting devices on IPv6 networks with MQX RTCS with IPv6 − Enable the migration of your products to IPv6 networks

• Where to get more information − www.freescale.com/mqx/ipv6 − www.freescale.com/mqx − www.freescale.com/mqx/support

TM External Use 65 Useful Resources on the web

• From “sixscape.com” − TCP/IP overview − IPv6 − NetConf - Windows PC Utility application • From CISCO − Overview of IPv6 – Excellent reading to give inherent understanding • From “youtube.com” − Keith Barker – Great short videos with much detail − Anthony Sequeira – Good higher level videos − James P. Early, Ph. D. – Good information but long and slow • From “ipv6now.com.au − IPv6 RFCs summary

TM External Use 66 TM