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

Stewart Bryant <stewart.bryant@gmail.com> Thu, 06 December 2018 14:35 UTC

Return-Path: <stewart.bryant@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 C4040126C7E; Thu, 6 Dec 2018 06:35:55 -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 5N22HE-ZS8aI; Thu, 6 Dec 2018 06:35:54 -0800 (PST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 E611D126BED; Thu, 6 Dec 2018 06:35:53 -0800 (PST)
Received: by mail-wr1-x436.google.com with SMTP id v13so719720wrw.5; Thu, 06 Dec 2018 06:35:53 -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-transfer-encoding:content-language; bh=aTUSt7jqwwtj1ew39Br/kcYtE8bOUM6ioxjIaRjNc90=; b=lamvJB1vBDBCfU7/7NIn2/8MPHHPcXICN95KATh3c753fivVyUgsXvRcca/qibhN+h 6V9jgxXo7kyiBj892LYG5zMBNX/gJRYq4FdrJ0xq1XVLYrIasA97jJKnoCJ294lY4lw8 K5FZGXu5lozifRZqw3bxdxI49MDisPj7YH7aMzmitwDmOYz3+XvwlxPyC7PAqr7kl44a ygQFbZy5dlAwS4sHSPh3LoF/aijQX+g27ZrIsznEonFjLGLPZWQnzQXuZoPHUbHDLeu2 UaJ3P6UwGJ6ASPlsvLwxIKQCqNq8WUOl1nhWc/JGAzMo9y9+tFT6fctRzU8r5aKGM5NT nvPA==
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-transfer-encoding :content-language; bh=aTUSt7jqwwtj1ew39Br/kcYtE8bOUM6ioxjIaRjNc90=; b=uA8ujHnEOgkYLqUMnaB10mCnQUzutYw9i9Hv9NpUu+5CwsvvyeyQ5+YRXzV6sTAuOT CSgedjXzYtHWAJ5rmvOl9jVxaqqRMmQ0uniUTI6csk9pDY2u0A9S20DBSya/q2vk+dkp 3afmskjYZVVnUHfz6B3JjpKhiD5t+vFfKlSkjAPlSPDmEyqOvcaq0BkHY+sBx6EBXnhs eGC3W3lj/TbIVYM8oWKWk/sP480/efqpikEK0wrwCjnK/yu6mDO3zayiBQ9N5Ayo9umc gaLLPvYSCvtnwWbgKoctwl44PSVdzsDcPDhhP4FG1gMmyDjtf+JoXUcceFQep0XV7qxB 3TOw==
X-Gm-Message-State: AA+aEWZavs0AnSxzK5cjcRYMHNiyxIhNFY3z38Gu+z1Xp49Pd/Haphjl s+nrwCjNgcJxY32zkDdqivSHsUAEI/4=
X-Google-Smtp-Source: AFSGD/V+aSbjJyUT8pgxJLfGCZyvAFmaujxkuxXM/tkdlRoXl20qj5kkvDuCHnHjDdAtyeJG2dXhbw==
X-Received: by 2002:adf:cc91:: with SMTP id p17mr26383105wrj.118.1544106952150; Thu, 06 Dec 2018 06:35:52 -0800 (PST)
Received: from [192.168.2.198] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id o9sm1364093wmh.3.2018.12.06.06.35.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 06 Dec 2018 06:35:51 -0800 (PST)
To: Joe Touch <touch@strayalpha.com>
Cc: Christopher Morrow <morrowc.lists@gmail.com>, tsv-art@ietf.org, opsec wg mailing list <opsec@ietf.org>, draft-ietf-opsec-ipv6-eh-filtering.all@ietf.org, ietf <ietf@ietf.org>
References: <977CA53D-7F72-4443-9DE2-F75F7A7C1569@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> <728C6048-896E-4B12-B80B-2091D7373D16@strayalpha.com> <8a676a4a-c76d-9fa5-ce79-534a14cf0511@gmail.com> <2386B45D-8AEE-4C95-BB00-A5A2ABF63F8A@strayalpha.com> <e5198c02-ebc6-ee3e-96cb-fd2831164f41@gmail.com> <02AD0268-BFB8-4CA2-8985-08AFE6013ABB@strayalpha.com> <6c071ce7-609b-fcf2-8977-9159afece9ec@gmail.com> <E008EA4B-74D3-4251-BFB8-B88F544B2A99@strayalpha.com> <260f1445-0690-691b-5aea-83b7a43bfdcb@gmail.com> <39A24B3F-1332-4A9B-AAF3-0E9B896F7906@strayalpha.co m> <CAL9jLaYPPiXECcLdCfe35tCwBaSvswObo7skO7pqN2t2TXskqw@mail.gmail.com> <52009CB5-FAA4-47D6-AC05-C16049758663@strayalpha.com> <16aaf3de-d020-1540-c2e5-5a570b838313@gmail.com> <3B4751F2-6C26-4F6E-826F-7E624AD76CE5@strayalpha.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <ba7f90d9-23de-24e5-3e20-d11469517355@gmail.com>
Date: Thu, 06 Dec 2018 14:35:50 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <3B4751F2-6C26-4F6E-826F-7E624AD76CE5@strayalpha.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsv-art/oO3OU9-nVt9uRZ2UpxpLGsmqsKg>
Subject: Re: [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: Thu, 06 Dec 2018 14:35:56 -0000

I disagree, although I image we will never agree on this.

The devices in an MPLS router are called label switching routers for a 
reason, and in the most common form of operation the LFIB is populated 
with data derived from the IGP and EGP.

There are many ways of thinking of MPLS labels, but one model is to 
consider them IP address equivalents, hence the use of the term 
Forwarding Equivalence Classes.

- Stewart


On 06/12/2018 14:04, Joe Touch wrote:
> Your right - it’s a broken L2.
>
> Only routers are supposed to decrement TTLs. Links and tunnels themselves aren’t.
>
> Joe
>
>> On Dec 6, 2018, at 5:16 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>>
>>
>>
>>> On 06/12/2018 05:22, Joe Touch wrote:
>>>
>>>> On Dec 5, 2018, at 9:01 PM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
>>>>
>>>> How is it, for example, different to put ipv6 packets into an MPLS path doing nothing along 'many' hops (except forwarding the packets along), and then once you pop out of the tunnel start processing the packet as you (joe) would want.
>>> The hopcount doesn’t get decremented by L2.
>>>
>>> Joe
>> MPLS is not L2.
>>
>> MPLS has two modes, one in which the TTL of the IP payload is decremented on ingress and the TTL across the MPLS path is ignored. In the other mode, the TTL of the IP packet minus one is copied into the MPLS label which is then decremented as the packet travels across the network at egress from the MPLS layer the TTL is copied back into the the IP packet.
>>
>> - Stewart