Re: [Pce] Éric Vyncke's Discuss on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with DISCUSS and COMMENT)

Dhruv Dhody <dd@dhruvdhody.com> Thu, 25 February 2021 15:46 UTC

Return-Path: <dd@dhruvdhody.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 E99643A1B72 for <pce@ietfa.amsl.com>; Thu, 25 Feb 2021 07:46:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=dhruvdhody-com.20150623.gappssmtp.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 QydtxWbddbhq for <pce@ietfa.amsl.com>; Thu, 25 Feb 2021 07:46:34 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 835803A1B6B for <pce@ietf.org>; Thu, 25 Feb 2021 07:46:34 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id o22so5206632pjs.1 for <pce@ietf.org>; Thu, 25 Feb 2021 07:46:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=AfHxFXz1xF2BlR+akW6khfyb4jDiX7oVasKWKhtfCC8=; b=Tjm7CIEfHGXHlNGGtKnPK6GTVCxZCFZV6rVBvSb6GODqNsw33I7fmiri2lxehJR4vy iUvURvEZzz7vEVunTBnKSwKB15fz50A3/Wz+16QYEXOeavLQmLX9zSxwCzfoJJolDJ37 iNcJ8Esa2bVtKLMXvMuARCgd39H2e4R/0xx+AXwYirsEfsYR4/+FkQ+Bg28UE5hbQxC3 r9rpAcslTq2zO105NITmLTiixWqovIZb38Uks0rSqegRS3kWCCSj5AVJ/ud9AB7KQDLG /rIY5Iq6soQcMpSDGErWS/SpBXVLHGOfokyDWCcmG1nbGC5OgZYrbwJ2UdVOyo64uiU8 wpKA==
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=AfHxFXz1xF2BlR+akW6khfyb4jDiX7oVasKWKhtfCC8=; b=chDu77AVQ29BTJQo2+lfzdUWaPO8Y3LQKd3D9IZML+5npeYi9D+SiZCcBMsjSwvyDc AxatpXinqYHHIWPu8CneC3kMZpoMhsFMsjV4jtMcit1ABbrUp2KfsD/ovch4Lt8G5b2q uOr+H+fFxREFbI2mPYMScU59FbB+nysbx5lfJBMnOZ1XKXiCla9gXGdsUrx56dzGjefk vyrdfQhTcZ2LFdzp+wSBQ7xUWe2kxGMkiNj988XcgIob0VSUhSYlkQ5zlss5BIsyfqAp nN87chm/fNjdfKCZ3B4BXCpezgNACRuFGm7wISOoWxszMuYm9x8EgKW4nw0m7J6Q+TsX sGig==
X-Gm-Message-State: AOAM531eznP6EXeseny5FuH2KWyjcrV07iJ+2Bz8vX4MNVQ67f7BFPXV qusBauLPEGBKFSbIx91E4mpDyx6LC9jqsfeu1C63Fw==
X-Google-Smtp-Source: ABdhPJxw5igTtDEnchrEC+21V4l+AO5WZdE9j4fPfvXDXRiEwZK928+qwZNxig9h/hXb0aHmnxuyTgyPa8l+uqbGM3w=
X-Received: by 2002:a17:90b:390b:: with SMTP id ob11mr3984780pjb.50.1614267994029; Thu, 25 Feb 2021 07:46:34 -0800 (PST)
MIME-Version: 1.0
References: <161426552149.16097.6516812692543543724@ietfa.amsl.com> <CAP7zK5Z8GdDghPhsknN6FVciV+vF61C8GGKC_LDm-oX9SgAq5w@mail.gmail.com>
In-Reply-To: <CAP7zK5Z8GdDghPhsknN6FVciV+vF61C8GGKC_LDm-oX9SgAq5w@mail.gmail.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Thu, 25 Feb 2021 21:15:58 +0530
Message-ID: <CAP7zK5Z+iBLuJnsqNO=3oiUTsmS00ZCRDG4spvJA_tEdjgHUEQ@mail.gmail.com>
To: Éric Vyncke <evyncke@cisco.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org, pce-chairs <pce-chairs@ietf.org>, pce@ietf.org, Julien Meuric <julien.meuric@orange.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/nP-p8dJNLdZvPBWcxW5eK9zhl6c>
Subject: Re: [Pce] Éric Vyncke's Discuss on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with DISCUSS and COMMENT)
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: Thu, 25 Feb 2021 15:46:36 -0000

Hi Eric,

I discussed this offline with one of the authors, who confirmed that
while NAI in RFC 8664 uses a pair, in this case, the pair is not
needed for the next-hop information and it can be updated as suggested
by you.

Thanks!
Dhruv

On Thu, Feb 25, 2021 at 8:50 PM Dhruv Dhody <dd@dhruvdhody.com> wrote:
>
> Hi Eric,
>
> On Thu, Feb 25, 2021 at 8:35 PM Éric Vyncke via Datatracker
> <noreply@ietf.org> wrote:
> >
> > Éric Vyncke has entered the following ballot position for
> > draft-ietf-pce-pcep-extension-for-pce-controller-12: Discuss
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/
> >
> >
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > Thank you for the work put into this document. I have not had time to review in
> > details though :( but I appreciated the detailed description as well as the
> > useful time diagrams.
> >
> > Please find below one blocking DISCUSS point (which may be my bad
> > understanding), some non-blocking COMMENT points (but replies would be
> > appreciated).
> >
> > I hope that this helps to improve the document,
> >
> > Regards,
> >
> > -éric
> >
> > == DISCUSS ==
> >
> > -- Section 7.3.1 --
> > LINKLOCAL-IPV6-ID-ADDRESS TLV: I fail to understand why there are two addresses
> > in this TLV while others have one one ? Also is 'local' and 'remote' really
> > global addresses ?
> >
> >
>
> Erik Kline had the same comment.
>
> The text and encoding is inspired by RFC 8664
> https://www.rfc-editor.org/rfc/rfc8664.html#section-4.3.2
>
> which says -
>
> IPv6 Link-Local Adjacency:
> Specified as a pair of (global IPv6 address, interface ID) tuples. It
> is used to describe an IPv6 adjacency for a link that uses only
> link-local IPv6 addresses. Each global IPv6 address is configured on a
> specific router, so together they identify a pair of adjacent routers.
> The interface IDs identify the link that the adjacency is formed over.
>
> A reference to RFC8664 and more description can be added.
>
> Thanks!
> Dhruv
>
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > == COMMENTS ==
> >
> > A minor comment: the abstract is clear but probably a little too long for an
> > abstract.
> >
> > -- Section 7.3 --
> > Just wonder why  LINKLOCAL-IPV6-ID-ADDRES is not mentioned in this section but
> > well in the next one ?
> >
> >
> >