Re: [tsvwg] TSVWG Status Report Oct 2009
"Michael Behringer (mbehring)" <mbehring@cisco.com> Fri, 16 October 2009 12:43 UTC
Return-Path: <mbehring@cisco.com>
X-Original-To: tsvwg@core3.amsl.com
Delivered-To: tsvwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A4DC3A67D8 for <tsvwg@core3.amsl.com>; Fri, 16 Oct 2009 05:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piItGOtRFHUX for <tsvwg@core3.amsl.com>; Fri, 16 Oct 2009 05:43:13 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 109D83A63D3 for <tsvwg@ietf.org>; Fri, 16 Oct 2009 05:43:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mbehring@cisco.com; l=18126; q=dns/txt; s=amsiport01001; t=1255696993; x=1256906593; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Michael=20Behringer=20(mbehring)"=20<mbehring@c isco.com>|Subject:=20RE:=20[tsvwg]=20TSVWG=20Status=20Rep ort=20Oct=202009|Date:=20Fri,=2016=20Oct=202009=2014:43:1 1=20+0200|Message-ID:=20<51865E1A72F61D48A247348DCCBA5CFB 5A8B1E@XMB-AMS-105.cisco.com>|To:=20<gorry@erg.abdn.ac.uk >,=20"tsvwg=20WG"=20<tsvwg@ietf.org>|Cc:=20"tsvwg=20chair "=20<tsvwg-chairs@tools.ietf.org>|MIME-Version:=201.0 |References:=20<4ACDED48.8030901@erg.abdn.ac.uk>; bh=XZysqwcZXTMuZMUj5MarGr00YYddCEVa/vjZIF780Ss=; b=ctAlkskxeE5FgF3TxeP84w30wgDTxOyg0aXm8EoZ9YJWT8mhwH5Oms4I wq7IUn6iKC+gEJyH04MAh2SWIh5bMceBZeTRPo+HMa6XXXnzviVgDe8/P STlW9ksn0waRmqzn8pqPm2ROtGN8J/cSk/jwn6hsOM30bpqCRuzhiDecw 8=;
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcAALsG2EqQ/uCWe2dsb2JhbACCJTGYQAEBFiQGpHeYKoQwBIFbiRk
X-IronPort-AV: E=Sophos; i="4.44,573,1249257600"; d="scan'208,217"; a="51988388"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 16 Oct 2009 12:43:11 +0000
Received: from xbh-ams-102.cisco.com (xbh-ams-102.cisco.com [144.254.73.132]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9GChBVn009282; Fri, 16 Oct 2009 12:43:11 GMT
Received: from xmb-ams-105.cisco.com ([144.254.74.80]) by xbh-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 16 Oct 2009 14:43:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA4E5E.388A5825"
Date: Fri, 16 Oct 2009 14:43:11 +0200
Message-ID: <51865E1A72F61D48A247348DCCBA5CFB5A8B1E@XMB-AMS-105.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tsvwg] TSVWG Status Report Oct 2009
Thread-Index: AcpIHdFY5UgGYprJQreCejkVM8Du0QGPuH1N
References: <4ACDED48.8030901@erg.abdn.ac.uk>
From: "Michael Behringer (mbehring)" <mbehring@cisco.com>
To: gorry@erg.abdn.ac.uk, tsvwg WG <tsvwg@ietf.org>
X-OriginalArrivalTime: 16 Oct 2009 12:43:11.0731 (UTC) FILETIME=[389EE430:01CA4E5E]
Cc: tsvwg chair <tsvwg-chairs@tools.ietf.org>
Subject: Re: [tsvwg] TSVWG Status Report Oct 2009
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2009 12:43:21 -0000
Gorry, Regarding -------------------------------------------- * draft-ietf-tsvwg-rsvp-security-groupkeying-05 (as INFO) Milestone: Nov 2009 - Submit 'Applicability of Keying Methods for RSVP Security' to IESG ACTION: Reviews Needed to say ready for WGLC Notes: Francois believes this is ready for WGLC. Ran Adkinson no longer has any objection to this. JP will shepherd. -------------------------------------------- I believe this status not to be correct. Please refer to http://tools.ietf.org/wg/tsvwg/minutes?item=minutes75.html " The WG will now take this to LC. People who have commented prior to WGLC please quickly re-read and confirm this is ready for publication. " My understanding from the last meeting was that: - the chairs would issue a WGLC (quite explicitly in the notes) - people who have commented before to quickly confirm that their concerns have been addressed. Please also refer to my mail to the list from 8 Sep http://www.ietf.org/mail-archive/web/tsvwg/current/msg09448.html Where I asked whether there are any open issues, and I was not told about any. So in my understanding the document should be in the section ================ WG Chair ACTION NEEDED ================ Could you please confirm this or correct my statements above? Thanks, Michael -----Original Message----- From: tsvwg-bounces@ietf.org on behalf of Gorry Fairhurst Sent: Thu 08-Oct-09 15:46 To: tsvwg WG Cc: tsvwg chair Subject: [tsvwg] TSVWG Status Report Oct 2009 I've summarised the list of drafts I know about in TSVWG and their current state. Please do take time to read this. If there are omissions or corrections, do let me know and I'll fix them. - If you are an author please do update your document before the deadline for the next IETF (not so many weeks from now!!) I see one document is even expired with pending comments! - If you have comments on these drafts, please let us know. If we are going to things completed by the milestones, we'll need people to comment on the documents and new revisions to be published. Best wishes, Gorry & James (as TSVWG Chairs) ======== TSVWG STATUS 8th OCT 2009 ======== ================ IESG Processing ================ * draft-ietf-tsvwg-rsvp-proxy-approaches-07 (as INFO) Notes: None. -------------------------------------------- * draft-ietf-tsvwg-rsvp-proxy-proto-09 (as PS) Notes: None. ================ WG Chair ACTION NEEDED ================ * draft-ietf-tsvwg-emergency-rsvp-12 (as PS) Status: In WGLC (Shepherd = Gorry Fairhurst) ACTION: WG Review reports, and notes of usefulness are needed. Notes: {WGLCTo end: 17th October 2009} 8th Oct - currently no nodes of support or comments. -------------------------------------------- * draft-ietf-tsvwg-port-randomization-04 (as BCP) Milestone: Nov 2009 - Submit 'Port Randomization for Transport Protocols' to the IESG Status: This ID is past WGLC. (Shepherd = James Polk) ACTION: JP to close the LC discussions and provide write-up. Notes: WGLC concluded April 15th New revision posted 3rd July - awaiting response by James Polk.= ================ With WG ================ * draft-ietf-tsvwg-admitted-realtime-dscp-05 (as PS) Status: This ID is past WGLC. (Shepherd = Magnus Westerlund) ACTION: Awaiting new revision by authors. Notes: JP to make final edits (based on Magnus' AD comments) -------------------------------------------- * draft-ietf-tsvwg-sctp-strrst-00 (as PS) ACTION: Awaiting new revision by authors. -------------------------------------------- * draft-ietf-tsvwg-rsvp-security-groupkeying-05 (as INFO) Milestone: Nov 2009 - Submit 'Applicability of Keying Methods for RSVP Security' to IESG ACTION: Reviews Needed to say ready for WGLC Notes: Francois believes this is ready for WGLC. Ran Adkinson no longer has any objection to this. JP will shepherd. -------------------------------------------- * draft-ietf-tsvwg-iana-ports-02 (as BCP) Milestone: Dec 2009 -'IANA Procedures for the Transport Protocol Port Number Space' ACTION: Awaiting new revision by authors. Notes: GF will shepherd. -------------------------------------------- * draft-ietf-tsvwg-sctpsocket-19 (as INFO) Milestone: Dec 2009 - 'Sockets API Extensions for SCTP' to IESG ACTION: Awaiting new revision by authors. Notes: Lacks a good IANA section, and security consideration. -------------------------------------------- * draft-ietf-tsvwg-ecn-tunnel-03 (as PS) Milestone: Jan 2010 - 'Layered Encapsulation of Congestion Notification' ACTION: Awaiting new revision by authors (WG Comments welcome) Notes: Substantial review of previous version. GF and David Black to confirm if issues raised were answered. New material needs review. -------------------------------------------- * draft-ietf-tsvwg-dtls-for-sctp-01 (as PS) Milestone: Dec 2009 - 'DTLS for SCTP' ACTION: Reviewers needed. Notes: Reviews needed to allow this to progress to LC. Authors think this is about ready for WGLC. -------------------------------------------- * draft-ietf-tsvwg-byte-pkt-congest (as INFO) Milestone: Feb 2010 - Request publication of 'Byte and Packet Congestion Notification' ACTION: Awaiting new revision by authors (WG Comments welcome) Notes: Comments received on rev 00, but no new revision. Current version has expired Feb 2009. Chairs need to know if author wishes to continue with a revised ID. ================ Individual Drafts ================ These drafts are ones that are being tracked, if you have a draft that you think is ready for WG comments please email the Chairs. -------------------------------------------- * draft-tuexen-sctp-udp-encaps-02 Notes: AD help requested to know what with encapsulation drafts. -------------------------------------------- * draft-fairhurst-6man-tsvwg-udptt-02 - The UDP Tunnel Transport mode Status: Individual Submission Notes: Presented at IETF-75 (Stockholm) to TSVWG and 6MAN. -------------------------------------------- * draft-tuexen-tsvwg-sctp-sack-immediately-02.txt Status: Individual Submission Notes: Presented at IETF-75 (Stockholm) to TSVWG -------------------------------------------- * draft-narayanan-tsvwg-rsvp-resource-sharing Status: Individual Submission Notes: Presented at IETF-75 (Stockholm) to TSVWG -------------------------------------------- * draft-lefaucheur-tsvwg-rsvp-multiple-preemption Status: Individual Submission Notes: Presented at IETF-75 (Stockholm) to TSVWG -------------------------------------------- draft-narayanan-tsvwg-rsvp-resource-sharing Status: Individual Submission Notes: Presented at IETF-75 (Stockholm) to TSVWG -------------------------------------------- * draft-adams-tsvwg-flow-signaling-identification-00 - Flow State Aware signalling standardisation, and a proposal for alerting nodes or end-systems on data related to a flow Status: Individual Submission, Not discussed by this group. Notes: None. -------------------------------------------- * draft-fairhurst-tsvwg-6man-udpzero-00 - IPv6 UDP Checksum Considerations Status: Individual Submission, Not discussed by this group. Notes: Linked to work in 6MAN, MBONED and LISP --------------------------------------------
- Re: [tsvwg] TSVWG Status Report Oct 2009 Francois Le Faucheur
- [tsvwg] TSVWG Status Report Oct 2009 Gorry Fairhurst
- Re: [tsvwg] TSVWG Status Report Oct 2009 Francois Le Faucheur
- Re: [tsvwg] TSVWG Status Report Oct 2009 Michael Behringer (mbehring)
- Re: [tsvwg] TSVWG Status Report Oct 2009 Francois Le Faucheur
- Re: [tsvwg] TSVWG Status Report Oct 2009 Francois Le Faucheur
- Re: [tsvwg] TSVWG Status Report Oct 2009 James M. Polk
- Re: [tsvwg] TSVWG Status Report Oct 2009 ken carlberg
- Re: [tsvwg] TSVWG Status Report Oct 2009 Brian Weis
- Re: [tsvwg] TSVWG Status Report Oct 2009 Francois Le Faucheur