Re: [Mops] WG -- your very last chance! Re: Roman Danyliw's Discuss on draft-ietf-mops-streaming-opcons-10: (with DISCUSS and COMMENT)
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Fri, 05 August 2022 18:07 UTC
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: mops@ietfa.amsl.com
Delivered-To: mops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59ABCC15948F for <mops@ietfa.amsl.com>; Fri, 5 Aug 2022 11:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 Dg3BKvTHORFQ for <mops@ietfa.amsl.com>; Fri, 5 Aug 2022 11:07:11 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 9D347C13C502 for <mops@ietf.org>; Fri, 5 Aug 2022 11:07:11 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id z3so2609458qtv.5 for <mops@ietf.org>; Fri, 05 Aug 2022 11:07:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=5Ev9tMHPVLkl2DEtNRiUis4yFyNxizcx+NpRaj3tglk=; b=FdIdV1OmqeVS/UnBj2H7LPPFR/2ozCOWUDdIXnNCZaMWcyHVzdiCZ6QsCmJmjo0blx bgr4xYY/49kDQtxVf3R51uE5cam74LWyjS894SItsWzCMowEVOh3F7s0ufwdy+hcPERR sDNRB6RNSDLAnxf/HECFchlz+5mVSlh6NpWT22q2x/MadIwu1VwvjWw5qRYHdU2E9kNY CEOrWpvW3ItQ7ALBrvKek/YBXLVDE9ZDt5TvDEZjWBSmR/BVmkrCoQsInGBzmkFrgyhO Qrkq5eDfJ+/2g48tPryIeAw9xWeu2KxvzPlhiIVy3YGa9NctqjwcqQQDf0EWNp8kRQ/L acXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=5Ev9tMHPVLkl2DEtNRiUis4yFyNxizcx+NpRaj3tglk=; b=42dKaFBYxw639g9nGkxGWD+vC/J2+cRV2RTmEPw7e6rHy5f8VaTGFgJeFIdDpPqdOJ XL41Tmf80It4WkkBLBWP3enm72oqko3FXaz0cplrFCIdZXdbpsHQxqyz8aZz2OdIkbbJ XYIIVwZxlgsVAsfRAmTWM44ozGJYWF+xrA6dmbu28XnFXkzWMKORhjkbvylzTcCNd7vv KdWiFfnk6Umh6CcNrJIOL9ZUyqFYeeUHrMMvgZr3GTMIRkyZIgbY0lLEpNJmTq5DoyrO xo30Afo/F+DNl1K5FOCmu+d/nghve1dwdTRS6FK3a9wEudb6ifIUAyGj32zAFdHYTeme l4lg==
X-Gm-Message-State: ACgBeo0fWQnfXgO86dqnvHgoP5NXc+4Hb9SJszQ77chzYbCRNbbagy9K 3T2yjgdVrGXQUNRRKq4dMBYqeivja4oVQ78Flec=
X-Google-Smtp-Source: AA6agR5hgLMTf6WW4NjN9lbAn88BWYWzB5fg+PSG7ek/4aDWKBEdnyQUMhp6zw9bSwC9C7YwsEVA60UI3BTNdmDBAy0=
X-Received: by 2002:ac8:7d90:0:b0:326:b431:6cd3 with SMTP id c16-20020ac87d90000000b00326b4316cd3mr6914772qtd.511.1659722830683; Fri, 05 Aug 2022 11:07:10 -0700 (PDT)
MIME-Version: 1.0
References: <802C4F26-1F7D-48A4-AE07-2F3F94D7B568@thinkingcat.com>
In-Reply-To: <802C4F26-1F7D-48A4-AE07-2F3F94D7B568@thinkingcat.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 05 Aug 2022 13:06:45 -0500
Message-ID: <CAKKJt-dsWvi9hYKoqBgbVLBGDyck_6W5-C8AxZST2OfQyWP7Ow@mail.gmail.com>
To: "Leslie Daigle (ThinkingCat)" <ldaigle@thinkingcat.com>
Cc: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, MOPS Working Group <mops@ietf.org>, Jake Holland <jakeholland.net@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000bfa2b805e582555a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mops/6eBYsEyzkByd0pE1QBi6w9iDr8c>
Subject: Re: [Mops] WG -- your very last chance! Re: Roman Danyliw's Discuss on draft-ietf-mops-streaming-opcons-10: (with DISCUSS and COMMENT)
X-BeenThere: mops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Media OPerationS <mops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mops>, <mailto:mops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mops/>
List-Post: <mailto:mops@ietf.org>
List-Help: <mailto:mops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mops>, <mailto:mops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2022 18:07:15 -0000
Hi, Leslie (and Kyle, and most of all, Éric), as we line up for the parade celebrating completion of the first MOPS WG chartered document, Two things about this draft. A quick peek at https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/issues/153 shows that the only remaining open issue for this draft is (ta-da!) from Roman's comments on his IESG ballot. I would love for the editors to look at that issue, which we have not done yet, and see if there's anything that needs to be changed to reflect those comments. I asked (begged?) the working group to take a look at the diffs from -10 (what left the working group, after AD evaluation) to -11 (the changes the editors made between receiving comments on -10 and the I-D submission cutoff before IETF 114), <https://datatracker.ietf.org/meeting/114/materials/slides-114-mops-draft-ietf-mops-streaming-opcons-update-00>looking especially at the changes highlighted in yellow on slide 3. The editors continued to work on comment resolution during the submission "quiet period" before IETF 114, so there are changes in the editor's copy in Github that are not in -11. These are not major changes, but we didn't point the working group at Compare Editor's Copy to WG Draft <https://tools.ietf.org/rfcdiff?url1=draft-ietf-mops-streaming-opcons&url2=https://github.com/ietf-wg-mops/draft-ietf-mops-streaming-opcons/raw/gh-pages/draft-ietf-mops-streaming-opcons.txt>, and it would be good if people took a quick look at those changes as well. Given these two points, could I suggest to Éric that he* wait until, perhaps, next Friday, August 12, to push the button and send a -12 version containing all of the changes in Github to the RFC Editor?* That would give the working group a week from today, to look things over. Do The Right Thing, of course ... Best, Spencer On Fri, Aug 5, 2022 at 12:07 PM Leslie Daigle (ThinkingCat) < ldaigle@thinkingcat.com> wrote: > Thanks, Éric! > > I will remind the WG that (as you will have seen in the minutes of IETF > 114 MOPS WG meeting :^) ) there have been many improvements in the document > as the authors have addressed the IESG and IETF last call input. These > edits have been summarized to the WG list in the GitHub summaries each > week, and you’ve seen the successive draft iterations. > > But, now is your very last moment (while Éric is enjoying a social evening > :^) ) to provide input if you think the changes have introduced an issue in > the document. > > Leslie. > > On 5 Aug 2022, at 12:57, Eric Vyncke (evyncke) wrote: > > Thank Roman for having taken the time to review the -11 and to reflect on > it. > > > > I will then approve shortly the I-D for publication after checking if > everything has been addressed (social time here in Europe already so not in > the next hour :-o ) > > > > Regards > > > > -éric > >
- [Mops] WG -- your very last chance! Re: Roman Dan… Leslie Daigle (ThinkingCat)
- Re: [Mops] WG -- your very last chance! Re: Roman… Spencer Dawkins at IETF
- Re: [Mops] WG -- your very last chance! Re: Roman… Eric Vyncke (evyncke)