gogoNET

IPv6 products, community and services

IPv6/IPv4 translation requirements

So here I add my list of top level requirements for IPv6 translation.
Considering not only the transition to 6 but the left behind 4 networks and the options they need to have for functionality. I hope it helps :)



6to4

Allowing 6to4 functionality so either 6in4 or ALG GW DNS64

4to4

Allowing 4to4/444 NAT

4to6

Allowing 6in4 or ALG/DNS translation

4 mapped

A different type of 6to4 mechanism but mapped IPv4 embedded into the IPv6 address

IPv6-IPv4 native (no DNS)

IP to IP connectivity across the protocols

Stateless & Stateful

Whether the implementation is stateful or stateless

DNS integration

Whether a separate DNS solution is required or it is integrated

DNS required (DNS64)

DNS functionality required

Allocation Saving

The level of allocation the solution provides

LI & DR

Whether LI and DR are possible and the costs, support and topology capable

Service Functionality

The level services you can run over the translation and the application compatibility

Transition Ease

The ease of translation comparatively. The technical configuration and the level of process needed in the technical solution

End goal alignment

Does the technical proposal or technology align with our end goal of a native IPv6 network

Last Resort

Does all of our known traffic (implemented with the technology) need to be processed through the TrGW/DNS or is it last resort

Traffic Throughput Percentage

What is the throughput rate of the devices doing the translation and will a bottleneck be created

CER pos

Where it is position and how it positions itself if at the Customer Edge Router and with what functionality at this

CEM pos

Where the translation is positioned is at the CER and what functionality sits at the node (note that multiple point of translation can occur)

CMTS pos

Where the translation sits if on CMTS and the functionality therein

IPE pos

Internal PE positioning and functionality if so

EPE pos

External PE translation and functionality

RoaS(hairpin)/Integrated

Whether the design is a router on a stick or integrated and the chassis needed if it is integrated

1-many/1-1

The IPv4 or IPv6 translation methodology flow of either one to many or one to one.

Bi-directional

Whether the in-bound connections can be created or visa versa or both

Security

What security issues are there and how they effect any particular product implemtnation

NAPT/NAT Technology

The type of technology and applicable technology used

Expected cost

The expected cost including LI, DR, Management, Monitoring, Support in general, hardware, & helpdesk .. to name but a few

Performance

The level of performance as a technology as a whole

Monitoring & Management

How easy ti will be to monitor, whether netflow and our known management and monitoring applications will have full functionality

CNR interoperability

Whether the CNR will have lease control, and if not what integration is possible for stateful tables of the lease for each customer or customer groups

Physical/Pseudo

Whether the interfaces provided are virtual or physical and the problems or benefits this can provide for this particular solution

Solution Term

How long a solution can last or should last and whether it can be used a an “all-round solution” for both the present customers and new installs

IPv6 Native Future

Will this product/technology allow us to go forward to a Native IPv6 customer/access structure in the future and the longevity of the necessity of the kit used

Resiliency

Is the product/technology resilient

Redundancy

Is the product/technology redundant

Recovery

Is the product recovery quick within its redundancy – convergence times etc …

Scalable

Is the product scalable in the short and long term & if necessary could we extend its functionality to encompass all of the translation needs

Potential Vendor Deployment Date

How current is the technology/products on offer and what is the present roadmap if not in deployment as of yet.

Views: 130

Comment

You need to be a member of gogoNET to add comments!

Join gogoNET

Comment by Phil on June 27, 2011 at 7:40am

the list needs to be expanded but haven't had the time.

Have added a new blog on it though

Comment by shivlu jain on March 20, 2010 at 10:16am
This is really a good check list. Thanks for sharing your great idea.

regards
shivlu jain
http://www.mplsvpn.info
Comment by Phil on March 20, 2010 at 5:21am
Thanks, I will be adding my list of traffic percentages & vendors with their present level of IPv6 readiness or their roadmap. The list of applications will be the 200 most used in Europe from a customer sub average.
Comment by Nikolay Milovanov on March 19, 2010 at 8:35am
Hi Phil,

This is a very good post indeed. To develop further I may just add that any network operator sooner or later will need most of the requirements listed above implemented and integrated within their current OSS systems. To be more precise in the fulfillment platforms that they currently use. Otherwise any transition or migration of services and subscribers will be a big mess.
Nikolay

Sponsor

special report

Training

gogoTRAINING

IPv6 Product Information

Fill out my online form.

© 2014   Created by gogo6.

Badges  |  Report an Issue  |  Terms of Service