Re: Re: I-D Action: draft-ietf-rtgwg-policy-model-13

t petch <ietfa@btconnect.com> Mon, 01 June 2020 10:52 UTC

Return-Path: <ietfa@btconnect.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C076F3A0F2E for <rtgwg@ietfa.amsl.com>; Mon, 1 Jun 2020 03:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-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=btconnect.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 MRi-bGn4DdQQ for <rtgwg@ietfa.amsl.com>; Mon, 1 Jun 2020 03:52:52 -0700 (PDT)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60096.outbound.protection.outlook.com [40.107.6.96]) (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 E14D43A0F2F for <rtgwg@ietf.org>; Mon, 1 Jun 2020 03:52:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Re2odMj90M9TSVWLKtsSgvPt9x0cUhchbls9JRERiGxmaJiZWXJ5R6bBLP1Da44aOqdWaIER45QtlU0Q9VyKXC1jdod/XxqEWBJs9eNt9N0Zi0oNowQGzPpDp3mPSZGbScP89/tsN7N7d5aM2nHY3bmezVQX1ZA1qcrnhG6eWKFcCeBSk57uWOYbLCIz829/T1I+zqYrXGb2hqmuJFjW3XneMd//45wPfnu/6vwFOfHqVoSeno/z0mJ38zpzmpasB0m1spz2wDEbhsT13i4Nyoh4wGxY939k6Y/1GsSmd7D7mpc+KNI1/FsS/zDG/1Wg/W9wgM+zKkUybMKrdNu/DA==
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=34TpuSP5b/VeS8L2iGS+QnQYwxrhFdWWfD6+w2fMEoI=; b=e/GKenOIw1wL1/5DSxFRemHcMQqt9fi1gUgN+H89Xc8MlIibCZbLeb20xX91kmoz1qWi/FvLjvQjJHXdwK1QeQeHuMEYPuWTQbYZkOHio5s7x87WRWsIy7+EVBATj/DajcWKNNf2Wuwzm5RTHEJbYf6KtljoXtmAgRdpqDgw76kxoe9uRjA1gOqDyQ5QEftUQIcfQxvasH2/f6mZdhzs3YBt/ro9zC/iQ7KJyAC7mQhHGV4t3KfKstloSLYzm8mvwyLOLctdnjfvPvzvmyTmVGPBqZuxzIcpc+BTYQVYke8EQC7h4e3NV3NpnfieOqyn4VvXIGOOp2OoZ7Dqilcdzg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=34TpuSP5b/VeS8L2iGS+QnQYwxrhFdWWfD6+w2fMEoI=; b=h4htyKGJprGlX0TfkOL1ad261yRHcnZCLcbFB6HKKdqQ0MC8F9SxiiQonkEh3LP4J7v+iZ+bl3Eb+/g50cN9v20zssjegK0uM0KSQ/tprdRTXaRkeuXYmvz7xHNzhgkmEJMfZVd5CUKpCpJLXXYq0LZF+rOuYlZM3BjuJioyQxc=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25) by DB7PR07MB5692.eurprd07.prod.outlook.com (2603:10a6:10:8c::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3066.7; Mon, 1 Jun 2020 10:52:49 +0000
Received: from DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::6d73:b879:b380:bed4]) by DB7PR07MB5340.eurprd07.prod.outlook.com ([fe80::6d73:b879:b380:bed4%7]) with mapi id 15.20.3066.016; Mon, 1 Jun 2020 10:52:49 +0000
Subject: Re: Re: I-D Action: draft-ietf-rtgwg-policy-model-13
To: "t.petch" <ietfa@btconnect.com>, rtgwg@ietf.org
From: t petch <ietfa@btconnect.com>
Message-ID: <5ED4DDFE.2070609@btconnect.com>
Date: Mon, 01 Jun 2020 11:52:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ClientProxiedBy: LNXP265CA0041.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5c::29) To DB7PR07MB5340.eurprd07.prod.outlook.com (2603:10a6:10:69::25)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (81.131.229.108) by LNXP265CA0041.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:5c::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.3045.22 via Frontend Transport; Mon, 1 Jun 2020 10:52:48 +0000
X-Originating-IP: [81.131.229.108]
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 589cace7-723e-4888-e40d-08d80619ec91
X-MS-TrafficTypeDiagnostic: DB7PR07MB5692:
X-Microsoft-Antispam-PRVS: <DB7PR07MB5692F19D45543460D3EAC01EA28A0@DB7PR07MB5692.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-Forefront-PRVS: 0421BF7135
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: gcM9e8189XV6/6Ilpx+4bTg9YSqsAIGZdp1C2cdhT49Bd1u7wjij921J9k5EkwSuy9mn706lZm4jSRgnIFggcmDj827F+hHyTJrdU4st0Id2U1umN+1AEHTxM0SCw+0JBzHfOKbOi1Q7HOHkukVVt1CzuT+d3WrmCSOJ6YJNtWotr7xMddmBQWczHjngWAxd8gTlMKPV3trmyn2yQkc6sJXEUKdDPbiQjtOV0G0bvLUAnRMkzH5zxsfCZBYRO4lsb/MgIZqZvKrF9XKYP7cujHeDDNXKBbDF33BauTKy52MCdjSrwvS4rql2FkjiceYq0B8/OtU5wPdn0KU6ySztbA==
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:DB7PR07MB5340.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(346002)(376002)(136003)(396003)(39860400002)(366004)(86362001)(6486002)(33656002)(16576012)(316002)(36756003)(5660300002)(66574014)(66946007)(2616005)(956004)(52116002)(87266011)(186003)(16526019)(26005)(66556008)(2906002)(8676002)(8936002)(83380400001)(478600001)(66476007); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: m3fRCqJpSQFc9uQ9cDuYLy/UKIWRqBLjrFovih/rN0Ftf32/rhIILaq5XFGPI7QnNuuKKOcUmCFdLyn4HdwTc0h7e8zR8EodoojQpkuz16Ncn9RF5iX8/S3Eg/18PJCloN/jytX47sm+JSLFp/2YxSbLdQA3ATXMvOAiGJWxrycquz6R+i6eLhG/WNvl93fNLej2yGZI+4EO/agKEzGovUW4jtEt2CyhDPo7Qz9nEe4LW+HU7cye1juZNMIVvhbsiE4J2WcELz7TdIIXP+17SC9GU0dQ1WZlIJgIpES8qK2OZX3rYxy7WLvp47vMYFpANq+hP1wfbqsjNeyg3Mwpp+a70tkNwXXkpLR3nROhaAug5zgsGrjDNUqhCKONxug4rulnjuVQmjxTiTWdV0bK+hVxP/I+nFGxZmSUymBEuYWAjcd4UbJ/qryLI+ECkjhNh2GOvzCkdMR4W+OpvEaEwB/cltuEtP9w/VcKjQtXF+Y=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 589cace7-723e-4888-e40d-08d80619ec91
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Jun 2020 10:52:48.9736 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: IgSAxXeu8448Nd4AoRhYL5NpoEXts3FOcOP2OocCuIsqQcjDsS8MqWQ5VFbz3nLVhy/HySXnHVTq2gAh0l8JdQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR07MB5692
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/xWOZOqVgeTuYtSOsKxXgjeUgxWs>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 10:52:54 -0000

I have some doubts about this I-D

-01 had four authors; -13 has four authors.  None are the same yet much
of the text in the I-D is the same.

NSSA could be added to the Terminology and/or expanded on first use.

Policy subroutines sound interesting - if there is one example I would
find useful it would be one involving subroutines.

10 YANG modules
I only see one singular

XXXX is used as a placeholder for two different I-D

I like the reference to RFC2178, RFC5130 but they need to appear in the
I-D References and more YANG reference clauses would not come amiss

       typedef metric-modification-type {
....
                   If the result would exceed the maximum metric
                (0xffffffff), set the metric to the maximum.";
OSPF has a 16 bit link metric, a 24 bit route metric as defined in
ospg-yang.  Defining a maximum of 0xffffffff seems problematic. Add two
to 16777215 and you get one.
The other LSR protocol has a 6 or 24 or 32 bit metric depending on where
you look.

             "The prefix member in CIDR notation -- "
member of what?  My prefix are a number!

         leaf mask-length-upper {
the example implies that upper and lower must both be present which I do
not see in the YANG.  Both upper and lower are part of the YANG key of
the list which also suggests that both need to be present

       grouping match-proto-route-type-condition {
gets a bit long; here and elsewhere, is 'proto' needed as part of the
identifiers?

           container prefix-sets {
               leaf mode {
I am not a fan of features - Cartesian explosion - but wonder if one is
called for here at least for mixed mode

Tom Petch
>
> ----- Original Message -----
> From: <internet-drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Cc: <rtgwg@ietf.org>
>