I think it would be much more useful if we could update the
document sufficiently to consider the telnet URI scheme
for Draft Standard or Full Standard.
The protocol itself meets the qualifications for a full
Standard document; it is widely deployed with multiple independent
implementations and
I previously sent my comments to the IESG, but I was
asked to re-raise the issue on the IETF mailing list
because ... The IESG at this point
seems to want public guidance on a document by document
basis... on the topic of how to move old documents
or protocols to Historic status. In this case,
May be IDN specialists will want to comment this.
http://www.shmoo.com/idn/homograph.txt
Is this exact? This is urgent as the IRI is based upon IDN and support of
multilingualism is a WSIS priority and comments for the WGIG are to close
the day after tomorrow.
Thank you.
jfc
May be IDN specialists will want to comment this.
http://www.shmoo.com/idn/homograph.txt
This is nothing new, analog to YAHOO.COM and YAH00.COM.
jaap
___
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf
--On Tuesday, 08 February, 2005 13:41 +0100 Jaap Akkerhuis
[EMAIL PROTECTED] wrote:
May be IDN specialists will want to comment this.
http://www.shmoo.com/idn/homograph.txt
This is nothing new, analog to YAHOO.COM and YAH00.COM.
Well, it is a little worse because there are tools
I'm in agreement with the purpose of updating these (and probably other
documents) to reflect the current state of affairs.
My comment is that the it is RFCs that move through the process, not parts
of RFCs. So, it would seem to me that an update to RFC 1738 needs to be
written: that drops wais,
Dear John,
you are right the lack of the really requested IRI in the bar is a true
problem. But this would we appealing for babel-names (the IDNs which
transcode in xn--squatting names such as http://xn--cocacola.com;).
Could not a correct solution be to have an option warning the
Hi John,
--On Tuesday, 08 February, 2005 13:41 +0100 Jaap Akkerhuis
[EMAIL PROTECTED] wrote:
May be IDN specialists will want to comment this.
http://www.shmoo.com/idn/homograph.txt
This is nothing new, analog to YAHOO.COM and YAH00.COM.
JFC (Jefsey) Morfin wrote:
May be IDN specialists will want to comment this.
http://www.shmoo.com/idn/homograph.txt
Is this exact? This is urgent as the IRI is based upon IDN and support
of multilingualism is a WSIS priority and comments for the WGIG are to
close the day after tomorrow.
That is
Jaap Akkerhuis wrote:
We are likely in violent agreement. I've been using cyrillic
characters looking like Latin ones in my slides as well as examples.
Russian people won't accept their 'C' shaped character represented
by anything (definitely not punycode) other than the 'C' shape.
And when
Dear James,
A Registry can certainly take care of SLD, not of lower levels. IMHO the
problem is no more with IDNs (no one want to change RFC 3490!), but to
avoid to propagate the problem into the IRI. For that we need to have a
precise langtag to precisely define the IDN locale in the IRI and
James,
At one level, you are clearly correct, and several other people
have made the same observation today and over the last four
years. Certainly, as my note and others indicated even before
you posted yours, this is old news. That fact doesn't change
things much, even if it has some limited
Date: 2005-02-08 08:39
From: John C Klensin [EMAIL PROTECTED]
Well, it is a little worse because there are tools that make
detection of the YAH00.COM problem and its relatives pretty easy
and those tools are widely understood. For example, forcing
those domain names to lower case makes
Per Harald's request, ISOC's legal counsel reviewed the latest
version of the IASA BCP and suggested a number of minor changes.
These changes are not intended to be substantive, but rather to
accommodate legalese or to improve clarity (in a legal sense). The
changes have been reviewed by and
JFC == JFC (Jefsey) Morfin [EMAIL PROTECTED] writes:
JFC Dear James, A Registry can certainly take care of SLD, not of
JFC lower levels. IMHO the problem is no more with IDNs (no one
JFC want to change RFC 3490!), but to avoid to propagate the
JFC problem into the IRI.
Handling
On Tue, 8 Feb 2005, Sam Hartman wrote:
Larry == Larry Masinter [EMAIL PROTECTED] writes:
Larry Does anyone see any real need to issue a new document on
Larry the gopher URI scheme merely to declare it Historic?
Yes. Our process currently requires a document action or protocol
action to move
Hi -
If anybody has problem reading .doc files, here is a version in pdf:
http://public.resource.org/adminrest/IETF-IASA-BCP-v6.pdf
Regards,
Carl
Per Harald's request, ISOC's legal counsel reviewed the latest
version of the IASA BCP and suggested a number of minor changes.
These changes
Bruce,
I'll try to respond to the issues and questions you raise, but
please note that the landscape here is strewn with dead horses
and that kicking them is not a particularly helpful or rewarding
activity.
--On Tuesday, 08 February, 2005 14:54 -0500 Bruce Lilly
[EMAIL PROTECTED] wrote:
John,
You are absolutely right. I believe there is a current discussion
within the Mozilla community to flag out IDN. There would certainly
help but would not help with 'sex.com' (as one guy noted on circleid)
if 'sex' is all written in Cyrillic.
I am also concern about creating new protocols
I want to also bring the UTR #36 Security Considerations for the
Implementation of Unicode and Related Technology. Although still draft, we
will be fleshing it out over time. Feedback is welcome.
http://www.unicode.org/reports/tr36/
Mark
- Original Message -
From: James Seng [EMAIL
On 03:36 09/02/2005, Mark Davis said:
I want to also bring the UTR #36 Security Considerations for the
Implementation of Unicode and Related Technology. Although still draft, we
will be fleshing it out over time. Feedback is welcome.
http://www.unicode.org/reports/tr36/
Brillant.
I think the
On Tue, 8 Feb 2005, Carl Malamud wrote:
Hi -
If anybody has problem reading .doc files, here is a version in pdf:
what happened to ascii?
http://public.resource.org/adminrest/IETF-IASA-BCP-v6.pdf
Regards,
Carl
Per Harald's request, ISOC's legal counsel reviewed the latest
version
The IESG has approved the following document:
- 'Entity MIB (Version 3) '
draft-ietf-entmib-v3-07.txt as a Proposed Standard
This document is the product of the Entity MIB Working Group.
The IESG contact persons are Bert Wijnen and David Kessens.
Technical Summary
This memo defines a
The IESG has approved the following document:
- 'Voucher Trading System Application Programming Interface (VTS-API) '
draft-ietf-trade-voucher-vtsapi-06.txt as an Informational RFC
This document is the product of the Internet Open Trading Protocol Working
Group.
The IESG contact persons
The Secure Network Time Protocol (stime) WG in the Security Area has concluded.
The IESG contact persons are Russell Housley and Sam Hartman.
The mailing list will be closed.
___
IETF-Announce mailing list
IETF-Announce@ietf.org
The Internet Open Trading Protocol (trade) WG in the Applications Area has
concluded.
The IESG contact persons are Ted Hardie and Scott Hollenbeck.
The mailing list will remain active.
___
IETF-Announce mailing list
IETF-Announce@ietf.org
26 matches
Mail list logo
