IETF Logo Mail Archive

Re: [OSPF] Signaling Entropy Label Capability Using OSPF - draft-ietf-ospf-mpls-elc-00

Xuxiaohu <xuxiaohu@huawei.com> Wed, 13 April 2016 07:42 UTC

Return-Path: <xuxiaohu@huawei.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 DF0B512DBCD; Wed, 13 Apr 2016 00:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.217
X-Spam-Level:
X-Spam-Status: No, score=-5.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Vwo8qLImAr7R; Wed, 13 Apr 2016 00:42:06 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6781612DB0B; Wed, 13 Apr 2016 00:42:05 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml707-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CHF90335; Wed, 13 Apr 2016 07:42:01 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml707-cah.china.huawei.com (10.201.5.199) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 13 Apr 2016 08:41:58 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Wed, 13 Apr 2016 15:41:37 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "draft-ietf-ospf-mpls-elc@ietf.org" <draft-ietf-ospf-mpls-elc@ietf.org>
Thread-Topic: Signaling Entropy Label Capability Using OSPF - draft-ietf-ospf-mpls-elc-00
Thread-Index: AQHRlBj81Lqya0qQckSeteuSX15/fJ+HehHg
Date: Wed, 13 Apr 2016 07:41:36 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0D539826@NKGEML515-MBX.china.huawei.com>
References: <D331595E.5903B%acee@cisco.com>
In-Reply-To: <D331595E.5903B%acee@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.99.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.570DF84B.0070, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: a599237cdaaf9e338ff22176db06957d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/IIM6RGj23ZmXVBvh611bOdGq-sI>
Cc: OSPF WG List <ospf@ietf.org>
Subject: Re: [OSPF] Signaling Entropy Label Capability Using OSPF - draft-ietf-ospf-mpls-elc-00
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: Wed, 13 Apr 2016 07:42:08 -0000

Hi Acee,

Thanks for your comments. Please see my response in line.

> -----Original Message-----
> From: Acee Lindem (acee) [mailto:acee@cisco.com]
> Sent: Tuesday, April 12, 2016 1:39 AM
> To: draft-ietf-ospf-mpls-elc@ietf.org
> Cc: OSPF WG List
> Subject: Signaling Entropy Label Capability Using OSPF -
> draft-ietf-ospf-mpls-elc-00
> 
> Authors,
> 
> We will soon be progressing the OSPFv2 SR draft. What is your intent for this
> draft? It is missing:
> 
>     1. A figure with the RI encoding like other OSPF documents

Will add two figures for ELC TLV and RLSDC TLV respectively.

>     2. Discussion as to precisely how the capability would be used by a router in
> an OSPF routing domain. For example, must a router remove the EL if the
> next-hop doesn’t support it?

This document only describes how the ELC and RLSDC are advertised via OSPF. As for how these capabilities would be used are actually described in https://tools.ietf.org/html/draft-ietf-mpls-spring-entropy-label. By the way, a router doesn't need to remove the EL if the next-hop doesn't support it. The only requirement on using EL is: An ingress LSR cannot insert ELs for packets going into a given tunnel unless an egress LSR has indicated via signaling that it can process ELs on that tunnel.

>     3. A discussion of backward compatibility for the new Router-Information
> LSA capability.

Is it enough to add the following text:

"To be compatible with RFC7770, ELC and RLSDC TLVs SHOULD continue to be advertised in the first instance, i.e., 0, of the Router Information LSA."

Best regards,
Xiaohu

> Thanks,
> Acee

v2.23.0 | Report a Bug | By Email