[Teas] Comments on draft-chen-teas-rsvp-tts-00.txt

Dieter Beller <Dieter.Beller@alcatel-lucent.com> Wed, 22 July 2015 16:42 UTC

To: TEAS WG <teas@ietf.org>
From: Dieter Beller <Dieter.Beller@alcatel-lucent.com>
Organization: Alcatel-Lucent
Message-ID: <55AFC7F8.6080309@alcatel-lucent.com>
Date: Wed, 22 Jul 2015 18:42:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/teas/mWMaXdlSPMWj3tdDq0x5pNloElI>
Subject: [Teas] Comments on draft-chen-teas-rsvp-tts-00.txt
Precedence: list

Hi all,

as there was no time for discussion left at the meeting when 
draft-chen-teas-rsvp-tts-00.txt was presented, I am posting my comments 
on the list.

While RSVP signaling extensions can be defined easily for scheduled 
connections, this has quite severe impacts on other control plane 
components.
As far as the TED is concerned, time has to be added as an additional 
new dimension which adds a huge amount of complexity to the management
of network resources. Additionally, this information also has to be 
disseminated into the network in order to synchronize the TEDs in the 
different
control plane instances which creates a lot of additional IGP traffic.

Therefore, I do have strong reservations with what this draft is proposing.


Thanks,
Dieter

[Teas] Comments on draft-chen-teas-rsvp-tts-00.txt Dieter Beller