Re: [Idr] draft-ietf-spring-segment-routing-policy

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Fri, 02 August 2019 02:37 UTC

Return-Path: <ketant@cisco.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 32FD2120091; Thu, 1 Aug 2019 19:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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=Z35wGBIZ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eV65ghzQ
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 ylhKW6H7Y5_b; Thu, 1 Aug 2019 19:37:23 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3B2412001A; Thu, 1 Aug 2019 19:37:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=21037; q=dns/txt; s=iport; t=1564713442; x=1565923042; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DfwFSWrZqSaTbEN+eCwabZtYydCR2f0lpim+VJF+wN0=; b=Z35wGBIZj4BMwEwx1tBhCSmDMUzkTcRiH6qsFLIsZbNbQi45ZFabSp6h Zn4W0IO/yQVskd4Cyl9HkmjdQF2aqgt+DrpssRXWlANbSCnTsOMAhaH4I BaIgPtL9WvoQQMOPGgGzIcrfLJFhBeao4RMhtEtoJclkjsvqZdg14fVbo Y=;
IronPort-PHdr: =?us-ascii?q?9a23=3A7yTg4xSXKV1T7K32i+GdUC1oFdpsv++ubAcI9p?= =?us-ascii?q?oqja5Pea2//pPkeVbS/uhpkESUDNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH1?= =?us-ascii?q?5g640NmhA4RsuMCEn1NvnvOi83AM1ESHdu/mqwNg5eH8OtL1A=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAAAJoUNd/5pdJa1lGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUwQBAQEBAQsBgRUvJCwDbVUgBAsqh2UDhFKGVoJbl1e?= =?us-ascii?q?BLhSBEANUCQEBAQwBASUIAgEBhEACglUjNAkOAQMBAQQBAQIBBm2FHgyFSgE?= =?us-ascii?q?BAQEDEhsTAQEqCgMBDwIBCBEEAQEeETIdCAEBBAENBQgagwGBHU0DHQECDKJ?= =?us-ascii?q?oAoE4iGCCI4J6AQEFhQIYghMDBoE0AYtfF4FAP4ERRoJMPoJhAQECAYErARI?= =?us-ascii?q?BISuDEIImjBSHdSOIUY4bCQKCGoZcjVqCLocojkSNQodRkBQCBAIEBQIOAQE?= =?us-ascii?q?FgVA4Z3FwFTuCbIJCDBeDToUUhT9yAYEoijCCQwEB?=
X-IronPort-AV: E=Sophos;i="5.64,336,1559520000"; d="scan'208,217";a="597340532"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Aug 2019 02:37:21 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id x722bLDW013543 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Aug 2019 02:37:21 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 21:37:20 -0500
Received: from xhs-rcd-002.cisco.com (173.37.227.247) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 1 Aug 2019 22:37:19 -0400
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-002.cisco.com (173.37.227.247) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 1 Aug 2019 21:37:19 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ixC5JrqLqagXmUXhnTTLSP40eWgS7wM7SRTnp6Cxs6ku+0coU2JJBSi92X77p34qDi/cJP1Q2M+wK/olNSzveiNDjoah6nx3MOeDfX+JJY7RqLXqoLfVmorpGAEzgXRf04KAF1ToygcDcAVY/N9Mlmg6HoWpHlaYOEy0D9JUAaAbnIb5g97tXtTiofKC7Gk5w7gZ+3xRdc4WlDRAVHxjVynBl+2h7YDLqAQtwuyluecis6ZAxXlO0j28zOs0RksXi7dJ3INTDBWL37/iVYyxpuN79TdQoZwPRCP8iflGc7yoW7K6FB6BvBJT8TC0wkmzeeJGUvEDOPo5UCQxeo37PQ==
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=cIn4iW3ER/dNaKPkV3Uox2aivE7rMcttJvzXjFTXwCw=; b=Jl0BZR69SvsffMI1un9kr8JdaNJSo1s8MuVjBbHTGIC0b3gtXcKFqtdDXMMrD+i0xCLFr/VR+IUKH0Gex1LOyuPVRb/WICpkJGEC5X2ekSzewREK5h3cUXfrXVIfNPrFcL6sW+x2dDpf1vsvRFgWCUbwhpnmKRCrqNCOyRbD6xDFvqr+PXYjtuFfMm+4UfK0uVYSifcNbeHPuNBKbcMrtirA7QEAPgIYod1Bf0bT+QMJ+3FZFwlLwGTdoGCBzhCycDPh6YY1jf2rIuxLFcVCiflv2Nrl3ufZI0mIG8XaoIJtWJt+qPHiYxY6t1snB/8su7xZ1b6t37nt7NYayv7Drg==
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=cIn4iW3ER/dNaKPkV3Uox2aivE7rMcttJvzXjFTXwCw=; b=eV65ghzQp3V3nU2FKc+T6vw2sXwO4S5ShZ9f1bSGnkMt1aDpyKlKdw5IezzKcEMiOb7wJH4RAsxjcq0awV3uElMtLzvdDu7tQSpHs4jCX09M1Y9elWUkQfwCG/fNEF4G7q8jeW6Sbpaqv7lbtxmDnjeH9l9Dixs7ZJWfm0j7aec=
Received: from BYAPR11MB3558.namprd11.prod.outlook.com (20.178.206.75) by BYAPR11MB2917.namprd11.prod.outlook.com (20.177.226.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2136.13; Fri, 2 Aug 2019 02:37:18 +0000
Received: from BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::3d73:9b60:6c26:2d0c]) by BYAPR11MB3558.namprd11.prod.outlook.com ([fe80::3d73:9b60:6c26:2d0c%6]) with mapi id 15.20.2136.010; Fri, 2 Aug 2019 02:37:18 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>, SPRING WG List <spring@ietf.org>
CC: idr wg <idr@ietf.org>
Thread-Topic: draft-ietf-spring-segment-routing-policy
Thread-Index: AdVIa5SmJroPUcCZR8q84NofG0DylwAap4eA
Date: Fri, 2 Aug 2019 02:37:18 +0000
Message-ID: <BYAPR11MB355899A67FBFBE1750E9A3A6C1D90@BYAPR11MB3558.namprd11.prod.outlook.com>
References: <18897_1564666804_5D42EBB4_18897_192_1_53C29892C857584299CBF5D05346208A48BCF785@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
In-Reply-To: <18897_1564666804_5D42EBB4_18897_192_1_53C29892C857584299CBF5D05346208A48BCF785@OPEXCAUBM43.corporate.adroot.infra.ftgroup>
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=ketant@cisco.com;
x-originating-ip: [2001:420:c0e0:1002::332]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 75984d61-825a-4170-1a86-08d716f2565d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BYAPR11MB2917;
x-ms-traffictypediagnostic: BYAPR11MB2917:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB291722893E3F12BACD4C22C1C1D90@BYAPR11MB2917.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 011787B9DD
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(346002)(366004)(39860400002)(376002)(189003)(199004)(71200400001)(68736007)(110136005)(4326008)(14454004)(5024004)(14444005)(86362001)(25786009)(256004)(606006)(186003)(74316002)(6246003)(8936002)(316002)(102836004)(478600001)(236005)(966005)(71190400001)(7736002)(7696005)(55016002)(2501003)(99286004)(52536014)(446003)(486006)(229853002)(81166006)(6306002)(64756008)(66476007)(5660300002)(33656002)(6436002)(6506007)(476003)(8676002)(76116006)(46003)(66446008)(81156014)(66556008)(790700001)(53936002)(66946007)(6116002)(2906002)(9686003)(76176011)(11346002)(54896002)(53546011); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2917; H:BYAPR11MB3558.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: BDXR3zMzNeP+3l0d2apUuixe4haVtI4V0gb4zwmBiYp1pUwagcJ1y46PFoqn6uhKDboBOIQuZStY0P4+9GoiuHogdvqjIYV9bbXl0L/vE7h0dK/sdlYPnmBqxwxvuvOW7ZpYwagsO+NKGuRVHQqo6vEQKc7g4L1A+jxfeHNBnZx9uq6aP6f356U3BaVmnZaXOegfBAbk19XEhChK7YNnw/NQWZZjPM+8zaXi3MsF7DZLPRBx92CNY/vbvXCF5mvqdFzTbEUVIOTsM5ws1UonlyBgExuD5XBtCQRis87DzsVgnG7TfhfO9JEcSH311heUjA2CpszO/4azJlVUt4gAgatclT5x0zUDY8OkZZxwItR3nVhcUXKdX6vC96mLI5cBlxtn4f8e9D/6EIPr9/zw+tmXsvSHWZCDLIk01N5MTcY=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB355899A67FBFBE1750E9A3A6C1D90BYAPR11MB3558namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 75984d61-825a-4170-1a86-08d716f2565d
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Aug 2019 02:37:18.1084 (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: ketant@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2917
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.22, xch-rcd-012.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ucCSqoqQBM04J9tc4-3hkW54Fw4>
Subject: Re: [Idr] draft-ietf-spring-segment-routing-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 02 Aug 2019 02:37:26 -0000

+ IDR WG since some of the affected documents are IDR WG drafts

Hi Bruno,

I agree that the draft-ietf-spring-segment-routing-policy [1] is the right place to normatively define the different segment types and perhaps would have been the right document to create an IANA registry for them.

I also agree that the draft-ietf-idr-segment-routing-te-policy [2] has a discrepancy between its IANA section 8.4 for the Segment-List sub-TLV space and section 2.4.3.2 (and it's sub-sections) where the different Segment Types have been defined. I will request the authors of this draft to fix the text in section 2.4.3.2 (and it's sub-sections) for the types 8 and above to adjust for the codepoint 9 allocated for the weight sub-TLV.

At this point, given the implementations available and already deployed for [2], I doubt if we can correct and map the segment types in that draft to what has been defined in [1].

There is also the https://tools.ietf.org/html/draft-ietf-idr-te-lsp-distribution-11#section-9.7 which creates the Segment Types IANA registry (aligned with [1]). And then I am not sure if draft-raza-spring-sr-policy-yang is able to benefit/leverage the IANA registry from [1].

So unless we can have the IANA registry created via [1] being consistently used in all dependent documents, I do not see much gain in setting up the Segment Type registry under IANA at this point.

Thanks,
Ketan

From: spring <spring-bounces@ietf.org> On Behalf Of bruno.decraene@orange.com
Sent: 01 August 2019 19:10
To: SPRING WG List <spring@ietf.org>
Subject: [spring] draft-ietf-spring-segment-routing-policy

Hi authors,

Speaking as individual contributor.

This document seems to define multiple types of segments (1 to 11).
May be this document would be the right place to define them normatively and creates the IANA registry for them. And this seems like a work for spring.
Otherwise, there is a risk that other documents redefine them, possibly in a non-consistent manner. (1) E.g.  the BGP draft is not using the same type numbers/name, which may bring confusion. I would expect YANG models to also need these types.
BTW is there any chance to align the types in the BGP document or is this too late? (alternatively may be changing the types in the sr-policy document)

Thanks,
Regards,
Bruno

(1)
SR-policy:

   Type 1: SR-MPLS Label:

   Type 2: SRv6 SID:

   Type 3: IPv4 Prefix with optional SR Algorithm:

   Type 4: IPv6 Global Prefix with optional SR Algorithm for SR-MPLS:

   Type 5: IPv4 Prefix with Local Interface ID:

   Type 6: IPv4 Addresses for link endpoints as Local, Remote pair:

   Type 7: IPv6 Prefix and Interface ID for link endpoints as Local, Remote pair for SR-MPLS:

   Type 8: IPv6 Addresses for link endpoints as Local, Remote pair for SR-MPLS:

   Type 9: IPv6 Global Prefix with optional SR Algorithm for SRv6:

   Type 10: IPv6 Prefix and Interface ID for link endpoints as Local, Remote pair for SRv6:

   Type 11: IPv6 Addresses for link endpoints as Local, Remote pair for SRv6:


BGP:
   1     MPLS SID sub-TLV                            This document
   2     SRv6 SID sub-TLV                            This document
   3     IPv4 Node and SID sub-TLV                   This document
   4     IPv6 Node and SID for SR-MPLS sub-TLV       This document
   5     IPv4 Node, index and SID sub-TLV            This document
   6     IPv4 Local/Remote addresses and SID sub-TLV This document
   7     IPv6 Node, index for remote and local pair  This document
         and SID for SR-MPLS sub-TLV
   8     IPv6 Local/Remote addresses and SID sub-TLV This document
   9     Weight sub-TLV                              This document
   10    IPv6 Node and SID for SRv6 sub-TLV          This document
   11    IPv6 Node, index for remote and local pair  This document
         and SID for SRv6 sub-TLV
   12    IPv6 Local/Remote addresses and SID for     This document
         SRv6 sub-TLV


_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.