[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Draft Minutes of April 30, 2003 Telechat





	*DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * 
		INTERNET ENGINEERING STEERING GROUP (IESG) 
				April 30, 2003

Reported by: Jacqueline Hargest, IETF Assistant Director

ATTENDEES 
--------- 
Alvestrand, Harald / Cisco 
Austein, Rob / IAB Liaison 
Bellovin, Steve / AT&T Labs 
Bush, Randy / IIJ 
Daigle, Leslie / Verisign (IAB) 
Falk, Aaron / ISI
Fenner, Bill / AT&T 
Freed, Ned / Innosoft 
Fuller, Barbara / IETF 
Hardie, Ted / Qualcomm, Inc. 
Hargest, Jacqueline / IETF 
Housley, Russ / Vigil Security, LLC 
Mankin, Allison / Bell Labs, Lucent 
Narten, Thomas / IBM 
Nordmark, Erik / Sun 
Peterson, Jon / NeuStar, Inc. 
Reynolds, Joyce K. / ISI (RFC Editor) 
Wijnen, Bert / Lucent 
Zinin, Alex / Alcatel

REGRETS 
------- 
Cotton, Michelle / ICANN 

Minutes 
------- 
1. The minutes of the April 17, 2003 teleconference were approved. 
Secretariat to place in public archives and update minutes web page.

2. The following action items were reported as DONE:

   o Secretariat to modify auto-response for Internet-Drafts 
     submissions so that when someone submits an I-D, a note is 
     automatically generated which recommends that they consider 
     the issues listed in ID-Nits before submitting the I-D to the 
     IESG.  Auto-response to include the URL pointing to the 
     I-D Nits page. IESG will review the auto-response text.
   o Secretariat to email Working Group Chairs a reminder after each 
     conference with pointer to I-D Nits.  Secretariat to draft 
     reminder text and pass by IESG first.

3. Protocol Actions Deferred:

   o Link Management Protocol (LMP) (Proposed Standard)
        <draft-ietf-ccamp-lmp-08.txt

4. Document Actions Tentatively Approved: 

   o IP over Optical Networks: A Framework (Informational)
        <draft-ietf-ipo-framework-04.txt>
     Note: Tentatively approved, subject to addressing Allison's 
     concerns.  Alex will notify Secretariat once ok to announce.
   o Content Internetworking (CDI) Scenarios (Informational)
        <draft-ietf-cdi-scenarios-01.txt>
     Note: Tentatively approved pending references correction.  Ted 
     will notify Secretariat when ready to announce.
   o A Description of the Camellia Encryption Algorithm 
     (Informational)
        <draft-nakajima-camellia-02.txt>
     Note: Tentatively approved pending new revision to address 
     Thomas's boilerplate issue.
   o A URN Namespace for SWIFT's Financial Messaging (Informational)
        <draft-gustin-goyens-urn-id-02.txt>
     Note: Tentatively approved pending note from Ted.
   o A URN Namespace for MPEG (Informational)
        <draft-smith-urn-mpeg-01.txt> 
     Note: Tentatively approved, subject to review by AVT Chair.
   o A URN Namespace for FIPA (Informational)
        <draft-bellifemine-urn-fipa-00.txt>
     Note: Tentatively approved pending update to security 
     considerations and expansion of acronym in title.

5. Document Action Deferred:

   o SDPng Transition (Informational)
        <draft-ietf-mmusic-sdpng-trans-03.txt> 

6. Working Group Actions Approved:

   o Multiparty Multimedia Session Control (mmusic)
     Note: Secretariat to send change in charter (WG Re-charter) to IAB, 
     IESG and WG Chairs.  After one week, if ok, Jon can tell the 
     Secretariat to send this charter to ietf-announce and new-work.
   o LDAP Duplication/Replication/Update Protocols
     Note: Secretariat to send WG Action/Re-charter announcement to IAB, 
     IESG, WG Chairs.  If nothing happens, in one week Ted will ask 
     Secretariat to announce.
   o Global Routing Operations (grow)
     Note: IESG gave final approval.  Secretariat to send WG Action 
     announcement to ietf-announce, install charter.

7. Working Group Action Tentatively Approved: 

   o Network Configuration (netconf)
     Note: Once WG Chairs are approved, Bert will ask Secretariat to 
     send WG Action to ietf-announce, cc: WG Chairs.

8. Documents Remaining Under Discussion:

   o LDAPv3: A Collection of User Schema (Proposed Standard) 
        <draft-zeilenga-ldap-user-schema-06.txt> 
   o Message Disposition Notification (Draft Standard)
        <draft-vaudreuil-mdnbis-03.txt>
   o The IETF XML Registry (BCP)
        <draft-mealling-iana-xmlns-registry-04.txt>
   o Generalized Multi-Protocol Label Switching Architecture 
     (Proposed Standard)
        <draft-ietf-ccamp-gmpls-architecture-05.txt>
   o Session Initiation Protocol Basic Call Flow Examples (BCP)
        <draft-ietf-sipping-basic-call-flows-02.txt>
   o UTF-8, a transformation format of ISO 10646 (Standard)
        <draft-yergeau-rfc2279bis-04.txt>
   o Internet X.509 Public Key Infrastructure Certificate Management 
     Protocols (Proposed Standard)
        <draft-ietf-pkix-rfc2510bis-08.txt>
   o Internet X.509 Public Key Infrastructure Certificate Request 
     Message Format (CRMF)(Proposed Standard)
        <draft-ietf-pkix-rfc2511bis-06.txt>
   o Exclusive XML Canonicalization, Version 1.0 (Informational)
        <draft-ietf-xmldsig-xc14n-00.txt>
   o Policy Requirements for Time-Stamping Authorities (Informational)
        <draft-ietf-pkix-pr-tsa-04.txt>
   o Extreme Networks' Ethernet Automatic Protection Switching 
     (EAPS), Version 1 (Informational)
        <draft-shah-extreme-eaps-02.txt>
   o A Framework for Purpose Built Keys (PBK) (Informational)
        <draft-bradner-pbk-frame-04.txt>

9. DNP (Do Not Publish):

   o OSPF-xTE: An experimental extension to OSPF for Traffic 
     Engineering (Experimental)
        <draft-srisuresh-ospf-te-05.txt>
     Note: Alex to send DNP message to Secretariat to send on behalf 
     of IESG.

10.  The IESG agreed that, since the IPR WG is currently discussing 
     boilerplate issues regarding informational and experimental 
     documents, until the working group reaches a conclusion it is 
     inappropriate for the IESG to make a permanent change to policy.  
     Where IPR might be relevant, standard boilerplate should be used.  
     In addition, if there are IPR, then IPR claims should be filed.

11. New Action Items:

     o Alex to send proposal and justification for interim document 
	 review.
     o Secretariat to send drafted auto-response text for I-D 
	 submissions to IESG for review.
     o Secretariat to send drafted Working Group Chairs reminder text 
	 w/ pointer to I-D Nits to IESG for review.
     o Allison will send RFC Editor Note to address Patrik's issues 
	 for Ted for draft-ietf-sipping-basic-call-flows
     o Allison to ask Steve Casner, AVT Chair, to review 
 	 draft-smith-urn-mpeg
     o Ted to make strawman for creating alternate decision mechanism 
	 in working groups
     o Alex will notify Secretariat once ok to announce 
       draft-ietf-ipo-framework-04.txt
     o Ted will notify Secretariat when ready to announce 
       draft-ietf-cdi-scenarios-01.txt 
     o Ted will send note as well as notify Secretariat when 
       draft-gustin-goyens-urn-id-02.txt is officially approved and 
	 ready to announce.
     o Secretariat to send change in mmusic charter (WG Re-charter) to 
	 IAB, IESG and WG Chairs.  After one week, if ok, Jon will tell 
	 the Secretariat to send this charter to ietf-announce and 
	 new-work.
     o Secretariat to send ldup WG Action/Re-charter announcement to 
	 IAB, IESG, WG Chairs.  If nothing happens, in one week Ted will 
	 ask Secretariat to announce.
     o Secretariat to send grow WG Action announcement to 
	 ietf-announce, install charter.
     o After netconf WG Chairs are approved, Bert will ask Secretariat 
	 to send WG Action to ietf-announce, cc: WG Chairs.
     o Alex to send DNP message for draft-srisuresh-ospf-te-05.txt to 
       Secretariat to send on behalf of IESG.
 
12. Outstanding Action Items:

IP   o Allison to review draft-agrawal-sip-h323-interworking-reqs 
       and send decision to IESG. 
IP   o Erik to document process of how the IESG goes about asking 
       architectural questions of the IAB 
IP   o Thomas to write (or cause to be written) a draft on "how to 
       get to Draft". 
IP   o Thomas to contact Cablelabs to discuss formal relationship 
       with IAB 
IP   o Allison and Thomas will email Secretariat note to send to RFC 
       Editor about 3GPP RFC Editor documents.
IP   o Ned to write an IESG note for draft-tegen-smqp (Informational) 
IP   o Steve to write RFC re: TCP MD5 option
IP   o Randy and Ned to finish ID on Clarifying when Standards Track 
       Documents may Refer Normatively to Documents at a Lower Level