At present android apps running on chromebooks do not work over nat64. I believe one of our colleagues at Google has filed a bug report on this, so hopefully it will no longer be an issue in Chicago. OpenVPN works with nat64, but requires special configuration file hacking in some cases. I have no other issues with it. If it weren't for the fact that my xmpp app is an Android app, I would be using ietf-nat64 exclusively. On Thu, Nov 17, 2016 at 9:16 AM, Randy Bush <randy@xxxxxxx> wrote: > last evening i was carrying a question from the noc team but my position > in the mic queue was preempted by more important people. > > but essentially, before we make tactical decisions we would like to know > what the purpose and goal of the meeting network is. > > o folk just want to get work done, and the net should bloody well work > > o i want to forward test internet futures: ipv6, auth methods, crypto, > ... > > o i have my own stuff i want to test (which may need inbound sessions) > > o network? what network? > > in the nat64 case, are we trying to validate the well-known lists of > what does not work over nat64, spotify, many vpns, ...? if it is > because we think we can modify nat64 to ameliorate the problems, this > would be brilliant. > > if we know what the goals are, we should be able to meet them. so far, > the assumption is that > > o the primary goal of the meeting netowrk is for attendees to get work > done > > o nats breaking applications and inbound connections would be > considered as breakage > > o we do want to support occasional experiments, both non-disruptive > and visible (remember the v6-only plenary?) > > o but basically, i just want my mtv > > randy, not speaking for anyone else >