[Pce] When LSP belongs to multiple association groups of the same association type...

Dhruv Dhody <dhruv.ietf@gmail.com> Fri, 12 July 2019 15:19 UTC

Return-Path: <dhruv.ietf@gmail.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 52AE612060F; Fri, 12 Jul 2019 08:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.704
X-Spam-Level:
X-Spam-Status: No, score=-0.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 GGuafUWxIimo; Fri, 12 Jul 2019 08:19:19 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 1FD1612062E; Fri, 12 Jul 2019 08:19:11 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id o9so21144145iom.3; Fri, 12 Jul 2019 08:19:11 -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:cc; bh=eOpLB4+IA/oq5yZlX79SlAmOaS26sdn+NdS8ZT4jig0=; b=l7XRgKxUwiZNSr90wNLof/C9hfO9JUCRH079ZBqcFPDPNQ7+sAHaKSPPi1K3lI8vDC sUuH2t8XH9AzCj+JVMMajKaN1I9iSLxk/Fwm4PzFnvLmkW56WoN1N5Jt9aQCFSy8rNF8 +wKl21CDfbnVINUQ6QZjPswKX06jSlIOM/OxiJhlHaGErxb8XiPIoqUuJLPFsMEzutIv uOExvMLByzTnyZviXHUuSyfEs43Nm5Ca39LO1Z2T7cqddoqG9cN6Su89NXBP3BQ1PwrW yUVRziIS/6bkF72mmryTHxIUH5DIwG7uG8qrwg81B9ps6bl9HT985JCv8CUoC+8zckae I1zA==
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=eOpLB4+IA/oq5yZlX79SlAmOaS26sdn+NdS8ZT4jig0=; b=EZJPj+Fy2t9HacuVY+jE7QTayG0sd9tIqTqnOWwFCMozTklHn1idPAshUVV7val6pp s0DaIkmiPhg7n5Cg88pH2ytdtWZNGSarjlF3hHegy3eWTAkavvg/877IXRkWnu1C3VvE 7tpux4GIi3iM0DvkvhRa0B5hsHTW/qEyydUxatgojM8GCWf99M3DRueGvV2aK8EguCn/ haKJaAITzw7Ym/xdnRes4s/lmahRDDsKJVPI4i3wN5ICQRgd/14EIRNzMYVuUKiHuVkg AddA3gFN9JIryJ2NgyjXCa7qTggOnwUzUlGZvTxA40cKElUrwhqxCEO8k3DJYbyBf3/j u79Q==
X-Gm-Message-State: APjAAAWnYbPLXC764uVfdiVaufyKEbUHnJpjQf4bVdjPhA59Isug1lev c+TCA5U/YlRUjUBJWbGV+RMmgGMfJl2mb+FKs6TjXpIX
X-Google-Smtp-Source: APXvYqzFMrFjP7RrsVsFl4AJJszlKPNf3Z1bqf8/X9odkwBqNndrRvAcJIQMssqW5xzPK30xadlR2OEW2fZ5YwR8yqA=
X-Received: by 2002:a6b:f80e:: with SMTP id o14mr8451980ioh.1.1562944749968; Fri, 12 Jul 2019 08:19:09 -0700 (PDT)
MIME-Version: 1.0
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Fri, 12 Jul 2019 20:48:33 +0530
Message-ID: <CAB75xn6_qL3ryDMHDcX=ycy6ok5Ay-SFBYAXrg-5wDzANAhOEg@mail.gmail.com>
To: pce@ietf.org
Cc: draft-ietf-pce-stateful-path-protection@ietf.org, draft-ietf-pce-association-policy@ietf.org, draft-ietf-pce-association-diversity@ietf.org, draft-ietf-pce-association-bidir@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/q2W42fcJ-pmqhnT-XCIYGYoqNUA>
Subject: [Pce] When LSP belongs to multiple association groups of the same association type...
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: Fri, 12 Jul 2019 15:19:21 -0000

Hi Authors, WG,

Please refer to this exchange with Benjamin regarding
draft-ietf-pce-association-group

--

>    Multiple types of associations can exist, each with their own
>    association identifier space.  The definition of the different
>    association types and their behaviours is outside the scope of this
>    document.  The establishment and removal of the association
>    relationship can be done on a per LSP basis.  An LSP may join
>    multiple association groups, of different or of the same association
>    type.
>
> Is it possible for an LSP to join multiple association groups of the same
> type and then for configuration to be assigned to two groups in a manner
> that conflicts?  What procedure is used for conflict resolution in such a
> case?
>
[[Dhruv Dhody]] This should be handled per association type. I will
make sure that future documents that define association types include
text for this.

--

We should update the I-Ds that define association types to include text on
what should be done when an LSP tries to join multiple association group of
the same association-type? And if it is allowed, what to do in case of
conflicts.

There are cases where taking this input into account is straightforward.
Multiple association of a given type may either be natively supported (e.g.,
the diversity I-D already mentions it) or obviously excluded (e.g., the
bidirectional association falls into this kind).  Sometimes, the resulting
behavior may require more specification on failure techniques: e.g., what
should a PCC do if requested a 1:3 protection while it only supports dedicated
protection?

Request the authors to think about this and make suitable update based on the
individual association type. The post WGLC I-Ds could be updated as part of
directorate review update.

Thoughts?

Thanks!
PCE Chairs