On 4/4/2014 4:12 PM, Dick Franks wrote:
Stephen asked about the last sentence:
New services will however generally only be made
available in ways that use security protocols such as
TLS.
Which to my eye looks like a conclusion; without shred of
justification and before any meaningful discussion has taken place.
I don't see anything odd about the statement. My input, once again and
I'll leave it at this, there might be 'new services' where the IETF
has no "legal" OR "Security Audit" choice but to provide it in secured
only mode and thus, for those who need to get access MUST be updated
with modern software client access tools that support such security,
not just TLS. The IETF lawyer should determine if they must comply
with PCI/DSS security audits. Thats all. It wasn't difficult.
Of course, where it isn't needed, its common sense to keep legacy
access for the old timers to access it via their own means or tools.
That includes me with various simple access tools, in particular, a
non-SSL FTP scripting tool for quick command line download of RFC
files from the IETF ftp site. If that was made SSL only, we would
have to update the script. I don't have time for that so it would
"break something" for me.
26 messages on and the consensus thus far is that an answer to Lloyd
Wood's one-liner is very much required.
I didn't see anything that stood out. Are you referring to his why
question? Really? It seems others answered why.
Thanks for your comments.
--
HLS