Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

<> Fri, 30 January 2015 08:07 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 3AE9B1A89B3 for <>; Fri, 30 Jan 2015 00:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jOUxir2QP-Do for <>; Fri, 30 Jan 2015 00:07:51 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 09DE01A899A for <>; Fri, 30 Jan 2015 00:07:51 -0800 (PST)
Received: from (unknown [xx.xx.xx.200]) by (ESMTP service) with ESMTP id 76D6B374169; Fri, 30 Jan 2015 09:07:49 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id BD5E815809E; Fri, 30 Jan 2015 09:07:48 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([]) by OPEXCLILH05.corporate.adroot.infra.ftgroup ([]) with mapi id 14.03.0224.002; Fri, 30 Jan 2015 09:07:48 +0100
From: <>
To: James Woodyatt <>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
Thread-Index: AQHQOxuJv5W9vu3skUKiVKZnDa9kKZzW83IAgACD6oCAANm6QA==
Date: Fri, 30 Jan 2015 08:07:48 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004902567@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933004902567OPEXCLILM23corp_"
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.12.16.134821
Archived-At: <>
Cc: IPv6 Ops WG <>
Subject: Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 30 Jan 2015 08:07:53 -0000

Dear James,

Your proposed wording is OK with me.

I implemented it in my local copy, thanks.


De : v6ops [] De la part de James Woodyatt
Envoyé : jeudi 29 janvier 2015 21:07
À : IPv6 Ops WG
Objet : Re: [v6ops] draft-ietf-v6ops-mobile-device-profile last call


Editorial: the section for Security Considerations currently says this:

Security-related considerations that apply when the cellular device provides LAN features are specified in [RFC6092<>]2>].

This sentence is a bit awkward— but more importantly, RFC 6092 is not a specification, and the chain of citation that lead to its reference here is far from clear.  I suggest the following wordier but more helpful replacement:

In the case of cellular devices that provide LAN features, compliance with L_REC#2 entails compliance with RFC 6204, which in turn recommends compliance with Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet Service [RFC6092<>]2>]. Therefore, the security considerations in section 6 of that document are relevant. In particular, it bears repeating here that the true impact of stateful filtering may be a reduction in security, and that IETF make no statement, expressed or implied, as to whether using the capabilities described in any of these documents ultimately improves security for any individual users or for the Internet community as a whole.

p.s. I also share all of Lorenzo's other specific concerns about this draft, as well as his broad general objections.

james woodyatt <<>>
Nest Labs, Communications Engineering