Re: [rtcweb] Positioning draft-ietf-rtcweb-ip-address as a standards-track document

Victor Pascual Avila <victor.pascual.avila@gmail.com> Tue, 05 April 2016 12:32 UTC

Return-Path: <victor.pascual.avila@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3992012D16B for <rtcweb@ietfa.amsl.com>; Tue, 5 Apr 2016 05:32:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_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 WwBn6JkkaFDC for <rtcweb@ietfa.amsl.com>; Tue, 5 Apr 2016 05:32:44 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::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 3D2C712D096 for <rtcweb@ietf.org>; Tue, 5 Apr 2016 05:32:44 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id q128so16690226iof.3 for <rtcweb@ietf.org>; Tue, 05 Apr 2016 05:32:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-transfer-encoding; bh=87O0hTLtfXVSDfCn+rLTs0PC0A49yCYA/+XaZK+MyHQ=; b=sZu8K+ooPQpY+WuiRFmaIyt0WIgxJJX+bR1gXr5f/W3SY3t9TFmoAVx8XwrnqpzbrQ TA+X6ciyXlttX/mbXUxx8SBbYObk1m4pstEps0QpN3ry/Apc4dL6UPrVQqOiU8+wSrOE UMYaJAUiuCL4X6352ZV3IiBX49m8aESbu07LQr2DpGjZlfyUSke93T+w4DCae6u0aiGS Azz6zouGk3pfTjpb1c4Oz5s5xf8exw4WLcluzdaiiZ/k3VbMlNllexqfrMpYBOhoM4b8 xXcTF+BeevPWHCNlwYm/gSJDoisrUqHINlfj3aYKHblyToeVPG4+qHe1JBCpmViI1wFe aU+Q==
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:date :message-id:subject:from:to:cc:content-transfer-encoding; bh=87O0hTLtfXVSDfCn+rLTs0PC0A49yCYA/+XaZK+MyHQ=; b=SUiWcLhCv+DTNlOCkGCrQFmtASO4OeEyqlqA+xFvk3TKfTRNKiXqJzWbrMxTkfjNCf ftTP5YvYQzFMPDejZTOuqk3gFD34zPPslwQVNwieoRw/0UBHXqxvZdZlDIEkEmf8y5oa d8Yp5Y59BI+u1ObFuzeYYe1txcCrQd5yVxXAeNF8t6nxL+sVp2bucHiq0ZiT9MBo9V4j 5s5QNKgGZj+X2wLIrtlct3D86qswhCs8iwbMAPeMa9Dib1ZaemmNgc/8DxmBGfpUqtT5 wXHZOcqDFaVlw+2Frcp8ic4nriEB/OC2/f92DjRDUcXl3JELs7tZiwEaqB2+w7Paxrxc vodA==
X-Gm-Message-State: AD7BkJI7HddttaKW8pIUDqZ07Hzg3WUDUm9SyqHkTzsnjrcXP/0q12EEg8qub8gbuxI1nMxsUg4Mexiy5yD7gw==
MIME-Version: 1.0
X-Received: by 10.107.39.139 with SMTP id n133mr23042307ion.57.1459859563523; Tue, 05 Apr 2016 05:32:43 -0700 (PDT)
Received: by 10.79.126.207 with HTTP; Tue, 5 Apr 2016 05:32:43 -0700 (PDT)
In-Reply-To: <CAOJ7v-1yXCSYSZqCAoiirMsGFNgSmYdk0+6SJKvLUzuYkue2zg@mail.gmail.com>
References: <57004D0F.70300@alvestrand.no> <CAOJ7v-1yXCSYSZqCAoiirMsGFNgSmYdk0+6SJKvLUzuYkue2zg@mail.gmail.com>
Date: Tue, 05 Apr 2016 14:32:43 +0200
Message-ID: <CAGTXFp9grt5+oSCbf+BAhLwAdFzpTcZJqKC=ero8PVz6++CoSQ@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/6jHE1QCG2k5FeRucg2w-3ZAOMXI>
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Positioning draft-ietf-rtcweb-ip-address as a standards-track document
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 12:32:46 -0000

+1

On Tue, Apr 5, 2016 at 4:08 AM, Justin Uberti <juberti@google.com> wrote:
> Thanks for the concrete feedback. I agree with the proposed direction.
>
> On Sat, Apr 2, 2016 at 3:51 PM, Harald Alvestrand <harald@alvestrand.no>
> wrote:
>>
>> I've read through draft-ietf-rtcweb-ip-address again, with an eye to
>> seeing how it would read as a standards-track document.
>>
>> As such, it seems to me to provide rather tentative language in a few
>> places, which could be strengthened by use of the CAPITALIZED WORDS.
>> I think this is a Good Thing; if this is standards-track, with
>> imperative, normative language, an implementation can claim support for
>> RFC XXXX and expect the statement to be understood.
>> (Remember - there is no protocol police. Nothing forces people to
>> support RFC XXXX.)
>>
>> Changes needed:
>>
>> - Add the RFC 2119 incantation, including Stefan's addition ("lowercase
>> words mean what they usually do")
>>
>> - Replace all occurences of "We recommend that..." with "an
>> implementation MUST".
>>
>> - In section 3, end of first paragraph: "   Specifically, WebRTC
>> should:" -> "Implementations of this specification will:"
>>
>> - In section 4: "We recommend Mode 1 ... " -> "Mode 1 and mode 2 MUST be
>> supported. Mode 1 SHOULD be the default when the user has not granted
>> access to camera / microphone. Mode 2 SHOULD be the default when the
>> user has granted access to camera / microphone. The implementation MAY
>> provide means of letting the user or administrator select between modes.
>> These means MUST NOT be placed under the control of WebRTC applications."
>>
>> I think this would make the spec a more useful tool for specifying what
>> an application does.
>>
>>
>>
>> --
>> Surveillance is pervasive. Go Dark.
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>



-- 
Victor Pascual Ávila