Reviewing the document, it looks very good overall. I have a few
comments and questions about Sections 1 through 4. The later sections
will be reviewed in a separate message.
Section 2:
Defines a number of terms, but not AAA server, which is first
referenced in Section 3.1. Similarly for
The final two IETF services to transition are email (including all
mailing lists) and the main web site (including the datatracker and
tools related to it -- this does not include tools.ietf.org which is an
independent web site). These are the two largest and most
complex moves.
The cut-over
At 2:25 PM -0500 1/27/08, Russ Housley wrote:
This just came in. I think it is rushed, but there really many need
to be a venue to discuss the issues that have been raised by the
Last Call of draft-carpenter-rfc2026-changes.
Without a venue, I'm not sure how any progress can be made. There
I'd like to comment as an individual on one part of our process for
doing IONs.
The process for publishing them has many bottlenecks and delays and we
need a better way of doing it. If we decide to continue with IONs, I
will provide detailed comments on issues with how we are doing them.
There have been two changes in the web configuration that may be
noticeable to you after the cut-over.
1. Up to this point there have been almost two dozen named and
independent web sites associated with the IETF. This has been
flattened to be less than half that many. Those that remain
There have been some changes in the email configuration that may be
noticeable to you after the cut-over.
1. We have updated the SPAM filtering of all email. This change should
reduce the overall amount of SPAM received by the IETF.
It is also an opportunity to remind the community of the
On 2008-01-30 10:35, Cullen Jennings wrote:
I'd like to comment as an individual on one part of our process for
doing IONs.
The process for publishing them has many bottlenecks and delays and we
need a better way of doing it. If we decide to continue with IONs, I
will provide detailed
The IESG has received a request from the Multicast Security WG (msec) to
consider the following document:
- 'On the applicability of various MIKEY modes and extensions '
draft-ietf-msec-mikey-applicability-07.txt as an Informational RFC
The IESG plans to make a decision in the next few weeks,
The IESG has approved the following document:
- 'SIEVE Email Filtering: Extension for Notifications '
draft-ietf-sieve-notify-12.txt as a Proposed Standard
This document is the product of the Sieve Mail Filtering Language Working
Group.
The IESG contact persons are Lisa Dusseault and Chris
The IESG has approved the following document:
- 'The EAP TLS Authentication Protocol '
draft-simon-emu-rfc2716bis-13.txt as a Proposed Standard
This document is the product of the EAP Method Update Working Group.
The IESG contact persons are Sam Hartman and Tim Polk.
A URL of this
There have been two changes in the web configuration that may be
noticeable to you after the cut-over.
1. Up to this point there have been almost two dozen named and
independent web sites associated with the IETF. This has been
flattened to be less than half that many. Those that remain
There have been some changes in the email configuration that may be
noticeable to you after the cut-over.
1. We have updated the SPAM filtering of all email. This change
should reduce the overall amount of SPAM received by the IETF.
It is also an opportunity to remind the community of the
12 matches
Mail list logo
