Hi all,
When an Annex G message will exceed max packet size (typically a DescriptorConfirm) on UDP, a Reject might be sent, and the session is repeated on TCP.
But, isn't our PDU size on TCP also limited? When using TPKT, the max pdu size is 65k too, as seen in RFC-1006....
Hope I'm wrong here.
Espen
No, I had reached the same conclusion - the packet size is, indeed, limited to 65K bytes. If the message size exceds the UDP MTU, it hould be sent by TCP. What I am still wondering is, will we exceed the 65K on TCP?
Subtly, this raises a similar question for Annex E which has the same limitation. Should Annex E have a larger size field, and Annex G use Annex E for a larger message size?
Does the TPKT size limitation affect anything else which uses it?
Douglas
At 09:35 1999-05-04 +0200, ETO wrote:
Hi all,
When an Annex G message will exceed max packet size (typically a DescriptorConfirm) on UDP, a Reject might be sent, and the session is repeated on TCP.
But, isn't our PDU size on TCP also limited? When using TPKT, the max pdu size is 65k too, as seen in RFC-1006....
Hope I'm wrong here.
Espen
participants (2)
-
Douglas Clowes
-
Espen Skjæran (ETO)