Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for January 29, 2009 Telechat

From: "Romascanu, Dan (Dan)" <[email-masked]>
Date: Fri, 23 Jan 2009 09:12:38 +0100

Please review the relevant documents and WG charters brought up for
approval and send me your comments until Wednesday 1/28 COB the latest. 

The full agenda and links to the documents is available at
http://www.ietf.org/IESG/agenda.html. 

Thanks and Regards,

Dan

2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-mext-nemo-mib-04.txt
    NEMO Management Information Base (Proposed Standard) - 1 of 10 
    Token: Jari Arkko
  o draft-ietf-radext-management-authorization-06.txt
    Remote Authentication Dial-In User Service (RADIUS) Authorization
for

    Network Access Server (NAS) Management (Proposed Standard) - 2 of 10

    Token: Dan Romascanu
  o draft-ietf-pkix-rfc4055-update-01.txt
    Update for RSAES-OAEP Algorithm Parameters (Proposed Standard) - 3
of
10 
    Token: Pasi Eronen
  o draft-ietf-softwire-mesh-framework-05.txt
    Softwire Mesh Framework (Proposed Standard) - 4 of 10 
    Token: Mark Townsley
  o draft-ietf-softwire-encaps-safi-04.txt
    BGP Encapsulation SAFI and BGP Tunnel Encapsulation Attribute
(Proposed 
    Standard) - 5 of 10 
    Token: Mark Townsley
  o draft-ietf-softwire-encaps-ipsec-01.txt
    BGP IPSec Tunnel Encapsulation Attribute (Proposed Standard) - 6 of
10
 
    Token: Mark Townsley
  o draft-ietf-softwire-bgp-te-attribute-04.txt
    BGP Traffic Engineering Attribute (Proposed Standard) - 7 of 10 
    Token: Mark Townsley
  o draft-ietf-softwire-v4nlri-v6nh-01.txt
    Advertising an IPv4 NLRI with an IPv6 Next Hop (Proposed Standard) -
8
of 
    10 
    Token: Mark Townsley
  o draft-ietf-tls-psk-new-mac-aes-gcm-05.txt
    Pre-Shared Key Cipher Suites for Transport Layer Security (TLS) with

    SHA-256/384 and AES Galois Counter Mode (Proposed Standard) - 9 of
10

    Note: Document Shepherd is [email-masked] 
    Token: Pasi Eronen
  o draft-ietf-idr-flow-spec-03.txt
    Dissemination of flow specification rules (Proposed Standard) - 10
of
10 
    Token: David Ward

2.1.2 Returning Item
  o draft-ietf-mipshop-mstp-solution-11.txt
    IEEE 802.21 Mobility Services Framework Design (MSFD) (Proposed
Standard) - 
    1 of 1 
    Token: Jari Arkko

2.2 Individual Submissions
2.2.1 New Item
  o draft-stjohns-sipso-06.txt
    Common Architecture Label IPv6 Security Option (CALIPSO) (Proposed 
    Standard) - 1 of 3 
    Token: Tim Polk
  o draft-hoffman-dac-vbr-05.txt
    Vouch By Reference (Proposed Standard) - 2 of 3 
    Token: Russ Housley
  o draft-melnikov-sieve-imapext-metadata-08.txt
    The Sieve mail filtering language - extensions for checking mailbox
status 
    and accessing mailbox metadata (Proposed Standard) - 3 of 3 
    Token: Lisa Dusseault

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-trill-prob-05.txt
    Transparent Interconnection of Lots of Links (TRILL): Problem and 
    Applicability Statement (Informational) - 1 of 3 
    Token: Mark Townsley
  o draft-ietf-pim-rpf-vector-08.txt
    The RPF Vector TLV (Informational) - 2 of 3 
    Token: David Ward
  o draft-ietf-tls-ecdhe-psk-05.txt
    ECDHE_PSK Ciphersuites for Transport Layer Security (TLS)
(Informational) - 
    3 of 3 
    Token: Pasi Eronen

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
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
NONE
3.3.3 For Action
  o draft-irtf-routing-history-09.txt
    Analysis of Inter-Domain Routing Requirements and History (Historic)
-
1 of 
    2 
    Token: Russ Housley
  o draft-irtf-routing-reqs-10.txt
    A Set of Possible Requirements for a Future Routing Architecture
(Historic) 
    - 2 of 2 
    Token: Russ Housley

4. Working Group Actions
4.1 WG Creation
4.1.1 Proposed for IETF Review
    NONE
4.1.2 Proposed for Approval
    NONE
4.2 WG Rechartering
4.2.1 Under evaluation for IETF Review
    NONE
4.2.2 Proposed for Approval
  o Network Configuration (netconf) - 1 of 2
    Token: Dan Romascanu
  o IP Performance Metrics (ippm) - 2 of 2
    Token: Lars Eggert

_______________________________________________
AAA-DOCTORS mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/aaa-doctors