Dave,
Thanks for your clarification, now I understand this has converged to
a more contract language issue.
At this stage, I may not be able to help on the detail languages since
I guess the hoster or IAOC already
have been deeply involved in it.
Anyhow, I apprecaite that you make everybody more
On 9/23/09, Nicolas Williams nicolas.willi...@sun.com wrote:
On Wed, Sep 23, 2009 at 07:54:56PM +0200, Simon Josefsson wrote:
I have noticed an additional problem related to additional data in
SCRAM. RFC 4422 section 5 item 2b says:
b) An indication of whether the server is
From: Hui Deng denghu...@gmail.com
Lastly, I think that everybody have to self-censor about what he does.
It's not clear that (self-)censorship is going to be the worst problem from
an IETF in the PRC. One of the things I would be most concerned about is the
PRC government using this
The use of market mechanisms to allocate radio spectrum is now pretty
much the norm around the world. The only countries that might object
to such mechanisms on ideological grounds are either powerless to
object (Cuba, North Korea) or considerably more concerned about
ensuring access to IP
I think the point is that the IESG should probably refer the doc to
the uri-review team to look for any red flags. Mistakes in URI
specs are common (speaking has one that has made some).
The editors asked the uri-review list for feedback in July of this
year, as required by RFC 4395.
--
--On Friday, October 02, 2009 11:55 -0400 Noel Chiappa
j...@mercury.lcs.mit.edu wrote:
It's not clear that (self-)censorship is going to be the worst
problem from an IETF in the PRC. One of the things I would be
most concerned about is the PRC government using this meeting
for propoganda
On 18 September 2009 the IAOC requested input via the IETF list and a
survey regarding a venue contract provision concerning the hotel's
right to terminate the IETF meeting under certain conditions. We
sought to determine the impact of this provision on the meeting and
the potential
The IESG has approved the following document:
- 'Use of SHA-2 algorithms with RSA in DNSKEY and RRSIG Resource Records
for DNSSEC '
draft-ietf-dnsext-dnssec-rsasha256-14.txt as a Proposed Standard
This document is the product of the DNS Extensions Working Group.
The IESG contact
The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'Virtual Subnet Selection Options for DHCPv4 and DHCPv6 '
draft-ietf-dhc-vpn-option-11.txt as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and
On 18 September 2009 the IAOC requested input via the IETF list and a
survey regarding a venue contract provision concerning the hotel's
right to terminate the IETF meeting under certain conditions. We
sought to determine the impact of this provision on the meeting and
the potential
A new Request for Comments is now available in online RFC libraries.
RFC 5648
Title: Multiple Care-of Addresses Registration
Author: R. Wakikawa, Ed.,
V. Devarapalli, G. Tsirtsis,
T. Ernst, K. Nagami
11 matches
Mail list logo
