A couple of nits:
s3: It might be helpful to make the first three paras into a bulleted
list and add an introductory sentence like:
'There are various ways in which an extension to an IETF can be
introduced into the IETF:'
s3, para 3: If my understanding is correct, a document from the
On 8/29/06, Julian Reschke [EMAIL PROTECTED] wrote:
Section 5.3.4., para. 4:
In the case where the data stored by a server as a result of a PUT
request is not equivalent by octet equality to the submitted
calendar
object resource, the behavior of the ETag response header is
-Original Message-
From: Richard Shockey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 6:55 PM
To: 'IETF-Discussion'
Subject: What is going on with the NOMCOM
Maybe my mail filters are failing but I understand there is a problem with
the selection process.
This seems to be on the IETF NOMCOM web page but I do not see it in the
ietf@ietf.org archives.
I suggest that given the unique importance of this NOMCOM cycle that a
fuller explanation is in order.
First .. the instant there was a problem the IETF community should have been
notified in full
Maybe my mail filters are failing but I understand there is a problem with
the selection process.
Can some one explain this ASAP.
Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
sip:rshockey(at)iptel.org
sip:5651(at)neustarlab.biz
One of the things missing from this years list of volunteers is their
association. That's one of the inputs into the selection algorithm
as the number of voting members from a particular association is
limited to two. I'd ask that the Nomcom chair include this in the
list of volunteers.
The reset should not be permitted.
The problem here is that the IAB and IESG could use this precedent to avoid
appointment of certain individuals to the NOMCOM.
The situation might appear to be that a member of the crazy gang got choosen
and someone wants to block them.
Given the tenuous
I agree with Phillip - there is no harm here. If someone ineligible
had happened to be selected, they would have been immediately
disqualified and the next number on the list selected. That's why
you actually ask for about 16 numbers to be output when you run the
program which outputs the
The IESG has received a request from the Global Routing Operations WG to
consider the following document:
- 'Operation of Anycast Services '
draft-ietf-grow-anycast-04.txt as a BCP
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please
The IESG has approved the following document:
- 'Observed DNS Resolution Misbehavior '
draft-ietf-dnsop-bad-dns-res-06.txt as a BCP
This document is the product of the Domain Name System Operations Working
Group.
The IESG contact persons are David Kessens and Dan Romascanu.
A URL of this
The IESG has approved the following document:
- 'NP Parameters for the tel URI '
draft-ietf-iptel-tel-np-11.txt as a Proposed Standard
This document is the product of the IP Telephony Working Group.
The IESG contact persons is Cullen Jennings.
A URL of this Internet-Draft is:
11 matches
Mail list logo
