Re: Comments on raft-fz-6man-ipv6-alt-mark-01
Ole Troan <otroan@employees.org> Fri, 01 November 2019 18:15 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 CA943120F20 for <ipv6@ietfa.amsl.com>; Fri, 1 Nov 2019 11:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 8AQgrwaeziWl for <ipv6@ietfa.amsl.com>; Fri, 1 Nov 2019 11:15:52 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 033D8120ECB for <ipv6@ietf.org>; Fri, 1 Nov 2019 11:15:51 -0700 (PDT)
Received: from [192.168.10.190] (246.51-175-81.customer.lyse.net [51.175.81.246]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id D657E4E11BC5; Fri, 1 Nov 2019 18:15:49 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Subject: Re: Comments on raft-fz-6man-ipv6-alt-mark-01
Date: Fri, 01 Nov 2019 19:15:47 +0100
Message-Id: <FE11E326-43C2-409C-864E-62AD8B893050@employees.org>
References: <CALx6S35298CHBJsSs3LGY_0Pp2_eW-dQFCbQ6SLQneoQ5U=_yQ@mail.gmail.com>
Cc: 6man <ipv6@ietf.org>
In-Reply-To: <CALx6S35298CHBJsSs3LGY_0Pp2_eW-dQFCbQ6SLQneoQ5U=_yQ@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
X-Mailer: iPhone Mail (17B5084a)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/JFU1AvCKxevQyK9VusI4jj41NcU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 01 Nov 2019 18:15:54 -0000
> On 1 Nov 2019, at 18:57, Tom Herbert <tom@herbertland.com> wrote: > > On Fri, Nov 1, 2019 at 10:46 AM Ole Troan <otroan@employees.org> wrote: >> >> DestOpt => measurement only by node in DA >> HBH => every router on the path with feature enabled >> SRH TLV => every node along the SR path >> DestOpt + SRH => every node along the SR path >> > Ole, > > So the last two have identical effects, hence we've introduced the > complexity or redundant protocol mechanisms. Yes, that should guide us in making choices here. Ole > > Tom > >> Cheers >> Ole >> >>>> On 1 Nov 2019, at 18:33, Tom Herbert <tom@herbertland.com> wrote: >>> >>> Hello, >>> >>>> From the draft: "Regarding Hop-By-Hop Options Header, if we consider >>> its real deployment, it is sometimes dropped by legacy devices and not >>> so used by intermediate nodes. Destination Options Header is >>> preferred." >>> >>> I don't think this is helpful guidance. First of all, it's not just >>> Hop-by-Hop options that can be dropped, it's pretty much packets with >>> any extension heades or atypical protocols that might be dropped by >>> legacy devices-- including packets with Destination Options or Routing >>> Headers. Neither does it make sense that Destination Options Header is >>> preferred, as correctly stated in the previous paragraph DO and HBH >>> address difference use cases (i.e. DO is end to end, and HBH is per >>> hop). Saying that DO is preferred is equivalent to saying that >>> end-to-end performance measurements are preferred which I doubt is the >>> intent. IMO, this whole paragraph could be removed without loss of >>> content. >>> >>> "SRH TLV can also be a good choice from this point of view. The >>> intermediated nodes that are not in the SID list can consider the SRH >>> as a green field, they cannot support and bypass or support and dig >>> into the SRH TLV." >>> >>> I disagree with the conclusion that SRH TLV is a good choice. The >>> implicit assumption in this paragraph is that somehow SRH EH is less >>> likely to be dropped by intermediate nodes than other EH like DO and >>> HBH. I don't think there's any data to support that. Additionally, >>> it's not clear what use case an SRH TLV addresses that can't already >>> be addressed by Destination or HBH options. >>> >>> Tom >>> >>> -------------------------------------------------------------------- >>> IETF IPv6 working group mailing list >>> ipv6@ietf.org >>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 >>> --------------------------------------------------------------------
- Comments on raft-fz-6man-ipv6-alt-mark-01 Tom Herbert
- Re: Comments on raft-fz-6man-ipv6-alt-mark-01 Ole Troan
- Re: Comments on raft-fz-6man-ipv6-alt-mark-01 Tom Herbert
- Re: Comments on raft-fz-6man-ipv6-alt-mark-01 Ole Troan
- RE: Comments on raft-fz-6man-ipv6-alt-mark-01 Tianran Zhou
- Re: Comments on raft-fz-6man-ipv6-alt-mark-01 Ole Troan
- RE: Comments on raft-fz-6man-ipv6-alt-mark-01 Tianran Zhou
- Re: Comments on raft-fz-6man-ipv6-alt-mark-01 Ole Troan
- Re: Comments on raft-fz-6man-ipv6-alt-mark-01 Mark Smith
- RE: Comments on raft-fz-6man-ipv6-alt-mark-01 Giuseppe Fioccola
- RE: Comments on raft-fz-6man-ipv6-alt-mark-01 Tianran Zhou