Neo4j specification points to Point datatype (both 2D and 3D), but there is no information about it in BOLT Protocol specification. Should we add it?

We have a neo4j EC2 instance, we want to add that to Auto scaling group with AWS ELB load balancer.
When I access the neo4j browser with Load balancer DNS name it works, but bolt connect does nt work.
How to setup AWS Load balancer for neo4j EC2 instance

I am running neo4j behind Apache proxy. I am using mod_proxy to route the traffic, but since bolt is not a standard protocol I couldn't find a mod_proxy plug-in for bolt.

Is there an Apache mod_proxy plugin for bolt protocol?

Hello there!

I'm currently working on a new rust driver for neo4j, using the bolt protocol. For ver1 I can follow closely the specification (which is nicely written, by the way). For the other versions I started to look at the drivers source code here on git. But it would be nice to have a somewhat official specification. Are there any plans to add the specification for the new iterations?

So far, is there anything different in these specification besides adding new types and message structs (and removing the "pull all" struct since V4)?

I believe that IGNORED messages do not typically include a metadata parameter (based on examples and Neo4j server responses), however, docs show that it does have a metadata parameter. It is unclear as to whether this is optional, or if it is a typo. Thanks in advance.