Requirements Document Update
"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 04 January 2002 14:01 UTC
Return-Path: <owner-ietf-provreg@cafax.se>
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.1/8.12.1) with ESMTP id g04E16C2006721 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 4 Jan 2002 15:01:06 +0100 (MET)
Received: from localhost (localhost [[UNIX: localhost]]) by nic.cafax.se (8.12.1/8.12.1/Submit) id g04E16Ym006720 for ietf-provreg-outgoing; Fri, 4 Jan 2002 15:01:06 +0100 (MET)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.1/8.12.1) with ESMTP id g04E14C2006715 for <ietf-provreg@cafax.se>; Fri, 4 Jan 2002 15:01:05 +0100 (MET)
Received: from vsvapostalgw2.prod.netsol.com (vsvapostalgw2.prod.netsol.com [216.168.234.29]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id JAA27604 for <ietf-provreg@cafax.se>; Fri, 4 Jan 2002 09:01:03 -0500 (EST)
Received: by vsvapostalgw2.bkup1 with Internet Mail Service (5.5.2653.19) id <ZVV42570>; Fri, 4 Jan 2002 09:01:23 -0500
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189B4F9@vsvapostal3.bkup6>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'ietf-provreg@cafax.se'" <ietf-provreg@cafax.se>
Subject: Requirements Document Update
Date: Fri, 04 Jan 2002 08:51:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
Earlier this week Ed Lewis received some additional comments from the IESG directed at draft-ietf-provreg-grrp-reqs-03.txt. I've made the requested changes, and sent an updated document to the I-D administrator a few moments ago. Here's a summary of the changes: 1. Changed the last sentence in section 4.4. "The protocol SHOULD be serviceable over multiple standard communications protocols." was changed to "The protocol MUST only be run over IETF approved protocols that feature congestion control, such as TCP and SCTP." 2. More fixes to "may", "must", and "should". Lower-case variants of these words were changed to alternate terms to avoid confusion with directives described in RFC 2119. 3. Updated the "Acknowledgements" section. I went through the list archives and collected the names of everyone who provided commentary on the document. This wasn't an IESG comment, but I took the opportunity to get it done. 4. Separated references into normative and informative subsections. The IESG apparently wants this sort of separation to help make normative reference dependencies more clear. -Scott-
- RE: Requirements Document Update Scott Bradner
- Re: Requirements Document Update Eric Brunner-Williams in Portland Maine
- Re: Requirements Document Update Edward Lewis
- Re: Requirements Document Update Allison Mankin
- Re: Requirements Document Update Dave Crocker
- RE: Requirements Document Update Patrik Fältström
- RE: Requirements Document Update Edward Lewis
- Re: Requirements Document Update Bill Manning
- Re: Requirements Document Update Lars-Johan Liman
- Re: Requirements Document Update Eric Brunner-Williams in Portland Maine
- Re: Requirements Document Update Bill Manning
- RE: Requirements Document Update Hollenbeck, Scott
- Requirements Document Update Hollenbeck, Scott