Re: [Perc] Confirmation of Consensus on PERC Double from IETF 99

Emil Ivov <emcho@jitsi.org> Thu, 10 August 2017 21:36 UTC

Return-Path: <emcho@jitsi.org>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78E3F132455 for <perc@ietfa.amsl.com>; Thu, 10 Aug 2017 14:36:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=jitsi-org.20150623.gappssmtp.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 zMIhQubSQ67H for <perc@ietfa.amsl.com>; Thu, 10 Aug 2017 14:36:10 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (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 2525C132452 for <perc@ietf.org>; Thu, 10 Aug 2017 14:36:10 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id t138so23748526wmt.1 for <perc@ietf.org>; Thu, 10 Aug 2017 14:36:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jitsi-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WJSRzc5dmgWpMwKRX092ys1Ih3kcbY1kV4+BVvPu42A=; b=gwU6pyPs7NME3dbZjI03EsXbb1u1g8S0rwzEkbcZV/WBHIx3x5SkUnApB3Pt7F+cy5 KnTB/xYVUNK3BQMCozdABq9Ldt5SUv8+WwPLuHgLIvG9sI3HpmljEOay5tRobqIypQKh woAi0WTXqy7jwWWRMUYM7DfwfwKvsRQyqbfdS3O8fFI1M1ahp4cHm/igwqZ1jhXZe6wv UJBm2JHGYCP6VmSPPgGNscFdXFz/tJ+vfE/VeJWLlQUvcSNYbWzF8d3mPVzhi8mcpFmj Q6FPGndGuZX/8ksVlWGQH/4YBrqZzNzU9fRa2zV+PH+znLIYzRhElfiEvfrHPUSarUhf Ldyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WJSRzc5dmgWpMwKRX092ys1Ih3kcbY1kV4+BVvPu42A=; b=gD16ftjC+397RQvCA2a1uR+ike3uyR7I0uUOjG4t/LvJSLU7T4PuVpAsQ7ck/eI37Q RbeZm6c/3vK0WE1k7y5DeA/OBvNRfyLdulOoxdL9fsc5W+Hqha7rluPRw9KNlaCQyYot JhI8WrSpzXWi0kKDgtCHdv2C0fNCc/6niuaIVYCtx4Gz5W99LZ5ICEhPMAJFqFNfn2ZV b3On6xhVMD7VxmuxrfXy020m4qrhZszjx/MGuWWPXBK6NVcXt5Zs+zCFbcirBWjYuNgH gihT0rnLigK3DtM5tBMBtjYl3pIMwB0f22rmDCTc4RIjdc+qeGgneZVZoFuKAEUfK/CY kLQA==
X-Gm-Message-State: AHYfb5hXfOxoSRv4unhECBsGLS6BhaKACV5GXMBEtxdPsqogQ8FEV5Dq 5px/jIF81k/ubsYPK3orxLGt/PzPejEV
X-Received: by 10.80.143.38 with SMTP id 35mr13342329edy.218.1502400968448; Thu, 10 Aug 2017 14:36:08 -0700 (PDT)
MIME-Version: 1.0
References: <CAMRcRGRW4JkyTSfUeDVWrXGAt0_x-yWhAzdKXDjkUJ0XH-P7cA@mail.gmail.com> <CAMRcRGSdPa6WDFDxCe=HxEsWA2fmb1_fEPBcybbgTsCRSGrdzQ@mail.gmail.com> <CAPvvaaJkL39k97tZf1gDtu-gcdf+gQmMRUW6Q_mxi91mPj5AMg@mail.gmail.com> <CAMRcRGS0B3Pg7wvuHjX5MBJ2BMKZJwA9Ggb0G783JfbzP=m6-A@mail.gmail.com> <CAPvvaaK8zZxKGnpKZR5Qp_Te2Cx+a_zbaGxRireKVFt5aLMPRQ@mail.gmail.com> <CAMRcRGSYFLRNd13GmtpepyGJu51-QVEVrsqAbFDqvg_QKeoX7g@mail.gmail.com>
In-Reply-To: <CAMRcRGSYFLRNd13GmtpepyGJu51-QVEVrsqAbFDqvg_QKeoX7g@mail.gmail.com>
From: Emil Ivov <emcho@jitsi.org>
Date: Thu, 10 Aug 2017 21:35:56 +0000
Message-ID: <CAPvvaaLz6NQypo65NKqbe60BGhATiCHZn_wYdeEiAnUwn_p2Xg@mail.gmail.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Cc: perc@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c194a3008f35005566cfcf8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/vNqveCTIJIhvba_vc6Lzx2VxzXM>
Subject: Re: [Perc] Confirmation of Consensus on PERC Double from IETF 99
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Aug 2017 21:36:13 -0000

On Thu, 10 Aug 2017 at 15:24, Suhas Nandakumar <suhasietf@gmail.com> wrote:

> Hello Emil
>
>    The votes that went to deciding consensus includes *both the  in-room
> and on-list responses* towards the proposal.  We had a strong consensus
> in the favor of the proposal in the room at the IETF 99 meeting (as
> reflected in the minutes and recordings).
>
> Hope this clarifies your question
>

Well no, of course it doesn't. It is unclear from the recording exactly how
much support there was during the meeting and there are no mails in support
of this proposal on the list.

There are some discussing it and some opposing it.

So why you choose to determine consensus in support of this proposal
remains a mystery to me. (Well not really)

Emil



> Cheers
> Suhas
>
>
>
> On Thu, Aug 10, 2017 at 8:29 AM, Emil Ivov <emcho@jitsi.org> wrote:
>
>> Suhas,
>>
>> I would really appreciate it if you could point me to mails on this list,
>> sent from the "substantially more people in the favor" that express theor
>> support?
>>
>> I am struggling to find any.
>>
>> Emil
>>
>> On Thu, 10 Aug 2017 at 10:26, Suhas Nandakumar <suhasietf@gmail.com>
>> wrote:
>>
>>> On Sun, Aug 6, 2017 at 2:26 PM, Emil Ivov <emcho@jitsi.org> wrote:
>>>
>>>> Come again?
>>>>
>>>> Regarding point 2, the only mail you received in response to your
>>>> request for confirmation were actually expressing the opposite.
>>>>
>>>> Is this working group really becoming that much of a joke?
>>>>
>>>
>>>
>>> Hello Emil,
>>>
>>> For calling the final consensus, the chairs considered the aggregate of
>>> inputs from the in-room consensus call at the IETF-99 and inputs on the
>>> email list. In effect, there were substantially more people in the favor of
>>> the proposal than against it. Hence following the IETF consensus process,
>>> the chairs made the final consensus call as described in
>>>
>>> https://mailarchive.ietf.org/arch/msg/perc/4JTYOVGcE9KXXjQ7ks3YRm7LFBI
>>>
>>> The WG has heard your concerns, but unless there are new technical
>>> arguments to be made, the consensus stands.
>>>
>>> Regards
>>>
>>> Chairs
>>>
>>>
>>>>
>>>> On Sun, Aug 6, 2017 at 3:42 PM, Suhas Nandakumar <suhasietf@gmail.com>
>>>> wrote:
>>>> > Hello All
>>>> >
>>>> >    Following up on the consensus confirmation email, the chairs have
>>>> > considered all the inputs received from the people in the room and the
>>>> > inputs from people on the email list and determined there is
>>>> consensus for
>>>> > the following 2 items.
>>>> >
>>>> > 1.   Allow MD to modify the 'M' (marker) bit.
>>>> >
>>>> > 2. Includes all the below
>>>> >     - Move the OHB information from header extension to payload
>>>> >     - RTX, RED and FlexFEC ordering : use the ordering of applying
>>>> repair on
>>>> > the double-encrypted packet. (Option 'A' in the slides)
>>>> >     - DTMF : PERC will only support E2E DTMF and MD will not be able
>>>> to read
>>>> > DTMF info sent as media
>>>> >
>>>> > Thanks for your inputs.
>>>> >
>>>> > Cheers
>>>> > Chairs
>>>> >
>>>> > On Thu, Jul 27, 2017 at 10:14 AM, Suhas Nandakumar <
>>>> suhasietf@gmail.com>
>>>> > wrote:
>>>> >>
>>>> >>
>>>> >> Hi All,
>>>> >>
>>>> >> At the IETF 99 meeting, we took hum on the following proposals and
>>>> there
>>>> >> was a strong consensus in the room in their favor, but we wish to
>>>> gather any
>>>> >> additional inputs on the list.
>>>> >> So, if there are any additional inputs that was not expressed in the
>>>> room,
>>>> >> please send them to the list by 4th August.
>>>> >>
>>>> >> First Consensus Call:
>>>> >>    Allow MD to modify the 'M' (marker) bit.
>>>> >>
>>>> >> Second Consensus called made includes all the following 3 proposals
>>>> as a
>>>> >> singleton:
>>>> >>     - Move the OHB information from header extension to payload
>>>> >>     - RTX, RED and FlexFEC ordering : use the ordering of applying
>>>> repair
>>>> >> on the double-encrypted packet. (Option 'A' in the slides)
>>>> >>     - DTMF : PERC will only support E2E DTMF and MD will not be able
>>>> to
>>>> >> read DTMF info sent as media
>>>> >>
>>>> >> Here are the notes from the meeting:
>>>> >>   https://www.ietf.org/proceedings/99/minutes/minutes-99-perc-01.txt
>>>> >>
>>>> >> Here are the slides corresponding to the above proposals :
>>>> >>
>>>> https://www.ietf.org/proceedings/99/slides/slides-99-perc-double-01.pdf
>>>> >>
>>>> >>
>>>> >> Thanks
>>>> >> Perc Chairs
>>>> >
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > Perc mailing list
>>>> > Perc@ietf.org
>>>> > https://www.ietf.org/mailman/listinfo/perc
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> https://jitsi.org
>>>>
>>> --
>> sent from my mobile
>>
>
> --
sent from my mobile