[Lsr] A question about Mirror SID and its advertisement using IS-IS

Alexander Vainshtein <Alexander.Vainshtein@ecitele.com> Tue, 19 June 2018 14:27 UTC

Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96EC6131144; Tue, 19 Jun 2018 07:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level:
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZBDZu10T-nxh; Tue, 19 Jun 2018 07:27:41 -0700 (PDT)
Received: from mail1.bemta26.messagelabs.com (mail1.bemta26.messagelabs.com [85.158.142.2]) (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 989B513113A; Tue, 19 Jun 2018 07:27:37 -0700 (PDT)
Received: from [85.158.142.103] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) by server-2.bemta.az-a.eu-central-1.aws.symcld.net id 69/AB-01518-8D2192B5; Tue, 19 Jun 2018 14:27:36 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA1WSfUhTURjGPfdu8ybOrjPzbWnkKsp0a8OCISn +FUkGUf+ElnrVmxvOq2wTl6aYgUQa+Fl+kgsp04JSE/tWo/yoNIzKNEtxZU4qs09Zavd6tOz+ cfnxPg/Pec7hpUjZM4mcYi1m1sgxBoXERbTd79dG5UuZX6T6XaGvdqj6vEjbZasTazufOlAou bu2dobYhyLEei422RIj1jXe+uGcMnkSWWYcuWQ2ep1xCq2gRPR5EsrmMgWW0aUEtNhcMI8huN oUIrCEDobGhmGJwKtoC1jvO5DAJJ0FA9f6CIE96F1wZa7CGXv2QMn3rkVWQdtwO4HP2gR26+R CjpSOgTvNdxdyEL0afvZcJnCmFwzazi0w0DTU3u4jMXvCxNicGPtj4e07K8JzXyh7U+WM2Qf6 z+XxcxeeWwjoKh4XY0EDnZfu8UEUz3vh25lQjBug+cNhbH+CYPz9lATbA+BVU98iJ0PO74bFD plQNN8iwrwO6k+PLvI9EnLb0nCmN9RcCMWZdRKYK7gtxu8ZB11VX0VYcBAwMFhMFiD/imV3xs xB/dgJsmLhjdyhu9wmwvMAqLk1LcHsDxesk+QSP24bI5bPa5BzPdLGGvUJOnMSozcoNWq1UqM JVKqVWrWKSVcyKjZVGcdyZiPDiyomzaQyHU2KM8SrONbciPjVcuK/VpRfxXagNRSh8JROtG6J lLnFJscf1TEmXbQx1cCaOpA3RSlAyrn7RcrcjWwCazmiN/D7uSQD5apYJU0TZKkphUky6ROw1 IMCqY7PJfkk1Sv8ZSIumWPlXtIpwUoLVl0q9zdoadf7kY/cQ4r4ajLXFNaYpDf/r9uRF4UUHt IwIcVVz5n/nmfnqxB8leb0zUIVM/NPkmejkYjOfaV1s8HpeYlFZ0c/zQ6OHAtae2CcqwnbWZX jp2kIeVH08PrQtbLCj/agQz7oU3hvv+p4kNcvf7cblSunL2bZ1mewHjucZrod+zvcbz6aZyZy hqrL6c6AglL7eHRioVEbsG1mjXxwCqUXf3mgbD1UcPBbZW94VKq1OCSq3f5cITLpGM1W0mhi/ gA9BCcQ5gMAAA==
X-Env-Sender: Alexander.Vainshtein@ecitele.com
X-Msg-Ref: server-12.tower-228.messagelabs.com!1529418452!2463985!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 3434 invoked from network); 19 Jun 2018 14:27:34 -0000
Received: from us-west-2a.mta.dlp.protect.symantec.com (HELO EUR01-DB5-obe.outbound.protection.outlook.com) (52.41.248.36) by server-12.tower-228.messagelabs.com with AES256-SHA256 encrypted SMTP; 19 Jun 2018 14:27:34 -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=mZ5K2Y7erlg3rVM7/EQ/hrGvsJclwkHo7aHdYopjkvk=; b=RB6So+qCZeanJjDBeVkozxchkWbNgqa5xM7/iYKhNGgo6RJpsZKVBtUDDgN7WNY2Wr9OTFkv4PTySA8Pfd8BmZvQH97PLoiedBxnyTMx9PTytndhN/hN3sAUtTpSNnLLYyjzyXfm3oNOdu0GH7nAT2V6mfShoyAoiGhRRKfFRlw=
Received: from DB5PR0301MB1909.eurprd03.prod.outlook.com (10.167.226.155) by DB5PR0301MB2071.eurprd03.prod.outlook.com (10.167.227.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.863.14; Tue, 19 Jun 2018 14:27:29 +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.0863.016; Tue, 19 Jun 2018 14:27:29 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "draft-ietf-isis-segment-routing-extensions.all@ietf.org" <draft-ietf-isis-segment-routing-extensions.all@ietf.org>
CC: Michael Gorokhovsky <Michael.Gorokhovsky@ecitele.com>, "spring@ietf.org" <spring@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: A question about Mirror SID and its advertisement using IS-IS
Thread-Index: AdQH14DTIRv7S0/NS+eaMKnMz1F/Kg==
Date: Tue, 19 Jun 2018 14:27:29 +0000
Message-ID: <DB5PR0301MB1909570F9D2830F933FD1B3D9D700@DB5PR0301MB1909.eurprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.234.241.1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB5PR0301MB2071; 7:bfAjfYlGgTeLOfI4U5H/VZtJPORxtxfDyJtQo160Xrc0B4RkulON0l9nxrwSw1RFo5ukychDKkNBECQ/qd3bmHMV8ga1GgT8/r8jV7crW+R5B4MuzbGRoK66Dutf+eBBvExu3cvZWht6cnol+PFQGPjz9IeMrNUsY3jUlqV6wF86Hlh7aXPQxqAIMm/JIfLyMS9H7faE27WuN6mxnVsi48Z20TRLXUrmnw35/4QiSr9Ov/isI2w1ftLyOYkaBYBp
x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR;
x-ms-office365-filtering-correlation-id: fc57b483-f2aa-4081-7cb2-08d5d5f0c97f
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(711020)(48565401081)(2017052603328)(7153060)(7193020); SRVR:DB5PR0301MB2071;
x-ms-traffictypediagnostic: DB5PR0301MB2071:
x-microsoft-antispam-prvs: <DB5PR0301MB2071A12968E41F59B7722D6E9D700@DB5PR0301MB2071.eurprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(120809045254105)(21748063052155)(279101305709854);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3231254)(944501410)(52105095)(3002001)(6055026)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:DB5PR0301MB2071; BCL:0; PCL:0; RULEID:; SRVR:DB5PR0301MB2071;
x-forefront-prvs: 07083FF734
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39380400002)(39860400002)(396003)(346002)(376002)(53754006)(252514010)(51874003)(189003)(199004)(2351001)(236005)(8936002)(53936002)(606006)(81156014)(81166006)(33656002)(8676002)(7736002)(6916009)(5660300001)(66066001)(25786009)(97736004)(3846002)(74316002)(6116002)(72206003)(790700001)(14454004)(2900100001)(4326008)(105586002)(9686003)(54896002)(6306002)(106356001)(478600001)(186003)(5630700001)(26005)(486006)(54906003)(6436002)(450100002)(2501003)(86362001)(5250100002)(7696005)(99286004)(476003)(5640700003)(6506007)(59450400001)(68736007)(102836004)(2906002)(3280700002)(316002)(55016002)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR0301MB2071; 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: EZF/7x5Xhfba3porBCrB3vvUrQmPh/ObTjyEhD4ftmQ4FqwE014YwLvxm6T/dCNScEtu+Li9H5Wu+kePztLwUZ+7Vue9qK7LxDca0ba5nFtXbIzo2onY1p2X2SiX8IMfM/WX/mQAHK0NjxDnHSKYmvU92WHPyMBCgHqbmU9W7SXMmoP15FS8eGnbSJvGGqUIaEbC+QUsSCUS+xO62ZUJFVnUJ5U96vQOwdEL+7ZYOwYrKh5O0V372UNnRTIwbxdAcevxhXsDMbHG4Y4/7cCHflyyU8aoCmbL/Q2SxEjQbYht6pM0t8M3A/DKPFzpuT0fFI0vI6jRv2WyJapPh1HADg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DB5PR0301MB1909570F9D2830F933FD1B3D9D700DB5PR0301MB1909_"
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-MS-Exchange-CrossTenant-Network-Message-Id: fc57b483-f2aa-4081-7cb2-08d5d5f0c97f
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jun 2018 14:27:29.1215 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 2c514a61-08de-4519-b4c0-921fef62c42a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR0301MB2071
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/9yhDauXGbqCqFdGJdD-Fjld2p9s>
Subject: [Lsr] A question about Mirror SID and its advertisement using IS-IS
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Jun 2018 14:27:45 -0000

Hi all,
I have a question about Mirror SID as defined in the SR Architecture<https://tools.ietf.org/html/draft-ietf-spring-segment-routing-15> draft and its advertisement defined in the IS-IS extensions for SR<https://datatracker.ietf.org/doc/draft-ietf-isis-segment-routing-extensions/> draft.

Mirror SID is defined in Section 5.1 of the SR Architecture draft as following:
5.1<https://tools.ietf.org/html/draft-ietf-spring-segment-routing-15#section-5.1>.1>.  IGP Mirroring Context Segment


   One use case for a Binding Segment is to provide support for an IGP
   node to advertise its ability to process traffic originally destined
   to another IGP node, called the Mirrored node and identified by an IP
   address or a Node-SID, provided that a "Mirroring Context" segment be
   inserted in the segment list prior to any service segment local to
   the mirrored node.

   When a given node B wants to provide egress node A protection, it

   advertises a segment identifying node's A context.  Such segment is

   called "Mirror Context Segment" and identified by the Mirror SID.



   The Mirror SID is advertised using the binding segment defined in SR

   IGP protocol extensions [I-D.ietf-isis-segment-routing-extensions<https://tools.ietf.org/html/draft-ietf-spring-segment-routing-15#ref-I-D.ietf-isis-segment-routing-extensions>] .



   In the event of a failure, a point of local repair (PLR) diverting

   traffic from A to B does a PUSH of the Mirror SID on the protected

   traffic.  B, when receiving the traffic with the Mirror SID as the

   active segment, uses that segment and processes underlying segments

   in the context of A.

Please note that these definitions do not mention SR Mapping Server or any such thing.

At the same time, the IS-IS Extensions for SR draft only mentions mirror context in Section 2.4 that says:

2.4<https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-17#section-2.4>.4>.  SID/Label Binding TLV





   The SID/Label Binding TLV MAY be originated by any router in an IS-IS

   domain.



   The SID/Label Binding TLV is used to advertise prefixes to SID/Label

   mappings.  This functionality is called the Segment Routing Mapping

   Server (SRMS).  The behavior of the SRMS is defined in

   [I-D.ietf-spring-segment-routing-ldp-interop<https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-17#ref-I-D.ietf-spring-segment-routing-ldp-interop>]p>].
...
2.4.1<https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-17#section-2.4.1>.1>.  Flags





   Flags: 1 octet field of following flags:



    0 1 2 3 4 5 6 7

   +-+-+-+-+-+-+-+-+

   |F|M|S|D|A|     |

   +-+-+-+-+-+-+-+-+



   where:



      F-Flag: Address Family flag.  If unset, then the Prefix carries an

      IPv4 Prefix.  If set then the Prefix carries an IPv6 Prefix.



      M-Flag: Mirror Context flag.  Set if the advertised SID

      corresponds to a mirrored context.  The use of the M flag is

      described in [I-D.ietf-spring-segment-routing<https://tools.ietf.org/html/draft-ietf-isis-segment-routing-extensions-17#ref-I-D.ietf-spring-segment-routing>]g>].

...

This seems to imply that mirrored context is related to the SRMS - but, to the best of my understanding, these are completely unrelated.
Please note also that the SR Architecture draft says that the Mirroring Context SID is a segment that identifies the node, and not any prefix. And, of course the SR Architecture draft does not describe usage of any flags.

What (if anything) did I miss?

Regards, and lots of thanks in advance,
Sasha

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


___________________________________________________________________________

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.
___________________________________________________________________________