Re: [OSPF] WG Last Call for "Signalling ELC using OSPF"
"Acee Lindem (acee)" <acee@cisco.com> Tue, 08 November 2016 01:26 UTC
Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04E7F1294D6 for <ospf@ietfa.amsl.com>; Mon, 7 Nov 2016 17:26:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.017
X-Spam-Level:
X-Spam-Status: No, score=-16.017 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, 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
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 RMNK7blO2j_4 for <ospf@ietfa.amsl.com>; Mon, 7 Nov 2016 17:26:47 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 805641293F5 for <ospf@ietf.org>; Mon, 7 Nov 2016 17:26:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25833; q=dns/txt; s=iport; t=1478568407; x=1479778007; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=OqKvKyLwMTjGDF8lVAyFSBQHIx1JtN3dPBIoReQTW8w=; b=j3wu321F/arqtFPkOEFD1ucNiXZ4dYTBPuAXwXH7Ike1s1UiPwRikTz0 5BVsYJC7Wc8PGiWfzX54WzBVvB6LitaLo1Cs0i3epYpcCrQl70hDgkioO l7Pq7LwqW9KTdQhXS8cbt9Z9cMGjtoAQwRCWqkNJTGYKxO8eYfezkynbH s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAQAEKSFY/4oNJK1dGQEBAQEBAQEBAQEBBwEBAQEBgnM7AQEBAQEfWHwHjTKXApJDgg+CCCuFeQIagWo/FAECAQEBAQEBAWIohGEBAQEEHQYKXAIBCBEDAQEBKAMCAgIwFAkIAgQBEohYDrFqgkCLQAEBAQEBAQEBAQEBAQEBAQEBAQEBARcFixOEGQoBBgE8FoJOglwFlEeFYAGGNIMLhwSBboRwiAmBKY0qhAUBHjdWJBuFD3IBhQ0BDheBCoEMAQEB
X-IronPort-AV: E=Sophos;i="5.31,459,1473120000"; d="scan'208,217";a="345662458"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Nov 2016 01:26:43 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id uA81QhcW026994 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 8 Nov 2016 01:26:43 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 7 Nov 2016 20:26:43 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 7 Nov 2016 20:26:42 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] WG Last Call for "Signalling ELC using OSPF"
Thread-Index: AQHSOOPZHSG+wWYC1kG9iSPI9fUK+KDOO7yA
Date: Tue, 08 Nov 2016 01:26:42 +0000
Message-ID: <D44692FE.88550%acee@cisco.com>
References: <D4438504.8827B%acee@cisco.com> <16761_1478515435_58205AEB_16761_1458_1_53C29892C857584299CBF5D05346208A1EC6CD2A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <16761_1478515435_58205AEB_16761_1458_1_53C29892C857584299CBF5D05346208A1EC6CD2A@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.197]
Content-Type: multipart/alternative; boundary="_000_D44692FE88550aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/AhoW_COwQ1hYufLxl0P3QaO-TSM>
Subject: Re: [OSPF] WG Last Call for "Signalling ELC using OSPF"
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Nov 2016 01:26:50 -0000
Hi Bruno, From: Bruno Decraene <bruno.decraene@orange.com<mailto:bruno.decraene@orange.com>> Date: Monday, November 7, 2016 at 6:43 AM To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, OSPF WG List <ospf@ietf.org<mailto:ospf@ietf.org>> Subject: RE: [OSPF] WG Last Call for "Signalling ELC using OSPF" Hi authors, all, Please find below some comments on the RLDC definition. 1) I’d like to see a more specific definition of RLDC. e.g. load-balancing hashing could be done based on (hashing): -a- a (stack of) N “regular” MPLS labels (i.e. there is no ELI in this stack) -b- the (IP) header below the stack of N labels -c- the EL label in the stack of N labels (i.e. there is one ELI in this stack) I’d like the specification to be clear on the applicability of the RLDC. Does it apply on these 3 cases, on only a subset? Personally, I’d like at least a and c be in scope of the RLDC definition, such that an ingress with limited push capability could have enough information to decide that it could avoid pushing an ELI,EL pair if the stack of MPLS labels that it pushes has enough entropy within the first RLDC labels. I think that the signaling document should reference section 4 of https://www.ietf.org/id/draft-ietf-mpls-spring-entropy-label-04.txt. However, I don’t think -b- is covered there. 2) Current text seems to limit the use of the RLDC to the insertion of a _second_ EL. Why is the RLD not applicable to the first EL? §1. Introduction “This capability, referred to as Readable Label Deepth Capability (RLDC) can be used by ingress LSRs to determine whether it's necessary to insert an EL for a given LSP tunnel in the case where there has already been at least one EL in the label stack [I-D.ietf-mpls-spring-entropy-label<https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-03#ref-I-D.ietf-mpls-spring-entropy-label>]” §6 Usage and Applicability “The RLDC is used by ingress LSRs to determine whether it's necessary to insert an EL for a given LSP tunnel in the case where there has already been at least one EL in the label stack. » I think that this is an unnecessary restriction of the RLDC usage. Indeed, an ingress with a limited capability in term of label push, could be forced to push a single EL label. It should be able to use the RLDC info in order to choose the best location for the EL, even if it pushes a single one. But both sentences seems to restrict RLDC usage for the additional EL push, not the first one. I would tend to agree. Thanks, Acee Thanks, Regards, --Bruno From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem (acee) Sent: Saturday, November 05, 2016 5:46 PM To: OSPF WG List Subject: [OSPF] WG Last Call for "Signalling ELC using OSPF" This begins the WG last call for "Signalling ELC using OSPF”, https://www.ietf.org/id/draft-ietf-ospf-mpls-elc-03.txt. Please review the document and send comments to this list prior to Nov 27th, 2016. Due to the IETF week, the last call period is going to be 3 weeks rather than usual 2 weeks. Thanks, Acee _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
- [OSPF] WG Last Call for "Signalling ELC using OSP… Acee Lindem (acee)
- Re: [OSPF] WG Last Call for "Signalling ELC using… Acee Lindem (acee)
- Re: [OSPF] WG Last Call for "Signalling ELC using… bruno.decraene
- Re: [OSPF] WG Last Call for "Signalling ELC using… Acee Lindem (acee)
- [OSPF] 答复: WG Last Call for "Signalling ELC using… Xuxiaohu
- Re: [OSPF] WG Last Call for "Signalling ELC using… bruno.decraene
- Re: [OSPF] WG Last Call for "Signalling ELC using… bruno.decraene
- Re: [OSPF] WG Last Call for "Signalling ELC using… Acee Lindem (acee)
- Re: [OSPF] WG Last Call for "Signalling ELC using… Carlos Pignataro (cpignata)
- Re: [OSPF] WG Last Call for "Signalling ELC using… Acee Lindem (acee)
- Re: [OSPF] WG Last Call for "Signalling ELC using… stephane.litkowski
- [OSPF] 答复: WG Last Call for "Signalling ELC using… Xuxiaohu
- Re: [OSPF] WG Last Call for "Signalling ELC using… bruno.decraene
- [OSPF] 答复: WG Last Call for "Signalling ELC using… Xuxiaohu
- Re: [OSPF] WG Last Call for "Signalling ELC using… Carlos Pignataro (cpignata)
- Re: [OSPF] WG Last Call for "Signalling ELC using… bruno.decraene
- Re: [OSPF] 答复: WG Last Call for "Signalling ELC u… Carlos Pignataro (cpignata)
- Re: [OSPF] 答复: WG Last Call for "Signalling ELC u… stephane.litkowski
- [OSPF] 答复: 答复: WG Last Call for "Signalling ELC u… Xuxiaohu
- [OSPF] 答复: WG Last Call for "Signalling ELC using… Xuxiaohu
- Re: [OSPF] WG Last Call for "Signalling ELC using… Carlos Pignataro (cpignata)
- Re: [OSPF] 答复: WG Last Call for "Signalling ELC u… Acee Lindem (acee)
- [OSPF] 答复: 答复: WG Last Call for "Signalling ELC u… Xuxiaohu
- [OSPF] 答复: 答复: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] 答复: ??: WG Last Call for "Signalling E… stephane.litkowski
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… Acee Lindem (acee)
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… Shraddha Hegde
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… Acee Lindem (acee)
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… John E Drake
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… Shraddha Hegde
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… John E Drake
- [OSPF] 答复: [mpls] 答复: ??: WG Last Call for "Signa… Xuxiaohu
- Re: [OSPF] 答复: [mpls] 答复: ??: WG Last Call for "S… John E Drake
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… Acee Lindem (acee)
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… Jeff Tantsura
- [OSPF] 答复: [mpls] 答复: ??: WG Last Call for "Signa… Xuxiaohu
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… stephane.litkowski
- [OSPF] 答复: [mpls] 答复: ??: WG Last Call for "Signa… Xuxiaohu
- [OSPF] 答复: 答复: [mpls] 答复: ??: WG Last Call for "S… Xuxiaohu
- Re: [OSPF] [mpls] 答复: ??: WG Last Call for "Signa… stephane.litkowski
- [OSPF] 答复: [mpls] 答复: ??: WG Last Call for "Signa… Xuxiaohu
- Re: [OSPF] [mpls] =?UTF-8?B?562U5aSN?=: ??: WG La… Jeff Tantsura
- [OSPF] 答复: [mpls] 答复: ??: WG Last Call for "Signa… Xuxiaohu
- [OSPF] 答复: 答复: [mpls] 答复: ??: WG Last Call for "S… Xuxiaohu
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… Acee Lindem (acee)
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… Acee Lindem (acee)
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… Acee Lindem
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… Acee Lindem (acee)
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] 答复: ??: WG Last Call for "Signalling E… Acee Lindem (acee)
- [OSPF] 答复: 答复: ??: WG Last Call for "Signalling E… Xuxiaohu
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… Acee Lindem (acee)
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] 答复: ??: WG Last Call for "Signalling E… Acee Lindem (acee)
- Re: [OSPF] 答复: ??: WG Last Call for "Signalling E… Shraddha Hegde
- Re: [OSPF] ??: ??: WG Last Call for "Signalling E… bruno.decraene
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] ??: WG Last Call for "Signalling ELC u… bruno.decraene
- Re: [OSPF] ??: ??: WG Last Call for "Signalling E… bruno.decraene
- Re: [OSPF] ??: ??: WG Last Call for "Signalling E… Acee Lindem (acee)
- [OSPF] 答复: ??: WG Last Call for "Signalling ELC u… Xuxiaohu
- Re: [OSPF] ??: ??: WG Last Call for "Signalling E… bruno.decraene
- Re: [OSPF] ??: ??: WG Last Call for "Signalling E… Carlos Pignataro (cpignata)
- Re: [OSPF] ??: ??: WG Last Call for "Signalling E… Acee Lindem (acee)
- Re: [OSPF] [mpls] ??: ??: WG Last Call for "Signa… Acee Lindem (acee)
- Re: [OSPF] [mpls] ??: ??: WG Last Call for "Signa… bruno.decraene
- Re: [OSPF] [mpls] ??: ??: WG Last Call for "Signa… Carlos Pignataro (cpignata)
- Re: [OSPF] [mpls] ??: ??: WG Last Call for "Signa… Acee Lindem (acee)
- Re: [OSPF] [mpls] ??: ??: WG Last Call for "Signa… Carlos Pignataro (cpignata)
- Re: [OSPF] [mpls] ??: ??: WG Last Call for "Signa… Shraddha Hegde
- [OSPF] 答复: [mpls] ??: ??: WG Last Call for "Signa… Xuxiaohu