Please review documents on IESG Agenda for July 21, 2005 Telechat

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

AAA-doctors,

pls review, specifically  from an AAA point of view.

Thanks,
Bert

-----Original Message-----
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-mpls-bgp-mpls-restart-04.txt
    Graceful Restart Mechanism for BGP with MPLS (Proposed Standard) - 1 of 6 
    Token: Alex Zinin
  o Two-document ballot:  - 2 of 6
     - draft-ietf-nntpext-tls-nntp-07.txt
       Using TLS with NNTP (Proposed Standard) 
     - draft-ietf-nntpext-authinfo-09.txt
       NNTP Extension for Authentication (Proposed Standard) 
       Note: Document shepherd: Russ Allbery <rra@stanford.edu> 
    Token: Scott Hollenbeck
  o draft-ietf-vrrp-ipv6-spec-07.txt
    Virtual Router Redundancy Protocol for IPv6 (Proposed Standard) - 3 of 6 
    Token: Alex Zinin
  o draft-ietf-pwe3-control-protocol-17.txt
    Pseudowire Setup and Maintenance using the Label Distribution Protocol 
    (Proposed Standard) - 4 of 6 
    Token: Mark Townsley
  o draft-ietf-pkix-rfc3770bis-03.txt
    Certificate Extensions and Attributes Supporting Authentication in 
    Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN) 
    (Proposed Standard) - 5 of 6 
    Note: proto shepherd: tim.polk@nist.gov 
    Token: Sam Hartman
  o draft-ietf-nntpext-streaming-06.txt
    NNTP Extension for Streaming Feeds (Proposed Standard) - 6 of 6 
    Note: Document shepherd: Russ Allbery <rra@stanford.edu> 
    Token: Scott Hollenbeck

2.1.2 Returning Item
  o draft-ietf-idr-bgp-ext-communities-09.txt
    BGP Extended Communities Attribute (Proposed Standard) - 1 of 3 
    Note: Return to agenda to see if Russ is OK with the security 
    considerations. 
    Token: Bill Fenner
  o draft-ietf-mpls-rsvpte-attributes-05.txt
    Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label 
    Switched Path (LSP) Establishment Using RSVP-TE (Proposed Standard) - 2 of 
    3 
    Token: Alex Zinin
  o draft-ietf-geopriv-dhcp-civil-06.txt
    Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic 
    Addresses Configuration Information (Proposed Standard) - 3 of 3 
    Note: Back on to check RFC Editor notes 
    Token: Ted Hardie


2.2 Individual Submissions
2.2.1 New Item
  o draft-lim-mpeg4-mime-03.txt
    MIME Type Registration for MPEG-4 (Proposed Standard) - 1 of 3 
    Note: To IESG and I'll hold a Discuss until Last Call ends (MPEG needs 
    before end of summer) 
    Token: Allison Mankin
  o draft-garudadri-avt-3gpp2-mime-02.txt
    MIME Type Registrations for 3GPP2 Multimedia files (Proposed Standard) - 2 
    of 3 
    Note: To IESG and I'll hold in Discuss until Last Call ends (3GPP2 deadline 
    this summer) 
    Token: Allison Mankin
  o draft-crispin-imap-rfc2359bis-04.txt
    Internet Message Access Protocol (IMAP) - UIDPLUS extension (Proposed 
    Standard) - 3 of 3 
    Token: Scott Hollenbeck

2.2.2 Returning Item
  o draft-freed-media-type-reg-04.txt
    Media Type Specifications and Registration Procedures (BCP) - 1 of 1 
    Note: Returning to discuss the last remaining discuss. 
    Token: Scott Hollenbeck


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-mmusic-offer-answer-examples-06.txt
    Session Description Protocol Offer/Answer Examples (Informational) - 1 of 1 
    Token: Jon Peterson

3.1.2 Returning Item
NONE

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
NONE
3.2.2 Returning Item
  o draft-nottingham-hdrreg-http-05.txt
    HTTP Header Field Registrations (Informational) - 1 of 1 
    Token: Scott Hollenbeck

3.3 Individual Submissions Via RFC Editor
	The IESG will use RFC 3932 responses: 1) The IESG has not
	found any conflict between this document and IETF work; 2) The
	IESG thinks that this work is related to IETF work done in WG
	<X>, but this does not prevent publishing; 3) The IESG thinks
	that publication is harmful to work in WG <X> and recommends
	not publishing at this time; 4) The IESG thinks that this
	document violates the IETF procedures for <X> and should
	therefore not be published without IETF review and IESG
	approval; 5) The IESG thinks that this document extends an
	IETF protocol in a way that requires IETF review and should
	therefore not be published without IETF review and IESG approval.
                                                                                              
	Other matters may be recorded in comments to be passed on
	to the RFC Editor as community review of the document.


3.3.1 New Item
NONE
3.3.2 Returning Item
NONE