[Pce] Backward compatibility with earlier version of draft-ietf-pce-segment-routing

Dhruv Dhody <dhruv.ietf@gmail.com> Sat, 02 February 2019 03: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 5D85B130EE0 for <pce@ietfa.amsl.com>; Fri, 1 Feb 2019 19:19:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, RCVD_IN_DNSWL_NONE=-0.0001, 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 9u8VYGnZPjYJ for <pce@ietfa.amsl.com>; Fri, 1 Feb 2019 19:19:49 -0800 (PST)
Received: from mail-io1-xd35.google.com (mail-io1-xd35.google.com [IPv6:2607:f8b0:4864:20::d35]) (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 561D0130EB8 for <pce@ietf.org>; Fri, 1 Feb 2019 19:19:49 -0800 (PST)
Received: by mail-io1-xd35.google.com with SMTP id r200so7431197iod.11 for <pce@ietf.org>; Fri, 01 Feb 2019 19:19:49 -0800 (PST)
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=Bb4peZ32hAJjsbUlcvwYd188cnCD9Hd8TmEVKWT4VHw=; b=KPbq5e6ZwpsnRmTRCnr1CtqHhj+qQ8u5mc/17cg4/MsUKSXHLA99w+tykhTrgnff2e f4I4Vi9vvBTScuI+Yx8YwYvwjeOQQoM7Mqc/+6Tepx5O3gUgJGwKJC1R7fPPdFru8b2Z Jthvlq4d1G+nlgH9dC6UaLxwtirA4x2JrqXYeccUQYGYXr9uvn4qhxYwbWh4E05SDLHz P246/5kZJABH8E8kU0FtYPx+ZXlEefk/xFT/v8BDV7eyeJD9bH75hn2dvwQhIXUVLCWK rewWUms3RlfECqsNifbckKa2a4xN3L9AN5ktgOunQGTCrFwFjxGnqaY3GcWMO8XiYZUv p5Ug==
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=Bb4peZ32hAJjsbUlcvwYd188cnCD9Hd8TmEVKWT4VHw=; b=I0tFIpxD9LeqbluH4G28lLxppgElPuUseWk2ifLuTKSAcRFdxjYBMyDGd+SC89hZv8 Xdf5dPuqdS85glZL+cNAYnr4XWoP+F2Eozj4W1AdE2KKLkb/Fa8u/o5xtslK5sCLrIy5 R5tuQ9fKAppVGv1PdwxhpZqiORWd3JtOyGWFRUUfvR6ZEL7uXR/0PwurOnNuYsD8QS3y tnNPvnIfP/1uSoODRZw7i+DoC/63LvK4ljBCbhqiWMVj9LMxNYfKQ2Wgka9m3GvUtHBq XRvcgvQYuPEMCGrtBLtFxBlMbVMAycbR08Wcj+qpoEBCGJ/HcdSlSafhwCxyGM/6lGr/ XMBg==
X-Gm-Message-State: AHQUAubmANRjypoAmW7Eg/UMXPHBKn4vq+ODVqHf7TNdDSKWwCX6PmLI FxpYzq0d4H6MoJi8Bns+ARm8gqtxSxEQJmpsgVfnUeah
X-Google-Smtp-Source: AHgI3IYyOuetOObztfKUDw9KCq2K86S2kVh2DU+53kCfu+e4P9hOVplOJ4JR2EKPNQ2My9PGtg6ClKpbRqRvZdLUsY4=
X-Received: by 2002:a6b:39c6:: with SMTP id g189mr12290037ioa.255.1549077588292; Fri, 01 Feb 2019 19:19:48 -0800 (PST)
MIME-Version: 1.0
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Sat, 02 Feb 2019 08:49:12 +0530
Message-ID: <CAB75xn6Kqt=gP0w9Gjk+Ce4qToRtstdV67CXAEic9bshgD98hw@mail.gmail.com>
To: pce@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/_XGg6S94O8RjDohXLHsDIZEunTo>
Subject: [Pce] Backward compatibility with earlier version of draft-ietf-pce-segment-routing
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, 02 Feb 2019 03:19:51 -0000

Hi WG,

To accommodate earlier implementations of PCEP-SR (before the path
setup type capability exchange was changed), we added this text to
allow backward compatibility with older versions -

   https://tools.ietf.org/html/draft-ietf-pce-segment-routing-14#section-7

   Some implementations, which are compliant with an earlier version of
   this specification, do not send the PATH-SETUP-TYPE-CAPABILITY TLV in
   their OPEN objects.  Instead, to indicate that they support SR, these
   implementations include the SR-CAPABILITY-TLV as a top-level TLV in
   the OPEN object.  Unfortunately, some of these implementations made
   it into the field before this document was published in its final
   form.  Therefore, if a PCEP speaker receives an OPEN object in which
   the SR-CAPABILITY-TLV appears as a top-level TLV, then it MUST
   interpret this as though the sender had sent a PATH-SETUP-TYPE-
   CAPABILITY TLV with a PST list of (0, 1) (that is, both RSVP-TE and
   SR-TE PSTs are supported) and with the SR-CAPABILITY-TLV as a sub-
   TLV.  If a PCEP speaker receives an OPEN object in which both the SR-
   CAPABILITY-TLV and PATH-SETUP-TYPE-CAPABILITY TLV appear as top-level
   TLVs, then it MUST ignore the top-level SR-CAPABILITY-TLV and process
   only the PATH-SETUP-TYPE-CAPABILITY TLV.

It has been a while since RFC8408 was published and this document
updated, and you might have already updated your implementations to
the latest standard.

- Are there any older implementations, still in the field that needs
to inter-operate with other pcep speakers that are running the latest
standard?
- If yes, can they be patched to latest standard in a planned manner,
without impacting the network operations?
- Please shout out the impact if the above text is removed.
- Further, if you have a valid rationale to keep the text, would you
be fine with changing MUST to SHOULD in the text?

Please respond by 8th Feb. You may choose to reply directly to the
chairs/AD instead of mailing list if you wish.

Thanks!
Dhruv (for the PCE chairs)