[conex] 1) Loss of ConEx information

Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de> Mon, 03 June 2013 13:09 UTC

From: Mirja Kühlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
To: conex@ietf.org
Date: Mon, 03 Jun 2013 15:09:38 +0200
User-Agent: KMail/1.9.10 (enterprise35 0.20101217.1207316)
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201306031509.38049.mkuehle@ikr.uni-stuttgart.de>
Subject: [conex] 1) Loss of ConEx information
Precedence: list

Hi,

it can happen that ConEx information can get lost, e.g. a packet with a ConEx 
marking gets drop at a full router queue or the traffic gets rerouted and a 
new audit element does not have the old credit state.

This might be a problem if an audit starts penalizing a flow because of this 
wrong information even though the sender has done nothing wrong.

The question is how to handle this case? And also where to document what the 
right behavior of the audit and sender should be?

I don't think we should try to retransmit any lost marking. Especially the L 
and E markings will be out-dated by the time of the retransmit. Thus the only 
solution is to send credits instead to keep the audit happy. But how to 
detect that ConEx information got lost?

Mirja

[conex] 1) Loss of ConEx information Mirja Kühlewind