Please review documents on IESG Agenda for May 12, 2005 Telechat

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

MIB doctors, as always, pls review if you can.
If you have any comments, I need them by Thursday 3pm European
time (9am US Eastern).
Sorry for being late (I was a way for the weekend)

Bert
----------------------                                                                 
2. Protocol Actions
	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
  o draft-ietf-l3vpn-mpls-vpn-mib-07.txt
    MPLS/BGP Layer 3 Virtual Private Network Management Information Base 
    (Proposed Standard) - 1 of 7 
    Note: This doc is being advanced together with 
    draft-ietf-l3vpn-tc-mib-06.txt 
    Token: Mark Townsley
  o draft-ietf-l3vpn-tc-mib-06.txt
    Definition of Textual Conventions for Virtual Private Network (VPN) 
    Management (Proposed Standard) - 2 of 7 
    Note: This doc is being advanced together with 
    draft-ietf-l3vpn-mpls-vpn-mib.. 
    Token: Mark Townsley
  o draft-ietf-avt-rtp-bv-04.txt
    RTP Payload Format for BroadVoice Speech Codecs (Proposed Standard) - 3 of 
    7 
    Note: PROTO shepherd: magnus.westerlund@ericsson.com 
    Token: Allison Mankin
  o draft-ietf-dhc-lifetime-03.txt
    Information Refresh Time Option for DHCPv6 (Proposed Standard) - 4 of 7 
    Token: Margaret Wasserman
  o draft-ietf-dhc-vendor-suboption-00.txt
    Vendor-Specific Information Suboption for the DHCP Relay Agent Option 
    (Proposed Standard) - 5 of 7 
    Token: Margaret Wasserman
  o draft-ietf-dhc-3315id-for-v4-04.txt
    Node-Specific Client Identifiers for DHCPv4 (Proposed Standard) - 6 of 7 
    Token: Margaret Wasserman
  o draft-ietf-ipv6-addr-arch-v4-03.txt
    IP Version 6 Addressing Architecture (Draft Standard) - 7 of 7 
    Note: The implementation report for this docment can be found at: 
    http://www.ietf.org/IESG/Implementations/rfc2373-74-implementation.txt 
    Token: Margaret Wasserman

2.1.2 Returning Item
NONE

2.2 Individual Submissions
2.2.1 New Item
  o draft-rescorla-dtls-04.txt
    Datagram Transport Layer Security (Proposed Standard) - 1 of 3 
    Token: Russ Housley
  o draft-kato-ipsec-ciph-camellia-01.txt
    The Camellia Cipher Algorithm and Its Use With IPsec (Proposed Standard) - 
    2 of 3 
    Token: Russ Housley
  o draft-mrose-rfc3288bis-01.txt
    Using the Simple Object Access Protocol (SOAP) in Blocks Extensible 
    Exchange Protocol (BEEP) (Proposed Standard) - 3 of 3 
    Token: Scott Hollenbeck

2.2.2 Returning Item
  o draft-malamud-keyword-discovery-05.txt
    Attaching Meaning to Solicitation Class Keywords (Proposed Standard) - 1 of 
    1 
    Note: Returning to clear the last discuss. 
    Token: Scott Hollenbeck

2.2.3 For Action
  o draft-ekrema-smldn-00.txt
    Standardization of Multilingualizing Domain Names(MLDN) (Proposed Standard) 
    - 1 of 1 
    Token: Brian Carpenter

3. Document Actions

3.1 WG Submissions
	Reviews should focus on these questions: "Is this document a reasonable
	contribution to the area of Internet engineering which it covers? If
	not, what changes would make it so?"

3.1.1 New Item
  o draft-ietf-sipping-conferencing-framework-04.txt
    A Framework for Conferencing with the Session Initiation Protocol 
    (Informational) - 1 of 2 
    Note: PROTO shepherd: gonzalo.camarillo@ericsson.com 
    Token: Allison Mankin
  o draft-ietf-sipping-conferencing-requirements-01.txt
    High Level Requirements for Tightly Coupled SIP Conferencing 
    (Informational) - 2 of 2 
    Note: PROTO shepherd: gonzalo.camarillo@ericsson.com 
    Token: Allison Mankin

3.1.2 Returning Item
  o draft-ietf-avt-hc-mpls-reqs-03.txt
    Requirements for Header Compression over MPLS (Informational) - 1 of 1 
    Token: Allison Mankin


3.2 Individual Submissions Via AD
	Reviews should focus on these questions: "Is this document a reasonable
	contribution to the area of Internet engineering which it covers? If
	not, what changes would make it so?"

3.2.1 New Item
  o draft-lilly-field-specification-03.txt
    Implementer-friendly Specification of Message and MIME-Part Header Fields 
    and Field Components (Informational) - 1 of 1 
    Token: Scott Hollenbeck

3.2.2 Returning Item
NONE
3.3 Individual Submissions Via RFC Editor
	Reviews should focus on these questions: "Does this document
	represent an end run around the IETF's working groups
	or its procedures? Does this document present an incompatible
	change to IETF technologies as if it were compatible?" Other
	matters may be sent to the RFC Editor in private review.

3.3.1 New Item
  o draft-eastlake-prominence-02.txt
    How to Gain Prominence and Influence in Standards Organizations 
    (Informational) - 1 of 1 
    Note: Author has been pointed at the RFC Editor's independent submission 
    mechanism. 
    Token: Brian Carpenter

3.3.2 Returning Item
NONE