“beltug challenges the telcos on ipv6” · 2013-03-08 · panel 1, focused on business...

Feedback for the IPv6 Council on BELTUG challenges the ISPs 1 7 March 2013 P.

“BELTUG challenges the TELCOs on IPv6” 5 March 2013


BELTUG strategy


Members


TELCO ISP

! Accepting the challenge: !  Belgacom, Telenet, Verizon

! Invited, but not present: ! Mobistar, Easynet, Colt, BT, AT&T, VOO

! Number of users present: 15

! All the above pointing in the same direction? !  IPV6 migration is NOT YET a HOT TOPIC


Challenging questions:

!   Panel 1, focused on business connectivity. (B2B, large accounts) ! When will you fully support IPv6 together with IPv4? ! Which of your services are not supported on IPv6? !   Is SIP Trunking also available in dual version? If not, when will it be? !   Do you or when will you have a dual path for international peering? !   Do you offer any additional services for IPv6?

!   Panel 2, for retail market + mobile networks. (SME + Home Work)

! When will you fully support IPv6 together with IPv4 for the retail market? ! What CPE equipment is compatible with IPv6? ! Regarding CPE equipment included in the service, what is the

replacement schedule? ! When will you promote the migration?

9 Verizon Confidential Verizon Confidential – Provided under Non Disclosure Agreement

9

Strategic Roadmap Phase

Internet

Distribution

Core

Access

Datacenter

DMZ

VPNs• Identify islands or elements

•  Focus on low hanging fruit or quick wins

•  Readiness of devices, applications and services may drive order of implementation

•  Fall back scenario per element or island (switch off IPv6)

Step 1 : Maintaining IPv4 connectivity Address sharing & translation (CGN)

Slide 10

What? Carrier Grade Network Address Transla3on (CGN) : Mul3ple customers using a single public IP address

Why? CGN solves shortage of IPv4 and guarantees Internet service con3nuity

Impact? Addi3onal technical requirements to cope with legal requirements (BIPT requirements).

Some customers may have to share a public IPv4 address

prof. market no CGN fixed-‐public IPv4 addr used

Beltug IPV6 workshop 4th March 2013 in commercial confidence

1.  Don’t wait, start now 2.  Education is key and learning takes time 3.  Make a plan – get IPv6 address space from Telenet 4.  Make network inventory (F/W, NAT-ing,routers, switches,

anything with an ACL) 5.  Upgrade all components as part of replacement investments 6.  Make inventory of all IT systems which are ‘IP aware’ 7.  Adapt the IT applications & databases (takes time !) 8.  Get your external presence enabled and managed on IPv6

first 9.  Fix your internal servers and F/W later (this is less urgent) 10. Finally, make inventory of internal LAN & pc’s and upgrade

IPv6 deployment advise for business customers

8/03/13 11 Beltug IPv6 conference 5 Mar 2013


What can be expected from Operators-ISPs ? 1#3

!   “It is difficult to get the right info from ISP” !   BUT the ISPs get very limited # questions from users !

!   Pull the plug out of IPv4 ? = NO WAY till 2020… !   As long as the economy is on tight budgets,

! all projects increasing turnover/profit will be realised ! while neglecting the perceived far-away-dangers of IPv6

!   The sharpest difference with Y2K analogy ? ! Here is no hard deadline, it is an evolutive proces…

!   KB-AR ? “within 2 yrs from now, every governemental service should be IPv6 compliant”: labelled as non-sense



!   ISP = in the middle of a chain: but… IPV6 comes with E2E challenges (so, don’t shoot)

! Any service “IPv6 ready” from a Telco-ISP ….

! requires more details: HOW is it achieved, eg. dual stack – CGN ? ! only launches the start for testing all the other elements in the chain, ! Requires continuous updates of all other services from that Telco-ISP

!   For the mobile world No fear for issues on the DEVICES… but on the APPS !

! Similar approach for all 3 operators, present:

! managed services = the chain is guaranteed & tested (CPE, router, FW, .. Firmware upgraded)

!   non-managed services will come at an extra cost when asked to migrate “in advance on the scheduled migrations” (eg. Gaming: I want NON-CGN now !)



! Local loops in exotic countries: this remains the full responsibility for the operator, eventually in Layer2 solutions

! Any operator unable to demonstrate its planned IPv6 migration should be banned from new RFP participation: OK

! Everyone is in a learning mode, ! don’t be afread to admit “I don’t know”, including the ISPs


Focus on the USER actions & attention (1#2)

!   CGN (Carrier Grade NAT) comes with a 16-to-1 ratio: consequences + performance issues ! Who decided 16-to-1 ? BIPT rule ? Action point for this Council?

!   VPN + IPv6 = NOT a right combination, “a can of worms”

! Users are recommended to list their “tested (E2E) applications/protocols”

! Operators-ISPs should publish What is already in dual-stack ?

! Compliancy ≠ Performance !   IPv6 Security requires more Attn !! !   Websites & DMZs: more attention for home made applic.


Focus on the USER actions & attention (2#2)

! Gigantic problem = helpdesks. (all company internal HDs, incl. ISP’s) ! What kind of info should they provide ? !   On which domains, into which details ?

!   But… how to stay informed/updated on the status of different services from different ISPs, all needed in 1 helpdesk

! Use some hardliners as a model of thoughts: !   No way to get Win-XP compatible with IPv6, !   No way to get SKYPE compatible… extra latency as a consequence ! Quid for any old router in the chain, ! Quid for any low-end device from the residential market (type D-link)

! Lesser problems for smartphones: sold today as Incompatible, but definitely obsolete before the bottlenecks arise


“Requested” by the BELTUG users

!   BELTUG should RAISE the general awareness

!   BELTUG-INTUG or IPv6 Council to “promote” a label for SW-vendors with tested E2E solutions ?

More than IPv6 ready: eg. Support of dual stack ? CGN? … !   BELTUG should offer a pragmatic course on top of the commercially

available (technical) courses

! Publish all available BEST PRACTICES and HOW TO START

!   BELTUG should create a “flyer” ! to raise the attention (concern) ! for multiple groups inside a company ! with different/limited technical skills !   but all being forced to be cooperate (analogy Y2K)

“beltug challenges the telcos on ipv6” · 2013-03-08 · panel 1, focused on business...

Documents