Re: [bess] WG Last Call, IPR and Implementation poll for draft-ietf-bess-mvpn-msdp-sa-interoperation-03

Gyan Mishra <hayabusagsm@gmail.com> Sat, 28 September 2019 01:41 UTC

Return-Path: <hayabusagsm@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 8C60912006B; Fri, 27 Sep 2019 18:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 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=0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 NFSnWLK0LL4I; Fri, 27 Sep 2019 18:41:26 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 B376F120026; Fri, 27 Sep 2019 18:41:25 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id 4so3509527qki.6; Fri, 27 Sep 2019 18:41:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VSNad0K9eefCetR71cRRsOhlq9zF4QHZvAiNX61Lrgk=; b=IL9c451IEF5KtYqOT93mAMEwzeihUf3ZzoO/jfW4mL2Yz/xxt/G3k5BBFfk6hiDflL v4/b8SQ/LEKZ+CWAl+Crj6C78oQQc5QBD/CQadWLgHKj0D/Dd4rC5u/aBsBZHbvPc/c1 vFQduKUL4YCX9EmW6nZNt9FcGApwE0DnjT9L8RbPcw3S0Yh7Jdhl7nHiCk4Nd8fcLNQJ 1o3z9zgST53tbN3SlL/6uu+FHZ69mus/SSUKfjYE98CmwanDsGJ8nGUA+j7z0vxzO0Sf LlGCyELCJ36J+vKPocIBt7WTH1dGNMp1ymnofPWw9c/83Qfz7Grs3akbEyHY9y8Ni0x/ m9VA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=VSNad0K9eefCetR71cRRsOhlq9zF4QHZvAiNX61Lrgk=; b=OmrGjUiBVGGo30r8c2D4327IUIxYLa0Vbo18MZgByUrdbKFeoMP66LkIyztAzAm7x9 fTb4UKFVLo+eMHD1iG8MSjgB+zn/JLkevvCh116rMRU0AgZcssraolVxVyDgFL5UB3GF GyCOr+Ha1o9EqBRNKaqBitkLnUkco7Cg/XPJmrYp5/6DUMMvB3VjGNmZ2dsC9gBbdvkv y3VikVXErIN67HWId38QczqcQzATuNPht6VPnP6VBiGmaIXlUgoK0/n9wnDLoCZ+PH9S 5/JVU6bdyPIPQFOrEZtx+dBcxzvMRpvqOAmsKDPZT9rSm9+MDXoaeJHZD44LP4H+qX/m SO5Q==
X-Gm-Message-State: APjAAAW1BFv/7BXX/XgVdvF37dx1ZkCoFK8as2AI02rHmdUodZ8jSdkB daQEeqGwfaLmLGnlfbS6vUQ=
X-Google-Smtp-Source: APXvYqxsqjy3hDKF0RZpWcqnSNeSl3fIRCAtE04MAC7rWKKpqDfjHQyC0ZQ93MgBJ2SIXe7MLDNGYw==
X-Received: by 2002:a37:7a46:: with SMTP id v67mr8160453qkc.298.1569634884506; Fri, 27 Sep 2019 18:41:24 -0700 (PDT)
Received: from ?IPv6:2600:1003:b003:900c:48a7:4c09:576d:1214? ([2600:1003:b003:900c:48a7:4c09:576d:1214]) by smtp.gmail.com with ESMTPSA id k54sm4749155qtf.28.2019.09.27.18.41.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Sep 2019 18:41:23 -0700 (PDT)
From: Gyan Mishra <hayabusagsm@gmail.com>
X-Google-Original-From: Gyan Mishra <hayabusaGSM@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-BC7385EE-61DF-49D0-89DA-A1F320CDEDA7"
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <190E7152-6706-40C3-8378-4C9824377FA0@juniper.net>
Date: Fri, 27 Sep 2019 21:41:22 -0400
Cc: "Jeffrey (Zhaohui) Zhang" <zzhang=40juniper.net@dmarc.ietf.org>, Lenny Giuliano <lenny@juniper.net>, "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>, "bess@ietf.org" <bess@ietf.org>, "draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org" <draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <EB9309E2-2F44-4EA3-85C8-5552D0A97B8F@gmail.com>
References: <9887A050-1ADC-4E26-B380-1B0F737456E5@nokia.com> <alpine.DEB.2.02.1909131203590.24347@contrail-ubm-wing.svec1.juniper.net> <DM5PR05MB354886941FF4B648FD831DDAD4850@DM5PR05MB3548.namprd05.prod.outlook.com> <190E7152-6706-40C3-8378-4C9824377FA0@juniper.net>
To: Vinod N Kumar <vinkumar=40juniper.net@dmarc.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/8vhynlOAIczmFb9ZZaTZlZBmkuM>
Subject: Re: [bess] WG Last Call, IPR and Implementation poll for draft-ietf-bess-mvpn-msdp-sa-interoperation-03
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: Sat, 28 Sep 2019 01:41:29 -0000


As a technical representative of Verizon from an operator and network designer perspective I support the draft as it stands and don’t know of any non disclosed IPRs.

I have a few questions.

So I agree this draft is very useful and fills a gap or problem where customers using ASM do not have a local RP and their shared tree needs to traverse the core.

I think for most customers it’s easy to change their location of their ASM anycast RP so it’s local at every edge and then build your msdp mesh group between all your CE edges and boom “no shared trees” over the mpls core MVPN.

From reading the draft it sounds like the Msdp SA is detected and mapped to the mvpn for the shared tree to get built.

So if your shared tree terminates locally at the edge CE and the edge see is running msdp then you would never have a shared tree. ^*,G that would traverse the core.

If their is an msdp session tcp/639 am not sure I understand how that would be detected also that is RP control plane and not the data plane forwarding.  Also how are you going to do SPT switchover and from shared to SPT tree.  Also then I guess you would need to provide option for RP  infinity to stay permanently on the shared tree.


Regards,

Gyan S. Mishra
IT Network Engineering & Technology 
Verizon Communications Inc. (VZ)
13101 Columbia Pike FDC1 3rd Floor
Silver Spring, MD 20904
United States
Phone: 301 502-1347
Email: gyan.s.mishra@verizon.com
www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT

Sent from my iPhone

> On Sep 24, 2019, at 12:07 AM, Vinod N Kumar <vinkumar=40juniper.net@dmarc.ietf.org> wrote:
> 
> Not aware of any IPR related to mvpn-msdp-sa-interoperation.
> Juniper has an implementation of this draft.
> 
> Regards,
> Vinod Kumar.
> 
> On 24/09/19, 12:07 AM, "BESS on behalf of Jeffrey (Zhaohui) Zhang" <bess-bounces@ietf.org on behalf of zzhang=40juniper.net@dmarc.ietf.org> wrote:
> 
>    Not aware of any relevant IPR.
> 
>    Juniper has an implementation.
> 
>    Jeffrey
> 
>    -----Original Message-----
>    From: Lenny Giuliano <lenny@juniper.net> 
>    Sent: Friday, September 13, 2019 3:07 PM
>    To: Bocci, Matthew (Nokia - GB) <matthew.bocci@nokia.com>
>    Cc: bess@ietf.org; draft-ietf-bess-mvpn-msdp-sa-interoperation@ietf.org
>    Subject: Re: [bess] WG Last Call, IPR and Implementation poll for draft-ietf-bess-mvpn-msdp-sa-interoperation-03
> 
> 
>    Not aware of any IPR related to draft-ietf-bess-mvpn-msdp-sa-interoperation
> 
> 
>    On Tue, 10 Sep 2019, Bocci, Matthew (Nokia - GB) wrote:
> 
>    | 
>    | Hello Working Group,
>    | 
>    |     
>    | 
>    | This email starts a two week Working Group Last Call on 
>    | draft-ietf-bess-mvpn-msdp-sa-interoperation-03 [1].
>    | 
>    |  
>    | 
>    | This poll runs until 25 September 2019.
>    | 
>    |  
>    | 
>    | 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.
>    | 
>    |  
>    | 
>    | There are currently no IPR disclosures against the document.
>    | 
>    |  
>    | 
>    | 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,
>    | 
>    |     Matthew and Stephane
>    | 
>    |  
>    | 
>    |     [1] 
>    | https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-bess-mvpn-msdp-sa-interope__;!8WoA6RjC81c!U8aCsuRpFMIP3TlcIw1_NuPboayld-LeUp2fk-4GbqPAhszKQS6xcSbHZR3Kw5Qb$ 
>    | ration/
>    | 
>    |     [2] 
>    | https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw__;!8WoA6RjC81c!U8aCsuRpFMIP3TlcIw1_NuPboayld-LeUp2fk-4GbqPAhszKQS6xcSbHZekFkSyU$ 
>    | 
>    |  
>    | 
>    |  
>    | 
>    | 
>    | 
> 
>    _______________________________________________
>    BESS mailing list
>    BESS@ietf.org
>    https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/bess__;!8WoA6RjC81c!U8aCsuRpFMIP3TlcIw1_NuPboayld-LeUp2fk-4GbqPAhszKQS6xcSbHZR5oAE0v$ 
> 
> 
> _______________________________________________
> BESS mailing list
> BESS@ietf.org
> https://www.ietf.org/mailman/listinfo/bess