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

Jeff Tantsura <jefftant.ietf@gmail.com> Mon, 10 April 2017 16:10 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 A5A031296C6 for <idr@ietfa.amsl.com>; Mon, 10 Apr 2017 09:10:28 -0700 (PDT)
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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 zT3VOs7xsLrr for <idr@ietfa.amsl.com>; Mon, 10 Apr 2017 09:10:25 -0700 (PDT)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 E47D3128C81 for <idr@ietf.org>; Mon, 10 Apr 2017 09:10:23 -0700 (PDT)
Received: by mail-pf0-x243.google.com with SMTP id a188so1385904pfa.2 for <idr@ietf.org>; Mon, 10 Apr 2017 09:10:23 -0700 (PDT)
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; bh=imloXI8B+N/ih08fSjZSR7Wug7Krd0hFzOlNQZivIsc=; b=Lgqu5kdpT3DwdTdjMX7wnAhzC6XmqwSMvJuCGL9raOLsa27flsl9+IQ6FW7EFXtbds /zgrpDeUgFx+Usfn1e3wM10HfXxky1vmG+LBILFM7hfeHCSmFPiQCggQtMQ9CczEmZvz jTum3iNY/RaND83Kz1T18sRhb2CWY7d/kaAHL5bWfaP5ERDyMlGJfQT3B4NInBGpm00U BCCYoJGYifB9N4DaNmVhB9sa5knXn6XqTggRz86kiGmgaO5Hc4wbt9nJBIvHj2Vbp9lk W84M7qobYiwVNOJ8i4+s/r0XOH5jFWmVjgBtKOH1Kgy8RFXeUgoLqRO/yXQlTbKOST50 5EYw==
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; bh=imloXI8B+N/ih08fSjZSR7Wug7Krd0hFzOlNQZivIsc=; b=HOfTxHq5Lqhtn8VLyBtZUNDieZmwuXpu57FOj5Gi9UIvp4uStIntorjlfLh415ek5i 6ZAK94rjPGLrU16yQPVfGHb0ZBK9PRM6qIxc7Rg5t4KPlQfVWoPLY0qBYJzEkrsWy90k lqAdInZKmqshwm3Z5VD7AzQbcYsijBKA0jRvrzPpIFdDD7AuWxDDgFcm9H6sMy6ZMbUZ K1QPFUjHFo77JAayoUZ/jlz9IN7Tu2k39Zq6+KjRHBSmSqgz+4RMG0Mr8wBCMd8GIXna Uu9hliFujnCpCmUe58LkZgdF3olaUkY2PUhJsomKYf5BErfWFwESk0ta/pd8yzryutmw q9Qg==
X-Gm-Message-State: AFeK/H3IxFynOQck9dRl96p/emAFmHJYrxDOMXXVvtDLCmhwLBxLAbAgkzG+ypYewBG46g==
X-Received: by 10.98.11.218 with SMTP id 87mr54124530pfl.214.1491840623419; Mon, 10 Apr 2017 09:10:23 -0700 (PDT)
Received: from [192.168.255.106] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id q7sm20694659pfj.24.2017.04.10.09.10.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 09:10:22 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.20.0.170309
Date: Mon, 10 Apr 2017 09:10:37 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: "Ketan Talaulikar Talaulikar (ketant)" <ketant@cisco.com>, Robert Raszuk <robert@raszuk.net>
CC: idr wg <idr@ietf.org>, "Van De Velde, Gunter (Nokia - BE)" <gunter.van_de_velde@nokia.com>
Message-ID: <92EB3AA9-005F-4502-B5BD-CF05A40A7867@gmail.com>
Thread-Topic: [Idr] FW: New Version Notification for draft-vandevelde-idr-bgp-ls-segment-routing-rld-01.txt
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> <19BCC3A8-48A7-4838-A999-5B304C0C7EED@gmail.com> <de730d8327314fa6bfa375c76c8fd116@XCH-ALN-008.cisco.com>
In-Reply-To: <de730d8327314fa6bfa375c76c8fd116@XCH-ALN-008.cisco.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3574660238_965366943"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/fFxlSW4lFQqY70mHujYv5YaH260>
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.22
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: Mon, 10 Apr 2017 16:10:29 -0000

Hi Ketan,

 

During my presentation in Chicago I have asked for adoption, I assume they would do so soon.

Wrt email topic – please do not mix MSD documents with RLD ones.

 

Thanks!

 

Cheers,

Jeff

 

 

From: "Ketan Talaulikar Talaulikar (ketant)" <ketant@cisco.com>
Date: Monday, April 10, 2017 at 08:30
To: Jeff Tantsura <jefftant.ietf@gmail.com>om>, "robert@raszuk.net" <robert@raszuk.net>
Cc: idr wg <idr@ietf.org>rg>, "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

 

Hi Jeff/Authors,

 

Could we get this MSD BGP-LS draft polled for IDR WG adoption? The corresponding IGP drafts are already respective WG documents.

 

Thanks,

Ketan

 

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Jeff Tantsura
Sent: 04 March 2017 16:21
To: Robert Raszuk <robert@raszuk.net>
Cc: idr wg <idr@ietf.org>rg>; 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

 

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