IETF Logo Mail Archive

Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt

Alejandro Acosta <alejandroacostaalamo@gmail.com> Fri, 19 October 2018 12:45 UTC

Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258BC127AC2 for <ipv6@ietfa.amsl.com>; Fri, 19 Oct 2018 05:45:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 klXmYKu0KW4m for <ipv6@ietfa.amsl.com>; Fri, 19 Oct 2018 05:45:56 -0700 (PDT)
Received: from mail-vs1-xe33.google.com (mail-vs1-xe33.google.com [IPv6:2607:f8b0:4864:20::e33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95BF5126CB6 for <ipv6@ietf.org>; Fri, 19 Oct 2018 05:45:56 -0700 (PDT)
Received: by mail-vs1-xe33.google.com with SMTP id r83so25165489vsc.4 for <ipv6@ietf.org>; Fri, 19 Oct 2018 05:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=feRbfFAUMYBhmWnSC4lS/QMP9K5PYZchmcN1Rzy+600=; b=dilDLAej3oEYFo2rXuOJzdB/9DDXqf4/stIbKQVWcDp0ppi+Z9fUpfFUO3B++MgRnQ WE//8tT28RdJHJevC07EA+8wulg4u4iomfYK4zr+5hcZPXRUmYpmDYwMQtqq8tuCqEeF BSGMoyZpyh9ryZra+71UfZ3KIsS3seowTm9s7re41kdhbcPp1zyNgo6yAUvjaTvYhVSb NDjkC4vbIqgrCT0vwpK7TQ6W0xVyw6byYrq2zozz/Tx4/CsG+MpSPgl4ksYm8PZkYKMw iljqsbIRzJVNy+yIhEuxxaNN2JPB9lrBlZl2lNIbNNq0PN8CEfxCBkqkJZMSoM0mq2m9 n8Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=feRbfFAUMYBhmWnSC4lS/QMP9K5PYZchmcN1Rzy+600=; b=J/5I+cqW+h7neXzkb0VaVsO/RuCeiMqsU9nDQf02GF30YxEsaeq9lrH4icvjCO6P4r oklLMqAfbxkP4591d8NVQ9W8w0k1wVivhGR8GUgHEUqiE+oN/s44bBgZL0nghx4G7hSo C03L9ZIlQW7CJ7z2/23e3lLgZYag+62wiLJZ8OHgvVlQZLYoo5CrhdrvxuPZHwGV+rUr Fw9w1fT6hLDxyBdiAv1J4MOVcQnO/9qJyVT1pjW2RSVnoRNwM//l8CCo/8Z/wFFAbOhC DQKwXqPbKr40O5N4w4P3FcI79eRk4IXpPDiogtvarIbS/vY9G6s/QhUPiHwXu26LTsZx kR/w==
X-Gm-Message-State: ABuFfogQ4WoEwoaGTqZwA5NSyUDqF6kZVEbYmp6aHTXdsKEi9wXA74Dg Va5GWs7IzfwA3iQvSzMxDVbqZdKS
X-Google-Smtp-Source: ACcGV62k35hcGuGsSJrEA1YPJNUGwBdgAhz9tI3usE+WY1pBf6kcAwX+XVDDydY3UMBgeqaoSQc3JA==
X-Received: by 2002:a67:344:: with SMTP id 65-v6mr604195vsd.80.1539953155266; Fri, 19 Oct 2018 05:45:55 -0700 (PDT)
Received: from MacBook-Pro.local ([186.188.61.209]) by smtp.gmail.com with ESMTPSA id a35sm3805488uaa.1.2018.10.19.05.45.54 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Oct 2018 05:45:54 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-ipv6only-flag-03.txt
To: ipv6@ietf.org
References: <153973137181.9473.10666616544238076833@ietfa.amsl.com> <092346e1-6350-e54e-e711-9c5ee6dc4e6b@gmail.com> <CAFU7BASO_ByzbanhLKnWV280O_fASd-8W+ujpj3sN6d2-whw2w@mail.gmail.com> <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com>
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Message-ID: <58716eef-6d67-9e91-a714-acec88b9e3eb@gmail.com>
Date: Fri, 19 Oct 2018 08:46:01 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CACWOCC-u7aAPwAOcixYvt2On=-o_8X25GhqdXTfA+tWRC1o2XA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------710380A6A303886BE661AF13"
Content-Language: es-ES
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gmPuq2NEZzWIIQepFwlkxScHcng>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2018 12:45:59 -0000

Hello,

  +1 to Job's comment.


Alejandro,



El 19/10/18 a las 08:35, Job Snijders escribió:
> I think it would be good to have some running code before advancing
> this to IESG review and RFC publication. I don’t mean someone being
> able to send the flag in a RA, but an operating system reacting to
> receiving a RA with the flag set.
>
> Operating system implementers will be able to provide valuable
> feedback to the working group on how to mitigate risk for some of the
> suspected attack vectors - and it’ll be educational to see how this
> works in practice. I think running code will improve this specification.
>
> Kind regards,
>
> Job
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email