IETF Logo Mail Archive

Re: [Idr] I-D Action: draft-ietf-idr-flowspec-l2vpn-09.txt

Jeffrey Haas <jhaas@pfrc.org> Thu, 03 October 2019 20:54 UTC

Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB3ED120818 for <idr@ietfa.amsl.com>; Thu, 3 Oct 2019 13:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 u_CBKovdXjv2 for <idr@ietfa.amsl.com>; Thu, 3 Oct 2019 13:54:49 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id B16A612003E for <idr@ietf.org>; Thu, 3 Oct 2019 13:54:49 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CB1EA1E2F8; Thu, 3 Oct 2019 16:57:53 -0400 (EDT)
Date: Thu, 03 Oct 2019 16:57:53 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Robert Raszuk <robert@raszuk.net>, "idr@ietf. org" <idr@ietf.org>
Message-ID: <20191003205753.GF28365@pfrc.org>
References: <154650798507.29744.11843661823190688795@ietfa.amsl.com> <CAOj+MMGPmUs4fAzDEwhq4z47r=TK78Kk-6Tp+KMHS0K4O=VdGg@mail.gmail.com> <CAF4+nEHwwPNL4cmXH-TMhL3xnT3LGiP-hWov-YCf=h4B-+N7QQ@mail.gmail.com> <CAOj+MMFQbY3WY9jYSLVXMUvOVMGzOCd1LsFKJupPM0W_3oFJDQ@mail.gmail.com> <CAF4+nEG4=0ew=ZzjaxT9ignbKeA3CgLBwhLp2mteQLfaBLh7VQ@mail.gmail.com> <CAOj+MMGwpUhspjxNiUiqoMnrpVnyyFTwGLTdPzpJNpzjL-vURA@mail.gmail.com> <CAF4+nEE04GbuHHdKerS8PnX_RiBSGf5NQcdL=HvY8AFBObpMDA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAF4+nEE04GbuHHdKerS8PnX_RiBSGf5NQcdL=HvY8AFBObpMDA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/IL4_vujyWSJrf3vQwKBLLDEHrCM>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-flowspec-l2vpn-09.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2019 20:54:52 -0000

Donald,

On Tue, Oct 01, 2019 at 11:37:08AM -0400, Donald Eastlake wrote:
> I also agree the different kinds of flowspec should be kept separate.

In my opinion, as a learning from our 5575bis work, new flowspec should
honestly be deferred for flowspec v2 encoding.  Otherwise, we're likely to
have implementations ignoring the NLRI and/or possibly dropping BGP
sessions.

Certainly figuring out what afi/safi the l2 flowspec encaps should use is a
continuing discussion as well.

-- Jeff

v2.23.0 | Report a Bug | By Email