Subject: Fwd: PRELIMINARY Agenda and Package for June 24, 2004 Telechat

From: Alex Zinin <[email-masked]>
Date: Thu, 17 Jun 2004 17:05:15 -0700

Comments by next 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: Thursday, June 17, 2004, 3:29:57 PM
Subject: PRELIMINARY Agenda and Package for June 24, 2004 Telechat

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

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

This agenda was generated at 17:22:29 EDT, June 17, 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 draft-ietf-xmpp-e2e-08.txt
    End-to-End Object Encryption in the Extensible Messaging and Presence 
    Protocol (XMPP) (Proposed Standard) - 1 of 7 
    Token: Scott Hollenbeck
  o draft-ietf-ospf-ospfv3-auth-04.txt
    Authentication/Confidentiality for OSPFv3 (Proposed Standard) - 2 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: Bill Fenner
  o draft-ietf-aaa-diameter-cc-05.txt
    Diameter Credit-control Application (Proposed Standard) - 3 of 7 
    Note: GEN-ART review has some (minor) comments (resulting from review 
    during IETF Last Call) that will be addressed by authors. They will do so 
    when IESG comments (if any) are available so that one revision can address 
    all comments at same time. 
    Token: Bert Wijnen
  o draft-ietf-ipsec-ikev2-14.txt
    Internet Key Exchange (IKEv2) Protocol (Proposed Standard) - 4 of 7 
    Token: Russ Housley
  o Two-document ballot:  - 5 of 7
     - draft-ietf-sip-parameter-registry-02.txt
       The Internet Assigned Number Authority (IANA) Header Field Parameter 
       Registry for the Session Initiation Protocol (SIP) (BCP) 
       Note: IANA reviewed (IESG list mail 20040602).Ãá 
     - draft-ietf-sip-uri-parameter-reg-02.txt
       The Internet Assigned Number Authority (IANA) Universal Resource 
       Identifier (URI) Parameter Registry for the Session Initiation Protocol 
       (SIP) (BCP) 
    Token: Allison Mankin
  o draft-ietf-mboned-embeddedrp-05.txt
    Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast Address 
    (Proposed Standard) - 6 of 7 
    Token: David Kessens
  o rfc2234.txt
    Augmented BNF for Syntax Specifications: ABNF (Draft Standard) - 7 of 7 
    Token: Scott Hollenbeck

2.1.2 Returning Item
  o draft-ietf-mpls-in-ip-or-gre-07.txt
    Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE) (Proposed 
    Standard) - 1 of 2 
    Note: to clear Steve's DISCUSS 
    Token: Alex Zinin
  o draft-ietf-ospf-scalability-08.txt
    Prioritized Treatment of Specific OSPF Packets and Congestion Avoidance 
    (BCP) - 2 of 2 
    Note: Additional response to each evaluation comment in comment log 
    Token: Bill Fenner

2.2 Individual Submissions
2.2.1 New Item
  o draft-blunk-rpslng-05.txt
    Routing Policy Specification Language next generation (RPSLng) (Proposed 
    Standard) - 1 of 2 
    Token: Bert Wijnen
  o draft-phillips-langtags-03.txt
    Tags for Identifying Languages (BCP) - 2 of 2 
    Token: Ted Hardie

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-seamoby-ctp-10.txt
    Context Transfer Protocol (Experimental) - 1 of 6 
    Note: "Experimental" experimental 
    Token: Allison Mankin
  o draft-ietf-pana-threats-eval-06.txt
    Protocol for Carrying Authentication and Network Access Threat Analysis and 
    Security Requirements (Informational) - 2 of 6 
    Token: Thomas Narten
  o draft-ietf-pana-requirements-08.txt
    Protocol for Carrying Authentication for Network Access (PANA)Requirements 
    (Informational) - 3 of 6 
    Token: Thomas Narten
  o draft-ietf-seamoby-iana-02.txt
    Instructions for Seamoby Experimental Protocol IANA Allocations 
    (Experimental) - 4 of 6 
    Note: Supports CTP (new on this agenda), CARD (returning). 
    Token: Allison Mankin
  o draft-ietf-mboned-mroutesec-01.txt
    PIM-SM Multicast Routing Security Issues and Enhancements (Informational) - 
    5 of 6 
    Token: David Kessens
  o draft-ietf-v6ops-unmaneval-03.txt
    Evaluation of Transition Mechanisms for Unmanaged Networks (Informational) 
    - 6 of 6 
    Token: David Kessens

3.1.2 Returning Item
  o draft-pillay-esnault-ospf-flooding-07.txt
    OSPF Refresh and Flooding Reduction in Stable Topologies (Informational) - 
    1 of 1 
    Note: Already reviewed in 6/2003; please don't re-review unless 
    showstoppers - want to clear ops-dir comment (see document log, there's no 
    ballot).&nbsp; IESG RED TEAM 
    Token: Bill Fenner

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
NONE
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
NONE
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

3.3.3 For Action
  o draft-baker-slem-architecture-02.txt
    Cisco Support for Lawful Intercept In IP Networks (Informational) - 1 of 1 
    Note: Given our new policy, do we still want the IESG note per Ted's 
    comment?&nbsp; Or just the new standard disclaimer? 
    Token: Steve Bellovin

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. Agenda Working Group News

6. IAB News We can use

7. Management Issue

------------------------------------------------------------------------------