Netdev List
 help / color / mirror / Atom feed
From: Duc Thinh Le <ducthinhle@yahoo.ca>
To: netdev@vger.kernel.org
Subject: Flag this message TCP fragmentation on IPv6
Date: Mon, 28 Jan 2013 14:20:06 -0800 (PST)	[thread overview]
Message-ID: <1359411606.93934.YahooMailClassic@web125402.mail.ne1.yahoo.com> (raw)

Hello TCP experts,

  I am sorry to bother you. But I am just wondering if
  you can shed some light on how TCP-v6 (Linux - Fedora) 
  handle the case where it send a segment of 1500 bytes 
  and then some router along the way sends back the 
  ICMPv6 "too big - 1300" message. There are two choices:

     1) TCPv6 resends the original segment (1500) into
        two new TCP segments (one with 1300) and the other
        is 200.

        OR

     2) TCPv6 sends out two IPv6 fragment packets to
        achieve the original 1500

    OR maybe, there are other ways as well. Thanks for your
  times and helps. If there is a another forum that I can ask these
  kinds of questions, please let me know. Thanks a lot.

Regards
Duc Le

             reply	other threads:[~2013-01-28 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 22:20 Duc Thinh Le [this message]
2013-01-28 22:21 ` TCP fragmentation on IPv6 Duc Thinh Le

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1359411606.93934.YahooMailClassic@web125402.mail.ne1.yahoo.com \
    --to=ducthinhle@yahoo.ca \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox