IETF Logo Mail Archive

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

"Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Fri, 03 May 2019 15:15 UTC

Return-Path: <satyamoh@cisco.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 13C7F120146; Fri, 3 May 2019 08:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=cM6RxJRC; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=aKVBewsA
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 HqIhFaET1PUo; Fri, 3 May 2019 08:15:19 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C57E11200CD; Fri, 3 May 2019 08:15:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17297; q=dns/txt; s=iport; t=1556896518; x=1558106118; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=06CV01nouAR4/bU67qRqB+OMZrhTGUZgPRDbk1VbPGQ=; b=cM6RxJRCRk9RReNX+ktk56YH7RyXkZT9s8UJbhFcRe0EL+K6PUKB0bZo 0c6GqGgdbDIZuLBdJWQBrpZJvdKo8EWzdwWM3OjcQgqKVUE7lBDkq77R8 QJrx+ruUyxSuBJztLhmKodAHp6DeLUy2dclKeCNTkdzHifriHpAYNSVdq 0=;
IronPort-PHdr: 9a23:QlP3pBNlLuSmKUxS9hwl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjgJeL7Zik9HOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AXAACCWsxc/5ldJa1lGwEBAQEDAQEBBwMBAQGBUQYBAQELAYEOL1ADaVUgBAsohBCDRwOEUoougleSV4RNgS6BJANUDgEBIwqEQAIXgW8jNAkOAQMBAQQBAQIBAm0cDIVKAQEBBBILBh0BATcBDwIBCBEDAQIrAgICMB0IAQEEAQ0FGweDAAGBHU0DHQECDKJ7AoE1iF9xgS+CeQEBBYFGQYJ5GIIOAwaBMgGLTReBQD+BOB+CFzU+gQSBXQIDAYF9DYJdMoImjVWETIgCjRMJAoIJhhiMLRuCDoY/jHuMG4ZMjh0CBAIEBQIOAQEFgU84gVZwFWUBgkGCDxiDV4UUhT9ygSmQFwEB
X-IronPort-AV: E=Sophos;i="5.60,426,1549929600"; d="scan'208,217";a="557810522"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 May 2019 15:15:17 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x43FFHeL025479 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 3 May 2019 15:15:17 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 3 May 2019 10:15:16 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 3 May 2019 11:15:15 -0400
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 3 May 2019 11:15:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=06CV01nouAR4/bU67qRqB+OMZrhTGUZgPRDbk1VbPGQ=; b=aKVBewsAfQXwWLfQX9E3Wy8gXxZTvEK325JK62Gfp6diamzDuuQwZNsOHF3/OeGMZzz76EEagjkLmobj5AUdQFAhec2EVUmvPghcO+X3qzBJr1nFX6jWz8z0TXRiKIRfJzoOrNMtMSQroQnxZWwMfi++EIJljLpD39weRyCLltY=
Received: from BYAPR11MB3094.namprd11.prod.outlook.com (20.177.227.76) by BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.10; Fri, 3 May 2019 15:15:13 +0000
Received: from BYAPR11MB3094.namprd11.prod.outlook.com ([fe80::db7:6a5d:b87e:320a]) by BYAPR11MB3094.namprd11.prod.outlook.com ([fe80::db7:6a5d:b87e:320a%2]) with mapi id 15.20.1856.012; Fri, 3 May 2019 15:15:13 +0000
From: "Satya Mohanty (satyamoh)" <satyamoh@cisco.com>
To: "Swadesh Agrawal (swaagraw)" <swaagraw@cisco.com>, "Zafar Ali (zali)" <zali@cisco.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Thread-Topic: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
Thread-Index: AdUA6N2Rf+SOd1UySuqIw1eSDjH8Zf//8jKAgAE6gQCAABI7gA==
Date: Fri, 03 May 2019 15:15:13 +0000
Message-ID: <729DED01-41EF-46A5-BE28-D06EF4ED2944@cisco.com>
References: <00c901d500e8$de7722e0$9b6568a0$@ndzh.com> <123572E6-EBA5-45CD-BD25-15E363512EED@cisco.com> <C70DB1A9-EF76-41BE-BC19-F35EF59CEF74@cisco.com>
In-Reply-To: <C70DB1A9-EF76-41BE-BC19-F35EF59CEF74@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=satyamoh@cisco.com;
x-originating-ip: [2001:420:c0c8:1003::5c0]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 437da507-c9a9-435c-7bae-08d6cfda2456
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR11MB3558;
x-ms-traffictypediagnostic: BYAPR11MB3558:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB3558808906899D58013C5E75D4350@BYAPR11MB3558.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0026334A56
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(366004)(376002)(346002)(39860400002)(396003)(189003)(199004)(8676002)(8936002)(256004)(110136005)(81156014)(4326008)(966005)(2906002)(6246003)(6116002)(5660300002)(99286004)(478600001)(83716004)(71190400001)(71200400001)(25786009)(316002)(6306002)(14454004)(36756003)(186003)(606006)(68736007)(81166006)(6506007)(76116006)(53546011)(102836004)(82746002)(476003)(486006)(2501003)(446003)(73956011)(66946007)(2616005)(11346002)(53936002)(236005)(76176011)(7736002)(86362001)(66476007)(66556008)(64756008)(66446008)(46003)(54896002)(229853002)(6436002)(6512007)(33656002)(6486002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3558; H:BYAPR11MB3094.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: Mmh3NOiUPJdzbWU8iOsDSoKfMbyvXtCX4EYdpM3D2WoYU0Gcf8SbQSm3F3/xypA4ltuGwyqrpbdofuoqNmLVNsb7+lpo9IUdWdh7MQqPAIk8hXBE1NsPNemjVAqa2VVDkEimGXLIMDoGjeGmzo9jE7gJf5lDlFNMs+YUE/TQwsZFGRCwPD6bDn9XlVKm4lGedj6owiLBwU6KuK7w+t4aSq20NGdLmQchVo6UlG1XkmRWFegHr+H5PhOIdOV7HvlNRAqdnY6MOLMXaCQCW2Z+tMj6kQb1Q7+TZ/v5T1qJICuUZG1wCfK67BCQKDz7orY1EnOUBC+hqZEdSZUI00mnzXaonm9jegUBPx4ZdIFDPmTVDh+glIdEs9hkDKf8vqgHSr7chBq65nJ8rniShHfqV0nmM1yTvD5bbP4RC/TDVEw=
Content-Type: multipart/alternative; boundary="_000_729DED0141EF46A5BE28D06EF4ED2944ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 437da507-c9a9-435c-7bae-08d6cfda2456
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 May 2019 15:15:13.6840 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB3558
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/5tM1YrsbVrCV5ZrZf7zYxU3cVxM>
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: Fri, 03 May 2019 15:15:21 -0000

Support.

Thanks,
---Satya

From: Idr <idr-bounces@ietf.org> on behalf of "Swadesh Agrawal (swaagraw)" <swaagraw@cisco.com>
Date: Friday, May 3, 2019 at 7:11 AM
To: "Zafar Ali (zali)" <zali@cisco.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Cc: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Subject: Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

Support.

Regards
Swadesh

From: Idr <idr-bounces@ietf.org> on behalf of "Zafar Ali (zali)" <zali@cisco.com>
Date: Thursday, May 2, 2019 at 9:24 AM
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Cc: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>, "Zafar Ali (zali)" <zali@cisco.com>
Subject: Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

Hi Susan and the WG,

Support!

More in-line.

Thanks

Regards … Zafar

From: Idr <idr-bounces@ietf.org> on behalf of Susan Hares <shares@ndzh.com>
Date: Thursday, May 2, 2019 at 9:14 AM
To: "idr@ietf.org" <idr@ietf.org>
Cc: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Subject: [Idr] 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


  1.  Does this draft needed support for the SRV6?

Yes


  1.  Is this draft a good starting point for the BGP support for SRv6?

Yes


  1.  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



  1.  Do you know of any existing implementations or any plans for implementation?

Yes

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

v2.23.0 | Report a Bug | By Email