Re: Question about pre-meeting document posting deadlines for the IESG and the community

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 17 March 2024 07:57 UTC

Return-Path: <abdussalambaryun@gmail.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 C294DC14F696; Sun, 17 Mar 2024 00:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level:
X-Spam-Status: No, score=-7.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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YfJoDH7OwL1W; Sun, 17 Mar 2024 00:57:46 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 425E1C14F5FA; Sun, 17 Mar 2024 00:57:46 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id ffacd0b85a97d-33e570ef661so1464190f8f.1; Sun, 17 Mar 2024 00:57:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710662264; x=1711267064; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ceDiN0MMqiN0sTYO+D/6cdIWhjqZ8e1ACL0/Wt6zEG0=; b=f5bl4xKcSs2sd7eAkKLQjjWi/iuYlwPEqsuL92UzywTz5v+3F7Ci443dRWtn7K0MEQ nEJJYhP/h/yC8nCCM+wyXi+dt1YxV5RIK6g/rocpLhX09do70vVntcP2hJmXFvftaimf RuoFnMju3iYA5C5bbTnwbFszRBl9+QkDwF3jW9mjlsvtOcQYoQfEbHytDNbf3i2ZrpmZ acuEskuMHSMlDLT/cBO5GZTtztPBgu0f7HVdGbzseAg6JlQU6EYpUrPeFO0iX++QMakz Rip8wAjoY5lLshFhcNEG5EAkEAOoBUiP1sJx28QZGWwP9qmZq4xz6uPedaV/spXVTIdv j0tQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710662264; x=1711267064; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ceDiN0MMqiN0sTYO+D/6cdIWhjqZ8e1ACL0/Wt6zEG0=; b=C2HA5WkO9gVOVNoNJjjY2qIgLME/JLY7o0h381n8pHpxdZZL7L23fAHCBQMhsXntqf R0xjC7Lhve2BJqnwzuIZy7MJ/Gb1Hl/VsE/9k+dkWgZg0OzMUK12obrIxUB/r2lErzKJ 642JDfhG75uk59ITcO1a9IrvVFIWxfoA4mKy+M3OetcKz6MiPV+O3jZm7/yY4w0unQZk 93LGL76Xu7ViSa8QU8i4KHBZlp05hDDJPisTn9ztHPu6cxkXbDclXEY4PR6BTrijov+k upl3vexmaTIUNP4g4tKc2k+7SSFvQF1cxgFSM40SiuntEGnC+lYl++h+2X+4wsKAU0zi Jhtg==
X-Forwarded-Encrypted: i=1; AJvYcCWnZF9+IRch0HOfATfpm1HwdQGr0AVMv7i+K/9Wp6qSBSESHJLjm/8x3BLFY8xgbQ2fwLL8C6lFcrDZpZ5D
X-Gm-Message-State: AOJu0YwgdD/7sYAbYfRvzXoBMgBnugb01S8XEAGCdG5lIqNy7A/zBo65 7xArglh5bbv1DTSZxvVBI5xJbdmJjcFg+EOkLgA6i8arJsWHVY0SLfgY/mi0kpWJrMvdNa6KZwV 8ZESkMU35iTMA9rDnYuW9D6u2578du3AZ
X-Google-Smtp-Source: AGHT+IFOk8S/fdlc0qBuBvj+xDTPPU+puYHEuiiR1pnWv38xML58xjk48fcILiPT4PhJtt9IpcF7bjSGrwSHE39POjI=
X-Received: by 2002:adf:cd0c:0:b0:33e:c522:e3b9 with SMTP id w12-20020adfcd0c000000b0033ec522e3b9mr6459218wrm.36.1710662263803; Sun, 17 Mar 2024 00:57:43 -0700 (PDT)
MIME-Version: 1.0
References: <7826C4F13FA874CD79459A4B@PSB>
In-Reply-To: <7826C4F13FA874CD79459A4B@PSB>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Sun, 17 Mar 2024 09:53:16 +0200
Message-ID: <CADnDZ8-YpgoDZPx2om7eGUbnNkOUXmSX4MPwEK2=P0=VectL9A@mail.gmail.com>
Subject: Re: Question about pre-meeting document posting deadlines for the IESG and the community
To: John C Klensin <john-ietf@jck.com>
Cc: iesg@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009096260613d6987b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GSBxWCQnBJbB0j5PrOlCCk6ExdM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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: Sun, 17 Mar 2024 07:57:46 -0000

Hi John,

I agree with you, it should not be allowed, but I think it is important
also the session's chairs/ADs must have a say in such special cases there
may be a need for a presentation or a document that is needed for the
session/WG/Charter. There is always a possibility that presenters don't
present for some reason (causes change of schedule/agenda at the start of
the meeting to be agreed_on/discussed), so the chair is responsible to
manage the session to be useful the most to attendance..

For my understanding the deadline (for conferences and meetings) is to give
time for participants read the documents and also for the author/presenter
to get enough/fair time to present, but also if there is some more time
available/open_mic at the end of meeting, then any one can present any
thing which is needed/maybe_needed by participants.

Best Regards,
AB

On Fri, Mar 15, 2024 at 9:27 PM John C Klensin <john-ietf@jck.com> wrote:

> Hi.
>
> For many, many, years we have had a cutoff for posting I-Ds
> about two weeks before an IETF meeting starts.  That cutoff was
> established to give people time to read documents (especially
> because, predictably, many documents would be posted just before
> it), figure out which WG meetings they needed to attend, prepare
> comments, etc.    We are now seeing pull requests that alter
> substantive parts of documents posted on Github within a short
> time before IETF starts and during the window when new or
> revised I-Ds are not allowed without special circumstances and
> specific permission from ADs.
>
> Allowing that seems to contradict, or at least seriously weaken,
> the principle of having documents available well in advance of
> meetings.  If they are announced only to the mailing list of the
> relevant WG(s) (and sometimes not even that widely), it seems to
> me that they impede both WG meeting discussions in which
> everyone has the same starting points and openness to IETF
> participants who have not signed up for the WG mailing list
> (newcomers included).
>
> Is the IESG considering some guidance on this subject or is it
> considered unnecessary?
>
> As an almost-separate question, if the "real" version of an I-D
> that is expected to be discussed in meetings and on mailing list
> is the the draft plus the cumulative effect of pull requests
> (some by other than the listed authors), should that be more
> clear and reflected in the datatracker?
>
> thanks,
>    john
>
>