Re: [Teas] Comments on draft-ietf-teas-yang-te-types

Igor Bryskin <Igor.Bryskin@huawei.com> Thu, 18 October 2018 17:49 UTC

Return-Path: <Igor.Bryskin@huawei.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E058F130DD8; Thu, 18 Oct 2018 10:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 skKsoPbqqMQV; Thu, 18 Oct 2018 10:49:42 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8FE7130DC0; Thu, 18 Oct 2018 10:49:41 -0700 (PDT)
Received: from LHREML714-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id A657698617FCE; Thu, 18 Oct 2018 18:49:38 +0100 (IST)
Received: from SJCEML702-CHM.china.huawei.com (10.208.112.38) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 18 Oct 2018 18:49:39 +0100
Received: from SJCEML521-MBX.china.huawei.com ([169.254.1.88]) by SJCEML702-CHM.china.huawei.com ([169.254.4.193]) with mapi id 14.03.0415.000; Thu, 18 Oct 2018 10:49:33 -0700
From: Igor Bryskin <Igor.Bryskin@huawei.com>
To: Matt Hartley <mhartley.ietf@gmail.com>
CC: "draft-ietf-teas-yang-te-types@ietf.org" <draft-ietf-teas-yang-te-types@ietf.org>, "teas@ietf.org" <teas@ietf.org>
Thread-Topic: Comments on draft-ietf-teas-yang-te-types
Thread-Index: AQHUZL1WhP3ct4KrWEGxpoX0tmy/i6UjeE3QgAI5AID//5iRQA==
Date: Thu, 18 Oct 2018 17:49:32 +0000
Message-ID: <0C72C38E7EBC34499E8A9E7DD00786391C5281AE@sjceml521-mbx.china.huawei.com>
References: <CAKfnWBhTrSZyfhpUZdBbyZWei_+grj7iGs3MP10mvryGCZ2XfQ@mail.gmail.com> <0C72C38E7EBC34499E8A9E7DD00786391C524514@sjceml521-mbx.china.huawei.com> <CAKfnWBi_dJXrO=SKC2RPGs-ZgbyG_Ev8gPYCSZmN8BGdXT_+sA@mail.gmail.com>
In-Reply-To: <CAKfnWBi_dJXrO=SKC2RPGs-ZgbyG_Ev8gPYCSZmN8BGdXT_+sA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.147.77]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/w2HXTpEkdLOpUCKJ3Gk6WHb1NoQ>
Subject: Re: [Teas] Comments on draft-ietf-teas-yang-te-types
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2018 17:49:44 -0000

Hi Matt,

Please, see my further responses in-line.

Igor

-----Original Message-----
From: Matt Hartley [mailto:mhartley.ietf@gmail.com] 
Sent: Thursday, October 18, 2018 12:51 PM
To: Igor Bryskin
Cc: draft-ietf-teas-yang-te-types@ietf.org; teas@ietf.org
Subject: Re: Comments on draft-ietf-teas-yang-te-types

Igor,

Thanks for the reply. Snipped most things (I assume you'll do mark-ups
where appropriate) but a couple of follow-ups:

On Wed, Oct 17, 2018 at 10:26 AM Igor Bryskin <Igor.Bryskin@huawei.com>
wrote:

> p26: identity lsp-protection-unidir-1-to-1: description is "LSP protection
> '1+1 Unidirectional Protection'", but that's inconsisent with the name. I'd
> expect this to be for 1:1 protection, not 1+1. Or if it is for 1+1, the
> name should be ...1-plus-1, shouldn't it? Same for the bidir one below.
>
> IB>> Correct.
>
OK - so is that going to be changed? And if so, how? In particular, are you
going to have a separate identity for 1:1, or is that considered to be just
a special case of 1:N and covered by that one?

IB>> We will have separate identities for 1+1 and 1:N, with the latter covering 1:1 as a special case


> p33: identity route-usage-type has route-exclude-ero as an option. Is that
> intended to cover XROs too?
>
> IB>> Yes
>
OK, but please make this clear in the description.
IB>> We will


> p34: identity te-optimization-criterion: Can't an optimization criterion
> be anything that can be used as a metric?
>
> IB>> Yes, in many cases path metrics and path optimization criteria are
> the same, but we do not assume that these are necessarily the same things