Re: [Idr] AD Review of draft-ietf-idr-bgp-ls-segment-routing-msd-09

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Mon, 30 March 2020 12:51 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 5D5083A1570; Mon, 30 Mar 2020 05:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.698
X-Spam-Level:
X-Spam-Status: No, score=-7.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=Q5dFIdkh; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=CgwCb17w
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 FqMhPq7Q5GgD; Mon, 30 Mar 2020 05:51:42 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DF6F3A156E; Mon, 30 Mar 2020 05:51:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3194; q=dns/txt; s=iport; t=1585572702; x=1586782302; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=r0zArrJPC70+0YxtMztbQbKAJjp0rSrg61xHJL1bPe0=; b=Q5dFIdkh+fNAxRzI+DdqFYehzAs/KBjS8qomBEv7+gujXOLUzZdjsWQf lr754KuW+8Ridf4JN5dR8qPwGoeDIz0n+xUCU7kgCSrUUzWMNGkrplrw/ bdtOw1w6X6s6vWRUHgfKlOm/nGpYXfZjoaYE74E2k4vHhWHoiYzJCfstf c=;
IronPort-PHdr: 9a23:h/n0+BOs5kTG9DJ4rkgl6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEuKQ/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBj4IeLjaTASF8VZX1gj9Ha+YgBY
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwAAAa6oFe/4wNJK1mGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF7gVRQBWxYIAQLKgqEEINFA4pogl+JbY4yglIDVAoBAQEMAQEnBgIEAQGERAIXghskOBMCAwEBCwEBBQEBAQIBBQRthVYMhXABAQEBAgESEREMAQE3AQQHBAIBCA4DBAEBAwImAgICHxEVCAgCBAENBQgagwWCSwMOIAEOoRYCgTmIYnWBMoJ/AQEFhHsNC4IMAwaBDiqMMRqBQT+BWIIYNT6CHkkCAgEZgUuDEDKCLI1xgwmJDocTjwlFCoI8h2GKdoRbgkyIMJBwjxmJFoI4kDUCBAIEBQIOAQEFgWkigVhwFYMnUBgNjh2Dc4UUhUF0AgEBgSWMYQGBDwEB
X-IronPort-AV: E=Sophos;i="5.72,324,1580774400"; d="scan'208";a="738955152"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Mar 2020 12:51:41 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by alln-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 02UCpf4G029758 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 30 Mar 2020 12:51:41 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 30 Mar 2020 07:51:41 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Mon, 30 Mar 2020 07:51:40 -0500
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Mon, 30 Mar 2020 07:51:40 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HQEseU9w2ktI1bnG6dH2JBUV2AaUkaXre9mx5bW/xxPERKEEMYMtaIs0tbmJYLyBVuQR6D60EZhqKfxmfnUDzTmtMraUhS+4c1Z7Ex8RyknXiZJ6O6iNteBrGPVjDXQ7xD+gQY8O8fqMc/VYckN7HKfCByHWDRurTWd0syHjgRMcm2LxycUa92wFIJwMMfpvNRIC26Iro7NZJd7NM7W4xJuDoG6cgcXtSwr1/4qoSKN9XEyYTMoQVMuCF/MwF2RBIn/xgHf0HuoLz+QwVfNDy01J73oCyzkdyi4Sx7+p9R03QoJW3DprN78FS8xyznmkSmSfnEPfp0gr7/q91Jht1Q==
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=r0zArrJPC70+0YxtMztbQbKAJjp0rSrg61xHJL1bPe0=; b=MmEV0qairw+e4m5F7Ngh7c0nPqHgh1vPLRltFEdPtxvl2l/Xlt07/U4iIOADH+X33Kuf/wu3VWyJmmoO1Uykcsboth2qW8qmbQxrCQ3nQvCxqPM2ykuz1A1dq5npAveM4wG5G750Vngqo/lgMkI2Y6oaLjhbo738ysWvpG1dc0+CyCLcdmuGcys7Ccf1H0lALAaYKqyNPZmZyWv2AspIo+ffXIVaVDdgVMQEit+0YSd6jK4LlTEJRZTMWoUDT8MGGxYma9+cQ0nu3MiI6B3Eh6Ts4iOl0L/XGLyOBnAlUD3pzbqedR422sLR+2P3rYq1kPwteB59nb7QLmKJk6N+VQ==
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=r0zArrJPC70+0YxtMztbQbKAJjp0rSrg61xHJL1bPe0=; b=CgwCb17wIQXsYEu0lq1xt0izrbN/vfRkFbLdpoLbnQR8HqG2ClI3PhNCA/1AkHauggNnBflR/oAOYAz0h0uu5R0Cusdqz5hhmc26XfpMtFk2NfLsme5s9AApeDUcfXce62COdsrvPbwc0eaCkwq+cBJxrHUXzF+V6VarAeAnVeY=
Received: from MW3PR11MB4570.namprd11.prod.outlook.com (2603:10b6:303:5f::22) by MW3PR11MB4555.namprd11.prod.outlook.com (2603:10b6:303:2e::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2856.19; Mon, 30 Mar 2020 12:51:39 +0000
Received: from MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::dc3d:f0de:21ec:cf87]) by MW3PR11MB4570.namprd11.prod.outlook.com ([fe80::dc3d:f0de:21ec:cf87%7]) with mapi id 15.20.2856.019; Mon, 30 Mar 2020 12:51:39 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, "draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org" <draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org>, Jeff Tantsura <jefftant.ietf@gmail.com>
CC: Susan Hares <shares@ndzh.com>, "idr-chairs@ietf.org" <idr-chairs@ietf.org>, "idr@ietf. org" <idr@ietf.org>
Thread-Topic: AD Review of draft-ietf-idr-bgp-ls-segment-routing-msd-09
Thread-Index: AQHV7PLTdyzxNHiQ7EKz98hQomp7HKgxYiOAgAp4Z4CAJWpzsA==
Date: Mon, 30 Mar 2020 12:51:39 +0000
Message-ID: <MW3PR11MB4570D21EA2E607E636325768C1CB0@MW3PR11MB4570.namprd11.prod.outlook.com>
References: <CAMMESszb=kVw+9Yw=ozk+k+32_Bz-06G-_xTmikgHJPtoiaUmw@mail.gmail.com> <66f54780-1ef3-4b1c-8e02-0680f9de38d7@Spark> <CAMMESsyHtp4NkxYiDn9NctPP0k3h647r-01fYO0jcDNdNonWng@mail.gmail.com>
In-Reply-To: <CAMMESsyHtp4NkxYiDn9NctPP0k3h647r-01fYO0jcDNdNonWng@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-originating-ip: [72.163.220.1]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4a6780ca-e24a-487b-1f3a-08d7d4a916f1
x-ms-traffictypediagnostic: MW3PR11MB4555:
x-microsoft-antispam-prvs: <MW3PR11MB45554996141F0776C81551C7C1CB0@MW3PR11MB4555.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0358535363
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:(10009020)(4636009)(396003)(136003)(376002)(366004)(39860400002)(346002)(8936002)(8676002)(9686003)(2906002)(81166006)(55016002)(71200400001)(33656002)(66446008)(66556008)(81156014)(66946007)(76116006)(66476007)(4326008)(64756008)(316002)(478600001)(110136005)(5660300002)(966005)(54906003)(26005)(6506007)(186003)(52536014)(86362001)(53546011)(7696005); DIR:OUT; SFP:1101;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 9NDT4XIpKRG8XNkA5t8FqMKdl+ht0ylrAX0ynAQEcQlKfVErjxCNDMY7tivlQrlYJbzxMsU35TcPVtwdIrtfjmkhlhnuq82wJekPE6EUZAAe09qhaF9cjEK8PJpKSBpnd7p2gcUEW5JqwIl91vAWbXTI1RnWKHc4/3R4tX+1ZgzuB1+K3tBeoYj8KgWzOH1RUXETV+FTa5DKjF4Y8Utn+LfuGXopsTbDxiTALzJPKfQWqU5aA1wSo3dfdU3trU+8Gi5Ltw22LQve3NJI+L03//94BlZIdIhsEP+Tq6I9v4q2EHLonR+VQPLJ8m80BP0UqHNGVEBF3pTLee7F+rPKKvkNElgzNr9UzR7kkKfSGwdyFB8Mo+4esJzEGXbUFHR4EsbE1i7cEc2VuDVmMFlZO6o/6xGsm7r/cqc5nUPGmIvHvWPLrrMtONGe3LrehUnNtjPyyngSR9yphc9uG3LqcueycM5rac5h0BouZZoRSfeuqVod0QsspDtEIC2GjyLJDAtf75uhU58VzunfMok2AQ==
x-ms-exchange-antispam-messagedata: hi1lho+v8ZOEoFkmXQuSag7NustVeXVWjY7A57MjTCidMsx8DqWgEU6lbQrz9lg860LDbJJkOAxKDD3yiB5J2XIBlH2Tt40P3tBoNYZvfXCQ2DAiNCh907eqWFeUubcC6pvLa4JCRR1fkkNFy+R3sA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 4a6780ca-e24a-487b-1f3a-08d7d4a916f1
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Mar 2020 12:51:39.4392 (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: trbSW5vlgOiLXJYtVGNLmJWMl0+xjjv13H5nX6CXh9mHnIHl0S4NsBrQautQStxR+cCshr3sVJwRPkFOGzNd0A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW3PR11MB4555
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: alln-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/7nNtfqJ6OyktdP4QETX2xHSHbTw>
Subject: Re: [Idr] AD Review of draft-ietf-idr-bgp-ls-segment-routing-msd-09
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: Mon, 30 Mar 2020 12:51:44 -0000

Hi Alvaro,

I see that the point of inclusion of advertisement of MSD in BGP-only networks is the only outstanding point to be addressed from your AD review. You have suggested that the aspects related to advertisement in BGP-only networks are better covered via draft-ketant-idr-bgp-ls-bgp-only-fabric.

As a co-author of both the concerned drafts, I am ok with removing the BGP-only network aspects from the MSD draft and taking it up in the draft that covers aspects of BGP-only networks.

Would like to take inputs of the WG as well on the same and we can plan to move the draft-ketant-idr-bgp-ls-bgp-only-fabric for adoption.

Thanks,
Ketan

-----Original Message-----
From: Alvaro Retana <aretana.ietf@gmail.com> 
Sent: 06 March 2020 22:41
To: draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org; Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: Susan Hares <shares@ndzh.com>; idr-chairs@ietf.org; idr@ietf. org <idr@ietf.org>
Subject: Re: AD Review of draft-ietf-idr-bgp-ls-segment-routing-msd-09

On February 28, 2020 at 8:17:42 PM, Jeff Tantsura wrote:


Jeff:

Hi!


Thanks for the updated text -- I looked at -13.

I think that including BGP, in this document, as one of the sources of the MSD is not the right thing to do.  Please see the details below.

That is the only major item remaining.  Please take a look at idnits as there are a couple of unused references left:
https://tools.ietf.org/idnits?url=https://tools.ietf.org/id/draft-ietf-idr-bgp-ls-segment-routing-msd-13.txt


Thanks!

Alvaro.



> On Feb 26, 2020, 2:19 PM -0800, Alvaro Retana , wrote:
...
> > This document, like many other BGP-LS specifications to carry 
> > IGP-derived information is written with that assumption: that the 
> > information will come from the IGPs. However, §2 reads:
> >
> > The BGP-LS speaker may also advertise the MSD information for the 
> > local node and its links when not running any link-state IGP 
> > protocol e.g. when running BGP as the only routing protocol.
> >
> > This case (no IGP) is not fully explained in the text. Borrowing 
> > from the IGP RFCs, two clear pieces of information that are missing are:
> >
> > (1) A definition of what the Node/Link MSDs are. I borrowed from 
> > rfc8476 and made suggestions for §3 and §4 of this document (in-line)