Good approximation of what will be
included in the Agenda of next Telechat (2006-02-02).
Updated
22:2:30 EDT, January 26, 2006
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 |
|||||||||
|
Area |
Date |
||||||||
---|---|---|---|---|---|---|---|---|---|---|
APP |
LDAP: Authentication Methods and Security Mechanisms (Proposed Standard) - 1 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
Spencer Dawkins (already reviewed for LC) |
|||||||||
|
|
|||||||||
RTG |
Definition of an RRO node-id subobject (Proposed Standard) - 2 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
John Loughney |
|||||||||
|
|
|||||||||
RTG |
Anycast-RP using PIM (Proposed Standard) - 3 of 12 |
|||||||||
Note: A -05 is coming to fix the Security Considerations to point just to pim-sm-v2-new and to fix some minor reference issues. |
||||||||||
Token: |
||||||||||
Reviewer: |
Joel Halpern (reviewed -04 for LC) |
|||||||||
|
|
|||||||||
INT |
Virtual Private LAN Service (Proposed Standard) - 4 of 12 |
|||||||||
Note: This document and draft-ietf-l2vpn-vpls-ldp are different solutions to similar problems. L2VPN agreed to advance both and essentially "let the market decide." |
||||||||||
Token: |
||||||||||
Reviewer: |
Elwyn Davies (already reviewed for 19 Jan telechat) |
|||||||||
|
|
|||||||||
INT |
Virtual Private LAN Services over MPLS (Proposed Standard) - 5 of 12 |
|||||||||
Note: This document and draft-ietf-l2vpn-vpls-bgp are different solutions to similar problems. L2VPN agreed to advance both and essentially "let the market decide." |
||||||||||
Token: |
||||||||||
Reviewer: |
Elwyn Davies (already reviewed for 19 Jan telechat) |
|||||||||
|
|
|||||||||
APP |
Lemonade Profile (Proposed Standard) - 6 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
Spencer Dawkins |
|||||||||
|
|
|||||||||
INT |
The Role of Wildcards in the Domain Name System (Proposed Standard) - 7 of 12 |
|||||||||
Note: The PROTO shepherd for this document is Olaf Kolkman <olaf@nlnetlabs.nl>. |
||||||||||
Token: |
||||||||||
Reviewer: |
Harald Alvestrand (reviewed -09 for LC) |
|||||||||
|
|
|||||||||
TSV |
A Resource Reservation Protocol Extension for the Reduction of Bandwidth of a Reservation Flow (Proposed Standard) - 8 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
Joel Halpern (reviewed -01 for LC) |
|||||||||
|
|
|||||||||
SEC |
Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94 and GOST R 34.10-2001 algorithms with the Cryptographic Message Syntax (CMS) (Proposed Standard) - 9 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
David Black (reviewed -06 for LC) |
|||||||||
|
|
|||||||||
APP |
Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map (Proposed Standard) - 10 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
Scott Brim (already reviewed for LC) |
|||||||||
|
|
|||||||||
SEC |
Kerberos Cryptosystem Negotiation Extension (Proposed Standard) - 11 of 12 |
|||||||||
Token: |
||||||||||
Reviewer: |
Michael Patton |
|||||||||
|
|
|||||||||
RAI |
RTP Payload Format for Video Codec 1 (VC-1) (Proposed Standard) - 12 of 12 |
|||||||||
Note: PROTO shepherd Colin Perkins csp@csperkins.org |
||||||||||
Token: |
||||||||||
Reviewer: |
Scott Brim (Note: LC ends on 1 February) |
|||||||||
|
|
|||||||||
2.1.2 Returning Item |
||||||||||
2.2 Individual Submissions |
||||||||||
|
2.2.1 New Item |
|||||||||
|
Area |
Date |
||||||||
SEC |
The AES-CMAC-96 Algorithm and its use with IPsec (Proposed Standard) - 1 of 3 |
|||||||||
Token: |
||||||||||
Reviewer: |
Joel Halpern (already reviewed for LC) |
|||||||||
|
|
|||||||||
APP |
Collected extensions to IMAP4 ABNF (Proposed Standard) - 2 of 3 |
|||||||||
Token: |
||||||||||
Reviewer: |
Elwyn Davies (reviewed -05 for LC) |
|||||||||
|
|
|||||||||
APP |
COSINE LDAP/X.500 Schema (Proposed Standard) - 3 of 3 |
|||||||||
Token: |
||||||||||
Reviewer: |
Harald Alvestrand (already reviewed for LC) |
|||||||||
|
|
|||||||||
2.2.2 Returning Item |
||||||||||
|
3.1 WG SubmissionsReviews should focus on these questions: "Is this document a reasonable |
|||||
|
3.1.1 New Item |
|||||
3.2 Individual Submissions Via ADReviews should focus on these questions: "Is this document a reasonable |
||||||
|
3.2.1 New Item |
|||||
|
Area |
Date |
||||
---|---|---|---|---|---|---|
SEC |
US Secure Hash Algorithms (SHA) (Informational) - 1 of 1 |
|||||
Token: |
||||||
Reviewer: |
John Loughney |
|||||
|
|
|||||
3.2.2 Returning Item |
||||||
3.3 Individual Submissions Via RFC EditorThe IESG will use RFC 3932 responses: 1) The IESG has not |
||||||
|
3.3.1 New Item |
|||||