Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

Gaurav Dawra <gdawra.ietf@gmail.com> Thu, 02 May 2019 15:02 UTC

Return-Path: <gdawra.ietf@gmail.com>
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 0311D1203A5; Thu, 2 May 2019 08:02:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 2Vbn0JT3UO-g; Thu, 2 May 2019 08:02:46 -0700 (PDT)
Received: from mail-pf1-x435.google.com (mail-pf1-x435.google.com [IPv6:2607:f8b0:4864:20::435]) (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 0D0C212038A; Thu, 2 May 2019 08:02:46 -0700 (PDT)
Received: by mail-pf1-x435.google.com with SMTP id z26so1263134pfg.6; Thu, 02 May 2019 08:02:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Yccnx5D1OBRIdjTaC276PNWunLm42ZmnkgELvMegEkA=; b=nlJg6HPW0/QQuEq9GriQ6GIAQXtGTRoEgqtt3zJTJvRS6wvuFdqzCwegQuWrZPHGEt gzo+OW0aMTUhAJ0mn6m4GlpO7DfYJhDUY3Viv4OISuePFlMPg9yKEbB/ORq7zZEBgWUk xu/Sbm7Vb/3O+GpmOWPKwdml/YB0+1X21cushqarNgT556m2CQ04BYAYzFHPczGtycjK PA+Y6os2uXuZWwEU2gjvzgchG4qZxYNDkJG7aNBtXRy4Gdbcacqw4amlfIakLcLwqAot uUT54dU0yvqu7nmpcVdNvfr+x0VWByf2wq1bT25v1EDXOSYXl84/oULheHYzQvmgtiVd zkIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Yccnx5D1OBRIdjTaC276PNWunLm42ZmnkgELvMegEkA=; b=s8cHeCDuPx0XQ+mpMDNXaBDOM5ix0l337dvs6T4AKNuR1f78cFhoWXRuaRwRFOeZBK 899iMkleHmF4Ubfjdptd8l6/ya2+jx2i09P03zPW+VdFrQAut1GH9jQbSZ5au3TnSyD3 KT4mtbnku+DvPIO13ZOXwvSXZi+dD4AxsO+S0XXQT9l7bcR0F2IiY/boRLmDZxFQSgk1 xDFW4MxDshnW2cDOlbri9AoZyg8AhvQfnHKQvtfPZve41QO//EWfA2kd+uj/vxqYb3mi dYrBB3Mk7yLEZ13zHU4HNtpOw6xI+1DEd4/MpGXX3hOznGfu4fh/m80VsJQ+vfBVBFS2 xDpA==
X-Gm-Message-State: APjAAAVYNA/G13HjOMUPC0We115SFvAkzXqFlpP4qTE0mYBBbAXoGCgn sND0IRIpSNwCumpzjio2U8w=
X-Google-Smtp-Source: APXvYqzAXA0061vKn4F7rvWDsVY+KJMaScnB6KHCes79sBqC1BAT/d/pk+7enUuEXy8adBvB4S4dAg==
X-Received: by 2002:a63:8449:: with SMTP id k70mr4439849pgd.53.1556809365570; Thu, 02 May 2019 08:02:45 -0700 (PDT)
Received: from [192.168.86.115] (c-73-231-117-2.hsd1.ca.comcast.net. [73.231.117.2]) by smtp.gmail.com with ESMTPSA id k9sm51878778pga.22.2019.05.02.08.02.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 May 2019 08:02:44 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-C21C77AB-ADF1-4601-AF6F-9FE1A73D8660
Mime-Version: 1.0 (1.0)
From: Gaurav Dawra <gdawra.ietf@gmail.com>
X-Mailer: iPhone Mail (16C101)
In-Reply-To: <SN6PR11MB28453B5F90F22039CD2F4CAAC1340@SN6PR11MB2845.namprd11.prod.outlook.com>
Date: Thu, 2 May 2019 08:02:43 -0700
Cc: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <83AC1968-AE1B-485C-A382-8648E826E279@gmail.com>
References: <00c901d500e8$de7722e0$9b6568a0$@ndzh.com> <SN6PR11MB28453B5F90F22039CD2F4CAAC1340@SN6PR11MB2845.namprd11.prod.outlook.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/PPNNCZsib2D3TC5Um8yqH9rRS5c>
Subject: Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
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, 02 May 2019 15:02:49 -0000

Hi Sue,

Support as Author. I concur and have same as Ketan’s response below.

Cheers,

Gaurav
LinkedIn

Sent from my iPhone

> On May 2, 2019, at 7:57 AM, Ketan Talaulikar (ketant) <ketant@cisco.com> wrote:
> 
> Hi Sue/All,
>  
> Support as co-author.
>  
>  
> Does this draft needed support for the SRV6?
> Yes. This enables the reporting of SRv6 information from multi-domain IGP topologies via BGP-LS to centralized applications/consumers that can leverage this information for use-cases like TE.
>  
> Is this draft a good starting point for the BGP support for SRv6?
> It is actually for BGP-LS support for SRv6. There is a separate draft-dawra-bess-srv6-services which was presented in BESS that covers the BGP services (Global, VPN, EVPN).
>  
> Do you know of any technical issues regarding this draft?
> If so, do these technical issues present any major problems to the technical solution?
> No.
>  
> Do you know of any existing implementations or any plans for implementation?
> Yes. We have implementation and deployment plans. Would like to request early allocation of code-points post adoption.
>  
> Thanks,
> Ketan
>  
> From: Susan Hares <shares@ndzh.com> 
> Sent: 02 May 2019 18:44
> To: idr@ietf.org
> Cc: draft-dawra-idr-bgpls-srv6-ext@ietf.org
> Subject: Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
>  
> This begins a 2 week WG Adoption call for draft-dawra-idr-bgpls-srv6
>  
> https://datatracker.ietf.org/doc/draft-dawra-idr-bgpls-srv6-ext/
>  
> Please consider the following questions in commenting on the
>  
> Does this draft needed support for the SRV6?
> Is this draft a good starting point for the BGP support for SRv6?
> Do you know of any technical issues regarding this draft?
> If so, do these technical issues present any major problems to the technical solution?
>  
> Do you know of any existing implementations or any plans for implementation?
>  
> One special note, if you mentioning technical issues regarding a draft it can be helpful to the WG.  Our goal is to provide good BGP support of the Spring BGP-LS work in a timely fashion.  The SRv6 support is key to the Spring effort – so it would be helpful to mention and get resolved any issues with this draft.
>  
> Cheerily, Sue Hares  
>