Hey Wim,
Thanks for (not 😉 ) reading. Yes, MPLS-SFC was certainly in mind, but we wrote the initial document only for NSH, and so the document is named for that and fully scoped for that. I believe that draft-ietf-mpls-sfc-encapsulation is “only” an interface encapsulation of NSH. Thus if we support NSH (we do, and we describe it), and if we support identifying the interface “tunnel type” (we do because this is a standard extension for BGP and we talk about it in the draft), I think we have that document covered. I haven’t read draft-guichard-spring-nsh-s (yet), but it might be a bit premature to include an applicability discussion of that work before it is adopted by SPRING. BUT, I certainly have no objection to someone (you?) starting one or more applicability documents. Ciao, Adrian Oh! John just sent almost the same email! From: BESS <bess-boun...@ietf.org> On Behalf Of Henderickx, Wim (Nokia - BE/Antwerp) Sent: 22 January 2019 17:00 To: stephane.litkow...@orange.com; bess@ietf.org Cc: bess-cha...@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-boun...@ietf.org <mailto:bess-boun...@ietf.org> > on behalf of Stephane Litkowski <stephane.litkow...@orange.com <mailto:stephane.litkow...@orange.com> > Date: Monday, 21 January 2019 at 08:06 To: "bess@ietf.org <mailto:bess@ietf.org> " <bess@ietf.org <mailto:bess@ietf.org> > Cc: "bess-cha...@ietf.org <mailto:bess-cha...@ietf.org> " <bess-cha...@ietf.org <mailto:bess-cha...@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/ [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw _________________________________________________________________________________________________________________________ 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
