[MIB-DOCTORS] FW: PRELIMINARY Agenda and Package for December 4, 2008 Telechat

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

 
Please find below the preliminary agenda of the 12/4 IESG telechat.
Please review the documents and send your comments or concerns until
Wednesday 12/3, COB the latest. 

Thanks and Regards,

Dan



2.1 WG Submissions
2.1.1 New Item
  o draft-ietf-nfsv4-minorversion1-26.txt
    NFS Version 4 Minor Version 1 (Proposed Standard) - 1 of 11 
    Note: Brian Pawslowski ([e-mail]) is the document shepherd..

    Token: Lars Eggert
  o draft-ietf-nfsv4-pnfs-block-10.txt
    pNFS Block/Volume Layout (Proposed Standard) - 2 of 11 
    Token: Lars Eggert
  o draft-ietf-nfsv4-pnfs-obj-09.txt
    Object-based pNFS Operations (Proposed Standard) - 3 of 11 
    Token: Lars Eggert
  o draft-ietf-sieve-notify-mailto-09.txt
    Sieve Notification Mechanism: mailto (Proposed Standard) - 4 of 11 
    Note: Barry Leiba to be the expert reviewer for the registry this
creates. 
    Token: Lisa Dusseault
  o draft-ietf-mip4-dsmipv4-08.txt
    Dual Stack Mobile IPv4 (Proposed Standard) - 5 of 11 
    Token: Jari Arkko
  o draft-cridland-urlfetch-binary-03.txt
    Extended URLFETCH for binary and converted parts (Proposed Standard)
-
6 of 
    11 
    Note: Eric Burger is document shepherd. Note this is a lemonade
WG 
    document despite the name. 
    Token: Chris Newman
  o draft-ietf-lemonade-imap-notify-07.txt
    The IMAP NOTIFY Extension (Proposed Standard) - 7 of 11 
    Note: Eric Burger is document shepherd 
    Token: Chris Newman
  o draft-ietf-dnsext-forgery-resilience-09.txt
    Measures for making DNS more resilient against forged answers
(Proposed 
    Standard) - 8 of 11 
    Token: Mark Townsley
  o draft-ietf-monami6-multiplecoa-10.txt
    Multiple Care-of Addresses Registration (Proposed Standard) - 9 of
11

    Token: Jari Arkko
  o draft-ietf-nfsv4-minorversion1-dot-x-09.txt
    NFSv4 Minor Version 1 XDR Description (Proposed Standard) - 10 of 11

    Note: Brian Pawslowski ([e-mail]) is the document shepherd. 
    Token: Lars Eggert
  o draft-ietf-6man-reserved-iids-01.txt
    Reserved IPv6 Interface Identifiers (Proposed Standard) - 11 of 11 
    Token: Jari Arkko

2.1.2 Returning Item
  o draft-ietf-nsis-ntlp-17.txt
    GIST: General Internet Signalling Transport (Proposed Standard) - 1
of
1 
    Note: RE-evaluate your ABSTAIN positions. All that stays in ABSTAIN
please 
    indicate in the comment field that you have performed this
re-evaluation 
    and also include some motivation behind your decision. . 
    Token: Magnus Westerlund


2.2 Individual Submissions
2.2.1 New Item
  o draft-housley-iesg-rfc3932bis-06.txt
    IESG Procedures for Handling of Independent and IRTF Stream
Submissions 
    (BCP) - 1 of 1 
    Note: Diff: http://www.arkko.com/ietf/iesg/rfc3932bisdiff.html 
    Token: Jari Arkko

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
NONE
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-arkko-arp-iana-rules-01.txt
    IANA Allocation Guidelines for the Address Resolution Protocol (ARP)

    (Informational) - 1 of 1 
    Token: Russ Housley

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
  o draft-irtf-asrg-dnsbl-08.txt
    DNS Blacklists and Whitelists (Informational) - 1 of 1 
    Note: Propose to respond "1. The IESG has not found any conflict
between 
    this document and IETF work." 
    Token: Lisa Dusseault

3.3.2 Returning Item
NONE
3.3.3 For Action
  o draft-bberry-rfc4938bis-00.txt
    PPP Over Ethernet (PPPoE) Extensions for Credit Flow and Link
Metrics

    (Informational) - 1 of 1 
    Note: Independent submission, being reviewed by pppext 
    Token: Mark Townsley

_______________________________________________
MIB-DOCTORS mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/mib-doctors