[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www.eftps.gov contact

Subject: www.eftps.gov contact
From: nanog at bitfreak.org (Darren Pilgrim)
Date: Tue, 18 Dec 2012 08:15:31 -0800
In-reply-to: <CAL9jLaZ4__KB_z-ojx4yyck9y_5m1fYV=FrYk6hM0XthugDqJA@mail.gmail.com>
References: <[email protected]> <[email protected]> <CAL9jLaY1B7Ni71vCC0x5VCC1tq=63OEqfyTucnKnoNtBE53mAw@mail.gmail.com> <CAL9jLab8_tFnvGWf8QHnz240HooGfs-A0jKaEGjmHeiuruQwMQ@mail.gmail.com> <CAL9jLabL_2sVt+Cn6uE_EUQiXYPGveiVC2wVDGYb0dG0gV0ZBA@mail.gmail.com> <[email protected]> <CAL9jLabj26ibQ7BKOUgGs6U-cqjtQU9d+=P3dHGp-PwP4EbftQ@mail.gmail.com> <[email protected]> <CAL9jLaZ4__KB_z-ojx4yyck9y_5m1fYV=FrYk6hM0XthugDqJA@mail.gmail.com>

On 2012-12-18 08:08, Christopher Morrow wrote:
> On Tue, Dec 18, 2012 at 11:02 AM, Darren Pilgrim<nanog at bitfreak.org>  wrote:
>> On 2012-12-18 07:52, Christopher Morrow wrote:
>>>
>>> see, now we're getting information that FDC/IRS could actually use!
>>> :) This looks like an MTU issue then?
>>
>>
>> I believe so.
>
> so, a suggestion to eftps.gov/irs/fdc is to simply clamp MSS on their
> servers, no?

I might instead suggest a read of RFC 4890. :)

Follow-Ups:
- www.eftps.gov contact
  - From: morrowc.lists at gmail.com (Christopher Morrow)

References:
- www.eftps.gov contact
  - From: nanog at bitfreak.org (Darren Pilgrim)
- www.eftps.gov contact
  - From: dmburgess at linktechs.net (Dennis Burgess)
- www.eftps.gov contact
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- www.eftps.gov contact
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- www.eftps.gov contact
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- www.eftps.gov contact
  - From: nanog at bitfreak.org (Darren Pilgrim)
- www.eftps.gov contact
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- www.eftps.gov contact
  - From: nanog at bitfreak.org (Darren Pilgrim)
- www.eftps.gov contact
  - From: morrowc.lists at gmail.com (Christopher Morrow)

Prev by Date: Re: Advisory — D-root is changing its IPv4 address on the 3rd of January.
Next by Date: www.eftps.gov contact
Previous by thread: www.eftps.gov contact
Next by thread: www.eftps.gov contact
Index(es):
- Date
- Thread