IETF Logo Mail Archive

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

otroan@employees.org Thu, 27 October 2016 20:55 UTC

Return-Path: <otroan@employees.org>
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 92695129523 for <ipv6@ietfa.amsl.com>; Thu, 27 Oct 2016 13:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.264
X-Spam-Level: **
X-Spam-Status: No, score=2.264 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=3.599, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
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 uDCwekl2fVQq for <ipv6@ietfa.amsl.com>; Thu, 27 Oct 2016 13:55:16 -0700 (PDT)
Received: from inbound03.kjsl.com (inbound03.kjsl.com [IPv6:2001:1868:a100:131::62]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF40312941A for <ipv6@ietf.org>; Thu, 27 Oct 2016 13:55:16 -0700 (PDT)
Received: from cowbell.employees.org ([65.50.211.142]) by ironport03.kjsl.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Oct 2016 20:55:16 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 581949CC4F; Thu, 27 Oct 2016 13:55:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=rutw78/RrkpuJ42D64qw8x9axPM=; b=Oa3iZXm7cieftssmKu C9e27vHjPyEEcRtpKLk2xePCVOyFFcTCIYZtmYgKS54e2RFN5MCMp2c1u/ryPfhr 2cHd8sNjg7JZymh9QuERuOfsSQaM2srOdPWehs6duH5gF+uAiUXHSbnzy5MpNp5J 7t3lNLfbD7ynAIlqOjoRkb21E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=DNKCgF6Iqn4mr6Kwe5N+aIoa3e4NexmNEbAE/ftaXbY5WdxERZa 5BNghgPXTUimiIiE2mFMNAQM0cG+cGE37QE33YVQEh77q8AV6eZdb3jA90gzWTXQ pHwRBQnLwKm2PWnaFEasZfINnEjJhbprYUm64LLOsNoD2AECMXS/7tGM=
Received: from h.hanazo.no (2.150.2.44.tmi.telenormobil.no [2.150.2.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 00E979CC0F; Thu, 27 Oct 2016 13:55:16 -0700 (PDT)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 829905555376; Thu, 27 Oct 2016 22:55:11 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\))
Subject: Re: Syntax glitch [Re: Next steps on Extension Header Insertion]
From: otroan@employees.org
In-Reply-To: <405364dc-9182-2eaf-235a-cc1b9873477c@gmail.com>
Date: Thu, 27 Oct 2016 22:55:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <507EE89A-B972-4A30-83CA-091C076E556D@employees.org>
References: <B291E9E6-A803-423F-BFA5-87A74DCFB784@gmail.com> <405364dc-9182-2eaf-235a-cc1b9873477c@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3251)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/psFlBll7DfcIE9pQGI-t6h0PPac>
Cc: 6man WG <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:55:17 -0000

> 
> 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.

Isn't that 3 examples. ;-)

Ole

v2.23.0 | Report a Bug | By Email