Second Call for Nominations: IETF-Selected ISOC Trustee

[IAB Chair]

This is a second call for candidates. The first call was posted to this
list jan 14 2008.

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 description of the IAB's process for selecting the Trustee each year
can be found in RFC3677.

* Jan 14   : Open nomination period

* Feb 24   : Close of the nomination period

* April 7 or before: IAB selection delivered to IESG for confirmation

* May 18  or before: Delivery of final confirmed selection to the ISOC
Elections Committee for announcement with the rest
of the new ISOC BoT slate.

Nominations
---

Nominations (including self-nominations) should be sent to the IAB --
[EMAIL PROTECTED] Please include e-mail contact details with the nomination.

Nomination Details
-

Nominees should be aware that ISOC Trustees are elected to three
year terms with approximately one third of the Board of Trustees
elected each year. The responsibilities of a Trustee include fiscal
management of the Internet Society, fundraising, and participation
in 3 physical Board meetings plus 3 conference-call meetings per
year.  The desirable characteristics of a candidate that are specific
to the IETF-selected ISOC BoT member are outlined in section 2 of
RFC 3677.

Nominees will be asked to provide to the IAB:

  1. Confirmation of their willingness to be considered within this
 process.

  2. Full name and contact information.

  3. A statement confirming willingness and ability to devote an
 appropriate level of time to activities associated with the
 position of Trustee.

  4. A brief biography outlining experience and background.

  5. A statement of interests, concerns about the Internet Society,
 goals as a Trustee and motivation to serve as a Trustee.

  6. Any further information that is relevant to the work of the IAB
 in considering your nomination.



Care of Personal Information


The following procedures will be used by the IAB in managing this
process:

  - The candidate's name will be published, with all other
candidate names, at the close of the nominations period

  - Excerpts of the information provided to the IAB by the
nominated candidate will be passed to the IESG as part of the
confirmation process. The IESG will be requested to maintain
confidentiality of the candidate's information

  - Except as noted above, all information provided to the IAB
during this process will be kept confidential to the IAB.


Current IETF-Selected Trustees
---

The current IETF-Selected ISOC Trustees and their term of
appointment are:

 -  Fred Baker 2005 - 2008 (*)

 -  Patrik Faltstrom   2006 - 2009

 -  Ted Hardie 2007 - 2010

  (*) Current term expires in 2008


-- Olaf Kolkman
 IAB Chair.
___
IETF-Announce mailing list
IETF-Announce@ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

Last Call: draft-ietf-netlmm-proxymip6 (Proxy Mobile IPv6) to Proposed Standard

[The IESG]

The IESG has received a request from the Network-based Localized Mobility 
Management WG (netlmm) to consider the following document:

- 'Proxy Mobile IPv6 '
   draft-ietf-netlmm-proxymip6-09.txt as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
[EMAIL PROTECTED] mailing lists by 2008-02-20. Exceptionally, 
comments may be sent to [EMAIL PROTECTED] instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-netlmm-proxymip6-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_iddTag=15940rfc_flag=0

___
IETF-Announce mailing list
IETF-Announce@ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce

Re: Call for Comment: RFC 4693 experiment

[Harald Alvestrand]

Cullen Jennings skrev:

 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.
 Overall I think we would need tools so that an ION author can put a
 new version, reviewers could easily see the diffs from the previous
 version, and when the document is approved by the approving body, it
 gets posted and does not require manual editing of the document after
 it was approved. 
one comment... the procedure as described in the ION RFC has exactly two
requirements:

- that one should be able to tell who approved it, and when
- that one should be able to tell the difference between a final
document and a draft.

I think we need to continue to have both of these properties.

There's no requirement that a process exist for handling them, or even
that it be consistent between IONs. The existing process is,
deliberately, unconstrained by the RFC.

I could argue that we might need fewer tools, not more; any tool you
create increases the number of tools one has to learn in order to get
one's job done. But that's part of what the experiment has been about.

  Harald

___
IETF-Announce mailing list
IETF-Announce@ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce