Re: draft-kawamura-ipv6-isp-listings-00.txt

[Seiichi Kawamura <kawamucho@mesh.ad.jp>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Kurt, Gert

Thanks for the comments.

Gert Doering wrote:
> Hi,
> 
> On Wed, Jul 21, 2010 at 08:28:22AM +0200, Lindqvist Kurt Erik wrote:
>>> Bringing an ISP to be fully dual stacked will take years.
>> So I suggest that minumum is 
>>
>> - PA Block
>> - Customer Assignments
>> - DNS resolvers IPv6 capable
>> - Native (v6 only or dual-stack) upstream connection
>> - SMTP relay / Submission IPv6
> 
> Seconded.  These are the most crucial blocks for an ISP to enable useful
> IPv6 connectivity for his customers.

This is actually a pretty good 'what to do first' list.
I would add a note about PMTUD functionality with the
native upstream. I come across networks where packets
over 1500bytes don't get through from time to time...

I wonder if reverse DNS shoulod be mentioned or not.

> 
>> - IMAP/POP IPv6
> 
> I'm not sure about this - yes, if the ISP offers hosted mail services
> for the customer, but this is already going into the "individual products"
> section.  A pure transit ISP might not need that.

I agree with Gert.

Regards,
Seiichi

> 
> Gert Doering
>         -- NetMaster


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkxKlV0ACgkQcrhTYfxyMkIoDQCeMxN8QNuIxuWdILrrdqE/8RDl
wDAAnRhoCiD5My8pqV7xN7AEoimVjenz
=N/ZF
-----END PGP SIGNATURE-----