[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(no subject)
- To: iesg@ietf.org
- Subject: (no subject)
- From: Jacqueline Hargest <jhargest@ietf.org>
- Date: Mon, 20 Jan 2003 12:27:34 -0500
- Sujbect: Agenda and Package for January 23, 2003 Telechat
Apologies for the delay. Please note that if the agenda viewable on
the web page doesn't presently match this package, it will be in sync when
the updates are made tonight. Thanks for your patience.
---------------------------------------
* DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT *
INTERNET ENGINEERING STEERING GROUP (IESG)
Agenda for the January 23, 2003 IESG Teleconference
1. Administrivia
o Roll Call
o Bash the Agenda
o Approval of the Minutes
- January 9, 2003
o Review of Action Items
OUTSTANDING TASKS
OUTSTANDING TASKS
Last updated: January 20, 2002
o <draft-dfncis-netnews-admin-sys-04.txt> in Expert Review; Ned to
evaluate.
IP o Allison to review draft-agrawal-sip-h323-interworking-reqs
and send decision to IESG. If OK, Steve/Secretariat to announce.
IP o Ned to write MIME and MEDIA TYPES Roadmap document
IP o Jeff to compare and contrast identity vs. identifier
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 Patrik to take action on elevating RFC2279 to Standard.
IP o Thomas to contact Cablelabs to discuss formal relationship
with IAB
o Patrik to re-evaluate state of draft-irtf-idrm-handle-system (Informational)
o Patrik to re-evaluate state of draft-jaffer-metric-interchange-format (None)
o Erik to re-evaluate state of draft-jl-pcdp (Informational)
IP o Allison to re-evaluate state of draft-malis-sonet-ces-mpls (Request)
o Patrik to re-evaluate state of draft-new-apex-server (Informational)
IP o Ned to re-evaluate state of draft-tegen-smqp (Informational)
IP o Ned to re-evaluate state of draft-tiwari-appl-wxxx-forms (Informational)
DONE o Allison and Thomas to draft note for draft-stoica-diffserv-dps
DONE o Scott to summarize discussion on the Osama document.
o Thomas to get IESG's sign off for draft-stoica-diffserv-dps.
Secretariat to announce.
o Secretariat to publish all liaison statements immediately.
o Secretariat to have aliases for statements to ietf.org that goes
to ticket system.
o Secretariat to include all IETF Secretariat action items on the
list.
o Harald to compose note for draft-ietf-isis-traffic-04.txt.
o Scott and Allison to confer on draft-foster-mgcp-basic-packages
and return next week with discussion points.
o Secretariat to place 'lemonade' on new-work.
2. Protocol Actions
o The AES-XCBC-MAC-96 Algorithm and Its Use With IPsec (Proposed
Standard)
<draft-ietf-ipsec-ciph-aes-xcbc-mac-02.txt>
Token: Schiller, Jeff
Note: Responsible: Jeff
3. Under discussion
o The application/ogg Media Type (Proposed Standard)
<draft-walleij-ogg-mediatype-08.txt>
Token: Mankin, Allison
Note: This is the documentation IESG felt needed to go with the
ogg mime type registration...with this in hand, the ogg mime type
should be able to go forward - but this needs to go on the IESG
agenda next time (that is 2002-Jan-23)
4. Working Group Submissions
o IP over Optical Networks: A Framework (Informational)
<draft-ietf-ipo-framework-03.txt>
Token: Bradner, Scott
o Internet X.509 Public Key Infrastructure Certificate Policy and
Certification Practices Framework (Informational)
<draft-ietf-pkix-ipki-new-rfc2527-01.txt>
Token: Schiller, Jeff
Note: Responsible: Responsible AD
o Policy Requirements for Time-Stamping Authorities (Informational)
<draft-ietf-pkix-pr-tsa-02.txt>
Token: Schiller, Jeff
o CR-LDP Extensions for ASON (Informational)
<draft-aboulmagd-ccamp-crldp-ason-ext-02.txt>
Token: Bradner, Scott
5. Individual via RFC Editor
o LDP and RSVP Extensions for Optical UNI Signaling (Informational)
<draft-bala-uni-ldp-rsvp-extension>
Token: Bradner, Scott
o IP Version 6 over MAPOS (Informational)
<draft-ogura-ipv6-mapos-01.txt>
Token: Narten, Thomas
o Generic Requirements for Provider Provisioned VPN (Informational)
<draft-ietf-ppvpn-generic-reqts-02.txt>
Token: Bradner, Scott
o The Ogg encapsulation format version 0 (Informational)
<draft-pfeiffer-ogg-fileformat-01.tx>
Token: Allison Mankin
6. Proposed Working Groups
o License to Enhance Messaging Oriented Network Access for Diverse
Endpoints
Token: Ned
Note: New title: Enhancements to Internet email to support
diverse service environments (lemonade) and updated charter
7. Working Group News We Can Use
8. IAB News we can use
9. Management Issues
o Basic MGCP Packages (Informational)
o IETF Meetings - avoiding overlaps
o Zorn Formal Appeal against IESG decision
DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT * DRAFT *
INTERNET ENGINEERING STEERING GROUP (IESG)
January 9, 2003
Reported by: Jacqueline Hargest, IETF Assistant Director
ATTENDEES
---------
Alvestrand, Harald / Cisco
Austein, Rob / IAB Liaison
Bradner, Scott / Harvard
Bush, Randy / IIJ
Cotton, Michelle / ICANN
Faltstrom, Patrik / Cisco
Fenner, Bill / AT&T
Hargest, Jacqueline / IETF
Mankin, Allison / Bell Labs, Lucent
Narten, Thomas / IBM
Reynolds, Joyce K. / ISI (RFC Editor)
Schiller, Jeff / MIT
Wijnen, Bert / Lucent
Zinin, Alex / Alcatel
REGRETS
-------
Bellovin, Steve / AT&T Labs
Coya, Steve / IETF
Daigle, Leslie / Verisign (IAB)
Freed, Ned / Innosoft
Nordmark, Erik / Sun
Minutes
-------
1. The minutes of the December 27, 2002 Teleconference were approved.
Secretariat to place in public archives.
2. Prior to the January 9, 2003 teleconference, the following
documents were APPROVED:
o 'The Group Domain of Interpretation' (Proposed)
<draft-ietf-msec-gdoi-07.txt>
o 'LDAPv2 to Historical Status' (Informational)
<draft-zeilenga-ldapv2-04.txt>
3. Protocol Actions TENTATIVELY APPROVED:
o 'RTP Payload Format for SMPTE 292M Video' (Proposed Standard)
<draft-ietf-avt-smpte292-video-08.txt>
Note: Scott to send note. Secretariat to announce.
4. Document Actions APPROVED:
The IESG has approved the Internet-Draft 'Requirements for Resource
Priority Mechanisms for the Session Initiation Protocol'
<draft-ietf-ieprep-sip-reqs-03.txt> as an Informational RFC.
Secretariat to send announcement.
5. Document Actions TENTATIVELY APPROVED:
o 'LDP and RSVP Extensions for Optical UNI Signaling' (Informational)
<draft-bala-uni-ldp-rsvp-extensions-03.txt>
Note: IANA to review assignments for this and two other documents.
Once Thomas gives ok, Secretariat to announce.
6. Working Group Action:
o 'License to Enhance Messaging Oriented Network Access for Diverse
Endpoints' (lemonade)
Note: Secretariat to place on new-work.
7. The following documents are still under DISCUSSION:
o 'A Presence Event Package for the Session Initiation Protocol (SIP)'
(Proposed Standard)
<draft-ietf-simple-presence-09.txt>
Note: Ned holds a "Defer".
o 'IS-IS extensions for Traffic Engineering' (Informational)
<draft-ietf-isis-traffic-04.txt>
Note: Harald will compose a note.
o 'Basic MGCP Packages' (Informational)
<draft-foster-mgcp-basic-packages-09.txt>
Note: Scott and Allison to confer and return next week with
discussion points.
8. NEW Action Items:
o Scott to summarize discussion on the Osama document.
o Thomas to get IESG's sign off for draft-stoica-diffserv-dps.
Secretariat to announce.
o Secretariat to publish all liaison statements immediately.
o Secretariat to have aliases for statements to ietf.org that goes
to ticket system.
o Secretariat to include all IETF Secretariat action items on the
list.
o Harald to compose note for draft-ietf-isis-traffic-04.txt.
o Scott and Allison to confer on draft-foster-mgcp-basic-packages
and return next week with discussion points.
o Secretariat to place 'lemonade' on new-work.
9. Outstanding Action Items:
o <draft-dfncis-netnews-admin-sys-04.txt> in Expert Review; Ned to
evaluate.
IP o Allison to review draft-agrawal-sip-h323-interworking-reqs
and send decision to IESG. If OK, Steve/Secretariat to announce.
IP o Ned to write MIME and MEDIA TYPES Roadmap document
IP o Jeff to compare and contrast identity vs. identifier
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 Patrik to take action on elevating RFC2279 to Standard.
IP o Thomas to contact Cablelabs to discuss formal relationship
with IAB
o Patrik to re-evaluate state of draft-irtf-idrm-handle-system (Informational)
o Patrik to re-evaluate state of draft-jaffer-metric-interchange-format (None)
o Erik to re-evaluate state of draft-jl-pcdp (Informational)
IP o Allison to re-evaluate state of draft-malis-sonet-ces-mpls (Request)
o Patrik to re-evaluate state of draft-new-apex-server (Informational)
IP o Ned to re-evaluate state of draft-tegen-smqp (Informational)
IP o Ned to re-evaluate state of draft-tiwari-appl-wxxx-forms (Informational)
To: Internet Engineering Steering Group <iesg@ietf.org>
From: IESG Secretary <iesg-secretary@ietf.org>
Reply-To: IESG Secretary <iesg-secretary@ietf.org>
Subject: Evaluation: draft-ietf-ipsec-ciph-aes-xcbc-mac - The
AES-XCBC-MAC-96 Algorithm and Its Use With IPsec to Proposed
Standard
--------
Last Call to expire on: August 6, 2002
Please return the full line with your position.
Yes No-Objection Discuss * Abstain
Harald Alvestrand [ ] [ ] [ ] [ ]
Steve Bellovin [ ] [ ] [ ] [ ]
Scott Bradner [ ] [ ] [ ] [ ]
Randy Bush [ ] [ ] [ ] [ ]
Patrik Faltstrom [ ] [ ] [ ] [ ]
Bill Fenner [ ] [ ] [ ] [ ]
Ned Freed [ ] [ ] [ ] [ ]
Allison Mankin [ ] [ ] [ ] [ ]
Thomas Narten [ ] [ ] [ ] [ ]
Erik Nordmark [ ] [ ] [ ] [ ]
Jeff Schiller [ ] [ ] [ ] [ ]
Bert Wijnen [ ] [ ] [ ] [ ]
Alex Zinin [ ] [ ] [ ] [ ]
2/3 (9) Yes or No-Objection opinions needed to pass.
* Indicate reason if 'Discuss'.
^L
To: IETF-Announce:;
Dcc: *******
Cc: RFC Editor <rfc-editor@isi.edu>,
Internet Architecture Board <iab@iab.org>, ipsec@lists.tislabs.com
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: The AES-XCBC-MAC-96 Algorithm and Its Use
With IPsec to Proposed Standard
-------------
The IESG has approved the Internet-Draft 'The AES-XCBC-MAC-96 Algorithm
and Its Use With IPsec' <draft-ietf-ipsec-ciph-aes-xcbc-mac-02.txt> as
a Proposed Standard. This document is the product of the IP Security
Protocol Working Group. The IESG contact persons are Jeffrey Schiller
and Steve Bellovin.
Technical Summary
(What does this protocol do and why does the community need it?)
Working Group Summary
(Was there any significant dissent? Was the choice obvious?)
Protocol Quality
(Who has reviewed the spec for the IESG? Are there implementations?)
Enhancements to Internet email to support diverse service environments
(lemonade)
Proposed Charter
================
Lemonade is tasked to provide a set of enhancements and profiles of Internet
email submission, transport, and retrieval protocols to facilitate operation in
environments which use Internet-based technologies but which have link
characteristics, device characteristics, or service environments that are
significantly different from those common on the Internet. A primary goal of
this work is to ensure that those profiles and enhancements continue to
interoperate with the existing Internet email protocols in use on the Internet,
so that these environments and more traditional Internet users have access to a
seamless service.
Lemonade's work is at the crossroads of a body of work related to Internet
messaging, in particular work done by the VPIM, FAX, IMAPEXT and other IETF
working groups. Given the potentially broad scope of activities this group
could engage in, the group will focus specifically on the following work items:
0. An informational RFC will be produced on LEMONADE requirements.
1. Enhance the existing IMAP4 message retrieval protocol to satisfy the
requirements for streaming playback of multimedia content.
2. Enhance the exsiting IMAP4 message retrieval protocol to facilitate
its use with devices that have limited capabilities such as mobile
endpoints. The existing standards-track CONNEG framework will be used
if content negotiation capabilities are needed.
3. Create a message notification protocol for the specific purpose of
servers reporting message status information to other servers.
4. Create a specification describing the use of Internet message
services in environments where message delivery may take place using
either Internet protocols or through an MMS server using
WAP to communicate with the receiving user agent.
Any protocols defined by this working group will include appopriate security
mechanisms, including authentication, privacy, and access control.
Mandatory-to-implement security mechanisms will be specified as needed in order
to guarantee secure protocol interoperability.
The transport area will be consulted to deal with any transport-related
issues that arise, especially in regards to items 1-4 above.
The working group is aware of several related activities in other groups:
- 3GPP TSG T WG2 SWG3 Messaging <http://www.3gpp.org/TB/T/T2/T2.htm>
- W3C Mulitmodal interaction Activity <http://www.w3.org/2002/mmi/>
- Open Mobile Alliance <http://www.openmobilealliance.org/>
- 3GPP2 TSG-P <http://3gpp2.org/Public_html/P/index.cfm>
- 3GPP2 TSG-N <http://3gpp2.org/Public_html/N/index.cfm>
The goal is to coordinate efforts with at least these groups as required.
While there is obvious synergy, given the end-of-life of the VPIM and FAX work
groups and the similar membership, the working group does not expect to
coordinate with these other groups.
Milestones (document completion)
==========
Feb 2003 - LEMONADE Requirements
May 2003 - Server to server notification protocol
Jul 2003 - IMAP4 extensions for VM playback
Sep 2003 - IMAP4 extensions for mobile devices
Jan 2004 - Translation to and from other messaging systems
Drafts to be used as input for working group
deliverables (grouped per milestone)
====================================
LEMONADE requirements
- draft-vaudreuil-um-issues-00.txt
- draft-burger-um-reqts-00.txt
- draft-wong-umcli-00.txt
Server to server notification protocol
- draft-shapira-snap-04.txt
IMAP4 extensions for VM playback
- draft-burger-imap-chanuse-00.txt
- draft-nerenberg-imap-channel-01.txt
IMAP4 extensions for mobile devices
- draft-neystadt-imap-status-counters-00.txt
- draft-shveidel-mediasize-00.txt
Translation to and from other messaging systems
- draft-vaudreuil-futuredelivery-00.txt