Good approximation of what will be
included in the Agenda of next Telechat (2005-08-18).
Updated
10:21:57 EDT, August 5, 2005
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 |
||||
---|---|---|---|---|---|---|
INT |
Encapsulation Methods for Transport of Ethernet Over MPLS Networks (Proposed Standard) - 1 of 2 |
|||||
Token: |
||||||
Reviewer: |
Joel Halpern |
|||||
|
|
|||||
INT |
PWE3 Control Word for use over an MPLS PSN (Proposed Standard) - 2 of 2 |
|||||
Token: |
||||||
Reviewer: |
John Loughney |
|||||
|
|
|||||
2.1.2 Returning Item |
||||||
2.2 Individual Submissions |
||||||
|
2.2.1 New Item |
|||||
|
3.1 WG SubmissionsReviews should focus on these questions: "Is this document a reasonable |
||||||||||
|
3.1.1 New Item |
||||||||||
|
Area |
Date |
|||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
INT |
Low Latency Handoffs in Mobile IPv4 (Experimental) - 1 of 3 |
||||||||||
Token: |
|||||||||||
Reviewer: |
Lakshminath Dondeti |
||||||||||
|
|
||||||||||
INT |
Extension to Sockets API for Mobile IPv6 (Informational) - 2 of 3 |
||||||||||
Token: |
|||||||||||
Reviewer: |
Mark Allman |
||||||||||
|
|
||||||||||
INT |
Mobile IPv6 and Firewalls: Problem statement (Informational) - 3 of 3 |
||||||||||
Token: |
|||||||||||
Reviewer: |
Spencer Dawkins |
||||||||||
|
|
||||||||||
3.1.2 Returning 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 |
Additional cryptographic algorithms for use with GOST 28147-89, GOST R 34.10-94, GOST R 34.10-2001, and GOST R 34.11-94 algorithms. (Informational) - 1 of 1 |
||||||||||
Token: |
|||||||||||
Reviewer: |
Avri Doria |
||||||||||
|
|
||||||||||
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 |
||||||||||