Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard

Mark Smith <markzzzsmith@gmail.com> Mon, 13 February 2017 01:51 UTC

Return-Path: <markzzzsmith@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 588D1129583; Sun, 12 Feb 2017 17:51:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level:
X-Spam-Status: No, score=-0.498 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 6BXGgOd4gYvk; Sun, 12 Feb 2017 17:51:35 -0800 (PST)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (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 C1258129587; Sun, 12 Feb 2017 17:51:34 -0800 (PST)
Received: by mail-ua0-x229.google.com with SMTP id 96so57547011uaq.3; Sun, 12 Feb 2017 17:51:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1kEThVIEMXC3EOZfk6+Inq3u+C5Sqx9zcGmtEhtCJ4o=; b=pksOgDFuKmVCCuENTNZxXn4CGsDQBl+VkiU4ZRqtuzhhhqiSO5k8AOHzOsqpV7hxb/ g28BBZJBhLjuQud/c5DkCAP4JuAhMIfmA5lupwwSf3rJ8GUUcTblZcuWaoysy1s2gfxX RSL3JofzRForx368CNL4yjfaNCSpzJnHTAdwRXO8BEdu9qTkoCkQa+aICD3qEqs7Qg2Q WY4aAh/CJTE8NbXsYtRHs3Gy9v+CqAr0U5hDrERD0kaNFjcPSQmHMwpMODeAeWUHM7Cq 7KccwHExkjiCYMwRAxEZO5iONpQ130oL+gCVjlohUPMbU6OoI5tx7cD6R5TOE0+2jrib dA8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1kEThVIEMXC3EOZfk6+Inq3u+C5Sqx9zcGmtEhtCJ4o=; b=SoZKZfJbY4oDy6Lkfduajv+4QEmMqdZU93SXYeNRzrHXVUmJUq1ihoH8PX1P1UdBXX 3q4dlvZpowcIGhvc+TEpSyhkyzdXfLsqya8wRU1qFe6eZNzJWg6O+DkodpXJz+drkwv1 zbeOfzD2WJeL2OkJkk0p9Pnr6e3H9NpKSQ7Y9V/woCECYI02er4K8WLpFNry5X0Z8rR7 3XadH5etEf1vJ+lw4hCY0p+eXb9bhLbhO2UiUlKUNQvHvo+qCGLiQ9dMk8PMFjfkCW5u zTBF/82CabwWcQxJX5l1riU7niUHpVFBgIT4iKrFxhFnEVjqAo9qt/3hR4HtlL7PBPPC MH/g==
X-Gm-Message-State: AMke39kFr+kgXFhmRmsaoI6oSrCu9vSf6Nf5pVzwc/T+U9ijP/Rul8byzByEDYEDfqJS+jXo1jyrISjh+Xs/rw==
X-Received: by 10.159.40.201 with SMTP id d67mr10552812uad.98.1486950693836; Sun, 12 Feb 2017 17:51:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.33.173 with HTTP; Sun, 12 Feb 2017 17:51:33 -0800 (PST)
Received: by 10.159.33.173 with HTTP; Sun, 12 Feb 2017 17:51:33 -0800 (PST)
In-Reply-To: <cd1ef13e-7d3c-0dbf-a4d9-61442f663d3e@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com> <5CE4B4BF-75A9-4DC9-80AE-220281B046E9@cisco.com> <A823FD1C-4ED8-4788-81F0-0F672F1FA364@cable.comcast.com> <cd1ef13e-7d3c-0dbf-a4d9-61442f663d3e@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 13 Feb 2017 12:51:33 +1100
Message-ID: <CAO42Z2zbnAZ5KUWmWouB4T0Cpg9WEk4aEKNi50X+Xow8L22LTg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c123f16e79e3505485faf79
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/UQK_1aS_lGfxXisxJ_WYjwn1OSw>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "Leddy, John" <John_Leddy@comcast.com>, Pete Resnick <presnick@qti.qualcomm.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Suresh Krishnan <suresh.krishnan@gmail.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 13 Feb 2017 01:51:40 -0000

On 13 Feb. 2017 11:40 am, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

John,

On 13/02/2017 12:05, Leddy, John wrote:
> I’m trying to understand how a ban of this functionality would work.  Is
it targeted at vendor products, precluding them from implementing the
functionality?

It's targetted at interoperability across the Internet. We can never stop
people doing whatever they please inside a private domain, obviously.
As always, there are no protocol police.

> If there is a technical problem that can be solved by using EH insertion
within a domain where there are no harmful side effects, it should be able
to be used.
> In a software networking world where functionality is being deployed that
is not from traditional network vendors; solutions that solve problems
efficiently will get deployed.

We had a lot of this conversation in a slightly different form prior to
RFC 6437. It proved impossible to specify "local domain" rules that could
reach consensus. I think we'd have the same problem trying to write rules
for header insertion/deletion within a domain. But in any case, that isn't
the target for RFC2460bis: the target is the Internet.


We also know that this statement from RFC1918 hasn't been 100% effective:



   Because private addresses have no global meaning, routing information
   about private networks shall not be propagated on inter-enterprise
   links, and packets with private source or destination addresses
   should not be forwarded across such links.


and we still don't have enough deployment of BCP38 which would also help
enforce that.

If it is possible to plug a device into the Internet I think it is better
to assume somebody probably will (and you won't be there to stop them) and
design to that assumption.

(All the recent "IoT" botnets and corresponding attacks are a result of
assuming those devices will only be connected to Private Internets, and
therefore they don't have to be individually "Internet proof" (conceptually
similar to a "water proof" watch).)

Regards,
Mark.



    Brian

>
> John Leddy
>
> From: ietf <ietf-bounces@ietf.org> on behalf of "Eric Vyncke (evyncke)" <
evyncke@cisco.com>
> Date: Sunday, February 12, 2017 at 3:56 PM
> To: Suresh Krishnan <suresh.krishnan@gmail.com>om>, 神明達哉 <jinmei@wide.ad.jp>
> Cc: "6man@ietf.org" <6man@ietf.org>rg>, IETF Discussion list <ietf@ietf.org>rg>,
Pete Resnick <presnick@qti.qualcomm.com>om>, "draft-ietf-6man-rfc2460bis@
tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>rg>, "
6man-chairs@ietf.org" <6man-chairs@ietf.org>
> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet
Protocol, Version 6 (IPv6) Specification) to Internet Standard
>
> Suresh, Jinmei and Fernando,
>
> I fully agree with you Suresh, the goal of an IETF last call is to get
NEW discussion and to re-do the lengthy discussions we had on 6MAN WG.
>
> -éric
>
> From: ipv6 <ipv6-bounces@ietf.org> on behalf of Suresh Krishnan <
suresh.krishnan@gmail.com>
> Date: Saturday 11 February 2017 at 07:11
> To: 神明達哉 <jinmei@wide.ad.jp>
> Cc: "6man@ietf.org" <6man@ietf.org>rg>, IETF Discussion list <ietf@ietf.org>rg>,
Pete Resnick <presnick@qti.qualcomm.com>om>, Fernando Gont <
fgont@si6networks.com>gt;, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <
draft-ietf-6man-rfc2460bis@tools.ietf.org>gt;, "6man-chairs@ietf.org" <
6man-chairs@ietf.org>
> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet
Protocol, Version 6 (IPv6) Specification) to Internet Standard
>
> Hi Jinmei,
>
> On Feb 10, 2017 1:23 PM, "神明達哉" <jinmei@wide.ad.jp<mailto:jinm
ei@wide.ad.jp>> wrote:
> At Thu, 9 Feb 2017 18:30:11 -0300,
> Fernando Gont <fgont@si6networks.com<mailto:fgont@si6networks.com>> wrote:
>
> While I largely agree with Fernando on everything he said, I have to
> admit most of the points are just repeated from the 6man discussion,
> and won't get us anywhere new by discussing these again at this point.
> I guess the only new input for the IETF last call is this:
>
>> 2) However, some folks came up with proposals to insert EH, on the basis
>> that "RFC2460 does not explicitly ban EH insertion". If there's people
>> arguing that, we clearly need to make this clear in the spec.
>>
>> 3) There was a consensus call, yes. When the call was made on the
>> mailing-list, the vast majority of supporters of "let's keep the
>> ambiguity" were folks from the same company as "2)". I have no idea if
>> this changes (or not) "consensus"... but this is clearly an important
>> datapoint.
> Although I don't want to point a finger at particular people or
> organizations without an evidence, I guess not a small number of 6man
> participants (not only those who explicitly spoke up here) suspected
> that the decision process was biased with the influence of a large and
> powerful organization and the process and resulting "consensus" was
> not really a fair one.  And I'm not an exception to it - in fact, it
> was so unbelievable to me that we can't clarify an ambiguity even when
> we were also open for future extensions, that I couldn't think of
> other reasons than a company agenda.
>
> Of course, it's quite possible that it was just a coincidence that
> many people with the same organization genuinely thought we should
> leave it ambiguous while many others strongly thought we should
> clarify it but few (if not no) people from that organization supported
> the clarification.  But I don't think we can prove it either way.
>
> But as Fernando said, I believe this point (and that several, and
> arguably more, participants suspected it) should be included in making
> the decision at the IESG and at the IETF last call.  And, whatever the
> decision, it would be more productive to move on after that and use
> our time for some other things.
>
> I am guessing that the people who spoke up during the WG process to not
put in an outright prohibition would make their case along with their
arguments here as well. We are only a week into a four week long last call.
>
> Thanks
> Suresh
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------