Re: [v6ops] new draft: draft-chen-v6ops-ipv6-roaming-analysis

["cb.list6" <[e-mail]>]

Hi Nick,

On Jul 30, 2013 9:55 AM, "Heatley, Nick" <[e-mail]> wrote:
>
> Hi Cameron,
>
> >
> > b.  dual-stack 1 PDP (v4v6) will not work any time soon.  Enabling
> this
> > feature in the HSS/HLR breaks roaming and there is no way to ensure
> > this issue is fixed in the hundreds of networks that are potentially
> > impacted.  There are some backs to do on the home network that can
> make
> > this easier but not exposing partner networks to the new release 8
> > features.
>
> [NH] Cameron I assume you referring to the issue of extended MAP (for
> Ipv4v6) causing exception at the visited operator's network?

Yes

Thanks for
> highlighting this issue. I guess I would like to know if the number of
> problem operators is significant, or a few isolated cases. Do you or

We saw a widespread issue in the 10 minutes before we rolled back the
changes.

> anyone have information to infer this is widespread or systemic? If it

The vendors gear / involved is highly deployed, afaik

> is unknown lets acknowledge it as such.
> If cases are isolated, then there may be operational actions a dual
> stack operator can take; for sake of argument, a roaming steering
> solution could be applicable to blacklist a problem operator and steer
> the outbound roamers away before the exception occurs.

Well, there is money involved in steering. Money is usually top of mind
for  the folks  involved,  not v6.

> I have not yet arrived at the conclusion that ipv4v6 roaming cannot be
> made to work, but perhaps I haven't seen the extent of the problem?

I am sure it can be made to work, I am just noting there is operational
risk. I know because we hit it, but  our ops folks had the presence of mind
to roll back quickly

In the long run, we plan to have whitelist for the v4v6 extended
attribute,  but HLR features are on an 18 month cycle for us.  We would
like all our apns to support any combination  of v4, v4v6, or v6. But we
can only safely support v4 or v6 in 2013.  In the 2nd half of 2014, we may
be able to try v4v6 again.

CB

> Regards,
> Nick
> NOTICE AND DISCLAIMER
> This e-mail (including any attachments) is intended for the above-named
person(s).  If you are not the intended recipient, notify the sender
immediately, delete this email from your system and do not disclose or use
for any purpose.
>
> We may monitor all incoming and outgoing emails in line with current
legislation. We have taken steps to ensure that this email and attachments
are free from any virus, but it remains your responsibility to ensure that
viruses do not adversely affect you.
>
> Everything Everywhere Limited
> Registered in England and Wales
> Company Registered Number: 02382161
> Registered Office Address: Hatfield Business Park, Hatfield,
Hertfordshire, AL10 9BW