Re: [tsvwg] TSVWG Status Report Oct 2009
Francois Le Faucheur <flefauch@cisco.com> Mon, 26 October 2009 18:21 UTC
Return-Path: <flefauch@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 ACC0A3A69A0 for <tsvwg@core3.amsl.com>; Mon, 26 Oct 2009 11:21:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.368
X-Spam-Level:
X-Spam-Status: No, score=-10.368 tagged_above=-999 required=5 tests=[AWL=0.231, BAYES_00=-2.599, 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 ImiIZJBBDmJL for <tsvwg@core3.amsl.com>; Mon, 26 Oct 2009 11:21:26 -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 0A3263A6996 for <tsvwg@ietf.org>; Mon, 26 Oct 2009 11:21:25 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.44,627,1249257600"; d="scan'208";a="52810501"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 26 Oct 2009 18:21:38 +0000
Received: from ams-flefauch-8716.cisco.com (ams-flefauch-8716.cisco.com [10.55.161.199]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9QILbIM016946; Mon, 26 Oct 2009 18:21:37 GMT
References: <4ACDED48.8030901@erg.abdn.ac.uk>
In-Reply-To: <4ACDED48.8030901@erg.abdn.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Message-Id: <823CC247-BA7F-49E5-8334-AC6D00A2A809@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur <flefauch@cisco.com>
Date: Mon, 26 Oct 2009 19:21:33 +0100
To: gorry@erg.abdn.ac.uk
X-Mailer: Apple Mail (2.1076)
Cc: tsvwg WG <tsvwg@ietf.org>, 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: Mon, 26 Oct 2009 18:21:27 -0000
Hello Gorry, Could you comment on draft-ietf-rsvp-l3vpn? The TSWG charter page (http://www.ietf.org/dyn/wg/charter/tsvwg-charter.html ) says: "Done Request publication of 'Support for RSVP in Layer 3 VPNs' as Proposed Standard RFC" However, the I-D Tracker had a state of "New Version Needed". I believe this is because with had a few comments from the IESG review. So I posted a new version addressing those comments. Should the document now be resubmitted to IESG? Thanks Francois On 8 Oct 2009, at 15:46, Gorry Fairhurst wrote: > > 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