TEWG draft-boyle-tewg-ds-nop-00.txt

[Jim Boyle <jimpb@nc.rr.com>]

NAME OF ID:

	draft-boyle-tewg-ds-nop-00.txt

	preview at http://www.tcb.net/meatloaf

SUMMARY:

  This ID gives a technical proposal in response to the Diffserv in TE
  networks requirements draft being discussed in the TE WG.

  In essense it states that these requirements can be met with
  existing TE specifications (namely the rsvp-tunnel and igp-te
  drafts) and that no new specifications or extensions are needed in
  order to meet the agreed upon scenarios and requirements.  A more
  generalized view of the semantics of the priority objects, as well
  as some additional flexibility in implementations would be required,
  as outlined in the memo.

RELATED DOCUMENTS

tewg requirements:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-01.txt

current specs:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-lsp-tunnel-08.txt
http://www.ietf.org/internet-drafts/draft-ietf-isis-traffic-03.txt
http://www.ietf.org/internet-drafts/draft-ietf-katz-yeung-ospf-traffic-05.txt

other proposal on table:
http://www.ietf.org/internet-drafts/draft-ietf-ospf-diff-te-00.txt
http://www.ietf.org/internet-drafts/draft-lefaucheur-diff-te-isis-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-mpls-diff-te-ext-01.txt

WHY IS IT TARGETED AT THIS WG

  As per IESG direction, requirements for enabling diffserv in traffic
  engineering environments, as well as initial protocol discussions
  are being hosted in TE WG.  This is a protocol discussion in
  response to stated requirements.

  Particular charter item is referenced in last paragraph of charter,
  and in at least four overdue milestones.

JUSTIFICATION

  See previous paragraph.