Is there a new set of Bogon IPs that can be filtered?

Yes, and it's expansive. https://github.com/autocracy/python-ipy/blob/d051b1ce7938f5eef6ea75bc72c51509b568b6ca/IPy.py#L36 is a decent start to look at how allocations are setup. See the IPv6ranges table.

Is there any proof-of-work or whitelisting possible for valid connections?

That one I don't know anything helpful for.

Are there any features inherent to IPv6 that could cause a DDoS risk or be used as a mitigation?

Yes, the massive address space can present an issue locally since any incoming message would typically result in the router trying to find a L2 address to forward the packet to. Every address can result in a new solicitation, so that's a negative effect. See http://tools.ietf.org/html/rfc6164#section-5.2

Is there a new set of Bogon IPs that can be filtered?

Yes, and it's expansive. https://github.com/autocracy/python-ipy/blob/d051b1ce7938f5eef6ea75bc72c51509b568b6ca/IPy.py#L36 is a decent start to look at how allocations are setup. See the IPv6ranges table.

Is there any proof-of-work or whitelisting possible for valid connections?

That one I don't know anything helpful for.

Are there any features inherent to IPv6 that could cause a DDoS risk or be used as a mitigation?

Yes, the massive address space can present an issue locally since any incoming message would typically result in the router trying to find a L2 address to forward the packet to. Every address can result in a new solicitation, so that's a negative effect. See https://www.rfc-editor.org/rfc/rfc6164#section-5.2

Is there a new set of Bogon IPs that can be filtered?

Yes, and it's expansive. https://github.com/haypo/python-ipy/blob/master/IPy.py#L34 is a decent start to look at how allocations are setup. See the IPv6ranges table.

Is there any proof-of-work or whitelisting possible for valid connections?

That one I don't know anything helpful for.

Are there any features inherent to IPv6 that could cause a DDoS risk or be used as a mitigation?

Yes, the massive address space can present an issue locally since any incoming message would typically result in the router trying to find a L2 address to forward the packet to. Every address can result in a new solicitation, so that's a negative effect. See http://tools.ietf.org/html/rfc6164#section-5.2

Is there a new set of Bogon IPs that can be filtered?

Yes, and it's expansive. https://github.com/autocracy/python-ipy/blob/d051b1ce7938f5eef6ea75bc72c51509b568b6ca/IPy.py#L36 is a decent start to look at how allocations are setup. See the IPv6ranges table.

Is there any proof-of-work or whitelisting possible for valid connections?

That one I don't know anything helpful for.

Are there any features inherent to IPv6 that could cause a DDoS risk or be used as a mitigation?

Yes, the massive address space can present an issue locally since any incoming message would typically result in the router trying to find a L2 address to forward the packet to. Every address can result in a new solicitation, so that's a negative effect. See http://tools.ietf.org/html/rfc6164#section-5.2