RE: [Ieprep] IDs to consider

I would like to ask why this is being considered in the IEPREP WG when
the drafts were always submitted to
the TSVWG and have been discussed there.  I don't think there was any
notice given to the tsvwg that this topic was being moved here.  (Then
again, when Fred submitted these drafts to that WG on work that had
been submitted here, he never announced on this list that he was
moving the topic to that forum.  Despite the fact that he was
attacking my draft, he never notified me that he was doing so. )

As to the draft itself, it is still attacks MLEF (the title throughout
the document after the first page is "MLEF Considered Harmful") on the
assumption that no CAC is being used.  As has been stated in recent
MLEF drafts, in discussion in TSVWG, and in private conversations with
both Fred Baker and James Polk, if the CAC works as advertised, MLEF
will have no effect but if for any reason the CAC is unable to avoid
congestion, MLEF will ensure that only lower priority packets are
dropped.  Some of us have doubts as to how well a CAC can work. If a
100% effective CAC can be implemented and demonstrated, MLEF will be
unnecessary and a tiny amount of code wasted.  But if congestion does
arise, the high priority  call packets will get thru.

The dropping of packets due to congestion is not the fault of MLEF, it
is necessitated by the congestion.  All MLEF is doing is deciding
WHICH packets are to be dropped.  It does not add significant
processing or introduce any delay to the packets.

The DOD can not deploy VoIP without a prioritization mechanism.  MLEF
is such a prioritization mechanism.

Steve Silverman

> -----Original Message-----
> From: ieprep-bounces@ietf.org
> [mailto:ieprep-bounces@ietf.org]On Behalf
> Of King, Kimberly S.
> Sent: Friday, October 15, 2004 10:15 AM
> To: Ieprep (E-mail)
> Subject: [Ieprep] IDs to consider
>
>
>
>
> 	draft-baker-tsvwg-mlef-concerns-02.txt
> 	draft-baker-tsvwg-mlpp-that-works-02.txt
>
> The above IDs are not quite in our charter but they are
> relevant to the ieprep mission - we would like people
> on the list to review and comment on them with a view
> to recommending to the IESG that they
> be published as informational RFCs
>
> Scott & Kimberly
>
> _______________________________________________
> Ieprep mailing list
> Ieprep@ietf.org
> https://www1.ietf.org/mailman/listinfo/ieprep
>

_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep