Re: [spring] Updating the SPRING WG Charter

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Sat, 09 June 2018 18:54 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12446130F5F for <spring@ietfa.amsl.com>; Sat, 9 Jun 2018 11:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.684
X-Spam-Level:
X-Spam-Status: No, score=-0.684 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.795, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=eci365.onmicrosoft.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 gSmwdY4Y1O6R for <spring@ietfa.amsl.com>; Sat, 9 Jun 2018 11:54:09 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 109D0130F63 for <spring@ietf.org>; Sat, 9 Jun 2018 11:54:08 -0700 (PDT)
Received: from [85.158.142.193] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-4.bemta.az-b.eu-central-1.aws.symcld.net id 58/C3-16868-D422C1B5; Sat, 09 Jun 2018 18:54:05 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHLsWRWlGSWpSXmKPExsViovlDRddHSSb a4MpVTYsN70Qs1m34wGzx98FsJovWHZ+ZLZoWNjFbHF6fY3H8wm9Gi6/7FjFavN7xld2B02PN z3dMHlN+b2T1OLHsCqtHy5G3rB5Llvxk8rjedJXdo3XHX3aP3RsXMAVwRLFm5iXlVySwZjze+ Yu9YMIhxooJjYoNjAf2M3YxcnGwCCxilpj3cxsriCMkMJlJYv7ObijnEaPEra23WboYOTnYBG wlNq2+ywZiiwioSnSeeMQMUsQscJRJ4l//DlaQhLCAicSG7beZIYpMJb6eWsACYU9jlNj6wgT EZhFQkWj9sYYJxOYVSJCYM/Ul1LafHBJdBxrYQRKcAoES/VvmgQ1iFBCT+H4KooFZQFzi1pP5 YLaEgIDEkj3nmSFsUYmXj/+xQtQnSdx/uhDoOQ6guIJE198siBJZiUvzu8F+lhDYxiQxb+Nrd oiErsSHqVOZIeqVJba8iIWoOcoosWfidhaIGh2JC6s+skHY+RI7OmZCDdrLKHF+0w2oIjmJVb 0PWSAS+5klJt3eDHWpjMTGhklMEInDbBITFywGGyUkkCxxYs5nlgmMurOQfDcL6BJmgTyJxXd NZ4FDSVDi5MwnLBBhTYn1u/QhqhUlpnQ/ZIewNSRa58xlRxZfwMi+itEyqSgzPaMkNzEzR9fQ wEDX0NBY11zXyMRYL7FKN0kvtVQ3OTWvpCgRKKuXWF6sV1yZm5yTopeXWrKJEZg+GYBgB2Pjn 5RDjJIcTEqivCfOS0YL8SXlp1RmJBZnxBeV5qQWH2KU4eBQkuANUpSJFhIsSk1PrUjLzAEmcp i0BAePkgivJEiat7ggMbc4Mx0idYrRkuPQ+yk9zBznwOSTy9N6mIVY8vLzUqXEea1AGgRAGjJ K8+DGwbLNJUZZKWFeRqADhXgKUotyM0tQ5V8xinMwKgnz6oJM4cnMK4Hb+groICaggzyYJUEO KklESEk1MGoXeU28mu4WMZFtM0NP3+zoKyvjpO5w2GzkWvX762l3nZWZ/0/N+DWr0bns2pIt8 X8WzDpiNJGd7c0vZ/GG5fGT5aV+ed7zeK7+cr/Vw58dlstm5DUzs1/abi+y+uuSon3WCukG27 um9mgaaj978WJ957kZPn+VNRt89A42NauXZas9ONmwIF2JpTgj0VCLuag4EQCqHkYEMQQAAA= =
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-34.tower-238.messagelabs.com!1528570439!1351949!1
X-Originating-IP: [52.41.248.36]
X-SYMC-ESS-Client-Auth: mailfrom-relay-check=pass
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=ecitele.com,-,-
X-VirusChecked: Checked
Received: (qmail 30110 invoked from network); 9 Jun 2018 18:54:02 -0000
Received: from us-west-2a.mta.dlp.protect.symantec.com (HELO EUR02-AM5-obe.outbound.protection.outlook.com) (52.41.248.36) by server-34.tower-238.messagelabs.com with AES256-SHA256 encrypted SMTP; 9 Jun 2018 18:54:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ECI365.onmicrosoft.com; s=selector1-ecitele-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=76ngIOQXTZLZlxbgRsFl0/+iZw07cSYKzFfx4KogvQk=; b=gvuc6Ve1ZCOWOQ/jrNMmamaw1l/H38X3ojFer5WMCrFLmJqppEdeNjYgLveihLzJd35Q870x2CmU1fF7svR+W0xojh6RWk6Ka5zP1kz3Dli5xb/EUWhA3zwfqN75g31CJOVdzL/9XmBQpxqjHMsDfl51+BaUcUX8tizNRaIcrR8=
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com (10.167.226.155) by DB5PR0301MB1960.eurprd03.prod.outlook.com (10.167.227.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.841.15; Sat, 9 Jun 2018 18:53:55 +0000
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::d461:c56e:7404:d5b1]) by DB5PR0301MB1909.eurprd03.prod.outlook.com ([fe80::d461:c56e:7404:d5b1%6]) with mapi id 15.20.0841.011; Sat, 9 Jun 2018 18:53:54 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Robert Raszuk <robert@raszuk.net>
CC: Paul Mattes <pamattes@microsoft.com>, "spring@ietf.org" <spring@ietf.org>, Xiejingrong <xiejingrong@huawei.com>, Michael McBride <michael.mcbride@huawei.com>, Rob Shakir <robjs=40google.com@dmarc.ietf.org>, "Zafar Ali (zali)" <zali@cisco.com>, Eric C Rosen <erosen@juniper.net>, "Voyer, Daniel" <daniel.voyer@bell.ca>
Thread-Topic: [spring] Updating the SPRING WG Charter
Thread-Index: AdP56p5QOgEqtjT0TPyaFDKrNzAuwABwo3NQABxnJIAAAQilgAAAHQ8AAGnMDQAAAkvagAAmSjeQAACmgwAAAgRUgAAAZ0QAAC91rRAAAI5xgAAIcROAAALRWboAAMXMAAAtzpkg
Date: Sat, 09 Jun 2018 18:53:54 +0000
Message-ID: <DB5PR0301MB1909DA951760E8B7A6477EF09D7A0@DB5PR0301MB1909.eurprd03.prod.outlook.com>
References: <8CCB28152EA2E14A96BBEDC15823481A1CB79F12@sjceml521-mbs.china.huawei.com> <16253F7987E4F346823E305D08F9115A99A7D4CE@nkgeml514-mbx.china.huawei.com> <CAHd-QWvx-tkP1Asx3PwM3p2=wjuJm7b=A4Hb-BUnCMRzwT1J8w@mail.gmail.com> <8CCB28152EA2E14A96BBEDC15823481A1CB7FBFE@sjceml521-mbs.china.huawei.com> <CAHd-QWu+184A3Nje_Bmki9A3wwpp=4YyyKTTkWBtLcf_gt7Lvg@mail.gmail.com> <75252B5F-6BCB-4166-ACC1-C9E9697B7B68@cisco.com> <CA802BB9-00E2-4DA4-B7F2-B0ECB5DBD8FD@bell.ca> <DB5PR0301MB1909A63446648764B90DA47D9D640@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ERnV1f9LoPUn0N7f5yHS4BWmHRKfdyF62tin2eSXOpx_yw@mail.gmail.com> <a57dfef6-40c6-eece-7c9a-2517fc0c5d16@juniper.net> <CA+b+ER=UknPNDweStHDXvbsuqkL2+r5=5zzS4ujAredew_F_vQ@mail.gmail.com> <DB5PR0301MB19094268D61209CFB345DE609D7B0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ER=WX6WOxM7BhiysZxY39dNYYAHwT2hemR-tD+PLGi+KiQ@mail.gmail.com> <DM5PR21MB018696A5159598D791C30830CA7B0@DM5PR21MB0186.namprd21.prod.outlook.com> <DB5PR0301MB19091032724ED7EDC11F63659D7B0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ERmzd1SjX4VqONwQGcUuD7rjuzx1zXb1nE3AyHWErBhMRw@mail.gmail.com>
In-Reply-To: <CA+b+ERmzd1SjX4VqONwQGcUuD7rjuzx1zXb1nE3AyHWErBhMRw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [109.66.10.10]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB5PR0301MB1960; 7:XMyKyET2exBw+tVnN4dzJ8LtBazGBonSShRtxTdAyYNy+6JvoWYynU/cmMUwU/9QtmXlO2LN8UiaUGqSPRLcGaf1pOuBBERCiWdEdvxXGKRKJLZNCJFjwF9h+L8uaJ8S0UosOsBB9SuUrbIiB/RDbec8dagnP8itada/A7llBcyJeMplcAEX+E+hX92zSpJqiTlFC2izrA7nWIixvAmM/ZzFSSeHHDZawrCej6W9x9BwavxZm9jB6ms4MBzYvxvQ
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(48565401081)(2017052603328)(7153060)(7193020); SRVR:DB5PR0301MB1960;
x-ms-traffictypediagnostic: DB5PR0301MB1960:
x-microsoft-antispam-prvs: <DB5PR0301MB19602CDBE4D51162055BDD139D7A0@DB5PR0301MB1960.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(226690903318834)(89211679590171)(50582790962513)(85827821059158)(95692535739014)(21748063052155)(279101305709854)(138986009662008);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123560045)(20161123564045)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:DB5PR0301MB1960; BCL:0; PCL:0; RULEID:; SRVR:DB5PR0301MB1960;
x-forefront-prvs: 06989017E3
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(39850400004)(366004)(376002)(396003)(346002)(189003)(51444003)(199004)(252514010)(3280700002)(606006)(66066001)(76176011)(25786009)(8676002)(81156014)(5660300001)(7736002)(54896002)(81166006)(93886005)(4326008)(19609705001)(6306002)(6916009)(8936002)(5250100002)(6506007)(33656002)(7696005)(9686003)(236005)(229853002)(53936002)(97736004)(55016002)(74316002)(8666007)(6436002)(86362001)(68736007)(2900100001)(486006)(106356001)(2906002)(105586002)(3660700001)(14454004)(102836004)(6116002)(790700001)(3846002)(45080400002)(54906003)(26005)(476003)(6246003)(316002)(99286004)(53546011)(446003)(72206003)(186003)(478600001)(11346002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR0301MB1960; H:DB5PR0301MB1909.eurprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: ecitele.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: KH6txyYjTd9hZhv+7feChXvBxLoWCQNoKUCeKEkREGTytN5XNV/U7lUfxEtxyf2ycidtyZRX3WJ+kmheliJl0h2Uu+3X/3YBHtrOB6td0f4jThjYj2zYz3yySW2VD66X2wVCVy3iWi3D8szzOKAvNoAeMEz15Nscme0eyvY96alX7+ZL0EGDxSuoCc77uBdO
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB1909DA951760E8B7A6477EF09D7A0DB5PR0301MB1909_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 1a15588a-0234-486e-6ecf-08d5ce3a5990
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1a15588a-0234-486e-6ecf-08d5ce3a5990
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jun 2018 18:53:54.7965 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR0301MB1960
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/Y_zh_pEka5BwnZQr_57Mt2d9_ak>
Subject: Re: [spring] Updating the SPRING WG Charter
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2018 18:54:13 -0000

Robert,
I think that you have cut the quoted text from the Segment Routing Architecture<https://tools.ietf.org/html/draft-ietf-spring-segment-routing-15> draft a bit too short. The complete fragment says:

   Where possible, it is recommended that identical SRGBs be configured
   on all nodes in an SR Domain.  This simplifies troubleshooting as the
   same label will be associated with the same prefix on all nodes.  In
   addition, it simplifies support for anycast as detailed in
   Section 3.3<https://tools.ietf.org/html/draft-ietf-spring-segment-routing-15#section-3.3>.

In other words,  the Segment Routing Architecture draft:

-          Does not consider identical SRGBs on all nodes in an SR domain as a requirement.

-          Explains that such configuration, if used, simplifies troubleshooting and support of anycast segments. With regard to the latter, please note that the Anycast Segments<https://tools.ietf.org/html/draft-ietf-spring-mpls-anycast-segments-02> draft defines a mechanism that facilitates usage of anycast segments in an environment with different SRGBs on different nodes.


Therefore, from my POV, domain-wide labels have been purged (for quite some time now) from the SR-MPLS architecture. I do not think that they should be re-introduced.

My 2c,
Sasha

Office: +972-39266302
Cell:      +972-549266302
Email:   Alexander.Vainshtein@ecitele.com

From: rraszuk@gmail.com [mailto:rraszuk@gmail.com] On Behalf Of Robert Raszuk
Sent: Friday, June 8, 2018 11:44 PM
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Cc: Paul Mattes <pamattes@microsoft.com>; spring@ietf.org; Xiejingrong <xiejingrong@huawei.com>; Michael McBride <michael.mcbride@huawei.com>; Rob Shakir <robjs=40google.com@dmarc.ietf.org>; Zafar Ali (zali) <zali@cisco.com>; Eric C Rosen <erosen@juniper.net>; Voyer, Daniel <daniel.voyer@bell.ca>
Subject: Re: [spring] Updating the SPRING WG Charter

Folks,

The only reason why SR-MPLS architecture is using indexes as opposed to domain wide labels is a claim from few folks that possibly in some networks deployed platforms would not be able to use the same global label block for SR.

So SR-MPLS architecture agreed to use index to offset possible per platform label block.

That said number of real deployment do use global (domain wide) identical block on all nodes and that is the actual recommendation from section 3.1.2 of SR architecture

"Where possible, it is recommended that identical SRGBs be configured on all nodes in an SR Domain."

But none of this really matters for the discussion at hand. Embedding instruction for specific function can be easily done within programmed domain wide index offset.

Best,
R.


On Fri, Jun 8, 2018 at 10:21 PM, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com<mailto:Alexander.Vainshtein@ecitele.com>> wrote:
Robert, Paul and all,
I concur with Paul.
Domain-wide labels have been successfully purged from SR-MPLS for quite some time now, and, from my POV this purge is irreversible now.
My 2c.
Thumb typed by Sasha Vainshtein



___________________________________________________________________________

This e-mail message is intended for the recipient only and contains information which is 
CONFIDENTIAL and which may be proprietary to ECI Telecom. If you have received this 
transmission in error, please inform us by e-mail, phone or fax, and then delete the original 
and all copies thereof.
___________________________________________________________________________