[AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for November 19, 2009 Telechat

["Romascanu, Dan (Dan)" <[e-mail]>]

Please find below the preliminary agenda of the 11/19 IESG telechat.
Please send me your questions, comments and concerns before 11/18 COB. 

Thanks and Regards,

Dan
 

2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-syslog-sign-28.txt
    Signed syslog Messages (Proposed Standard) - 1 of 8 
    Token: Pasi Eronen
  o draft-ietf-mboned-rfc3171bis-07.txt
    IANA Guidelines for IPv4 Multicast Address Assignments (BCP) - 2 of
8

    Token: Ron Bonica
  o draft-ietf-6man-overlap-fragment-03.txt
    Handling of overlapping IPv6 fragments (Proposed Standard) - 3 of 8 
    Note: Brian Haberman ([e-mail]) is the document
shepherd. 
    Token: Jari Arkko
  o draft-ietf-tsvwg-rsvp-l3vpn-03.txt
    Support for RSVP in Layer 3 VPNs (Proposed Standard) - 4 of 8 
    Token: Magnus Westerlund
  o draft-ietf-pkix-authorityclearanceconstraints-03.txt
    Clearance Attribute and Authority Clearance Constraints Certificate 
    Extension (Proposed Standard) - 5 of 8 
    Token: Tim Polk
  o draft-ietf-dna-simple-11.txt
    Simple procedures for Detecting Network Attachment in IPv6 (Proposed

    Standard) - 6 of 8 
    Note: (no document shepherd) 
    Token: Jari Arkko
  o draft-ietf-mmusic-connectivity-precon-06.txt
    Connectivity Preconditions for Session Description Protocol Media
Streams 
    (Proposed Standard) - 7 of 8 
    Note: Please note sec-dir review comments were addressed in RFC Ed
Note.. 
    Document Shepherd: Jean-Francois Mule ([e-mail]) 
    Token: Cullen Jennings
  o draft-ietf-forces-sctptml-06.txt
    SCTP based TML (Transport Mapping Layer) for ForCES protocol
(Proposed
 
    Standard) - 8 of 8 
    Note: The document shepherd has been changed to Joel Halpern 
    ([e-mail]). 
    Token: Ross Callon

2.1.2 Returning Item
  o draft-ietf-mipshop-pfmipv6-09.txt
    Fast Handovers for Proxy Mobile IPv6 (Proposed Standard) - 1 of 2 
    Note: Vijay Devarapalli ([e-mail]) is the document
shepherd.
 
    Token: Jari Arkko
  o draft-ietf-l3vpn-2547bis-mcast-bgp-08.txt
    BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs
(Proposed 
    Standard) - 2 of 2 
    Token: Ross Callon


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
NONE

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-ccamp-mpls-graceful-shutdown-12.txt
    Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering
Networks 
    (Informational) - 1 of 3 
    Note: Lou Berger ([e-mail]) is the document shepherd. 
    Token: Adrian Farrel
  o draft-ietf-bmwg-ipsec-term-12.txt
    Terminology for Benchmarking IPsec Devices (Informational) - 2 of 3 
    Note: Al Morton ([e-mail]) is the document shepherd. 
    Token: Ron Bonica
  o draft-ietf-bmwg-ipsec-meth-05.txt
    Methodology for Benchmarking IPsec Devices (Informational) - 3 of 3 
    Note: Al Morton ([e-mail]) is the document shepherd. 
    Token: Ron Bonica

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
  o draft-turner-deviceowner-attribute-02.txt
    Device Owner Attribute (Informational) - 1 of 4 
    Token: Tim Polk
  o draft-turner-clearancesponsor-attribute-02.txt
    Clearance Sponsor Attribute (Informational) - 2 of 4 
    Token: Tim Polk
  o draft-carpenter-renum-needs-work-04.txt
    Renumbering still needs work (Informational) - 3 of 4 
    Token: Dan Romascanu
  o draft-melnikov-sasl-scram-ldap-04.txt
    LDAP schema for storing SCRAM secrets (Informational) - 4 of 4 
    Token: Pasi Eronen

3.2.2 Returning Item
NONE
3.3 Independent 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.

	The document shepherd must propose one of these responses in
	the Data Tracker note and supply complete text in the IESG
	Note portion of the write-up. The Area Director ballot positions
	indicate consensus with the response proposed by the
	document shepherd.

	Other matters may be recorded in comments, and the comments will
	be passed on to the RFC Editor as community review of the
document.


3.3.1 New Item
NONE
3.3.2 Returning Item
  o draft-levy-sip-diversion-10.txt
    Diversion Indication in SIP (Historic) - 1 of 1 
    Token: Robert Sparks

3.3.3 For Action
  o draft-nsri-aria-02.txt
    A Description of the ARIA Encryption Algorithm (Informational) - 1
of
1 
    Token: Russ Housley

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
  o HTTP State Management Mechanism (http-state) - 1 of 1
    Token: Lisa Dusseault
4.1.2 Proposed for Approval
  o Internet Area Working Group (intareawg) - 1 of 1
    Token: Jari Arkko
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Handover Keying (hokey) - 1 of 1
    Token: Tim Polk