[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

FW: UPDATED Agenda and Package for May 25, 2006 Telechat



 
There are a few last additions to the agenda of the IESG telechat this
week. Please refer to them and the other documents brought for approval
if you have any issues. 

 Dan


-----Original Message-----
From: IESG Secretary [mailto:iesg-secretary@ietf.org] 
Sent: Tuesday, May 23, 2006 1:55 AM
To: IESG
Cc: Dinara.Suleymanova@neustar.biz; Barbara.Fuller@neustar.biz;
tme@multicasttech.com; Amy.Vezza@neustar.biz; spencer@mcsr-labs.org
Subject: UPDATED Agenda and Package for May 25, 2006 Telechat 

INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the May 25, 2006 IESG Teleconference

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-behave-nat-udp-06.txt
    NAT Behavioral Requirements for Unicast UDP (BCP) - 1 of 4 
    Note: Dan Wing <dwing@cisco.com> in sheperd. IETF Last call ends 
    2006-05-23 
    Token: Magnus Westerlund
  o Two-document ballot:  - 2 of 4
     - draft-ietf-avt-rfc2833bisdata-06.txt
       Definition of Events For Modem, FAX, and Text Telephony Signals 
       (Proposed Standard) 
       Note: PROTO shepherd magnus.westerlund@ericsson.com 
     - draft-ietf-avt-rfc2833bis-13.txt
       RTP Payload for DTMF Digits, Telephony Tones and Telephony
Signals 
       (Proposed Standard) 
       Note: PROTO shepherd Colin Perkins <csp@csperkins.org> 
    Token: Cullen Jennings
  o Two-document ballot:  - 3 of 4
     - draft-ietf-rddp-security-09.txt
       DDP/RDMAP Security (Proposed Standard) 
       Note: PROTO Sherpherd: David Black (Black_David@emc.com) 
     - draft-ietf-rddp-applicability-06.txt
       Applicability of Remote Direct Memory Access Protocol (RDMA) and
Direct 
       Data Placement (DDP) (Informational) 
       Note: PROTO Shepherd: David Black (Black_David@emc.com) 
    Token: Jon Peterson
  o draft-ietf-pwe3-hdlc-ppp-encap-mpls-08.txt
    Encapsulation Methods for Transport of PPP/HDLC Over MPLS Networks 
    (Proposed Standard) - 4 of 4 
    Token: Mark Townsley

2.1.2 Returning Item
  o draft-ietf-grow-rfc1519bis-04.txt
    Classless Inter-Domain Routing (CIDR): The Internet Address
Assignment and 
    Aggregation Plan (BCP) - 1 of 1 
    Note: Geoff Huston is the proto shepherd 
    Token: David Kessens


2.2 Individual Submissions
2.2.1 New Item
NONE
2.2.2 Returning Item
  o draft-fenner-iana-exp-2780-04.txt
    Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP and TCP
Headers 
    (Proposed Standard) - 1 of 1 
    Note: 3/20/06: Waiting for -03 version from Bill Fenner to address 
    discusses.. 5/5/06: Waiting for Mark to remove his Discuss and/or
talk to 
    Bill.. 16/5/06: Bill submits a new revision, document placed on next

    telechat agenda. 
    Token: Jari Arkko


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-bmwg-benchres-term-07.txt
    Benchmarking Terminology for Resource Reservation Capable Routers 
    (Informational) - 1 of 9 
    Note: Proto Spepherd: Al Morton <acmorton@att.com> 
    Token: David Kessens
  o draft-arberg-pppoe-mtu-gt1492-03.txt
    Accommodating an MTU/MRU greater than 1492 in PPPoE (Informational)
- 2 of 
    9 
    Token: Mark Townsley
  o draft-ietf-pce-comm-protocol-gen-reqs-06.txt
    PCE Communication Protocol Generic Requirements (Informational) - 3
of 9 
    Token: Ross Callon
  o draft-ietf-pce-discovery-reqs-04.txt
    Requirements for Path Computation Element (PCE) Discovery
(Informational) - 
    4 of 9 
    Token: Ross Callon
  o draft-ietf-rmt-bb-tfmcc-07.txt
    TCP-Friendly Multicast Congestion Control (TFMCC): Protocol
Specification 
    (Experimental) - 5 of 9 
    Note: PROTO shepherd: lorenzo vicisano lorenzo@cisco.com. IETF last
call 
    ends 24th of May 
    Token: Magnus Westerlund
  o draft-ietf-bmwg-dsmterm-12.txt
    Terminology for Benchmarking Network-layer Traffic Control
Mechanisms 
    (Informational) - 6 of 9 
    Note: Al Morton <acmorton@att.com> is the proto shepherd 
    Token: David Kessens
  o draft-ietf-v6ops-security-overview-04.txt
    IPv6 Transition/Co-existence Security Considerations (Informational)
- 7 of 
    9 
    Note: PROTO-SHEPHERDING WG chairs: Kurt Erik Lindqvist,
kurtis@kurtis.pp.se 
    Token: David Kessens
  o draft-ietf-v6ops-bb-deployment-scenarios-04.txt
    ISP IPv6 Deployment Scenarios in Broadband Access Networks
(Informational) 
    - 8 of 9 
    Note: SHEPHERDING WG chair: Kurt Erik Lindqvist, kurtis@kurtis.pp.se

    Token: David Kessens
  o draft-ietf-v6ops-nap-02.txt
    IPv6 Network Architecture Protection (Informational) - 9 of 9 
    Note: PROTO-SHEPHERDING WG chair: Kurt Erik Lindqvist,
kurtis@kurtis.pp.se 
    Token: David Kessens

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-hoffman-taobis-07.txt
    The Tao of IETF - A Novice's Guide to the Internet Engineering Task
Force 
    (Informational) - 1 of 2 
    Token: Brian Carpenter
  o draft-eronen-ipsec-ikev2-clarifications-09.txt
    IKEv2 Clarifications and Implementation Guidelines (Informational) -
2 of 2 
    Token: Russ Housley

3.2.2 Returning Item
  o draft-hartman-mailinglist-experiment-03.txt
    Experimental Procedure for Long Term Suspensions from Mailing Lists 
    (Experimental) - 1 of 1 
    Note: Last call ended March 15 
    Token: Brian Carpenter

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
  o draft-bivens-sasp-03.txt
    Server/Application State Protocol v1 (Informational) - 1 of 1 
    Token: Magnus Westerlund