#4 Support for ECN-marking the PDUs at the RMT

1.0
closed
Michael welzl
RMT (2) ECN (1)
2015-02-03
2014-11-04
edugrasa
No

T3.1 needs the ability in the RMT to set the "ECN-related" byte(s) of PDUs in order to perform their work. Further details to be discussed with Michael Welzl.

Discussion

  • Vladimír Veselý
    Vladimír Veselý
    2014-11-10

    +1 for this ticket added by Kewin and Roberto

    Their text:

    •EFCP: flow control

    •RMT: customization support for ECN. It should be possible to define new classification policies and new scheduling policies. Feedback between status of the queues and EFCP could also be useful, e.g. to affect EFCP on queue-based events. Possible policies could be RMTQMonitorPolicy, MAXQPolicy, RMT-SchedulingPolicy

     
    Link

  • Tomáš Hykel
    Tomáš Hykel
    2014-11-29

    The current development version (https://github.com/kvetak/RINA) provides calls for both dropping and ECN-marking a last packet in a queue from MaxQPolicy.

    I also added sample policies for Random Early Detection (that can both drop and mark PDUs) and the congestion control method described on https://wiki.ict-pristine.eu/wp2/d22/D22-CongestionControl (that one doesn't seem to use RED so it's simpler).

     
    Link

  • Tomáš Hykel
    Tomáš Hykel
    2015-02-03

    The functionality along with examples is now present in the stable version.

    ECN-marking of an incoming PDU should be done from MaxQueue policy via RMTQueue::markCongestionOnLast().

    An example setup of one policy configuration (RED Monitor + RED MaxQueue) can be seen in scenario SimpleRelay, configuration PingWithCongestion.

     
    Link

  • Tomáš Hykel
    Tomáš Hykel
    2015-02-03

    • status: open --> closed
     
    Link