Re: [tsvwg] TSVWG Status Report Oct 2009

Francois Le Faucheur <flefauch@cisco.com> Thu, 05 November 2009 18:55 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 B523828C0F3 for <tsvwg@core3.amsl.com>; Thu, 5 Nov 2009 10:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.435
X-Spam-Level:
X-Spam-Status: No, score=-10.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 OOWBQ9lR-xxL for <tsvwg@core3.amsl.com>; Thu, 5 Nov 2009 10:55:21 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id CC49B3A68ED for <tsvwg@ietf.org>; Thu, 5 Nov 2009 10:55:20 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.44,687,1249257600"; d="scan'208";a="53741520"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 05 Nov 2009 18:55:40 +0000
Received: from [144.254.53.136] ([144.254.53.136]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id nA5ItdFu003965; Thu, 5 Nov 2009 18:55:39 GMT
References: <4ACDED48.8030901@erg.abdn.ac.uk> <51865E1A72F61D48A247348DCCBA5CFB5A8B1E@XMB-AMS-105.cisco.com> <11A12A19-3F02-453C-9104-9BA96D5ED2C1@cisco.com> <32CF1043-84E3-4EA9-B836-8F03657CA25A@cisco.com>
In-Reply-To: <32CF1043-84E3-4EA9-B836-8F03657CA25A@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
Message-Id: <BD962917-8B5B-434F-A5CF-624C2C25CDDB@cisco.com>
Content-Transfer-Encoding: 7bit
From: Francois Le Faucheur <flefauch@cisco.com>
Date: Thu, 05 Nov 2009 19:55:39 +0100
To: Francois Le Faucheur <flefauch@cisco.com>
X-Mailer: Apple Mail (2.1076)
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "James (jmpolk) Polk" <jmpolk@cisco.com>, tsvwg WG <tsvwg@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: Thu, 05 Nov 2009 18:55:22 -0000

Hello Gorry, James,

Any comments on why this document is not going for Last Call as  
(apparently) agreed 4 months ago?

Francois

On 26 Oct 2009, at 19:14, Francois Le Faucheur wrote:

> Gorry, James,
>
> Any comments on why this document is not going for Last Call as  
> (apparently) agreed 3.5 months ago?
>
> Thanks
>
> Francois
>
> On 16 Oct 2009, at 15:04, Francois Le Faucheur wrote:
>
>> Gorry, James,
>>
>> Independently of getting the Status Report corrected, my  
>> understanding is that draft-ietf-tsvwg-rsvp-security-groupkeying  
>> has been declared ready to go to WGLC 3 months ago as per the  
>> Stockholm meeting minutes. Could you please:
>> 	(i) either issue the Last Call
>> 	(ii) or let us know if there are outstanding thing sin the way.
>>
>> Thanks
>>
>> Francois
>>
>> On 16 Oct 2009, at 14:43, Michael Behringer (mbehring) wrote:
>>
>>> 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
>>>
>>> --------------------------------------------
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>