From nobody Thu Mar 9 07:33:49 2017 Return-Path: X-Original-To: ppsp@ietfa.amsl.com Delivered-To: ppsp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66695129416 for ; Thu, 9 Mar 2017 07:33:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 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, URIBL_BLOCKED=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 VX9qtJC9mOUj for ; Thu, 9 Mar 2017 07:33:46 -0800 (PST) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 81F86129677 for ; Thu, 9 Mar 2017 07:33:46 -0800 (PST) Received: by mail-yw0-x22b.google.com with SMTP id v198so9376431ywc.2 for ; Thu, 09 Mar 2017 07:33:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dFLGyLcKlzeXPBYdo2K+1OEYPC5JlVGuJBJXCVl+5Es=; b=sLY4xPf/csXIdFJ3tUC9iZA5/4Q+0XI0WK+Ek3Fj2oHE/9nzc2iQg92XGZtnVfUzXA NXLPTUGq2DCZWLKwE4pyWvYpyJz8fvO4NjzRSCpZNmjGTOFQtAQ6p0IttlX29lqNfrav 61UlZIo5NBINrI9cdCgnRyYMHZqP9bHQvJcDEoEmfhAMXUWAajf56qAY+CptzGB3gEl6 kmDa/op677ReNLP/aYY6RY823yUgo7Br63S3xIEqMY4z3Tn1vImNWNYP/f4fCE3YgDOS daYMkXq90plItSQLasoL3/xUvZXih5Tmf20vtUKyItLxdYxuu6wrpmXe5RiquXug5b2a qZ1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dFLGyLcKlzeXPBYdo2K+1OEYPC5JlVGuJBJXCVl+5Es=; b=qUmhAAUD/A8230mIIVTj23iBwkwU2w7pld0NCP8kS0Zu1nX8TgvBBqu00QPRB4XKZI U4pOst2uoa19LhUS/ddcqZQOGco79aVwfy2Ae8RMrLNa3MebtHo041DQkc9C0fnA0P/0 0Bpqs2ulp46LV0jUFiWSfXeeB0pngl6gq6xeR7m4BH+9eUuOdIg9oPrueEEGCZvFQ6BJ Ap58XpJnvT+R0KLgIsu4DCI7UgH9KwStlIu6D3EDt4m3uHnu7nJWB2g/44fM4wmHHf0R D0WPix2OJzNj8XbBLz25IaF6+cqE0UDdcx3YPC0IwIKgYU2FgxgUoXfxGXYCghg9OpGa DC0g== X-Gm-Message-State: AMke39k3fyS5XpEsVELakM6AgsM9sbaOsMMWe7baer0UZ+G2GviWKaHT/NH7mKlUaEXMkYEcch4Ti9lpqyj8CA== X-Received: by 10.129.152.22 with SMTP id p22mr4510027ywg.276.1489073625851; Thu, 09 Mar 2017 07:33:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.77.197 with HTTP; Thu, 9 Mar 2017 07:33:45 -0800 (PST) In-Reply-To: References: From: Spencer Dawkins at IETF Date: Thu, 9 Mar 2017 09:33:45 -0600 Message-ID: To: Riccardo Petrocco Content-Type: multipart/alternative; boundary=94eb2c0b8fb48370e3054a4df843 Archived-At: Cc: ppsp Subject: Re: [ppsp] Feedback on Errata for RFC 7574, "Peer-to-Peer Streaming Peer Protocol (PPSPP)" X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Mar 2017 15:33:48 -0000 --94eb2c0b8fb48370e3054a4df843 Content-Type: text/plain; charset=UTF-8 Hi, Riccardo, On Wed, Feb 8, 2017 at 9:11 AM, Spencer Dawkins at IETF < spencerdawkins.ietf@gmail.com> wrote: > Hi, Riccardo, > > On Wed, Feb 8, 2017 at 9:10 AM, Riccardo Petrocco > wrote: > >> Dear Spencer, >> >> Thank you for for keeping us updated on the progress. >> I'll try to go over the feedback, and come back with my thoughts. >> > Have you had an opportunity to look at these errata yet? Thanks, Spencer > > Thanks! > > Spencer > > >> Have a nice day, >> Riccardo Petrocco >> >> 2017-02-08 16:01 GMT+01:00 Spencer Dawkins at IETF < >> spencerdawkins.ietf@gmail.com>: >> >>> Dear PPSPers, >>> >>> We've had implementers for your RFC, which is good, and some feedback >>> from them, filed in the IETF Errata system. >>> >>> We'd like your thoughts on these three errata, so we'll know what to do >>> with them. If the resolutions are approved, other implementers will have an >>> easier time in their work. >>> >>> The errata are available at https://www.rfc-editor.org/ >>> errata_search.php?rfc=7574. >>> >>> We thank you for your help. >>> >>> Spencer Dawkins, TSV Area Director >>> >>> _______________________________________________ >>> ppsp mailing list >>> ppsp@ietf.org >>> https://www.ietf.org/mailman/listinfo/ppsp >>> >>> >> > --94eb2c0b8fb48370e3054a4df843 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi, Riccardo,

On Wed, Feb 8, 2017 at 9:11 AM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
Hi, Riccardo,

On Wed, Feb 8, 2017 at 9:1= 0 AM, Riccardo Petrocco <r.petrocco@gmail.com> wrote:
=
Dear Sp= encer,

Thank you for for keeping us updated on the progress.
I'll try to go over the feedback, and come back with my thought= s.

Have you had an opportunity to look at these errata yet?

Thanks,

Spencer
= =C2=A0

Thanks!
Spencer
=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Have a nice day,
Riccardo Petrocco

2017-02= -08 16:01 GMT+01:00 Spencer Dawkins at IETF <spencerdawkins.= ietf@gmail.com>:
Dear PP= SPers,

We've had implementers for your RFC= , which is good, and some feedback from them, filed in the IETF=C2=A0Errata=C2=A0system.=C2=A0

We'd like your thoughts on these three=C2=A0errata, so we'll know what to do with them. If the resolutions= are approved, other implementers will have an easier time in their work.

The=C2=A0errat= a=C2=A0are available at=C2=A0https://www.rfc-editor.org/erra= ta_search.php?rfc=3D7574.=C2=A0

We thank you for your help.

Spencer Dawkins, TSV Area Director

_______________________________________________
ppsp mailing list
ppsp@ietf.org
https://www.ietf.org/mailman/listinfo/ppsp




--94eb2c0b8fb48370e3054a4df843-- From nobody Fri Mar 24 08:16:14 2017 Return-Path: X-Original-To: ppsp@ietfa.amsl.com Delivered-To: ppsp@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68B09129416 for ; Fri, 24 Mar 2017 08:16:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 nZ5QH1h6RzpX for ; Fri, 24 Mar 2017 08:16:11 -0700 (PDT) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 3A6C2126D73 for ; Fri, 24 Mar 2017 08:16:11 -0700 (PDT) Received: by mail-qt0-x235.google.com with SMTP id r45so4768579qte.3 for ; Fri, 24 Mar 2017 08:16:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NjwZiP1r1UtW5DiHZPPvnAyRcbgLYWx9q5zTZQKJO8w=; b=RbHEJJq45xnQ+yQIn+fJRUCsDwvuTckgcAqeZtB8GQevUnp49HI/vfh0eIouXCItx2 ktLNWddA9Nuef+zgHkO4/6L2mX9XccMNM3YyE1yQC5Ief3faTzP/j5Rag58K3pZwP/VO Z/dW4jvUSz5nldCdAf9UVOhFsXVcJKf5ozV+D+nbHMoXskQbdwr1umjl3sXPyO1EH4PN WyXv0wYhljMBBP29XuVrIm4EirbKg88GyejAzACM6+gSVDvJ7H7AxyIYOgjv0wq7gm7G MUSW8XA48JKF2QB3KIVoGrBndAoYOuSqzd3PK5hrwG6wzXQ/MILXaMg4cmLxZLUpHylq AgwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NjwZiP1r1UtW5DiHZPPvnAyRcbgLYWx9q5zTZQKJO8w=; b=KaRFnGLkAmU/dI+JfsnUe21okiByY0rmJezn7g/wXwKZc811BuUZjLmIwh9diX38x0 O1uVmlAZPPcWZWiJ0sh2XpPzf9QLNAEi8xBRnyBt0i0g5p9ZqaUCXITD6O+SPh3mdRfd F40kHxz8BgyLyAtAP/7TVo1xkne4lbQn3QkYekJtT0dcyM6NnidkStsKz/252O35flgf Y6QuohZzS6ETb0Y3aVn+ZqjtbCOpLV3wCnAzh7szNwr7v+lglCmVS+qnitOs1eCKz0gx iqxn7BNLcyFNkC/VIt9+fWhPj4G0dMNgSGDrsPN+9lAbfSrlsSA5Tyk9JYWutuJE+2kx Dtng== X-Gm-Message-State: AFeK/H0fUwv6yU9/75b5jmq6H5TWbwjh4SQg6Jrmn8ajrVjuXIyXiGXkdIYVwQq3xAEvCP1Bz00fJXBmR4lfnQ== X-Received: by 10.237.33.143 with SMTP id l15mr8186899qtc.222.1490368570245; Fri, 24 Mar 2017 08:16:10 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.58.194 with HTTP; Fri, 24 Mar 2017 08:15:29 -0700 (PDT) In-Reply-To: References: From: Victor Grishchenko Date: Fri, 24 Mar 2017 16:15:29 +0100 Message-ID: To: Spencer Dawkins at IETF Cc: Riccardo Petrocco , ppsp Content-Type: text/plain; charset=UTF-8 Archived-At: Subject: Re: [ppsp] Feedback on Errata for RFC 7574, "Peer-to-Peer Streaming Peer Protocol (PPSPP)" X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Mar 2017 15:16:13 -0000 I generally support Mr Kim and Mr Lee. That no-protection option is not well defined and better be removed. We need integrity protection just to store data locally. That way, we protect it from disk corruptions/failures. I believe that no-protection is an unnecessary optimization. After all, an optimistic receiver may not check those hashes to speed things up. By the way, the DAT project made some use of the RFC. https://datproject.org On 9 March 2017 at 16:33, Spencer Dawkins at IETF wrote: > Hi, Riccardo, > > On Wed, Feb 8, 2017 at 9:11 AM, Spencer Dawkins at IETF > wrote: >> >> Hi, Riccardo, >> >> On Wed, Feb 8, 2017 at 9:10 AM, Riccardo Petrocco >> wrote: >>> >>> Dear Spencer, >>> >>> Thank you for for keeping us updated on the progress. >>> I'll try to go over the feedback, and come back with my thoughts. > > > Have you had an opportunity to look at these errata yet? > > Thanks, > > Spencer > >> >> >> Thanks! >> >> Spencer >> >>> >>> Have a nice day, >>> Riccardo Petrocco >>> >>> 2017-02-08 16:01 GMT+01:00 Spencer Dawkins at IETF >>> : >>>> >>>> Dear PPSPers, >>>> >>>> We've had implementers for your RFC, which is good, and some feedback >>>> from them, filed in the IETF Errata system. >>>> >>>> We'd like your thoughts on these three errata, so we'll know what to do >>>> with them. If the resolutions are approved, other implementers will have an >>>> easier time in their work. >>>> >>>> The errata are available at >>>> https://www.rfc-editor.org/errata_search.php?rfc=7574. >>>> >>>> We thank you for your help. >>>> >>>> Spencer Dawkins, TSV Area Director >>>> >>>> _______________________________________________ >>>> ppsp mailing list >>>> ppsp@ietf.org >>>> https://www.ietf.org/mailman/listinfo/ppsp >>>> >>> >> > > > _______________________________________________ > ppsp mailing list > ppsp@ietf.org > https://www.ietf.org/mailman/listinfo/ppsp > -- Victor