The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Apr> msg00102



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

cos tspec in RSVP-TE

  • From: Lou Berger <lberger@labn.net>
  • Date: Fri, 14 Apr 2000 06:57:14 -0400
  • Cc: mpls@UU.NET

At 08:56 PM 4/13/00 -0400, David Charlap wrote:
>Lou Berger wrote:
> >
> > Again, Adspec isn't needed with the Class-of-Service SENDER_TSPEC.
> > (It is optional per RFC2205.)
>
>Is it?
>
>I thought Adspec was only optional for the ingress node (or source host
>in non-MPLS RSVP), and that routers received a Path without an Adspec
>were required to provide one to the next hop.
>
>Do you mean that it's legal for a transit router to emit a Path message
>without an Adspec object?  (Assuming it received a Path without one, of
>course.)
>
>-- David

 From rfc2205:

RFC 2205                          RSVP                    September 1997


          The format of a Path message is as follows:

            <Path Message> ::= <Common Header> [ <INTEGRITY> ]

                                      <SESSION> <RSVP_HOP>

                                      <TIME_VALUES>

                                     [ <POLICY_DATA> ... ]

                                     [ <sender descriptor> ]

            <sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC>

                                     [ <ADSPEC> ]

Obviously, per RFC2210, ADSPEC is needed for int-serv.

Lou