Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane
"Andrew G. Malis" <agmalis@gmail.com> Fri, 25 January 2019 23:32 UTC
Return-Path: <agmalis@gmail.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 62BC912872C; Fri, 25 Jan 2019 15:32:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3TQcdqoaByN7; Fri, 25 Jan 2019 15:32:31 -0800 (PST)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4467F1288BD; Fri, 25 Jan 2019 15:32:31 -0800 (PST)
Received: by mail-qk1-x734.google.com with SMTP id y78so6395140qka.12; Fri, 25 Jan 2019 15:32:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=S07siVsTjx3zFUaWKsYwU23setPEdowwoT5yKs4rrEg=; b=BWL0mx8uKy5VzS38CQidF3U2YoaGFl/OrkFF0COCGGAW2tkwbZnDIYjMtTEQfSM1lV vDZYbiFKSbMkBsv7kFTA3S3f/RPmT6zRQd/qcAs6CdRWmA+f//Ylczr7YzJ7hqL07Evc sFaDtaW7/RuAbRdp/Ias4K2jTFbTTbwUf6nmvXVfro/VX83WtLmcmh/OZnzfvZEi2Mhk 2KsE/WWedkXuK+CxvZgdwz71F6Ejo+S5+RFdyUdz8YI86NrsQUvEVbBFr7vwTgUjlnmP 0lH0+GqUrCgiRjPU1Z2ZsQlr/esNKdFOwQ2pd6E5A/hSqnEyq2fw/GPaLm8MSpM4e89o kLPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=S07siVsTjx3zFUaWKsYwU23setPEdowwoT5yKs4rrEg=; b=m9ZkSOs2wMnhdCTAYRB5ETzfS+DDG1tZNDv/ynSZ8b9Sb6cUVsOHQZ8AS2sF9zKLHa y8DC/ZNOSPkH2V/2QKegZGuhjsYMoxtsH1UgSpGcSeXEopC1RTFrxwlucsfdOY+5RHeZ DpHo8ri5nPplvKNWzYlrkyfrv/qCho3gb116ldfuGBiVQyoe+6UWm4TKsImQThml5ajG MDA2qFojnu8+n3sdYP7kBUWIri5R8ku171MLuotTkthsR3Dn4tQ8kH00KRrjLDKXRpwH qYKK0FntzVTSDa1ooNUpg1gGw2htnoYlw7/4bFsU1/lzHEfvWkwatavHC91c/o0cyv1K ++NA==
X-Gm-Message-State: AJcUukeQ9dqiBHyrwIqaMUd7H5FmZ2S/n9BMcKTH4hTxDnqsQzhzhk46 5LPf73OSVQxmdhfl3JNqdkxIn7uMJ+SAaXIPID8=
X-Google-Smtp-Source: ALg8bN7loyWeIe3edwX0/xqHVpwY2jFIAfVinRBLDHEcDtNa+8VHzlIlO/5ME0AAtGUHd/FhTAU21VXZvLTGCCSo6ZA=
X-Received: by 2002:a37:781:: with SMTP id 123mr11607502qkh.231.1548459150326; Fri, 25 Jan 2019 15:32:30 -0800 (PST)
MIME-Version: 1.0
References: <DDB7E727-F64B-4D52-9E9D-13E54D22AA08@nokia.com> <BL0PR05MB5025160316AA8EEEA59C8573C7980@BL0PR05MB5025.namprd05.prod.outlook.com>
In-Reply-To: <BL0PR05MB5025160316AA8EEEA59C8573C7980@BL0PR05MB5025.namprd05.prod.outlook.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 25 Jan 2019 18:32:19 -0500
Message-ID: <CAA=duU2sOzfhq4rzryFCW6aJMiccO0+c0CV+p_p4yGx0dv41ag@mail.gmail.com>
To: John E Drake <jdrake@juniper.net>
Cc: "Henderickx, Wim (Nokia - BE/Antwerp)" <wim.henderickx@nokia.com>, "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "bess@ietf.org" <bess@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ac141058050bdc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/jhRynKD_p0jmHfD0ZCgTZ9YPygQ>
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-nsh-bgp-control-plane
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: Fri, 25 Jan 2019 23:32:34 -0000
John, So, in order to support draft-ietf-mpls-sfc-encapsulation, looking at draft-ietf-idr-tunnel-encaps, you would use the value 10 from the "BGP Tunnel Encapsulation Attribute Sub-TLVs" registry, and also from your draft use the SFP Traversal With MPLS Label Stack TLV and the SPI/SI Representation sub-TLV with bit 0 set and bit 1 cleared? I just want to make sure I correctly read the details. Thanks, Andy On Tue, Jan 22, 2019 at 1:15 PM John E Drake <jdrake@juniper.net> wrote: > Wim, > > > > The subject draft was designed w/ NSH in mind. We added an MPLS > representation of the NSH later, which is the subject of the first draft > you referenced, below. > > > > The way the subject draft is written, the representation of the NSH and > the type of transport tunnel can change on a hop-by-hop basis at the > discretion of the selected next-hop SFF. This is through the use of the > encapsulation attribute, which gives us a very open-ended framework in > which to work. > > > > I think the latter two drafts you referenced, below, are actually > supported already but what needs to be written down is exactly what an SFF > needs to advertise in the encapsulation attribute in order to support > them. > > > > I would be happy to work on this w/ anyone else who is interested. > > > > Yours Irrespectively, > > > > John > > > > *From:* BESS <bess-bounces@ietf.org> *On Behalf Of * Henderickx, Wim > (Nokia - BE/Antwerp) > *Sent:* Tuesday, January 22, 2019 12:00 PM > *To:* stephane.litkowski@orange.com; bess@ietf.org > *Cc:* bess-chairs@ietf.org > *Subject:* Re: [bess] WGLC, IPR and implementation poll for > draft-ietf-bess-nsh-bgp-control-plane > > > I need to get into more details, but the current draft is written with draft-ietf-mpls-sfc-04 > dataplane in mind. I believe that the draft can be useful with other > dataplanes like: draft-ietf-mpls-sfc-encapsulation and > draft-guichard-spring-nsh-s > > So I would like the see the BGP control plane extensions here to become > more generic to support multiple data-planes options. I need to go in more > detail, but from high level this is my feedback here. I don’t want to > stop/block this work as I believe this is a very useful proposal, but if we > make it more generic it can serve a bigger purpose. > > > > So I would like to see the following: > > 1. Protocol draft > 2. Use case drafts for the different data planes. > > > > My 2 cents. > > > > *From: *BESS <bess-bounces@ietf.org> on behalf of Stephane Litkowski < > stephane.litkowski@orange.com> > *Date: *Monday, 21 January 2019 at 08:06 > *To: *"bess@ietf.org" <bess@ietf.org> > *Cc: *"bess-chairs@ietf.org" <bess-chairs@ietf.org> > *Subject: *[bess] WGLC, IPR and implementation poll for > draft-ietf-bess-nsh-bgp-control-plane > > > > Hello Working Group, > > > > This email starts a three weeks Working Group Last Call on > draft-ietf-bess-nsh-bgp-control-plane [1]. > > > > This poll runs until *the 4th of February*. > > > > We are also polling for knowledge of any undisclosed IPR that applies to > this Document, to ensure that IPR has been disclosed in compliance with > IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). > > If you are listed as an Author or a Contributor of this Document please > respond to this email and indicate whether or not you are aware of any > relevant undisclosed IPR. The Document won't progress without answers from > all the Authors and Contributors. > > > > We have several IPRs already disclosed. > > > > If you are not listed as an Author or a Contributor, then please > explicitly respond only if you are aware of any IPR that has not yet been > disclosed in conformance with IETF rules. > > > > We are also polling for any existing implementation as per [2]. > > > > Thank you, > > Stephane & Matthew > > > > [1] > https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Dnsh-2Dbgp-2Dcontrol-2Dplane_&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8&s=TfgMeOz6kzVSiGyw-h1RMGo9QIYi6K9bz8AcyCd3BNI&e=> > > > > [2] > https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw > <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CRB2tJiQePk0cT-h5LGhEWH-s_xXXup3HzvBSMRj5VE&m=NmtJTnm15eI5V8pM4BEFevbruNYPMxijWj6csDXLze8&s=hHwZCKH4zzsnENDFhTn86H9rP-vyWW-Wux-hC7pP6BE&e=> > > > > > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess >
- [bess] WGLC, IPR and implementation poll for draf… stephane.litkowski
- Re: [bess] WGLC, IPR and implementation poll for … Henderickx, Wim (Nokia - BE/Antwerp)
- Re: [bess] WGLC, IPR and implementation poll for … John E Drake
- Re: [bess] WGLC, IPR and implementation poll for … Adrian Farrel
- Re: [bess] WGLC, IPR and implementation poll for … Luay Jalil
- Re: [bess] WGLC, IPR and implementation poll for … Adrian Farrel
- Re: [bess] WGLC, IPR and implementation poll for … Andrew G. Malis
- Re: [bess] WGLC, IPR and implementation poll for … John E Drake
- Re: [bess] WGLC, IPR and implementation poll for … Andrew G. Malis
- Re: [bess] WGLC, IPR and implementation poll for … John E Drake
- Re: [bess] WGLC, IPR and implementation poll for … Andrew G. Malis
- Re: [bess] WGLC, IPR and implementation poll for … stephane.litkowski
- Re: [bess] WGLC, IPR and implementation poll for … Stuart Mackie
- Re: [bess] WGLC, IPR and implementation poll for … Eric C Rosen