id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
151	Accept I2P destinations	duck	duck	"To be able to use I2P with Foolscap (see #150 and [http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1007 Tahoe-LAFS #1007], I have extended `decode_location_hint` to accept I2P base32 destinations. Since I2P destinations can't have a port as part of the location, the current IPv4 regex doesn't work.

These I2P destinations look like this:
{{{
3u2mqm3mvcyc27yliky3xnr4khpgfd4eeadhwwjneaqhj25a65ua.b32.i2p
}}}

They have the format: `base32_encode(sha256_hash) + "".b32.i2p""`"	enhancement	new	minor	undecided	network	0.5.0		i2p transport review-needed i2p-collab	Zooko zooko@… killyourtv@…