Re: [Idr] FW: New Version Notification for draft-vandevelde-idr-bgp-ls-segment-routing-rld-01.txt

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 03 March 2017 22:25 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 404D1129644 for <idr@ietfa.amsl.com>; Fri, 3 Mar 2017 14:25:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 dEQRGdAC2lLr for <idr@ietfa.amsl.com>; Fri, 3 Mar 2017 14:25:19 -0800 (PST)
Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (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 6025712964D for <idr@ietf.org>; Fri, 3 Mar 2017 14:25:19 -0800 (PST)
Received: by mail-pg0-x22a.google.com with SMTP id b129so48143149pgc.2 for <idr@ietf.org>; Fri, 03 Mar 2017 14:25:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-transfer-encoding; bh=IdfVRWg469veVVyAQSZYxtStgXrNgh3sZrVh88Nv1Co=; b=fqpJslP/u8Yf7CT+0GH9IRaY2pP62dBdPIMhdcQjG57Guxqb05p8xZC7j3rOvrijrR 0EKKcKSU/PgArOQ1aztkbIpRpH/eukZPTRdWqLX/Ehz9xeMoCr5INIvEvV882YaJaOyM h52ky0wVqI7wByrSxJxchEou6oOMrT99KLuCXV0FgYgPDAWaYBPmXdr1z6lWobmwrilu ITiqkdZdhOVP5yIH/OLpXLFa+OVAYR5ZpQ9yllQkQJeF7eDTHLfg0wqsKFbPDuQLSqFF ThsFF81OKB286LAjffZ2svpaOXNSpv+UxPhaHGNujUZBpIbTvJp3gRI2nYr8xNk0N30z VX8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=IdfVRWg469veVVyAQSZYxtStgXrNgh3sZrVh88Nv1Co=; b=P+Ktl/cBCe1q/disuLU2Bsk4N+6Qu/6/J44oyMjrtN/EsRVlHJ+iLXOSGjtx8szwLs IndLCydYnM5UzQRNlDMwXDig3ZAN982zjLznJ3MGTFoccRu9sEeBvM/CxidouhFBz9xT E+p0+6HxGxFfppJfyry/r2/6hVaPg2vUbFeoRBkrWmTvJiLaWvZ4skLnhAE14TIoHoJe OSjh9VBuAMLruth3xsxWKEJAeMrVN7oiqJE4llu8R1guwChI3wonUyj1uS2bdiTHHBbQ QMq3IZo5omrfKmKY3R5oy6Glm/06iQTX289R5JzOW277Aj5jSJyI1hKGr4O1jSnnKPgP uDUg==
X-Gm-Message-State: AMke39misiEIRdQdv7DRMbVRB2nLDq3/y3vvHLGO+qt2RwhZiMMqy9tCVK5Gi62HaMxEPw==
X-Received: by 10.98.112.134 with SMTP id l128mr6209329pfc.81.1488579918924; Fri, 03 Mar 2017 14:25:18 -0800 (PST)
Received: from [192.168.254.57] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id a90sm4764920pfg.78.2017.03.03.14.25.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Mar 2017 14:25:17 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.1f.0.170216
Date: Fri, 03 Mar 2017 14:25:16 -0800
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Van De Velde, Gunter (Nokia - BE)" <gunter.van_de_velde@nokia.com>, Gunter Van De Velde <guntervandeveldecc@icloud.com>
Message-ID: <0D328A1E-5481-46C2-B94F-D52CC61C203C@gmail.com>
Thread-Topic: [Idr] FW: New Version Notification for draft-vandevelde-idr-bgp-ls-segment-routing-rld-01.txt
References: <952FA19E-4DBF-4141-BBAC-AC69E56F0E4F@gmail.com> <41BA4B21-FA04-4D00-B84D-AF78E17A2898@icloud.com> <7949CB98-F75F-4C04-A9B7-A36642A71B9D@alcatel-lucent.com>
In-Reply-To: <7949CB98-F75F-4C04-A9B7-A36642A71B9D@alcatel-lucent.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/LcTSq6Kqz8H3ftykeb2Z61chsqk>
Cc: idr <idr@ietf.org>
Subject: Re: [Idr] FW: New Version Notification for draft-vandevelde-idr-bgp-ls-segment-routing-rld-01.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Mar 2017 22:25:24 -0000

Aren’t Synonimous labels significant on egress only?

 
Cheers,
Jeff
 

On 3/3/17, 13:58, "Van De Velde, Gunter (Nokia - BE)" <gunter.van_de_velde@nokia.com> wrote:

    For completeness, I was referring to the following work as use case of the RLD info in addition to entropy use-case:
    https://tools.ietf.org/html/draft-bryant-mpls-sfl-framework-02
    
    G/
    
    On 03/03/2017, 22:26, "Gunter Van De Velde" <guntervandeveldecc@icloud.com> wrote:
    
        There is other use case also to do with Synonimous labels and measurements (Alternate marking for passive measurements) potentially….
        Maybe i should add that one also to the use cases.
        
        G/
        
        > On 3 Mar 2017, at 21:48, Jeff Tantsura <jefftant.ietf@gmail.com> wrote:
        > 
        > Hi Gunter,
        > 
        > If it is up to a controller to setup EL, this extension needed, same way as described in the IGP drafts.
        > 
        > I’d questions usefulness of RLD outsldie of Entropy Labels use case.
        > Transit nodes in  general are not interested in the full label stack content outside of entropy use case.
        > 
        > Even if the node in question  can’t read whole stack, it can still properly forward the packet, perhaps with less optimal hasing.
        > Using RLD as a contsrain in path computation doesn’t seem to be a right thing to do.
        > 
        > Thanks!
        > 
        > Cheers,
        > Jeff
        > 
        > 
        > On 3/3/17, 06:55, "Idr on behalf of Van De Velde, Gunter (Nokia - BE)" <idr-bounces@ietf.org on behalf of gunter.van_de_velde@nokia.com> wrote:
        > 
        >    Heads-up… Happy to learn feedback and comments.
        > 
        >    This draft is short and defines the attribute to use for BGP-LS to expose a 
        >    node RLD "Readable Label Depth" to a centralised controller (PCE/SDN).
        > 
        >    G/
        > 
        >    On 03/03/2017, 14:21, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote:
        > 
        > 
        >        A new version of I-D, draft-vandevelde-idr-bgp-ls-segment-routing-rld-01.txt
        >        has been successfully submitted by Gunter Van de Velde and posted to the
        >        IETF repository.
        > 
        >        Name:		draft-vandevelde-idr-bgp-ls-segment-routing-rld
        >        Revision:	01
        >        Title:		Signalling RLD using BGP-LS
        >        Document date:	2017-03-03
        >        Group:		Individual Submission
        >        Pages:		5
        >        URL:            https://www.ietf.org/internet-drafts/draft-vandevelde-idr-bgp-ls-segment-routing-rld-01.txt
        >        Status:         https://datatracker.ietf.org/doc/draft-vandevelde-idr-bgp-ls-segment-routing-rld/
        >        Htmlized:       https://tools.ietf.org/html/draft-vandevelde-idr-bgp-ls-segment-routing-rld-01
        >        Diff:           https://www.ietf.org/rfcdiff?url2=draft-vandevelde-idr-bgp-ls-segment-routing-rld-01
        > 
        >        Abstract:
        >           This document defines the attribute to use for BGP-LS to expose a
        >           node RLD "Readable Label Depth" to a centralised controller (PCE/
        >           SDN).
        > 
        > 
        > 
        > 
        > 
        >        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
        > 
        > 
        > 
        >    _______________________________________________
        >    Idr mailing list
        >    Idr@ietf.org
        >    https://www.ietf.org/mailman/listinfo/idr
        > 
        > 
        > 
        > _______________________________________________
        > Idr mailing list
        > Idr@ietf.org
        > https://www.ietf.org/mailman/listinfo/idr