Subject: Re: TTL field in RSVP header

From: Bob Braden <[email-masked]>
Date: Fri, 12 Apr 2002 17:29:41 GMT

*> From [email-masked]  Fri Apr 12 07:46:43 2002
  *> Date: Fri, 12 Apr 2002 16:47:32 +0200
  *> From: Rosella Greco <[email-masked]>
  *> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
  *> X-Accept-Language: en-us
  *> MIME-Version: 1.0
  *> To: [email-masked]
  *> Subject: TTL field in RSVP header
  *> Content-Transfer-Encoding: 7bit
  *> X-AntiVirus: scanned by AMaViS 0.2.1
  *> 
  *> hi all,
  *>     is there someone who an explain me which are the points in konwing 
  *> the number of not-RSVP aware hops? (there is the TTL field in the header 
  *> of RSVP to this scope)
  *> Thank a lot
  *>           Rosella
  *> 

Hops that are not RSVP-capable are presumably not able to provide the
admission control and queuing discipline called for by the RSVP
signaling.  Their existence in the path must be detected, and this fact
must be passed to the local traffic control mechanism on each host and
end-to-end so the user knows she is not getting the requested QoS
"guarantees" on the entire path.

This should be clear from RFC 2205 and RFC 2210.

Bob Braden