Re: [bess] I-D Action: draft-ietf-bess-srv6-services-13.txt
"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 20 March 2022 06:04 UTC
Return-Path: <jmh@joelhalpern.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6713A0C5F for <bess@ietfa.amsl.com>; Sat, 19 Mar 2022 23:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.111
X-Spam-Level:
X-Spam-Status: No, score=-2.111 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, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 qvsh6kYg0noN for <bess@ietfa.amsl.com>; Sat, 19 Mar 2022 23:04:54 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 648F33A0C5D for <bess@ietf.org>; Sat, 19 Mar 2022 23:04:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4KLnK20Ylgz6GYy6; Sat, 19 Mar 2022 23:04:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1647756294; bh=KREQFk5DXUoIkn1uCy4snnuMfkJMZ/lPwkj/sAiuxqI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=VXfuOYjgeG1I3eLQ68yl84s1D1ub2xglXkLiPpHN+QKR4cGV/RGDADIjprs0YUOPi LgynmzUsqBa0BHuLb8vHcMUH36fDsZwYoUnFckqcIkCwHUO3pSFInzCG8/4RWVq0Rr N5MtQ0G/Uru1GPcOU4Mfq2CcRcD3Bdih6yV/jO+c=
X-Quarantine-ID: <xqYTb8vVgw6Y>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.21.218] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4KLnK1343wz6GYy3; Sat, 19 Mar 2022 23:04:53 -0700 (PDT)
Message-ID: <270f23a8-6d29-28c5-1669-37029e908f59@joelhalpern.com>
Date: Sun, 20 Mar 2022 02:04:51 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: Ketan Talaulikar <ketant.ietf@gmail.com>
Cc: BESS <bess@ietf.org>
References: <164774714961.16649.7874978579378917523@ietfa.amsl.com> <afa17ecf-3345-6756-637c-d4917861563b@joelhalpern.com> <CAH6gdPwgdvDo9oFFYef5B8OWwtrv=22RPW3cF1j2BLNo6+X1yw@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <CAH6gdPwgdvDo9oFFYef5B8OWwtrv=22RPW3cF1j2BLNo6+X1yw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/ecvGvNjecRpR_0IMyott5Vm0-oU>
Subject: Re: [bess] I-D Action: draft-ietf-bess-srv6-services-13.txt
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Mar 2022 06:05:00 -0000
I seem to be missing something. The ingress PE (domain edge) applies the destination SID (possibly as part of a SID list). Either it is deciding to use the destination SID, or something else is deciding to use the destination SID. Ignoring the issue of argument manipulation, if the Ingress PE is deciding on its own, doesn't it have to understand the meaning of the behavior in order to decide that it wants to invoke it? If something else provides the SID list and the rules for which traffic should use it (e.g. the SR policy or similar) then the Ingress PE would not seem to need such understanding. Yours, Joel On 3/20/2022 1:37 AM, Ketan Talaulikar wrote: > Hi Joel, > > There is no implicit assumption such as the one you refer to. The > ingress PE does not need to do anything specific with the choice of the > behavior picked by the egress PE except where the behavior involves the > use of argument. Ingress PE does need to know & support the specific > behavior when it needs to supply the argument based on the behavior > definition. > > Thanks, > Ketan > > On Sun, Mar 20, 2022 at 10:56 AM Joel M. Halpern <jmh@joelhalpern.com > <mailto:jmh@joelhalpern.com>> wrote: > > I keep reading the description of the handling of unknown endpoint > behaviors. > > It seems there is an implicit assumption that I would think it would be > helpful to make explicit. As far as I can tell, a head end would never > choose based purely based on local policy to make use of an advertised > SID with an unknown behavior? However, a head end might use such a > ISD, > without knowing what it was really asking, if so instructed by a policy > engine (e.g. SR Policy)? > > Yours, > Joel > > On 3/19/2022 11:32 PM, internet-drafts@ietf.org > <mailto:internet-drafts@ietf.org> wrote: > > > > A New Internet-Draft is available from the on-line > Internet-Drafts directories. > > This draft is a work item of the BGP Enabled ServiceS WG of the IETF. > > > > Title : SRv6 BGP based Overlay Services > > Authors : Gaurav Dawra > > Clarence Filsfils > > Ketan Talaulikar > > Robert Raszuk > > Bruno Decraene > > Shunwan Zhuang > > Jorge Rabadan > > Filename : draft-ietf-bess-srv6-services-13.txt > > Pages : 34 > > Date : 2022-03-19 > > > > Abstract: > > This document defines procedures and messages for SRv6-based BGP > > services including L3VPN, EVPN, and Internet services. It > builds on > > RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432 > > "BGP MPLS-Based Ethernet VPN". > > > > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/ > <https://datatracker.ietf.org/doc/draft-ietf-bess-srv6-services/> > > > > There is also an htmlized version available at: > > > https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services-13 > <https://datatracker.ietf.org/doc/html/draft-ietf-bess-srv6-services-13> > > > > A diff from the previous version is available at: > > > https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-srv6-services-13 > <https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-srv6-services-13> > > > > > > Internet-Drafts are also available by rsync at > rsync.ietf.org::internet-drafts > > > > > > _______________________________________________ > > I-D-Announce mailing list > > I-D-Announce@ietf.org <mailto:I-D-Announce@ietf.org> > > https://www.ietf.org/mailman/listinfo/i-d-announce > <https://www.ietf.org/mailman/listinfo/i-d-announce> > > Internet-Draft directories: http://www.ietf.org/shadow.html > <http://www.ietf.org/shadow.html> > > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > <ftp://ftp.ietf.org/ietf/1shadow-sites.txt> > > _______________________________________________ > BESS mailing list > BESS@ietf.org <mailto:BESS@ietf.org> > https://www.ietf.org/mailman/listinfo/bess > <https://www.ietf.org/mailman/listinfo/bess> >
- [bess] I-D Action: draft-ietf-bess-srv6-services-… internet-drafts
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Ketan Talaulikar
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Joel M. Halpern
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Ketan Talaulikar
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Joel M. Halpern
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Joel Halpern Direct
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Ketan Talaulikar
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Joel M. Halpern
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Ketan Talaulikar
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Joel Halpern Direct
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Ketan Talaulikar
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Joel M. Halpern
- Re: [bess] I-D Action: draft-ietf-bess-srv6-servi… Ketan Talaulikar