IETF Logo Mail Archive

Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?

Sander Steffann <sander@steffann.nl> Tue, 26 May 2020 17:03 UTC

Return-Path: <sander@steffann.nl>
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 0FBD73A0AD7; Tue, 26 May 2020 10:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
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 O1LB8eeM6CTG; Tue, 26 May 2020 10:03:54 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C31B33A0AD9; Tue, 26 May 2020 10:03:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id CB5B44C; Tue, 26 May 2020 19:03:47 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:in-reply-to:references:message-id:date:date:subject :subject:mime-version:from:from:content-transfer-encoding :content-type:content-type:received:received; s=mail; t= 1590512625; bh=CxYd4VhIUXsA1Dqi4uy36d505YkWzWC9eeMR6DUMmjg=; b=X BLhIALRH6xwpD8firv7olFxwCi8A6umNdWWBzdQcy0jKa5TCMcq8MOcajZOVNhWi dojUKCZRP2vo6kplSbcbOJLtR9zRXKLYcZTUZIS8REN8YXGL/d4f1Ak6f0vhKEXO f4t6zP5EoCfur8DJeJ0iCIFCV22KIjMfKonoWbYcFc=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xSJYTMyE_LRk; Tue, 26 May 2020 19:03:45 +0200 (CEST)
Received: from [IPv6:2a02:a213:a300:ce80:4047:9a1c:3280:98fe] (unknown [IPv6:2a02:a213:a300:ce80:4047:9a1c:3280:98fe]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 688EF49; Tue, 26 May 2020 19:03:45 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Mime-Version: 1.0 (1.0)
Date: Tue, 26 May 2020 19:03:44 +0200
Message-Id: <804CF77C-461F-4ACC-9132-FB75D43A483C@steffann.nl>
References: <E26D0925-9D7E-44CC-A66C-87F972B5D073@nokia.com>
Cc: Mach Chen <mach.chen@huawei.com>, "Zafar Ali (zali)" <zali=40cisco.com@dmarc.ietf.org>, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>, "Chengli (Cheng Li)" <c.l@huawei.com>, 6man <6man@ietf.org>, "spring@ietf.org" <spring@ietf.org>
In-Reply-To: <E26D0925-9D7E-44CC-A66C-87F972B5D073@nokia.com>
To: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>
X-Mailer: iPhone Mail (17E262)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/4SYIrBp5bNSWVuROYoDGzcmoA2w>
Subject: Re: [spring] CRH is not needed - Re: How CRH support SFC/Segment Endpoint option?
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: Tue, 26 May 2020 17:03:56 -0000

Hi Wim,

> WH> Sander RFC8663  is supported in linux and various implementations. You can do the encap in the same way as you have done with CRH w/o a router doing the encap. 

You misunderstand. I don't want any encap overhead, I just want IPv6 packets...

Cheers,
Sander

v2.23.0 | Report a Bug | By Email