Re: [Tsvwg] Rr:Comments on draft-lefaucheur-rsvp-dste-02.txt

Francois, 

Each of the hosts issuing a RESV is waiting for an approval of its
request. When aggregation is performed, one might have the case where
the aggregate of the reservation could fail due to b/w, etc.  

In that case, a) shouldn't the aggregator inform the individual hosts
with a PathErr message? b) if the condition which caused the PathErr
message persists, say due to insufficient b/w for the aggregate, some
individual requests could have obtained a PATH if they had been
responded individually (i.e. through a PATH message instead of an
E2EPATH).

Regards,

Rurick

> >> 5) Section 3.6
> >> 
> >> On a reservation failure at the aggregator, is a PathErr 
> >> also sent out
> >> upstream (towards sender) ?
>  
> I don't believe so.
> In regular RSVP, Path Err report errors in the processing of Path
> messages. In case of CAC rejection on the Resv, we should just send a
> ResvhErr. The destination may decide to try make a smaller reservation
> or try a different Intserv service. Everything is normal as far Path is
> concerned.
> 
> >> Finally, you may want to mention somewhere (just to prevent 
> >> confusion)
> >> that these reservations are assumed to be unidirectional.
>  
> We can state that. But RSVP reservations are unidirectional of course,
> so sas there something specific that you feel would create confusion?
> 
> Thank you for your review an comments.
> 
> Francois
> 
> >> thanks,
> >> -arthi
> >> 
> 
> _______________________________________________
> tsvwg mailing list
> tsvwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/tsvwg
> 