[192745] in North American Network Operators' Group
Re: pay.gov and IPv6
daemon@ATHENA.MIT.EDU (Lee)
Fri Nov 18 09:54:17 2016
X-Original-To: nanog@nanog.org
In-Reply-To: <1479426029.8037.10.camel@ns.five-ten-sg.com>
From: Lee <ler762@gmail.com>
Date: Fri, 18 Nov 2016 09:51:51 -0500
To: Carl Byington <carl@five-ten-sg.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On 11/17/16, Carl Byington <carl@five-ten-sg.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Thu, 2016-11-17 at 15:32 -0500, Lee wrote:
>> That's fine, but until someone is willing to work with them don't
>> expect it to get fixed.
>
> I am working with pay.gov.clev@clev.frb.org, trying to explain the
> problem. They seem to think I should provide "application name and ID"
> before they can research this.
They probably want that so they know where to route the ticket. I
pointed them at
https://tools.ietf.org/html/rfc4890#page-14
and suggested they have someone on the network team use ipv6 to
connect to pay.gov over a 1280 byte MTU link. Hopefully that's enough
to get the ticket routed to the correct group.
> I responded as below. I will let you know
> if there is any progress on this.
I'd appreciate that.
And thanks for being willing to work with them to fix the problem.
Lee
> It is 100% reproducible here - and
> should be reproducible from anywhere with a slightly smaller than normal
> MTU.
>
>
>
> We try to get to https://www.pay.gov/public/home - which fails. I
> presume that is before there is any application name or ID.
>
> Try to reach that page from a browser on a machine with ipv6
> connectivity that goes thru a tunnel with a 1300 byte MTU. It will fail.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
>
> iEYEAREKAAYFAlguP8oACgkQL6j7milTFsFgrQCfY2QLE0njiSRIILTzR4Fjpk3c
> F3AAnjZj8+3W51Qr9e1oGWAxrUC8Pnf3
> =UpN0
> -----END PGP SIGNATURE-----
>
>
>
