[DNSOP] Enough to break a camel's back?
Nick Johnson <nick@ethereum.org> Wed, 25 April 2018 10:37 UTC
Return-Path: <nick@ethereum.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7670912DB6B for <dnsop@ietfa.amsl.com>; Wed, 25 Apr 2018 03:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.641
X-Spam-Level:
X-Spam-Status: No, score=-0.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_12=2.059, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ethereum.org
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 fue1SyMCFYqV for <dnsop@ietfa.amsl.com>; Wed, 25 Apr 2018 03:37:39 -0700 (PDT)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::235]) (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 59D4012DA6E for <dnsop@ietf.org>; Wed, 25 Apr 2018 03:37:38 -0700 (PDT)
Received: by mail-wm0-x235.google.com with SMTP id l16so5947582wmh.2 for <dnsop@ietf.org>; Wed, 25 Apr 2018 03:37:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ethereum.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=LXr/g1Xgq6Vb6P46OcPa7MwkzfcSLVPj1tMVW13Ew8c=; b=WuXwOWEq0ZnSNrjCjA59Dg1Inz6EcrLIdlKsXrzeFUbWewq3TXvQMwTigYmPdhw9Dy fjPFcC8EeGqbb26CfFZgMqLS+RvBTwgkDLmSK65B90FktZYmb92zuLnII/rcKhSyOQS2 ltBglhgv87iHFK9aOc1FyjvO4RXM3QZQLN4jA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LXr/g1Xgq6Vb6P46OcPa7MwkzfcSLVPj1tMVW13Ew8c=; b=rYxQGfQfl2wt7n2ABD+nqbIRos8VeFYc2U6o80qz4HddX7asUAJASy0gutj76wsMU7 iAKz43cYudMjcF7x4vM2X99/YMscNQD6g4X6SMFsqwBlOdphSw4OcQ/EYFvTCvpvXCc7 SLpR1BvoayVSjFgk1qYggVHNwEkclSGGFoMmZW3jc50O5kp6J34wXMun7vSgnd3EauUL N7VEMaNZmrpFYFOdlDa5glPeek4sWIaLGjjOYneuDqgICEGSdFbS7osXPsr6mzWj8Bwp tPB2FAuJu2k7XKYuovp2XePNURsEBnUHRRnh6kFltvTji/17RiLpEOeizluWBJXaCyof I9aQ==
X-Gm-Message-State: ALQs6tD3XiiZHoUS7FoHydjnmy5IriJrYbcWXHqREEbtvHgsGmW1r4hM kdaEkiSZ+CuQIIR6GCp/v7N86XGi7NX2yY4/NL3elBVO
X-Google-Smtp-Source: AIpwx4/yInwENhRf3X6hqV3fW+ZDyCW8O8I70ydn/IA3cidUjZWimzQiB/tYnGn+OkT7Gh0Fe9KWM9tKkp+aoIBjgcg=
X-Received: by 10.80.130.67 with SMTP id 61mr38525586edf.308.1524652655403; Wed, 25 Apr 2018 03:37:35 -0700 (PDT)
MIME-Version: 1.0
From: Nick Johnson <nick@ethereum.org>
Date: Wed, 25 Apr 2018 10:37:24 +0000
Message-ID: <CAFz7pMsHGv+fY9KEw2cxR6E9-y7z-iwyKxv6DjBf_UWnzZwG5A@mail.gmail.com>
To: dnsop@ietf.org
Content-Type: multipart/related; boundary="94eb2c06977cef3cbe056aa9db7f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TpzQXXkLb1swPQR7Jdbcs2RV8pg>
Subject: [DNSOP] Enough to break a camel's back?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Apr 2018 10:37:44 -0000
I'm working on something DNS related, and needed to reference a number of the DNS RFCs. With the IETF 101 "camel's back" talk in my mind, I found myself wondering - just how big *are* all the DNS RFCs together? So I threw together a quick script <https://gist.github.com/Arachnid/c51b450b0c80eb246394aab5c867d666> that collates together all RFCs with a particular tag, or updated by those RFCs, into PDFs. And once I had that, well... Notably this doesn't include at least a few DNS related RFCs that weren't tagged "DNS", such as RFC5155. It also doesn't pull in citations, since those are mentioned only in the text, not in the XML metadata. So the correct count is probably a bit more than the ~1300 pages you see here.
- [DNSOP] Enough to break a camel's back? Nick Johnson
- Re: [DNSOP] Enough to break a camel's back? Paul Wouters
- Re: [DNSOP] Enough to break a camel's back? Nick Johnson
- Re: [DNSOP] Enough to break a camel's back? Paul Wouters
- Re: [DNSOP] Enough to break a camel's back? Nick Johnson
- Re: [DNSOP] Enough to break a camel's back? Paul Vixie