[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for October 8, 2009 Telechat
Please find below the preliminary agenda of the IESG telechat on 10/8.
Please send your comments, questions and concerns before 10/7 COB.
Thanks and Regards,
Dan
-----Original Message-----
From: iesg-bounces at ietf.org [mailto:iesg-bounces at ietf.org] On Behalf Of
IESG Secretary
2.1 WG Submissions
2.1.1 New Item
o draft-ietf-ipsecme-ikev2-resumption-08.txt
IKEv2 Session Resumption (Proposed Standard) - 1 of 7
Note: Paul Hoffman (paul.hoffman at vpnc.org) is the document shepherd.
Token: Pasi Eronen
o draft-ietf-mipshop-pfmipv6-09.txt
Fast Handovers for Proxy Mobile IPv6 (Proposed Standard) - 2 of 7
Note: Vijay Devarapalli (vijay at wichorus.com) is the document
shepherd.
Token: Jari Arkko
o draft-ietf-pmol-sip-perf-metrics-04.txt
SIP End-to-End Performance Metrics (Proposed Standard) - 3 of 7
Note: Vijay Gurbani is the PROTO-shepherd
Token: Dan Romascanu
o draft-ietf-dime-diameter-cmd-iana-01.txt
Updated IANA Considerations for Diameter Command Code Allocations
(Proposed
Standard) - 4 of 7
Note: Victor Fajardo (vfajardo at research.telcordia.com) is the
document
shepherd.
Token: Ron Bonica
o draft-ietf-yam-rfc1652bis-pre-evaluation-00.txt
Preliminary Evaluation of RFC 1652 for Advancement to Full Standard
(Standard) - 5 of 7
Note: This draft contains the list of changes planned by the YAM WG
to
move
RFC 1652 to Full Standard. There is no intention to publish this
document
as an RFC, so IESG should vote on this document as if RFC 1652 is
advancing
to Full Standard.. S Moonesamy <sm+ietf at elandsys.com> has agreed
to
serve as the document shepherd, but note that there is no
shepherding
write-up for this document.
Token: Alexey Melnikov
o draft-ietf-mpls-tp-oam-requirements-03.txt
Requirements for OAM in MPLS Transport Networks (Proposed Standard)
-
6 of
7
Note: Loa Andersson (loa at pi.nu) is the document shepherd.. Note that
this
document is a requirement document, for reasons that have. to do
with
referencibility by ITU-T we have opted to put it on the standards
track.
The same decision applies to all MPLS-TP requirement. documents.
Token: Adrian Farrel
o draft-ietf-mpls-tp-nm-req-05.txt
MPLS TP Network Management Requirements (Proposed Standard) - 7 of 7
Note: Loa Andersson (loa at pi.nu) is the Document Shepherd.. Note that
this
document is a requirement document. For reasons that. have to do
with
how
the ITU-T can reference RFCs we have opted to put. it on the
Standards
Track.
Token: Adrian Farrel
2.1.2 Returning Item
o draft-ietf-tcpm-tcpsecure-12.txt
Improving TCP's Robustness to Blind In-Window Attacks (Proposed
Standard) -
1 of 2
Note: IESG: Please read the Document Shepherd Writeup, we need to
discuss
the "Updates: 793" issue.
Token: Lars Eggert
o draft-ietf-mboned-lightweight-igmpv3-mldv2-05.txt
Lightweight IGMPv3 and MLDv2 Protocols (BCP) - 2 of 2
Token: Ron Bonica
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
o draft-ietf-simple-interdomain-scaling-analysis-08.txt
Presence Interdomain Scaling Analysis for SIP/SIMPLE (Informational)
-
1 of
10
Note: Ben Campbell is document shepherd
Token: Robert Sparks
o draft-ietf-krb-wg-cross-problem-statement-04.txt
Problem statement on the cross-realm operation of Kerberos
(Informational)
- 2 of 10
Token: Tim Polk
o draft-ietf-speermint-requirements-07.txt
SPEERMINT Requirements for SIP-based Session Peering (Informational)
-
3 of
10
Token: Cullen Jennings
o draft-ietf-speermint-voip-consolidated-usecases-14.txt
VoIP SIP Peering Use Cases (Informational) - 4 of 10
Token: Cullen Jennings
o draft-ietf-roll-home-routing-reqs-08.txt
Home Automation Routing Requirements in Low Power and Lossy Networks
(Informational) - 5 of 10
Note: JP Vasseur (jvasseur at cisco.com) is the document shepherd
Token: Adrian Farrel
o draft-ietf-msec-tesla-for-alc-norm-08.txt
Use of TESLA in the ALC and NORM Protocols (Experimental) - 6 of 10
Token: Tim Polk
o draft-ietf-rtgwg-lf-conv-frmwk-06.txt
A Framework for Loop-free Convergence (Informational) - 7 of 10
Token: Ross Callon
o draft-ietf-rtgwg-ipfrr-framework-12.txt
IP Fast Reroute Framework (Informational) - 8 of 10
Token: Ross Callon
o draft-ietf-ipsecme-ikev2-ipv6-config-02.txt
IPv6 Configuration in IKEv2 (Experimental) - 9 of 10
Note: Paul Hoffman (paul.hoffman at vpnc.org) is the document shepherd.
Token: Tim Polk
o draft-ietf-eai-downgraded-display-02.txt
Displaying Downgraded Messages for Email Address
Internationalization
(Experimental) - 10 of 10
Note: Harald Alvestrand agreed to shepherd the document
Token: Alexey Melnikov
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
o draft-harkins-emu-eap-pwd-08.txt
EAP Authentication Using Only A Password (Informational) - 1 of 2
Token: Russ Housley
o draft-iana-ipv4-examples-02.txt
IPv4 Address Blocks Reserved for Documentation (Informational) - 2
of
2
Token: Russ Housley
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.
The document shepherd must propose one of these responses in
the Data Tracker note and supply complete text in the IESG
Note portion of the write-up. The Area Director ballot positions
indicate consensus with the response proposed by the
document shepherd.
Other matters may be recorded in comments, and the comments will
be passed on to the RFC Editor as community review of the
document.
3.3.1 New Item
o draft-keromytis-keynote-x509-02.txt
X.509 Key and Signature Encoding for the KeyNote Trust Management
System
(Informational) - 1 of 1
Token: Tim Polk
3.3.2 Returning Item
o draft-templin-ranger-07.txt
Routing and Addressing in Next-Generation EnteRprises (RANGER)
(Informational) - 1 of 2
Token: Jari Arkko
o draft-irtf-mobopts-mmcastv6-ps-08.txt
Multicast Mobility in MIPv6: Problem Statement and Brief Survey
(Informational) - 2 of 2
Note: Rajeev Koodli (rajeev.koodli at gmail.com) is the document
shepherd.
Token: Jari Arkko
3.3.3 For Action
o draft-levy-sip-diversion-10.txt
Diversion Indication in SIP (Historic) - 1 of 1
Token: Robert Sparks
4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
NONE
4.1.2 Proposed for Approval
o Multipath TCP (mptcp) - 1 of 1
Token: Magnus Westerlund
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
NONE
4.2.2 Proposed for Approval
o Behavior Engineering for Hindrance Avoidance (behave) - 1 of 2
Token: Magnus Westerlund
o Access Node Control Protocol (ancp) - 2 of 2
Token: Ralph Droms