The MPLS WG Archive

[Markus Jork <mjork@avici.com>]

There was a minor change from draft-ietf-mpls-rsvp-lsp-tunnel-04
to draft-ietf-mpls-rsvp-lsp-tunnel-05. The section about the
CoS Tspec/Flowspec maximum packet size (M) parameter now says:
"When the object is contained in Path
messages, this parameter is updated at each hop with the lesser
of the received value and the MTU of the outgoing interface."

This is clearly the wrong thing to do and unnecessary. It conflicts
with the traditional rsvp model where the sender_tspec characterizes
the sender's traffic and the adspec is used to gather information
along the path. Now requiring that a tspec has to be updated along
the path with link specific information is not a good idea, especially
when we don't gain any advantage by doing so. The adspec already
has the path mtu information and there is no point in collecting
the same information in the tspec where it doesn't belong.
And doing this because it is more convenient than parsing
an intserv adspec is a rather weak argument, too.

Markus