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

Gunter Van De Velde <guntervandeveldecc@icloud.com> Sat, 04 March 2017 10:01 UTC

Return-Path: <guntervandeveldecc@icloud.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 F0D511294DD for <idr@ietfa.amsl.com>; Sat, 4 Mar 2017 02:01:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.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 ge-wJoH565mu for <idr@ietfa.amsl.com>; Sat, 4 Mar 2017 02:01:39 -0800 (PST)
Received: from st13p11im-asmtp004.me.com (st13p11im-asmtp004.me.com [17.164.40.219]) (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 E8371129469 for <idr@ietf.org>; Sat, 4 Mar 2017 02:01:38 -0800 (PST)
Received: from process-dkim-sign-daemon.st13p11im-asmtp004.me.com by st13p11im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OMA00B00BQ31S00@st13p11im-asmtp004.me.com> for idr@ietf.org; Sat, 04 Mar 2017 10:01:38 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=4d515a; t=1488621698; bh=pAVLl3tOKhnPnhloq6xlXxbK7VZ9ssBmyrzCzGFEsPI=; h=From:Message-id:Content-type:MIME-version:Subject:Date:To; b=krLpOmOV+iR4caqhUtOgxK/UkcyEuQw2wHLT6mGBAyWT3UgfPFtUO23APBqf1o85r L0YsK7qyAb/bpVLV42uGLrnsX1lDpLf5uxAwqhJiXExuuUrMTD+wQoo4gUZUCHpgBK zUO8orNHetsuAg6jj/JjoflCKiD/pLn/sEZt48GR+nN2KCg8PQl4/filNdGb+iuOzD vSZoKii96Zxi4HDOllVahVEdEv1j1aUQ6uzaQN6G4Aq1V/3pJFMtUIXk3r6OjMU/Lb 7jGvPr8PTP0ztQ9tXRUndh+zTpqArV568cKpasSKohQmQrdTvt56IJ8cT6JOrMKaSL 9DlCINDkxC+5w==
Received: from icloud.com ([127.0.0.1]) by st13p11im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OMA008Z0BUM1K20@st13p11im-asmtp004.me.com>; Sat, 04 Mar 2017 10:01:37 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-04_04:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1703040077
From: Gunter Van De Velde <guntervandeveldecc@icloud.com>
Message-id: <A414191A-98F3-49B5-9722-B41426A2D061@icloud.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_FDDA7015-D85E-46EF-ADC9-51E7749FA503"
MIME-version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Sat, 04 Mar 2017 11:01:33 +0100
In-reply-to: <CA+b+ER=sT-jnZM+sR5tQKYcyEzSzPXNHMk-GfkxjCGJaykgh2A@mail.gmail.com>
To: Robert Raszuk <robert@raszuk.net>
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+ER=sT-jnZM+sR5tQKYcyEzSzPXNHMk-GfkxjCGJaykgh2A@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/S0ymyFJ2N1U4orncuXDkTrEBCzs>
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: Sat, 04 Mar 2017 10:01:41 -0000

When i was looking the MSD draft is looking at “How Many labels can device (node/link) impose”.
(look at introduction in section 1 as it is explicitly written in the text)

The RLD draft is about “How many labels a device (node/link) can read”

Even for the IGPs there is are different documents in either OSPF or ISIS WG:
OSPF MSD: https://tools.ietf.org/html/draft-ietf-ospf-segment-routing-msd-00 <https://tools.ietf.org/html/draft-ietf-ospf-segment-routing-msd-00>
OSPF ELC/RLD: https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-04 <https://tools.ietf.org/html/draft-ietf-ospf-mpls-elc-04>

ISIS MSD: https://tools.ietf.org/html/draft-ietf-isis-segment-routing-msd-02 <https://tools.ietf.org/html/draft-ietf-isis-segment-routing-msd-02>
ISIS ELC/RLD: https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-02 <https://tools.ietf.org/html/draft-ietf-isis-mpls-elc-02>

BGP MSD: https://tools.ietf.org/html/draft-tantsura-bgp-ls-segment-routing-msd-02 <https://tools.ietf.org/html/draft-tantsura-bgp-ls-segment-routing-msd-02>
BGP ELC/RLD: Was MIA … so now there is https://trac.tools.ietf.org/html/draft-vandevelde-idr-bgp-ls-segment-routing-rld-01 <https://trac.tools.ietf.org/html/draft-vandevelde-idr-bgp-ls-segment-routing-rld-01>

Hence i assumed that there is sense for two drafts in IDR to be in sync with the IGP capabilities … one to make BGP-LS in alignment with the IGPs for MSD and one to make BGP-LS in alignment with ELC

@Robert, I do believe those data-points are of interrest to a network SDN controller. I am not convinced they all belong in the same document.
I think that on shorter term there is need that the IGP LSDB can be exported to BGP-LS because right now that is not possible for ISIS-ELC or OSPF-ELC. 
My understanding is it is potentially worth having a draft on signalling new functionality beyond the capability to signal it in the IGPs… It is an important deviation from anything that was done before with BGP-LS because main purpose has been to allow the export of IGP LSDB into BGP-LS

G/






> On 4 Mar 2017, at 09:54, Robert Raszuk <robert@raszuk.net> wrote:
> 
> Jeff,
> 
> I am talking about max supported depth.
> 
> If this is already addressed elsewhere (which I doubt) I am not sure why this draft would be needed at all then.
> 
> But if it has value let's make it complete.
> 
> Best,
> R.
> 
> On Mar 4, 2017 09:41, "Jeff Tantsura" <jefftant.ietf@gmail.com <mailto: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 <mailto: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 <mailto: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 <mailto:internet-drafts@ietf.org>" <internet-drafts@ietf.org <mailto: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 <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/ <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 <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 <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 <http://tools.ietf.org/>.
> 
>     The IETF Secretariat
> 
> 
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org <mailto:Idr@ietf.org>
> https://www.ietf.org/mailman/listinfo/idr <https://www.ietf.org/mailman/listinfo/idr>
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org <mailto:Idr@ietf.org>
> https://www.ietf.org/mailman/listinfo/idr <https://www.ietf.org/mailman/listinfo/idr>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr