RE: Next step on web phishingdraft(draft-hartman-webauth-phishing-05.txt)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Next step on web phishingdraft(draft-hartman-webauth-phishing-05.txt)
- To: <ned.freed at mrochek.com>, "'Keith Moore'" <moore at cs.utk.edu>
- Subject: RE: Next step on web phishingdraft(draft-hartman-webauth-phishing-05.txt)
- From: "Debbie Garside" <debbie at ictmarketing.co.uk>
- Date: Tue, 11 Sep 2007 21:56:49 +0100
- Cc: ietf at ietf.org, discuss at apps.ietf.org, 'Iljitsch van Beijnum' <iljitsch at muada.com>, ietf-http-wg at w3.org, bmanning at ISI.EDU, saag at mit.edu, ietf-http-auth at osafoundation.org
- In-reply-to: <01ML8GHD48YO00005F@mauve.mrochek.com>
- List-help: <mailto:ietf-request@ietf.org?subject=help>
- List-id: IETF-Discussion <ietf.ietf.org>
- List-post: <mailto:ietf@ietf.org>
- List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-reqve null sections that's fine, if they feel they should be retained that's
- List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
- References: <46E2E54A.2050406@isode.com> <8B056441-7E57-46D4-9A2C-5BF7DE0297BF@muada.com> <420921CE-C4A9-49A8-9626-2BEAB70D7107@multicasttech.com> <26C12754-DA05-4545-84E8-2ECE136C5A2D@muada.com> <20070909234839.GA2020@boreas.isi.edu> <003101c7f465$9b90c9a0$0b00a8c0@CPQ86763045110> <01ML8DYIHPJQ003GRV@mauve.mrochek.com> <46E6F657.4040204@cs.utk.edu> <01ML8GHD48YO00005F@mauve.mrochek.com>
- Reply-to: debbie at ictmarketing.co.uk
- Thread-index: Acf0tHbuUjgnFndgS1K93T2ZSOfPrwAASNWw
> There are a lot of times when these sections aren't applicable,
> and having them in the final document just interferes with readability.
It depends on what sort of reading you're doing.
> I also think that a Terms and Definitions section might encourage
> document authors to make up new terms when they're not necessary, which
> would also interfere with readability. (geeks love to create new language.)
Very good point. Having lots of slightly varying definitions of various terms
could be hugely harmful.
RFC 2119 is a case in point. While I have some small issues with how RFC 2119
defines its terms, I've come to realize that having consistent meanings for
these terms is far more important.
Ned
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions
of the senders and do not imply endorsement by the IETF.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.