IETF Logo Mail Archive

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

Bob Hinden <bob.hinden@gmail.com> Thu, 27 October 2016 19:32 UTC

Return-Path: <bob.hinden@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 0A396129842 for <ipv6@ietfa.amsl.com>; Thu, 27 Oct 2016 12:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 SYdrEbEazYgq for <ipv6@ietfa.amsl.com>; Thu, 27 Oct 2016 12:32:53 -0700 (PDT)
Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 AF3A2129801 for <ipv6@ietf.org>; Thu, 27 Oct 2016 12:32:52 -0700 (PDT)
Received: by mail-yb0-x22c.google.com with SMTP id f97so27852907ybi.1 for <ipv6@ietf.org>; Thu, 27 Oct 2016 12:32:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc:message-id:references :to; bh=0YoHBl+qSNsQgTyqS+bBcy4xSrtsaSCkTHuqJuAN9Og=; b=aURbuwrsnt8ytihyt9wzG+UJMS7rX0cVqSTmJ3X62RRm9Py6q5BT2nDqkzDdzVKa9f 6GJuKMVgq8Z29xBxPBuaf+Bq8oj+qkFXUVjh1XK+XfPTd1JFuj25K1AE/2h3qoLjllKJ zxasaJdKOMcETkYAEG77CszoAEGW7bpo9jMrJCcPe4k/11vmIlQ/IEnexd89lHHL8Y20 iw1YsGOpRB0aKsE3+x7ECJTnV7i6/jO/wnHedJPiU/PihtA6cyo/93lxSiqnB7hXrMWn AiubckWvNDf6czwPaME8KmupkT0KbpuW1urBMK4JCjscHR11mu7qyvUX191BZi0ALdo0 9R0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=0YoHBl+qSNsQgTyqS+bBcy4xSrtsaSCkTHuqJuAN9Og=; b=L/3Sprsl3A0NK7n4RJ+c2oaqkIPZxA93h8exbvgTMfTVa3Jahcou5yq13MKNJR33Nu NFyRcqbM1khs0KzQIMaBPdRb06MHmNmWzoXBTv/thrYV9WJy5NctLJUlEdDCrJGxCyR5 0ZoiJGyEtNT7B4MhMO+0KuhfshaxS432eVHkNBOb3fZP23ODtqAaYC/THlMOtvHy5IRY Jnb0mx81iPYkZerO5aPwWe7VWU5V1eAd4Vzw+f+UujnE1D+H6wlsPA8eHuZWl7cWlugo wd0OD4IGzQpEUKs6448uELLsRax/rWT40VEj3l40awJhMDcv6X8v9wDS0cShl6TNenb5 qaSA==
X-Gm-Message-State: ABUngvcRsOIUwqRot2cCNNf5xT4h7HFy+d1r8uJNa0ivOd354CFRLRXcHMudmv/v+t4uwQ==
X-Received: by 10.36.29.17 with SMTP id 17mr288404itj.33.1477596771658; Thu, 27 Oct 2016 12:32:51 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id g127sm1530011itc.7.2016.10.27.12.32.50 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 27 Oct 2016 12:32:50 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E913D885-5840-4DE4-958A-61FD63244707"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Syntax glitch [Re: Next steps on Extension Header Insertion]
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <405364dc-9182-2eaf-235a-cc1b9873477c@gmail.com>
Date: Thu, 27 Oct 2016 12:32:48 -0700
Message-Id: <3D4B3D62-A0F3-4B85-94BC-FA1EBB19D5F6@gmail.com>
References: <B291E9E6-A803-423F-BFA5-87A74DCFB784@gmail.com> <405364dc-9182-2eaf-235a-cc1b9873477c@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9ZTquffckw3vhtjEEifJ-Cc58wI>
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 19:32:55 -0000

Brian,

> On Oct 27, 2016, at 12:20 PM, 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.

Yes, thanks.

Bob

v2.23.0 | Report a Bug | By Email