Re: [AVTCORE] Fwd: New Version Notification for draft-shepherd-multicast-udp-guidelines-01.txt

Kevin Gross <kevin.gross@avanw.com> Sun, 30 June 2013 12:51 UTC

Return-Path: <kevin.gross@avanw.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC37121F994A for <avt@ietfa.amsl.com>; Sun, 30 Jun 2013 05:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.186
X-Spam-Level:
X-Spam-Status: No, score=0.186 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JDOzwTOd6TbQ for <avt@ietfa.amsl.com>; Sun, 30 Jun 2013 05:51:33 -0700 (PDT)
Received: from qmta09.emeryville.ca.mail.comcast.net (qmta09.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:96]) by ietfa.amsl.com (Postfix) with ESMTP id 8986D21F994C for <avt@ietf.org>; Sun, 30 Jun 2013 05:51:33 -0700 (PDT)
Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta09.emeryville.ca.mail.comcast.net with comcast id ucme1l0020vp7WLA9crYrq; Sun, 30 Jun 2013 12:51:32 +0000
Received: from mail-oa0-f51.google.com ([209.85.219.51]) by omta05.emeryville.ca.mail.comcast.net with comcast id ucpV1l00i177q698RcpWtS; Sun, 30 Jun 2013 12:49:31 +0000
Received: by mail-oa0-f51.google.com with SMTP id i4so3888671oah.10 for <multiple recipients>; Sun, 30 Jun 2013 05:49:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vasYF8M4/QfxAGEAnNfIhpY3tIzyaYRIJzk3ddYU7q8=; b=IuXdhWtDxupzwxOLc1RMXDQiUKxeX25He5qE6fgj20aJnu6DCeG6QzI0d+mXF9E01p Y2VfwALSDnjKw2jv7t6KxXkhlxpHRuP9UaD63A6JHoCCbxf78PYlK02ozR5kZg5RkavB fSxIH/rnt5zym+WbcYlzUSCVkUkMyCSFpW6K/lYXra9con6NJQmidoF02cgv0HfyIo9a nTMt/6GiQ+otBNXvNLoLUHRUWUr2o06nkUJyCedkFZTRfwdAJTOi26EiEkwLad89xLeP qFgUzqZfGZ5bTeKJXwVuLCncLZuxYtuKodd0gM60I+jRba9RGVpV9A9mXj2ul5HG0fTo Fj2A==
MIME-Version: 1.0
X-Received: by 10.60.97.34 with SMTP id dx2mr8081385oeb.54.1372596569488; Sun, 30 Jun 2013 05:49:29 -0700 (PDT)
Received: by 10.182.149.98 with HTTP; Sun, 30 Jun 2013 05:49:29 -0700 (PDT)
In-Reply-To: <CABFReBoR_-UVCHuOA_L5=dDVSFxomVtMcBsMMqaXKNyPtDS9dg@mail.gmail.com>
References: <20130612173141.16659.99790.idtracker@ietfa.amsl.com> <CABFReBoR_-UVCHuOA_L5=dDVSFxomVtMcBsMMqaXKNyPtDS9dg@mail.gmail.com>
Date: Sun, 30 Jun 2013 06:49:29 -0600
Message-ID: <CALw1_Q09A5S1tXcxqcYJVsPxVbLL6Y60nq45KAioBt-mOY4SrQ@mail.gmail.com>
From: Kevin Gross <kevin.gross@avanw.com>
To: gjshep@gmail.com
Content-Type: multipart/alternative; boundary="089e011619bef1c5f904e05e8aba"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372596692; bh=vasYF8M4/QfxAGEAnNfIhpY3tIzyaYRIJzk3ddYU7q8=; h=Received:Received:Received:MIME-Version:Received:Date:Message-ID: Subject:From:To:Content-Type; b=l66/OSsXM+T/zTxfN+yqdEPmobvUo5+imWF7MxT5JAsrVgouaJ4yK4tyMJlOesE4W WTkURbEz3yeKw0cpc6zx/90q6Xax9PTu4u2Weu1TdD45lfpogcPWqMysaFeja0TYQy t937Kur556B5RwQ5mPSDmrIUXMBRTVvlNKtaNIXMNgQz3DmbYgcMCglLebY2bb2X3I owrD4HdYMkayppHDqmwGctaKsDZxa9ehLG3GwCO0M12q8hhdkmAw8yEt6/UvJHF6+D UopVGARmcPnfq8Dts8qL0GdZ0fpcIrDMyECRNyVPZpWzJ9MVTDADKE4fYp0lmqG/Rd /3KO4CL1iiptA==
Cc: joel jaeggli <joelja@bogus.com>, rmcat WG <rmcat@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Subject: Re: [AVTCORE] Fwd: New Version Notification for draft-shepherd-multicast-udp-guidelines-01.txt
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jun 2013 12:51:38 -0000

It seems like this overlaps with what RMCAT is working on. We're trying to
quantify fairness to some degree. I have, for no scientific reason proposed
a factor of 3. How did you settle on a factor of 10 in your proposal?

Kevin Gross
+1-303-447-0517
Media Network Consultant
AVA Networks - www.AVAnw.com <http://www.avanw.com/>, www.X192.org


On Wed, Jun 12, 2013 at 11:35 AM, Greg Shepherd <gjshep@gmail.com> wrote:

> Please read and comment. I'd like to present this in Berlin, and get ample
> feedback before then in order to help this progress as quickly as possible.
> In addition to its overall value, it will be a helpful document in
> addressing outstanding Discuss issues in the RFC Editors' queue.
>
> Thanks,
> Greg
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>
> Date: Wed, Jun 12, 2013 at 10:31 AM
> Subject: New Version Notification for
> draft-shepherd-multicast-udp-guidelines-01.txt
> To: Greg Shepherd <gjshep@gmail.com>
>
>
>
> A new version of I-D, draft-shepherd-multicast-udp-guidelines-01.txt
> has been successfully submitted by Greg Shepherd and posted to the
> IETF repository.
>
> Filename:        draft-shepherd-multicast-udp-guidelines
> Revision:        01
> Title:           Multicast UDP Usage Guidelines for Application Designers
> Creation date:   2013-06-12
> Group:           Individual Submission
> Number of pages: 8
> URL:
> http://www.ietf.org/internet-drafts/draft-shepherd-multicast-udp-guidelines-01.txt
> Status:
> http://datatracker.ietf.org/doc/draft-shepherd-multicast-udp-guidelines
> Htmlized:
> http://tools.ietf.org/html/draft-shepherd-multicast-udp-guidelines-01
> Diff:
> http://www.ietf.org/rfcdiff?url2=draft-shepherd-multicast-udp-guidelines-01
>
> Abstract:
>    The multi-recipient nature of Multicast prevents the use of any pont-
>    to-point connection-oriented transport, therefore restricts all
>    Multicast data to be sent over the User Datagram Protocol (UDP).  UDP
>    provides a minimal message-passing transport that has no inherent
>    congestion control mechanisms.  Because congestion control is
>    critical to the stable operation of the Internet, applications and
>    upper-layer protocols that choose to use Multicast UDP as an Internet
>    service must employ mechanisms to prevent congestion collapse and to
>    establish some degree of fairness with concurrent traffic.  This
>    document provides guidelines on the use of UDP for the designers of
>    multicast applications and higher-level protocols.
>
>
>
>
> The IETF Secretariat
>
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>