From ajs@anvilwalrusden.com Mon Jul 9 11:22:49 2012 Return-Path: X-Original-To: dns-dir@ietfa.amsl.com Delivered-To: dns-dir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B35CC11E8119 for ; Mon, 9 Jul 2012 11:22:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.889 X-Spam-Level: X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[AWL=-1.538, BAYES_05=-1.11, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0j8B4FIXm0R for ; Mon, 9 Jul 2012 11:22:48 -0700 (PDT) Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 356D811E8118 for ; Mon, 9 Jul 2012 11:22:45 -0700 (PDT) Received: from mail.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 441818A031 for ; Mon, 9 Jul 2012 18:23:09 +0000 (UTC) Date: Mon, 9 Jul 2012 14:23:07 -0400 From: Andrew Sullivan To: dns-dir@ietf.org Message-ID: <20120709182306.GF75702@mail.yitter.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: [dns-dir] How bad an idea is this? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 18:22:50 -0000 Dear colleagues, I wasn't sure where else to send this: it's not actually about the protocol, and it's not about operations as such, but it is about the (ab)use of the DNS. Suggestions for a better target welcome, but reactions to the suggestion below are even more welcome. In draft-sullivan-domain-origin-assert-00, I outline a mechanism to make claims about whether a given DNS name lies within the same administrative realm as another name. By "same administrative realm", what I mean to say is that the services at that name and at some other name are somehow subject to the same control, &c. The standard example of where this might help is with the "cookies problem", but I don't think we have to be too creative to think of ways in which it would be helpful to know that services at different names are related to one another in important ways, without really being "the same service". I received a number of comments about that draft, not least of which was that to be useful it needed finer granularity. (More exactly, the mechanism is apparently worthless without being able to specify it by scheme, port, _and_ name.) That would be easy given that I was originally inclined to create a new RRTYPE, except that I also heard over and over again that new RRTYPEs are not deployable: the provisioning software doesn't know how to do it. I have some sympathy for this, since Dyn (who partly pays for the roof over my head) has plenty of clueful staff, but avoids completely unknown RRTYPE support in its consumer-grade offerings because of the potential support headaches. As a result of this, I have been toying with reusing the SRV RRTYPE, adding some additional underscore labels to the front. This idea makes me want to tear at my clothes, but I haven't been able to think of ways in which it actually breaks anything. Does anyone have such an argument? In addition (just to make you even more queasy), it seems to me that the mechanism is going to have to be able to say "for everything under this name, the same label under that name". A wildcard isn't exactly going to work, particularly on the target side of the SRV record. I was thinking of inventing a new "prefix" (like the xn-- in IDNA) to express this sort of thing. It's yet more evidence, I think, that a real RRTYPE with its own semantics is just going to be necessary, but that probably means the mechanism will never get deployed. Thoughts? A -- Andrew Sullivan ajs@anvilwalrusden.com From paf@frobbit.se Mon Jul 9 12:53:04 2012 Return-Path: X-Original-To: dns-dir@ietfa.amsl.com Delivered-To: dns-dir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE9621F8517 for ; Mon, 9 Jul 2012 12:53:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9+PoJTSwXFuR for ; Mon, 9 Jul 2012 12:52:57 -0700 (PDT) Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id D457D11E8083 for ; Mon, 9 Jul 2012 12:52:56 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id AFB5C142AD8F4; Mon, 9 Jul 2012 21:53:21 +0200 (CEST) X-Virus-Scanned: amavisd-new at frobbit.se Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuoTFdq7tv2o; Mon, 9 Jul 2012 21:53:21 +0200 (CEST) Received: from [172.20.10.2] (2.67.95.148.mobile.tre.se [2.67.95.148]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 60452142AD8F1; Mon, 9 Jul 2012 21:53:21 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= In-Reply-To: <20120709182306.GF75702@mail.yitter.info> Date: Mon, 9 Jul 2012 21:53:20 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <5464750F-2E63-4AAE-9616-E0A95A8E227F@frobbit.se> References: <20120709182306.GF75702@mail.yitter.info> To: Andrew Sullivan X-Mailer: Apple Mail (2.1278) Cc: dns-dir@ietf.org Subject: Re: [dns-dir] How bad an idea is this? X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 19:53:04 -0000 On 9 jul 2012, at 20:23, Andrew Sullivan wrote: > It's yet more evidence, I think, that a > real RRTYPE with its own semantics is just going to be necessary, but > that probably means the mechanism will never get deployed. I hear you, but I am not giving up! :-P Patrik P.S. Will sleep on this and possibly respond differently or stronger = tomorrow. From brian@innovationslab.net Tue Jul 10 14:22:33 2012 Return-Path: X-Original-To: dns-dir@ietfa.amsl.com Delivered-To: dns-dir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C5911E80E5 for ; Tue, 10 Jul 2012 14:22:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tia0GbEoffqV for ; Tue, 10 Jul 2012 14:22:32 -0700 (PDT) Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0C52111E80CC for ; Tue, 10 Jul 2012 14:22:32 -0700 (PDT) Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id C9F8E88091 for ; Tue, 10 Jul 2012 14:23:00 -0700 (PDT) Received: from clemson.local (unknown [24.229.3.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id BCB61130017 for ; Tue, 10 Jul 2012 14:22:59 -0700 (PDT) Message-ID: <4FFC9D4B.3070402@innovationslab.net> Date: Tue, 10 Jul 2012 17:23:23 -0400 From: Brian Haberman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: dns-dir@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [dns-dir] Request for review : draft-ietf-pkix-caa X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jul 2012 21:22:33 -0000 Hi all, Could I get a volunteer or two to sanity check the DNS component of draft-ietf-pkix-caa? It specifies the use of a Resource Record to identify Certification Authorities for a domain. It is currently slated to be discussed on the July 17th IESG telechat, so it could be useful to have a review in-hande, before then. Regards, Brian From bclaise@cisco.com Fri Jul 13 16:47:57 2012 Return-Path: X-Original-To: dns-dir@ietfa.amsl.com Delivered-To: dns-dir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBE5E11E80EE; Fri, 13 Jul 2012 16:47:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.439 X-Spam-Level: X-Spam-Status: No, score=-10.439 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTJBDkjHFkok; Fri, 13 Jul 2012 16:47:56 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id ED65B11E80C0; Fri, 13 Jul 2012 16:47:55 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q6DNmWQK024250; Sat, 14 Jul 2012 01:48:32 +0200 (CEST) Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q6DNmTxj020470; Sat, 14 Jul 2012 01:48:29 +0200 (CEST) Message-ID: <5000B3CD.5000604@cisco.com> Date: Sat, 14 Jul 2012 01:48:29 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: aaa-doctors@ietf.org, "MIB Doctors (E-mail)" , YANG Doctors , "ops-dir@ietf.org" , IETF DNS Directorate References: <20120712224354.13043.7504.idtracker@ietfa.amsl.com> In-Reply-To: <20120712224354.13043.7504.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20120712224354.13043.7504.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------090602040801030608060707" Subject: [dns-dir] [IESG-AGENDA-DIST] Summarized Agenda for the 2012-07-19 IESG Teleconference X-BeenThere: dns-dir@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: IETF DNS directorate discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 23:47:58 -0000 This is a multi-part message in MIME format. --------------090602040801030608060707 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, Please find below the agenda of the July 19th IESG telechat. Please send your questions, comments and concerns before July 18th COB. Thanks and Regards, Benoit. -------- Original Message -------- Subject: [IESG-AGENDA-DIST] Summarized Agenda for the 2012-07-19 IESG Teleconference Date: Thu, 12 Jul 2012 15:43:54 -0700 From: IESG Secretary To: iesg-agenda-dist@ietf.org INTERNET ENGINEERING STEERING GROUP (IESG) Summarized Agenda for the 2012-07-19 IESG Teleconference This agenda was generated at 2012-07-12 15:42:12 PDT Up-to-date web version of this agenda can be found at: http://datatracker.ietf.org/iesg/agenda/ 2. Protocol Actions 2.1 WG Submissions 2.1.1 New Items o draft-sakane-dhc-dhcpv6-kdc-option-17 Kerberos Options for DHCPv6 (Proposed Standard) Note: The Document Shepherd for this document is Jeffrey Hutzelman, (jhutz@cmu.edu). Token: Stephen Farrell o draft-ietf-behave-lsn-requirements-08 Common requirements for Carrier Grade NATs (CGNs) (Best Current Practice) Note: Dan Wing (dwing@cisco.com) is the document shepherd. Token: Wesley Eddy o draft-ietf-6lowpan-btle-08 Transmission of IPv6 Packets over Bluetooth Low Energy (Proposed Standard) Note: Carsten Bormann (cabo@tzi.org) is the Document Shepherd. Token: Ralph Droms o draft-ietf-idr-rfc4893bis-07 BGP Support for Four-octet AS Number Space (Proposed Standard) Note: John Scudder (jgs@juniper.net) is the document shepherd. Token: Stewart Bryant o draft-ietf-abfab-gss-eap-08 A GSS-API Mechanism for the Extensible Authentication Protocol (Proposed Standard) Token: Stephen Farrell o draft-ietf-dnsext-dnssec-algo-imp-status-03 Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm Implementation Status (Best Current Practice) Note: Andrew Sullivan (ajs@anvilwalrusden.com) is the Document Shepherd Token: Ralph Droms o draft-ietf-dnsext-dnssec-registry-update-03 DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates (Proposed Standard) Note: Andrew Sullivan (ajs@anvilwalrusden.com) is the Document Shepherd Token: Ralph Droms o draft-ietf-appsawg-received-state-04 Indicating Email Handling States in Trace Fields (Proposed Standard) Token: Barry Leiba o draft-ietf-pkix-caa-10 DNS Certification Authority Authorization (CAA) Resource Record (Proposed Standard) Note: Steve Kent (kent@bbn.com) is the Document Shepherd. Token: Sean Turner 2.1.2 Returning Items NONE 2.2 Individual Submissions 2.2.1 New Items o draft-sandlund-rfc4996bis-02 RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP) (Proposed Standard) Token: Wesley Eddy o draft-camarillo-rai-media-policy-dataset-02 A User Agent Profile Data Set for Media Policy (Proposed Standard) Note: Mary Barnes is the document shepherd Token: Robert Sparks o draft-farrell-decade-ni-09 Naming Things with Hashes (Proposed Standard) Note: Alexey Melnikov (Alexey.Melnikov@isode.com) is the document shepherd. Token: Barry Leiba 2.2.2 Returning Items NONE 3. Document Actions 3.1 WG Submissions 3.1.1 New Items o draft-ietf-karp-threats-reqs-05 Keying and Authentication for Routing Protocols (KARP) Overview, Threats, and Requirements (Informational) Note: Brian Weis (bew@cisco.com) is the document shepherd. Token: Stewart Bryant o draft-ietf-cdni-use-cases-09 Use Cases for Content Delivery Network Interconnection (Informational) Note: Francois Le Faucheur (flefauch@cisco.com) is the Document Shepherd. Token: Martin Stiemerling o draft-ietf-ippm-twamp-value-added-octets-04 Ericsson TWAMP Value-Added Octets (Informational) Note: Henk Uijterwaal (henk@uijterwaal.nl) is the document shepherd. Token: Wesley Eddy o draft-ietf-oauth-urn-sub-ns-05 An IETF URN Sub-Namespace for OAuth (Informational) Note: Derek Atkins (derek@ihtfp.com) is the document shepherd. Token: Stephen Farrell 3.1.2 Returning Items NONE 3.2 Individual Submissions Via AD 3.2.1 New Items o draft-claise-export-application-info-in-ipfix-09 Cisco Systems Export of Application Information in IPFIX (Informational) Note: Individual Submission, AD-sponsored, Nevil Brownlee is the document shepherd, Token: Ronald Bonica o draft-melnikov-smtp-priority-tunneling-03 Tunneling of SMTP Message Transfer Priorities (Experimental) Token: Pete Resnick o draft-krishnan-nomcom-tools-01 Requirements for IETF Nominations Committee tools (Informational) Token: Russ Housley 3.2.2 Returning Items NONE 3.3 IRTF and Independent Submission Stream Documents 3.3.1 New Items NONE 3.3.2 Returning Items NONE 3.3.3 For Action o draft-mme-trill-fcoe-02 FCoE over TRILL (Informational) Note: ISE submission Token: Ralph Droms 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 NONE --------------090602040801030608060707 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

Please find below the agenda of the July 19th  IESG telechat.

Please send your questions, comments and concerns before July 18th COB.

Thanks and Regards, Benoit.


-------- Original Message --------
Subject: [IESG-AGENDA-DIST] Summarized Agenda for the 2012-07-19 IESG Teleconference
Date: Thu, 12 Jul 2012 15:43:54 -0700
From: IESG Secretary <iesg-secretary@ietf.org>
To: iesg-agenda-dist@ietf.org 


INTERNET ENGINEERING STEERING GROUP (IESG)
Summarized Agenda for the 2012-07-19 IESG Teleconference

This agenda was generated at 2012-07-12 15:42:12 PDT
Up-to-date web version of this agenda can be found at:
http://datatracker.ietf.org/iesg/agenda/
                                                                                


2. Protocol Actions
2.1 WG Submissions
2.1.1 New Items

  o draft-sakane-dhc-dhcpv6-kdc-option-17
    Kerberos Options for DHCPv6 (Proposed Standard)
    Note: The Document Shepherd for this document is Jeffrey Hutzelman,
    (jhutz@cmu.edu).
    Token: Stephen Farrell

  o draft-ietf-behave-lsn-requirements-08
    Common requirements for Carrier Grade NATs (CGNs) (Best Current
    Practice)
    Note: Dan Wing (dwing@cisco.com) is the document shepherd.
    Token: Wesley Eddy

  o draft-ietf-6lowpan-btle-08
    Transmission of IPv6 Packets over Bluetooth Low Energy (Proposed
    Standard)
    Note: Carsten Bormann (cabo@tzi.org) is the Document Shepherd. 
    Token: Ralph Droms

  o draft-ietf-idr-rfc4893bis-07
    BGP Support for Four-octet AS Number Space (Proposed Standard)
    Note: John Scudder (jgs@juniper.net) is the document shepherd.
    Token: Stewart Bryant

  o draft-ietf-abfab-gss-eap-08
    A GSS-API Mechanism for the Extensible Authentication Protocol
    (Proposed Standard)
    Token: Stephen Farrell

  o draft-ietf-dnsext-dnssec-algo-imp-status-03
    Applicability Statement: DNS Security (DNSSEC) DNSKEY Algorithm
    Implementation Status (Best Current Practice)
    Note: Andrew Sullivan (ajs@anvilwalrusden.com) is the Document
    Shepherd
    Token: Ralph Droms

  o draft-ietf-dnsext-dnssec-registry-update-03
    DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry Updates
    (Proposed Standard)
    Note: Andrew Sullivan (ajs@anvilwalrusden.com) is the Document
    Shepherd
    Token: Ralph Droms

  o draft-ietf-appsawg-received-state-04
    Indicating Email Handling States in Trace Fields (Proposed Standard)
    Token: Barry Leiba

  o draft-ietf-pkix-caa-10
    DNS Certification Authority Authorization (CAA) Resource Record
    (Proposed Standard)
    Note: Steve Kent (kent@bbn.com) is the Document Shepherd.
    Token: Sean Turner

2.1.2 Returning Items

  NONE

2.2 Individual Submissions
2.2.1 New Items

  o draft-sandlund-rfc4996bis-02
    RObust Header Compression (ROHC): A Profile for TCP/IP (ROHC-TCP)
    (Proposed Standard)
    Token: Wesley Eddy

  o draft-camarillo-rai-media-policy-dataset-02
    A User Agent Profile Data Set for Media Policy (Proposed Standard)
    Note: Mary Barnes is the document shepherd
    Token: Robert Sparks

  o draft-farrell-decade-ni-09
    Naming Things with Hashes (Proposed Standard)
    Note: Alexey Melnikov (Alexey.Melnikov@isode.com) is the document
    shepherd.
    Token: Barry Leiba

2.2.2 Returning Items

  NONE

3. Document Actions
3.1 WG Submissions
3.1.1 New Items

  o draft-ietf-karp-threats-reqs-05
    Keying and Authentication for Routing Protocols (KARP) Overview,
    Threats, and Requirements (Informational)
    Note: Brian Weis (bew@cisco.com) is the document shepherd.
    Token: Stewart Bryant

  o draft-ietf-cdni-use-cases-09
    Use Cases for Content Delivery Network Interconnection
    (Informational)
    Note:  Francois Le Faucheur (flefauch@cisco.com) is the Document
    Shepherd.
    Token: Martin Stiemerling

  o draft-ietf-ippm-twamp-value-added-octets-04
    Ericsson TWAMP Value-Added Octets (Informational)
    Note: Henk Uijterwaal (henk@uijterwaal.nl) is the document shepherd.
    Token: Wesley Eddy

  o draft-ietf-oauth-urn-sub-ns-05
    An IETF URN Sub-Namespace for OAuth (Informational)
    Note: Derek Atkins (derek@ihtfp.com) is the document shepherd.
    Token: Stephen Farrell

3.1.2 Returning Items

  NONE

3.2 Individual Submissions Via AD
3.2.1 New Items

  o draft-claise-export-application-info-in-ipfix-09
    Cisco Systems Export of Application Information in IPFIX
    (Informational)
    Note: Individual Submission, AD-sponsored, Nevil Brownlee is the
    document shepherd, 
    Token: Ronald Bonica

  o draft-melnikov-smtp-priority-tunneling-03
    Tunneling of SMTP Message Transfer Priorities (Experimental)
    Token: Pete Resnick

  o draft-krishnan-nomcom-tools-01
    Requirements for IETF Nominations Committee tools (Informational)
    Token: Russ Housley

3.2.2 Returning Items

  NONE

3.3 IRTF and Independent Submission Stream Documents
3.3.1 New Items

  NONE

3.3.2 Returning Items

  NONE

3.3.3 For Action

  o draft-mme-trill-fcoe-02
    FCoE over TRILL (Informational)
    Note: ISE submission
    Token: Ralph Droms

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

  NONE
--------------090602040801030608060707--