Re: [Teas] [Last-Call] Opsdir last call review of draft-ietf-teas-gmpls-signaling-smp-10

Dan Romascanu <dromasca@gmail.com> Fri, 18 February 2022 05:46 UTC

Return-Path: <dromasca@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CEE53A0A8C; Thu, 17 Feb 2022 21:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 D437S12w6nff; Thu, 17 Feb 2022 21:46:38 -0800 (PST)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (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 177413A0A81; Thu, 17 Feb 2022 21:46:38 -0800 (PST)
Received: by mail-ej1-x630.google.com with SMTP id p9so12458693ejd.6; Thu, 17 Feb 2022 21:46:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IOIi2Vhsr1PmHifxGrqu5NkehZk+4Edl+MUXwMm6HkU=; b=HCwCIQTCdyInWt4+cQhqlhNzG/JPAtuB0To4OwUPwrqbMU9uWpYmIrx64LTiaBacwn nJkcQydwSZzjiMVbiHCUj8SWoSN/iFSd+4eB7hc9pqEuawwpW0Wr3htOeAdis7Gl8nYr bbp50fZH16Jfk8R5yZmDEBZDs+H1rMznO6HsHuQHXwkimNN5QjtgEgjd1+5AVZQm5DY2 TQVd1+qMaooROA1HlPXPTDlzeF8mG3+79fonOQAfVriOVKTmp+wPyjXVFdWg9ISO5Ukc 52i5NPsog9vqo5evUOIpOqtx9dWPD1GUvDvKRTzrozXBT2jTP3oDmH3iq4GiiNiVAR94 uqfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IOIi2Vhsr1PmHifxGrqu5NkehZk+4Edl+MUXwMm6HkU=; b=IEOdSnWmo7DdD7Ay42uFhYVk5jIErcPdHdjFh3nSudmY2K/M7hC8lR9+RZJvTpI0PB yM3ugo8Al13Bp8lAH2E0NnZ+6osI2dsvRI7W1UGJBEvPra2fV8Jqax9yyYLPRHjDZDyk zciFh9gRO20VR4CWbdc80fKzIQQgfX7SXurnO/9kEqQu6xupUv21rIs2nejmrBIj/NW9 pFKoPMPFqttB/rbXmJF4krE/Kx1ebSbrzl5RSwcRBHZAI0RCdrJRDio73fD0BxfXooIn 5pkIc/R28dnrkMmLH3nS1Tm+O8DgxFWzNZVhU/zjcopjA/8tlX8zVDPosjWc71F9MMxx r1jQ==
X-Gm-Message-State: AOAM5330CAvwdTSC7bnHl48OhC1pfvFR31m6nHttQTqK00cy8gSi311d DuHvYWX9joPhRB62JIpNdtHpgrVUz17FbNzXo3dXHy1z
X-Google-Smtp-Source: ABdhPJzwWOzRgXNjF3dKeDlAJgh1RO6yzHOVz/Tu7Crpjlbq6lv9nRQom58hUsViOd18pjre5rTg2s7CeqAgvVozRnw=
X-Received: by 2002:a17:906:bc99:b0:6ce:e0b6:52bf with SMTP id lv25-20020a170906bc9900b006cee0b652bfmr4855772ejb.313.1645163195721; Thu, 17 Feb 2022 21:46:35 -0800 (PST)
MIME-Version: 1.0
References: <164371679974.9237.1674072571446722747@ietfa.amsl.com> <oee7qoslrhtl.oee7qosmewz7.g1@dooray.com>
In-Reply-To: <oee7qoslrhtl.oee7qosmewz7.g1@dooray.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Fri, 18 Feb 2022 07:46:24 +0200
Message-ID: <CAFgnS4XDEyyEiXsNLM=DTnuJH=XhuVxEyouE77T+q1q9i1+dkw@mail.gmail.com>
To: Jeong-dong Ryoo <ryoo@etri.re.kr>
Cc: ops-dir@ietf.org, Last Call <last-call@ietf.org>, teas@ietf.org, draft-ietf-teas-gmpls-signaling-smp.all@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e0eae705d8446721"
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/RSZFp86hfokVBYQu7ebG4bj9zpg>
Subject: Re: [Teas] [Last-Call] Opsdir last call review of draft-ietf-teas-gmpls-signaling-smp-10
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Feb 2022 05:46:44 -0000

Hi Jeong-dong,

Thank you for your response and for addressing the issues that were raised
in my review. The proposed text for the Introduction section addresses my
concerns.

Regards,

Dan


On Fri, Feb 18, 2022 at 4:31 AM Jeong-dong Ryoo <ryoo@etri.re.kr> wrote:

> Dear Dan,
>
> Thank you for your review of this document. In an effort to address the
> issue you raised, the authors of this document prepared a new paragraph to
> add in the Introduction section as follows:
>
> [RFC8776] defines a collection of common YANG data types for Traffic
> Engineering (TE) configuration and state capabilities. It defines several
> identities for LSP protection types. As this document introduces a new LSP
> Protection Type, [RFC8776] is expected to be updated to support the SMP
> specified in this document. [draft-ietf-teas-yang-te] defines a YANG data
> model for the provisioning and management of TE tunnels, LSPs, and
> interfaces. It includes some protection and restoration data nodes relevant
> to this document. Management aspects of the SMP are outside the scope of
> this document, and they are expected to be addressed by other documents.
>
> Please, let us know if this is not sufficient to address your concerns.
>
> Best regards,
>
> Jeong-dong (on behalf of the co-authors)
>
>
>
>
>
> -----Original Message-----
> From:  "Dan Romascanu via Datatracker" <noreply@ietf.org>
> To:      <ops-dir@ietf.org>;
> Cc:      <last-call@ietf.org>;   <dromasca@gmail.com>;   <teas@ietf.org>;
>  <draft-ietf-teas-gmpls-signaling-smp.all@ietf.org>;
> Sent:  2022-02-01 (화) 21:00:54 (UTC+09:00)
> Subject: [Last-Call] Opsdir last call review of
> draft-ietf-teas-gmpls-signaling-smp-10
>
> Reviewer: Dan Romascanu
> Review result: Not Ready
>
> This document updates RFC 4872 and RFC 4873 to provide the extensions to
> the
> Generalized Multi-Protocol Label Switching (GMPLS) signaling to support the
> control of the Shared Mesh Protection (SMP) mechanism defined by ITU-T
> Recommendation G.808.3. It describes in details the operation of SMP with
> GMPLS
> Signaling Extension, the GMPLS Signaling Extension for SMP, and the
> updates to
> PROTECTION Object.
>
> I believe that the document is useful for operators runing GMPLS and SMP.
> The
> signaling aspects seem to be well defined. However, the document misses
> completly any operational and manageability considerations. Are they
> covered by
> other documents? Are updates required for any GMPLS management RFCs? Are
> there
> any configuration or alarms aspects that the operators should be aware
> about?
> What is the operational impact of upgrading networks to run SMP? These are
> parts of the questions I would expect to be addressed, or at least some
> pointers provided to existing documents (IETF, ITU-T) or future work.
>
> I would suggest that these issues be addressed before the document is
> approved
> for publication.
>
>
> --
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call
>
>