Evolving Documents (nee "Living Documents") side meeting at IETF105.
Warren Kumari <warren@kumari.net> Wed, 03 July 2019 20:05 UTC
Return-Path: <warren@kumari.net>
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 7F02E120483 for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 13:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kumari-net.20150623.gappssmtp.com
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 iSvT9w52Sqdq for <ietf@ietfa.amsl.com>; Wed, 3 Jul 2019 13:05:36 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 230651204AD for <ietf@ietf.org>; Wed, 3 Jul 2019 13:05:36 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id 44so1594423qtg.11 for <ietf@ietf.org>; Wed, 03 Jul 2019 13:05:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=ZRNuUIhkRwg2gj0yttexV2kSJ7lKHZqEA/x+qTJnDGk=; b=yO6mVunPN5EYVd/3wAyc09pN1NuB6SOGTHssuHR64MgyLWFAY70nwsHd//0rjC5w5+ dImjvPpEJvqnuolrzNhYfXRwXvWDPTksOfRQEs1xkLnsrxixT+l3cIB5miZwfw/+BuLl oB85B6id+4rdYhki7R/X0kYrD5IidrNytYZi6Ubce3TsPXvtOwGW6VbE2bp4f5cOrO4c v11S8pOCoU1i6lWRY/EMN0o3KXWXUHXVPPI9yQ0BmGv4yhKUReCSAqn+22ffHFH9g6d9 c0I0TJBsJ5XL+kVqLd0zv99gnVG09AKGOKJ91M5xor9PkL6z0iUILBA3N+OuXKfCtZNP vtwg==
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 :content-transfer-encoding; bh=ZRNuUIhkRwg2gj0yttexV2kSJ7lKHZqEA/x+qTJnDGk=; b=mUyIUY/nb8DOpWUgtQOCKHrztJzmM2xRBhUFqf4HlngJv2rF9ohRZEWVuhWBt18yKr QNZQhFZPoDp+Gq4lsY56imm7HEIOaG5QjztI71KzVd4QtwervafRXlu1ccWBeAxvqGRW RgmRNJuFRwGRyFxrg5MPaK3bL2iNfDeT9sZEh262tyRm2XQuoAzoViWvwIR1SOQ3ThAT /Hlb2dPIpObJjypLDZl3AHT1Ak43Pp++6YrLdGdu+WC44N5n4AgT1NR9sBViy7B/U9C2 zCk1Z/0WguF4TOivjVMA0ixp+xX+hJ++145ES2lNqP3KkF9GJuBv2GN+9ynE84eAjuzr q2fA==
X-Gm-Message-State: APjAAAXWvZbb6vw/iWvNokYzvCSeLp2paSr3lQvN47gKWZT3BThRhpdP t4mgFXMsbr0h3wckocCgIyd5AYapzdZ9LvQWFVkG3vh3kZocQA==
X-Google-Smtp-Source: APXvYqx7wd3cHKH/W8ngGsRxxrT0SK1TSav1Kf/ipx0g5XjgmT/2uvY44VyDvIGdLXvHq8NKdrWLWO+QKv+pKBx7O0o=
X-Received: by 2002:aed:2fe1:: with SMTP id m88mr51573qtd.77.1562184334407; Wed, 03 Jul 2019 13:05:34 -0700 (PDT)
MIME-Version: 1.0
From: Warren Kumari <warren@kumari.net>
Date: Wed, 03 Jul 2019 13:04:56 -0700
Message-ID: <CAHw9_iKv7xDY-rT98F_BAEvGOGbWGL7UpXS42rSVLsHB+=SOZg@mail.gmail.com>
Subject: Evolving Documents (nee "Living Documents") side meeting at IETF105.
To: IETF Discuss <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zy2l7gWR8yGRIIt5mYY5WSorqGY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <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: Wed, 03 Jul 2019 20:05:40 -0000
Hi there all, TL;DR: Being able to mark a specific version of an *Internet Draft* as “stable” would often be useful. By encoding information in the name (stable-foo-bar-00) we can do this. Heather and I will be holding a side meeting at IETF 105 to discuss the idea and get feedback. When: Tue, July 23, 3:00pm – 4:30pm Where: C2 (21st Floor) Details: Back at IETF 103 (Nov 2018, Bangkok) Job presented on “Living Documents” at the GROW session - https://datatracker.ietf.org/meeting/103/materials/slides-103-grow-living-documents-growroutingsecurity-00 . Ever since then I’ve had an action item to write this up, and get more feedback on this. I’ve had a number of discussions with people about this, and have had a bit of a tricky time explaining it -- we’ve realized that this is because there are multiple use cases, and people have been pigeonholing the idea into their preconceived use-case. The two *main* use-cases are: “Evolving” documents (there were originally called “Living documents”, but that name is already in use in the web community, and so we chose another name to make it less confusing). “State of Play” documents. My main use-case / interest is the “evolving documents” idea, and so I’ll be focusing on that (the “State of Play” idea is taking the sorts of things used to plan interop events in QUIC and HTTPBIS, and creating a common format and location for them; this will be fleshed out further in the future). There are a number of topics / drafts where the best current practice changes over time - a simple example of this is something like routing security, and so I’ll use it as an example (also, the concept was first presented in GROW!), but the concept is applicable to all sorts of cases. The best practices for routing security (what / how to filter, route-leak prevention, etc) change over time and it is not really feasible to document how to e.g build route filters and then release -bis documents quickly enough to keep up with how the operational advice changes; this means that much of this sort of information doesn’t get documented in the IETF, and instead is scattered around in institutional knowledge, personal blogs, IRC channels, etc. An obvious solution is to simply document this in an Internet Draft, and then update the ID as the advice changes; this is indeed a reasonable solution, but makes it hard to refer to the WG’s *best current* understanding while still allowing the WG to continue working on the draft. If you refer to a specific version (draft-ietf-foo-bar-23) it is hard to let people (especially external people!) know when the WG thinks that there is a new “stable” version (draft-ietf-foo-bar-30); if you refer just to the draft name (draft-ietf-foo-bar) it makes it hard for the WG to make any changes to the draft without potentially causing confusion. In order to allow us to refer to “stable” and “development” versions of drafts I’m proposing that we use the draft naming scheme to annotate a version as “stable”: Currently when draft-wkumari-bar-03 gets adopted by the BAR working group, it gets renamed to draft-ietf-foo-bar-00. I’m proposing that, when a WG determines that there is consensus that a version of a draft is “stable”, a copy of the draft would be created called draft-stable-foo-bar-00. When a new version of draft-ietf-foo-bar is deemed stable, it would be copied into draft-stable-foo-bar-01. This is simple for external people to understand, etc. When and if the draft becomes an RFC, the link for draft-stable-foo-bar would redirect to RFCxxx (just like draft-ietf-foo-bar). There are a few open questions / notes (AKA FAQ!): 1: How does the WG decide that a document is “stable”? One obvious option would be for the chairs to run something that looks like a very lightweight WGLC. Another would simply be to have the chairs decide (chairs are already trusted to judge consensus). This is still open and I’m looking for feedback… 2: What are we calling these? The original name for this was “Living Documents” - a number of people have pointed out that this name is already in use in, and so has “baggage”. I’d love some suggestions, so far the closest I’ve gotten is “Evolving Documents”. There are only 3 problems in computer science: off-by-one errors and naming things… 3: Why did it take so long from IETF 103 till this is being suggested? <Warren hangs head in shame> This has been sitting on my todo list, and kept getting pushed down. I had some time at an ICANN meeting and finally wrote it up… 4: We had also considered a new tag in the Datatracker, and allowing the chairs to assign it to a specific version of a document; this would have been simple to implement, but much of the purpose of this idea is to make it easy for external people to reference the latest version of a document - and expecting them to understand datatracker tags seems more complex. 5: What happens when an “Evolving Document” dies? Evolving documents are just copies of drafts, tagged with a prefix (just like adopted WG documents are tagged with a draft-ietf) - this means that they behave just like any other draft - it is hoped that, if a WG decides to abandon an “evolving document” they would replace it with a tombstone (e.g “The foo WG has decided to abandon this document because $reasons”). 6: Can an Evolving Document update an RFC?! Nope - see the previous question; this is simply a way to mark an ID as “stable”, they don’t have special powers. Just like an ID cannot update an RFC, neither can an Evolving Document. 7: Can an Evolving Document become an RFC? No!, see the previous two questions :-) The ID that an evolving document is a based on can be published an RFC (and it might be identical to an evolving document), but this doesn’t in any way change the RFC publication process. It is expected that if / when the ID gets published, the datatracker link (e.g: https://datatracker.ietf.org/doc/stable-foo-bar/ ) will point to the published RFC, just like ID links ( https://datatracker.ietf.org/doc/draft-ietf-foo-bar/ ) currently do. 8: This looks like you are creating something like semantic versioning for drafts. Why not simply create something like draft-ietf-foo-bar-17.42.9?! This does have some similarities, but I think a better analogy is “development” and “release” branches. I also believe that the current draft naming and versioning system has been around for a long time, is well understood, and works well - we have lots of tooling which uses it, and it has lots of history. I really really *really* don’t want to mess with that - this proposal allows those who would like to annotate a version as “stable” to do so without us mucking with the existing process, etc. 9: This ain’t new, $person proposed something similar at $meeting_or_list…. Indeed. As an example, Phillip Hallam-Baker mentioned a desire for something similar at the IETF102 plenary; I think that this demonstrates that there is an interest for this, let’s explore it further. 10: Does a WG have to use this? I think it’s a [waste of time | confusing | useless for my WG | <something>]? Nope. This is only for those WGs that would like to use it - if you don’t want to use it, feel free to ignore it. If you think it would be better if only $something, please come tell us. Obviously, if you feel that this is harmful, please speak up! Please come to the side meeting and discuss the idea of Evolving Documents further, Warren Kumari and Heather Flanagan P.S: I'm traveling for the next few weeks (and am also part of the NOC team, and so get to Montreal early), and so my responses might be delayed - 'pologies in advance. -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf
- Evolving Documents (nee "Living Documents") side … Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Richard Barnes
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Richard Barnes
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Paul Wouters
- Re: Evolving Documents (nee "Living Documents") s… Joel M. Halpern
- Re: Evolving Documents (nee "Living Documents") s… Scott O. Bradner
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… heather flanagan
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… Heather Flanagan
- Re: Evolving Documents (nee "Living Documents") s… Scott O. Bradner
- Re: Evolving Documents (nee "Living Documents") s… Michael Richardson
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… Ted Lemon
- Things that used to be clear (was Re: Evolving Do… Andrew Sullivan
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Carsten Bormann
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… John C Klensin
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Lars Eggert
- Re: Things that used to be clear (was Re: Evolvin… Ted Lemon
- Re: Things that used to be clear (was Re: Evolvin… Job Snijders
- Re: Evolving Documents (nee "Living Documents") s… Salz, Rich
- Re: Evolving Documents (nee "Living Documents") s… Heather Flanagan
- Clarity, evolving documents, living documents, th… John C Klensin
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Clarity, evolving documents, living documents… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Joe Abley
- Re: Clarity, evolving documents, living documents… John C Klensin
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Randy Bush
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Leif Johansson
- RE: Clarity, evolving documents, living documents… Rob Wilton (rwilton)
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Fwd: Things that used to be clear (was Re: Evolvi… Keith Moore
- Re: Fwd: Things that used to be clear (was Re: Ev… Randy Bush
- Re: Fwd: Things that used to be clear (was Re: Ev… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Ted Lemon
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Ted Lemon
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… john heasley
- Re: Things that used to be clear (was Re: Evolvin… Theodore Ts'o
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Things that used to be clear (was Re: Evolvin… john heasley
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Warren Kumari
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Warren Kumari
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Benjamin Kaduk
- Re: Things that used to be clear (was Re: Evolvin… Benjamin Kaduk
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Alissa Cooper
- Re: Things that used to be clear (was Re: Evolvin… Christian Huitema
- On XML and $EDITORs (Re: Things that used to be c… Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Ted Lemon
- Re: Things that used to be clear (was Re: Evolvin… Julian Reschke
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Randy Bush
- Re: Things that used to be clear (was Re: Evolvin… Richard Barnes
- Re: Things that used to be clear (was Re: Evolvin… Randy Bush
- Re: Things that used to be clear (was Re: Evolvin… Eric Rescorla
- RE: Things that used to be clear (was Re: Evolvin… Adrian Farrel
- Re: Things that used to be clear (was Re: Evolvin… Kathleen Moriarty
- Re: Things that used to be clear (was Re: Evolvin… Stewart Bryant
- Re: Things that used to be clear (was Re: Evolvin… Leif Johansson
- Re: Things that used to be clear (was Re: Evolvin… Ted Lemon
- Re: Things that used to be clear (was Re: Evolvin… Sarah B
- Re: Things that used to be clear (was Re: Evolvin… Randy Bush
- Re: Things that used to be clear (was Re: Evolvin… Richard Barnes
- Re: Things that used to be clear (was Re: Evolvin… Ted Lemon
- Re: Things that used to be clear (was Re: Evolvin… Richard Barnes
- Re: Things that used to be clear (was Re: Evolvin… Randy Bush
- Re: Things that used to be clear (was Re: Evolvin… Richard Barnes
- Re: Things that used to be clear (was Re: Evolvin… Leif Johansson
- Re: Things that used to be clear (was Re: Evolvin… Andrew G. Malis
- Re: Things that used to be clear (was Re: Evolvin… Donald Eastlake
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Michael Richardson
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- RE: Things that used to be clear (was Re: Evolvin… Eric Gray
- Re: Things that used to be clear (was Re: Evolvin… Michael StJohns
- Re: Things that used to be clear (was Re: Evolvin… Melinda Shore
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Phillip Hallam-Baker
- Re: Things that used to be clear (was Re: Evolvin… Phillip Hallam-Baker
- Re: Things that used to be clear (was Re: Evolvin… Phillip Hallam-Baker
- Re: Things that used to be clear (was Re: Evolvin… Kathleen Moriarty
- Re: Things that used to be clear (was Re: Evolvin… Keith Moore
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Nico Williams
- Re: Things that used to be clear (was Re: Evolvin… Phillip Hallam-Baker
- Re: Things that used to be clear (was Re: Evolvin… lloyd.wood@yahoo.co.uk
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: Things that used to be clear (was Re: Evolvin… Julian Reschke
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- Re: On XML and $EDITORs (Re: Things that used to … Carsten Bormann
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- Re: On XML and $EDITORs (Re: Things that used to … Carsten Bormann
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: Things that used to be clear (was Re: Evolvin… Stewart Bryant
- Re: On XML and $EDITORs (Re: Things that used to … Phillip Hallam-Baker
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- Re: On XML and $EDITORs (Re: Things that used to … Carsten Bormann
- Re: Things that used to be clear (was Re: Evolvin… Mary B
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… Phillip Hallam-Baker
- Re: On XML and $EDITORs (Re: Things that used to … Andrew G. Malis
- Re: On XML and $EDITORs (Re: Things that used to … Ted Lemon
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: On XML and $EDITORs (Re: Things that used to … Carsten Bormann
- Re: On XML and $EDITORs (Re: Things that used to … Ted Lemon
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: On XML and $EDITORs (Re: Things that used to … Julian Reschke
- Re: On XML and $EDITORs (Re: Things that used to … Randy Bush
- Re: On XML and $EDITORs (Re: Things that used to … Eric Rescorla
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Nico Williams
- Re: On XML and $EDITORs (Re: Things that used to … Keith Moore
- Re: On XML and $EDITORs (Re: Things that used to … Phillip Hallam-Baker
- Re: On XML and $EDITORs (Re: Things that used to … Phillip Hallam-Baker
- Re: On XML and $EDITORs (Re: Things that used to … Phillip Hallam-Baker
- Re: On XML and $EDITORs (Re: Things that used to … Joe Touch
- Re: On XML and $EDITORs (Re: Things that used to … Phillip Hallam-Baker
- Re: On XML and $EDITORs (Re: Things that used to … lloyd.wood@yahoo.co.uk
- Re: On XML and $EDITORs (Re: Things that used to … Joe Touch
- Re: On XML and $EDITORs (Re: Things that used to … Ted Lemon
- Re: On XML and $EDITORs (Re: Things that used to … Joe Touch
- Re: Too many tools, was Things that used to be cl… John Levine
- Re: Too many tools, was Things that used to be cl… Scott Kitterman
- Re: Too many tools, was Things that used to be cl… Joe Touch
- Re: Too many tools, was Things that used to be cl… Scott Kitterman
- Re: Too many tools, was Things that used to be cl… John C Klensin
- Re: Things that used to be clear (was Re: Evolvin… John C Klensin
- Re: Too many tools, was Things that used to be cl… Nico Williams
- Re: Too many tools, was Things that used to be cl… Stan Kalisch
- Re: Too many tools, was Things that used to be cl… Joe Touch
- Re: Too many tools, was Things that used to be cl… Carsten Bormann
- Re: Too many tools, was Things that used to be cl… Joe Touch
- Re: Too many tools, was Things that used to be cl… Julian Reschke
- Re: Too many tools, was Things that used to be cl… John R Levine
- Re: Too many tools, was Things that used to be cl… Phillip Hallam-Baker
- Re: Too many tools, was Things that used to be cl… Phillip Hallam-Baker
- Re: Too many tools, was Things that used to be cl… Carsten Bormann
- Re: Too many tools, was Things that used to be cl… Phillip Hallam-Baker
- Re: Things that used to be clear (was Re: Evolvin… S Moonesamy
- Re: Evolving Documents (nee "Living Documents") s… Spencer Dawkins at IETF
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Stephen Farrell
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Job Snijders
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Brian E Carpenter
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Ted Lemon
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Ted Lemon
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: Evolving Documents (nee "Living Documents") s… Joel M. Halpern
- Re: Evolving Documents (nee "Living Documents") s… Christopher Morrow
- Re: Evolving Documents (nee "Living Documents") s… Job Snijders
- Re: Evolving Documents (nee "Living Documents") s… Joel M. Halpern
- Re: Evolving Documents (nee "Living Documents") s… Randy Bush
- Re: Evolving Documents (nee "Living Documents") s… Brian E Carpenter
- Re: Evolving Documents (nee "Living Documents") s… Job Snijders
- Re: Evolving Documents (nee "Living Documents") s… Jared Mauch
- Re: Evolving Documents (nee "Living Documents") s… Brian E Carpenter
- Re: Evolving Documents (nee "Living Documents") s… Stephen Farrell
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Ted Lemon
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Ted Lemon
- Re: Evolving Documents (nee "Living Documents") s… Jared Mauch
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Phillip Hallam-Baker
- Re: Evolving Documents (nee "Living Documents") s… John C Klensin
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- is there a specific proposal for living ops docs?… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: is there a specific proposal for living ops d… john heasley
- Re: Evolving Documents (nee "Living Documents") s… Christopher Morrow
- Re: Evolving Documents (nee "Living Documents") s… john heasley
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: Evolving Documents (nee "Living Documents") s… Christopher Morrow
- Re: Evolving Documents (nee "Living Documents") s… Christopher Morrow
- Re: Evolving Documents (nee "Living Documents") s… Nico Williams
- Re: is there a specific proposal for living ops d… Brian E Carpenter
- Re: is there a specific proposal for living ops d… Job Snijders
- Re: is there a specific proposal for living ops d… Brian E Carpenter
- Re: Evolving Documents (nee "Living Documents") s… Matthew Kerwin
- Re: Evolving Documents (nee "Living Documents") s… John C Klensin
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Christopher Morrow
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Martin Thomson
- Re: Evolving Documents (nee "Living Documents") s… Warren Kumari
- Re: Evolving Documents (nee "Living Documents") s… John C Klensin
- Re: Evolving Documents (nee "Living Documents") s… John C Klensin
- Re: Evolving Documents (nee "Living Documents") s… Keith Moore
- Re: Evolving Documents (nee "Living Documents") s… Salz, Rich
- Re: is there a specific proposal for living ops d… Randy Bush
- Re: is there a specific proposal for living ops d… Jared Mauch
- Re: is there a specific proposal for living ops d… Randy Bush
- Re: is there a specific proposal for living ops d… Jared Mauch
- Re: Evolving Documents (nee "Living Documents") s… Hans Petter Holen
- Re: is there a specific proposal for living ops d… Miles Fidelman