[Pce] Shepherd Review of draft-ietf-pce-association-policy-12
Hariharan Ananthakrishnan <hari@netflix.com> Sat, 03 October 2020 21:44 UTC
Return-Path: <hari@netflix.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323E33A08C3 for <pce@ietfa.amsl.com>; Sat, 3 Oct 2020 14:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level:
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (1024-bit key) header.d=netflix.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 fMjMEywzdG-7 for <pce@ietfa.amsl.com>; Sat, 3 Oct 2020 14:44:10 -0700 (PDT)
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) (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 4B21F3A07B0 for <pce@ietf.org>; Sat, 3 Oct 2020 14:44:10 -0700 (PDT)
Received: by mail-io1-xd2c.google.com with SMTP id g7so5389615iov.13 for <pce@ietf.org>; Sat, 03 Oct 2020 14:44:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netflix.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=+77q/XEPdWAOqq+G7bFYzGvAYdDrJHu+XUjlBew6mbE=; b=B1iMeVZcUJ7km5hhfmQes3X+MqCt7S1DtVx0UUORvqRegqFlBYglIo1K7EDjB8BL8j zDZ4/a+1FuK9iHiwzrChNqvKbLKzzVFzkHrFEx/macwdWod3rrkMENj5zJZEE/KwTdgA KuhL5pyvpT4/5rQ6r03UflDJZSjs/O1Oa0JN8=
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:cc; bh=+77q/XEPdWAOqq+G7bFYzGvAYdDrJHu+XUjlBew6mbE=; b=gAs+BfNWp6wSVjgMZbsGfOax/B7QkzUHwWlZafbwD0+5oOYcTNQyWOgZpNopS3G0o/ YYGjE12LAreI9VlpigyDUEgRwBqK6TvYL/q4XQFFIIS+AGFCO3P2sFyK13e8ATVXotUj rRPFVDXE/pownQKOrgRuKy5t9igNTfvu/B1aY0rWEu8IMnY/WD7Z1+85uH2j/CK34W0z KvXLbgbcW1gOMFCKxNNZrMmf3DKuuW7GKF2DK96OuTV8UI0hKTgHVTfI+Tk2M7HMbHae UpZp1C0DIlLhYe80wyoGfwsj5w/kKRZIA8jBgaI/PVpm9YkF8f7xqW38Mw03FDjfTVdZ 3L3Q==
X-Gm-Message-State: AOAM532kGb1orDYg9ZMLKG0lFo4+mlOGrBESqXFQ4OLP66m1v1zR3/M/ sSrThEg3IicbgHjvcSXD5rO0Y7a8r88Wt4S2fWxT+w==
X-Google-Smtp-Source: ABdhPJw9vbFnkVFnk7FfARBENS052xgBmC05FQxkZOm8sIDYO4L3fXqJSEcU4JWC8yrSBnd3PG9GxxwMqhg/n5MpvYE=
X-Received: by 2002:a05:6602:2f07:: with SMTP id q7mr6319941iow.191.1601761449144; Sat, 03 Oct 2020 14:44:09 -0700 (PDT)
MIME-Version: 1.0
From: Hariharan Ananthakrishnan <hari@netflix.com>
Date: Sat, 03 Oct 2020 14:43:58 -0700
Message-ID: <CAL70W4pkwjYdjO9dOc36LuFn=39fgd9X=BCR60p9802jo3dERA@mail.gmail.com>
To: slitkows@cisco.com, msiva282@gmail.com, jefftant.ietf@gmail.com, Jonathan Hardwick <jonathan.hardwick@metaswitch.com>, Mahend Negi <mahend.ietf@gmail.com>, c.l@huawei.com
Cc: pce@ietf.org
Content-Type: multipart/alternative; boundary="00000000000031380c05b0cb265f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/TSVb9fllbTtiWUHr0KZoX7ZC5pc>
Subject: [Pce] Shepherd Review of draft-ietf-pce-association-policy-12
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Oct 2020 21:44:12 -0000
Hi Authors, Please find the review comments below: Title OLD Path Communication Element (PCE) communication Protocol (PCEP) extension for associating Policies and Label Switched Paths (LSPs) NEW Path Communication Element (PCE) Communication Protocol (PCEP) extension for associating Policies and Label Switched Paths (LSPs) 1. Introduction OLD [RFC5440] describes the Path Computation Element communication Protocol(PCEP) which enables communication between a Path Computation Client(PCC) and a Path Control Element (PCE), NEW [RFC5440] describes the Path Computation Element Communication Protocol(PCEP) which enables communication between a Path Computation Client(PCC) and a Path Computation Element (PCE), 2. Terminology OLD PCC: Path Computation Client. Any client application requesting a path computation to be performed by a Path Computation Element. NEW PCC: Path Computation Client; any client application requesting a path computation to be performed by a Path Computation Element. OLD PCE: Path Computation Element. An entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints. NEW PCE: Path Computation Element; an entity (component, application, or network node) that is capable of computing a network path or route based on a network graph and applying computational constraints. 3. Motivation OLD Similarly, a PCC could request a user- or service-specific policy NEW Similarly, a PCC could request a user-specific or service-specific policy 3.1 Policy based Constraints OLD In the context of policy-enabled path computation [RFC5394], path computation policies may be applied at both a PCC and a PCE. NEW In the context of Policy-Enabled Path Computation Framework [RFC5394], path computation policies may be applied at either a PCC or a PCE or both. OLD The PCC may also apply user- or service-specific policies to decide NEW The PCC may also apply user-specific or service-specific policies to decide OLD The user- or service-specific policies applied to PCC and are passed to the PCE along with the Path computation request, in the form of constraints [RFC5394] NEW The user-specific or service-specific policies applied to PCC are passed to the PCE along with the path computation request, in the form of constraints [RFC5394] 4. Overview OLD This document defines a new Association type, called “Policy Association” (TBD1), based on the generic ASSOCIATION object. NEW This document defines a new association type, called “Policy Association” of value 3, based on the generic ASSOCIATION object. OLD This capability exchange for the PAT (TBD1) MUST be done before using the policy association. NEW This capability exchange for the PAT MUST be done before using the policy association. OLD Thus the PCEP speaker MUST include the PAT (TBD1) in the ASSOC-Type-List TLV NEW Thus the PCEP speaker MUST include the PAT in the ASSOC-Type-List TLV 5.1. Policy Parameters TLV OLD 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=TBD2 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ NEW 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=48 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ OLD The type of the POLICY-PARAMETERS-TLV is TBD2 NEW The type of the POLICY-PARAMETERS-TLV is 48 Thanks, Hari
- [Pce] Shepherd Review of draft-ietf-pce-associati… Hariharan Ananthakrishnan
- Re: [Pce] Shepherd Review of draft-ietf-pce-assoc… Mahend Negi
- Re: [Pce] Shepherd Review of draft-ietf-pce-assoc… Hariharan Ananthakrishnan