Re: [v6ops] reclassify 464XLAT as standard instead of info

[Alexandre Petrescu <[e-mail]>]

Le 20/09/2017 à 02:02, Fred Baker a écrit :
> 
> 
>> On Sep 19, 2017, at 2:15 PM, Alexandre Petrescu
>> <[e-mail]> wrote:
>> 
>> Hi Fred,
>> 
>> Let me comment.
>> 
>> Le 19/09/2017 à 22:41, Fred Baker a écrit :
>>> Chair hat off. If it were ONLY about IPv4, I might agree with
>>> you, or suggest another working group. 464XLAT is about
>>> connecting an IPv6-only (subset of a) network to an IPv4
>>> network,
>> 
>> If it is an IPv6-only (subset of a) network then it must run
>> DHCPv6-PD to get a prefix.  DHCPv6-PD is Standards Track.  I did
>> not see DHCPv6-PD on networks where 464XLAT is present.
> 
> Let's agree that it has to have a prefix. T-Mobile, for example, has
> a prefix. Cameron Byrne, from T-Mobile, is a co-author of 464XLAT.

Hello to Mr. Byrne.

That prefix is not DHCPv6-PD.

That prefix is an INFORMATIONAL method that is 64share.

The StdsTrack method is DHCPv6-PD.

If one looks at making 464XLAT StdsTrack one also considers 64share to 
go StdsTrack.

>> Second, when you say connecting IPv6-only network to an IPv4-only
>> network: GTPU does that already.
> 
> Which is great if you're going to a mobile network. If you're going
> anywhere else on the Internet, a mobile-only protocol doesn't do much
> for you. That's why we defined 464XLAT.

Well, I dont think 464XLAT is deployed anywhere else than on cellular. 
These are the big numbers that the Original Poster talked about: 
miliions of users - they are on cellular.

Alex

>