Re: [spring] Question about SRv6 Insert function

Suresh Krishnan <> Wed, 04 September 2019 02:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3EF3A12007C; Tue, 3 Sep 2019 19:23:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bAVMJllBKUig; Tue, 3 Sep 2019 19:23:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::b31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9DEDF120033; Tue, 3 Sep 2019 19:23:46 -0700 (PDT)
Received: by with SMTP id t15so6755643ybg.7; Tue, 03 Sep 2019 19:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hOOm+QKcD+WYTqgs6vKpHpaTZ5FuG+2jyYHwXtDcXG0=; b=Si5FHAGxGwGsR0CwUTPXhhUwlfehlkQLvfxU0sbw7ujnIFm1aKAc3mJHZOm0+qXWdF lwGUUWuU+yueXtJK6EoWKY5gG0SXYP3sRVVUY+/uRDyL1Wrd5PrI3dlt4mNDm8EiYLtx 68faDK/6KGIBx3eAwY5mtn+N3isCmRHfRSuiNKGfjVZCYl7iOvcN+RmNDXj1WXsHxV9E DQeJIxvhLK9wQNx0MfD1Y0fArJ9S3Mi/mvhyw8g39C6PAIpbz4xoptThHZ6TrUkBD/qK Zg6J2czBQlI+pqcBCyi8KPqwHe5ixFdqR+RYnkuLcGQxlCQaE7atL82XpU6evRbFWnVc XUKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=hOOm+QKcD+WYTqgs6vKpHpaTZ5FuG+2jyYHwXtDcXG0=; b=CUiV0L74gkofyxynv2fSIDz9yRnZyU0X7DjVigdD5LnQNr4shihBoAdKZkUrTPKJxc 5McOgs8H8m/0V5dX/cRh2so7E3wh3HlWjn/QCzLNJS7TwN3BP2LAXhegWHs6Tbwmgn/w v7PfhH4f7Uh18k7/Sj850e4QrYXXdxLXCgoA21Jhoq8texUXXB5P/tM3xY/FWumzx4Nv 0DO1I3gCAHxf7s57pWdb53ET/pxyiSdnyf3Yk14qMS6+IoXvymqmkQYT1kp78X6+Brm+ QeBSFEZAKlLcvmgcALLIw2AuP3gJLnXYElyO9eaWwQUESFemiQjigg0sRLCo4tpNFGOY ALaw==
X-Gm-Message-State: APjAAAXDMVKEFsfF/HJT9TuascKkRIJwrQFzalPHrth/dGHa6SLiV+/G c+Cn8C8Pa/9MSETjEatLz64=
X-Google-Smtp-Source: APXvYqx7z3b31WJscrc2aRLe+Kn948R15JYfy+MGjS2MgFqMl905iLZUUaE2ZBv5OQwNkiB/sMIKew==
X-Received: by 2002:a5b:f41:: with SMTP id y1mr26964530ybr.164.1567563825695; Tue, 03 Sep 2019 19:23:45 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id p199sm4120409ywe.1.2019. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Sep 2019 19:23:44 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Suresh Krishnan <>
In-Reply-To: <>
Date: Tue, 3 Sep 2019 22:23:43 -0400
Cc: Ron Bonica <>, li zhenqiang <>, draft-voyer-6man-extension-header-insertion <>, draft-ietf-spring-srv6-network-programming <>, "" <>, "" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <>
To: Fernando Gont <>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <>
Subject: Re: [spring] Question about SRv6 Insert function
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Sep 2019 02:23:50 -0000

Hi Fernando,

> On Sep 3, 2019, at 7:17 AM, Fernando Gont <> wrote:
> Hello, Suresh,
> On 2/9/19 19:07, Suresh Krishnan wrote:
> [....]
>>>> So, we should probably explore the motivation for Option 2). If the
>>>> motivation is not sufficient, we should probably standardize on Option 1.
>>> My argument would be:
>>> Folks would do whatever they please with 1). If somehow they feel the
>>> need to do 2), they should *refrain from even suggesting it*, post an
>>> internet draft that proposes to update RFC8200 to allow for the
>>> insertion of EHs, wait for that to be adopted and published, and only
>>> then suggest to do EH insertion.
>> I have put down my thoughts on the future of header insertion work in a
>> mail to the 6man list in May 2017. The mail can be found below
> This seems e bit misleading. What I would expect is that before any work
> is published on EH-insertion, the IPv6 standard is updated to allow for
> EH insertion. (plese see bellow)

>>> P.S.: Given the amount of discussion there has been on this topic in the
>>> context of RFC8200, I'd like to hope that there's no draft-ietf document
>>> suggesting EH-insertion or, if there is, the relevant ADs and chairs
>>> make sure that's not the case anymore.
>> Yes. If a draft violates RFC8200 and it hits the IESG for evaluation, I
>> will certainly hold a DISCUSS position until the violations are fixed.
> Since there have been plenty of attempts to do EH insertion or leave the
> IPv6 standard ambiguous in this respect, and the IETF has had consensus
> that EH insertion is not allowed, I think it would be bad, wastefull,
> tricky, and even dangerous to let a document go through the whole
> publication process, and just rely on the AD to keep the "DISCUSS"
> button pressed.
> Put another way: what'd be the rationale for having a draft-ietf and
> have the corresponding wg ship the document with something that clearly
> goes against IETF consensus, and that the relevant AD has declared that
> wouldn't let pass?

In short, this is not the case. I am *not* the relevant AD for the SRv6 Network Programming draft. If this document was in 6man I would have flagged it much earlier like I did for the SRH draft.