rnet-Draft that is published as an RFC, or that has remained
unchanged in the Internet-Drafts directory for more than six months
without being recommended by the IESG for publication as an RFC, is
simply removed from the Internet-Drafts directory. At any time, an
Internet-Draft may b
by a consultant to the IEEE RA followed by
IEEE RAC confirmation.
Since Ethertypes are a fairly scarce resource, the IEEE RAC has let us
know that they will not assign a new Ethertype to a new IETF protocol
specification until the IESG has approved the protocol specification for
publication as an
The Routing and Addressing Directorate (RADir) is closed. The RADir was
chartered by Brian Carpenter and Leslie Daigle when they were IETF Chair and
IAB Chair, respectively. The RADir has not done anything in quite some time,
and
it is time to close. Thank you to the members of RADir for their
Colleagues,
The IESG has observed very rough consensus in favor of the allocation proposed
in draft-weil-shared-transition-space-request. Therefore, the IESG will approve
the draft. In order to acknowledge dissenting opinions and clarify the IETF
position regarding IPv6, the IESG will attach
To provide a complete picture, I should have said something about the
P2PSIP working group in the announcement. Sorry for omitting it.
Because the P2PSIP WG is nearing the end of its chartered work, P2PSIP
is not being moved from the RAI Area to the TSV Area.
On behalf of the IESG,
Russ Housley
The IESG has decided to move the ALTO and DECADE working
groups from the Applications Area to the Transport Area. Two
factors played a role in this decision. First, the IESG feels
that consolidating the standardization of peer-to-peer
technologies in one Area will strengthen this important
The IESG is seriously considering a WG and BOF scheduling experiment. The
goal of the experiment is to provide WG agenda sooner and also provide
more time to craft BOF proposals.
The proposed experiment includes three parts. First, schedule all BOFs
for Monday afternoon. Second, schedule WGs
This statement provides guidance from the IESG on selection of a
Document Shepherd for documents from IETF working groups and documents
from individuals.
RFC 4858 defines the role of the Document Shepherd for documents from
IETF working groups, and it also says:
The Document Shepherd is
On 29-Sep-2009, the IESG issued a Last Call draft-ietf-idnabis-mappings
("Mapping Characters in IDNA"). On 16-Mar-2010, Lisa Dusseault, the
shepherding Area Director for this document, notified the IDNAbis
Working Group that the IESG will not proceed with publication of this
document. Th
RFC 3777 requires that voting members of the nominating committee
(NomCom) be selected from volunteers that have attended at least three
of the last five IETF meetings. The IAOC is conducting a day pass
experiment, making it necessary to clarify the NomCom eligibility rules
to address IETF particip
This is an update to the Last Call that is currently in progress.
The IESG is considering the following Statement on the Day Pass
Experiment. The IESG plans to make a decision in the next few weeks on
this statement, and the IESG actively solicits comments on this
statement. Please send
The IESG is considering the following Statement on the Day Pass
Experiment. The IESG plans to make a decision in the next few weeks on
a policy statement, and the IESG actively solicits comments on this
action. Please send substantive comments to the ietf@ietf.org mailing
lists by 2010-05-20
During the 76th IETF meeting, the Transport Area sponsored a Broadband
Home Gateway BoF, called HOMEGATE. Since that time, interested IETF
participants have been working to narrow the scope of the draft charter
and to reach out to other Standards Development Organizations (SDOs) to
ensure that the
The IESG approved publication of this document, and then the RFC Editor
noticed that it should have been approved as a BCP not a Proposed
Standard. If you have any concerns with this document being published as
a BCP, please send a message stating your reasons to i...@ietf.org in the
next few
As described in BCP 101 (RFC 4071) and BCP 113 (RFC 4333),
the IESG and the IAB each select one person for a two-year IAOC
term in alternate years. This year, the IESG will select one person
for a term beginning in March 2010.
Following the call for nominations, which ran through 16 November 2009
Ole Jacobsen is the IAOC member that was appointed by the IESG, and
his two-year term is up in March. The IESG is starting the process
to fill this seat in March 2010, with the term ending in March 2012.
The IESG is responsible for filling one seat every other year. BCP 101
says:
The IAOC
The IESG has received a request from an individual submitter to consider
the following document:
- 'MIME Type Registrations for 3GPP Multimedia files'
RFC 3839 as a Historic
RFC 3839 defines the original audio/3gpp and video/3gpp MIME
media type registrations. These registr
This IESG Statement obsoletes all earlier IESG Statements regarding
Copyright statements in MIB and PIB Modules.
The IESG is providing this guidance to align current practice with
RFC 5377, RFC 5378, and the resulting IETF Trust Legal Provisions (TLP)
(http://trustee.ietf.org/license-info).
IETF
The IESG conducted an experiment during IETF 73 in Minneapolis and
IETF 74 in San Francisco to increase face-to-face meeting time by
adding two one hour meeting slots on Friday afternoon. While it is
recognized that these meeting slots are not preferred by anyone, these
meeting slots have been
The IESG has received a request from the Audio/Video Transport WG (avt)
to consider the following document:
- 'The SEED Cipher Algorithm and Its Use with the Secure Real-time
Transport Protocol (SRTP) '
as a Proposed Standard
The IESG plans to make a decision in the next few
The IESG has received an appeal regarding the previously approved
draft-kucherawy-sender-auth-header-20. The appeal text can be
found here:
http://www.ietf.org/IESG/APPEALS/appeal-otis-2009-02-16.txt
The IESG plans to make a decision in the next few weeks, and solicits
comments on the
The IESG is considering publication of the attached IESG Statement on
IETF activities that are overtaken by events (OBE). Please review and
comment.
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
ietf
This IESG Statement deals with the proposed status for IETF documents
reserving values, numbers, addresses, etc. for example purposes. In this
statement we use the term 'resources' for these values, numbers,
addresses, etc.
As a general practice the IESG recommends that setting aside of
The IESG has received the attached text for a proposed IESG Statement:
IESG Statement on the Usage of Assignable Codepoints in Specification
Examples
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this proposed IESG statement. Please send substantive
ent-Disposition Header", rather
than as updating the same document.
- http://www.rfc-editor.org/errata_search.php?rfc=2183&eid=1457
- http://tools.ietf.org/html/rfc2183
- http://tools.ietf.org/html/rfc1806
Since the approval of this errata would mark an RFC as obsoleted,
the IESG solicit
This statement provides IESG guidance on interim IETF Working Group
meetings, conference calls, and jabber sessions.
Historically the work of the IETF has been conducted over mailing lists.
This practice ensures the widest possible involvement in the working
group process. This practice is not as
The attached describes the manner in which the IESG will be
processing RFC Errata for the IETF Stream. The current tools on the
RFC Editor site support "approved" and "rejected", but they need to
be updated to also permit "hold for document update" as errata sta
The IESG has received a request to consider the following document:
- 'RTP Payload Format for Adaptive TRansform Acoustic Coding (ATRAC)
Family '
as a Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. P
The IESG is considering the following statement to guide the handling of
RFC Errata for IETF Stream RFCs. Your review and comment on this policy
is encouraged.
Russ Housley
on Behalf of the IESG
- - - - - - - - - - - -
Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs
dropped as apparent
spam.
* The Internet draft editor, RFC editor, IESG secretary, IETF chair and
IANA MUST be able to post to IETF mailing lists. The relevant identity
information for these roles will be added to any white-list mechanism used
by an IETF mailing list.
* There MUST be a mechanism to
The IETF Operational Notes (IONs) experiment has concluded. The IESG
has determined that IONs will not be used in the future. It is clear
that the IESG, IAB, and IAOC need the ability to publish documents
that do not expire and are easily updated. Information published as
web pages
or locators. Duplicating the
special case logic in many different URIs is going to be error-
prone as well as costly.
The IESG feels that since the Tel URI is quite extensible,
extending it is the preferred approach over defining new URIs
containing telephone numbers
namespaces):
- Review on the [EMAIL PROTECTED] (now [EMAIL PROTECTED])
- Expert review on behalf of IANA
- IETF Consensus including IETF Last Call and IESG Evaluation
The RFC also provides a list of considerations that might be used in
review by all these parties. The considerations in section 4.3
RFC 4693, Section 4 says:
> This experiment is expected to run for a period of 12 months,
> starting from the date of the first ION published using this
> mechanism. At the end of the period, the IESG should issue a
> call for comments from the community, asking for people to s
The IESG is making a call for volunteers for the IETF Administrative
Oversight Committee (IAOC), as described in BCP 101 (RFC 4071), following
the procedures documented in BCP 113 (RFC 4333). The nominations open
now, and they will close on 18 Nov 2007.
In alternate years. the IESG and the IAB
The IESG re-affirms that its reading of RFC 2026 is that any action
made by an Area Director or the IESG may by made the subject of the
conflict resolution mechanisms set out in Section 6.5 of RFC 2026.
The IESG further wishes to highlight that the primary aim of the
appeals mechanism set out
The IESG has evaluated a request for an RFC 3683 PR-Action for JFC (Jefsey)
Morfin. Please see the following URL for the corresponding Last Call message
and associated information:
http://www1.ietf.org/mail-archive/web/ietf/current/msg40011.html
There was extensive discussion on the IETF list
The IESG has created a web page that tracks some long-term projects which have
been undertaken by its members. This page is called the IESG Projects List.
Projects tracked on this page are generally not resolved with a simple
deliverable, but are exploratory in nature. They might involve the
Your mail to 'iesg' with the subject
Re:
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a members-only list
Either the message will get posted to the list, or you will receive
notification of the m
A new IETF working group has been proposed in the Routing Area. The IESG has not made
any determination as yet. The following description was submitted, and is provided for
informational purposes only. Please send your comments to the IESG mailing list
([EMAIL PROTECTED]) by February 19
40 matches
Mail list logo
