[Tsv-art] HbH flags [Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06]

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 05 December 2018 20:04 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: tsv-art@ietfa.amsl.com
Delivered-To: tsv-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5518B130ED7; Wed, 5 Dec 2018 12:04:57 -0800 (PST)
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 5mq11NGaMm6Z; Wed, 5 Dec 2018 12:04:54 -0800 (PST)
Received: from mail-pl1-x636.google.com (mail-pl1-x636.google.com [IPv6:2607:f8b0:4864:20::636]) (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 9E1BF130DF1; Wed, 5 Dec 2018 12:04:54 -0800 (PST)
Received: by mail-pl1-x636.google.com with SMTP id u6so10562926plm.8; Wed, 05 Dec 2018 12:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=fgODihu3c8W5sSIORnhLirCOqbSuUM5I5/SIXNaZ1ZA=; b=tlBy6YdRkOS4dVn7H0dcxtz5zd9tPnHSp/f5P9r/nS/HwiRyXI/EnfBIhwTAjZCLen 49rlxgQ5bS9S79FpjE24AcZ7E/s/tcFH6uVbXm5GxHZymGTJWUzk+ukzxGg1DN7LfjIu JFmI81xEELwwLe9aPngLWwzDel7hJoPHhcoC9CM2Uu/tjxcgtUcMMmLpQQYJe70UluNf Wof+OKxMvef8+RFaq39KDJTiWw0pztvCkRAmeGUhz88WjGs09WEZlJepkp9p10HDHkA1 zM5lde9GK5g+yEXOloFL7rwuQjLuD8TOzu9oJfsUb95sxQ3gF2d7nJ9HPjIdPg/+rCpn 1pbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fgODihu3c8W5sSIORnhLirCOqbSuUM5I5/SIXNaZ1ZA=; b=fa2Xowwy0SsBJ5Ev442nbMfNLfwmTdjDKjxhtFLQqbf/FGxrQTSBa6J8dUG0RWKs59 LKnlTzrTUjy7O+2gLl34TGgfR/zUOMUAuufJsT/3lCgJknqwZziBiKMIs7YzbuTBFg/U 7wOV4SfatqD5WpirNvPD3Gnm9EgVz35BUcReSYd4xI0JHZRPSrtQo2ajymZbkEbGvx4L 8PNbLFfeeS9UvNI+wNjalNBo23Njmbbi3IRJD/H1QrF7o4lhv4qFhIIvU1Np+dKyVmNt fPDOBcDUkEF91DAUFrct9dY0Z0xXypL6c4jyebUd5G/BEhNKDQeVJsrsMqRm0Fq3GPJc FTJg==
X-Gm-Message-State: AA+aEWZBqxbdA0ZozrKTTyE9xm+iAnyt5rzCVpIlx5n6OJRIzkcm3KIU nwEaaWl9trzhATkpOq0wJc/nBtI+3b8=
X-Google-Smtp-Source: AFSGD/V5B5hnnv7C5DUdJYFFTcfFNq0qCYVUC3EmzMZpas6hNCvdk9D+azVWUbwRPvTMipFC7b7Kwg==
X-Received: by 2002:a17:902:6185:: with SMTP id u5mr25360244plj.194.1544040293827; Wed, 05 Dec 2018 12:04:53 -0800 (PST)
Received: from [192.168.178.30] ([118.148.76.40]) by smtp.gmail.com with ESMTPSA id p6sm27411558pfn.53.2018.12.05.12.04.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 05 Dec 2018 12:04:53 -0800 (PST)
To: Joe Touch <touch@strayalpha.com>
Cc: Christopher Morrow <morrowc.lists@gmail.com>, ietf <ietf@ietf.org>, draft-ietf-opsec-ipv6-eh-filtering.all@ietf.org, opsec wg mailing list <opsec@ietf.org>, tsv-art@ietf.org
References: <977CA53D-7F72-4443-9DE2-F75F7A7C1569@strayalpha.com> <6bd1ec94-f420-1f4c-9254-941814704dbb@gmail.com> <6be84ccf-9a72-2694-e19d-fa19043a0cb1@huitema.net> <4C249487-BD58-41BB-B8B6-081323E29F6C@strayalpha.com> <20181126075746.GO72840@Space.Net> <6C50775C-EB67-4236-93B8-DF0259E04167@strayalpha.com> <20181126175336.GW72840@Space.Net> <c959d8cb6f6a04a8da8318cfa89da341@strayalpha.com> <2425355d-e7cc-69dd-5b5d-78966056fea7@foobar.org> <C4D47788-0F3D-4512-A4E3-11F3E6EC230B@strayalpha.com> <8d3d3b05-ecc3-ad54-cb86-ffe6dc4b4f16@gmail.com> <C929A8B9-D65C-4EF7-9707-2238AE389BE3@strayalpha.com> <CAL9jLaY4h75KK4Bh-kZC6-5fJupaNdUfm1gK2Dg99jBntMCEyQ@mail.gmail.com> <C47149DC-CAF2-449F-8E18-A0572BBF4746@strayalpha.com> <CAL9jLaYfysKm7qrG=+jq7zV=5ODnSX-tAhBAiTU7SzYF-YmcGw@mail.gma il.com> <728C6048-896E-4B12-B80B-2091D7373D16@strayalpha.com> <8a676a4a-c76d-9fa5-ce79-534a14cf0511@gmail.com> <2386B45D-8AEE-4C95-BB00-A5A2ABF63F8A@strayalpha.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e5198c02-ebc6-ee3e-96cb-fd2831164f41@gmail.com>
Date: Thu, 06 Dec 2018 09:04:48 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2
MIME-Version: 1.0
In-Reply-To: <2386B45D-8AEE-4C95-BB00-A5A2ABF63F8A@strayalpha.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/h45O3YgUliOdsicAjZ4ACDrmzUY>
Subject: [Tsv-art] HbH flags [Tsvart last call review of draft-ietf-opsec-ipv6-eh-filtering-06]
X-BeenThere: tsv-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Review Team <tsv-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-art/>
List-Post: <mailto:tsv-art@ietf.org>
List-Help: <mailto:tsv-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-art>, <mailto:tsv-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2018 20:04:58 -0000

On 2018-12-06 01:16, Joe Touch wrote:
> 
> 
> On Dec 4, 2018, at 8:46 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
>>> Nobody deprecated the flags that require HBH options to be processed or dropped if not supported. 
>>
>> Intentionally. If a forwarding node is transparent to HbH options,
>> it is not looking at those flags. If it is looking at HbH options,
>> it will obey those flags. Why is that a problem?
> 
> What exactly does ‘transparent to HbH options mean’ if not ‘not supported’?

It means a forwarding node that uses the exception added by RFC7045 and simply
doesn't even look for an HbH header. The flag bits are invisible and irrelevant
to such a node. The flag bits apply as defined for a forwarding node that *does*
process HbH options, so they certainly should not be deprecated.

   Brian

> 
> In that case, the flags have exactly no meaning anywhere. But they’re not deprecated.
> 
> That makes no sense at all.
> 
> Joe
> .
>