The MPLS WG Archive

["Feng, Mark" <m_feng@trillium.com>]

ASPEC is optional. It is used by the receiver to get information about the
path, such as the MTU. It is used because there is no negotiation in RSVP.
If it is not present, the receiver can either get the information through
other mechanism, or make the reservation without knowledge of the path, and
risk having the reservation request rejected, due to factors like path MTU.

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.

 - Mark

> -----Original Message-----
> From: Yuan Gu [mailto:Yuan.Gu@usa.alcatel.com]
> Sent: Tuesday, August 28, 2001 1:23 PM
> To: mpls
> Subject: ASPEC and MTU
>
>
> Hello, everyone:
>
>
> According to section 2.6 of draft-ietf-mpls-rsvp-lsp-tunnel-08.txt and
> RFC2210, MTU should be getten from ASPEC if Integrated Services object
> is presented in Path msg.
>
> On the other hand, ASPEC is an OPTIONAL object according to
> section 3.1
> of draft-ietf-mpls-rsvp-lsp-tunnel-08.txt.
>
> My quesions are:
>
> 1. In the case of Integrated Service Tspec is presented in
> Path msg, is
> ASPEC still OPTIONAL?
> 2. If the answer of above question is YES, how do we manage
> the Path MTU
> if ASPEC is not presented in Path msg?
>
> Thanks for your answer!
>
> Best Regards!
> Yuan Gu
>