[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PCN] New edge behaviour:draft-karagiannis-pcn-hose-edge-behaviour-00
Hi Fortune
Thank you very much for the comments!
Please see in line!
> -----Original Message-----
> From: Fortune HUANG [mailto:fqhuang at huawei.com]
> Sent: dinsdag 3 november 2009 10:42
> To: 'Georgios Karagiannis'; pcn at ietf.org
> Subject: RE: [PCN] New edge
> behaviour:draft-karagiannis-pcn-hose-edge-behaviour-00
>
> Hi Georgios,
>
> Basically, I think the HOSE model has its great advantage to
> solve the ECMP issue, which is well described in this draft.
>
> But I still have a comment that it should be the decision
> node that makes the decision to admit/block/terminate a flow.
> According to the PCN architecture, neither PCN-ingress-node
> nor PCN-egress-node contains the function of making decision.
> So I think the role of decision node is missing and the
> behaviour of making decision is misplaced in this draft.
Georgios: You are right, we are not emphasizing which entity is the decision
point.
Please note that the decision point can be either the ingress, the egress or
a centralized
decision point. Please note that in a future version of the draft we can
clarify this,
by explicitly using the notion of the decission point.
Best regards,
Georgios
>
> Best regards,
> Fortune
>
> -----Original Message-----
> From: pcn-bounces at ietf.org [mailto:pcn-bounces at ietf.org] On
> Behalf Of Georgios Karagiannis
> Sent: Wednesday, October 21, 2009 9:59 PM
> To: pcn at ietf.org
> Subject: [PCN] New edge behaviour:
> draft-karagiannis-pcn-hose-edge-behaviour-00
>
> Hi all
>
> During the last two IETF meetings I had promissed to publish
> the HOSE edge behaviour draft.
>
> Via the following URL you can find this draft:
>
> http://www.ietf.org/id/draft-karagiannis-pcn-hose-edge-behavio
ur-00.txt
>
> If you have any comments please let me know!
>
> --------------------------------------------------------
>
> Abstract ++
>
> Precongestion notification (PCN) is a means for protecting
> quality of
> service for inelastic traffic admitted to a Diffserv domain. The
> overall PCN architecture is described in RFC 5559. This
> memo is one
> of a series describing possible boundary node behaviours for a PCN
> domain. The behaviour described here is denoted as the HOSE model.
> In this document the term HOSE is referring to the
> aggregation of incoming traffic from all ingress edges, which is
> associated with one traffic class, i.e., PHB, towards one egress
> edge. This type of HOSE model is equivalent to the
> Multiple Point to
> Point (MP2P) type of aggregation.
>
> The HOSE model ensures bandwidth limits without the need of
> maintaining per each ingress and egress pair ingress-egress-
> aggregated states. In this case all edges maintain one aggregated
> state per each traffic class, i.e., PHB (Per Hop
> Behaviour), used in
> the PCN domain. Moreover, the HOSE model is able to
> provide solutions
> for the ECMP (Equal Cost Multi Path) problem for both admission
> control and flow termination procedures.
>
>
> -------------------------------------
>
>
>
> Best regards,
> Georgios
>
>
> _______________________________________________
> PCN mailing list
> PCN at ietf.org
> https://www.ietf.org/mailman/listinfo/pcn
>
>