[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FW: Agenda and Package for March 18, 2004 Telechat
- To: "Mreview (E-mail)" <mreview@ops.ietf.org>
- Subject: FW: Agenda and Package for March 18, 2004 Telechat
- From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
- Date: Sat, 13 Mar 2004 16:16:40 +0100
Pls review from an SNMP, MIB, NM perspective and if you
have any concerns/comments, let me know asap, but no later
than coming Ednesday
Thanks,
Bert
-----Original Message-----
2. Protocol Actions
2.1 WG Submissions
2.1.1 New Item
o draft-ietf-spirits-protocol-07.txt
The SPIRITS (Services in PSTN requesting Internet services) Protocol
(Proposed Standard) - 1 of 5
Note: Responsible: Working Group
Token: Jon Peterson
o draft-ietf-dhc-server-mib-10.txt
Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Server MIB
(Proposed Standard) - 2 of 5
Token: Margaret Wasserman
o draft-ietf-imapext-sort-14.txt
INTERNET MESSAGE ACCESS PROTOCOL - SORT AND THREAD EXTENSION (Proposed
Standard) - 3 of 5
Token: Scott Hollenbeck
o draft-ietf-nemo-basic-support-02.txt
Nemo Basic Support Protocol (Proposed Standard) - 4 of 5
Token: Margaret Wasserman
o draft-ietf-ipv6-deprecate-site-local-02.txt
Deprecating Site Local Addresses (Proposed Standard) - 5 of 5
Token: Margaret Wasserman
2.1.2 Returning Item
NONE
2.2 Individual Submissions
2.2.1 New Item
o draft-weltman-ldapv3-proxy-12.txt
LDAP Proxied Authentication Control (Proposed Standard) - 1 of 1
Token: Ted Hardie
2.2.2 Returning Item
o draft-zeilenga-ldap-authzid-08.txt
LDAP 'Who am I?' Operation (Proposed Standard) - 1 of 2
Note: Proposed RFC Editor Note: RFC Editor note: In section 1, please
replace:. OLD:. Bind controls are not protected by
the security layers. established by the Bind operation
which they are. transferred as part of.. NEW:.
Bind controls are not protected by the security layers.
established by the Bind operation which includes them. In section
3, please add the following sentence to the last paragraph. (which ends
with "a multi-stage Bind operation"):. NEW:. Where a
request is received in violation of this absolute.
prohibition, the server should respond with an operationsError.
result code
Token: Ted Hardie
o draft-mealling-uuid-urn-03.txt
A UUID URN Namespace (Proposed Standard) - 2 of 2
Note: Revised to deal with DISCUSS issues; back on telechat to clear
Token: Ted Hardie
2.2.3 For Action
o draft-nottingham-hdrreg-http-00.txt
Registration of HTTP header fields (Informational) - 1 of 1
Note: This is HTTP header data for the klyne message header registry
Token: Ted Hardie
3. Document Actions
3.1 WG Submissions
3.1.1 New Item
o draft-ietf-pkix-pkixrep-02.txt
Internet X.509 Public Key Infrastructure Repository Locator Service
(Experimental) - 1 of 2
Token: Russ Housley
o draft-ietf-mip4-vpn-problem-statement-02.txt
Problem Statement: Mobile IPv4 Traversal of VPN Gateways (Informational)
- 2 of 2
Token: Thomas Narten
3.1.2 Returning Item
o draft-ietf-speechsc-reqts-05.txt
Requirements for Distributed Control of ASR, SI/SV and TTS Resources
(Informational) - 1 of 2
Token: Jon Peterson
o draft-ietf-dnsext-dns-threats-06.txt
Threat Analysis Of The Domain Name System (Informational) - 2 of 2
Note: 2003-03-06: This document has been before the IESG before; this.
version addresses comments from smb, housley, and wijnen (from ops.
directorate)..
Token: Thomas Narten
3.2 Individual Submissions Via AD
3.2.1 New Item
NONE
3.2.2 Returning Item
o draft-zhao-slp-remote-da-discovery-05.txt
Finding Remote Directory Agents and Service Agents in the Service
Location Protocol via DNS SRV (Experimental) - 1 of 1
Note: 2004-03-06: This document was originally intended for proposed. But
many. IESG comments, and long set of discussions among authors and
review. party. Eventual decision that publishing as experimental was.
reasonable. Many changes (simplifications) relative to original.
document.
Token: Thomas Narten
3.2.3 For Action
o draft-nottingham-hdrreg-http-00.txt
Registration of HTTP header fields (Informational) - 1 of 1
Note: This is HTTP header data for the klyne message header registry
Token: Ted Hardie
3.3 Individual Submissions Via RFC Editor
3.3.1 New Item
o draft-gurbani-sin-02.txt
Interworking SIP and Intelligent Network (IN) Applications
(Informational) - 1 of 1
Note: On several occasions the SIP and SIPPING WGs stated that this was
not an end-run. Issues remained: no SIP-ite could review the
IN stuff; what org will think we're end-running them when it comes
out? Some diligence did not identify one, but TSV has been burned
before. New iesg / rfc-ed model means these issues have much
less weight on IETF.
Token: Allison Mankin
3.3.2 Returning Item
NONE