[newtrk] SRD - normative or not?
John Leslie <john@jlc.net> Wed, 19 October 2005 15:59 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESGLV-0000PT-Uh for newtrk-archive@megatron.ietf.org; Wed, 19 Oct 2005 11:59:18 -0400
Received: from mailapps.uoregon.edu (mailapps.uoregon.edu [128.223.142.45]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24803 for <newtrk-archive@lists.ietf.org>; Wed, 19 Oct 2005 11:59:08 -0400 (EDT)
Received: from mailapps.uoregon.edu (IDENT:U2FsdGVkX19bCITk09klmV7mpTCAUQiHuaLG6ENKxxc@localhost [127.0.0.1]) by mailapps.uoregon.edu (8.13.4/8.13.4) with ESMTP id j9JFuF6u021077; Wed, 19 Oct 2005 08:56:15 -0700
Received: (from majordom@localhost) by mailapps.uoregon.edu (8.13.4/8.13.4/Submit) id j9JFuFBJ021076; Wed, 19 Oct 2005 08:56:15 -0700
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.9]) by mailapps.uoregon.edu (8.13.4/8.13.4) with ESMTP id j9JFuEhS021072 for <newtrk@lists.uoregon.edu>; Wed, 19 Oct 2005 08:56:14 -0700
Received: by mailhost.jlc.net (Postfix, from userid 104) id 9DD2AE057D; Wed, 19 Oct 2005 11:56:12 -0400 (EDT)
Date: Wed, 19 Oct 2005 11:56:12 -0400
From: John Leslie <john@jlc.net>
To: John C Klensin <john-ietf@jck.com>
Cc: Douglas Otis <dotis@mail-abuse.org>, 'NEWTRK Mailing List' <newtrk@lists.uoregon.edu>
Subject: [newtrk] SRD - normative or not?
Message-ID: <20051019155612.GB30745@verdi>
References: <001901c5d07d$12441bb0$1df1070a@corp.adobe.com> <9A48C561-95E6-4AD4-8F6D-C5202F920D6C@mail-abuse.org> <E7F40996197A9D2E9F2B7C96@scan.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E7F40996197A9D2E9F2B7C96@scan.jck.com>
User-Agent: Mutt/1.4.1i
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: John Leslie <john@jlc.net>
John C Klensin <john-ietf@jck.com> wrote: > > I have to agree with Larry. There is nothing inherent in the > ISD proposal that requires that it contain either more or less > information, or a different granularity, etc., from SRDs. I hesitate to comment on ISDs -- I'm not sure we're all talking about the same thing. However, I'm happy to talk about SRDs. > As I understand things, there were, when you proposed SRDs, only > two key differences between the ISD concept and the SRD one: > > (i) As mentioned above, ISDs are explicitly normative, > to the point that they become the formal definition of > the standard, are the real subject of IETF Last Calls > with RFCs being included in the last call as normatively > cited supporting documents. SRDs, as I understand them, > do not have that property. SRDs are not normative, IMHO. They describe sets of RFCs, of which each RFC may or may not be normative. If this is not clear in the draft http://www.ietf.org/internet-drafts/draft-otis-newtrk-rfc-set-02.txt feel free to propose text to make it clearer. > (ii) Largely because they have that normative property, > ISDs must contain at least some text, and normative text > at that, explaining what they are about. They cannot be > just list of things that go together, providing > informative cross-references among those things. When > the SRD concept was first floated, I understood SRDs as > potentially being links-only, with no local substantive > text. As of the time the WG meeting in Paris ended, I > understood that SRDs had evolved to potentially contain > some local text and possibly even to require some. Admittedly, I was not _in_ Paris, but I was following the audio. I do not recall anything about requiring text, least of all any normative text, in SRDs. The current I-D makes it clear that <srdref> is an empty element, which _cannot_ contain text. I suppose it could be argued that the <core>, <extensions>, <guidance>, <replaces>, <experimental>, and <companion> sections could contain text, although that is not the intent. The only free-format sections are intended to be <title> and <description>. <title> is intended for searching, and <description> is intended merely to describe the set, not its members. > So there may be little substantive difference between the two > proposals along that text versus no-text dimension any more. IMHO, SRDs do not contain any normative text. I accept John Klensin's opinion that ISDs _must_ contain normative text. I think this difference remains unchanged. -- John Leslie <john@jlc.net> . newtrk resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html
- [newtrk] I-D ACTION:draft-ietf-newtrk-interop-rep… Internet-Drafts
- [newtrk] draft-ietf-newtrk-interop-reports-00.txt Douglas Otis
- RE: [newtrk] draft-ietf-newtrk-interop-reports-00… Larry Masinter
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… Douglas Otis
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… John C Klensin
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… Spencer Dawkins
- [newtrk] SRD - normative or not? John Leslie
- "Normative"? (Re: [newtrk] SRD - normative or not… Harald Tveit Alvestrand
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Douglas Otis
- Re: "Normative"? (Re: [newtrk] SRD - normative or… John C Klensin
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Douglas Otis
- Re: "Normative"? (Re: [newtrk] SRD - normative or… John C Klensin
- [newtrk] Normative & standards track Larry Masinter
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Douglas Otis
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Spencer Dawkins
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Harald Tveit Alvestrand
- Re: "Normative"? (Re: [newtrk] SRD - normative or… John Leslie
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Harald Tveit Alvestrand
- Re: "Normative"? (Re: [newtrk] SRD - normative or… Douglas Otis
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… Douglas Otis
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… Brian E Carpenter
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… C. M. Heard
- Re: [newtrk] draft-ietf-newtrk-interop-reports-00… Brian E Carpenter