Re: [Idr] draft-ietf-idr-segment-routing-te-policy Policy Name Sub-TLV considerations

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 13 February 2020 18:08 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 0F2511201A3; Thu, 13 Feb 2020 10:08:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=BkodmExI; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=fYDFybG3
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 H6XlqEfmrblm; Thu, 13 Feb 2020 10:08:23 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E747A1200B8; Thu, 13 Feb 2020 10:08:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3399; q=dns/txt; s=iport; t=1581617302; x=1582826902; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=IUN0jGUrHraHrmlAjsPRXdKw1lZpp4FzwgRu9qNbk1g=; b=BkodmExIsNMO21aQ3lXWxRXcA2TgL3I2gEroFWRsL0RlXAre6ye+e4/7 iahMAb8U4xosukXRxtbRdTQM+olDvLEGXpQC0p/1ToMflw+bKmx7/iHZW XUYKBrAHKKznUFaU1mr+cgze1iw4kEbbu5dCsTbJ9szPqVF3ByR3DbYSP U=;
IronPort-PHdr: =?us-ascii?q?9a23=3AZYPynxM4+YI1frJ+rMMl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEuKQ/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBj4IeLjaTASF8VZX1gj9Ha+YgBY?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CMDAA0j0Ve/5JdJa1cChwBAQEBAQc?= =?us-ascii?q?BAREBBAQBAYF7gVQkLAVsWCAECyoKh1ADindOghGYEYJSA1QJAQEBDAEBIwo?= =?us-ascii?q?CBAEBhEACgkwkOBMCAw0BAQUBAQECAQUEbYU3DIVmAQEBAQMSKAYBATgLBAI?= =?us-ascii?q?BCA4DBAEBHxAyHQgCBAESCBqDBYJKAy4BDqIXAoE5iGKCJ4J/AQEFhR8Yggw?= =?us-ascii?q?DBoE4jCQagUE/gRFHgkw+gmQBAQIBgTUFKoNAgiyWZZgfdgqCOodNjyCbF45?= =?us-ascii?q?oiG6SPwIEAgQFAg4BAQWBaSKBWHAVgydQGA2OHQkag1CFFIU/dAIBgSaLNoE?= =?us-ascii?q?yAYEPAQE?=
X-IronPort-AV: E=Sophos;i="5.70,437,1574121600"; d="scan'208";a="725449245"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Feb 2020 18:08:21 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id 01DI8L9h012012 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 13 Feb 2020 18:08:21 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 13 Feb 2020 12:08:21 -0600
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 13 Feb 2020 13:08:20 -0500
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 13 Feb 2020 12:08:19 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h+uwcPvhYSV8ygPPBKWZKqHUVDy5r0dVxyC7ubAIP3wA3T+btf1+sx2EPd3tS9+fT/51KNacKGYOlvx2rhWiaB0AHS4HWcdyQaCLwLse6rv9VWmnbCsEXMxwm1uMSe4LRvaN674Z9pDg0viEQu3I3/lXMn/VRjwJiZOCpy1qHdJ5IfNY43ANlFWX+mISbaziFPpy0dtFDvnOtNtQNaztCA+M1vr8WD62A+WBh71vcMonwG8RriRApo5FBs3mYEdKkcgQTId7dmh4DU2bvDdqqRnIrytXuGx8ONrOPX5lJ6qS8BCqbPn3I9yAZ5vf1J/AxP9jmHri/eIcvjeRKVhzoQ==
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=o5e8eP/pmY9gaQlKGgM24HR0QVAlC9qyOirageIuP74=; b=KrZPxSSqOatue5hiINLBZdeHPitYVo+Vsy1Xojg+nNF2N+M5sUZ7m76GmQUcCz4gXvvx1bXfDCWSejo5PfmiimFVfX5ZmXDNkoYJqg3oRIGpUpMSnvV0+8eIMf04Lo/Tc3N473a8vmONQjc11ItGZoyEO2GnF00KNbEX/jHbxCJaj7p35z95MaN4x5h0UOg6oVV5nWwkSHn5SHdAXBtP68PVlKM0oHsdXIH6gdszHc1EgIKy8fLo/FtmIuIbQM/gaHbaR6JCz7yYiFccBW9EftIkgc4TzAINOfM2NNDVTRmeq+kLdOeXrFnfKKqLPbzn8HajMDCr9SQD6zbuwrGN6A==
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=o5e8eP/pmY9gaQlKGgM24HR0QVAlC9qyOirageIuP74=; b=fYDFybG3mT4TAQ3kdQS5miGIJlapP4JUJquhG3IoHea/ly5ee/Xcvi/YWEhmWfea/+DV7n9ZymbYA4fVvPkgC49qW4LhwTjVMmg4bGG4O+cFy/EJCrAL2GBjddT3km3qOukB1JkRJxORgHldDJb9uFYQ3okID9PqnArBUW2RS24=
Received: from CY4PR11MB1589.namprd11.prod.outlook.com (10.172.71.13) by CY4PR11MB1816.namprd11.prod.outlook.com (10.175.63.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2729.23; Thu, 13 Feb 2020 18:08:19 +0000
Received: from CY4PR11MB1589.namprd11.prod.outlook.com ([fe80::140e:e5e7:62e5:2a4c]) by CY4PR11MB1589.namprd11.prod.outlook.com ([fe80::140e:e5e7:62e5:2a4c%6]) with mapi id 15.20.2729.025; Thu, 13 Feb 2020 18:08:19 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>, "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: draft-ietf-idr-segment-routing-te-policy Policy Name Sub-TLV considerations
Thread-Index: AQHV4fnX9GqjNaH+OECMSUudeTzukagZZg2A
Date: Thu, 13 Feb 2020 18:08:18 +0000
Message-ID: <CY4PR11MB158938E9C613B793782A27E1C11A0@CY4PR11MB1589.namprd11.prod.outlook.com>
References: <20200212231711.GB32507@pfrc.org>
In-Reply-To: <20200212231711.GB32507@pfrc.org>
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: [128.107.241.187]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5825ef8f-9dd8-4946-ad0f-08d7b0afb484
x-ms-traffictypediagnostic: CY4PR11MB1816:
x-microsoft-antispam-prvs: <CY4PR11MB18166ED360DD73F188CD878FC11A0@CY4PR11MB1816.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 031257FE13
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(346002)(396003)(376002)(366004)(39860400002)(199004)(189003)(52536014)(316002)(26005)(2906002)(186003)(7696005)(5660300002)(66446008)(966005)(64756008)(53546011)(6506007)(110136005)(478600001)(66476007)(71200400001)(33656002)(66946007)(76116006)(66556008)(86362001)(81166006)(81156014)(8676002)(8936002)(9686003)(55016002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1816; H:CY4PR11MB1589.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 83mHLhQbOXau6Je0E1jp9okDmIsTezF2dPUUww6ht7on2pOmVe5JZ9ov2P1LOuu4tP2Y6+c3wNi31ZAsxWSH76dS6TS1+rlRbnhyM/5cGBz8L3JstVhfzc4ARu2oBUctxWziAk7gMGBWUx++8AUQ1ADEBcz8mcmi+iWnseX48avBrEGWvLgu2WHTkoZK8+XGZUebVH9PMNd1AWHKdXhaxZ5XJ44Tel55LsBNHWXJODe5239EpsdCD8/fFIDphoEdfvPcoo52UeLgn0uDHC3Ql3UiWk4eOlTlRx7blw8zNvnXGoBMRGC0+39YFo3fDb163egYUnlYFIykkb606n/pyOnC9PKyT8wYORCBENZNy+SRjkTdBay3xDlZZHI4PDoh73mk9/X3wmDAZol1PK5T97xy6LAMI/R34rxQv3AGHHgPDw27Cf+GCF5e9X+tcA0y8F7iMQuU1eAnosdjYrR8GOhTJQocsIBPnZRqR0X9S+cxcbBNIwGT/R/RB/hSWR9KcjeRwqsYOEa+dM5CU3GvYA==
x-ms-exchange-antispam-messagedata: PNZ41JkW1vNm5dCGM4imNPIY7/z9Fl2NYM/K63e/+G/gmMGA5l+VCezD4J8aBH3Q1E5hlZPmw41KZemaxeXAteOBOd8mcB9WcWgZTtZXX+gB9QorYToHBJJBYJfMgG35wsJPTwGMCpdFwPKPfA2btA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5825ef8f-9dd8-4946-ad0f-08d7b0afb484
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Feb 2020 18:08:18.4446 (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: 5AMkOeZ8v2Dh6ywws4L/TXQEF6pJTo88VubI0fTiVfOegkffUmDsAdF28hgEePvJkRSp4K8OEjgNkG7W/glndA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1816
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/3ggDsvkJBbMCdn7MkMeDq2m0_aE>
Subject: Re: [Idr] draft-ietf-idr-segment-routing-te-policy Policy Name Sub-TLV considerations
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: Thu, 13 Feb 2020 18:08:25 -0000

Hi Jeff,

I agree with you about the limits on the policy name size. 

I am not aware of any IETF standard that mandates the use of UTF-8 for encoding of string for names. The similar object in PCEP is encoded in ASCII - https://tools.ietf.org/html/rfc8231#section-7.3.2 

Thanks,
Ketan

-----Original Message-----
From: Jeffrey Haas <jhaas@pfrc.org> 
Sent: 12 February 2020 15:17
To: draft-ietf-idr-segment-routing-te-policy@ietf.org; idr@ietf.org
Subject: draft-ietf-idr-segment-routing-te-policy Policy Name Sub-TLV considerations

Authors,

In draft-ietf-idr-segment-routing-te-policy-08, Section 2.4.6 we have a TLV for Policy Name.  Its text is:

: 2.4.6.  Policy Name Sub-TLV
: 
:    An operator MAY set the Policy Name sub-TLV to attach a symbolic name
:    to the SR Policy candidate path.
: 
:    Usage of Policy Name sub-TLV is described in section 2 in
:    [I-D.ietf-spring-segment-routing-policy].
: 
:    The Policy Name sub-TLV may exceed 255 bytes length due to long
:    policy name.  Therefore a 2-octet length is required.  According to
:    [I-D.ietf-idr-tunnel-encaps], the first bit of the sub-TLV codepoint
:    defines the size of the length field.  Therefore, for the Policy Name
:    sub-TLV a code point of 128 or higher is used.
: 
:    The Policy Name sub-TLV is optional and it MUST NOT appear more than
:    once in the SR Policy TLV.
: 
:    The Policy Name sub-TLV has following format:
: 
:    0                   1                   2                   3
:     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
:    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:    |     Type      |   Length                      |   RESERVED    |
:    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
:    //                        Policy Name                          //
:    +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: 
:    Where:
: 
:       Type: 129.
: 
:       Length: Variable.
: 
:       RESERVED: 1 octet of reserved bits.  SHOULD be set to zero on
:       transmission and MUST be ignored on receipt.
: 
:       Policy Name: Symbolic name for the policy.  It SHOULD be a string
:       of printable ASCII characters, without a NULL terminator.

draft-ietf-spring-segment-routing-policy-06, Section 2.1 discusses this
Sub-TLV:

:    An implementation MAY allow assignment of a symbolic name comprising
:    of printable ASCII characters to an SR Policy to serve as a user-
:    friendly attribute for debug and troubleshooting purposes.  Such
:    symbolic names may identify an SR Policy when the naming scheme
:    ensures uniqueness.

There are two observations I'd like to make:
1. A 65K length isn't very likely in BGP. :-)  I suggest that greater guidance for shorter names should be offered. For example, perhaps limit the length to 1K.  Alternatively, offer advice such as: "Implementations may choose to truncate long Policy Names".

2. The guidance about "printable ASCII" is rather old-style and likely to run askance of IESG review for internationalization considerations.  I'd suggest that the field be encoded in UTF-8 and make reference to print-safety similar to RFC 8203 (BGP Administrative Shutdown) in its Security Considerations.

-- Jeff