Re: [Pce] [PCE]:New Version Notification for draft-peng-pce-entropy-label-position-05.txt

Jeff Tantsura <jefftant.ietf@gmail.com> Sun, 21 February 2021 01:40 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A3B3A11DC; Sat, 20 Feb 2021 17:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4ZJTFGLdQjdK; Sat, 20 Feb 2021 17:40:25 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 275263A11DB; Sat, 20 Feb 2021 17:40:24 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id e9so6519767pjj.0; Sat, 20 Feb 2021 17:40:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=j2RtxTNubFnAwg0klxnwChg+v8hN8GEnIxt4ytguK3U=; b=oQUQrniUdAYNlPVNBSTjOVj0Q+sIg2x6bV7RaDqYCxRNTGrp50abgVzjaAoaedf+1R sevn1M9oTXpsKLeH06PgUF6trUBWz9pd2Q8XTrDjl62rZw4AH1LgfmyP207Wk8HTJgAs YKTVAvrsq9eAn878Ar/UbhGiNwNOmmYp9kw7Rq8dHjE9cgrLTEir24MND76VoiGsg4O4 6T5dBk5WsM1cVtU/ctp5KYUInlnF+afTRwepFWJXKdjGWzxFSE86W8vrrmJLaFSx4Djz /oCY9tTO7RcCz4AUGhFUHrXk68FPLsn1HFXsu/qRbSsFfEO89tzD3DgU7VAmWce8B118 MpMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=j2RtxTNubFnAwg0klxnwChg+v8hN8GEnIxt4ytguK3U=; b=TRZ8K+q6BBUlgAdHLCVpMk/ZdKJ3ZZ1SrlAZRz/JnR+dpsiG7x0jJMLYz/6HXGltEW 6ECkfUQgrkWjfM9diIHXN9MPk2ttbYLj1Do8fWk/EsGn7x3BWspbSJq4gzLOF+YVhABx WpiA2bsIi+p7nZkXrFL48vOmgVZZF2JxBf3tsrGwBYDDhHCxpa5wLQ4rfAu1qaXKOjau /RqVAHhywvNRO0xiEPWCNFD6GAlVrKlY07f1nkty3+ZFb/HdnIcRFjk8+ActWH/IvVW8 5p+tjw2w2ygpGnVr9MUIMDxYIc6CdYTcd/RfgHogEVsfDDwgPk8z/R+42jpCzBDpvYfH sBoA==
X-Gm-Message-State: AOAM53185M6xys70B2lHdEz3xG9uqFJWw/x9RGwpsYQUthcR5Xe8NfaC NkKvgRDcn2z+nyNLAzACBucQ8k8HcWj+WA==
X-Google-Smtp-Source: ABdhPJyZuhkVCpAuuKX/cskvrkpv/aF/g4HHFpuvhgVnH9zRuDQ9UYBbc1px278x3Jwrbk+iqSGthA==
X-Received: by 2002:a17:90a:fa90:: with SMTP id cu16mr16662515pjb.155.1613871624020; Sat, 20 Feb 2021 17:40:24 -0800 (PST)
Received: from [192.168.1.12] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id b14sm13565265pji.14.2021.02.20.17.40.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 20 Feb 2021 17:40:22 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-9FB6226F-31D9-4CF3-9C2E-40EB94DF87ED"
Content-Transfer-Encoding: 7bit
From: Jeff Tantsura <jefftant.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Sat, 20 Feb 2021 17:40:21 -0800
Message-Id: <42DB5A02-A277-4D6F-896E-04C001BBF212@gmail.com>
References: <202102201615225016703@zte.com.cn>
Cc: dhruv.ietf@gmail.com, tsaad.net@gmail.com, slitkows.ietf@gmail.com, lizhenbin@huawei.com, draft-peng-pce-entropy-label-position@ietf.org, pce@ietf.org, pce-chairs@ietf.org
In-Reply-To: <202102201615225016703@zte.com.cn>
To: xiong.quan@zte.com.cn
X-Mailer: iPhone Mail (18D52)
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/W2hgPGF3iS_I6ZPjYuXA2tpgkso>
Subject: Re: [Pce] [PCE]:New Version Notification for draft-peng-pce-entropy-label-position-05.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Feb 2021 01:40:30 -0000

Hi,

It is the job of ingress router to impose the SID(label) stack that would include one or more pairs of ELI/EL. This is always a subject to MSD limitations (per platform/per LC if applicable). 
The draft is not discussing implications of these limitations , which I find rather unfortunate.

Regards,
Jeff

> On Feb 20, 2021, at 00:15, xiong.quan@zte.com.cn wrote:
> 
> 
> Dear Dhruv,Stephane,Zhenbin Li,Tarek and WG,
> 
> 
> 
> I just submitted a new version of the draft-peng-pce-entropy-label-position-05. This draft has been presented in IETF 106 and 107. Many thanks for your comments and discussions. 
> 
> 
> 
> First, I think we have the consensus that in case of inter-domain scenario, PCE would be useful for computing both SR path and the placement of entropy labels. We should propose a set of extensions for PCEP.
> 
> 
> 
> Second, I fully agree with that the ingress MUST support the capability of  inserting multiple ELI/ELs and it needs to advertise the capability to PCE. So I think we should add the capability in OPEN message from PCC to PCE. In the current version, we define the E bit for a PCC  to  indicate that it supports the capability of inserting multiple ELI/EL pairs and and supports the results of SR path with ELP from PCE. What is your suggestion? If the E bit is enough? Or should we define the BGP/IGP extension?
> 
> 
> 
> Finally, thanks to Zhenbin, I need to clarify that the ELI/EL pairs are calculated for a specific traffic flow but the placement of the ELI/EL pairs are calculated for a SR-path. In our draft, we propose the PCEs perform computation of SR-path with the the placement of the ELI/EL pairs and the value of ELI/EL pairs are calculated  at the ingress.
> 
> 
> 
> I look forward and appreciate any comment and suggestion from you.
> 
> 
> 
> Thanks,
> 
> Quan
> 
> 
> 
> 
> 
> 主 题 :New Version Notification for draft-peng-pce-entropy-label-position-05.txt
> 
> A new version of I-D, draft-peng-pce-entropy-label-position-05.txt
> has been successfully submitted by Quan Xiong and posted to the
> IETF repository.
> 
> Name:        draft-peng-pce-entropy-label-position
> Revision:    05
> Title:        PCEP Extension for SR-MPLS Entropy Label Position
> Document date:    2021-02-19
> Group:        Individual Submission
> Pages:        9
> URL:            https://www.ietf.org/archive/id/draft-peng-pce-entropy-label-position-05.txt
> Status:         https://datatracker.ietf.org/doc/draft-peng-pce-entropy-label-position/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-peng-pce-entropy-label-position
> Htmlized:       https://tools.ietf.org/html/draft-peng-pce-entropy-label-position-05
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-peng-pce-entropy-label-position-05
> 
> Abstract:
>    This document proposes a set of extensions for PCEP to configure the
>    entropy label position for SR-MPLS networks.
> 
>                                                                                    
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 
> 
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce