Re: [DNSOP] Milestones changed for dnsop WG

Warren Kumari <> Fri, 27 October 2017 17:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B0BA7138F21 for <>; Fri, 27 Oct 2017 10:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rlWKpgYBl7nK for <>; Fri, 27 Oct 2017 10:08:44 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 75300138A38 for <>; Fri, 27 Oct 2017 10:08:44 -0700 (PDT)
Received: by with SMTP id b189so4695976wmd.4 for <>; Fri, 27 Oct 2017 10:08:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yzJZSeriWKCqZwJ6ZlmrrQLbUvC9qq1sxXQrfbg2Pas=; b=SA/DlxwAHRmbD0nfhV5xmsn/+EUawqtsuG+uI/dOVC7mqbyxOWqsZ21tgwTXXEtxai tWvZleCCPDumQwEp12OB5HFPVokPkufwqzQuoJk1Hq+VcAGlpMd0nauLhfCic+lRnoIH j/m7R9dvDt3UD8J39Cw1XgQ9FvvbjjaC2LRbeZjlHH5CyQ3P6cioPckUsRJk5OATDaKp yNYMAcSo9/2MWYvDNctgDoXROoRHlqEnEcVS8UGbP8epRTpeyf6RC5v9tXMNSieK3eQL FZ/OU3A6x6fRxBByrBtogHspkQ6Re/G0OWt8V0O5mfHxWtle/ab3TFzvUm4QwimMIkqz +LOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yzJZSeriWKCqZwJ6ZlmrrQLbUvC9qq1sxXQrfbg2Pas=; b=JapEbRoApiojOty+06yfwf6Kg+cxH0ZpvLEQ1zn6Nf8FZD1haEMBoIcfJGfhAMWZCa zgobGqMf2x4qs3Kg2a2w1eBb2KLjfajXEFqSxV6ARePjRBeBlTgBYX1bgAusV0LArgpG jIHWJ+8FcZeSN6u36TSwq74lCnlxxiShNnQVEUeXwRLsVPT3z9oNXaLUH0PDmw7pfurv fjM7KGizAeom4Pv0fV6HGsoR5YtfaVtaXTPAsNS+Oyrtb2Z77K4wNCOCvp4AN1MRF+yM dKBayvQryZnWpK8/SzvribmbF0HKw09wLbDuezSWXySgm3HioUgVjQnfVeo+l1ULORAK HQfg==
X-Gm-Message-State: AMCzsaUhoxG5VvCLTUCMHXXz4LcDktOv+SzVtclOvbrJX2w0MsBaoqCV 4kxDYL0pXcXYRuld23AzlxgL8HZgdQS6PK7X7M9iJQ==
X-Google-Smtp-Source: ABhQp+Qh+/LtneD4LOo7oGhvhqfst6qm1T/i1tQ/czI4Tel+8D1ocMQAlkRyJ/0B+3DdayUyPIfu+V5DbbGIATKtB1w=
X-Received: by with SMTP id a132mr1002114wma.124.1509124122598; Fri, 27 Oct 2017 10:08:42 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 27 Oct 2017 10:08:01 -0700 (PDT)
In-Reply-To: <>
References: <> <>
From: Warren Kumari <>
Date: Fri, 27 Oct 2017 13:08:01 -0400
Message-ID: <>
To: Stephane Bortzmeyer <>
Cc: dnsop <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [DNSOP] Milestones changed for dnsop WG
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 27 Oct 2017 17:08:48 -0000

On Fri, Oct 27, 2017 at 9:10 AM Stephane Bortzmeyer <>; wrote:
> On Tue, Oct 24, 2017 at 12:32:14PM -0700,
>  IETF Secretariat <>; wrote
>  a message of 9 lines which said:
> > Deleted milestone "Complete WGLC for dnsop-dnssec-roadblock-avoidance and
> > send to IESG".
> >
> > URL:
> Is it a bug or an human error? The only milestone (three years late)
> is draft-ietf-dnsop-dnssec-key-timing (was actually published as RFC
> 7583)?

This was my fault -- the chairs had an arrangement with Joel to not do
milestones; I knew about this, but forgot...

The secretariat sent out a reminder email on how to find milestones
which ADs need to approve - I hit the button and it sent the above

> What about the stuff in
> <>?

Yup - DNSOP is an ops type WG, and so takes on and deals operational
issue type documents; we don't really map out our plans for the next N
years. There are a significant number of documents in flight, and so
constantly adding, approving, closing milestones is more admin faff
than needed -- however, we do seem to have lost momentum getting
documents over the final hurdles, and so the plan is for the chairs,
secretary and myself to sit down in Singapore and figure out how to
better track things and stop documents slipping through the cracks.

So, sorry for the random closing of an old milestone, the current
milestones don't actually reflect what the group is working on (which
may or may not be an issue), and we're planning on figuring out how to
not lose momentum in the future.


> _______________________________________________
> DNSOP mailing list