RE: [ANCP] ANCP Multicast Admission Control

["OOGHE Sven" <Sven.Ooghe at alcatel-lucent.be>]

Hi Francois,

I'm ok with both suggested changes. They better reflect what I intended
to write.

Regards,
Sven 

-----Original Message-----
From: Francois Le Faucheur IMAP [mailto:flefauch at cisco.com] 
Sent: woensdag 30 januari 2008 12:05
To: OOGHE Sven
Cc: Francois Le Faucheur IMAP; ancp at ietf.org
Subject: Re: [ANCP] ANCP Multicast Admission Control

Hi again Sven,

I support introduction of the text you propose below for section
3.4.2.1 (related to our earlier agreement on being able to do CAC on
some flows and not on others).

Minor suggestions:
	- could change title into something like "By-passing admission
control for some flows" or "When not to perform admission control for a
subset of flows". The idea being that the title makes it clear that we
don't do CAC on some flows BUT still do CAC on others.
	- s/"so that other streams are not impacted"/"so that other
streams (that are subject to admission control) are not impacted"/

Thanks

Francois


>
> 3.4.2.1.  When not to perform Admission Control
>
>    In general, the Access Node and NAS may not be aware of all 
> possible
>    multicast groups that will be streamed in the access network.  For
>    instance, it is likely that there will be multicast streams offered
>    across the Internet.  For these unknown streams, performing 
> bandwidth
>    admission control may be challenging.
>
>    To solve this, these requests could be accepted without performing
>    Admission Control.  This solution works, provided that the network
>    handles the streams as best effort, so that other streams are not
>    impacted at times of congestion.
>
>    Disabling Admission Control for unknown stream can be achieved by
>    adding a "catch-all statement" in the Access Node white list or 
> grey
>    list.  In case the Access Node queries the NAS, the NAS on his turn
>    will have to accept the request.  That way, the unknown streams are
>    not blocked by default.
>
>    Next, in order to ensure that the streams are handled as best 
> effort,
>    the flow must be marked as such when entering the service provider
>    network.  This way, whenever congestion occurs somewhere in the
>    access/aggregation network, this stream will be kicked out before 
> the
>    access provider's own premium content.
>
>    The above concept is applicable beyond the notion of "Internet
>    streams" or other unknown streams; it can applied to known 
> multicast
>    streams as well.  In this case, the Access Node or NAS will accept
>    the stream even when bandwidth may not be sufficient to support the
>    stream.  This again requires that the stream is marked as best 
> effort
>    traffic before entering the access/aggregation network.
>



_______________________________________________
ANCP mailing list
ANCP at ietf.org
https://www1.ietf.org/mailman/listinfo/ancp