Re: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08

Uma Chunduri <uma.chunduri@futurewei.com> Wed, 11 September 2019 23:27 UTC

Return-Path: <uma.chunduri@futurewei.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C68EA12081F; Wed, 11 Sep 2019 16:27:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 NS01VvVM_gSz; Wed, 11 Sep 2019 16:27:56 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760134.outbound.protection.outlook.com [40.107.76.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E4B612003F; Wed, 11 Sep 2019 16:27:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cHjOx0UB3LZCx70asv2b1xXnbOJ4aikqdvWqjYtXo9iKehOEDriAyT+4kzPHczD42/g10ggAUf0EkD5rNJ6jgjB4mFI2zA2pXjdTm2PNwtWckSKOFLnqiAud64lQlMuvtn8fHsM0zE4UX8Tcu4iCW4UCf7ZpMCZVS9KFdb6oRAPlMCuaeHSYCkg17FBBjRusTigaKfG675MznJWI7FR2yCkJ6Hnmkq3reQGD928Bh6U6mes3FYuiK8wwJvM4+ysqbESVkbsgZhocV81rQ3FQYHY5o18CjKAQo+9r53tpVaZXifG7NrQVkdCtg4nU9NLBuvISzFJnP7ZC+4/AizDJbA==
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=3ctFlB8h0ngIJ4mvwbx7nbhXIV0SwR1Ex+wUmOI4saQ=; b=WPiLmLPbUKvt3WsNS+uzEKIxJCAvP4tLczuGzNREiVenA7iX9Jw+RtARU1p18yvwGc0ltiMYCyVCwAA9qo7DPK4uOIAAVtD1wCUTTq/YqYwFgF34hcMzJYRWzGJPjPodRhtcKIC2seg6IM/wU3RfuLWHpPw+++GDm7mRROSFH/ZHMEUo/42VUhaTA4gdfMgqmPR6fX2sMsvJEsiTMe6DM9LhRIcxqcLaW7PfWWAXEEvPNZ4FXdpmK1HBLX5NxTI1M4qKSHA+/rJaPEIlhzOEtx0N3HJdod1Wp7mauNlpauU9cTeJaJmsEI9BnVCAtYNU6xoBBeLUyFUpqXk13jdumQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=3ctFlB8h0ngIJ4mvwbx7nbhXIV0SwR1Ex+wUmOI4saQ=; b=LYXfeqhD8apxOEg9hvodnVRYDsiuf06R/3GgjuKo95cuLlZokBVcZt+3tAe2H1aHGBFIlVhbpYKNue5Y5xVHY07EvuYNhwihkhhMQcJbi5TFrdvghayQmUif8htIG9mZhq9XoDC0A/2TNjOexaUYGB4jkjdwnRqEXtPSwWumSCA=
Received: from CH2PR13MB3462.namprd13.prod.outlook.com (52.132.245.88) by CH2PR13MB3431.namprd13.prod.outlook.com (52.132.245.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.10; Wed, 11 Sep 2019 23:27:51 +0000
Received: from CH2PR13MB3462.namprd13.prod.outlook.com ([fe80::adb4:957:86bf:ef98]) by CH2PR13MB3462.namprd13.prod.outlook.com ([fe80::adb4:957:86bf:ef98%7]) with mapi id 15.20.2263.016; Wed, 11 Sep 2019 23:27:51 +0000
From: Uma Chunduri <uma.chunduri@futurewei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "lsr-ads@ietf.org" <lsr-ads@ietf.org>, "draft-ietf-ospf-mpls-elc@ietf.org" <draft-ietf-ospf-mpls-elc@ietf.org>
Thread-Topic: Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08
Thread-Index: AQHVX2sAQulbgKOGJkm1XSoIFYiCBKclStHQ///GBwCAAhuAYA==
Date: Wed, 11 Sep 2019 23:27:51 +0000
Message-ID: <CH2PR13MB3462420201CF52542532A7D086B10@CH2PR13MB3462.namprd13.prod.outlook.com>
References: <3378034A-5DF1-41BE-8BEF-A6B153B6B1DE@cisco.com> <CH2PR13MB34624F42DD8F755BCD8F735086B60@CH2PR13MB3462.namprd13.prod.outlook.com> <D72A046B-3550-435B-91EE-31B1E2036F12@cisco.com>
In-Reply-To: <D72A046B-3550-435B-91EE-31B1E2036F12@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=uma.chunduri@futurewei.com;
x-originating-ip: [206.16.17.150]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 522970b9-4fc7-48b8-11fd-08d7370faa25
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CH2PR13MB3431;
x-ms-traffictypediagnostic: CH2PR13MB3431:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <CH2PR13MB34319E7AF8E541595BD3CB3A86B10@CH2PR13MB3431.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0157DEB61B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(346002)(39840400004)(136003)(366004)(396003)(199004)(189003)(6246003)(66446008)(4744005)(55016002)(9686003)(66476007)(186003)(54906003)(110136005)(3846002)(7736002)(6306002)(86362001)(74316002)(790700001)(6116002)(71200400001)(6506007)(5660300002)(2501003)(52536014)(102836004)(316002)(33656002)(478600001)(14454004)(26005)(71190400001)(446003)(7696005)(76116006)(66066001)(25786009)(6436002)(76176011)(44832011)(53936002)(54896002)(66574012)(81166006)(81156014)(99286004)(4326008)(11346002)(476003)(486006)(8676002)(2906002)(66556008)(229853002)(8936002)(66946007)(256004)(64756008); DIR:OUT; SFP:1102; SCL:1; SRVR:CH2PR13MB3431; H:CH2PR13MB3462.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 3WH/JDlKj8Co/5dAJLVqt6mmKdEFgHHGNRHni0QNspPZ1b8FkaxRXK7oYxcXtAI7wVnC8b/H3QFZe+H9uiePRiqLOTR6QkXkPlhXXQsARUIQREZD/Atck/DNmWlYeWINgps5AAuYXoAWJT+FMe4XccW71Y6+STR/Q75WzUrRkCOSedZDfxkOV8XTmekhikq/GVy8dd8vj7ueLoj4KdY27wu2j5bLu83zYCvlBD8ywonJAT0TAGyo+CJVvocDLA/75u/8p0llC2op5l/ZvDFhK1RdOzyUJkSdGW8uoE2rtTShEj+Wq4hE88vpaofpMsqWu9qdIChwZ3lFgAzSXfsAwwpivsl0nfe+p9KIKplM0I3A0iUqO8JzR0I3vi3oQdYma+J69UR5/O5YvqaOvcewvPxomIiG3pLUAo0NOBzwd/w=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR13MB3462420201CF52542532A7D086B10CH2PR13MB3462namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 522970b9-4fc7-48b8-11fd-08d7370faa25
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Sep 2019 23:27:51.3948 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: F9H8Q3pOWJxs55m3K9yVwl4djaH4QYnD4W962ErepL7lr1fyhF85/n683NsHpU8ty1g/cq/On2Ri7Lcf8Ttt0g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR13MB3431
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/3Iq-D9ZjTGlEBAB3QAqBnAlYjdc>
Subject: Re: [Lsr] Working Group Last Call for "Signaling Entropy Label Capability and Entropy Readable Label-stack Depth Using OSPF" - draft-ietf-ospf-mpls-elc-08
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Sep 2019 23:27:59 -0000

>Because the intra-area link topology is not exposed across areas or to other protocols.

Agreed Acee.

But just looking this again then:


  1.  Not really clear why ELC is required in Section 4, when it’s confirmed from Stephane’s email (Sept 4th 2019) ERLD covers both reading + doing and action.
  2.  Section 4 extending RFC 7794, with E bit, which is defined for prefix attributes for inter-area purposes (no  ERLD value obviously). Same thing can be achieved simply if router capability with ERLD value itself is propagated (per RFC 7981).

Overall, I am more confused here than earlier. But feel free to ignore my comments.


--
Uma C.