proposed example text and question on draft-ietf-rtgwg-policy-model

Chris Bowers <cbowers107@gmail.com> Wed, 10 June 2020 21:23 UTC

Return-Path: <cbowers107@gmail.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 838E03A1522; Wed, 10 Jun 2020 14:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 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, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 OrC44cYQP6WB; Wed, 10 Jun 2020 14:23:33 -0700 (PDT)
Received: from mail-oo1-xc29.google.com (mail-oo1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AC113A150C; Wed, 10 Jun 2020 14:23:33 -0700 (PDT)
Received: by mail-oo1-xc29.google.com with SMTP id x17so809621oog.6; Wed, 10 Jun 2020 14:23:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=49kgdKPC9Cwqx/6yGvsA+VU0Z+yUXdo6v+4ozAJ+8/E=; b=kik200yO1HSbRMb4lNTsoCK8PiVuvm+nr4ZxpjdXUhlYoJiump5pT/P404LJ4ctYzr mqx71bu32mOn9QbTFDN/L3slZlN7KW9XIj5fyCho1oOWcxVSc9BRC9qmW4PjQfzGVZDr z5FQF87ixcOjsxd00j1ZtC1buaegXsZ8cImK0CAgJIwSaa48FxgN0Ce/94u1BVpGLueN T3sRAtSQlCh0GYZFvF10ychQIYV8vuU6NxY9rQMdZr2bgBCJPLxAJ7HHUsbQc2Eo/v4U PYTTM2hYP9YwVrTY1zj+3TCBbD+MIVrVh1qBos4iahXUM9xJ6swlbt3cXV4Bpk1z4lTJ PIXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=49kgdKPC9Cwqx/6yGvsA+VU0Z+yUXdo6v+4ozAJ+8/E=; b=Qie5K8aN/7kt5fv6hONfA2opTg7jng2Jd7brJ2GpAUWrH+dcP0uVsNzMODtvjQZnKM 2VxfWvnGnV1XAbQATUZ7WQ1ormw6Y4Eps0pn6FXVZ8q0iWTxSQD2cCSXdKUJubXWJX7a WCGMeL48RrPD2k4dn0iCsq1Adwsx/+Cb9OaiWaELL4oMAlOT+GNt+ISebNKNdHPhUTVi 5ij+KrXpPTpOes9VCTZrmT5udlF4HqfV+DQuA6L806LwKgFVYU/sNTfRdh+E+FW20KxN KEemyI/zXuzxrnwJVfi5l6n70GySnp1o0RGmfqs4KwqAGAXxXTS2lpzTiEgiu/3fw568 lhZA==
X-Gm-Message-State: AOAM530eqHDIvDfqwsMHUm3i0i8IwGaXVszYW+O+SVY5p8SySMvaCNJm Ke9dPq1nKTtAs0gRG/mNPiRrLj2u9fseQKSiFcy+vDK/dtk=
X-Google-Smtp-Source: ABdhPJxT5LQ51Nm+Kci4jhNCjfiq7nmrHWp4lHhCX6rl9cVlTE4Ljtadgud8lJ5+XaZ9v9xFqtrz4yqg/ch6YxSsycs=
X-Received: by 2002:a4a:decf:: with SMTP id w15mr4176304oou.8.1591824211948; Wed, 10 Jun 2020 14:23:31 -0700 (PDT)
MIME-Version: 1.0
From: Chris Bowers <cbowers107@gmail.com>
Date: Wed, 10 Jun 2020 16:23:24 -0500
Message-ID: <CAMTSGm3uf+KU_0N6Qp46aMBKDnmrU4rsMopEZmzGfzEXpbSCZw@mail.gmail.com>
Subject: proposed example text and question on draft-ietf-rtgwg-policy-model
To: draft-ietf-rtgwg-policy-model@ietf.org, rtgwg@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b2df3a05a7c174a7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/CLKdIOIn6ob5QbnU5l6rokTM5FI>
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, 10 Jun 2020 21:23:35 -0000

I would like to propose adding the following example to the text of
draft-ietf-rtgwg-policy-model
to better illustrate how the model will work in practice with routing
policies involving IGPs.
The proposed text is shown below.

I think that the example below also illustrates a problem with the naming
of what is currently called "import-level" and "set-import-level".  In the
example, the export policy called
"export-all-OSPF-prefixes-into-ISIS-level-2" uses the "set-import-level"
 action.  As far as I can tell, it only makes sense to use
"set-import-level" in an export policy, and not in an import policy.  If
this is the case, wouldn't it make more sense to call it "set-export-level"?

===========
Proposed text for new IGP routing policy example:

This example illustrates the import and export policies corresponding to
the following scenario.

All routes that are learned via OSPF advertisements should get installed in
the RIB.

All routes in the RIB that have been learned from OSPF advertisements
corresponding to

OSPF intra-area and inter-area route types should get advertised into ISIS
level 2 advertisements.



          <policy-definitions>

           <policy-definition>

             <name>import-all-OSPF</name>

             <statements>

               <statement>

                 <name>term-0</name>

                 <conditions>

                   <match-prefix-set>

                     <prefix-set>all-prefixes</prefix-set>

                   </match-prefix-set>

                 </conditions>

                 <actions>

                   <policy-result>accept-route</policy-result>

                 </actions>

               </statement>

             </statements>

           </policy-definition>

              <policy-definition>

             <name>export-all-OSPF-prefixes-into-ISIS-level-2</name>

             <statements>

               <statement>

                 <name>term-0</name>

                 <conditions>

                   <match-prefix-set>

                     <prefix-set>all-prefixes</prefix-set>

                   </match-prefix-set>

                   <match-route-type>

                     <proto-route-type>ospf-internal-type</proto-route-type>

                   </match-route-type>

                 </conditions>

                 <actions>

                   <set-import-level>

                     <import-level>isis-level-2</import-level>

                   </set-import-level>

                   <policy-result>accept-route</policy-result>

                 </actions>

               </statement>

             </statements>

           </policy-definition>

         </policy-definitions>


==========

Thanks,
Chris