IETF Logo Mail Archive

Re: [spring] How CRH support SFC/Segment Endpoint option?

Nick Hilliard <nick@foobar.org> Sat, 23 May 2020 17:40 UTC

Return-Path: <nick@foobar.org>
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 CBA6E3A0C9F; Sat, 23 May 2020 10:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 nnUA8UWx2pJy; Sat, 23 May 2020 10:40:26 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EAEF33A040C; Sat, 23 May 2020 10:40:25 -0700 (PDT)
X-Envelope-To: 6man@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id 04NHeAlF042673 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 23 May 2020 18:40:11 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
To: "Chengli (Cheng Li)" <c.l@huawei.com>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, 6man <6man@ietf.org>, "spring@ietf.org" <spring@ietf.org>
References: <C7C2E1C43D652C4E9E49FE7517C236CB02A2CD12@dggeml529-mbx.china.huawei.com> <DM6PR05MB63482CFA4D5AB938D5A4B818AEB40@DM6PR05MB6348.namprd05.prod.outlook.com> <C7C2E1C43D652C4E9E49FE7517C236CB02A37DC6@dggeml509-mbs.china.huawei.com> <2a1737d1-bc5d-3aa5-8865-b916952cc0ed@joelhalpern.com> <C7C2E1C43D652C4E9E49FE7517C236CB02A37EA8@dggeml509-mbs.china.huawei.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <46a8adfd-7c31-1aad-02fc-136f4fecda30@foobar.org>
Date: Sat, 23 May 2020 18:40:09 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:52.0) Gecko/20100101 PostboxApp/7.0.16
MIME-Version: 1.0
In-Reply-To: <C7C2E1C43D652C4E9E49FE7517C236CB02A37EA8@dggeml509-mbs.china.huawei.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/G_mGXwOeZH_9uhrYHh1yywQHlj0>
Subject: Re: [spring] 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: Sat, 23 May 2020 17:40:28 -0000

Chengli (Cheng Li) wrote on 23/05/2020 18:27:
> Sure, you are right, we can use CRH and NSH, but personally, I don't think this is a good idea.

As an operator, I agree - this sounds like a foolish thing to do.

Fortunately, both CRH and NSH processing are disabled by default.  I.e. 
this is only an issue if the operator has explicitly enabled it.

It's also not a bug that if you aim a gun at your feet and pull the 
trigger, that injury will occur.

Nick

v2.23.0 | Report a Bug | By Email