[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Comment: draft-ietf-crisp-requirements-05.txt
- To: iesg@ietf.org
- Subject: Comment: draft-ietf-crisp-requirements-05.txt
- From: Allison Mankin <mankin@psg.com>
- Date: Thu, 10 Jul 2003 07:58:02 -0700
My previous comment on the following text's use of "transport"
resulted in no changes, perhaps because Leslie pointed out that
"transport mechanisms" meant to the WG beep, http or something of that
sort. But since in the sentence before, there is the term "transport
layer", this is confusing. So I would like to see a slight rewrite of
this to avoid the transport jangle, with an RFC-Editor note
Something like: "The protocol MUST employ the use
of network and transport layer standards as defined by the Internet
Engineering Task Force. The protocol MUST define one or more
higher layer transport mechanisms for mandatory implementation.
^^^^^^^^^^^^
3.1.2 Minimal Technical Reinvention
The protocol MUST NOT employ unique technology solutions for all
aspects and layers above the network and transport layers and SHOULD
make use of existing technology standards where applicable. The
protocol MUST employ the use of network and transport layer standards
as defined by the Internet Engineering Task Force. The protocol MUST
define one or more transport mechanisms for mandatory implementation.