Please review documents on (PRELIMINARY) IESG Agenda for March 31 , 2005

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

Please review and let me have any feedback no later than Wed 11pm
(US Eastern).

Thanks,
Bert
-----------
          INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the March 31, 2005 IESG Teleconference

This agenda was generated at 17:46:19 EDT, March 24, 2005
                                                                                
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-sipping-qsig2sip-04.txt
    Interworking between SIP and QSIG (BCP) - 1 of 6 
    Token: Allison Mankin
  o draft-ietf-sipping-kpml-07.txt
    A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus 
    (KPML) (Proposed Standard) - 2 of 6 
    Token: Allison Mankin
  o draft-ietf-sipping-dialog-package-05.txt
    An INVITE Inititiated Dialog Event Package for the Session Initiation 
    Protocol (SIP) (Proposed Standard) - 3 of 6 
    Token: Allison Mankin
  o draft-ietf-kitten-2478bis-05.txt
    The Simple and Protected GSS-API Negotiation Mechanism (Proposed Standard) 
    - 4 of 6 
    Note: proto shepherd: jaltman@columbia.edu 
    Token: Sam Hartman
  o draft-ietf-ipv6-host-load-sharing-03.txt
    IPv6 Host to Router Load Sharing (Proposed Standard) - 5 of 6 
    Token: Margaret Wasserman
  o draft-ietf-dnsext-insensitive-05.txt
    Domain Name System (DNS) Case Insensitivity Clarification (Proposed 
    Standard) - 6 of 6 
    Note: 2005-01-25: AD review raises some questions, then to IETF LC. 
    Token: Margaret Wasserman

2.1.2 Returning Item
  o Five-document ballot:  - 1 of 3
     - draft-ietf-secsh-architecture-22.txt
       SSH Protocol Architecture (Proposed Standard) 
       Note: IPR Issues have greatly delayed this block of documents.  At 
       IETF 62, the IPR WG gave advice that has been included in these 
       documents.  By approving these documents, the IESG will be 
       approving the approach recommended by the IPR WG. 
     - draft-ietf-secsh-connect-25.txt
       SSH Connection Protocol (Proposed Standard) 
     - draft-ietf-secsh-transport-24.txt
       SSH Transport Layer Protocol (Proposed Standard) 
     - draft-ietf-secsh-userauth-27.txt
       SSH Authentication Protocol (Proposed Standard) 
     - draft-ietf-secsh-assignednumbers-12.txt
       SSH Protocol Assigned Numbers (Proposed Standard) 
    Token: Russ Housley
  o draft-ietf-avt-rtp-retransmission-11.txt
    RTP Retransmission Payload Format (Proposed Standard) - 2 of 3 
    Token: Allison Mankin
  o draft-ietf-ipsec-esp-v3-10.txt
    IP Encapsulating Security Payload (ESP) (Proposed Standard) - 3 of 3 
    Note: Placed on 2005-03-31 agenda to confirm resolution of discuss 
    positions. 
    Token: Russ Housley


2.2 Individual Submissions
2.2.1 New Item
  o draft-malamud-keyword-discovery-03.txt
    Attaching Meaning to Solicitation Class Keywords (Proposed Standard) - 1 of 
    2 
    Token: Scott Hollenbeck
  o draft-crocker-abnf-rfc2234bis-00.txt
    Augmented BNF for Syntax Specifications: ABNF (Draft Standard) - 2 of 2 
    Note: This document obsoletes RFC 2234.Aa It was produced to address 
    comments received during the IESG evaluation of moving 2234 to Draft 
    Standard status. 
    Token: Scott Hollenbeck

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
NONE
3.1.2 Returning Item
  o draft-ietf-dnsop-ipv6-dns-configuration-05.txt
    IPv6 Host Configuration of DNS Server Information Approaches 
    (Informational) - 1 of 1 
    Note: Back to the IESG to check new version 
    Token: David Kessens


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-malamud-subject-line-03.txt
    Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered 
    Ineffective At Best (Informational) - 1 of 2 
    Token: Scott Hollenbeck
  o draft-shafranovich-mime-csv-03.txt
    Common Format and MIME Type for CSV Files (Informational) - 2 of 2 
    Token: Scott Hollenbeck

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-melsen-mac-forced-fwd-03.txt
    MAC-Forced Forwarding: A Method for Traffic Separation on an Ethernet 
    Access Network (Informational) - 1 of 1 
    Note: Back on agenda to resolve IPv6 issues noted by Margaret. 
    Token: Mark Townsley