Re: [Idr] Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?

Linda Dunbar <linda.dunbar@futurewei.com> Wed, 23 October 2019 14:40 UTC

Return-Path: <linda.dunbar@futurewei.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 18F85120825; Wed, 23 Oct 2019 07:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 l0Yfl7F4BEA0; Wed, 23 Oct 2019 07:40:19 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690117.outbound.protection.outlook.com [40.107.69.117]) (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 82A4E1200E6; Wed, 23 Oct 2019 07:40:19 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OzeSTV4Y0RngVdFL9VpgwujZ0ZMpbcUb9LBsNCEYQOBMXt6XzxTyTfcjac91ksw5Pv8K/Mf2cqcQfm24GebW5C9J9/bkwakiR+kPbJaTKX7WEgG45p592hj88v7m9i5DVcTPtgJEp9Vfo/kCyy4m4I1niscTv0+wut8ar7hv6OiRE+OKu23dWpnzKtn1BM/J2JXHyn0P1Zy/+nB6CMo/ev4jh9Wc7GaUz+wx0vuCXxe4n6UXe0W69B00YDtUAd0Af7b+MqIJiOO2fbeVV4WKYpPW2kvREHfWg9I4P0CBN6si2q6HSut0bA0PQPWQH0r8q74y2Y0h+vLPuZuZvLM+ZQ==
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=uOeNhIer6Kodybr1wzZUTtZtBUuu+jSVRIh5PrLWTAk=; b=GMHMBsxqPLTickNCw0N5ng3nkcl1E95LHxrUv702Ucp6MXivZ1gPo/WQHDB/vbTX6RGDApNMtpnnejKxuaOS8AbsI4lmmM8SW+Io238tBC9KTk13hHQwUmg4nAfHtNnm4+oAort4XfPLyUIAZbNg8FAWl6Rsds7NUhO8aIBlSOFWsFoZSkhFvizq7NPgsBU325y0Zox3GiZbL/x4RONM7hCsZTrABswIBRhpm+n0Sh9mbVmlG0ayxqzbWmL1CdBXGjVuKOw5GYHO0pqfFG4X1gHHkqbc5ax4Xsfzngi4uKIeolv2Zf7RAOUFAPQBaI40DwGmGxV5A/o0mGSOuGqWXg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uOeNhIer6Kodybr1wzZUTtZtBUuu+jSVRIh5PrLWTAk=; b=KHaMkAhaQub4jByGaUfEuOfWKQ8xdMSElW3QQgctfmfG5tmyY1DLuBuvauLwWiPLxKdhu1vvAAGf0L5xd2CAx/BHqZ2XNinfRUsBi1Dqq0NTv16+Ewzyr4kxGwz8TxYkTPhuogveOL9OceAOHuOAzaVCdlx0KFGj3uPXEa0XG0Y=
Received: from BN8PR13MB2628.namprd13.prod.outlook.com (20.178.219.10) by BN8PR13MB2803.namprd13.prod.outlook.com (20.178.219.78) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.17; Wed, 23 Oct 2019 14:40:17 +0000
Received: from BN8PR13MB2628.namprd13.prod.outlook.com ([fe80::9f3:c754:7ac8:b3dd]) by BN8PR13MB2628.namprd13.prod.outlook.com ([fe80::9f3:c754:7ac8:b3dd%7]) with mapi id 15.20.2387.021; Wed, 23 Oct 2019 14:40:17 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: stefano previdi <stefano@previdi.net>
CC: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>
Thread-Topic: Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?
Thread-Index: AdWJL8Q1O9N1oazERLGVGmbsrPofSQAUTi+AAAtzquA=
Date: Wed, 23 Oct 2019 14:40:17 +0000
Message-ID: <BN8PR13MB26280DC9375BF0AF242A8A01856B0@BN8PR13MB2628.namprd13.prod.outlook.com>
References: <BN8PR13MB2628C035A31A9D40F4E07F1485680@BN8PR13MB2628.namprd13.prod.outlook.com> <2F4F86FE-E7AA-4496-BE65-1F0124367399@previdi.net>
In-Reply-To: <2F4F86FE-E7AA-4496-BE65-1F0124367399@previdi.net>
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=linda.dunbar@futurewei.com;
x-originating-ip: [72.180.73.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c45e2e6d-2c0f-4eb5-fe4e-08d757c6ec49
x-ms-traffictypediagnostic: BN8PR13MB2803:
x-microsoft-antispam-prvs: <BN8PR13MB2803B13F90147C0C453706AC856B0@BN8PR13MB2803.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 019919A9E4
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(376002)(396003)(136003)(346002)(39850400004)(366004)(13464003)(199004)(189003)(86362001)(76176011)(71200400001)(305945005)(71190400001)(44832011)(7696005)(76116006)(99286004)(33656002)(186003)(102836004)(53546011)(6506007)(6116002)(4326008)(26005)(7736002)(52536014)(3846002)(5660300002)(55016002)(74316002)(66066001)(54906003)(256004)(316002)(486006)(2906002)(9686003)(6246003)(8676002)(14444005)(25786009)(8936002)(66556008)(66476007)(66446008)(476003)(66946007)(11346002)(478600001)(81156014)(14454004)(6436002)(6916009)(229853002)(81166006)(64756008)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN8PR13MB2803; H:BN8PR13MB2628.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Ho7p2NOseMnK/s0uNkNvMB6hL3s8lvODX4Dbn3XarS4x1wjG/AMG97MrIUwBjr6LW8c4qh29M4cVzZPgKjBOqF+B/RpnJ/S5+l9FfRD/rX1S+OMrYn3P3nH5U4yH1lVYSx9dykgVCiXBkIrYuEECaxoq+g7TR6k8ditYLWnBJqP+NFUEv7xIwD+MwJOtupcbwsmVtaHism1BWAsAMR6slcjDGOBZXpimlDiQWr1tG6cPuLrbSJmQygM3igCXVY7q3bsxuUvpN6599GsvS0xhQRpAI6h8PORScJ1tgO9I1pZV75u7RBs2v1C3AGcjfQj5iCHTakH2pRighGggv2EfpEakXUZh+7AQ5h2Vu8NQlJt1+NsqEXDCXEcoehtX7R6Ka1XCVYGKzAjm6VrQDF7IOxLYkVLr8whUd0dBBInWuqmTWLktwPchwOZK+nmNfUZM
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c45e2e6d-2c0f-4eb5-fe4e-08d757c6ec49
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2019 14:40:17.3339 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: A4uRZwvXZ3jd6jfqkXxOAwYg8KQpA3wnlZi7h6Fz58+pEb4QE+bq8UU+ieO/zFSY14juZ1iEsTjn8rWYd7Ud3w==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR13MB2803
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/1ncWXJgMZaz2zKXpPlk5CDx5m2s>
Subject: Re: [Idr] Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?
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: Wed, 23 Oct 2019 14:40:23 -0000

Stefano, 

Since the MP-NLRI Path Attribute (code=14) and the Tunnel Path Attribute (code =23) are at the same level, does it mean that one BGP UPDATE can only carry one policy? 

I am just curious why not encoding the Policy Content as subTLVs nested within the Policy Identifier encoded in the MP-NLRI? So that one BGP UPDATE can carry multiple SR policies.

Thanks, Linda

-----Original Message-----
From: stefano previdi <stefano@previdi.net> 
Sent: Wednesday, October 23, 2019 4:05 AM
To: Linda Dunbar <linda.dunbar@futurewei.com>
Cc: idr@ietf.org; draft-ietf-idr-segment-routing-te-policy@ietf.org
Subject: Re: Is the SR Policy SAFI described in draft-ietf-idr-segment-routing-te-policy-07 under the MP-NLRI (code =14) or under the Tunnel Path attribute (code = 23)?


> On Oct 23, 2019, at 1:23 AM, Linda Dunbar <linda.dunbar@futurewei.com> wrote:
> 
> IDR experts and the Authors of draft-ietf-idr-segment-routing-te-policy-07:
>  
> The section 2.1 of draft-ietf-idr-segment-routing-te-policy-07 describes a new SR Policy SAFI under NLRI of BGP UPDATE to advertise SR policies.
>  
> Does it mean that SR Policy SAFI is under the MP-NLRI Path Attribute (Code = 14)?


yes, the nlri with the new safi identifies the policy:
   +------------------+
   |  NLRI Length     | 1 octet
   +------------------+
   |  Distinguisher   | 4 octets
   +------------------+
   |  Policy Color    | 4 octets
   +------------------+
   |  Endpoint        | 4 or 16 octets 
   +------------------+


> The Section 2.2 indicates that SR Policy is encoded in the Tunnel Encapsulation Path Attribute defined in the draft-ietf-idr-tunnel-encaps-12.
>  
> Does it mean the SR policy is also under the Tunnel Path Attribute with Code =23?


the content (i.e., the details) of the sr policy is encoded in the tunnel path attribute.


> Can you please explain is it MP-NLRI Path Attribute or Tunnel Encap Path Attribute that SR policy are encoded?


there are separate items: policy identifier and policy content.

the policy identifier (distinguisher, color, endpoint) goes into the nlri and the policy content (e.g., the segment list) go into the tunnel path attribute.

s.


>  
> Thank you very much. 
>  
> Linda Dunbar