[IESG-AGENDA-DIST] IESG Telechat Agenda (HTML) for June 21, 2007
IESG Agenda
IESG Agenda
Good approximation of what will be included in the Agenda of next Telechat (2007-06-21).
Updated 18:2:28 EDT, June 14, 2007
1. Administrivia
1.1 Roll Call
1.2 Bash the Agenda
1.3 Approval of the Minutes of the past telechat
1.4 List of Remaining Action Items from Last Telechat
2. Protocol Actions
Reviews should focus on these questions: "Is this document a
reasonable basis on which to build the salient part of the Internet
infrastructure? If not, what changes would make it so?"
| |
2.1 WG Submissions
| |
2.1.1 New Item
2.1.2 Returning Item
2.1.3 For Action
| | Area | Date | |
|---|
| SEC | Nov 8 | Two-Document ballot: - 1 of 1 |
| | |
The syslog Protocol (Proposed Standard) - 1 of 1 |
| | |
http://www.ietf.org/internet-drafts/draft-ietf-syslog-protocol-21.txt" rel="nofollow">draft-ietf-syslog-protocol-21.txt |
| | |
Note: The WG chairs believe they may have backed out enough changes that
this no longer requires an second IETF last call. In the hopes that I
will get a chance to review this weekend and issue a ballot I'm placining it on the agenda.
If I fail to issue a ballot by Monday I will remove. |
| | |
Transmission of syslog messages over UDP (Proposed Standard) |
| | |
http://www.ietf.org/internet-drafts/draft-ietf-syslog-transport-udp-09.txt" rel="nofollow">draft-ietf-syslog-transport-udp-09.txt |
| | |
Note: The WG chairs believe they may have backed out enough changes that
this no longer requires an second IETF last call. In the hopes that I
will get a chance to review this weekend and issue a ballot I'm placining it on the agenda.
If I fail to issue a ballot by Monday I will remove. |
| | Token: |
Sam Hartman |
|
2.2 Individual Submissions
| |
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE
|
|
3. Document Actions
| |
3.1 WG Submissions
Reviews should focus on these questions: "Is this document a reasonable
contribution to the area of Internet engineering which it covers? If
not, what changes would make it so?"
| |
3.1.1 New Item
3.1.2 Returning Item
NONE
|
3.2 Individual Submissions Via AD
Reviews should focus on these questions: "Is this document a reasonable
contribution to the area of Internet engineering which it covers? If
not, what changes would make it so?"
| |
3.2.1 New Item
3.2.2 Returning Item
NONE
|
3.3 Independent Submissions Via RFC Editor
The IESG will use RFC 3932 responses: 1) The IESG has not
found any conflict between this document and IETF work; 2) The
IESG thinks that this work is related to IETF work done in WG
<X>, but this does not prevent publishing; 3) The IESG thinks
that publication is harmful to work in WG <X> and recommends
not publishing at this time; 4) The IESG thinks that this
document violates the IETF procedures for <X> and should
therefore not be published without IETF review and IESG
approval; 5) The IESG thinks that this document extends an
IETF protocol in a way that requires IETF review and should
therefore not be published without IETF review and IESG approval.
Other matters may be recorded in comments to be passed on
to the RFC Editor as community review of the document.
| |
3.3.1 New Item
NONE
3.3.2 Returning Item
NONE
|
|
4. Working Group Actions
| |
4.1 WG Creation
| |
4.1.1 Proposed for IETF Review
NONE
|
| |
4.1.2 Proposed for Approval
NONE
|
|
| |
4.2 WG Rechartering
| |
4.2.1 Under evaluation for IETF Review
NONE
|
| |
4.2.2 Proposed for Approval
NONE
|
|
5. IAB News We Can Use
6. Management Issues
7. Working Group News
_______________________________________________
IESG-AGENDA-DIST mailing list
IESG-AGENDA-DIST@ietf.org
https://www1.ietf.org/mailman/listinfo/iesg-agenda-dist
