Russ and other IESG members,
I have been trying to avoid getting embroiled in IETF process
issues since the collapse of NEWTRK, but, after reviewing
draft-housley-two-maturity-levels and the discussion on the
IETF list, the situation leaves me little choice other than
reengaging. Several of the c
Well folks can certainly do what they want to do. And the IETF has a
lamentable record of some protocols that don't accomplish much. But the core
of this proposed WG is based on a fallacy. ViPR cannot verify or
authenticate the responsible party for a E.164 number. It is incapable of
doing so since
Please read the forwarded message below.
It describes the Final Call for Volunteers for the 2010-11 Nomcom. We could
still use another 10-20 volunteers.
The IETF nominating committee appoints folks to fill the open slots on the
IAOC, the IAB, and the IESG. The 10 nominating committee members
All,
To date, we have 80 volunteers for this year's nomcom as seen below.
We could still use more volunteers. You may volunteer until 17:00 PDT (24:00
UTC) this Thursday, July 8, 2010.
The final call for volunteers will be issued today with the details on how to
volunteer, so please consi
We've had deployments where we've taken over the hotel's wireless
Infrastructure and as result been expected to serve their customers as well...
Doing so is more or less incompatible with authenticated network access. It
imagine us doing that again sometime...
Joel
Joel's iPad
On Jul 4, 2010,
That is understood, Andrew's comment I seconded was about the
possibility of the change becoming permanent after Beijing.
--
Ciao,
Enrico
Sent from my iPhone
On Jul 3, 2010, at 21:19, "Ole Jacobsen" wrote:
>
> Enrico,
>
> Nobody has suggested there was anything wrong with the old (NUL)
> acces
