Re: [Spud] updated draft PLUS charter, rev. 1 June

Ted Hardie <ted.ietf@gmail.com> Tue, 07 June 2016 21:17 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3596012D6A6 for <spud@ietfa.amsl.com>; Tue, 7 Jun 2016 14:17:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MsvVCKy_z2oE for <spud@ietfa.amsl.com>; Tue, 7 Jun 2016 14:17:37 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6B5C12D508 for <spud@ietf.org>; Tue, 7 Jun 2016 14:17:37 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id k23so297827719oih.0 for <spud@ietf.org>; Tue, 07 Jun 2016 14:17:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JlAR+Uo033QNPxKsOLxBC4PfFC+acb4jF+XghXqP01A=; b=cm6ys4a5EtzfUN6OyRs5rKqkiPVroRVUfnipgUZ+WXU7bD9xJsezmduSYHPvKgNMVH iWt1GRa0pWuNVu8v9RR+2eEgbto6W9FmKqI/f3oGV4RMe32vxjyEJ2TTKBpU15TqR9sP ZEjV+JesM4BHddaojouzQLVpp8i7DJzWM1SexzK4lLqMbeqVJCxWEwCIFADKB0ePsavL X8N3iy9Zrl0JH7bvrw++x7Ho9K7ZILBxHPsHXg+owfg/n5bH6vZ8xK2DoVPjK2QXOCW2 z+1MEH7F5Qymef4spJNb6j4oxqXH4YMIF0zsjuyqG56ChMZuBgm1QDIeZSwV3L9jCYYC zsGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JlAR+Uo033QNPxKsOLxBC4PfFC+acb4jF+XghXqP01A=; b=RuElQgA+HXj6v0njYw80LmLRVxVO6m7aNCx3kHiDiQxSo5oRV5J2sQsY+doP4fyEkc 5bgsl+4l1+sBgRRAeZgbptyNhqlmyIeF3dCXBBuJpB3yWMyBis64ec68ZnzDuq6ajuND vV/f0xnX7A0WsHhN+qplGgisx/BJ0OoliCB8w9ANrizYiPxFZ6B3IsX1go0asgE8A/oq MJLeB2b55QVLFFQ03JABXntK2zJpeWT6hku7So1gn228i1woot2PgHH+ew9cFr318WuW LxRg3wImt29EsGoe91s0x7a9YqN9/YAgMlN4Ft5Q2clkg4iQC+/STX64y6OfwDJt3Ow4 ICUw==
X-Gm-Message-State: ALyK8tLib4nFbqwGeu6VM00gqrhqU7J1cSfLvw54kgRVpDFEGTKf1xobLVu/9ri12nRUnB5ycZRU+kahyOVAEA==
X-Received: by 10.202.87.205 with SMTP id l196mr236064oib.53.1465334257168; Tue, 07 Jun 2016 14:17:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.171.146 with HTTP; Tue, 7 Jun 2016 14:17:17 -0700 (PDT)
In-Reply-To: <CALx6S37rY=JsvnxiEEa0agNr4ZX2wV6O7uoH6kPRkpNsL9XfXg@mail.gmail.com>
References: <85E24D9D-F666-49C3-A022-2F207227A153@trammell.ch> <CAD62q9UiLi1ffGPm=xEXOSH=sqZPv7hYiNBTGvAX52a9dhV8yg@mail.gmail.com> <CALx6S34kEjb4R+RCcv32TGFqGYVk6JsHWoo3t6n6qHFmjF1TpQ@mail.gmail.com> <FE1B3918-6A8A-4905-9D09-34687DA91016@gmail.com> <CALx6S37rY=JsvnxiEEa0agNr4ZX2wV6O7uoH6kPRkpNsL9XfXg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 07 Jun 2016 14:17:17 -0700
Message-ID: <CA+9kkMDPFS8Rvd0Bp55pkYjgPq9VpNafexDCp5BRTCbQgvkLtw@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
Content-Type: multipart/alternative; boundary="001a113df23ee03a360534b6b7be"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spud/PjxG5hZOVBW-FxVvVQQl5KsBGGQ>
Cc: Aaron Falk <aaron.falk@gmail.com>, Brian Trammell <ietf@trammell.ch>, spud <spud@ietf.org>
Subject: Re: [Spud] updated draft PLUS charter, rev. 1 June
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2016 21:17:40 -0000

On Tue, Jun 7, 2016 at 1:47 PM, Tom Herbert <tom@herbertland.com> wrote:

> On Tue, Jun 7, 2016 at 1:41 PM, Aaron Falk <aaron.falk@gmail.com> wrote:
> >
> > On Jun 7, 2016, at 4:37 PM, Tom Herbert <tom@herbertland.com> wrote:
> >
> > 1st para of the charter says “The working group will not specify any new
> > transport protocols.” and the 5th para says “The PLUS working group will
> > specify a new protocol”.  I think the latter statement is correct.
> > I’d like to see a comment on PLUS re-enabling ICMP functionality
> >
> >
> > What does "re-enabling ICMP functionality" mean?
> >
>

ICMP often isn't available to the application; by putting similar
information in in-band signalling, it would reach the application.  For the
RTP application I noted above, for example, that might result in a codec
shift or change in FEC tuning.

regards,

Ted