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

<> Fri, 30 January 2015 15:25 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0B94C1A9050 for <>; Fri, 30 Jan 2015 07:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=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 aClaKf33H1Pl for <>; Fri, 30 Jan 2015 07:25:06 -0800 (PST)
Received: from ( []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EEC961A904D for <>; Fri, 30 Jan 2015 07:25:05 -0800 (PST)
Received: from (unknown [xx.xx.xx.200]) by (ESMTP service) with ESMTP id 278E6C090D; Fri, 30 Jan 2015 16:25:04 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown []) by (ESMTP service) with ESMTP id 0123D158059; Fri, 30 Jan 2015 16:25:04 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([]) by OPEXCLILH04.corporate.adroot.infra.ftgroup ([]) with mapi id 14.03.0224.002; Fri, 30 Jan 2015 16:25:03 +0100
From: <>
To: "STARK, BARBARA H" <>, James Woodyatt <>
Thread-Topic: [v6ops] draft-ietf-v6ops-mobile-device-profile last call
Date: Fri, 30 Jan 2015 15:25:02 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933004902B03@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <> <> <> <787AE7BB302AE849A7480A190F8B933004902567@OPEXCLILM23.corporate.adroot.infra.ftgroup> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
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 15:25:08 -0000

Hi Barbara,

Thank you for the comment.

I'm planning to put back that text if there is no objection from the WG. 

As per RFC7084, we didn't included it because it included some IPv4 continuity service features that are not valid for the mobile context. The document already mentions the following: 

                "Note, even if RFC7084 obsoletes [RFC6204], this profile
                does not require RFC7084 because IPv4 service continuity
                techniques used in mobile networks are not the same as
                in fixed networks."

Thank you.


-----Message d'origine-----
Envoyé : vendredi 30 janvier 2015 16:18
À : BOUCADAIR Mohamed IMT/OLN; James Woodyatt
Cc : IPv6 Ops WG
Objet : RE: [v6ops] draft-ietf-v6ops-mobile-device-profile last call

Proposed text from James:
> 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]. 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.

FYI. RFC 6204 (in James’ proposed text above) was obsoleted by RFC 7084. If this text is to be included, that should be changed.

I would also like to see some of the removed text (referring to discussion around some of Lorenzo's comments) put back.