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

Jeff Tantsura <jefftant.ietf@gmail.com> Sun, 05 March 2017 00:21 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 75F6D1293F8 for <idr@ietfa.amsl.com>; Sat, 4 Mar 2017 16:21:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=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 7SoJn4lYrF6r for <idr@ietfa.amsl.com>; Sat, 4 Mar 2017 16:21:20 -0800 (PST)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (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 D876C120724 for <idr@ietf.org>; Sat, 4 Mar 2017 16:21:19 -0800 (PST)
Received: by mail-pg0-x230.google.com with SMTP id 77so10841291pgc.1 for <idr@ietf.org>; Sat, 04 Mar 2017 16:21:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=EF8XG+uXgw6Q76leZfiGegQ38EdUamcrzxaXRP8dhO8=; b=Vy9u+vNpETrKvvj5CI/6sVp5izcK/STD3qt9iBzSGN9b/Kh++47HBixt6pHdRhUSA6 YLox7ATU6vna+U08v++M3S4sgepFFSRNakea+JNIITM5HsOWyQP7Sg7cFUrnkFW+I7aJ vFWhks77TsiQHB6i+wnZYqcecuCjx2PogaoITJuLaHqCSgQnwzEAGtbPRU0rFaWn5dGd dEaOSQ1wLesKv1rwnuLTNmqs0KigRmZfbaEWt0B0KQUT7A8eln4OddjoqBwcx22HP9vz RxJCRiW71MMUk+y6n9b6boxW4Jx86lZ8ESF4wX/Hf9llLnBeEbwbOKMg0bvuMOmbV4Bt qzuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=EF8XG+uXgw6Q76leZfiGegQ38EdUamcrzxaXRP8dhO8=; b=lSMLri6BQ796+DAUlj/e5k/sOnIyv0DiruDYLC7kg1NdwEUZXwGnov7pZ7tKrGcKdx SK5QT5B4QOxIQU9hiSD/C2LKYNYD3mS7/oc7NCMikSJSI+rZ7zNXaQ472G+adDiqD+Hd y/hTUUwrBu1N60v3eO0YWOO1QQkqPpUFQ6uRwocjG2SXAUXnmz41z/VbLqmooR2ZWRIf jwUOyXReWpUDiUjFw8XCi2H1X/0DM/MltLZfiRfC3NULUNi9b7hFkqyyTTaZYAgd5oee P6YKlmyTaFIPvC8ucRF+abnvcB5icEtGa66fnkpipjAxeNJNyOINQdBSWNA1XeNKAFoc x57g==
X-Gm-Message-State: AMke39lr+JAZ+ag1VZk3x4bMWi1XJa+ulozhsUM23KNzwD9L/QZsTQQcKSlGUyVgV3LFlw==
X-Received: by 10.84.218.205 with SMTP id g13mr14931001plm.78.1488673279383; Sat, 04 Mar 2017 16:21:19 -0800 (PST)
Received: from ?IPv6:2607:fb90:2200:1813:3485:a453:869a:d6ce? ([2607:fb90:2200:1813:3485:a453:869a:d6ce]) by smtp.gmail.com with ESMTPSA id e129sm31099169pfe.8.2017.03.04.16.21.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Mar 2017 16:21:17 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-628BC08D-6B2D-407A-995C-58A9006CBD66
Mime-Version: 1.0 (1.0)
From: Jeff Tantsura <jefftant.ietf@gmail.com>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <CA+b+ERmyFNOv0HpoW98ecvbKg0T05pYL6uFZ7Me4nW5n0V+S6g@mail.gmail.com>
Date: Sat, 4 Mar 2017 16:21:13 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <19BCC3A8-48A7-4838-A999-5B304C0C7EED@gmail.com>
References: <148854728632.10105.590253116263033290.idtracker@ietfa.amsl.com> <4BF12F22-F605-406F-9CD8-ACE350B981D0@alcatel-lucent.com> <CA+b+ERkNLHPN23TTC2=Cb-GKDOkFysHca9N3iwopipHPFhLjyA@mail.gmail.com> <CAFAzdPW-KiGdt-Ndtpf4v6TVDPPA2eTaVjKEPkq_s4SPan5oTg@mail.gmail.com> <CA+b+ERmyFNOv0HpoW98ecvbKg0T05pYL6uFZ7Me4nW5n0V+S6g@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1Tg5fKP4RCV03Mh9Ykt-06MvqHM>
Cc: idr wg <idr@ietf.org>, "Van De Velde, Gunter \(Nokia - BE\)" <gunter.van_de_velde@nokia.com>
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: Sun, 05 Mar 2017 00:21:21 -0000

Robert,

Please take a look at 02 isis draft published yesterday, we have added type flag that defines the type of a SID and could be used with v6 dataplane.
The limitations wrt label operations are well understood across both custom and merchant  silicon and from use case prospective had to be addressed first.
V6 dataplane will be added.

Please let me know if this answers your questions and addresses concerns.

Regards,
Jeff

> On Mar 4, 2017, at 06:24, Robert Raszuk <robert@raszuk.net> wrote:
> 
> Jeff,
> 
> MSD drafts (yours invluded) talks about labels while MSD as such seems to be defined as maximum SID depth.
> 
> In SRv6 SID is *NOT* a label. So why not to define MSD properly across all SR scenarios?
> 
> Are we going to have now new zoo of drafts now defining MSD for SRv6 vs current docs just defining MSD for SR-MPLS ?
> 
> Cheers,
> R.
> 
> 
> 
>> On Mar 4, 2017 9:41 AM, "Jeff Tantsura" <jefftant.ietf@gmail.com> wrote:
>> Robert,
>> 
>> That's done in MSD drafts.
>> In the recently published isis draft we have also introduced MSD type flag that would be used to signal different types of SID's: recirculated labels, EL's, etc
>> 
>> Cheers,
>> Jeff
>> 
>> On Fri, Mar 3, 2017 at 22:35 Robert Raszuk <robert@raszuk.net> wrote:
>> Hey Gunter,
>> 
>> Good proposal however why do you only think about labels ?
>> 
>> Seriously if this is to move fwd let's add ability to signal also following elements:
>> 
>> * ability to punt SR-MPLS to local CPU (slow path) when not handled in hardware (per node basis)
>> 
>> * add signalling for number of SRv6 SRHs supported per node/per LC
>> 
>> * add signalling for depth per SRH and total of SIDs supported per node/per LC
>> 
>> * signal ability to punt to slow path or not for longer then support SRH stack or number of SIDs in each SRH structure.
>> 
>> Cheers,
>> Robert.
>> 
>> 
>> On Fri, Mar 3, 2017 at 3:55 PM, Van De Velde, Gunter (Nokia - BE) <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