IETF Logo Mail Archive

Re: [Pce] FW: New Version Notification for draft-stone-pce-local-protection-enforcement-00.txt

Dhruv Dhody <dhruv.ietf@gmail.com> Sun, 26 July 2020 12:06 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 8B4863A0DE5 for <pce@ietfa.amsl.com>; Sun, 26 Jul 2020 05:06:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 k-KYYzOaD2iT for <pce@ietfa.amsl.com>; Sun, 26 Jul 2020 05:06:52 -0700 (PDT)
Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) (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 1E7CF3A0DE4 for <pce@ietf.org>; Sun, 26 Jul 2020 05:06:52 -0700 (PDT)
Received: by mail-il1-x12e.google.com with SMTP id i138so4892575ild.9 for <pce@ietf.org>; Sun, 26 Jul 2020 05:06:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=yrRvciQWUuG+GmENQwqTOtyy9EWT4vsycTxseg+N0Hk=; b=hx2sF8xybVbcZ5Z1iAB1ayS1jTgnUqQfYAMlFhcGCIc1YxGwdEiuIAC+WP626trugf Gqmpkz2AKgR4ch6KKVRiTHR8+4YeHMtt6+68+whOpQgX7EnnCHvRgd3pSlpSvm/Zzo/Y 4bCwAAEG8pJ3wHwhYgF9nY+Nwu3MuROzOd1j3tDB7hBTSmX0zu1/zUBSllLVKqbJT5rO D+K/GeOfXFA90ErR4lAvWvhdEwkVcFuzUXXvKFw8NDA9mJ008gs9b6Da4W1w8JPJK2UX o8tLnO4Jah3UtxIniC6O2uMKXM1LaRJAbvfO3MBI8y1OZKcmjXtSzYHfykTgAoetOZRN iRWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=yrRvciQWUuG+GmENQwqTOtyy9EWT4vsycTxseg+N0Hk=; b=l+h2mX+40fxkenhZNfhLFp9oS0I18E65Ppv3a4ti44NutHWHyFVWQgEcHFP2HRGLpe X1Ry3A2/r9iqtSWjspqyOHkGuehKywJDbFLojCA8n/GZ9N7T9b/E/h0PIpCERkmY5/gy hA9zvbmeoDgOzI3OBzEhDGH4+MP/Oc8ksg381n82S1Gva/s3LmxzeM8QErYNXBr0fplz AeedDFK+MHTqc+c6/j4jykhY7zkZu6xe3iuIpm6NGUQpECkyLtIxLODa1sZWGCT422d0 8DkucZvvlshn1GSsdr8mQ0sDejoJkNEByBp20V8AzfRgEyUDs9JwSc4/itUkPZvPwE/w 5gNw==
X-Gm-Message-State: AOAM533+RIMG33MlptTVSudBEFOWnAipedoXqVjf1UCpM1801yNN39gM V+MaluKmE/wcIyLZZxeQ2x1i/rtgNbVP7ocQFyM=
X-Google-Smtp-Source: ABdhPJwNh4WwrECQjyI6i+d29zmIZPBf4FKpJ69F2RKnklufkeyEjFiR5i4e2fJuRYE2ldXUBFAlRxm9ufoCIezGznc=
X-Received: by 2002:a92:c087:: with SMTP id h7mr18016282ile.279.1595765211165; Sun, 26 Jul 2020 05:06:51 -0700 (PDT)
MIME-Version: 1.0
References: <158316673618.27361.7017725094379697473@ietfa.amsl.com> <C161A604-BB57-4347-A816-FE50CF164F68@nokia.com>
In-Reply-To: <C161A604-BB57-4347-A816-FE50CF164F68@nokia.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Sun, 26 Jul 2020 17:36:14 +0530
Message-ID: <CAB75xn6JB=JLteD2NzsmGrQLcKQXW0Ef7hwssFni+PLHZMpUGA@mail.gmail.com>
To: "Stone, Andrew (Nokia - CA/Ottawa)" <andrew.stone@nokia.com>
Cc: "pce@ietf.org" <pce@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/lmQNXwJTIcPRkLf8JeAXRv59eMo>
Subject: Re: [Pce] FW: New Version Notification for draft-stone-pce-local-protection-enforcement-00.txt
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: Sun, 26 Jul 2020 12:06:54 -0000

Hi Andrew,

Do you think an update to RFC 5440 is required (with meta-data set in
the document header)?
Based on the description of the flag field it feels like an update
would be needed -

  o  L flag: As defined in [RFC5440] and further updated by this
      document.  When set, protection is desired.  When not set,
      protection is not desired.  The enforcement of the protection is
      identified via the E-Flag.


BTW, thanks for section 4 it helps!

Maybe add an explicit backward compatibility section. Consider a PCC
that supports your extension, and sets the E flag to 1 and a PCE that
does not support your extension will ignore it and behave as before
and thus not enforce local protection, and there would be no way for
the PCC to know about it! Not sure if we need some sort of capability
exchange here?

Thanks!
Dhruv

On Fri, Mar 6, 2020 at 10:45 PM Stone, Andrew (Nokia - CA/Ottawa)
<andrew.stone@nokia.com> wrote:
>
> Hi PCE WG,
>
> This draft was updated to include the following:
>
> - Draft renamed to reflect this is for "local" protection enforcement (used to be called path-protection)
> - new co author
> - Added more text regarding the various use cases / why a user may want these options
> - Added text discussing situations of no preference / "no not care"
>
> Thanks
> Andrew
>
>
>
> On 2020-03-02, 11:32 AM, "internet-drafts@ietf.org" <internet-drafts@ietf.org> wrote:
>
>
>     A new version of I-D, draft-stone-pce-local-protection-enforcement-00.txt
>     has been successfully submitted by Andrew Stone and posted to the
>     IETF repository.
>
>     Name:               draft-stone-pce-local-protection-enforcement
>     Revision:   00
>     Title:              Local Protection Enforcement in PCEP
>     Document date:      2020-03-02
>     Group:              Individual Submission
>     Pages:              8
>     URL:            https://www.ietf.org/internet-drafts/draft-stone-pce-local-protection-enforcement-00.txt
>     Status:         https://datatracker.ietf.org/doc/draft-stone-pce-local-protection-enforcement/
>     Htmlized:       https://tools.ietf.org/html/draft-stone-pce-local-protection-enforcement-00
>     Htmlized:       https://datatracker.ietf.org/doc/html/draft-stone-pce-local-protection-enforcement
>
>
>     Abstract:
>        This document aims to clarify existing usage of the local protection
>        desired bit signalled in Path Computation Element Protocol (PCEP).
>        This document also introduces a new flag for signalling protection
>        strictness in PCEP.
>
>
>
>
>     Please note that it may take a couple of minutes from the time of submission
>     until the htmlized version and diff are available at tools.ietf.org.
>
>     The IETF Secretariat
>
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

v2.23.0 | Report a Bug | By Email