Re: How CRH support SFC/Segment Endpoint option?
"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 22 May 2020 16:16 UTC
Return-Path: <jmh@joelhalpern.com>
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 26F623A085C; Fri, 22 May 2020 09:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 EanN2d3mK7Or; Fri, 22 May 2020 09:16:03 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 29FD43A0AD7; Fri, 22 May 2020 09:16:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 49TBS26ZKvz1nvML; Fri, 22 May 2020 09:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1590164162; bh=4PsFAGKbjLDw3VpTxUrZF8kn+UTWevIXH5aO5zYw1uk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=I8KA2GK5h/CDFhW8Xy4TEwKQKz4lClJpuQY7PBPh2bt/HRh7wQtZYagZgfELYlPoP 2FypxFq0qxlpn2XB9U/K0/JMMlrVOiqt5M2IKrvo991owtZilfj5/adBSfY92wUsdK qP0vGqID310luTwX2hmeg29Da8SYT/d7frgBQkUA=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 49TBS164yHz1nt7C; Fri, 22 May 2020 09:16:01 -0700 (PDT)
Subject: Re: How CRH support SFC/Segment Endpoint option?
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>, 6man <6man@ietf.org>, "spring@ietf.org" <spring@ietf.org>
References: <C7C2E1C43D652C4E9E49FE7517C236CB02A2CD12@dggeml529-mbx.china.huawei.com> <DM6PR05MB63482CFA4D5AB938D5A4B818AEB40@DM6PR05MB6348.namprd05.prod.outlook.com> <4278D47A901B3041A737953BAA078ADE18F3D928@DGGEML532-MBX.china.huawei.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <415f3c97-db7d-99bd-eb9d-1fe173a47d97@joelhalpern.com>
Date: Fri, 22 May 2020 12:15:59 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <4278D47A901B3041A737953BAA078ADE18F3D928@DGGEML532-MBX.china.huawei.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/l0kapGxoH8Y3RgMecuod54VJcp0>
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, 22 May 2020 16:16:07 -0000
SFC NSH is not a DOH. SFC is a next-header. And the preferred way to carry the VPN information for SFC is to use an SFC metadatum, since that is already supported. The VPN destination option is for the non-SFC case. Yours, Joel On 5/22/2020 11:11 AM, Pengshuping (Peng Shuping) wrote: > Hi Ron, > > If using DOH, then we would have DOH (VPN) + DOH (SFC) + RH per packet > in some circumstances, right? What if more (ever-emerging) services are > required? Not sure about the forwarding efficiency. > > Best regards, > > Shuping > > *From:*ipv6 [mailto:ipv6-bounces@ietf.org] *On Behalf Of *Ron Bonica > *Sent:* Friday, May 22, 2020 10:17 PM > *To:* Chengli (Cheng Li) <c.l@huawei.com>; 6man <6man@ietf.org>; > spring@ietf.org > *Cc:* spring@ietf.org > *Subject:* RE: How CRH support SFC/Segment Endpoint option? > > Cheng, > > The sole purpose of a Routing header is to steer a packet along a > specified path to its destination. It shouldn’t attempt to do any more > than that. > > The CRH does not attempt to deliver service function information to > service function instances. However, it is compatible with: > > -The Network Service Header (NSH) > > -The Destination Options header that precedes the Routing header > > Both of these can be used to deliver service function information to > service function instances. > > Ron > > Juniper Business Use Only > > *From:*Chengli (Cheng Li) <c.l@huawei.com <mailto:c.l@huawei.com>> > *Sent:* Friday, May 22, 2020 2:56 AM > *To:* 6man <6man@ietf.org <mailto:6man@ietf.org>>; spring@ietf.org > <mailto:spring@ietf.org>; Ron Bonica <rbonica@juniper.net > <mailto:rbonica@juniper.net>> > *Cc:* spring@ietf.org <mailto:spring@ietf.org> > *Subject:* How CRH support SFC/Segment Endpoint option? > > *[External Email. Be cautious of content]* > > Hi Ron, > > When reading the CRH draft, I have a question about how CRH support SFC? > > For example, we have a SID List [S1, S2, S3, S4, S5], and S3 is a SFC > related SID, how to indicate that? By PSSI? [1] > > But how to know which segment endpoint node/egress node should process > this PSSI? At the beginning of the SRm6 design, this is described in > [2]. But you deleted the containers [2]. > > Without that, I don’t really understand how SFC can be supported. > > Best, > > Cheng > > [1]. > https://tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01#section-4.1 > <https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-bonica-spring-sr-mapped-six-01*section-4.1__;Iw!!NEt6yMaO-gk!UD4vf0darQ9cskFhH1fJ9jwZJ-nIciQxgVnf1219YuyyaNcgvNdRUdkjwP15i-Xa$> > > [2]. > https://tools.ietf.org/rfcdiff?url2=draft-bonica-6man-seg-end-opt-04.txt > <https://urldefense.com/v3/__https:/tools.ietf.org/rfcdiff?url2=draft-bonica-6man-seg-end-opt-04.txt__;!!NEt6yMaO-gk!UD4vf0darQ9cskFhH1fJ9jwZJ-nIciQxgVnf1219YuyyaNcgvNdRUdkjwNmXwyHT$>. > > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- >
- How CRH support SFC/Segment Endpoint option? Chengli (Cheng Li)
- RE: How CRH support SFC/Segment Endpoint option? Ron Bonica
- Re: How CRH support SFC/Segment Endpoint option? Sander Steffann
- RE: [spring] How CRH support SFC/Segment Endpoint… James Guichard
- Re: [spring] How CRH support SFC/Segment Endpoint… Sander Steffann
- RE: How CRH support SFC/Segment Endpoint option? Pengshuping (Peng Shuping)
- Re: How CRH support SFC/Segment Endpoint option? Joel M. Halpern
- Re: How CRH support SFC/Segment Endpoint option? Joel M. Halpern
- RE: How CRH support SFC/Segment Endpoint option? Ron Bonica
- RE: How CRH support SFC/Segment Endpoint option? Chengli (Cheng Li)
- Re: How CRH support SFC/Segment Endpoint option? Joel M. Halpern
- RE: How CRH support SFC/Segment Endpoint option? Chengli (Cheng Li)
- Re: How CRH support SFC/Segment Endpoint option? Nick Hilliard
- RE: How CRH support SFC/Segment Endpoint option? Ron Bonica
- Reply: RE: How CRH support SFC/Segment Endpoint o… Chengli (Cheng Li)
- Re: [spring] How CRH support SFC/Segment Endpoint… Robert Raszuk
- Re: [spring] How CRH support SFC/Segment Endpoint… Brian E Carpenter
- Re: [spring] How CRH support SFC/Segment Endpoint… Robert Raszuk
- Re: [spring] How CRH support SFC/Segment Endpoint… Tom Herbert
- Re: [spring] How CRH support SFC/Segment Endpoint… Robert Raszuk
- Re: [spring] How CRH support SFC/Segment Endpoint… Brian E Carpenter
- Re: [spring] How CRH support SFC/Segment Endpoint… Joel M. Halpern
- RE: [spring] How CRH support SFC/Segment Endpoint… James Guichard
- Re: [spring] How CRH support SFC/Segment Endpoint… Joel M. Halpern
- Re: [spring] How CRH support SFC/Segment Endpoint… Tom Herbert
- RE: [spring] How CRH support SFC/Segment Endpoint… James Guichard
- Re: [spring] How CRH support SFC/Segment Endpoint… Joel Halpern Direct
- RE: Reply: RE: How CRH support SFC/Segment Endpoi… Ron Bonica
- RE: [spring] How CRH support SFC/Segment Endpoint… Ron Bonica
- RE: [spring] How CRH support SFC/Segment Endpoint… Chengli (Cheng Li)
- RE: [spring] How CRH support SFC/Segment Endpoint… Ron Bonica
- Re: [spring] How CRH support SFC/Segment Endpoint… Robert Raszuk
- RE: [spring] How CRH support SFC/Segment Endpoint… Xiejingrong (Jingrong)