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> Fri, 26 February 2021 07:26 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 8432A3A0652 for <pce@ietfa.amsl.com>; Thu, 25 Feb 2021 23:26:00 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 O8wAJvGrme1o for <pce@ietfa.amsl.com>; Thu, 25 Feb 2021 23:25:58 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 7BC183A03EE for <pce@ietf.org>; Thu, 25 Feb 2021 23:25:17 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id t25so5717231pga.2 for <pce@ietf.org>; Thu, 25 Feb 2021 23:25:17 -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=W8r32DZ0l97cgBsNgPW6vwWPTGivT63L2XT1Fvq8SnQ=; b=H10ufjtn3qGEt+QsUUOxXQYJA4hDoK/ip9XQor5TmVquMx5omyFjWPw6k53vWpopa8 YG8Xe+EvGBGJQi8qst9bCm6Nnr7uFoHZUdPu+nigdhhXsckVPBrNFrGKvEfAy5KzBfOd qS1BHJHcWpCRP6NRW70WOrm74Xm3a+T+i/2J0ApC/UGqe2mkotVeTC+3cvkuAI/bxFKv EOy71Idu+sx1Ldz+3q1KKBkQf6sYNGB6px7UR64mpwBYSTT3qrMTAju1ffz1tBr6uaMK J+5ccklQDsAm6CztuLjdbYpp6+cg7aJ2Del/36vR1zP2FNy2uumol/0jlcrhGt+EtIwt irrQ==
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=W8r32DZ0l97cgBsNgPW6vwWPTGivT63L2XT1Fvq8SnQ=; b=ehNqnFyyJGVYqwdtX075VLjzTIKFhyYrCsngsQii0DG7stxKyqKSXXCvdhVClDGZRf 2sXw5W1oQ5AzNougeKuT/RbSkWWqPU+k9DpTS5AsxHCHxXLYsA8VNqs3UPp/9aeUozX9 Sb5Z8fEbtSxFA8ggxmnocg6D/WQoB/KLKV/NXkq121etWUgbApX1FtVRvM2mD4spGiOM 0+aFjBV31KEDxYBi34YI7H5L05eyHtS6FHaTexZKgIB8P0YSjZL8DjyZkZrI6QvpY3LG 5AfA41oC8pi9wU3kCPgQ3oyQImP3ZeMS6Par5lxe2Uq9HNZJZfm3Yw3b2VLdSx4+ge38 qNNA==
X-Gm-Message-State: AOAM531lvGuniQVLp/1le1gPLjfvUTPdh64s9IDdgrKPUKb59LBs9Udp wphnTknaKTprdOjFdM/8pHolAoy0GdNpuML3RiZhBQ==
X-Google-Smtp-Source: ABdhPJzOs8UQCAtQ0AWh9xllYRfRR1om4bTIC5UfNYEOa/rVnMd8uGX4AayaOgI0T/gDXHxsUWZzSPC1axL5icSSSd0=
X-Received: by 2002:a63:111b:: with SMTP id g27mr1717983pgl.447.1614324316911; Thu, 25 Feb 2021 23:25:16 -0800 (PST)
MIME-Version: 1.0
References: <161426552149.16097.6516812692543543724@ietfa.amsl.com> <CAP7zK5Z8GdDghPhsknN6FVciV+vF61C8GGKC_LDm-oX9SgAq5w@mail.gmail.com> <CAP7zK5Z+iBLuJnsqNO=3oiUTsmS00ZCRDG4spvJA_tEdjgHUEQ@mail.gmail.com> <CAMGpriWChaGc+wcng61OP=SB98y7w9BFzpUqDx+NDnZ+TYP8hw@mail.gmail.com> <4278D47A901B3041A737953BAA078ADE19938F4E@DGGEML532-MBX.china.huawei.com> <71F28145-A366-41DF-8481-F65B86A1BF7F@cisco.com>
In-Reply-To: <71F28145-A366-41DF-8481-F65B86A1BF7F@cisco.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Fri, 26 Feb 2021 12:54:40 +0530
Message-ID: <CAP7zK5YHfQoLC3OKTj5tB+Jva5G3W2OasRX6bt5O8qZq0THQVg@mail.gmail.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
Cc: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>, Erik Kline <ek.ietf@gmail.com>, Julien Meuric <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>, The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>, "draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org" <draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/xytckcelsjFUOG_756ExvJPdK6E>
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: Fri, 26 Feb 2021 07:26:01 -0000

Hi Eric,

On Fri, Feb 26, 2021 at 12:45 PM Eric Vyncke (evyncke)
<evyncke@cisco.com> wrote:
>
> Shuping,
>
> The text is much better but may I still suggest the following:
>
> --- Proposed text by the authors --
>                  Further, this document specify a new TLV called ONLINK-IPV6-ADDRESS
>            to describe an IPv6 unnumbered adjacency for a link that does not
>            have an IPv6 address assigned.
>
> ---- Proposed text by Éric Vyncke ----
>                  Further, this document specify a new TLV called LINKLOCAL-IPV6-ADDRESS
>            to describe an IPv6 unnumbered adjacency for an interface that does not
>            have a global IPv6 address assigned.
> -----
> As a side note, I find " IPv6 unnumbered adjacency" a very strange wording as an IPv6 always has a 'number' in the sense that link-local address is always there.
>

Maybe we could say -

           Further, this document specifies a new TLV called
LINKLOCAL-IPV6-ADDRESS
           to describe an IPv6 adjacency for an interface that does not
           have a global IPv6 address assigned.

Erik suggested using ONLINK instead of LINKLOCAL for the TLV name. I
am not sure, to me using LINKLOCAL to match with RFC 8664 seems to be
okay. Any thoughts on that?

Thanks!
Dhruv



> Once the revised I-D is posted, then I am clearing my DISCUSS point (please send me an email when the revised I-D is posted)
>
> -éric
>
> -----Original Message-----
> From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
> Date: Friday, 26 February 2021 at 04:43
> To: Erik Kline <ek.ietf@gmail.com>, Dhruv Dhody <dd@dhruvdhody.com>
> Cc: Eric Vyncke <evyncke@cisco.com>, Julien Meuric <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>, The IESG <iesg@ietf.org>, pce-chairs <pce-chairs@ietf.org>, "draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org" <draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org>
> Subject: RE: Éric Vyncke's Discuss on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with DISCUSS and COMMENT)
>
>     Hi Erik,
>
>     Thank you for your comments! Please find the diff including the updates based on your comments. Thank you!
>
>     Diff: https://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht?url1=draft-ietf-pce-pcep-extension-for-pce-controller-12&url2=https://raw.githubusercontent.com/dhruvdhody/ietf/master/draft-ietf-pce-pcep-extension-for-pce-controller-13.txt
>
>     Best regards,
>     Shuping
>
>
>
>     -----Original Message-----
>     From: Erik Kline [mailto:ek.ietf@gmail.com]
>     Sent: Thursday, February 25, 2021 11:57 PM
>     To: Dhruv Dhody <dd@dhruvdhody.com>
>     Cc: Éric Vyncke <evyncke@cisco.com>; Julien Meuric <julien.meuric@orange.com>; pce@ietf.org; The IESG <iesg@ietf.org>; pce-chairs <pce-chairs@ietf.org>; draft-ietf-pce-pcep-extension-for-pce-controller@ietf.org
>     Subject: Re: Éric Vyncke's Discuss on draft-ietf-pce-pcep-extension-for-pce-controller-12: (with DISCUSS and COMMENT)
>
>     Dhruv,
>
>     Thanks for this.
>
>     >From my previous review, for reference only:
>
>     """
>     * Saying that the LINKLOCAL-IPV6-ID-ADDRESS TLV holds a pair of global IPv6
>       addresses seems confusing to me.
>
>       If the pair of global IPv6 addresses is to be considered "on link" in the
>       sense that IPv6 ND can be successfully be performed on the link for both
>       of these addresses, then "ONLINK" might be better than LINKLOCAL.
>
>     * Also, why are two interface IDs required?  I would have expected that only
>       the outgoing interface name/ID would be of relevance to the recipient of
>       a message with TLV in it?
>     """
>
>     Just for your consideration, in case "ONLINK" seems like it might be useful naming.
>
>     One more thing of note: I am terrible at naming!
>
>     On Thu, Feb 25, 2021 at 7:46 AM Dhruv Dhody <dd@dhruvdhody.com> wrote:
>     >
>     > 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 ?
>     > > >
>     > > >
>     > > >
>     >
>