John C Klensin wrote:
--Frank Ellermann wrote:
...
Hopefully somebody can confirm that IND is correct, or not.
For HT and FF I hope the final version will somehow express
that both are not really bad, and as far as they're bad FF is
worse than HT.
See
Frank Ellermann wrote:
John C Klensin wrote:
It is ambiguous for HT.
Yes, but we typically don't care about this in protocols as
long as it behaves like one or more spaces. I think that's
Well, they don't exactly behave like a sequence of spaces.
(See below.)
the idea of WSP = SP /
To those considering the TLS-authz proposal:
The patent shenanigans of RedPhone Security have reduced implementation
status from open to taxed at the whim of RedPhone Security. This
should be enough to disqualify the proposal from further consideration
unless, and until, RedPhone Security grants
What are the retention requirements here Ray and what are the availability
requirements per the Stored Communications Act is the US and has this
transition ever been scoped out against these constraints? or is it the
IETF's intent to ignore US Law again?
Todd Glassey
- Original Message
Mr. Wilbur,
- Original Message -
From: Richard Wilbur [EMAIL PROTECTED]
To: ietf@ietf.org
Cc: [EMAIL PROTECTED]
Sent: Monday, October 22, 2007 2:42 PM
Subject: TLS-authz experimental standard
To those considering the TLS-authz proposal:
The patent shenanigans of RedPhone Security
On Mon, Jan 14, 2008 at 07:51:58AM -0800,
TS Glassey [EMAIL PROTECTED] wrote
a message of 134 lines which said:
or is it the IETF's intent to ignore US Law again?
The IETF is (or should be) an international organization. Why should
it respect the US law more than, say, the tanzanian law or
On Mon, Jan 14, 2008 at 07:51:58AM -0800, TS Glassey wrote:
What are the retention requirements here Ray and what are the availability
requirements per the Stored Communications Act is the US and has this
transition ever been scoped out against these constraints? or is it the
IETF's intent
Because the IAOC and ISOC are incorporated and do business in the US
and not Tanzania or Mongolia?
Regards,
-drc
On Jan 14, 2008, at 8:01 AM, Stephane Bortzmeyer wrote:
On Mon, Jan 14, 2008 at 07:51:58AM -0800,
TS Glassey [EMAIL PROTECTED] wrote
a message of 134 lines which said:
or is it
The transition of the following web sites:
iaoc.ietf.org
trustee.ietf.org
www.iab.org
has been completed. We encourage you to look through these sites
and verify the material you rely on and are familiar with. If you
identify an issue please submit an action request to:
[EMAIL
The FSF copntinues to attempt to re-open this decision.
I don't see any infomation content to these posts, beyond the already known
facts that 1) RMS has people read his Web site and 2) perpetrates a one-way
form of communication - we have to listen to him but he has no intention of
listening
At 6:00 PM -0600 1/11/08, Nicolas Williams wrote:
...
Finally, multi-user systems may need to authenticate individual users to
other entities, in which case IPsec is inapplicable[*]. (I cannot find
a mention of this in the I-D, not after a quick skim.)
[*] At least to my reading of RFC4301,
The archives are being transitions too.
At 10:51 AM 1/14/2008, TS Glassey wrote:
What are the retention requirements here Ray and what are the
availability requirements per the Stored Communications Act is the
US and has this transition ever been scoped out against these
constraints? or is it
The IESG wrote:
The IESG has received a request from an individual submitter to consider
the following document:
- 'IMAP METADATA Extension '
draft-daboo-imap-annotatemore-12.txt as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on
Hallam-Baker, == Hallam-Baker, Phillip [EMAIL PROTECTED] writes:
Hallam-Baker, The FSF copntinues to attempt to re-open this
Hallam-Baker, decision.
Phil, I think the important point here can be made in a much more
neutral manner. The last call period is closed. Additional
discussion
On Mon, Jan 14, 2008 at 02:25:53PM -0500, Stephen Kent wrote:
At 6:00 PM -0600 1/11/08, Nicolas Williams wrote:
...
Finally, multi-user systems may need to authenticate individual users to
other entities, in which case IPsec is inapplicable[*]. (I cannot find
a mention of this in the I-D,
On 2008-01-15 09:19, Sam Hartman wrote:
Hallam-Baker, == Hallam-Baker, Phillip [EMAIL PROTECTED] writes:
Hallam-Baker, The FSF copntinues to attempt to re-open this
Hallam-Baker, decision.
Phil, I think the important point here can be made in a much more
neutral manner. The last
On Mon, Jan 14, 2008 at 10:27:02AM -0800, Hallam-Baker, Phillip wrote:
The FSF copntinues to attempt to re-open this decision.
I don't see any infomation content to these posts, beyond the
already known facts that 1) RMS has people read his Web site and 2)
perpetrates a one-way form of
At 08:01 14-01-2008, Stephane Bortzmeyer wrote:
The IETF is (or should be) an international organization. Why should
it respect the US law more than, say, the tanzanian law or the
mongolian law?
The IETF is an organized activity of the ISOC. ISOC is incorporated
in the US as a non-profit.
At 2:06 PM -0600 1/14/08, Nicolas Williams wrote:
...
Ipsec does support
^
You're slipping :) :)
oh my!
per-user authentication if protocol ID and port pairs can be used to
distinguish the
and these are all IPv6 enabled sites...
Ray Pelletier wrote:
The transition of the following web sites:
iaoc.ietf.org
trustee.ietf.org
www.iab.org
has been completed. We encourage you to look through these sites
and verify the material you rely on and are familiar with. If you
Dean - I guess I don't get what the problem is. The IETF's process standards
require that there be two instances of a technological specification
implemented to create the proposed standard, so as long as that was done,
it seems to me that the only issue here is whether the parties who donate
Theodore Tso wrote:
Actually, to be fair, I don't think this can be laid at the feet of
the FSF. Todd Glassey replied to a message approximately 3 months old
with some legal reasoning that at best seems highly contorted, and at
worst total nonsense.
All of which raises the deeper
My mail client only shows the arrival date as today.
Admittedly I am on a somewhat limited Webmail version after my laptop hit a
halt and catch fire instruction. But the message has certainly been reinjected
somehow.
From: Dave Crocker [mailto:[EMAIL
Karlsson, Kent wrote:
Doing what you call 'old HTAB-compression' is a bad idea
Yes, nevertheless it is something that happens sometimes, and
protocols accepting *WSP or 1*WSP can handle the odd effects.
Starting a folded line (in headers) with HT isn't too bad.
[LS and PS]
They were
--On Monday, 14 January, 2008 11:11 +0100 Kent Karlsson
[EMAIL PROTECTED] wrote:
...
I think this document is at least one draft, maybe two or three
drafts, away from being of sufficient clarity and of sufficient
quality to become a standards document. In addition you state
that you don't
The Internet Society (ISOC) provides organizational and financial
support for the IETF. As part of the arrangements between ISOC and the
IETF, the IETF is called upon to name 3 Trustees to its Board (BoT),
with staggered 3 year terms. This requires that the IETF select one
Trustee each year.
A
The transition of the following web sites:
iaoc.ietf.org
trustee.ietf.org
www.iab.org
has been completed. We encourage you to look through these sites
and verify the material you rely on and are familiar with. If you
identify an issue please submit an action request to:
[EMAIL
The IESG has received a request from the IP over Cable Data Network WG
(ipcdn) to consider the following document:
- 'Management Event Management Information Base (MIB) for PacketCable-
and IPCablecom-Compliant Devices '
draft-ietf-ipcdn-pktc-eventmess-12.txt as a Proposed Standard
The
The IESG has approved the following document:
- 'IANA Allocation Guidelines for the Protocol Field '
draft-arkko-rfc2780-proto-update-02.txt as a BCP
This document has been reviewed in the IETF but is not the product of an
IETF Working Group.
The IESG contact person is Russ Housley.
A URL
29 matches
Mail list logo
