Lisa Dusseault wrote:
> one could define a Very Liberal Comparator (VLC) for general
> use. It would be handy to have one which matched e with E,
> é, è É... and matched o with O, ø, ô, and so on.
Good idea. I'm thinking of something in that direction for my
mail filters: At the moment any ty
I think that we need to decide what we are trying to achieve in any given
situation. I have been thinking mostly about DNS but the ideas are probably
more general:
Modifying Soebok's trichotemy, there are different uses that can be made of an
identifier:
0) Random
There is no systemati
--On Monday, 25 September, 2006 11:07 -0700 Lisa Dusseault
<[EMAIL PROTECTED]> wrote:
> On Sep 23, 2006, at 2:20 AM, Julian Reschke wrote:
>> But as a matter of fact, draft-newman-i18n-comparator-14
>> doesn't define any collations that would actually solve the
>> Unicode NF issue, so it's
I've got a "very liberal" comparator in production at the Linux Counter
project.
It mostly works, because the people who assign names tend to not assign
names that collide under the comparator.
But the strings that result from the comparator are quite distant from
"expected" strings in many c
It was 25 years ago this month that IP and TCP were formally standardized
by the publication of RFC 791 and RFC 793.
"Vint Cerf and Robert Kahn are widely credited with the design of TCP/IP,
and many others involved in the ARPANET project made significant
contributions," says the Internet Society.
> From: [EMAIL PROTECTED]
> It was 25 years ago this month that IP and TCP were formally
> standardized by the publication of RFC 791 and RFC 793.
It might be worth emphasizing to people that this is the anniversary of the
*RFC's* (from September, 1981), and *NOT* the anniversary of I
*>
*> There was a substantial discussion on the Internet-History mailing list
*> ([EMAIL PROTECTED]) of which date was the correct one for the
*> creation of TCPv4/IPv4, earlier this year (at the end of March, if anyone's
*> looking in the mailing-list archive). I don't know if we follo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
And one of the lessons learned that night (as the person cutting over
0/6 (aka 10.0.0.6, MIT-MULTICS):
Don't do cutovers like this on January 1st!
-Jeff
On Tue, Sep 26, 2006 at 11:35:21AM -0700, Bob Braden wrote:
>
> *>
>
Bob Braden wrote:
I believe that the birth date for the Internet (protocols) was Jan 1, 1983,
when the ARPAnet cut over from NCP to TCP/IP.
or perhaps 1976 when TCP was first implemented and tested, including
crossing administrative boundaries.
(There is a minor question about how to clas
Or perhaps the lesson should be that planning for the transition is as
important as the end state.
If you look at the big dig something like a quarter of their cost went into
keeping the traffic movving while they moved the highway.
> -Original Message-
> From: Jeffrey I. Schiller [mai
Phillip Hallam-Baker wrote:
*> Or perhaps the lesson should be that planning for the transition is as
important as the end state.
Please see RFC 801, "NCP/TCP TRANSITION PLAN" by Jon Postel.
See also RFCs 845 and 846 on the transition progress.
Bob Braden
_
Still got the button? -s
On Sep 26, 2006, at 14:35, Bob Braden wrote:
*>
*> There was a substantial discussion on the Internet-History
mailing list
*> ([EMAIL PROTECTED]) of which date was the correct
one for the
*> creation of TCPv4/IPv4, earlier this year (at the end of
March,
I was the person who wrote the IMP code and, on January 1, "pulled the switch" to disable port 0 (NCP) on the ARPANET IMP interfaces. I had also included the abiltity to override the switch on a port-by-port basis, and we had a procedure in place well prior to the cutover for approved exceptions t
The IESG wrote:
> as a Proposed Standard
What's a "domain suffix" ? I don't see or missed it in 3315
and 4361. LDH labels with a TLD maybe ? Are they guaranteed
to be "valid" in some ways, could a host "name" send mail as
"name.suffix" ? Could it use "@name.suffix" in Message-IDs ?
Does the
OK, Andy. Can we put you in charge of the IP v4/v6 transition, say
January 1, 2009?
:-)
Ole J. Jacobsen
Editor and Publisher, The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972 GSM: +1 415-370-4628
E-mail: [EMAIL PROTECTED] URL: http://www.cisco.com/ipj
___
On Sep 26, 2006, at 1:15 PM, Frank Ellermann wrote:
Sorry, probably that's all obvious, but where is ["domain suffix"]
defined ?
At the Verisign site. It is the new-speak for use when all us ancient
geeky types would prefer "TLD".
___
Ietf mail
Ole,
That's a good one! I would hate to see the length of that exception list :-) And who would have the authority to grant the exceptions
Cheers,
Andy
-
On 9/26/06, Ole Jacobsen <[EMAIL PROTECTED]> wrote:
OK, Andy. Can we put you in charge of the IP v4/v6 transition, sayJ
> "John" == John C Klensin <[EMAIL PROTECTED]> writes:
John> --On Monday, 25 September, 2006 11:07 -0700 Lisa Dusseault
John> <[EMAIL PROTECTED]> wrote:
>> On Sep 23, 2006, at 2:20 AM, Julian Reschke wrote:
>>> But as a matter of fact, draft-newman-i18n-comparator-14
>>>
Fred Baker wrote:
["domain suffix"]
> It is the new-speak for use when all us ancient geeky types
> would prefer "TLD".
I thought it's some new kind of DHCP builtin DynDNS service.
If it's a TLD I'm perplexed why that would ever change for a
given DHCP server. And for clients of different serv
Ole Jacobsen wrote:
OK, Andy. Can we put you in charge of the IP v4/v6 transition, say
January 1, 2009?
That soon?
That's only 15 years after work on IPv6 began.
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
___
Ietf mailing li
20 matches
Mail list logo
