[Idr] Comments on draft-zhang-idr-sr-policy-template

Nat Kao <pyxislx@gmail.com> Thu, 14 March 2024 09:08 UTC

Return-Path: <pyxislx@gmail.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 D4304C14F614 for <idr@ietfa.amsl.com>; Thu, 14 Mar 2024 02:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AILFmlCm0qb7 for <idr@ietfa.amsl.com>; Thu, 14 Mar 2024 02:08:11 -0700 (PDT)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67C21C14F68A for <idr@ietf.org>; Thu, 14 Mar 2024 02:08:11 -0700 (PDT)
Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5684ea117a3so940560a12.0 for <idr@ietf.org>; Thu, 14 Mar 2024 02:08:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710407289; x=1711012089; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=k7XB6NeTpSwyTd0sW3l1mIjWU1vv0qkqWMJ7HEPfQI8=; b=jkJJg3OYnl5OyGItMJ/PJx1Pu6eyOjcApc9uwQ3FfLOJ49uzqkvx6WmqDPar7rt0cG cbyXp/aHQjRKEJUKvqjPmEtAKzrhR9Icz60vTYL752MaP4hVGZsEzBDCfW5weuK92PVb oArIY0ZS/mydM7lijnNBUe2EN4slqVvbSrCQqmE7ELZq7MRja0cXZKWCCQLeVE9ni7fc 4L0gYwmkuWDhEO+Ri42UClH7wM6Hzh2ks+WKHlbn7uZVFo5L5Nybxdpi2ZGIeescTUqo 3yuC9GK+uZZFcIXEaZkprR3JFN5la7l+CVarEmv1ov7GHnRiqgHD7R440uQ1REw4wc4a 4QMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710407289; x=1711012089; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=k7XB6NeTpSwyTd0sW3l1mIjWU1vv0qkqWMJ7HEPfQI8=; b=M/oT9B0tceSKyq6PVkkZFKDpcfCzNvPa+YJKOq4am1GPsoahyyiiLB6E0NIlloqK0P WlEVuqVm4x26fvKXFxuQ3WuHmrGj+fWOH8zpP5L02ZBC7v9/yMII7F3nIcJhMvYmulTK cV96YwFb8IKoiIo+zhnqpV+gOdkVOoDFzybg6zAp3tAZ5SlILc4WgWl35/UR1IBuff4S NsfubECQUVD1Q1aAWdIHJeMEwy6A5KUjgEIVR+e0SFOG/WI7MC6Wyf+9FO0Z7oZsxCdv kRekmKAsJvpCF0IxPQ8NKcSeWNGv12yo6348VjxbjF7/Ox3RXfkKuggeRj7pAeFQcdqs uQ2g==
X-Forwarded-Encrypted: i=1; AJvYcCW++jjxGsTOklgQiyWk4ioLDwG4erJUPdVGKkWgexAJGctgXFAQkNvJ5iVqMgTfMrrNeCp2Cq8ee9p6KGs=
X-Gm-Message-State: AOJu0Ywzqtt4JIS1mnkQOb1mwHCnYGzpPzg3LKNWeq8zbJoxc/uVUFoO QpWZYH+is97kBBy1ESdg0xAhx0EYLixNBJrTcLOEHlAR4NytZT2Zx4SNA7cGSMuckvxwMNj/pEF DGlVfta0QJsiSm37L4OWhzrYSVEQ=
X-Google-Smtp-Source: AGHT+IHPDxlO7O0dQx6BLXKlH4BmpK8Tei9S8Xq/WM440OKU5pdqAjdJ6rVC11Lmq4QPIlkFPJ1oQCMhXXYmqT/z4vY=
X-Received: by 2002:a17:906:a415:b0:a46:1f6d:3047 with SMTP id l21-20020a170906a41500b00a461f6d3047mr745296ejz.4.1710407289006; Thu, 14 Mar 2024 02:08:09 -0700 (PDT)
MIME-Version: 1.0
From: Nat Kao <pyxislx@gmail.com>
Date: Thu, 14 Mar 2024 17:07:32 +0800
Message-ID: <CAKEJeo6TUhz8MSu2aDxTBkaayQwvydPdaRK=rQ8KmsNxe=KJug@mail.gmail.com>
To: zhangka@huawei.com, idr@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e1f6d006139b3a63"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/doinU5MCP7KtDsYtwYjGnB6br50>
Subject: [Idr] Comments on draft-zhang-idr-sr-policy-template
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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, 14 Mar 2024 09:08:11 -0000

Hi, Ka.

I believe this draft provides a handy extension to the SR-Policy SAFI.
It would be nice if we can clarify some details of the procedure.

Consider the following case on headend H1:

CP1<E1, C1>:
    <BSID=2000,
     SL(Weight=W1):<S1, S2, S3>,
     SL(Weight=W2):<S4, S5, S6>,
     TemplateID=100>

Template 100:
    <BSID=4000,
     PolicyCandidatePathName="Template4k"
     SL(Weight=W11):<S11, S12, S13>,
     SL(Weight=W21):<S24, S25, S26>,
     ENLP=4>

- When CP1 is received by H1 over BGP, what exact characteristics would CP1
have?
 * For Sub-TLV types that appear at most once(BSID, ENLP, ...),
    would the value specified in CP1 override the value specified in
Template 100?
   More precisely, which BSID would CP1 have? 4000 or 2000?
 * For Sub-TLV types that can appear multiple times(SL, ...), do we merge
them?
   More precisely, what SLs would CP1 have?
 * I guess the CP1 validation process occurs after referring to Template
100. Am I correct?

- It's worth mentioning how to deal with the CP when the template changes.
  For example, when:
    * The template is added after receiving the CP.
    * The template is removed.
    * The template is modified.

Thanks,
Nat