Re: WG last call for draft-ietf-rtgwg-policy-model

"Acee Lindem (acee)" <acee@cisco.com> Wed, 16 September 2020 17:47 UTC

Return-Path: <acee@cisco.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 10FC33A0128; Wed, 16 Sep 2020 10:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.62
X-Spam-Level:
X-Spam-Status: No, score=-9.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=cgjEc3lM; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=iqSC6E4U
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 8YhhJ7XX1xPR; Wed, 16 Sep 2020 10:47:45 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8ECB3A0138; Wed, 16 Sep 2020 10:47:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7424; q=dns/txt; s=iport; t=1600278464; x=1601488064; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=4uf57aUd98mjvqTePzFnXaZuIlisfinc7C5Szo5DlZg=; b=cgjEc3lM6yoFliC3ipIURzmCsQDPmoLl2GCQgEwampEwB4sz96yNi89q NSrILB2ErG4moRUa4dZp/yATupugD5wSpWnDvzYX0x0mef6JYCVxf+KwE Cb+1jDv4AH+yEhKi2b/DYZ51acCJ+u0rIdV082/QhStXOmrxn8ZGe5u6+ U=;
IronPort-PHdr: 9a23:D1sv8R8DheBapv9uRHGN82YQeigqvan1NQcJ650hzqhDabmn44+7ZhaN7+lmi1nPUI7HrflDjrmev6PhXDkG5pCM+DAHfYdXXhAIwcMRg0Q7AcGDBEG6SZyibyEzEMlYElMw+Xa9PBtfBM35YVvfqWH05jkXSV3zMANvLbHzHYjfx828y+G1/cjVZANFzDqwaL9/NlO4twLU48IXmoBlbK02z0jE
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CwAACRTmJf/5BdJa1ZBhoBAQEBAQEBAQEBAwEBAQESAQEBAQICAQEBAUCBT4FSUQdwWS8sCoQvg0YDjW+BAokLjmaCUwNVCwEBAQ0BARgLCgIEAQGESwIXggsCJDgTAgMBAQsBAQUBAQECAQYEbYUvBicMhXIBAQEBAwEBEAsGEQwBASwLAQ8CAQgRBAEBAwImAgICHwYLFQgIAgQBDQUigwQBgksDLgEOqkYCgTmIYXaBMoMBAQEFhRINC4IQAwaBDiqCcYNpgkGEERuCAIERJxyCGDU+ghpCAQECgU0Qgxczgi2TKqMjUQqCZZU9hQcDHoMJiXiFOI5Akm+NRpIrAgQCBAUCDgEBBYFrI4FXcBU7KgGCPlAXAg2BFo0Jg3GFFIVCdAI1AgYBCQEBAwl8ix8tgQYBgRABAQ
X-IronPort-AV: E=Sophos;i="5.76,433,1592870400"; d="scan'208";a="543559198"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 16 Sep 2020 17:47:43 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id 08GHlhD0024008 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 16 Sep 2020 17:47:43 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 16 Sep 2020 12:47:42 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 16 Sep 2020 13:47:41 -0400
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 16 Sep 2020 12:47:40 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=iusCNFVSqz05dWaoQVJYRdaHjK+uo+HHiRqJb0grNtQYWscAwLiiwd0INLM5477AHv0/9kfJpQUtoeYARAJi3/whKIs1W1DGkohUp6nxH5H61S3chtqLVNRNDx2Sv+2jamdkbZ97Itl76MnCFp3Pt35rUViC0WwIM+fXe59opsCiHrx3oROR1v0VWQgN9IwnSTcihN9DeD1D3HyjRJy0IrGn26CSYi+oPRpp/9q1mbM3Q9EzRl+nOnfB/L/V5kr+Jqmsr9Hv0Zq3XAy3f1in0gjw6TGTN6xD101U//XxzHcyVdkjZ/w8eMEjOQaGZzfcRXTtG3J0rk5flFLnhyOXAg==
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=4uf57aUd98mjvqTePzFnXaZuIlisfinc7C5Szo5DlZg=; b=nx4uoEhqLTL4wX+3rmA6am5EuLdE85rJtMXKtco9NVqa8wB7wKA3mtWVjgsAdtVwYQIUm6NiKu+91KeaZg+gRrOoRWPKlZIcrKyNPeFbYxnq3saswn254IONaMvHw0Ft3Fg4VLGdjUPaUg5ANhce1VqZAt3RTRy0J0AW/pEwvb+P+253e5j5QHn2QZJBUssFBXD83gI0exnnR6CbiACuCI25PEJUh2U3rKNyOjbCSM6MM9nrQwz5HLwQQXJwf1xkE2Mu4ihPNutFuLhxBBpWCqvEF/o3Zt0MSNAgKJD1uOkQ7WYCSq+cx/wauSLMCLmmYwrkqRJsN4uxfxGK9mYf1w==
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=4uf57aUd98mjvqTePzFnXaZuIlisfinc7C5Szo5DlZg=; b=iqSC6E4UWa151Galcvo1jyhW2UJa0yirq4Ht0ZSggVDvdtodOzE/xulzMnVy0ls+wU3nblpNizYojPX1N6dLwH2SK1JJRfvOk3W6hu7f/Jr3YMRSioM+eo4XVcgRzM70MpulvbGzr3sVtrGsCVlyHRDaFKohZbku8gQQSahKSks=
Received: from BYAPR11MB2887.namprd11.prod.outlook.com (2603:10b6:a03:89::27) by BY5PR11MB4340.namprd11.prod.outlook.com (2603:10b6:a03:1bb::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Wed, 16 Sep 2020 17:47:39 +0000
Received: from BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::ed2a:6cdf:3bc4:dbf2]) by BYAPR11MB2887.namprd11.prod.outlook.com ([fe80::ed2a:6cdf:3bc4:dbf2%6]) with mapi id 15.20.3348.019; Wed, 16 Sep 2020 17:47:39 +0000
From: "Acee Lindem (acee)" <acee@cisco.com>
To: tom petch <ietfa@btconnect.com>, "Acee Lindem (acee)" <acee=40cisco.com@dmarc.ietf.org>, Chris Bowers <chrisbowers.ietf@gmail.com>, RTGWG <rtgwg@ietf.org>
CC: rtgwg-chairs <rtgwg-chairs@ietf.org>
Subject: Re: WG last call for draft-ietf-rtgwg-policy-model
Thread-Topic: WG last call for draft-ietf-rtgwg-policy-model
Thread-Index: AQHWdOBUMxhRDuxlwkqot1Yubab0gqlXfeEAgAEhWACAAcGmgIACqGcAgAPWtACAAUi+gIAAKJUAgAfB4QCAASN8AIAAH5AAgABN9AD//9HzgA==
Date: Wed, 16 Sep 2020 17:47:39 +0000
Message-ID: <A4D00913-668A-4A0C-8EB4-6C4ED850812F@cisco.com>
References: <CAHzoHbu7g7VifCVf4hEuvNkf46+3AG8_A6JhJdKQ5y2WN1njQA@mail.gmail.com> <CAHzoHbtCvr+9pALnTeV_SQ8fGzebrvHBJ0014Kpxkspd4G+n-A@mail.gmail.com> <DB7PR07MB53400AD2E7D7D741B708C7A1A22D0@DB7PR07MB5340.eurprd07.prod.outlook.com> <D97B9C42-A24C-40E7-93E4-27F344AC9A9A@cisco.com> <DB7PR07MB5340CCD0ABC8382B77C12CECA2280@DB7PR07MB5340.eurprd07.prod.outlook.com> <CAHzoHbtUoyXg7i3epHzOzmUi1A2bUaN6Un9+t5S+6r8aq4JQjw@mail.gmail.com> <DB7PR07MB534069339AB0EFD673CE58C9A2270@DB7PR07MB5340.eurprd07.prod.outlook.com> <F8ED3B80-AB3F-4000-A675-795235F0AFD6@cisco.com> <97D736FD-42BA-483A-9290-15202A678A4D@cisco.com> <DB7PR07MB5340BD58056B435F5ABC606AA2210@DB7PR07MB5340.eurprd07.prod.outlook.com> <6B7CCA52-0A9F-49BD-B390-6637EEA582D4@cisco.com> <DB7PR07MB5340B6FB8725469FBB6925D9A2210@DB7PR07MB5340.eurprd07.prod.outlook.com>
In-Reply-To: <DB7PR07MB5340B6FB8725469FBB6925D9A2210@DB7PR07MB5340.eurprd07.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.40.20081000
authentication-results: btconnect.com; dkim=none (message not signed) header.d=none;btconnect.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [136.56.133.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 119b3646-32bc-4c2a-169f-08d85a689b2c
x-ms-traffictypediagnostic: BY5PR11MB4340:
x-microsoft-antispam-prvs: <BY5PR11MB4340119CDCF86E37BD620091C2210@BY5PR11MB4340.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: s+mSbh2ieRjy//NiqIOp1OvyB6vgsIe+DJDJ3qeFAsyZSDFkpelU2BzFq9pp1y66naDH5Dqe6VUm7DmYiRi9czDssLAD1/GN5TO3dBTGremgIe6sEqJhlS5dZ20vKDGh3AI3A8oqu0xoelHEXXRSN7Lh2rEBHamndb6qqpbLXT6ZTRNLJX8EvbLmFWLSzkU2btRad+Nc+XnmzYXo2Izhhz8GhdB0Ju4d7g3RipT45ecchNwicqManeT8RAlDQZei1F/8xqwVVhdbAeRMPQrP9eDplm+erosLiYy4tpAS4Yms2BrP5ZTBN/eCDryDlM3NVty873nCA+rFj61qmjSlRIQ2qy7lfPH1SdfeuWUzMg6++fdOA3m/CFEN3J4l0XSt880A3utQ+2FKFfJlkEUsSw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:BYAPR11MB2887.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(39860400002)(136003)(396003)(376002)(366004)(346002)(26005)(6506007)(316002)(6512007)(296002)(53546011)(2616005)(8676002)(83380400001)(86362001)(186003)(2906002)(33656002)(478600001)(6486002)(8936002)(66476007)(64756008)(66556008)(66446008)(66946007)(110136005)(71200400001)(966005)(4326008)(36756003)(76116006)(91956017)(5660300002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: CJymqXDxlOoduMcek5kMXaK0UOtmNzSLvAq2NvthPVQY3rBKLgI3d77F1m76XKuIyC6K6Lc0j7P0JDcnpd3S2CbDPhAA4jUg8JVEgM7HUnJ1qSp1vpI5VlMVnkP09FtaghJ/ZVfxSXyK+8Xp7L/6mqAm0ZzuvBZlFEYtWv5g5Ss2FyRGhI+SC/NCcNJ3bF8kdJfoVu0zgOG/C2qU2lor8kvccQp3VK9vKgeJDFI7P5fuBKAsKWorUgGLI4O9V/GZj4OgSmz1Yl00NF4ioIcTc1u4ZXjzqYPvDfZqfnBB5gsDZi6rX5sNtzGLboKxJ/XMYvELX18iROhonzyoAya0to7deEICiqLFwcNTxZb5yrdiXzOgfDkz/Eniz/EbFkSrHWuz0rgxe3gW4tika1d1L86Y/wBVWnutjra3xg2GRKhOqmPnbqhp5+tD6U1FiXzsJ9iCfRrcPxnS6i9/9RH47P4e/9QQpv/Q7ha8YCXsFmYZpyAghuvCbA2ciqmRQPpuBVx+EELmN1z3J2LUuC3vGrzZjDPdbifx9y73FKGJkxVi04lFvB1l+W4EGsS6C175+/npxcnL3C/b9PabDYjotvWweF/8GQ50cR3Ag8BzpQ57S428bn/AAqXg26xBkn1hC6kzmhhuo+UgrBY6oQ6fxw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C166ED16401B74B8B16B3CB38EF1A42@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR11MB2887.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 119b3646-32bc-4c2a-169f-08d85a689b2c
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Sep 2020 17:47:39.7312 (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: 6TtByZUUJbOjEz7WfA8tJhde9zKAT3TXBktx2HbzbB2aSOMYLT/JeXHSNklEnTFR
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR11MB4340
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.12, xch-aln-002.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/6KsbkBbJOvOV6uNzF-3cTqNZ98Q>
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: Wed, 16 Sep 2020 17:47:48 -0000

Hi Tom, et al, 
I have clarified the usage of policy chain and added the normative language in the YANG description constraints - which I believe is the right approach. 
Thanks,
Acee

On 9/16/20, 12:33 PM, "tom petch" <ietfa@btconnect.com> wrote:

    From: Acee Lindem (acee) <acee@cisco.com>
    Sent: 16 September 2020 16:53
    To: tom petch; Acee Lindem (acee); Chris Bowers; RTGWG
    Cc: rtgwg-chairs
    Subject: Re: WG last call for draft-ietf-rtgwg-policy-model

    Hi Tom,

    On 9/16/20, 6:01 AM, "tom petch" <ietfa@btconnect.com> wrote:

        From: Acee Lindem (acee) <acee@cisco.com>
        Sent: 15 September 2020 21:37

        Hi Tom, Chris, et al,
        I've moved the non-normative sections to appendixes in the -22 version. Also, at the risk of being redundant, I included an explicit reference for the unpopular BGP sub-module prefixes.

        <tp>
        Looks good.

        Every time I read this, I see something:-(  So some trivia for as and when a new version is needed:

        container prefixes has 'is is'
    <acee>
    Fixed in -22.
    </acee>

        container conditions /returns control the/returns control to the/
    <acee>
    Fixed in -22
    </acee>

        and
        should or SHOULD? (an AD is bound to ask if we meant this:-)

    <acee>
    I think it should... Started a thread on this amongst YANG doctors. There is no consistency in published models on "description" statement validation. However, in times we've discussed this on the NETMOD list, these descriptions are normative.
    </acee>

        'chain' is probably worth expanding on.  It appears in 4.4 and is relied on in s.5 without ever a formal definition and it might not be obvious how it is represented in the YANG model. I infer that it is the leaf-list import-policy or export-policy but chain does not appear in the descriptions thereof.  So I think a sentence in 4.4 saying what a chain looks like as YANG would help as would a mention of chain alongside list in the description of export-policy and import-policy.  If my inference is wrong, then please tell me what a chain is!

    <acee>
    Good catch. I think the problem here is that "policy chain" is used for both the list of import or export policies and the list of statement within a called policy. This is clearly wrong and policy chain should only be used for the former.  Let me assure my co-authors agree.

    <tp2>
    Well yes, I think I coped with that one but it is more that I cannot program a chain in YANG the way I can in other languages, forward pointers, backward pointers and so on,  and an ordered by user leaf-list is not an immediately obvious substitute to so I would add in s.4/s.5
    'A policy chain is represented in YANG by a user-ordered leaf-list such as ...'
    and then in the YANG
    'This leaf-list implements a policy  chain as described in ...'

    Tom Petch
    Thanks,
    Acee
    </acee>

    Thanks,
    Acee

        Tom Petch

        Thanks
        Acee

        On 9/10/20, 6:10 PM, "rtgwg on behalf of Acee Lindem (acee)" <rtgwg-bounces@ietf.org on behalf of acee=40cisco.com@dmarc.ietf.org> wrote:

            Hi Tom,

            As previously noted, the BGP model augments the routing-policy model and not the other way around. Hence, resolution of BGP model issues is not a prerequisite for publication of this YANG model. AFAIK, none of the open issues with the BGP model are related to its augmentation of the routing-policy model.


            Now, I'd like to see the BGP model issues addressed and the model progress as much as you but there is absolutely nothing unusual regarding its treatment.

            Thanks,
            Acee

            On 9/10/20, 11:44 AM, "rtgwg on behalf of tom petch" <rtgwg-bounces@ietf.org on behalf of ietfa@btconnect.com> wrote:

                From: rtgwg <rtgwg-bounces@ietf.org> on behalf of Chris Bowers <chrisbowers.ietf@gmail.com>
                Sent: 09 September 2020 21:07

                RTGWG,

                I think there is rough WG consensus to submit draft-ietf-rtgwg-policy-model to the IESG for publication.  I will include a description of the discussion related to draft-ietf-idr-bgp-model in the shepherd writeup.  It will likely take the IESG several months to publish draft-ietf-rtgwg-policy-model.  If there are changes in draft-ietf-idr-bgp-model that make it desirable to change the text of the example in draft-ietf-rtgwg-policy-model before publication, then any changes in draft-ietf-rtgwg-policy-model will be discussed within RTGWG.

                <tp>
                Chris
                The other thought that I had was that the treatment of bgp-model, which I would regard as unusual, might attract some interesting comment from such as Genart or Opsdir reviews so it might be valuable to get those done earlier rather than later.

                Tom Petch

                Thanks,
                Chris


                _______________________________________________
                rtgwg mailing list
                rtgwg@ietf.org
                https://www.ietf.org/mailman/listinfo/rtgwg

            _______________________________________________
            rtgwg mailing list
            rtgwg@ietf.org
            https://www.ietf.org/mailman/listinfo/rtgwg