From nobody Wed Mar 2 11:58:46 2022 Return-Path: X-Original-To: bier@ietfa.amsl.com Delivered-To: bier@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7A9D3A0C43; Wed, 2 Mar 2022 11:58:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.107 X-Spam-Level: X-Spam-Status: No, score=-1.107 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 LDfAAg3EGKw1; Wed, 2 Mar 2022 11:58:40 -0800 (PST) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 430893A0C3E; Wed, 2 Mar 2022 11:58:40 -0800 (PST) Received: by mail-yb1-xb33.google.com with SMTP id f38so5698041ybi.3; Wed, 02 Mar 2022 11:58:40 -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=9W2z+1TnOYJ2ZzcodSui/BQkTjzOPLmcFxjtfrY3LuE=; b=QWw48uqgPu05FoXKh9U6i0lOp9eybA8Mjd7ErC4vRpDOUj6oEa3cKaGVXV5szzwDAT r1aWAapfC14YOpzleSpZYZhofkLO4SPTLYmEeC1hnBgXyPEEbmAS7OSPw917lS7Ex1Bu zHgd/Q+Gu0PQ/QX+3UWv+rT2BWwm5xxKUI3ez2a0pwrfo7IS9HkSu+LUx6VwpKpofKcw +K6SDhrDu4PRN6lLanoP4v6fslQb+K1JOFpX3EWJNPhpnO6hBzruo1M2hJvRDDck2S9W +uV/cfXCbXzSvGbFk5/YxAZdSf3PeVGFTtts+B7pIOmcLJhw2pz+fhM1XLsRcMgyFCqo zuXw== 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=9W2z+1TnOYJ2ZzcodSui/BQkTjzOPLmcFxjtfrY3LuE=; b=57hcyi9zIW7Z4MLWLEPjisfeRU74Y8FLW4ohJF+K7M7aPnuWFzb/we+/sFV0aDykb8 6jycnnt7UaILWWD2gPp8EAKl8qsoRu4CbAg4lQrOfmt+gfhz13BGyTI9HZ9hpgPZM5Bm W2R2oQUH18dCTD/KOBHvSj6c+1xIrzBnRdAYOgfIYQBW4vsnU5//THYr4aFU3PKTzIlN ol5NFxDYNd4s9AyXO/b3DxkUkGBWSIrFD+Bxcr+e+iM839l21h4Ua17Prsurv2OYKycH s8z7FLbZclTgxEjLSpVrE6fC9BjF23mIwFaK9jXwg3ebo6G+KTeWNs9JxppH+dieiHbG AGDA== X-Gm-Message-State: AOAM530/0/hrWtkb+8+GLrTw5ZBQgcvpGyoZnucZlzRcOCIW81IOSGYM JdAhkEYiZWtaBW+sQDmnqCqg7C3uiuF7081N4XA= X-Google-Smtp-Source: ABdhPJwboDONe+NRNCNFokRcrFoklO4lDsdgUSraKRQVVEuJ9PS7ON55fblWp0B2m1qnKeNaC8x1if8DW8lKwceziXA= X-Received: by 2002:a25:4b84:0:b0:628:bc07:5fad with SMTP id y126-20020a254b84000000b00628bc075fadmr1126820yba.247.1646251119055; Wed, 02 Mar 2022 11:58:39 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Tony Przygienda Date: Wed, 2 Mar 2022 20:58:02 +0100 Message-ID: To: "Jeffrey (Zhaohui) Zhang" Cc: "Xiejingrong (Jingrong)" , draft-ietf-bier-lsr-ethernet-extensions , BIER WG , "senthil.dhanaraj.ietf@gmail.com" , "yangang@huawei.com" Content-Type: multipart/alternative; boundary="0000000000002995f905d941b584" Archived-At: Subject: Re: [Bier] Renaming draft-bier-lsr-ethernet-extensions to draft-bier-lsr-non-mpls-extensions? X-BeenThere: bier@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "\"Bit Indexed Explicit Replication discussion list\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2022 19:58:45 -0000 --0000000000002995f905d941b584 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Jeffrey, thanks for taking up the pen -- tony On Wed, Mar 2, 2022 at 8:18 PM Jeffrey (Zhaohui) Zhang wrote: > Hi, > > > > After offline communication, we learned that current editors can no longe= r > focus on this work, so I took over the pen and submitted > draft-ietf-bier-lsr-bier-non-mpls-extensions-00. > > I will present the changes in the coming IETF113 and hopefully we can mov= e > to WGLC. > > > > Thanks! > > Jeffrey > > > > > > Juniper Business Use Only > > *From:* Jeffrey (Zhaohui) Zhang > *Sent:* Tuesday, February 8, 2022 9:12 AM > *To:* Xiejingrong (Jingrong) ; Tony Przygienda < > tonysietf@gmail.com>; draft-ietf-bier-lsr-ethernet-extensions < > draft-ietf-bier-lsr-ethernet-extensions@ietf.org>; BIER WG ; > senthil.dhanaraj.ietf@gmail.com; yangang@huawei.com > *Subject:* Renaming draft-bier-lsr-ethernet-extensions to > draft-bier-lsr-non-mpls-extensions? > > > > Hi Jingrong, Gang, Senthil, > > > > Thanks for refreshing it. Now that most our Chinese friends are back afte= r > the spring festival holidays, I want to bring back this discussion from > more than two years ago and move forward. > > > > Here is the history: > > > > 1. The draft was initially draft-dhanaraj-bier-isis-non-mpls-extension= s, > but it explicitly states that non-ethernet encap is outside the scope > 2. As a result, I suggested to replace =E2=80=9Cnon-mpls=E2=80=9D with= ethernet =E2=80=93 it > became draft-dhanaraj-bier-lsr-ethernet-extensions in Jan 2019 > 3. In April 2019 I raised the question among the co-authors if we > should remove the =E2=80=9Cethernet-only=E2=80=9D restriction and go b= ack to =E2=80=9Cnon-mpls=E2=80=9D > 4. There were on-and-off discussions among co-authors and the latest > email that I can found was on 11/30/2020, arguing **for** changing > back to non-mpls > 5. After that the draft has been stalled. There were a few nudges > offline to the editors but nothing happened other than refreshing > > > > I think we should rename it and move forward now =E2=80=93 after two year= s. The > co-authors were on those old discussions so should all have the context = =E2=80=93 > can the editors respond here if we should rename? > > > > If you have concerns about going back to non-mpls, please discuss it here= . > > > > Thanks. > > > > Jeffrey > > > > > > Juniper Business Use Only > > *From:* Xiejingrong (Jingrong) > *Sent:* Monday, January 31, 2022 12:35 AM > *To:* Tony Przygienda ; > draft-ietf-bier-lsr-ethernet-extensions < > draft-ietf-bier-lsr-ethernet-extensions@ietf.org>; BIER WG > *Subject:* RE: Last call to authors of draft-bier-lsr-ethernet-extensions > for update of draft ... > > > > *[External Email. Be cautious of content]* > > > > Hi, > > > > I have just re-published the draft. > > The submission needs xml v3 format and the previous version of the draft > is old, so a text file has to be used as the base. Hope the authors could > update it soon after the spring festival to use xml to reflect the latest > references. > > > > thx. > > jingrong. > > > > > > *From:*Tony Przygienda > > *To:*draft-ietf-bier-lsr-ethernet-extensions < > draft-ietf-bier-lsr-ethernet-extensions@ietf.org>;BIER WG > > *Date:*2022-01-20 05:03:24 > > *Subject:*Last call to authors of draft-bier-lsr-ethernet-extensions for > update of draft ... > > > > Authors of the above draft, we need IANA assignments and registries > contained in draft-bier-lsr-ethernet-extensions to progress further WG > drafts here. The authors have been given couple of heads up behind the > scenes to re-publish the according draft given it expired 6 months ago. > > > > As WG chair I would request with this email for an update/re-publish so I > can call the IANA assignments. If we don't see a re-publish within the ne= xt > 2 weeks we will consider to call/assign an editor to the draft to keep it > alive. > > > > thanks > > > > -- tony > > > --0000000000002995f905d941b584 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Jeffrey, thanks for taking up the pen
=
-- tony

On Wed, Mar 2, 2022 at 8:18 PM Jeffrey (Zh= aohui) Zhang <zzhang@juniper.net> wrote:

Hi,

=C2=A0

After offline communication, we learned that current= editors can no longer focus on this work, so I took over the pen and submi= tted draft-ietf-bier-lsr-bier-non-mpls-extensions-00.

I will present the changes in the coming IETF113 and= hopefully we can move to WGLC.

=C2=A0

Thanks!

Jeffrey

=C2=A0

=C2=A0

Juniper Business Use Only<= u>

From: Jeffrey (Zhaohui) Zhang <zzhang@juniper.net> Sent: Tuesday, February 8, 2022 9:12 AM
To: Xiejingrong (Jingrong) <xiejingrong@huawei.com>; Tony Przygienda <= tonysietf@gmail.co= m>; draft-ietf-bier-lsr-ethernet-extensions <draft-iet= f-bier-lsr-ethernet-extensions@ietf.org>; BIER WG <bier@ietf.org>; senthil.dhanaraj.ietf= @gmail.com; yan= gang@huawei.com
Subject: Renaming draft-bier-lsr-ethernet-extensions to draft-bier-l= sr-non-mpls-extensions?

=C2=A0

Hi Jingrong, Gang, Senthil,

=C2=A0

Thanks for refreshing it. Now that most our Chinese = friends are back after the spring festival holidays, I want to bring back t= his discussion from more than two years ago and move forward.=

=C2=A0

Here is the history:

=C2=A0

  1. The draft was initially draft-dhanaraj-bier-isis-non-mpls-extensions, but it explicitly states that non-eth= ernet encap is outside the scope
  2. As a result, I= suggested to replace =E2=80=9Cnon-mpls=E2=80=9D with ethernet =E2=80=93 it= became draft-dhanaraj-bier-lsr-ethernet-extensions in Jan 2019
  3. In April 2019 I raised the question among the co-authors i= f we should remove the =E2=80=9Cethernet-only=E2=80=9D restriction and go b= ack to =E2=80=9Cnon-mpls=E2=80=9D
  4. There were on= -and-off discussions among co-authors and the latest email that I can found= was on 11/30/2020, arguing *for* changing back to non-mpls
  5. After that the draft has been stalled. There were a fe= w nudges offline to the editors but nothing happened other than refreshing<= u>

=C2=A0

I think we should rename it and move forward now =E2= =80=93 after two years. The co-authors were on those old discussions so sho= uld all have the context =E2=80=93 can the editors respond here if we shoul= d rename?

=C2=A0

If you have concerns about going back to non-mpls, p= lease discuss it here.

=C2=A0

Thanks.

=C2=A0

Jeffrey

=C2=A0

=C2=A0

Juniper Business Use Only<= u>

From: Xiejingrong (Jingrong) <xiejingrong@huawei.com&= gt;
Sent: Monday, January 31, 2022 12:35 AM
To: Tony Przygienda <tonysietf@gmail.com>; draft-ietf-bier-lsr-ethernet-exte= nsions <draft-ietf-bier-lsr-ethernet-extensions@ietf.org&= gt;; BIER WG <bier@ietf.org>
Subject: RE: Last call to authors of draft-bier-lsr-ethernet-extensi= ons for update of draft ...

=C2=A0

[External Email. Be cautious of co= ntent]

=C2=A0

Hi,

=C2=A0

I have just re-published the draft.=C2=A0<= /u>

The submission needs xml v3 format and the previous = version of the draft is old, so a text file has to be used as the base. Hop= e the authors could update it soon after the spring festival to use xml to = reflect the latest references.

=C2=A0

thx.

jingrong.

=C2=A0

=C2=A0

To:draft-ietf-= bier-lsr-ethernet-extensions <draft-ietf-bier-lsr-ethernet-ex= tensions@ietf.org>;BIER WG <bier@ietf.org>

Date:2022-01-2= 0 05:03:24

Subject:Last c= all to authors of draft-bier-lsr-ethernet-extensions for update of draft ..= .

=C2=A0

Authors of the above draft, we need IANA assignments= and registries contained in draft-bier-lsr-ethernet-extensions to progress= further WG drafts here. The authors have been given couple of heads up beh= ind the scenes to re-publish the according draft given it expired 6 months ago.

=C2=A0

As WG chair I would request with this email for an u= pdate/re-publish so I can call the IANA assignments. If we don't see a = re-publish within the next 2 weeks we will consider to call/assign an edito= r to the draft to keep it alive.

=C2=A0

thanks

=C2=A0

-- tony

=C2=A0

--0000000000002995f905d941b584--