Attached herewith is a diffmarked .pdf file with comments that were posted some time ago to the author team of the Diffserv TE requirements draft, http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-01.txt. While some of the comments are purely editorial, a number of technical issues have been raised. As a response to the following call from Jim, they are now re-posted for discussion in the list. In addition to the comments in the attached file, the draft http://search.ietf.org/internet-drafts/draft-ash-mpls-diffserv-te-alternativ e-02.txt also addresses the following two requirements: 1. No new LSAs used to signal per-class-type (CT) available bandwidth, maximum bandwidth, preemption parameters, etc. Rather, CT-bandwidth allocated and protected by mechanisms that do not require new per-CT LSAs, as illustrated in the draft. 2. Limit to 6 CTs, which align QoS class (Y.1541/DiffServ), admission-control priority, restoration priority, preemption priority, traffic type (user/control), etc. Your comments on any of these aspects are welcome. Thanks, Wai Sum. -----Original Message----- From: Jim Boyle [mailto:jimpb@nc.rr.com] Sent: Thursday, August 23, 2001 11:35 AM To: te-wg@ops.ietf.org Subject: reminder: things todo in august and shortly thereafter From the minutes: o) End of August: Operators actually interested in Diffserv TE, read the requirements draft draft-ietf-tewg-diff-te-reqts-01.txt and provide feedback to list. Would like to wrapup the requirements draft by end of August! o) First week of September: After this time, please don't raise new issues with draft-team-restore-hierarchy-00.txt. The goal is to have the team revise and republish so as to be able to "hand off" to ccamp for consideration by last day of September.
draft-ietf-tewg-dste-reqts-00-08.pdf