Re: [mpls] Draft submitted - MPLS Entropy Block

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 02 June 2020 21:18 UTC

Return-Path: <jefftant.ietf@gmail.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 A26953A100A for <mpls@ietfa.amsl.com>; Tue, 2 Jun 2020 14:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 SH22fGw9MYWh for <mpls@ietfa.amsl.com>; Tue, 2 Jun 2020 14:18:17 -0700 (PDT)
Received: from mail-pl1-x633.google.com (mail-pl1-x633.google.com [IPv6:2607:f8b0:4864:20::633]) (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 3E7823A1008 for <mpls@ietf.org>; Tue, 2 Jun 2020 14:18:17 -0700 (PDT)
Received: by mail-pl1-x633.google.com with SMTP id bg4so1928430plb.3 for <mpls@ietf.org>; Tue, 02 Jun 2020 14:18:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=GSOfZMQ1l4PL5GWtHN2VscradxcmIwEJUenQnuyypUM=; b=PmPuOYkdMlbVJqr/Xt/4xxlVCg57JUqhzVp7CmM3n6EFxTzM7ZKLLJhzjP+J0tiYgM 1SvPqeCriTBC7/TRdDe3eANs5Q3DWHp+HVNxDNbyutm5KK3GQjgMehofq/AJgY/kmQEz SowMXdy8bhPCUM4jNvER6/kYQ5wO+K+MADnEvfNszX7OLEqcX+fIlmyq8/6kRxkEfWss bDuaP6kw2ab6Zeu5LqiI8hjmEcFTdT79H62Voei3KX8uQqvyp5LFt24/UBPba8C6poaz hqAVkuF1sbkkaPPIhhL1vCCmyMQ6f7Ieov50XiwHublnwnaGNdQMwbbHcku7Skb5OCPH EQ0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=GSOfZMQ1l4PL5GWtHN2VscradxcmIwEJUenQnuyypUM=; b=GJWRPwfDh+lHCafu7cYFAbK2Ym8lg+Ol0KX/7AZuMkjORZSBg15TWWhSdniMM4HoIs TvvpOB9abUg6qAbI0DuqgCiigdhGfj0AKqkoIDk9ficynirpb+ykTXvDuG9dRjT/tDcN 7/NcHv1FQlaFP59xnEU+bHIEYsqo/DVb1ivnqceEOareyHody8ynu91IgWbLBzFRafOx G2OeAqhB3p7qTAxSGybKGKrf4ZyIeOkmksJFw2m9V3/3Dwr+RgAC6xqf4jrc9LbZFs+x mCFIKkrg6eHF6S0lQl+Fd7EdTswk0tarOoa6FIdvJgkUXV48w5QRnlC8khBOAu/mh/Cn DksA==
X-Gm-Message-State: AOAM532OiPUlJVv8svgLG/xscRG4wi4+tgeKu5BwfjdBTBRi5zuy7oAp eV0swVvcXIBHDZbs5t2eCQ8KeyWwBTs=
X-Google-Smtp-Source: ABdhPJzc0CpH9ElvEkrdpEBwiHiDtSENVtbZDjhypBkvklCHzcNmpkBhDbdKylsGcLUe1jGdR5Y/NA==
X-Received: by 2002:a17:902:6b09:: with SMTP id o9mr27517279plk.100.1591132695136; Tue, 02 Jun 2020 14:18:15 -0700 (PDT)
Received: from [192.168.1.11] (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id x2sm59910pfr.186.2020.06.02.14.18.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Jun 2020 14:18:11 -0700 (PDT)
Date: Tue, 02 Jun 2020 14:18:04 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "mpls@ietf.org" <mpls@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <76b40a4a-87ed-4c37-a830-ef9327a83f82@Spark>
In-Reply-To: <8884715b-fcc9-201d-dc92-78027599ec51@joelhalpern.com>
References: <VI1PR07MB3168E8FD0C1562DB7B48C40CE18B0@VI1PR07MB3168.eurprd07.prod.outlook.com> <188d0d07-5e1f-4422-b144-b1ac547558c0@Spark> <8884715b-fcc9-201d-dc92-78027599ec51@joelhalpern.com>
X-Readdle-Message-ID: 76b40a4a-87ed-4c37-a830-ef9327a83f82@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5ed6c212_569951fe_a91"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/w9qlDUHPwSyhTEmTiCiHeyhw32w>
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:18:19 -0000

Joel,

My assertion is based on reading the draft, no magic involved. None of what you have mentioned below is discussed in the draft, hence ignored.
8662 goes in details as to why particular options have been chosen/rejected.

Cheers,
Jeff
On Jun 2, 2020, 2:01 PM -0700, Joel M. Halpern <jmh@joelhalpern.com>, wrote:
> 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>, 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
> >