IETF Logo Mail Archive

Re: [v6ops] Android must allow root access

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 07 September 2017 07:53 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D67132EC4 for <v6ops@ietfa.amsl.com>; Thu, 7 Sep 2017 00:53:41 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 UmqmOlrTY69Y for <v6ops@ietfa.amsl.com>; Thu, 7 Sep 2017 00:53:39 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0AC0132EBC for <v6ops@ietf.org>; Thu, 7 Sep 2017 00:53:38 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 14E5CB1; Thu, 7 Sep 2017 09:53:36 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1504770816; bh=KIr+5yVmCNbRSh1U5P4ZpY0MnaeZF7W1zbw9cSFmD5E=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=XEtbfgsfz7TucThWb2ZmZDxZOHWnFTcS9y/HOfaiuIHOnx6GgEv8eyktTlxR3e9Pd FRJVB17xSSdqTX4qgBR0tp30EwgnBz9G7BYH3jDv5xJhQy7XYUtK1xBNy2v2eE83hj ba/HjvP9oHDF9Q/WSxWTu106EGDZgvE1gDxRm4EY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 12011AF; Thu, 7 Sep 2017 09:53:36 +0200 (CEST)
Date: Thu, 07 Sep 2017 09:53:36 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
cc: "v6ops@ietf.org" <v6ops@ietf.org>
In-Reply-To: <2f27efa3-dd4a-535d-dc2e-34f42d63d519@gmail.com>
Message-ID: <alpine.DEB.2.20.1709070951290.29378@uplift.swm.pp.se>
References: <7537deef-8f87-5187-1e44-595ac63a16ca@gmail.com> <9948cb75-6c11-9071-697f-a79702472132@gmail.com> <5c78ea63-6764-13a2-ddd4-ba7956694f4d@gmail.com> <f42ea748-ac6a-450d-cd49-aef9e1efd720@gmail.com> <9ea82cc815424d038978f46f94fbf5b3@XCH15-06-08.nw.nos.boeing.com> <0b5919f6-a146-2086-055b-7ac16787556a@gmail.com> <7367f3ec99ae42c2b425b38d80ca2abd@XCH15-06-08.nw.nos.boeing.com> <acf4bdf0-ec50-d7e1-a62c-8ca2aad6055c@gmail.com> <d2493aa78d6646268316ab24cfe591e9@XCH15-06-08.nw.nos.boeing.com> <7bd0ceb3-b17e-3448-d5ac-bf98dc1e6db4@gmail.com> <alpine.DEB.2.20.1709061916370.29378@uplift.swm.pp.se> <92c1bb9c-0d23-6037-e124-dfe74df530f7@gmail.com> <alpine.DEB.2.20.1709062000330.29378@uplift.swm.pp.se> <77f8d0a6-a717-7411-61d5-130c1246477d@gmail.com> <alpine.DEB.2.20.1709062135290.29378@uplift.swm.pp.se> <145ed661-5aa2-9ea6-593e-83ab6763871d@gmail.com> <alpine.DEB.2.20.1709070542490.29378@uplift.swm.pp.se> <2f27efa3-dd4a-535d-dc2e-34f42d63d519@gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/LVCpZq_lQ_K9uF6hx6wf1cZjNAY>
Subject: Re: [v6ops] Android must allow root access
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Sep 2017 07:53:42 -0000

On Thu, 7 Sep 2017, Alexandre Petrescu wrote:

> This is not a happy situation to be in.

Sure. But I don't see any standards-action here. You can write operational 
document how to get around the problem of hardware/software not 
implementing support for existing standards (which typically means 
tunneling).

But I doubt you're going to see anyone interested in standardizing unicast 
DHCPv6-in-3GPP with out-of-band address for DHCP communication. That seems 
more like a 3GPP profile than anything else.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email