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

[Alexandre Petrescu <[e-mail]>]

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.

Second, when you say connecting IPv6-only network to an IPv4-only 
network: GTPU does that already.

A pure IPv6 IoT device that does not run 464XLAT connects to a cellular 
network and its IPv6 traffic gets encap/decap into an IPv4 network by 
using IPv6-in-GTP.  GTP is an IPv4 protocol.

A packet dump sent by the IPv6 IoT Router and captured on the PGW looks 
like this.  This capture was run on a network that does not use 464XLAT.

INBOUND>>>>>  15:47:48:883 Eventid:142004(3)
GTPU Rx PDU, from [IPv4-address]:2152 to [IPv4-address-2]:2152 (129)
TEID: 0x80072183, Message type: GTP_TPDU_MSG (0xFF)
Sequence Number:: NA
GTP HEADER FOLLOWS:
[snip]
GTP HEADER ENDS.
            Payload protocol: IPv6
PROTOCOL PAYLOAD FOLLOWS:
fe80::b9d9:c10a:2c2d:3c3b.546 > ff02::2.546:  [udp sum ok]
IPv6 Header Follows:
[snip]
PROTOCOL PAYLOAD ENDS.

Alex