Re: AD Sponsorship of draft-moonesamy-recall-rev

Eric Rescorla <ekr@rtfm.com> Mon, 20 May 2019 10:46 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C8A120086 for <ietf@ietfa.amsl.com>; Mon, 20 May 2019 03:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-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 o_oeFZ4Chu3V for <ietf@ietfa.amsl.com>; Mon, 20 May 2019 03:46:11 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 66685120157 for <ietf@ietf.org>; Mon, 20 May 2019 03:46:11 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id l26so9889865lfh.13 for <ietf@ietf.org>; Mon, 20 May 2019 03:46:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uAZrq8jSgiexszYg+ELilxlaEWiThiNrJ8nLICA08V0=; b=v6ZBsOiYLdk/bAPfMYMCmxS1FKaqB/rwdTQVjJ0LHL54b+u8cC1YuaJAwT2/KMF6G5 qD+6H/Fw9dDmWsmwXXMI4qt4iuTJs7EksK1npIT6NgWb01peVFi+MO96w3B0kTOLChno O52IaSrYW9Ua6ZrhhbiglhroS1ERoEZORHjLChtewDmNNhvIUARe7kQtAI3j2hd4csk2 ULVotI8pmCdrgsbruvdlvAHLiE74TmENB26MkLwq0fBqMtpyvYf88vOKP2wiw5Z9RfSZ +mtx0LEuAUtUDAd67sL97T+Pdcy9dAD+tSLThlG4zr3BbW2Fp0lKL8YK8IE9RaWSSt6r c7Gg==
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; bh=uAZrq8jSgiexszYg+ELilxlaEWiThiNrJ8nLICA08V0=; b=Jlh6EXR1B5kXTy3dY0qG3B7rZdMJjZK8xU0oeqmqi6gLUhPYOCLJOC6YSFKNP9kevI y0aMsSDY5b+I25gZe+r7Jfv3cxTi9BofttGvIbJfM3sGG7BqEwR1KTGLg4Xjzd7WRx9Q Ec6oVFOBpGwIrjxeaq+h+5l7U1/yKXHKfUADviAYzbu3RicQ6Avyw3/N69OQYruucVLA OoJiP7tul1x503/x90bXLK+6GPgnpeGVfnOCAXEVB5e13Dl/RIll5Skom9w22hnhnabO gVjTHW5gib8fHgxfmCQx/0d39hHlvC77cbE6ykPP0G4/T09DV39NRjyqao/XFCnR2pbk PL4Q==
X-Gm-Message-State: APjAAAU3J/s/5urvaIhP2cd05o/cm++NkgeBiVSUyRvlrr2uVYgVo6w3 L4QfxnpkivH0o4GDYSRkoLKLSGLYvMU55Cq33+b/Ng==
X-Google-Smtp-Source: APXvYqwrIP0wVMwnT4XUZ0QGaCM5iQGRiOh0a9Wpf7z2l2CYN4Yhu3L2CaWn3h7LTCN0knw77e7JyFFWSXn4gZ0cgn0=
X-Received: by 2002:ac2:43af:: with SMTP id t15mr26300735lfl.45.1558349168822; Mon, 20 May 2019 03:46:08 -0700 (PDT)
MIME-Version: 1.0
References: <6.2.5.6.2.20190509041736.0d6d4548@elandsys.com> <f5834466-8f40-42bd-82d8-4dcb7d418859@www.fastmail.com> <6.2.5.6.2.20190509105617.0c08ef60@elandnews.com> <e854adaf-1ead-41d0-95bf-df56cb5a5914@www.fastmail.com> <6.2.5.6.2.20190514234822.0bc461f0@elandnews.com> <15BCE05FEA1EEA6AD0E7E5BD@PSB> <6.2.5.6.2.20190516103829.11f9fb18@elandnews.com> <E85C84CF-DB0B-410E-A0B2-A7C7E705E469@kaloom.com> <6.2.5.6.2.20190518141450.1163e590@elandnews.com> <75FF5D48-C416-4198-BC44-1B25524BF0E2@cooperw.in> <6.2.5.6.2.20190520025912.0ce8f378@elandnews.com>
In-Reply-To: <6.2.5.6.2.20190520025912.0ce8f378@elandnews.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 20 May 2019 03:45:31 -0700
Message-ID: <CABcZeBNV0VxRrW0-Z4hY4zh_Ok3cRM8FJGyogYogP6R6X8K12Q@mail.gmail.com>
Subject: Re: AD Sponsorship of draft-moonesamy-recall-rev
To: S Moonesamy <sm+ietf@elandsys.com>
Cc: "iab@iab.org IAB" <iab@iab.org>, John C Klensin <john-ietf@jck.com>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a4dee605894f70e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DoW-jOYPY92lnLyi-jLHtnWxSys>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2019 10:46:13 -0000

I'm not on any kind of I*, but when I was, the idea behind an IAB shepherd
was not that primarily that they provided a review but that they helped the
proponents of the work navigate the IETF process (especially the BOF
process) and get to a crisp problem statement, etc. I never thought of it
as a requirement, but rather something that was intended to result in a
more productive discussion.

-Ekr


On Mon, May 20, 2019 at 3:21 AM S Moonesamy <sm+ietf@elandsys.com> wrote:

> Dear IAB,
>
> I assume that the IAB has received a briefing about
> draft-moonesamy-recall-rev [1] as it was discussed at the IESG
> Retreat.  If I am not mistaken, an IAB shepherd can provide a review
> of architectural consistency and integrity.  Does the short draft [1]
> require that type of review?
>
> Regards,
> S. Moonesamy
>
> 1. https://tools.ietf.org/html/draft-moonesamy-recall-rev-02
>
>