Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc7437bis-07: (with DISCUSS and COMMENT)

Barry Leiba <> Tue, 09 July 2019 01:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D1D2D120091; Mon, 8 Jul 2019 18:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.108
X-Spam-Status: No, score=-0.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.247, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id HqdAijFisMA9; Mon, 8 Jul 2019 18:41:14 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 44997120047; Mon, 8 Jul 2019 18:41:14 -0700 (PDT)
Received: by with SMTP id i10so39603533iol.13; Mon, 08 Jul 2019 18:41:14 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YEZcpUATB62WNK3/fbMh+OzuPHq7CXqs3SmQkCh2pBs=; b=LRC2suWRCejW6TWsXByf23tFDm0IZnSZJPyPUIMOO4t5+m7ISDmzrd/vPXv1OsUycP d4E3dbefIzpP7VoQWgg0rtzDJ3VgWNQQmMevO1Os5aZ35nSRn7OxBjwKkvIXUpESkvhw e972FJTSRdfuOHCv4Tb2R5z29bbdbhgRu2n6rtQmwCbXr2JtpTccX/+XTjpbThAhEPyB E3bEoH/1L4FnrVoUjjOOtO/I6eVGCILGtTSgzucacQqr5foZZ3jUOGK5kgB36hw4GsOq lsrG15Y+UWkBl9RBSKvtqKWwTGa0IuK4SE0/JZkW4eoCc8NEJJp9rrFq25BSMK9mOkch PL7w==
X-Gm-Message-State: APjAAAVixy1GRl7BSHK2LJZVIl084fdUxFcsbGdIJMGdOm93rO5r4vOa eeBwVO4mgTEW4+ZcNfuWawOfrfyBpHXxrW0IiPY=
X-Google-Smtp-Source: APXvYqwgTdDDDPrmXI9FxgmdWXvqM6IaQihToK2SBy+YQlYISHIIeKPYQ8V3dOK0QFN3Pyf1YAumsgChSnxp+s0MoYU=
X-Received: by 2002:a05:6602:2248:: with SMTP id o8mr2378403ioo.90.1562636473191; Mon, 08 Jul 2019 18:41:13 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <> <> <> <> <> <B2AD2AADD838CCA85DCDF3FE@PSB>
From: Barry Leiba <>
Date: Mon, 8 Jul 2019 21:41:02 -0400
Message-ID: <>
To: John C Klensin <>
Cc: Brian E Carpenter <>,, IASA 2 WG <>,, IESG <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Iasa20] Barry Leiba's Discuss on draft-ietf-iasa2-rfc7437bis-07: (with DISCUSS and COMMENT)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 09 Jul 2019 01:41:16 -0000

Hi, John.

> > FWIW I think I finally understood what was bothering Barry and
> > I think this tweak does express what the drafters of RFC7437
> > thought they were saying. So this would be a confirmed erratum
> > on RFC7437, if that was where we were in the process. It's
> > above my pay grade to decide whether we should handle it now
> > or wait for RFC7437bisbis.
> >
> > John Klensin's subsequent message would be a substantive
> > change of intent, IMHO. I'm not sure how I feel about it.
> I'm actually not sure how I feel about it either.  I am,
> however, fairly certain it was a scenario that was not actively
> discussed when 7437 was being discussed and approved.  However,
> the bottom line to me is that either
> * we have general consensus that the sentences in the document
> mean what the above (and Barry's suggested revised text) say it
> means.  In that case, the clarification is not urgent and can
> wait until we get around to doing a comprehensive revision of
> 7437bis.

I'm sure it was not actively discussed with respect to 7437, because
the text came there directly from 3777.  It likely *was* discussed
then, because it was added at that time.  Possibly Jim Galvin
remembers, so maybe I'll ask him.  I can't find mailing list archives
of the former "nomcom" working group, which produced 3777.

I don't agree that it's not urgent; to the extent that we can say that
anything here is really *urgent*: I think it's urgent that we make the
text say what the intent is, and fix it if it's not clear.  The
alternative, as I see it, is to remove the exception for now and
revisit it later.  (Note that I am NOT suggesting that, except as an
alternative to clarification; I think that having unclear text is
what's bad.)

Why, John, If we agree on what the intent is, do you not think it's
urgent to clarify it?  At the very least, it provides a baseline for
discussion of changes later.

> or
> * we don't have that level of agreement on what the sentence
> means, in which case there is no clarification in our
> traditional sense but a substantive decision followed by, or
> associated with, text to reflect that decision and make it
> perfectly clear.  In that case, it is unambiguously out of scope
> for IANA2 documents given both the decisions that have been made
> by WG Chairs and the AD and rules applied to other documents on
> that WG's menu.

I think that if we don't have agreement on what it means, we should
either remove it or flag it as problematic and not to be used until
it's clarified later.

I understand the scenario you laid out, which might lead someone to
put her name in for the vacated position when she didn't put it in for
the IAB during the initial call.  Notwithstanding that, I do think,
now, that this is what the exception was meant to be for.

I'm off to ping Jim Galvin now....