IETF Logo Mail Archive

Re: Syntax glitch [Re: Next steps on Extension Header Insertion]

Mark Smith <markzzzsmith@gmail.com> Thu, 27 October 2016 20:22 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 633A3129857 for <ipv6@ietfa.amsl.com>; Thu, 27 Oct 2016 13:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 ETuBkwRZr_cv for <ipv6@ietfa.amsl.com>; Thu, 27 Oct 2016 13:22:09 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (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 B99DC1296DB for <ipv6@ietf.org>; Thu, 27 Oct 2016 13:22:08 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id d65so10127503vkg.0 for <ipv6@ietf.org>; Thu, 27 Oct 2016 13:22:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NsJIESq37QNvrSpgIqlWTYTIjM6ZrkB0GLkdmff5x9I=; b=qu/URSojlGuqiNg9a5uuqqlzzfO6gxwTV8b/y0cWy0ScOF/6XadKopzMvX8JC20PW/ PljAbAyYZP4ekoxwes7xpVHVgG1Y9kElOspHhMX3wbIXGUw3mTrQnjXj14E7qqr1iZRK OwgYsjFo99gmk+BzH6t411Z2bfT+YiInN72dcgxWiE72ERuA8B5vKNUcqkp8IYZRXRDZ Z2nLpaZlN++KvDObiACURdlf40GCUA9WrXO/z5l+c4qbPhlGvqu24Rme1wi1VY4SsyVl xHWiqls+dJTubCCwqr8VjEgZVA/IJgX1HPZxlKH3+4VYcPmHJDQqRdlXciSL8ov/xl+0 Pvkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NsJIESq37QNvrSpgIqlWTYTIjM6ZrkB0GLkdmff5x9I=; b=gsx4R+ahZ3uiUk252UMkactHXjHDe+1I61PzBpGQWHW7foAwvWlbgRYjecYpf3a4mn Di8qCAefR2CEV7n9kuQ4xrYboo4drm4+b1gygMnZrMCiZDCD9OmXe3vbhSELaTbDKWwv ZqmQN9hSz4zqZ327ppE+8H7vo14ooRbrTojtPl9CFPDmxRvhRGQIwX5aQbNDzNqEdvbR wEknRmgANScdv0IS00FKlJR0XUpM1iEqgtpjtrEbZdcZo5LA0TYHzKN1hrMJHzwPwJnf V1vD/3w+gZ3dgn/xH9hTwCMvMm5kjbxYhs2+8PvcsCuvoSRbGpENiJps3cSZlFVbaO0G qMEg==
X-Gm-Message-State: ABUngve1jZwNwt+vwlBG5jkVI7f2ELr23denQUZ9mY+Kz7QN/8qEW1+8G3AE65m5Om1kPhCnvvUMFVYyEV6Vgw==
X-Received: by 10.31.12.17 with SMTP id 17mr9047748vkm.108.1477599727811; Thu, 27 Oct 2016 13:22:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.16.79 with HTTP; Thu, 27 Oct 2016 13:21:37 -0700 (PDT)
In-Reply-To: <405364dc-9182-2eaf-235a-cc1b9873477c@gmail.com>
References: <B291E9E6-A803-423F-BFA5-87A74DCFB784@gmail.com> <405364dc-9182-2eaf-235a-cc1b9873477c@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 28 Oct 2016 07:21:37 +1100
Message-ID: <CAO42Z2yEZ3nspTcLQ3rBhN7i-wypzE-fDF3h8VN0oVmUawpViQ@mail.gmail.com>
Subject: Re: Syntax glitch [Re: Next steps on Extension Header Insertion]
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mGAwALUYeKpsdmOMIn1NWsb3OKU>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
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: Thu, 27 Oct 2016 20:22:10 -0000

On 28 October 2016 at 06:20, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> This is just about a syntax issue and will not affect my response to the survey:
>
>>   Two examples include breaking
>>   the integrity checks provided by the Authentication Header Integrity
>>   [RFC4302], and breaking Path MTU Discovery and can
>>   result in ICMP error messages being sent to the source of the packet
>>   that did not insert the header.
>
> That "and can" doesn't parse for me. I *think* you mean:
>
>   Two examples include breaking
>   the integrity checks provided by the Authentication Header Integrity
>   [RFC4302], and breaking Path MTU Discovery, which can
>   result in ICMP error messages being sent to the source of the packet
>   that did not insert the header.
>

In this text I'd also like to see a mention of operational implications e.g.,

"It will also make troubleshooting harder, as construction of the
entire packet cannot now be reliably attributed to the host assigned
the source address in the packet."

Regards,
Mark.


> Regards
>    Brian
>
> --------------------------------------------------------------------
> 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