Re: [secdir] [v6ops] Secdir last call review of draft-ietf-v6ops-transition-ipv4aas-11

<mohamed.boucadair@orange.com> Fri, 14 December 2018 07:44 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B74E1310CC; Thu, 13 Dec 2018 23:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RGBPB-8Tak34; Thu, 13 Dec 2018 23:44:30 -0800 (PST)
Received: from orange.com (mta239.mail.business.static.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C95A21310C2; Thu, 13 Dec 2018 23:44:29 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 43GMy41f3wz8tbS; Fri, 14 Dec 2018 08:44:28 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.18]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 43GMy40jd2z5vNC; Fri, 14 Dec 2018 08:44:28 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM34.corporate.adroot.infra.ftgroup ([fe80::cba:56d0:a732:ef5a%19]) with mapi id 14.03.0415.000; Fri, 14 Dec 2018 08:44:27 +0100
From: <mohamed.boucadair@orange.com>
To: Christian Huitema <huitema@huitema.net>, JORDI PALET MARTINEZ <jordi.palet@consulintel.es>, "secdir@ietf.org" <secdir@ietf.org>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-v6ops-transition-ipv4aas.all@ietf.org" <draft-ietf-v6ops-transition-ipv4aas.all@ietf.org>
Thread-Topic: [v6ops] Secdir last call review of draft-ietf-v6ops-transition-ipv4aas-11
Thread-Index: AQHUk35gwIitBLjfoEqKymi2z0/HLKV92cbw
Date: Fri, 14 Dec 2018 07:44:26 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E059014@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <154473417654.32125.9104927217788947044@ietfa.amsl.com> <5BF30E2E-4B57-415E-8D8D-6C6815B604FF@consulintel.es> <2a90813d-bae7-1bd0-90fa-9fd1a8621b78@huitema.net>
In-Reply-To: <2a90813d-bae7-1bd0-90fa-9fd1a8621b78@huitema.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/A0xEHf9E_lDXpTy7SSf3EM5IdnM>
Subject: Re: [secdir] [v6ops] Secdir last call review of draft-ietf-v6ops-transition-ipv4aas-11
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2018 07:44:33 -0000

Christian,

As mentioned by Jordi, RFC8026 already describes the attack vector you mentioned. 

Wouldn't pointing to https://tools.ietf.org/html/rfc8415#section-22 be sufficient here? 

Cheers,
Med

> -----Message d'origine-----
> De : ietf [mailto:ietf-bounces@ietf.org] De la part de Christian Huitema
> Envoyé : vendredi 14 décembre 2018 08:26
> À : JORDI PALET MARTINEZ; secdir@ietf.org
> Cc : v6ops@ietf.org; ietf@ietf.org; draft-ietf-v6ops-transition-
> ipv4aas.all@ietf.org
> Objet : Re: [v6ops] Secdir last call review of draft-ietf-v6ops-transition-
> ipv4aas-11
> 
> 
> On 12/13/2018 2:09 PM, JORDI PALET MARTINEZ wrote:
> > Hi Christian,
> >
> > Thanks a lot for your review.
> >
> > Please see below in-line.
> >
> > I'm working in a new version according to the comments got from the ops
> review as well, so will be able to integrate yours very quickly.
> >
> > Regards,
> > Jordi
> >
> >
> >
> > -----Mensaje original-----
> > De: v6ops <v6ops-bounces@ietf.org> en nombre de Christian Huitema
> <huitema@huitema.net>
> > Fecha: jueves, 13 de diciembre de 2018, 21:50
> > Para: <secdir@ietf.org>
> > CC: <v6ops@ietf.org>rg>, <ietf@ietf.org>rg>, <draft-ietf-v6ops-transition-
> ipv4aas.all@ietf.org>
> > Asunto: [v6ops] Secdir last call review of draft-ietf-v6ops-transition-
> ipv4aas-11
> >
> >     Reviewer: Christian Huitema
> >     Review result: Has Issues
> >
> >     I have reviewed draft-ietf-v6ops-transition-ipv4aas-11 as part of the
> >     security directorate's ongoing effort to review all IETF documents
> >     being processed by the IESG.  These comments were written primarily for
> >     the benefit of the security area directors.  Document editors and WG
> chairs
> >     should treat these comments just like any other last call comments.
> >
> >     The summary of the review is "ready with issue".
> >
> >     The document describes solution for providing "IPv4 as a service", i.e.
> >     provision of IPv4 as a service over an IPv6 only network.
> >     It calls this support "transition as a service".
> >
> >     For various reasons, IETF working groups have standardized not just one
> but
> >     five different mechanisms for providing this transition: 464XLAT
> [RFC6877],
> >     Dual-Stack Lite [RFC6333], Lightweight 4over6 (lw4o6) [RFC7596],
> >     MAP-E [RFC7597], and MAP-T [RFC7599]. (I am sure that Monty Python
> could have
> >     produced a nice sketch about that.) The purpose of the draft is to
> >     state how home routers (a.k.a. customer premise equipment, CPE) should
> >     inform local devices about which of the mechanisms are available, which
> >     should be preferred, and what parameters should be used when deploying
> >     the chosen services. This is done using the DHCPv6 "S46" option
> >     specified in RFC 8026.
> >
> >     The draft also makes specific recommendation regarding the use of the
> UPnP and
> >     PCP services, by requiring specific error codes when a requested port
> mapping
> >     is not available through the specified transition technology.
> >
> >     The security section briefly points to the "Basic Requirements for IPv6
> >     Customer Edge Routers" specified in RFC 7084, and to the security
> >     section of each of the RFC describing the security technologies, and
> implicitly
> >     argues that there are no other security issues. I think that is
> insufficient.
> >
> >     The draft introduces a reliance on the DHCPv6 "S46" option for
> assessing the
> >     relative priority of different transition technologies. An attacker
> could spoof
> >     the DHCPv6 response, and direct client traffic to a different
> technology than
> >     selected by the service provider. This could be used, for example, to
> capture
> >     IPv4 traffic in an IPv6 network and send it to a route chosen by the
> attacker.
> >     The attack might also be used in a dual stack network that does not
> support
> >     any transition technology. I don't understand how this attack is
> mitigated.
> >
> > Not sure if you will suggest here that we should say something about the
> security considerations already mention in RFC8026. In general all those are
> generic DHCPv6 security considerations I think.
> 
> Basically, the devices should be programmed to ignore DHCPv6 if they
> have another more secure way of getting their configuration data. Plus,
> apply general defense against DHCPv6 hacks in the network, etc. I
> understand that your draft is meant to inform the building of CPEs, but
> its effect is generalization of an unsafe mechanism.
> 
> 
> >
> >     Nits:
> >
> >     The introduction uses the acronym WAN without spelling out "Wide Area
> Network".
> >     Also, WAN is used as substitute for local Internet Service Provider
> network. We could
> >     debate whether such networks are always "wide area", by opposition to
> say
> >     "metropolitan" or "regional". This is the same convention used in RFC
> 7084 that
> >     this document updates. It is arguably defined by reference, but
> spelling it out
> >     would be nice.
> >
> > Will do.
> >
> >
> >     The comparison with RFC7084 section includes a mangled sentence:
> >
> >        This document doesn't include support for 6rd ([RFC5969]), because
> as
> >        in an IPv6-in-IPv4 tunneling.
> >
> > Typo, sorry the correct sentence was:
> >        This document doesn't include support for 6rd ([RFC5969]), because
> is
> >        an IPv6-in-IPv4 tunneling.
> 
>        This document doesn't include support for 6rd ([RFC5969]), because it
> is
>        an IPv6-in-IPv4 tunneling.
> 
> >
> >     Please rephrase. Please also rephrase the next sentence, for similar
> reasons:
> >
> >        Regarding DS-LITE [RFC6333], this document includes slightly
> >        different requirements, because the PCP ([RFC6887]) support and the
> >        prioritization of the transition mechanisms, including dual-stack.
> >
> > I think it is much clear this way:
> >
> >        Regarding DS-LITE [RFC6333], this document includes slightly
> >        different requirements, related to the support of PCP ([RFC6887]),
> >        IGD-PCP IWF [RFC6970] and the prioritization of the transition
> >        mechanisms, including dual-stack.
> 
> OK.
> 
> 
> >
> >
> >     _______________________________________________
> >     v6ops mailing list
> >     v6ops@ietf.org
> >     https://www.ietf.org/mailman/listinfo/v6ops
> >
> >
> >
> >
> > **********************************************
> > IPv4 is over
> > Are you ready for the new Internet ?
> > http://www.theipv6company.com
> > The IPv6 Company
> >
> > This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the exclusive use of the
> individual(s) named above and further non-explicilty authorized disclosure,
> copying, distribution or use of the contents of this information, even if
> partially, including attached files, is strictly prohibited and will be
> considered a criminal offense. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, even if partially, including attached files, is strictly
> prohibited, will be considered a criminal offense, so you must reply to the
> original sender to inform about this communication and delete it.
> >
> >
> >