Hi Joe,
Sorry for the delayed response -- I have been away for my vacation.
On 08/10/2013 01:20 AM, Joseph Salowey (jsalowey) wrote:
On Aug 8, 2013, at 12:24 PM, Martin Stiemerling
<martin.stiemerl...@neclab.eu> wrote:
Martin Stiemerling has entered the following ballot position for
draft-ietf-emu-eap-tunnel-method-07: Discuss
----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------
Two points about Section 3.7. "Fragmentation"
- Both ends have to wait for either each fragment or fragment ack
to arrive. However, the timers on how to long to wait before giving
up waiting for fragments or acks are missing.
[Joe] Retransmission and timeout behavior for EAP is discussed in the
EAP RFC 3748 Section 4.3.
The cited section describes retransmission and the associated timeouts
for complete messages, but **not** fragments!
RFC 3748 says clearly in Section 1:
"Fragmentation is not supported within EAP itself; however, individual
EAP methods may support this."
I assume TEAP is an EAP method that has to write-up how fragmentation is
handled, isn't it?
- how does the sending TEAP entity determine what the maximum
transmission unit (MTU) of the path is?
[Joe] Typically EAP receives MTU information from the lower layer.
This is described in EAP RFC 3748 section 3.1.
Ok, I am fine to clear this position if you add a pointer to RFC 3748,
Section 3.1 -- as a reminder for the implementers where to look for
guidance.
Martin
--
martin.stiemerl...@neclab.eu
NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End Road, London, HA4 6QE, GB
Registered in England 2832014
_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu
