From nobody Mon Dec 13 18:36:11 2021 Return-Path: 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 63D083A0D7C; Mon, 13 Dec 2021 18:36:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.097 X-Spam-Level: X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 9mGiChhte06z; Mon, 13 Dec 2021 18:36:05 -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 0BD7E3A0DE3; Mon, 13 Dec 2021 18:36:05 -0800 (PST) Received: by mail-pg1-x52a.google.com with SMTP id m15so16144573pgu.11; Mon, 13 Dec 2021 18:36:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=m5BGXjZRUhBj73aA1qk0jsLfVDgMiskWPB8i3Mmg1xo=; b=N7lskjtt1x+XAKPHSGlFPl22uzPQrxTM60i6xYVEqlQCYTo5s2kF7miOQyafVdFeto UR46luZONP0j6Mj6vtrCUbM7m7VSVAyFQudupsXA73A2elhE42JfjKqFgLi/LZVHiyd9 DQccSjfLr+ztPsreNmoZMesQ/WoyNVvsWiLKtndlxN5e9GVcrmvKXnH8sI2MozF2mjBf P2Ti7ka7uZTCxpgoBq0XaeXsrrhkWcQjgj6I3EKEAqvbEGjYVcvbuTPF1fvbjz/SC9PY H7AtFrwguIIVentEaBswTpUOxLA81faEIWu5WdMy0iT9pD0RBA/KvGiQaX2e5zDjq2Bq t/Pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=m5BGXjZRUhBj73aA1qk0jsLfVDgMiskWPB8i3Mmg1xo=; b=0zTJvFfVgFM/3/+0WOOvKZoNojuLmZT3AVg4igWAUo4vb8w/7lAZ94wq6lY86HpTu0 T/iLTg8NFOP9T4/lefnFV//Bqwg56inyo+wvxhFgnu34ZubhwQKTHLanWNriVoT84bhH uL7EjoINEjtlQeFHFIPBsA8yhtzzccEo6aMKXThhPMEgAEPLFqwrj6Q10N+TMxB7fONe SrbXU8US9Sem5u+msf3IEa9toUT7yzq0S8wBxuOKcEMfZyBJWlpItQofeGqKeMIz5YS+ fAbCuACD34a3HSzn0fH2YfNNxbp4xnGovJCxlsEauMCrWf0bAsg+jpLJKoyvVWNUT7lk fmtA== X-Gm-Message-State: AOAM531lbel8H/7jaejOD2v8mrYwIlvMfRiknJAnRHsyfLkvxAVPwo0s i92iVtPDEbmXy7Nfch+jMRU= X-Google-Smtp-Source: ABdhPJzZBrdMCg+NDpopgv6HPVtJVnLLhFjJjXmbaVr+RVhs/JVttJrhw4b6OB5P9A2MJa1I4454FA== X-Received: by 2002:a05:6a00:10d3:b0:4a4:e516:826f with SMTP id d19-20020a056a0010d300b004a4e516826fmr1758464pfu.70.1639449363104; Mon, 13 Dec 2021 18:36:03 -0800 (PST) Received: from smtpclient.apple (47-209-11-64.mmlkcmtc01.res.dyn.suddenlink.net. [47.209.11.64]) by smtp.gmail.com with ESMTPSA id j23sm11774673pgn.40.2021.12.13.18.36.01 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Dec 2021 18:36:02 -0800 (PST) From: Kireeti Kompella Message-Id: <198DFF50-B9C6-4719-A16D-DDECE9C28770@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_FC56DA91-C560-438A-80CC-D084BF655204" Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Date: Mon, 13 Dec 2021 18:36:00 -0800 In-Reply-To: Cc: Kireeti Kompella , Tarek Saad , mpls , "yingzhen.qu@huawei.com" , "mpls-chairs@ietf.org" , "draft-kompella-mpls-larp@ietf.org" To: Xufeng Liu References: X-Mailer: Apple Mail (2.3654.120.0.1.13) Archived-At: Subject: Re: [mpls] MPLS-RT for draft-kompella-mpls-larp X-BeenThere: mpls@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2021 02:36:10 -0000 --Apple-Mail=_FC56DA91-C560-438A-80CC-D084BF655204 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Xufeng, Thanks for your review. Please see inline for replies. > On Dec 3, 2021, at 13:28, Xufeng Liu = wrote: >=20 > Hi Authors, > I have reviewed the document and I think that the document is useful = by addressing a gap for network operations. The approach is technically = sound and easily implementable. The document is coherent. It is ready to = be considered for WG adoption. > Here are a few comments that can wait until the WG adoption. > 1. The aging/timeout mechanism used by Ethernet ARP is not mentioned = in this document. Is it intended to recommend implementing such a = mechanism? >=20 Thanks for this reminder! We will add more on this in a future = revision. > 2. It is understandable that the initial use case came from MPLS over = Ethernet, but is this mechanism Ethernet dependent, or usable for other = types of hardware (at least in theory)? >=20 This mechanism is general. However, the details for MPLS over some = other hardware type may be a little bit different (for example, = depending on the media, the hardware address may contain media addresses = in addition to labels). So, for now, the focus is on MPLS over = Ethernet. > 3. Sec 3.3. says that =E2=80=9C1. checks if it has reachability to = H3.=E2=80=9D Is this check for =E2=80=9CIP reachablity=E2=80=9D, or MPLS = reachability with an available lable stack that can be used to reach H3? >=20 Fixed. > 4. In Figure 3. of Sec 5.1., there is =E2=80=9C ... (3 octets)=E2=80=9D.= Should it be =E2=80=9C2 octets=E2=80=9D here? Also, if these 2 octets = are not used, why 6 is chosen as the hardware address length? >=20 3 octets (clarified). > Thanks, > - Xufeng >=20 > On Mon, Nov 8, 2021 at 11:19 AM Tarek Saad > wrote: > Hi Xufeng/Yingzhen/Rakesh, >=20 > =20 >=20 > You have been selected as potential MPLS-RT reviewers for = draft-kompella-mpls-larp-10. >=20 > =20 >=20 > Note to authors: You have been CC'd on this email so that you can know = that this review is going on. >=20 > =20 >=20 > Reviews should comment on whether the document is coherent, is it = useful (ie, is it likely to be actually useful in operational networks), = and is the document technically sound? We are interested in knowing = whether the document is ready to be considered for WG adoption (ie, it = doesn't have to be perfect at this point, but should be a good start). >=20 > =20 >=20 > Reviews should be sent to the document authors, WG co-chairs and WG = secretary, and CC'd to the MPLS WG email list. If necessary, comments = may be sent privately to only the WG chairs. >=20 > =20 >=20 > If you have technical comments you should try to be explicit about = what *really* need to be resolved before adopting it as a working group = document, and what can wait until the document is a working group = document and the working group has the revision control. >=20 > =20 >=20 > =20 >=20 > Can you review the document by November 26, 2021? >=20 > =20 >=20 > Regards, >=20 > Tarek (as MPLS WG chair) >=20 > _______________________________________________ > mpls mailing list > mpls@ietf.org > https://www.ietf.org/mailman/listinfo/mpls --Apple-Mail=_FC56DA91-C560-438A-80CC-D084BF655204 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = Xufeng,

Thanks for = your review.  Please see inline for replies.

On Dec = 3, 2021, at 13:28, Xufeng Liu <xufeng.liu.ietf@gmail.com> wrote:

Hi Authors,

I have reviewed the document and I think that the document is useful by addressing a gap for network operations. The approach is technically sound and easily implementable. The document is coherent. It is ready to be considered for WG adoption.

Here are a few = comments that can wait until the WG adoption.

1. The aging/timeout mechanism used by Ethernet ARP is not mentioned in this document. Is it intended to recommend implementing such a mechanism?



Thanks= for this reminder!  We will add more on this in a future = revision.

2. It is understandable that the initial use case came from MPLS over Ethernet, but is this mechanism Ethernet dependent, or usable for other types of hardware (at least in = theory)?



This = mechanism is general.  However, the details for MPLS over some = other hardware type may be a little bit different (for example, = depending on the media, the hardware address may contain media addresses = in addition to labels).  So, for now, the focus is on MPLS over = Ethernet.

3. Sec 3.3. says that =E2=80=9C1. checks if it has reachability to H3.=E2=80= =9D Is this check for =E2=80=9CIP reachablity=E2=80=9D, or MPLS reachability = with an available lable stack that can be used to reach = H3?



Fixed.

4. In Figure 3. of Sec 5.1., there is =E2=80=9C ... (3 octets)=E2=80=9D. = Should it be =E2=80=9C2 octets=E2=80=9D here? Also, if these 2 octets are not = used, why 6 is chosen as the hardware address length?



3 octets (clarified).

Thanks,

- Xufeng


On Mon, Nov = 8, 2021 at 11:19 AM Tarek Saad <tsaad.net@gmail.com> wrote:

Hi = Xufeng/Yingzhen/Rakesh,

 

You have = been selected as potential MPLS-RT reviewers for = draft-kompella-mpls-larp-10.

 

Note to authors: You have been CC'd = on this email so that you can know that this review is going on.

 

Reviews should comment on whether = the document is coherent, is it useful (ie, is it likely to be actually = useful in operational networks), and is the document technically = sound?  We are interested in knowing whether the document is ready to be considered for WG adoption (ie, it = doesn't have to be perfect at this point, but should be a good start).

 

Reviews should be sent to the = document authors, WG co-chairs and WG secretary, and CC'd to the MPLS WG = email list. If necessary, comments may be sent privately to only the WG = chairs.

 

If you = have technical comments you should try to be explicit about what = *really* need to be resolved before adopting it as a working group = document, and what can wait until the document is a working group document and the working group has the revision control.

 

 

Can you review the document by = November 26, 2021?

 

Regards, =

Tarek (as = MPLS WG chair)

_______________________________________________
mpls = mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

= --Apple-Mail=_FC56DA91-C560-438A-80CC-D084BF655204--