Subject: Fwd: UPDATED Agenda and Package for June 10, 2004 Telechat

From: Alex Zinin <[email-masked]>
Date: Mon, 7 Jun 2004 16:05:15 -0700

FYI. Comments /if any/ by Wed, please.
-- 
Alex
http://www.psg.com/~zinin

This is a forwarded message
From: IESG Secretary <[email-masked]>
To: [email-masked]
Cc: [email-masked], [email-masked]
Date: Monday, June 7, 2004, 3:29:18 PM
Subject: UPDATED Agenda and Package for June 10, 2004 Telechat

===8<==============Original message text===============

          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the June 10, 2004 IESG Teleconference

This agenda was generated at 17:23:6 EDT, June 7, 2004
                                                                                
1. Administrivia
                                                                                
  1.1 Roll Call
  1.2 Bash the Agenda
  1.3 Approval of the Minutes
  1.4 Review of Action Items
  1.5 Review of Projects
      http://www.unreason.com/jfp/iesg-projects
                                                                                
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
  o Two-document ballot:  - 1 of 7
     - draft-ietf-l3vpn-rfc2547bis-01.txt
       BGP/MPLS IP VPNs (Proposed Standard) 
     - draft-ietf-l3vpn-as2547-05.txt
       Applicability Statement for BGP/MPLS IP VPNs (Informational) 
    Token: Thomas Narten
  o draft-ietf-iptel-rfc2806bis-08.txt
    The tel URI for Telephone Numbers (Proposed Standard) - 2 of 7 
    Token: Jon Peterson
  o draft-ietf-ipsec-ikev2-14.txt
    Internet Key Exchange (IKEv2) Protocol (Proposed Standard) - 3 of 7 
    Token: Russ Housley
  o draft-ietf-tewg-mib-08.txt
    A Traffic Engineering MIB (Proposed Standard) - 4 of 7 
    Note: Participant in PROTO Team pilot:. Workgroup Chair Followup of AD 
    Evaluation Comments. 
    http://www.ietf.org/internet-drafts/draft-ietf-proto-ad-comments-pilot-00.txt 
    Token: Bert Wijnen
  o draft-iesg-rfced-documents-02.txt
    The IESG and RFC Editor documents: Procedures (BCP) - 5 of 7 
    Token: David Kessens
  o draft-ietf-send-ndopt-05.txt
    SEcure Neighbor Discovery (SEND) (Proposed Standard) - 6 of 7 
    Token: Margaret Wasserman
  o draft-ietf-smime-rfc2632bis-07.txt
    S/MIME Version 3.1 Certificate Handling (Proposed Standard) - 7 of 7 
    Token: Russ Housley

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-ietf-nat-natmib-09.txt
    Definitions of Managed Objects for Network Address Translators (NAT) 
    (Proposed Standard) - 1 of 3 
    Note: Had careful MIB doctor review.&nbsp; Wrt function, allowed to 
    configure. only the NAT's address range and not NAT/firewall binds or. 
    firewall policies.&nbsp; This means no conflict with MIDCOM. 
    Token: Allison Mankin
  o draft-ymbk-downref-02.txt
    Clarifying when Standards Track Documents may Refer Normatively to 
    Documents at a Lower Level (BCP) - 2 of 3 
    Token: Harald Alvestrand
  o draft-klensin-process-july14-02.txt
    A model for IETF Process Experiments (BCP) - 3 of 3 
    Token: Harald Alvestrand

2.2.2 Returning Item
NONE
2.2.3 For Action
  o draft-duerst-iri-08.txt
    Internationalized Resource Identifiers (IRIs) (Proposed Standard) - 1 of 1 
    Token: Harald Alvestrand

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-ieprep-framework-09.txt
    Framework for Supporting ETS in IP Telephony (Informational) - 1 of 7 
    Token: Jon Peterson
  o draft-ietf-l3vpn-ppvpn-terminology-02.txt
    PPVPN terminology (Informational) - 2 of 7 
    Note: 2004-06-07: on IESG agenda for review; needed by other ppvpn 
    documents. 
    Token: Thomas Narten
  o draft-ietf-v6ops-application-transition-02.txt
    Application Aspects of IPv6 Transition (Informational) - 3 of 7 
    Note: Participant in PROTO Team pilot:. Working Group Chair Followup of 
    DISCUSS Comments. 
    http://www.ietf.org/internet-drafts/draft-ietf-proto-wgchair-discuss-pilot-01.txt 
    Token: David Kessens
  o draft-ietf-dnsop-ipv6-dns-issues-07.txt
    Operational Considerations and Issues with IPv6 DNS (Informational) - 4 of 
    7 
    Note: Participant in PROTO Team pilot: Workgroup Chair Followup of AD 
    Evaluation Comments 
    http://www.ietf.org/internet-drafts/draft-ietf-proto-ad-comments-pilot-00.txt 
    Token: David Kessens
  o draft-ietf-dnsop-misbehavior-against-aaaa-01.txt
    Common Misbehavior against DNS Queries for IPv6 Addresses (Informational) - 
    5 of 7 
    Note: Participant in PROTO Team pilot: Workgroup Chair Followup of AD 
    Evaluation Comments 
    http://www.ietf.org/internet-drafts/draft-ietf-proto-ad-comments-pilot-00.txt 
    Token: David Kessens
  o draft-ietf-mboned-mroutesec-01.txt
    PIM-SM Multicast Routing Security Issues and Enhancements (Informational) - 
    6 of 7 
    Token: David Kessens
  o draft-ietf-rtgwg-igp-shortcut-01.txt
    Calculating IGP Routes Over Traffic Engineering Tunnels (Informational) - 7 
    of 7 
    Token: Alex Zinin

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-walker-ieee802-req-01.txt
    EAP Method Requirements for Wireless LANs (Informational) - 1 of 1 
    Note: To be reviewed by the IESG BLUE TEAM! 
    Token: Margaret Wasserman

3.2.2 Returning Item
NONE
3.3 Individual Submissions Via RFC Editor
	Reviews should focus on these questions: "Does this document
	represent an end run around the IETF's working groups
	or its procedures? Does this document present an incompatible
	change to IETF technologies as if it were compatible?" Other
	matters may be sent to the RFC Editor in private review.

3.3.1 New Item
  o draft-wlai-tewg-bcmodel-04.txt
    Bandwidth Constraints Models for Diffserv-aware MPLS Traffic Engineering: 
    Performance Evaluation (Informational) - 1 of 1 
    Token: Bert Wijnen

3.3.2 Returning Item
  o draft-dfncis-netnews-admin-sys-06.txt
    Netnews Administration System (NAS) (Experimental) - 1 of 1 
    Note: Re-review in light of new procedures for individual submissions via 
    the RFC Editor.&nbsp; This one has been in the IESG's hands for two years! 
    Token: Scott Hollenbeck

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
  o Protocol for carrying Authentication for Network Access (pana) - 1 of 3
    Token: Thomas Narten
  o Extensible Authentication Protocol (eap) - 2 of 3
    Token: Margaret Wasserman
  o Multiprotocol Label Switching (mpls) - 3 of 3
    Token: Alex Zinin
4.2.2 Proposed for Approval
    NONE

5. Agenda Working Group News

6. IAB News We can use

7. Management Issue

 7.1 PERM - Protected Entertainment Rights Management (Harald Alvestrand)

 7.2 3667/3668 fix (Steve Bellovin)