- From: Tuexen Michael <Michael.Tuexen AT icn.siemens.de>
- To: "'discussion AT sctp.de'" <discussion AT sctp.de>
- Subject: RE: [SCTP-Discussion] MTU Fragmentatiion of control chunks
- Date: Wed Jul 11 13:49:01 2001
- List-id: SCTP Discussions <discussion.sctp.de>
Dear Dinesh,
IP fragmentation is the answer. IPv4 is capable to handle packet up to 64k.
Best regards
Michael
Michael Tuexen Tel.: +49 89 722 47210
Siemens AG Fax: +49 89 722 48212
ICN WN CS SE 5 E-mail:
Michael.Tuexen AT icn.siemens.de
>
-----Original Message-----
>
From: Dinesh JN
>
[SMTP:jdinesh AT convergsoft.com]
>
Sent: Wednesday, July 11, 2001 1:49 PM
>
To:
>
discussion AT sctp.de
>
Subject: [SCTP-Discussion] MTU Fragmentatiion of control chunks
>
>
In RFC 2960
>
>
we have come across this note in RFC 2960
>
>
IMPLEMENTATION NOTE: An implementation MUST be prepared to receive a
>
INIT ACK that is quite large (more than 1500 bytes) due to the
>
variable size of the state cookie AND the variable address list. For
>
example if a responder to the INIT has 1000 IPv4 addresses it wishes
>
to send, it would need at least 8,000 bytes to encode this in the
>
INIT ACK.
>
>
the fragmentation of Data chunk is very clear,but in cases above note,
>
the size of the INIT CHUNK will be exceeding 1500 MTU, so how these chunks
>
have to be handle
>
>
>
thanx in advance
>
Dinesh
>
>
_______________________________________________
>
discussion mailing list
>
discussion AT sctp.de
>
http://www.sctp.de/mailman/listinfo/discussion
Archive powered by MHonArc 2.6.19+.