valsad Escorts Service ☎️ 6378878445 ( Sakshi Sinha ) High Profile Call Girls...
Panel with IPv6 CE Vendors
1. - 1
IPv6 CE Vendors Panel
APNIC 44
Taichung - Taiwan
September 2017
Jordi Palet (jordi.palet@theipv6company.com)
2. - 2
RFC7084
• RFC7084: Basic Requirements for IPv6 Customer Edge Router
– Know as CPE (Customer Premises Equipment), or CE (Customer Edge)
– Originally RFC6204 (2011), obsoleted as RFC7084 (2013)
• Lots of changes since then:
– No more IPv4 space
• You can’t think anymore in deploying dual-stack
– New (or updated) transition mechanism to cope with that
• lw4o6 (less complexity in the CGN, cheaper & more scalable)
• MAP-T and MAP-E
• 464XLAT
– New technologies for the home
• Homenet
– Often SOHO and medium enterprises use this kind of CEs
• New work in IETF v6ops WG:
– draft-ietf-v6ops-rfc7084-bis
3. - 4
Panel Organization
• 4-5 minutes short intro from each vendor
• 7 “main” topics, 1-2 minutes each
speaker, each topic
• Extra time for other topics
4. - 3
Panel Participants
• Hans Liu
–Director of Strategic Technology, D-Link
• Wen-Hsien Peng
–Senior Programmer, Zyxel
• Masanobu Kawashima
–Assistant Manager, Product Planning, NEC Platforms
6. •2006/5 Certified IPv6 Ready Logo (Phase 2) for consumer router
•2008/7 Start shipping IPv6 Ready CE routers to the retail market
•2010-2011 Many interops hosted by Cablelabs and UNH-IOL
•2011/4 RRFC 6204 (Basic Requirements for IPv6 Customer Edge Routers)
•2011/6 Initiative member of World IPv6 Day
•2012/6 Initiative member of World IPv6 Launch
•2012/6 Passed BBF.069 Certification with IPv6 support.
•2013/11 RFC 7084 (Basic Requirements for IPv6 Customer Edge Routers)
•2014/10 RFC 7368 (IPv6 Home Networking Architecture Principles)
•2014-2017 More transition protocols were invented
A little background
8. • Homenet
• Multi-router, Multi-ISP
• Arbitrary Topology
• Auto IP Prefix Configuration
• Name Resolution
• Service Discovery
• IPv6 Focus w/ IPv4 in mind
• Network Security
• Are we ready for homenet?
Coming works
16. What Can We Do for
IPv6 CE Router Deployment?
September 12, 2017
NEC Platforms, Ltd.
Masanobu Kawashima
APNIC 44 BoF: Discussion with IPv6 CE Vendors
17. Outline of Presentation
1. NEC Platforms’ Activity for IPv6 Deployment
2. Why is It Hard to Deploy IPv6 CE Router?
3. What Can We Do for IPv6 CE Router Deployment?
34. - 5
Your Customers/Products
• Retail market vs OEMs vs Service Providers
• Same products in terms of hardware or firmware
• Same products in different regions/countries
• If something “new” becomes implemented, can be shared across the
above “different” situations
• Will you implement new transition mechanisms if there is an update
or “companion” document for RFC7084
• What is your “base” OS
35. - 6
New Transition Mechanisms Support
• lw4o6, MAP-E/T, 464XLAT
• When do you think it will be available in your CEs
• New hardware requirements
– Such as CPU, flash, RAM, others
• Development, testing, other cost
• Minimum order for implementing
36. - 7
Firmware Upgrade for Existing CEs
• Why existing CEs can’t be upgraded
• Hardware reasons (don’t look like)
• Marketing / commercial
• Licensing model with extra cost
37. - 8
Homenet
• When do you think it will be available in your CEs
• New hardware requirements
– Such as CPU, flash, RAM, others
• Development, testing, other cost
• If not, existing products will have new firmware
supporting it
38. - 9
Security Features
• Since IPv6 has no NAT, stateful firewall for IPv6
– Enabled by default
• Improvements to avoid being part of new botnet DDoS
• Other issues