Re: [babel] Work to do

Donald Eastlake <d3e3e3@gmail.com> Mon, 26 March 2018 20:54 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9FF11242F5; Mon, 26 Mar 2018 13:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 RzxjRYClRFVF; Mon, 26 Mar 2018 13:54:35 -0700 (PDT)
Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 1FA63124234; Mon, 26 Mar 2018 13:54:35 -0700 (PDT)
Received: by mail-io0-x231.google.com with SMTP id r18so24912579ioa.1; Mon, 26 Mar 2018 13:54:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DO+jfMaAsRRDeCFIDv2W90zkdhMVq7iE1FuapIEc7xU=; b=cwmyP0dktCBdXwZg4RXYcqSekHJhZxKGcEJTjpegOhxBIVblq4NHzIcYBg6/ScxnyI DYlR1FW2eSlgHJ6LPXmbCMT/FZft8zJHEwIWsFJGrn2O+9Z+h8mFm/KV0GQRhwEspBu+ Y7R/6A9L5MQpjz8kyoBdNJ08ARvJ9zMqyoSfzFMa3rkIIg0rRmxsSoSFAp5d56ozORJX iK0Z8xPZndWvkj0BaKsGGmgZCJ0WkQ9t5lYv/PfD7QNwj+Lfg49R38oitCpkd9aKXE/W Trie78j2u+YHkR7CxddYvEKHA9u/zWzBClAYA9J4VHC27f9n7DJT827lJkatchkTT8Vd mZ5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DO+jfMaAsRRDeCFIDv2W90zkdhMVq7iE1FuapIEc7xU=; b=p45exoiFLGIS4CFoMMMwT3OpdzH2o3i/imQN1+tR+C4wuO5byQP+D0EIJ5+ayWSOB7 0mayPUjXydIMRaomUX3GF4Ks5DbnrVGnhXEW4s3YEGvB+tbS/9IyH0DDXO+iI3fmwNdG SutGUHkxXrW4xLGuMwIwJ4bXScyw2rdPJ6Ivwne0v27mvOopb9prYLNHKTnuUQ0pTUxr cVZBuhR0Gky0Kf1SvJHT26TCx1u2b9E9gRBxmJDD8kJ3Sjxw/Rc/cqYioM5d484HSh+n 1ZnwiNd+F8MKbWP4/Pz+u0lRQkCK0jeD6AoZJwudtK0wA+4/Exoxs08OHkRJzxOCit3v aNug==
X-Gm-Message-State: AElRT7H8kvzuF9GE3fz8DyIxl8iBW0MjHnj74iDCvPftPn+d1Dtodtvn GWACjceIbecR9Vui0jm8TzytEBUoG57hmOJnY40=
X-Google-Smtp-Source: AG47ELuKNglmx/zrt742AaQtjGlXeje01HmNrq9a5ujjkY7hpNrXkEfGEdGwJY+KZzf5Axatl2VvzjywEWReRFDGrGU=
X-Received: by 10.107.3.71 with SMTP id 68mr44085058iod.66.1522097674197; Mon, 26 Mar 2018 13:54:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.58.193 with HTTP; Mon, 26 Mar 2018 13:54:18 -0700 (PDT)
In-Reply-To: <871sg6lk86.wl-jch@irif.fr>
References: <87k1u1uekt.wl-jch@irif.fr> <CAF4+nEF8h26Vg+NasZjP061UdsPCqRbqoTi8Ltr6jVYE8fy9fw@mail.gmail.com> <871sg6lk86.wl-jch@irif.fr>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 26 Mar 2018 16:54:18 -0400
Message-ID: <CAF4+nEH8C--Bz3wD7aW7B4oH8qzEj8r9+UcDzTZA4NA+9Sj7VQ@mail.gmail.com>
To: Juliusz Chroboczek <jch@irif.fr>
Cc: Babel at IETF <babel@ietf.org>, babel-chairs@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/C1oMKtG2R2yfF391iman8YHf9NQ>
Subject: Re: [babel] Work to do
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 20:54:37 -0000

Hi Juliusz,

On Mon, Mar 26, 2018 at 3:17 PM, Juliusz Chroboczek <jch@irif.fr> wrote:
>
> >> 1. draft-ietf-babel-rfc6126bis
> >>
> >> This has been in last call, like, forever. We're still waiting for IESG
> >> review, let's please make it happen. Donald, Russ, could you please poke
> >> the responsible AD?
>
> > While I think there is pretty strong support for this draft in the WG, I do
> > not believe that the Routing Directorate review comments that were sent 3
> > January 2018 have been resolved.
>
> I am not requesting publication at the current time.  I am requesting a review.

Sorry for misunderstanding you. The term "IESG Review" refers to the
ballot process and telechat in the IESG which occurs after AD review
and after publication request.

> The comments received in January do not constitute a review.  The reviewer
> only discussed Sections 1 and 2 (Introduction and Conceptual Overview),
> and then spent the rest of her review claiming that we do not deal with
> management.  I suspect that she may not even have read the technical parts
> of rfc6126bis.

I'll go back and re-read the conversation from January.

> > In particular those related to OAM which were also discussed on the
> > BABEL WG mailing list.
>
> I have sent a lengthy reply about management on 7 January, and requested
> a full review (in a separate mail).  It has been over two months now, and
> I have received no reply from her.

That is certainly a legitimate complaint. I'll see what I can do.

> > I believe that if we just declare consensus in the WG and request
> > publication of the current draft,
>
> I am not requesting publication at the current time.  I am requesting
> a full review of the document, including the technical parts.  It's up to
> the IESG, of course, but I am of the conviction that this can only be
> achieved by choosing a different reviewer.

Actually, it isn't up to the IESG. The document is still inside the
BABEL WG. If appropriate, we can certainly request assistance from our
AD. But, until WG consensus is declared and publication is requested,
the IESG normally doesn't have involvement with individual WG drafts.

Getting a full review with fresh eyes is an excellent path to take. As
I say, I'll see what I can do.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> -- Juliusz