To qualify for protection, an industrial design must be aesthetic,
and I believe that elegant design should be one of our goals in protocol
design.
However, industrial designs are divorced from all technical aspects of
the article,
and thus at least some small portion of our ongoing work may be
I think this is a good and much-needed document. Thanks to the authors and
whoever else contributed to it.
The title and the abstract starts reading like a general AAA key management
guideline, but later the document gets too EAP-specific. Is the intent to
provide general guidelines that should
Yaakov - Did you cut that from Nolo's site - they are good people.
My argument is that the negotiation of the protocol inside the IETF's
vetting process is identical to two engineers arguing and then coming to a
new aesthetic implementation, its the new fenders for the truck., or a new
warning
http://www.kulefornia.blogspot.com
ALL RIGHTS RESERVED
From: Yaakov Stein [EMAIL PROTECTED]
To: ietf@ietf.org
Subject: RE: WIPO issues (was: Network Endpoint Assessment (nea))
Date: Tue, 10 Oct 2006 08:59:15 +0200
To qualify for protection, an industrial design must be aesthetic,
and I
Be careful offering legal advise.
I wasn't offering legal advice but thanks for the warning; if I ever
mean to offer legal advice I will explicitly call it out as legal
advice. Generally I express my opinions, thoughts, and feelings and not
legal advice.
A few people have pointed out that
Hey Ted - the more I thought about this post of yours the more it annoyed
me. You see - when a WG chair doesn't want someone saying something in their
WG and they control the number of players in that WG, they will always
control the consensus such as it is.
The point is that there is no where to
Todd,
I've received several complains from people that think that you are crossing
the limit again and being off-topic with this thread and I seriously agree
with them.
Consequently I warn you. If you keep going on this, I will apply a new ban
(two weeks, as it will be your second one in a very
Who filed the complaints? if you are accusing me of something I have the
right to know of what I am accused and by whom.
Todd Glassey
- Original Message -
From: JORDI PALET MARTINEZ [EMAIL PROTECTED]
To: todd glassey [EMAIL PROTECTED];
Cc: [EMAIL PROTECTED]
Sent: Tuesday, October 10,
I have seen a lot of discussion about whether NEA provides
network protection. In fact, it has been suggested that
the charter be revised to say NEA must not be considered
a protection mechanism for networks. I don't agree.
Let's start by examining this concept of network protection.
It's an
Todd,
People got very irritated with this type of messages and actually even
complain why I'm not more strict. I got at the time being already 3 new
complains after this message and obviouly I don't need to justify to you who
is complaining.
Clearly you crossed the line once more, and it took
Yes actually you do -how does anyone complained against know who is
complaining or why? - if the complaints are not public then the oversight is
not real - its a paper fiction - a lie in print.
Speaking of lies in print this is why IETF complaints are addressed and
penalties for them assessed
I'm sorry to enter this fray, but I'd like to point out that while I
respect Todd's request to know who is accusing him and why, the rest of
us don't need to be copied that information. In fact, it is better that
we aren't copied because to do so would be unfair to the complainer(s).
Discipline
Hi Eric,
I don't really agree with that. I've first the obligation to keep the
privacy about any email received in private. Of course, I can always suggest
that the people which complained in private speak up in the list, but I
don't think that noise will help anyone.
If there is a need to
Hi Steve,
Let me start with a couple of fundamental points that have already been
stated before.
A. Any network is exposed to threats from lying endpoints, compromised
endpoints and unknown vulnerabilities even on NEA-compliant endpoints.
B. A network needs to be protected against such generic
On Tue, Oct 10, 2006 at 07:45:48PM -0500, JORDI PALET MARTINEZ wrote:
Hi Eric,
I don't really agree with that. I've first the obligation to keep the
privacy about any email received in private. Of course, I can always suggest
that the people which complained in private speak up in the list,
The IESG has received a request from an individual submitter to consider
the following document:
- 'Fragmentation Considered Very Harmful '
draft-heffner-frag-harmful-02.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this
A new Request for Comments is now available in online RFC libraries.
RFC 4636
Title: Foreign Agent Error Extension for
Mobile IPv4
Author: C. Perkins
Status: Standards Track
Date: October 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4681
Title: TLS User Mapping Extension
Author: S. Santesson, A. Medvinsky,
J. Ball
Status: Standards Track
Date: October 2006
A new Request for Comments is now available in online RFC libraries.
RFC 4680
Title: TLS Handshake Message for Supplemental
Data
Author: S. Santesson
Status: Standards Track
Date: October 2006
19 matches
Mail list logo
