Re: [mpls] Draft submitted - MPLS Entropy Block

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 02 June 2020 21:01 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0863A0FE6 for <mpls@ietfa.amsl.com>; Tue, 2 Jun 2020 14:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 OxaeGWCBxzja for <mpls@ietfa.amsl.com>; Tue, 2 Jun 2020 14:01:27 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 EE1AE3A0F3F for <mpls@ietf.org>; Tue, 2 Jun 2020 14:01:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 49c4GH6BJTz1nytZ; Tue, 2 Jun 2020 14:01:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1591131687; bh=o/XeZdQHntmMNxmIlSndKPaeEEhU00o1bL3TrS+A4+E=; h=Subject:To:References:From:Date:In-Reply-To:From; b=mSf8HWPjo3qP3p/C6jUegm9DZopee7dnJ9Qhz6CUMoF33+Px9LtK2qSAaS7PDeBDt X65O5Ov/iDt+1uCAYR3TW+dKWaeLXrE2Y2yrA4UaGQOeu8OctmS5ckDDT91ZMDvK8M 4KYEywmSAkuHEMYOwF/i0poO1eHrcZ3zBcrnTxYI=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 49c4GH2JZRz1nylx; Tue, 2 Jun 2020 14:01:27 -0700 (PDT)
To: Jeff Tantsura <jefftant.ietf@gmail.com>, "mpls@ietf.org" <mpls@ietf.org>
References: <VI1PR07MB3168E8FD0C1562DB7B48C40CE18B0@VI1PR07MB3168.eurprd07.prod.outlook.com> <188d0d07-5e1f-4422-b144-b1ac547558c0@Spark>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <8884715b-fcc9-201d-dc92-78027599ec51@joelhalpern.com>
Date: Tue, 2 Jun 2020 17:01:25 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <188d0d07-5e1f-4422-b144-b1ac547558c0@Spark>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/5DR9eqidHC027zb73bqbFTW7xgU>
Subject: Re: [mpls] Draft submitted - MPLS Entropy Block
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jun 2020 21:01:30 -0000

Jeff, you assertion that the authors are ignoring existing work seems to 
border on mind-reading.  Binding SIDs (ala 8662) are a way to reduce 
label stack depth.  It is a useful tool.  Being able to remove the 
Entropy Label Indicator would also be beneficial.

The proposal does recognize that one may well need more than one entropy 
label (and thus labels aimed at different targets) in the stack.  The 
initial portion of the document does focus on the single entropy label 
case to make the idea clear.  The authors (i am not one of them) are 
well aware of the work on advertising various attributes of label depeth 
for generation and processing.

Yours,
Joel

On 6/2/2020 4:54 PM, Jeff Tantsura wrote:
> Hello co-authors,
> 
> The solution proposed ignores all the previous work done to address this 
> particular issue. Without going into more details
> Please read RFC8662 to better understand all the different pieces involved.
> draft-ietf-isis-mpls-elc/draft-ietf-ospf-mpls-elc specifically to 
> understand control plane involved.
> 
> Cheers,
> Jeff
> On Jun 2, 2020, 1:47 AM -0700, Jiang He 
> <jiang.he=40ericsson.com@dmarc.ietf.org>rg>, wrote:
>>
>> Hello All,
>>
>> I just submitted a draft, 
>> https://datatracker.ietf.org/doc/draft-jiang-mpls-entropy-block/ .  it 
>> describes an approach for MPLS load balance, by  allocating a specific 
>> MPLS label block for entropy usage.
>>
>> The purpose is to mitigate the limitation of the number of labels can 
>> be pushed and the number of labels can be inspected when looking for 
>> entropy information.
>>
>> Your comments are highly appreciated!
>>
>> Regards,
>>
>> Jiang
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
> 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>