Re: [Rum] Call for WG adoption of: draft-rosen-rue-01

Brian Rosen <br@brianrosen.net> Mon, 16 September 2019 15:24 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: rum@ietfa.amsl.com
Delivered-To: rum@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36A8A1202A0 for <rum@ietfa.amsl.com>; Mon, 16 Sep 2019 08:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.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 Lx_mEEK-ICr5 for <rum@ietfa.amsl.com>; Mon, 16 Sep 2019 08:24:26 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 DA6D0120052 for <rum@ietf.org>; Mon, 16 Sep 2019 08:24:25 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id z67so306026qkb.12 for <rum@ietf.org>; Mon, 16 Sep 2019 08:24:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eNNoDP5uSIYCnxAHJCYQqOZH5DH+KNyC+oUNxWETCxQ=; b=QoIdFZp4gIxhHL/pv1Hcgl8Z5u2YHLgpiQ+f+joO4x6APSBVc9rY1UCJqn2oNfFW9h CRDYWytBfq0VGX5XcpWuIlKhAT/yzJ56f5fJsDsHpl4PtGY/ceSqAeb6VlOm0FGSd+oA eOUTVrVpNx60ScV4f1drIgH3oj2pDZSHpKDgwbKub/1w6zyVmQIaUl6b+RdBoNvGNiNh cdpUvm+2rqJoY0AVY+l9gKh3EkcBUKu/v9UIT4AAd4r0jeP1WzC1UenPEnDuXtmI1Zy1 6LbG+oz5x6Tp9Oa5/CJccWUnJ9Iqb9RvIBLIxJGH2xSjxCniLENywEFVe4iAJ+5RqkMc NkkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=eNNoDP5uSIYCnxAHJCYQqOZH5DH+KNyC+oUNxWETCxQ=; b=JYUDLWVtJf+UJLvBKmEgXltuW9DACdOA5Y5IggRrR7WGzf3uAfnnHiXht5XD4d+yFh kbSzJ27yLfD+GXmTdzyr5Og1n2tVmPQeig5SXAMrMK/cj1FGR2K6oFL5+XVLR/1WTYq/ O5pGvk1rCF1EfBAnl6oBEJy3x1GeoPy6c+MMKNrhRmljWpIhQ6VEY9fnl9YXEiVIAoEW U1NdACr9hRem7ykgdmiBD8XggvoyRRrmGRiIDACyILolE1tEP62gzM4A7iaenMPohg4I 57v9+5eEKhH7Z2LTAKj6h3QYmZTv/feJtUnVxOlhfmSjASCDtrpP/95xhPI195/6Rh2X im2w==
X-Gm-Message-State: APjAAAX0YovFR133fLJmoybG9JEj5CAVA2pCiSCULi8x1VOIFQHGNFfh jdOllJbVOV+bZDci/BMFuHI17Q==
X-Google-Smtp-Source: APXvYqx0TkUmeZgbirPS2LtsqRjURvP2dZihyEZuAiTYGhKz8uFy20OoI93iNeqBaZ+iUrJP4QjL2A==
X-Received: by 2002:a37:6250:: with SMTP id w77mr483684qkb.153.1568647464811; Mon, 16 Sep 2019 08:24:24 -0700 (PDT)
Received: from brians-mbp-2388.lan ([24.154.122.195]) by smtp.gmail.com with ESMTPSA id z141sm9378833qka.126.2019.09.16.08.24.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Sep 2019 08:24:24 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <d2118081-1d81-3a43-8768-f9038f30ad4c@alum.mit.edu>
Date: Mon, 16 Sep 2019 11:24:22 -0400
Cc: "rum@ietf.org" <rum@ietf.org>, Isaac Roach <IRoach@sorenson.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <353212D6-B090-42E4-B2E6-9F5271BB12DA@brianrosen.net>
References: <f3c1d9fe-8785-86e9-4220-e7d7971b29d4@alum.mit.edu> <CAKewAXUHHEnZ1zYHkOkntLYLBUXX0Vy42hLBestKY5NNbQGn9g@mail.gmail.com> <d2118081-1d81-3a43-8768-f9038f30ad4c@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rum/Hio_ozFWgcx14f943btm4vFaJns>
Subject: Re: [Rum] Call for WG adoption of: draft-rosen-rue-01
X-BeenThere: rum@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Relay User Machine <rum.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rum>, <mailto:rum-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rum/>
List-Post: <mailto:rum@ietf.org>
List-Help: <mailto:rum-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rum>, <mailto:rum-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 15:24:30 -0000

With respect to 9-1-1: 
Devices don’t have any requirements to be able to support classic emergency calling (what we would call E9-1-1 in the US) other than, perhaps, the ability to dial a “service code”, like 9-1-1 or 3-1-1.  

With NG9-1-1 and the equivalents in the EU and elsewhere, the device has to conform to RFC6881.

Brian

> On Sep 16, 2019, at 11:18 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> Isaac,
> 
> On 9/14/19 8:59 PM, Isaac Roach wrote:
>> Hi Paul,
>> Sorenson has concerns about using the current draft as the starting point for the working group.
> 
> Right now this is the only candidate we have. Unless there is an indication that an alternative is forthcoming it will be a matter of an bird in the hand vs another in the bush.
> 
> If you wish to make an alternative proposal I am willing to help you with the mechanics of doing so.
> 
> Adopting this does not prevent addressing the points you raise below.
> 
>> For example, Sorenson agrees with your earlier comments highlighting the security issues that the draft presents and that it doesn't solve the client cert issue.
> 
> It would be helpful to have a discussion of the issue you want to solve. I sketch out my understanding of it in my comments. But if I properly understand your concerns then I don't know any way to satisfy them. And ISTM that web server developers should have similar concern about browsers and yet they manage without any similar verification.
> 
>> I also am concerned about how the draft addresses 911, requiring endpoints to comply with RFC6881 and to send geolocation information, rather than using the method that the FCC’s rules require (Registered Location).  
> 
> I hope Brian Rosen will respond to this, since he is expert in 911 issues.
> 
>> Sorenson would be concerned if these issues become part of a WG document.
> 
> Again, adopting this draft does not preclude subsequently addressing these issues. Your issues will need to be resolved one way or another before the resulting document can survive a last-call.
> 
> 	Thanks,
> 	Paul
> 
>> Thanks,
>> Isaac
>> On Thu, Aug 29, 2019 at 7:51 AM Paul Kyzivat <pkyzivat@alum.mit.edu <mailto:pkyzivat@alum.mit.edu>> wrote:
>>    This is a call for the adoption of draft-rosen-rue-01 as a RUM wg
>>    document. This is intended to evolve into the document our charter
>>    calls
>>    for.
>>    Comments, pro or con, on this proposal are due by Sunday September 15.
>>             Thanks,
>>             Paul Kyzivat, as RUM co-chair
>>    --     Rum mailing list
>>    Rum@ietf.org <mailto:Rum@ietf.org>
>>    https://www.ietf.org/mailman/listinfo/rum
> 
> -- 
> Rum mailing list
> Rum@ietf.org
> https://www.ietf.org/mailman/listinfo/rum