The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] ASPEC and MTU
Sorry for the bad wording. What I am tring to say is that, in the TE draft, path MTU is used during transmission of data (Seciont 2.6). That path MTU should be derived from the FLOWSPEC, not the ADSPEC. - Mark > -----Original Message----- > From: David Charlap [mailto:david.charlap@marconi.com] > Sent: Tuesday, August 28, 2001 2:03 PM > To: mpls > Subject: Re: ASPEC and MTU > > > "Feng, Mark" wrote: > > > > ASPEC is to collect information along the path only. The decision > > for QoS, and what you refer to in the mail, should be derived from > > the FLOWSPEC. > > FLOWSPEC is provided by the egress router. It _IS_ the QoS request. > > The egress router chooses a FLOWSPEC based on anything it wants. > Typically, the TSPEC and ADSPEC that exist in the incoming > Path message > will be used to compute this. > > The TSPEC represents the QoS that the ingress router wants. > The ADSPEC > represents what the network is capable of providing. Between the two, > and maybe also some local policy decisions, the egress router > has enough > information to choose a FLOWSPEC. > > -- David > |
|