From rtg-dir-bounces@ietf.org Mon Jun 05 07:01:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnCqF-0003Ef-Ek; Mon, 05 Jun 2006 07:01:51 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnCqE-0003EZ-O4 for rtg-dir@ietf.org; Mon, 05 Jun 2006 07:01:50 -0400 Received: from [63.240.77.84] (helo=sccrmhc14.comcast.net) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnCqA-0006Hl-DA for rtg-dir@ietf.org; Mon, 05 Jun 2006 07:01:50 -0400 Received: from frogbits.attlabs.att.com (c-24-6-155-213.hsd1.ca.comcast.net[24.6.155.213]) by comcast.net (sccrmhc14) with ESMTP id <2006060511004801400moauke>; Mon, 5 Jun 2006 11:00:53 +0000 Received: from frogbits.attlabs.att.com (localhost [127.0.0.1]) by frogbits.attlabs.att.com (8.13.4/8.13.4) with ESMTP id k55B09fY046871 for ; Mon, 5 Jun 2006 04:00:09 -0700 (PDT) (envelope-from fenner@frogbits.attlabs.att.com) Received: (from fenner@localhost) by frogbits.attlabs.att.com (8.13.4/8.13.4/Submit) id k55B08GP046870 for rtg-dir@ietf.org; Mon, 5 Jun 2006 04:00:08 -0700 (PDT) (envelope-from fenner) Date: Mon, 5 Jun 2006 04:00:08 -0700 (PDT) Message-Id: <200606051100.k55B08GP046870@frogbits.attlabs.att.com> From: fenner@research.att.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) X-Spam-Score: 0.1 (/) X-Scan-Signature: bfe538a859d88717fa3c8a6377d62f90 Subject: IESG agenda for 2006-06-08 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2006-06-08). Updated 2:2:32 EDT, June 5, 2006 ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 1.5 Review of Projects 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 Area Date Encapsulation Methods for Transport of ATM INT Over MPLS Networks (Proposed Standard) - 1 of 6 draft-ietf-pwe3-atm-encap-11.txt [Open Web Ballot] Note: PROTO Shepherd: Stewart Bryant Token: Mark Townsley OPS Mar 8 The Virtual Fabrics MIB (Proposed Standard) - 2 of 6 draft-ietf-imss-fc-vf-mib-02.txt [Open Web Ballot] Token: Dan Romascanu An additional mode of key distribution in SEC MIKEY: MIKEY-RSA-R (Proposed Standard) - 3 of 6 draft-ietf-msec-mikey-rsa-r-05.txt [Open Web Ballot] Note: PROTO Shepherd: Ran Canetti Token: Russ Housley RADIUS Attributes for Virtual LAN and OPS Priority Support (Proposed Standard) - 4 of 6 draft-ietf-radext-vlan-05.txt [Open Web Ballot] Note: PROTO Shepherd: David Nelson Last Call ends 6/9/2006 Token: David Kessens RAI RTP Payload Format for E-AC-3 Audio (Proposed Standard) - 5 of 6 draft-ietf-avt-rtp-eac3-01.txt [Open Web Ballot] Note: Colin Perkins is PROTO Shepherd Token: Cullen Jennings OPS RADIUS Delegated-IPv6-Prefix Attribute (Proposed Standard) - 6 of 6 draft-ietf-radext-delegated-prefix-01.txt [Open Web Ballot] Note: PROTO Shepherd: Bernard Aboba Last Call ends 6/9/2006. Token: David Kessens 2.1.2 Returning Item Area Date RAI NP Parameters for the "tel" URI (Proposed Standard) - 1 of 1 draft-ietf-iptel-tel-np-10.txt [Open Web Ballot] Note: Proto Shepherd: Jonathan Rosenberg Token: Cullen Jennings 2.2 Individual Submissions 2.2.1 New Item Area Date GEN Calendaring Extensions to WebDAV (CalDAV) (Proposed Standard) - 1 of 2 draft-dusseault-caldav-12.txt [Open Web Ballot] Token: Ted Hardie SEC Transport Layer Security (TLS) Authorization Extensions (Proposed Standard) - 2 of 2 draft-housley-tls-authz-extns-06.txt Token: Sam Hartman 2.2.2 Returning Item NONE 2.2.3 For Action Area Date GEN CellML Media Type (Proposed Standard) - 1 of 1 draft-miller-media-type-cellml-03.txt Token: Brian Carpenter 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 Area Date RTG PCE Communication Protocol Generic Requirements (Informational) - 1 of 4 draft-ietf-pce-comm-protocol-gen-reqs-06.txt [Open Web Ballot] Token: Ross Callon OPS IPv6 Transition/Co-existence Security Considerations (Informational) - 2 of 4 draft-ietf-v6ops-security-overview-04.txt [Open Web Ballot] Note: PROTO-SHEPHERDING WG chairs: Kurt Erik Lindqvist, kurtis@kurtis.pp.se Token: David Kessens OPS IPv6 Network Architecture Protection (Informational) - 3 of 4 draft-ietf-v6ops-nap-02.txt [Open Web Ballot] Note: PROTO-SHEPHERDING WG chair: Kurt Erik Lindqvist, kurtis@kurtis.pp.se Token: David Kessens OPS IPv6 Enterprise Network Analysis (Informational) - 4 of 4 draft-ietf-v6ops-ent-analysis-05.txt [Open Web Ballot] Note: PROTO Shepherd: Fred Baker 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 Area Date APP Registration of media type audio/mobile-xmf (Informational) - 1 of 2 draft-kosonen-mobile-xmf-mediatype-01.txt [Open Web Ballot] Note: Note: David Kessens put this on the agenda for Ted (see comment log) Token: Ted Hardie SEC GigaBeam High-Speed Radio Link Encryption (Informational) - 2 of 2 draft-housley-gigabeam-radio-link-encrypt-00.txt [Open Web Ballot] Token: Bill Fenner 3.2.2 Returning Item Area Date OPS Apr 6 Transferring MIB Work from IETF Bridge MIB WG to IEEE 802.1 WG (Informational) - 1 of 1 draft-harrington-8021-mib-transition-03.txt [Open Web Ballot] Note: Legal Counsel review received and the current version includes the changes following this review that should allow clearing Bert Wijnen's DISCUSS. Token: Dan Romascanu 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 Area Date GEN Server/Application State Protocol v1 (Informational) - 1 of 1 draft-bivens-sasp-03.txt [Open Web Ballot] Token: Magnus Westerlund 3.3.2 Returning Item NONE 3.3.3 For Action Area Date GEN iSeries Telnet Enhancements (Informational) - 1 of 1 draft-murphy-iser-telnet-04.txt Note: Recommended for Response 1, Note 2. of RFC 3932. Token: Ted Hardie 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review Area Date INT May 30 Access Node Control Protocol (ancp) - 1 of 1 Token: Mark 4.1.2 Proposed for Approval Area Date INT Apr 19 IP over IEEE 802.16 Networks (16ng) - 1 of 1 Token: Jari 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 7. Working Group News From rtg-dir-bounces@ietf.org Mon Jun 05 18:25:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnNW2-0005Yd-CF; Mon, 05 Jun 2006 18:25:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnNW0-0005YY-U3 for rtg-dir@ietf.org; Mon, 05 Jun 2006 18:25:40 -0400 Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnNVz-0001ZU-JF for rtg-dir@ietf.org; Mon, 05 Jun 2006 18:25:40 -0400 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k55MPc1Z079885; Mon, 5 Jun 2006 15:25:39 -0700 (PDT) (envelope-from rcallon@juniper.net) Received: from rcallon-lt1.juniper.net ([172.23.1.24]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k55MPc579974; Mon, 5 Jun 2006 15:25:38 -0700 (PDT) (envelope-from rcallon@juniper.net) Message-Id: <5.0.0.25.2.20060605182246.036f7070@zircon.juniper.net> X-Sender: rcallon@zircon.juniper.net X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Mon, 05 Jun 2006 18:25:32 -0400 To: rtg-dir@ietf.org From: Ross Callon Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Cc: jari.arkko@piuha.net Subject: Fwd: Re: routing expert to help with NETLMM WG? X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org The NETLMM working group is looking for a volunteer (or a very small number of volunteers) with routing clue to help with their work. Any volunteers? Please let Bill and I know if you are volunteering, so that we can stop beating horses. >The NETLMM working group is designing a local mobility >mechanism, basically allowing unmodified hosts to move >around within a domain and keep their IP address assignments. >As a part of the discussions in the WG's list a question has >come up whether routing protocols could be a component >of the NETLMM solution. The group has previously assumed >that such a solution would not scale, but they recently learned >that some tools (e.g. OSPF stub areas) might avoid the >scalability issues. > >A design team is currently working towards a solution >proposal. I was wondering if you knew someone with >routing clue and interest in looking at the mobility space >and provide some feedback to the design team on what's >possible and not possible with routing solutions. > >--Jari From rtg-dir-bounces@ietf.org Tue Jun 06 09:45:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnbrj-0002RS-5q; Tue, 06 Jun 2006 09:45:03 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnbrh-0002RH-OR for rtg-dir@ietf.org; Tue, 06 Jun 2006 09:45:01 -0400 Received: from sj-iport-4.cisco.com ([171.68.10.86]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fnbrg-00024Z-9t for rtg-dir@ietf.org; Tue, 06 Jun 2006 09:45:01 -0400 Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-4.cisco.com with ESMTP; 06 Jun 2006 06:44:42 -0700 X-IronPort-AV: i="4.05,214,1146466800"; d="scan'208"; a="1820159695:sNHT4508497748" Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id k56DiflE009235; Tue, 6 Jun 2006 06:44:41 -0700 Received: from [10.82.217.32] (rtp-vpn3-286.cisco.com [10.82.217.32]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k56DieIs001891; Tue, 6 Jun 2006 09:44:40 -0400 (EDT) Message-ID: <448586C2.2060203@cisco.com> Date: Tue, 06 Jun 2006 09:44:34 -0400 From: Russ White User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Ross Callon References: <5.0.0.25.2.20060605182246.036f7070@zircon.juniper.net> In-Reply-To: <5.0.0.25.2.20060605182246.036f7070@zircon.juniper.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit DKIM-Signature: a=rsa-sha1; q=dns; l=1569; t=1149601481; x=1150465481; c=relaxed/simple; s=sjdkim4001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=riw@cisco.com; z=From:Russ=20White=20 |Subject:Re=3A=20Fwd=3A=20Re=3A=20routing=20expert=20to=20help=20with=20NETLMM=20 WG?; X=v=3Dcisco.com=3B=20h=3DY6eZrwcH2Nck2svzSA+Arb0UR3A=3D; b=a1Oyjoh9MA+LGRXxPMeQBY0A4sldSmbwRX+mTxApxcdte7tXbh2fb6V90xSLh4MgjmlyenhA pGKKdzWl4JjNron+UgxeT4QoU7knniXLLViCAtiHVk0dqYS2ZRuiaYH2; Authentication-Results: sj-dkim-4.cisco.com; header.From=riw@cisco.com; dkim=pass ( 27 extraneous bytes; sig from cisco.com verified; ); X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: rtg-dir@ietf.org, jari.arkko@piuha.net Subject: Re: Fwd: Re: routing expert to help with NETLMM WG? X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alvaro and I both volunteer for this. Is the best thing just to join the list, or is there some specific list we need to join? :-) Russ Ross Callon wrote: > The NETLMM working group is looking for a volunteer (or > a very small number of volunteers) with routing clue to help > with their work. > > Any volunteers? Please let Bill and I know if you are > volunteering, so that we can stop beating horses. > >>The NETLMM working group is designing a local mobility >>mechanism, basically allowing unmodified hosts to move >>around within a domain and keep their IP address assignments. >>As a part of the discussions in the WG's list a question has >>come up whether routing protocols could be a component >>of the NETLMM solution. The group has previously assumed >>that such a solution would not scale, but they recently learned >>that some tools (e.g. OSPF stub areas) might avoid the >>scalability issues. >> >>A design team is currently working towards a solution >>proposal. I was wondering if you knew someone with >>routing clue and interest in looking at the mobility space >>and provide some feedback to the design team on what's >>possible and not possible with routing solutions. >> >>--Jari - -- riw@cisco.com CCIE <>< Grace Alone -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEhYbCER27sUhU9OQRAh5YAJ9Ys5GW6MVoYN8tRYyNQ8tGjoZxwwCeL7SA 8eqcaE+yxnSzO0z4IiPq5jg= =Z5GW -----END PGP SIGNATURE----- From rtg-dir-bounces@ietf.org Mon Jun 19 07:02:05 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsHW8-00032S-PC; Mon, 19 Jun 2006 07:02:04 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsHW7-000318-68 for rtg-dir@ietf.org; Mon, 19 Jun 2006 07:02:03 -0400 Received: from rwcrmhc11.comcast.net ([204.127.192.81]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsHW6-0006sx-PI for rtg-dir@ietf.org; Mon, 19 Jun 2006 07:02:03 -0400 Received: from frogbits.attlabs.att.com (c-24-6-155-213.hsd1.ca.comcast.net[24.6.155.213]) by comcast.net (rwcrmhc11) with ESMTP id <20060619110201m1100avs7fe>; Mon, 19 Jun 2006 11:02:01 +0000 Received: from frogbits.attlabs.att.com (localhost [127.0.0.1]) by frogbits.attlabs.att.com (8.13.4/8.13.4) with ESMTP id k5JB1NH4035634 for ; Mon, 19 Jun 2006 04:01:23 -0700 (PDT) (envelope-from fenner@frogbits.attlabs.att.com) Received: (from fenner@localhost) by frogbits.attlabs.att.com (8.13.4/8.13.4/Submit) id k5JB1N1r035633 for rtg-dir@ietf.org; Mon, 19 Jun 2006 04:01:23 -0700 (PDT) (envelope-from fenner) Date: Mon, 19 Jun 2006 04:01:23 -0700 (PDT) Message-Id: <200606191101.k5JB1N1r035633@frogbits.attlabs.att.com> From: fenner@research.att.com (Bill Fenner) To: rtg-dir@ietf.org (Routing Area Directorate) X-Spam-Score: 0.1 (/) X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b Subject: IESG agenda for 2006-06-22 telechat. X-BeenThere: rtg-dir@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Routing Area Directorate List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: rtg-dir-bounces@ietf.org IESG Agenda Good approximation of what will be included in the Agenda of next Telechat (2006-06-22). Updated 2:2:42 EDT, June 19, 2006 ----------------------------------------------------------------------- 1. Administrivia 1.1 Roll Call 1.2 Bash the Agenda 1.3 Approval of the Minutes of the past telechat 1.4 List of Remaining Action Items from Last Telechat 1.5 Review of Projects 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 Area Date RTG Graceful Restart Mechanism for BGP (Proposed Standard) - 1 of 3 draft-ietf-idr-restart-12.txt [Open Web Ballot] Token: Bill Fenner RAI The ENUM Dip Indicator parameter for the "tel" URI (Proposed Standard) - 2 of 3 draft-ietf-iptel-tel-enumdi-04.txt [Open Web Ballot] Note: Proto Shepherd: Jonathan Rosenberg Token: Cullen Jennings IANA Registration for an Enumservice RAI Containing PSTN Signaling Information (Proposed Standard) - 3 of 3 draft-ietf-enum-pstn-04.txt [Open Web Ballot] Note: PROTO Sherpherd: Patrik Faltstrom (paf@cisco.com) Token: Jon Peterson 2.1.2 Returning Item NONE 2.1.3 For Action Area Date RTG OSPF Version 2 Management Information Base (Proposed Standard) - 1 of 1 draft-ietf-ospf-mib-update-11.txt [Open Web Ballot] Token: Bill Fenner 2.2 Individual Submissions 2.2.1 New Item Area Date INT IANA Considerations for PPP over Ethernet (PPPoE) (BCP) - 1 of 5 draft-arberg-pppoe-iana-01.txt [Open Web Ballot] Note: Should end IETF LC 06/21 Token: Mark Townsley SEC IKE and IKEv2 Authentication Using ECDSA (Proposed Standard) - 2 of 5 draft-ietf-ipsec-ike-auth-ecdsa-05.txt [Open Web Ballot] Token: Russ Housley APP Calendaring Extensions to WebDAV (CalDAV) (Proposed Standard) - 3 of 5 draft-dusseault-caldav-12.txt [Open Web Ballot] Token: Ted Hardie GEN Atom Threading Extensions (Proposed Standard) - 4 of 5 draft-snell-atompub-feed-thread-12.txt [Open Web Ballot] Token: Lisa Dusseault APP SMTP Submission Service Extension for Future Message Release (Proposed Standard) - 5 of 5 draft-vaudreuil-futuredelivery-03.txt [Open Web Ballot] Note: Last Call ends on June 22, 2006 Token: Ted Hardie 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 Area Date RAI ISDN subaddress encoding type for tel URI (Informational) - 1 of 1 draft-munakata-iptel-isub-type-02.txt [Open Web Ballot] Token: Cullen Jennings 3.2.2 Returning Item NONE 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 , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for 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 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval Area Date INT May 30 Access Node Control Protocol (ancp) - 1 of 2 Token: Mark INT Apr 19 IP over IEEE 802.16 Networks (16ng) - 2 of 2 Token: Jari 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review Area Date INT Jun 13 Mobility for IPv4 (mip4) - 1 of 4 Token: Jari OPS Jun 14 IP Flow Information Export (ipfix) - 2 of 4 Token: Dan TSV Jun 12 Transport Area Working Group (tsvwg) - 3 of 4 TSV Jun 12 Datagram Congestion Control Protocol (dccp) - 4 of 4 Token: Lars 4.2.2 Proposed for Approval NONE 5. IAB News We Can Use 6. Management Issues 7. Working Group News