Re: Last Call for draft-ietf-rolc-apr-00.txt

[Curtis Villamizar <[e-mail]>]

In message <[e-mail]>, Yakov Rekhter writes:
> 
> True. However, what would be the reason to make it impossible for an
> application to know how the network service (e.g. direct SVC vs going
> through routers) is being provided.
> 
> Yakov.

My ftp doesn't know which route it takes to get data onto my disk.  My
copy of vat doesn't know anything about how the data travelled from
the source to my speaker.  It shouldn't.  It should only know what the
traffic characteristics are and what the requirements are and provide
some parameters to aid the network in making the decision (elastic,
not delay sensitive, low minimum, moderate to high max, low cost vs
real time, prefer low delay, tolerant of delay variation, fairly low
bandwidth).  Parameterizing this belongs in int-serv, communicating it
to other nodes belongs in rsvp.  SVC management does not belong in the
application at all.  See Lixia's comments.

Curtis