Re: [spring] Question about IPv6 EH-insertion in draft-ietf-spring-srv6-network-programming

Robert Raszuk <robert@raszuk.net> Sat, 07 September 2019 11:43 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE1D1200B1 for <spring@ietfa.amsl.com>; Sat, 7 Sep 2019 04:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=raszuk.net
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 7RObZoMeN649 for <spring@ietfa.amsl.com>; Sat, 7 Sep 2019 04:43:49 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 73AE912006D for <spring@ietf.org>; Sat, 7 Sep 2019 04:43:49 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id u184so5443104qkd.4 for <spring@ietf.org>; Sat, 07 Sep 2019 04:43:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=32/P+36izobQGeDsW6atd0pOLeK+8WoizIedi17z5bA=; b=VDTZTpLCw1SwczIbs9CPFL0qoCuuTWhkCjd4gyQCgG2Vno9UHuxR8Yrq+kagH87lfY LixGx5R+iX5D4Ecxc9eJSzQuDPMwgvMTsDv0VWrQ9n/PyLv9HM4B4zsL9ydaaVgTT+kH TA9eKOC0M9lfcg2L39nnKIJ4YNeXp9mfj/QZ1T+stOiU2BwnBRcZEhDlZ6tUBTE2MjYe 0s3mzTBeaxtxy9Ctuu8dZfY8HSXS+DG+yGwYzevZLmBYqsh1L/Of0w1K1+AAJYcl4Zyz MM46fwCh7N4EEVA0DUzvxGxLnI+VFs9kC4lVfrGO5BwZfNbn70Z7NkZmLIzDJCXBNSiQ ZPdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=32/P+36izobQGeDsW6atd0pOLeK+8WoizIedi17z5bA=; b=HhAGw9YOx/+4lGDv3ZjsuD4DryP8Pnu4WIeXYT0vbe5rSH4u/clgEtZyTValOTA4DI TmoicZPuQZdqFx6XjmdUMmfINtCAbme9A4SqZFElk7ZyK5R08HpvtCckFHSnt89wvs3J Ox6AeSBWBoRsp7qrcdzyMrpcQbq9ybLWRMmiS1JxERd8NGlzFO399OjOHgW/AKB1RQr8 /pXf7hdUXz42Gd17N07fHk/JdD+5823kxVySuy9WRjp/Oh377Sy20cbyUMqpAtKuP7hU fO3OMYI3o+QlL/Fnx0aw+kMZrPKxnux/FUkoyioIQ2hFhqRPbfeFwh8q7YVa+iynRQrZ lDvA==
X-Gm-Message-State: APjAAAXslxgz3a5Cn26Ot8g88hTIYU7dD8Zc5WGUqYsn9AODtZJn7oX5 v2Z8Ocr3QYE/wSfWhMansT3DzKd5tkJVaoOtSz4HUA==
X-Google-Smtp-Source: APXvYqzNXTs9r4D4bhi1EObCX+Fy8AviwdJegxdLoDxAWt7iW/kaPpuQszLBrGMwX4VkG5PrOmzZNlOYu1QcWD9HThk=
X-Received: by 2002:a37:a7c5:: with SMTP id q188mr11467637qke.445.1567856622732; Sat, 07 Sep 2019 04:43:42 -0700 (PDT)
MIME-Version: 1.0
References: <8fe37b98-cba3-ab74-3b00-68f8d46d850e@si6networks.com> <CY4PR11MB1541D0C4B5A65057BB241739C1B50@CY4PR11MB1541.namprd11.prod.outlook.com> <634bdc26-2029-72fa-3fcd-d42923e47d85@si6networks.com>
In-Reply-To: <634bdc26-2029-72fa-3fcd-d42923e47d85@si6networks.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Sat, 07 Sep 2019 13:43:33 +0200
Message-ID: <CAOj+MMHA4pXAoJQSkC5OanRJ2SwD9minC7f_RB+bHUjcFSitAw@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, "spring@ietf.org" <spring@ietf.org>, "draft-ietf-spring-srv6-network-programming@ietf.org" <draft-ietf-spring-srv6-network-programming@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000e9e1d0591f51128"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/0117Mu5PqZQUYFBKWOANHvc2kCc>
Subject: Re: [spring] Question about IPv6 EH-insertion in draft-ietf-spring-srv6-network-programming
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Sep 2019 11:43:51 -0000

> So, double-checking if I understood correctly: You are saying that the
> two uses cases that you are referring to already have an alternative
> specification with encap/decap, but this document proposes to use EH
> insertion to avoid the extra overhead of adding an additional IPv6 header?
>

That is correct.

I have been telling you this over and over again and you were choosing not
to accept it.

But please do think about real deployments which do SRH insertion with
encapsulation on ingress to their network for TE or NP reasons. Then the
same customer would like to use TI-LFA to protect data plane.

So per your and few other comments he would not be able to add another
local (to the protection zone) SRH to his already encapsulated on ingress
packet, but would have to add another IPv6 encapsulation with SRH to be in
line with RFC8200 even if the only point of the new SRH is local single dst
detour and protection of arriving dst address in the outer  most IPv6
header.

How efficient/wise that is ?

Thx,
R.