Re: [spring] draft-ietf-spring-sr-yang: question about absolute SIDs

"Acee Lindem (acee)" <acee@cisco.com> Fri, 13 September 2019 15:59 UTC

Return-Path: <acee@cisco.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 7927F120073; Fri, 13 Sep 2019 08:59:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=aidv6wYa; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=cEZgeEdK
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 UzE_V0LfWJSF; Fri, 13 Sep 2019 08:59:21 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7C5E12001E; Fri, 13 Sep 2019 08:59:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11327; q=dns/txt; s=iport; t=1568390360; x=1569599960; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=VsQMM5VeD4ZqtAP0FQOI/TNYeOBUPY4doUHwAf/04UI=; b=aidv6wYaK8B8fXNIR/4Z2fT2lUE+Hsji8VrtYSc9OvQoQsaDOQOf6Gt2 hGYZsTFAtpvBwn8XLfwNUjyd3hyKf7sF6lc33IvywW0n6bGks+qDW53Fb jOKI7igQZyhwlTz/qHSw+bnvYQ0ZxaWkXBflDIh8R+N4NgNhjhwFX3qpy k=;
IronPort-PHdr: 9a23:ZfW8pBzTPs2h1ojXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YRGN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A+GsHbIQKUhYEjcsMmAl1CcWIBGXwLeXhaGoxG8ERHFI=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DiAQApvHtd/4kNJK1mGwEBAQEDAQEBBwMBAQGBZ4EWLyknA21WIAQLKoQhg0cDim+CNyWJZYkvhFyCUgNUCQEBAQwBAS0CAQGEPwIXgkkjOBMCAwkBAQQBAQECAQYEbYUuDIVKAQEBAQMSER0BATcBDwIBCBEDAQIrAgICHxEdCAIEAQ0FIoMAAYEdTQMdAQKfXwKBOIhhc4Eygn0BAQWFEQ0LghYJgTSLeBiBf4ERJwwTgkw+ghqCSoJrMoImjDyDBIUhlylBCoIhkHeEABuNA4wHjX+KCo5kAgQCBAUCDgEBBYFpIYFYcBVlAYJBgkIMF4EEAQiCQopTc4Epjn8BAQ
X-IronPort-AV: E=Sophos;i="5.64,501,1559520000"; d="scan'208,217";a="627865236"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Sep 2019 15:59:19 +0000
Received: from XCH-ALN-010.cisco.com (xch-aln-010.cisco.com [173.36.7.20]) by alln-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id x8DFxJZJ001736 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 13 Sep 2019 15:59:19 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-010.cisco.com (173.36.7.20) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Sep 2019 10:59:19 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Fri, 13 Sep 2019 10:59:18 -0500
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Fri, 13 Sep 2019 10:59:18 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=X/nEehamnsUUP0Jp9QiVU74v69Gvy4fmjWr3c7VwzdeukEcr7IWMF/JmXv0eOeWQznbVU/zF4to+pjrwXJvOeTzsRDMwIWtaZBm53m3Mm9BC71mRi8jh/9w8FQc9eDODypc4Q5kcqUXCdA/lvWWJMScLsqwWKv0ly2kuH8uPDF1vTld2t/xdzZhga4QAZtQMmq2aduCF/iBEATH/UDhD5yKonHtPTVww1yAC9pHccmT53WODHEc97wOkfj1mw2oAdBMVrXq5gA9Ip5CmMa0kw2RshA6O/T3zXctJkz04vCjjZ8PVkf74vp4fEWTP8Sh373TEeNb5wQ/Z7ZLFEw6aFQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VsQMM5VeD4ZqtAP0FQOI/TNYeOBUPY4doUHwAf/04UI=; b=nyeSkWNzeNaTOiB120ukpFpEnRrCP0o6oVWwTjgLDaHjGGeDEccmbz+6zh0zeq5FCRPowMsduRKXxJcrRN79vsJAAyohiH55PtgLROihMT+2jqnz8kISTKwwCV9I8flRDQtYoBUaBoHblKahHYfq+h4D/HjqsGDpmSMhjxv0CxwUmLJw4yWjgEXsdwJXtsjM5Gd/3TfQpEZjS8b4mqcdUrVbIY+m13fHzOkHrZMtch9Z4bNmnVDotM3OvV+zvFvNTl4BFAKNiJNihLpwEXhn9Mv8HvZYZPNVgMhexd1QIKEuoBncfcoTR4oKJPJqkLACEyCMufevOsQF63FNsRB+WQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VsQMM5VeD4ZqtAP0FQOI/TNYeOBUPY4doUHwAf/04UI=; b=cEZgeEdKZc6pXnmg24i0iNsvbJeh7RM9PY7dsZf25qC+M5BLoMFQK2p9JyNMyVDfrzX+sFAv+sGBpVsbz5t2oJZ0DEwe+GKqqYqc7P1U0TfJ7LJIEje9eqwLFRgy1ur6A6cge1U0wZtxtTSDUJgJTJ737Fv/7PI+K5UqDz6lYzc=
Received: from MN2PR11MB4221.namprd11.prod.outlook.com (52.135.38.14) by MN2PR11MB4511.namprd11.prod.outlook.com (52.135.37.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.20; Fri, 13 Sep 2019 15:59:17 +0000
Received: from MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::cdc1:a2cf:eb3:a420]) by MN2PR11MB4221.namprd11.prod.outlook.com ([fe80::cdc1:a2cf:eb3:a420%6]) with mapi id 15.20.2263.021; Fri, 13 Sep 2019 15:59:17 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Renato Westphal <renato@opensourcerouting.org>, "draft-ietf-spring-sr-yang@ietf.org" <draft-ietf-spring-sr-yang@ietf.org>, "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>
CC: Olivier Dugeon <olivier.dugeon@orange.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: draft-ietf-spring-sr-yang: question about absolute SIDs
Thread-Index: AQHVakZjF2xBDXJzsEWXzjBQHspynKcpgMeA
Date: Fri, 13 Sep 2019 15:59:17 +0000
Message-ID: <FFD7B6D3-E7F2-422F-9478-FE8EC9027220@cisco.com>
References: <CAB6ZmXGh1+R-Uq-Yz_vtjeCaWFXtBx51oL1OywaavuBTFB5yAQ@mail.gmail.com>
In-Reply-To: <CAB6ZmXGh1+R-Uq-Yz_vtjeCaWFXtBx51oL1OywaavuBTFB5yAQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=acee@cisco.com;
x-originating-ip: [2001:420:c0c4:1008::18f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c59d7e56-6acf-4a5d-06aa-08d738635507
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB4511;
x-ms-traffictypediagnostic: MN2PR11MB4511:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB4511341F183CB5AFA44C7627C2B30@MN2PR11MB4511.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0159AC2B97
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(366004)(376002)(39860400002)(51874003)(53754006)(189003)(199004)(14454004)(76176011)(76116006)(478600001)(8936002)(81166006)(71190400001)(2906002)(8676002)(81156014)(25786009)(71200400001)(7736002)(86362001)(66556008)(64756008)(6246003)(66476007)(186003)(6436002)(4326008)(6486002)(66946007)(11346002)(5660300002)(486006)(99286004)(2616005)(36756003)(6512007)(229853002)(66446008)(446003)(2501003)(316002)(46003)(54906003)(53936002)(476003)(256004)(110136005)(33656002)(14444005)(6116002)(6506007)(54896002)(102836004)(53546011)(2201001)(6306002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4511; H:MN2PR11MB4221.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: WtMzIcAdq0UPipHCowaI7qJpF0L9Uq8kGhfNsDKycWpHvx2sS/8zmCyQ5Suo90r0g8ZZHOvWjjIrHvOiaUFPC8zduDvMPCD6pXWem+9I4jo0B9nvwYlJxX/LjGajlOkp+6zOUMKR3WQM9aJqBbjLqy14xe1HqCDpbUVbOEzu53C/b+Puq2Ik6tDq7WfI0Pz8tPFbkvzp3ryPb+/lh5Vstq8kfdgXqr2MoSOf3RWo16QJsnSAALCUd5jpK/MZRYroQH9iL0t7OyTo6gnmydfxeXbA0d0oZDp4Bqzhd7hckM0HpW3aQNYYEiDZsFRH7CMqxkg9TNjHBc+NFat9gzyrpOx97dakE5uS7v59aprELz7/c0k8RUSDP1Reg09fJ67EYM35moIf/wuZkry1sVOCKwcCTXd2I5d5Bd9V8p9Emuk=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_FFD7B6D3E7F2422F9478FE8EC9027220ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c59d7e56-6acf-4a5d-06aa-08d738635507
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Sep 2019 15:59:17.4176 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: KULaI992LIw1fZwwMG1V2s8GQ48Yy8nd1193ReBIXiMIbjh+2XojdO/neIhfx8wG
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4511
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.20, xch-aln-010.cisco.com
X-Outbound-Node: alln-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ef_p8jE0p5U7f-Zl0CY0DS3Dc_A>
Subject: Re: [spring] draft-ietf-spring-sr-yang: question about absolute SIDs
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 13 Sep 2019 15:59:23 -0000

Hi Renato, +SPRING WG,

It is an MPLS label (i.e., your option 2).

Excerpted from RFC 8402:

3.1.2.  SR-MPLS

   When SR is used over the MPLS data plane, SIDs are an MPLS label or
   an index into an MPLS label space (either SRGB or SRLB).

We’ll make this clear by rewording “absolute value” to avoid the mathematical connotation.

Thanks,
Acee


From: Renato Westphal <renato@opensourcerouting.org>
Date: Friday, September 13, 2019 at 11:17 AM
To: "draft-ietf-spring-sr-yang@ietf.org" <draft-ietf-spring-sr-yang@ietf.org>, "slitkows.ietf@gmail.com" <slitkows.ietf@gmail.com>
Cc: Olivier Dugeon <olivier.dugeon@orange.com>
Subject: draft-ietf-spring-sr-yang: question about absolute SIDs
Resent-From: <alias-bounces@ietf.org>
Resent-To: Stephane Litkowski <stephane.litkowski@orange.com>, <yingzhen.qu@futurewei.com>, Acee Lindem <acee@cisco.com>, Pushpasis Sarkar <pushpasis.ietf@gmail.com>, Jeff Tantsura <jefftant.ietf@gmail.com>
Resent-Date: Friday, September 13, 2019 at 11:17 AM

Hi all,

I have a quick question about the ietf-segment-routing-common YANG module.

Prefix-SIDs can be configured using either an index or an absolute label, as specified by the "value-type" leaf below:

    leaf value-type {
      type enumeration {
        enum "index" {
          description
            "The value will be interpreted as an index.";
        }
        enum "absolute" {
          description
            "The value will become interpreted as an absolute
             value.";
        }
      }
      default "index";
      description
        "This leaf defines how value must be interpreted.";
    }

I think the draft it not very clear about what an absolute value means. There are two possible interpretations:
1. The absolute value must be mapped to a SID index and must be within the SRGB range (as documented on Clarence's book, and this is also what IOS-XR does). The Prefix-SID V/L flags are set to 0.
2. The absolute value represents an MPLS label that can be outside the SRGB range. The Prefix-SID V/L flags are set to 1.

Which one would be the correct interpretation? I tend to think #1 is the intended design, but I'd like to hear a confirmation from the draft authors to be sure about it.

Thanks in advance,
--
Renato Westphal