Signaling 3 PCN states with baseline encoding

PCN based admission control functions best with threshold marking. This means, that once PCN traffic is above a links PCN-threshold-rate, all PCN packets passing this link are marked. With baseline encoding, only two codepoints are available to signal a links pre-congestion state. As all PCN traffic is marked with the single available codepoint to indicate any (pre) congestion state, there's little solution space to further differentiate crossing of the PCN-excess-rate by a codepoint or by excess marking (the latter being the more suitable marking behaviour to indicate that a links PCN load reached termination state).

Admission control is realised by threshold marking of PCN traffic, once the PCN traffic is above a links PCN-treshold-rate. If PSDM is applied, no PCN egress measurement functionalities need to be supported to operate admission control. Admission control is thus operated as suggested by combining mechanisms already proposed for standardisation. Assuming that the PCN rate is strictly limited above the PCN-excess-rate by the links physical bandwidth or by a policer and further assuming this PCN rate limit to be, say, no more than 10% above the PCN-excess-rate, then excess marking would result in no more than 10% of the packets above PCN-excess-rate to be marked. If admission control is applied to path coupled signaling packets with a piggybacked probing functionality between PCN boundary nodes (which consists of setting the ECN field of that signaling packet), starting to mark only packets above the PCN-excess-rate as "M/CE" once the latter is passed doesn't result in desirable operational conditions. As only a small percentage of traffic is marked, most PSDM coded admission requests have a good chance to pass the pre-congested link without being marked and lead to admission of new PCN traffic. If however the operational regime of the excess rate marker is "inverted", and the percentage of traffic excessing the PCN-excess-rate is left unmarked (i.e. "NM" coded), then PSDM admission control will prevent admission of 90% or more of the user sessions requesting admission. Please note, that the threshold marker still continues to mark all packets crossing the link and so the excess marker would indeed have to unmark packets again (if marking is realised eg. by sequential single rate token buckets). The marking behaviour as described in pcn-marking-behaviour has to further be changed in the following way to support the functionalities specified by this document. Two encoding states are available: one for "PCN-marked" one for "not PCN-marked". The metering and marking function MUST be implemented to support the following threshold and excess-traffic marking functions: All PCN packets MUST be counted by the PCN meter. Threshold marking MUST be executed prior to (or simultaneously with) excess traffic marking. To threshold mark a packet, its PCN mark is set to "PCN-marked" (M/CE following pcn-baseline-encoding). To excess-traffic mark a packet, its PCN mark is set to "not PCN-marked" (NM/ECT0 following pcn-baseline-encoding). Additionally, this document has outlined already, that two marking behaviours are combined with PCN baseline encoding and this so far isn't part of pcn-marking-behaviour. The concept is illustrated by .

Schematic of how PCN's baseline encoding-3state admission control and flow termination mechanisms kick in as the rate of PCN-traffic increases, for a PCN-domain with three encoding states (modified from [architecture]). pcn-architecture. A way to further increase the probability of blocking new flows requesting admission, while a PCN interface reached termination state is to generally "unmark" only a known share of the excess traffic (say 50% or 10% of the packets to be unmarked at the excess rate instead of all of them). This however may make it more difficult for an egress node to correctly determine the termination rate of a small PCN aggregate that has passed a link in termination state.

If the behaviour exposed in the case of termination marking allows an egress node to non ambiguously identify termination state for an aggregate, then it can request the sources to terminate (or reduce) their traffic. As only a single code point is used to signal pre congestion states and two different marking behaviours indicate the pre-congestion status, this solution may be deployed within MPLS networks, where only 8 Codepoints are available to support DiffServ and ECN. Finally, it should be noted that by support of PSDM no rate measurements are required for admission control and that for termination, the egress node is able to measure traffic rates and take decisions on termination without having to provide feedback to another PCN node within its PCN domain.

Experimental simulation may not require the development of new code for policers if egress and ingress policers can be simulated on both ends of a PCN link. The egress policer of the PCN egress interface operates the threshold policer at the PCN-threshold-rate. The ingress policer of the ingress interface of the PCN node connected by the link is set to meter packets marked as "PCN/CE". Operated in "excess mode", it starts to mark packets as "PCN/NM", once the rate of PCN/CE marked packets crosses the "PCN-excess-rate" which it is configured for. Obviously, the termination threshold MUST be bigger or equal to the admissible rate configured at the other end of the link. Routers supporting ingress and egress policing could also be used, which would allow experiments with real equipment, if desired.

The question, whether it is at all possible to infer the current operational state of one or more pre-congested interface(s) of a PCN domain by interpretation of the marking behaviour observed by the PCN egress nodes can't be answered yet. This section lists a few operational conditions under which the proposed two state marking three state signaling method must work reliably or reasonably stable, respectively. Differing oscillating "admission"/"admission stop" state from termination state. This operational condition is likely to be present and the egress node MUST be able to reliably differ admission stop state from termination, if such oscillating "admission"/"admission stop" state is occurring. Admission of sessions during termination state. As a certain percentage of packets will pass the pre congested interface unmarked during termination state, a number of new sessions will be admitted while others are terminated. The egress nodes MUST be able to terminate more traffic swiftly to push the PCN traffic rate below the PCN-excess-rate despite admission of new sessions while this link is in termination state. If traffic that has passed a PCN interface in termination state later on passes a PCN interface in admission stop state, an end node will no longer be able to recognise the termination state of the prior PCN node, as all packets passing the interface in admission stop state will be "PCN-marked". If traffic that has passed a PCN interface in termination state later on passes another PCN interface in termination state, an end node will only recognise the termination state of the last PCN node by the relation of "not PCN-marked" to "PCN-marked" packets as created by the last interface in termination mode.