nsis-12----Page:4
1  2  3  4  5  6  7  8 

Updates to Current -05 QSPEC I-DMinor issues Removed individual MTU parameter as agreed at Interim Meeting (May 2005) Assume MTU is discovered by another process (e.g. see Path MTU Discovery (PMTUD) WG) MTU still part of because this is how it is defined by RSVP Leave as is? Added “Tunneled QSPEC Parameter Flag” When a RESERVE is tunneled, internal QNEs cannot update QSPEC information (e.g. expected Path Latency) If the QNE at the tunnel egress cannot update the information on behalf of the tunneled domain it raises the “Tunneled QSPEC Parameter Flag” One for each optional and mandatory parameter This is in addition to the “non-support flag” for optional parameters Define 2nd token bucket parameters for more precise traffic description E.g. for DiffServ This is an optional parameter The “first” token bucket is a mandatory parameter Differentiate the two token buckets by parameter IDs

PPT Version