[Lwip] Spencer Dawkins' Yes on draft-ietf-lwig-cellular-05: (with COMMENT)
"Spencer Dawkins" <spencerdawkins.ietf@gmail.com> Wed, 16 September 2015 18:31 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD251A889B; Wed, 16 Sep 2015 11:31:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001] autolearn=ham
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 rp_FTdPtz534; Wed, 16 Sep 2015 11:31:54 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C3C3E1A887E; Wed, 16 Sep 2015 11:31:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150916183154.4711.69709.idtracker@ietfa.amsl.com>
Date: Wed, 16 Sep 2015 11:31:54 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/lwip/TNGor_Ukrq-lvVDYYkUbsBGw6uQ>
Cc: lwip@ietf.org
Subject: [Lwip] Spencer Dawkins' Yes on draft-ietf-lwig-cellular-05: (with COMMENT)
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.15
List-Id: Lightweight IP stack <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Sep 2015 18:31:57 -0000
Spencer Dawkins has entered the following ballot position for draft-ietf-lwig-cellular-05: Yes When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-lwig-cellular/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Nice work. I had a couple of thoughts while reading through it. This is a very useful draft. Thank you for producing it. You mention the difficulty of acting as a server behind a NAT. I wonder if you might also mention the power drain that's often required to maintain port bindings on NATs when a device is not actively transmitting. That may not be a problem for sleepy devices, but might be for real-time reachable devices. In this text Manufacturer Server The DNS name of the directory or proxy is hardwired to the software by the manufacturer, and the directory or proxy is actually run by the manufacturer. This approach is suitable in many consumer usage scenarios, where it would be unreasonable to assume that the consumer runs any specific network services. The manufacturer's web interface and the directory/proxy servers can co-operate to provide the desired functionality to the end user. For instance, the end user can register a device identity in the manufacturer's web interface and ask specific actions to be taken when the device does something. Delegating Manufacturer Server The DNS name of the directory or proxy is hardwired to the software by the manufacturer, but this directory or proxy merely redirects the request to a directory or proxy run by the whoever bought the device. This approach is suitable in many enterprise environments, as it allows the enterprise to be in charge of actual data collection and device registries; only the initial bootstrap goes through the manufacturer. In many cases there are even legal requirements (such as EU privacy laws) that prevent providing unnecessary information to third parties. The reference to legal requirements under "Delegating Manufacturer Server" made me think this was only appliable to "Delegating Manufacturer Server", but not to "Manufacturer Server". Is that the case? Or is it applicable whether the Manufacturer Server is delegating or not? I share Stephen's comment on Figure 1.
- [Lwip] Spencer Dawkins' Yes on draft-ietf-lwig-ce… Spencer Dawkins
- Re: [Lwip] Spencer Dawkins' Yes on draft-ietf-lwi… Jari Arkko