Opened 8 years ago

Closed 7 years ago

#18 closed enhancement (fixed)

Need to say that ConEx is not applicable to multicast

Reported by: mattmathis@… Owned by: mattmathis@…
Priority: minor Milestone:
Component: abstract-mech Version:
Severity: - Keywords:
Cc:

Description

Per old message:

Date: Mon, 14 Dec 2009 18:18:14 +0000
From: Bob Briscoe <rbriscoe at jungle.bt.co.uk>
Subject: [re-ECN] ConEx?-IP & ConEx?-TCP as separate docs?
To: ConEx? IETF list <re-ecn at ietf.org>

I propose we rule multicast out of scope in ConEx?. Not because we're doign TCP-only, but because ConEx? is unnecessary for multicast (and it would be hard if you did need it).

The rationale behind ConEx? is that the sender controls unicast packet sending, so you need info on congestion at the sender's network. With multicast, the receiver can control whether it receives (even tho it can't control how fast it receives). So ECN is sufficient for multicast, without re-ECN.

We need to have this discussion tho, but that's a brief version of the argument.

Change History (1)

comment:1 Changed 7 years ago by rbriscoe@…

  • Resolution set to fixed
  • Status changed from new to closed

Under "3.3 Requirements for non-abstract ConEx? specifications"
Added that spec must state that ConEx? on multicast packets should be ignored, and note explaining why.

Note: See TracTickets for help on using tickets.