Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-extended-error

George Michaelson <> Wed, 24 October 2018 22:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AE689130E1A for <>; Wed, 24 Oct 2018 15:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 aPUFQ9cFrtLX for <>; Wed, 24 Oct 2018 15:30:33 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0637D12D4EC for <>; Wed, 24 Oct 2018 15:30:33 -0700 (PDT)
Received: by with SMTP id g9-v6so7206329wrq.4 for <>; Wed, 24 Oct 2018 15:30:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qoqdVhrVhMVe+5Cut2ceEWpG0duQY+OkG1QGpggKR1Q=; b=PC9PGNymSFss9xX3uGRHyeJ66aMLj/l3jh00XrP0P/76T5MLWC1ghpO/lhPN8/7I1Y om8oU8RA/2rrpzUGM5ne/q5XQVDlwq5sMNKS8P9zpoSY2QKhvn+4+8sgq2358A+9XmXn p142PxWudstBt0CasmsW+uHyKdReVH8ZvAVbnRyBREFNo6MVfZ5NbQaWMuZtNO2lK2eL gSyypYzjEpad7KSt7D7eU3UY0xSrYJBBPQBIVPrDi0/qztdzgZn5WNsZ0N2u1GU3xplj eiXEWHwJFVvbtxA4ddjZkyz1dmj2kgoQnL8VX5mLp7kkOlqUH/AWPmeBS/m1NVSg2wst BHbw==
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=qoqdVhrVhMVe+5Cut2ceEWpG0duQY+OkG1QGpggKR1Q=; b=IWGqFVV3N5lZX2z+iipBXwF2FZHTNTYwRCeCU0n/1udDIdqbz6hsT/j8/tD53fkfiZ OGmpR99vguO2gVbg398q4SfpbSBuiVBBaWpZk/AwQgPt7V/SA5zROZEUlyZZBR8OTm74 hxHm2+4mOEF4l6P9LtrfasiFFpyaZY8mn2VfxIIe+Cv2u7pyCQ02gjn2lXXIgVEeSLaP oSmB0+lVkKqMN8LlyxE5hNEN6lZw+iwa8t4E5/hLzGHkS0tCRmXUf5UlPh1oTFvvuccA NvSeKUCEaxRSpb4q40Ej/NbJ4EpbZm+4xF3S4YdkZzQi7B7+oin0YgAv5fC8ALwXm6yp DlvA==
X-Gm-Message-State: AGRZ1gJFBRFcO+GzioNJLNYuBiwg5StDvENsBBdT1+rOJFNZo++ttDF2 F6Pf9Mg4hxKT31qZCXrMPBg8K7tnqMj0qIk692MnuA==
X-Google-Smtp-Source: AJdET5cLHjl38vMavsVho6ni9MbFUIkv6Zrqsn5RnI0Lq7QD0VVYWv7qajoR9S1SUFBOS+Tmhibgz6YB9cZB19YSJBQ=
X-Received: by 2002:a5d:4b0f:: with SMTP id v15-v6mr1532246wrq.180.1540420231453; Wed, 24 Oct 2018 15:30:31 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: George Michaelson <>
Date: Thu, 25 Oct 2018 08:30:20 +1000
Message-ID: <>
To: Tim WIcinski <>
Cc: dnsop WG <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-extended-error
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 24 Oct 2018 22:30:38 -0000

How can it go WGLC with section 6 an open question?

in every other respect I like the document. Bad Hair and all.

I would like to understand if we could work out a way to do traceroute
in the codes, with some defined code to ask the DNS resolver to
perform a TTL drop on a counter and mark itself into the chain, which
would help uncover resolver chains.

With IANA registry requests, I may be wrong here, but I thought we had
some (boilerplate?) language about how IANA is asked to operate the
registry: what criteria judge acceptance. Is it like the OID and
basically open (hair oil) slather, or is it only at WG RFC documented


On Wed, Oct 24, 2018 at 4:42 PM Tim Wicinski <> wrote:
> Hi
> We've been talking with the authors of Extended Error and now that
> they've gotten around to updating the document, and the chairs
> feel it is ready for Working Group Last Call.
> We're going to kick this WGLC off this week and run it through IETF103.
> This will give folks time during the meeting to bring up any issues
> they may have there.
> This starts a Working Group Last Call for draft-ietf-dnsop-extended-error
> Current versions of the draft is available here:
> The Current Intended Status of this document is: Standards Track
> Please review the draft and offer relevant comments.
> If this does not seem appropriate please speak out.
> If someone feels the document is *not* ready for publication,
> please speak out with your reasons.
> This starts a two+ week Working Group Last Call process,
> and ends on at the end of IETF 103: 9 November 2018
> thanks
> tim
> _______________________________________________
> DNSOP mailing list