[mpls] Intended status of draft-ietf-mpls-spl-terminology

Greg Mirsky <gregimirsky@gmail.com> Fri, 16 October 2020 14:59 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD953A0F96; Fri, 16 Oct 2020 07:59:20 -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, 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 (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 82n0FpjORXm8; Fri, 16 Oct 2020 07:59:19 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 12F263A0F93; Fri, 16 Oct 2020 07:59:18 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id l28so3292909lfp.10; Fri, 16 Oct 2020 07:59:18 -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=S18vxW/EZB3lUK/Lw0vvK/FXR4ts6s0keR0rA8N224k=; b=mj9tVmt1+CfFeawZ4cCJARF8pwhFaEV8zRCwfmFJgAo78r6kgIFmCyIFmKjDx7JD3C PlyueDrZePu2YGhOShmLmiK5SCAGRrKWKWTFpT8Ug+RZpXYZdr0W6puByFcIxZJyYFQI XXV//CdMCAPbnzBYkxtOpkOGGAYsrKSjrK4YbXICmjJHITAcvIEuoDMS1+oK+CXVkeOP kXbrQSg5SdzZaIwUjuLum+WUZL+c+EKZHmgen0gKIxCcTTpobCc6QL9PripcFg91Fz+O dK6evYWhtjWCwvw1XdUzFB9TB/a76WAH3J9FGDFBLEAPi3jPPdmvA74vVyediNSxVCow mqiQ==
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=S18vxW/EZB3lUK/Lw0vvK/FXR4ts6s0keR0rA8N224k=; b=f1JEAzJZ1RvetfBy5/hklJV69EejRM219JiWp4UMf7/372IIthjaNXSHf5GzcgBZcD ajzQ623XRMywLm1SFQWIF08iuj2D/QCL5dEo/52EXjGtH4BhZUJkn/S6XHRXxI7RMZfY dKF+lA+7HVAKCSleM5liYSKGizqGKW7eVqLKIZQqe07DxrT/JoiDVpvoir/xMUrQccOf uzZx2nyHNLkwzVR/PRe4ditTDA9yQ3h/RJV7jQ0HCBzVrDRnac3dR9HXRrLSf9lln+Bm /NGRONa+2gij0E89bShTSrnIfIQNTN418ZlpL5YS0wNLcvjCasvXs1iy5e7EPRETs7mA Fcmw==
X-Gm-Message-State: AOAM532WVoQRixB4E97KFJt6JzCZCC29fEryCLr1Yitg19BuHFQcQYGv bw92p9J0HGJrvVqgSfCELMH3qJn1dDE04ivquMeJI36g
X-Google-Smtp-Source: ABdhPJx5I5i28idiKFWVobhFqe2weOVG1M7sdzkIbas+J1OBLFegAUQb8YEO/HU0cwvee7NPR6hTm1fJBW9TA2T1iDY=
X-Received: by 2002:a05:6512:529:: with SMTP id o9mr1437023lfc.331.1602860356625; Fri, 16 Oct 2020 07:59:16 -0700 (PDT)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 16 Oct 2020 07:59:04 -0700
Message-ID: <CA+RyBmViLvqf6hZzsB704MC95fdYc36v7tb96itzHWaGeLaRKw@mail.gmail.com>
To: draft-ietf-mpls-spl-terminology@ietf.org
Cc: mpls <mpls@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002e6a4105b1cb02a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/1LB4n-NDNYHAbDm2aEctHTx1Mps>
Subject: [mpls] Intended status of draft-ietf-mpls-spl-terminology
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2020 14:59:21 -0000

Dear Authors,
hope you can clarify the intended status of the draft. I've noticed that
the datatracker reflects it as Informational while the document itself
states that is on the Standards track. As I understand RFC 2026 a document
is either on Standards or non-Standards, e.g., Informational track.
Thank you in advance.

Regards,
Greg