Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Sun, 26 July 2020 05:06 UTC

Return-Path: <ketant@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 A4F7C3A0B0C for <idr@ietfa.amsl.com>; Sat, 25 Jul 2020 22:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.619
X-Spam-Level:
X-Spam-Status: No, score=-9.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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=kvej4IUt; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=TqJ7cmyI
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 7RuC2RZ-mwHi for <idr@ietfa.amsl.com>; Sat, 25 Jul 2020 22:06:55 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DCA43A0B03 for <idr@ietf.org>; Sat, 25 Jul 2020 22:06:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31644; q=dns/txt; s=iport; t=1595740015; x=1596949615; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=uYJVLonUD9bP04wh6OG1gF1n1ddcfsqD2WoB76Y/yXk=; b=kvej4IUtIUUX0DM2Nkez4Hks8N//BH+H8rRqLq734HLUY/a7pCuIuCdw LXJpJCLNRsqS8c635/A4y2PwJYZVsF7q4jY6DtcvJz00mpO+fh3mdHsyl oSQudnd7MH2FIfKl/48QEkNEfV4wsEn5S9lr4wbc8N/XLfvCUCbMmvRrE w=;
IronPort-PHdr: 9a23:bpo92hCIxBprIuCFTdoDUyQJPHJ1sqjoPgMT9pssgq5PdaLm5Zn5IUjD/qw30A3FWIzB4LRFhvbY9af6Vj9I7ZWAtSUEd5pBH18AhN4NlgMtSMiCFQXgLfHsYiB7eaYKVFJs83yhd0QAHsH4ag7ep3So5ngTFwnxcw1vKbe9Fovblc/i0ee09tXaaBlJgzzoZ7R0IV22oAzdu9NQj5FlL/M6ywDCpT1DfOEFyA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CVBQCSDh1f/5FdJa1gHAEBAQEBAQcBARIBAQQEAQGCCoEjL1EHb1gvLAqEKoNGA41UgQGXYIJTA1UDCAEBAQwBASUIAgQBAYRMAheCCwIkOBMCAwEBCwEBBQEBAQIBBgRthVwMhXEBAQEEEhEKEwEBOA8CAQYCEQMBAQEhBwMCAgIwFAkIAgQBEggagwWBfk0DLQEBDpFakGgCgTmIYXaBMoMBAQEFgTcCDkGDIxiCDgMGgTiCbYNZhjcagUE/gRABQ4IYNT6BBIFYAQECAQGBXR4GBwmCYDOCLY82PIJuhlmbOH0Kgl6IVpE5gnuJSI1DhV6FTYxJgWiIRpRsAgQCBAUCDgEBBYFqI4FXcBU7gmlQFwINjh4MFxSDOoUUhUJ0AjUCAwMBBwEBAwl8jgEBgRABAQ
X-IronPort-AV: E=Sophos;i="5.75,397,1589241600"; d="scan'208,217";a="517884441"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Jul 2020 05:06:54 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id 06Q56s3e004673 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 26 Jul 2020 05:06:54 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 26 Jul 2020 00:06:53 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Sun, 26 Jul 2020 01:06:52 -0400
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Sun, 26 Jul 2020 00:06:52 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=J/8fR+In9iUR30nVzpScS/v8wraX+qBVf1JjPDsJei6Mmnb2z25d5xGR29wfUHz/bmTbjj2U4eCz3WxsW7yAJW4rKTHv2Q65KDYK+52EWWyg5cxjcMyUVfgl+Vp/ew368ljOAanaChXpZmGV0MIw/Sdc5hc7+MNBcG5ioX4xXoCUCf4l4PsLH5gUBCcLNid4gfkY863f10XSH9Xe+VG85bhflzDkSRsAzGe2FDR09wOtR4Ky8QrgEp8g97W7o3PLTweYDVjB4YnbGc5ShVjmDOUwPj+R4PSLu8tgw/9kv4HOLwvNBtEjO3OT8u0SdACSsfkCQ5sZtCdmMrrZDGlvpA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uYJVLonUD9bP04wh6OG1gF1n1ddcfsqD2WoB76Y/yXk=; b=SPCqoiRTH4c96lASjiuJ3rYOciFV1vFakLlf7XoBo/m+yd/JBqncYGhGN7/wwCKHTIJGeT/2XpwMJWrd/DhZRw44OIgo3gMr15bM/UfvCeFhfLmmSmkXglNCGLMk7VsFbNxGrkx/FJ94uUuk07nDUJO8X5mhRQIlVUe9/C1WvP/NH1r7yBip/erTOLSSrt1NfijSJoQjaIrcFD6YV+eHxFLsA9jUW+ukVEMREGZ1+mThT+BfSI7Q2ppu23BB3nLIH6C+GeMAJ1hDoGUgMcnnyCEXujn+aOxBBbeKxEHbIfO9W2zcd4P37V32bPK7RkTZTxodPulbwpt65SZAz5zksw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uYJVLonUD9bP04wh6OG1gF1n1ddcfsqD2WoB76Y/yXk=; b=TqJ7cmyIZ5G96eSmLW0CNWnwaLH93KUGL72DZy+yGFDBdS3SvxLXvcSV2ENOIjRYviUBS3NN91zqK5aIgvg/AdS5h5AtPGdl6yTnbI4xmOn4m7Z+bsxPaq/i6x8YlM5uKAu8AbyylFBf39QCq61Pr22Xgr6Esl+MNrpq13TaE3k=
Received: from MW3PR11MB4570.namprd11.prod.outlook.com (2603:10b6:303:5f::22) by MWHPR11MB1471.namprd11.prod.outlook.com (2603:10b6:301:b::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.23; Sun, 26 Jul 2020 05:06:50 +0000
Received: from MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::658f:69a3:2fc5:d430]) by MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::658f:69a3:2fc5:d430%7]) with mapi id 15.20.3216.028; Sun, 26 Jul 2020 05:06:50 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, Susan Hares <shares@ndzh.com>, "'idr@ietf. org'" <idr@ietf.org>
Thread-Topic: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)
Thread-Index: AdZaFCD6TU8kSttDSqqWH2X1sYwTJwAApoyAAAp8JQAAtxI9AAAA2NCAABnjjMABYKGRwA==
Date: Sun, 26 Jul 2020 05:06:50 +0000
Message-ID: <MW3PR11MB4570DB966935084752067FA2C1750@MW3PR11MB4570.namprd11.prod.outlook.com>
References: <015f01d65a14$2551ec60$6ff5c520$@ndzh.com> <F7ACA628-2463-49C0-894C-8E5F2DE1ADB1@cisco.com> <029701d65a40$ac63b270$052b1750$@ndzh.com> <B6B4B65E-48FB-46FF-84F3-0ABB0F157332@cisco.com> <CE4329F8-F1D8-418C-ABAE-7C089762AAC3@cisco.com> <MW3PR11MB4570E0DBAD352B8C24BB9DB5C17A0@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4570E0DBAD352B8C24BB9DB5C17A0@MW3PR11MB4570.namprd11.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [49.36.52.93]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2f811a0a-adda-4149-c703-08d83121b4b4
x-ms-traffictypediagnostic: MWHPR11MB1471:
x-microsoft-antispam-prvs: <MWHPR11MB1471CE9DA0AC5D010CC33B8EC1750@MWHPR11MB1471.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: uKG15O4Ne+XhR9AoGCcuXjJbmxdRgaOorOp7TRoR3Nj4WGgz03QY1dOhGX4aN+REwLtsrCeQf/v7oqh953X5KbMIO++Go6fnDXVcDVE5/8IU497SjYYkz2DWhoGd5Q+O86Dh5ueEQ9GdNdUM3Gz0sNRZa19r15yxHLk5+ynKirvLwMRwwSPCwDbJjr7vF2CVPFtljoi5eJyK2r37uMeY/FuGNXdoWd3KsAvX0AiXr8i/TVT4dBxWVtd2fF1V/Ja+WAbOXMSgqrVQCmJ9MURKLIKB0RpClhuZCuibwoL4TVnSKglOXwRmXbSoHaLXdNbJv4rwuhfNHpcVQWR3dpzlt6prp0JiiwO7OXtrAkHeUeEOPPVKRDxQFx0rMBYxWuKn274Z3gi5js0AtEM6E+IiCA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MW3PR11MB4570.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(376002)(396003)(136003)(366004)(346002)(39860400002)(71200400001)(33656002)(7696005)(26005)(9686003)(53546011)(5660300002)(6506007)(186003)(52536014)(76116006)(66446008)(64756008)(66556008)(66476007)(86362001)(66946007)(478600001)(110136005)(8676002)(83380400001)(8936002)(55016002)(316002)(966005)(9326002)(2906002)(166002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: A92ntvjbkYy166ZF9xen3/JGkm3fyUZ8UxTyqfS1n/v753CHJEvITXGzq9q/oL3/c93u+5rZk5BjjSGiN3aVRCNOJgCQsDxcOT8CItnkTqwG+DWJKswZXvER7AJUifHc3MI40A+G/RehWvbRqx/fR4c6kAP6vLscB/zB8FN+rgqVC0FxhUqe0awQOzYbkkBJWp7rMaBlw73H5W1UzrzCJkNYdZLP12ckXsTTxfIDj7XNxvZPMSMkNH6/RaxoJKam60/ANkxai2x72LjZTdZra+FvqMkMGolDhlrBnieBVbOiVYGX6I9YY95kkvDASxj8zcn1HDgaqRV5QTcKLw1NLhABO4OuzQK+YHcpe8zj+cMqtTx+AGoWAv75pSFAKM2+Jidc7P+8g9eIhFvWhEDuqdczRIQ21fhwVIYfZpywg+pLYiGQRRPyRZco32qkOUS6Be3sA2AevG24t4wyDX7x04IiEPPSJadNcWY9T7CpiTw=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MW3PR11MB4570DB966935084752067FA2C1750MW3PR11MB4570namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MW3PR11MB4570.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2f811a0a-adda-4149-c703-08d83121b4b4
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jul 2020 05:06:50.7297 (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-CrossTenant-userprincipalname: jyGz4omIYhN0QzYUnXheV9AtoQhz3yLR2UFqQvbRGNGY6RUNGJC+PCXaVLO1x9YaR2zVmoyb578O4r9j/15IiA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR11MB1471
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.14, xch-rcd-004.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/WiB5f4hYKeJTmzGdRMx_VlTOclg>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)
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: Sun, 26 Jul 2020 05:06:58 -0000

Hi All,


Just wanted to share that an updated version with the following changes has just been posted : https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-app-specific-attr-03

Thanks,
Ketan

From: Ketan Talaulikar (ketant)
Sent: 19 July 2020 10:20
To: Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org>; Susan Hares <shares@ndzh.com>; 'idr@ietf. org' <idr@ietf.org>
Subject: RE: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

Hi Acee,

Thanks for your review and we’ve incorporated all of your comments. These would be included in the next update.

Thanks,
Ketan

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Acee Lindem (acee)
Sent: 19 July 2020 01:58
To: Acee Lindem (acee) <acee=40cisco.com@dmarc.ietf.org<mailto:acee=40cisco.com@dmarc.ietf.org>>; Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>; 'idr@ietf. org' <idr@ietf.org<mailto:idr@ietf.org>>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

It seems I should apply the same scrutiny to my Emails as I do to draft reviews… 😉
Acee

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org<mailto:acee=40cisco.com@dmarc.ietf.org>>
Date: Saturday, July 18, 2020 at 4:14 PM
To: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>, IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

Hi Authors, Sue,

I’ve suggested looks like a lot of changes (see attached). However, many of them are fall into these categories.


1.      Hyphenate application-specific when the term is used as a compound adjective (as we did in the IGP documents).

2.      Use “that” rather than “which” when it introduces a defining clause.

3.      Use “advertised” rather than “sourced” – this is somewhat subjective and I’ll leave it to the discretion of the authors.

In general, I think the details of the procedures are well thought out.

Thanks,
Acee

From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Tuesday, July 14, 2020 at 8:41 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: RE: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

Acee:

Thank you for sending the editorial comments.   I’ve learned from getting Alvaro’s detailed reviews that I want all the editorial comments considered before I sent it into Alvaro.

Sue

From: Acee Lindem (acee) [mailto:acee@cisco.com]
Sent: Tuesday, July 14, 2020 7:41 PM
To: Susan Hares; 'idr@ietf. org'
Subject: Re: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

Hi Sue,
I support publication. This draft is needed to support the IS-IS and OSPF application-specific attribute drafts on the RFC Queue. I have some editorial comments to align with these documents that I’ll post prior to WG last call end.
Thanks,
Acee

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> on behalf of Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Date: Tuesday, July 14, 2020 at 3:23 PM
To: IDR List <idr@ietf.org<mailto:idr@ietf.org>>
Subject: [Idr] draft-ietf-idr-bgp-ls-app-specific-attr - IPR Call and WG LC (7/14 to 7/29/2020)

This begins a 2 week WG LC for draft-ietf-bgp-ls-app-specific-attr-02.txt.

You can find the draft at:
https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-app-specific-attr/

You can find the implementations reports at:
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-app-specific-attr%20implementations

This is a rather short draft (real text about 8 pages), and the

the corresponding OSPF and ISIS drafts have recently approved by the IESG.



Therefore, we are going to combine WG LC and IPR together.



In your comments please consider:

1) Do you feel this draft is ready for publication?



2) Do you know of deployments of these 2 implementations from Cisco?

Are the features useful in these deployments?



3) Do you have any concerns regarding this technology?



Also, please mention support/no support in your reply.



Cheerily, Sue

(co-chair and shepherd for draft).