Re: [IPFIX] draft-ietf-ipfix-export-per-sctp-stream version 1
"Juergen Quittek" <Quittek@nw.neclab.eu> Mon, 27 April 2009 08:44 UTC
Return-Path: <Quittek@nw.neclab.eu>
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1EDA3A6F5D for <ipfix@core3.amsl.com>; Mon, 27 Apr 2009 01:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 pEAyIz1CbNVe for <ipfix@core3.amsl.com>; Mon, 27 Apr 2009 01:44:56 -0700 (PDT)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id C56D73A6F51 for <ipfix@ietf.org>; Mon, 27 Apr 2009 01:44:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 349C22C0008EB; Mon, 27 Apr 2009 10:46:16 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wc0ckZbGVhvF; Mon, 27 Apr 2009 10:46:16 +0200 (CEST)
Received: from VENUS.office (mx2.office [192.168.24.15]) by smtp0.neclab.eu (Postfix) with ESMTP id EFAC22C000305; Mon, 27 Apr 2009 10:46:00 +0200 (CEST)
Received: from 10.1.2.178 ([10.1.2.178]) by VENUS.office ([192.168.24.102]) with Microsoft Exchange Server HTTP-DAV ; Mon, 27 Apr 2009 08:46:00 +0000
MIME-Version: 1.0
Content-class: urn:content-classes:message
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3323673958_17647250"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Mon, 27 Apr 2009 10:45:57 +0200
Message-ID: <C61B3D65.6B40F%Quittek@nw.neclab.eu>
In-Reply-To: <49F56456.3000506@cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: [IPFIX] draft-ietf-ipfix-export-per-sctp-stream version 1
Thread-Index: AcnHFJUCfRbFCR2KXE6EGbrwNNACgg==
From: Juergen Quittek <Quittek@nw.neclab.eu>
To: Benoit Claise <bclaise@cisco.com>, ipfix-chairs@tools.ietf.org
Cc: IETF IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [IPFIX] draft-ietf-ipfix-export-per-sctp-stream version 1
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2009 08:44:57 -0000
Dear Benoit,
Sorry, this is my fault. Also the session minutes are late.
I have time scheduled for these issues this week.
Juergen
On 27.04.09 09:52 "Benoit Claise" <bclaise@cisco.com> wrote:
> Dear IPFIX-chairs,
>
> Can we please progress this draft: this I-D was not yet submitted by the
> WG to the IESG.
> This draft has been untouched for 3 months, as there is nothing more to
> be done on the authors side.
>
> Regards, Benoit.
>> Dear all,
>>
>>> From the last IPFIX meeting minutes at
>> http://www.ietf.org/proceedings/08nov/minutes/ipfix.txt, there was
>> only a single concern regarding the
>> draft-ietf-ipfix-export-per-sctp-stream draft after the WGLC:
>>
>> - draft-ietf-ipfix-export-per-sctp-stream-00
>> ============================================
>> Benoit:
>> WGLC finished.
>> Clarifications on the interaction with RFC5101.
>> Only one opern issues left: There is a normative reference to
>> SCTP-RESET draft (draft-stewart-tsvwg-sctpstrrst-00.txt) from the
>> Transport WG. This ID describes allows the addition of streams within
>> an existing SCTP association as this functionality is required.
>>
>> Dan (AD):
>> This draft cannot be a normative reference as long as it is
>> not adopted by a the TSVWG. Suggestion: describe the mechanism in the
>> normative part of the text and add an informative reference to the
>> SCTP-RESET document. Once the document is included in the Transport WG
>> charter it can be used as a normative reference.
>>
>> Juergen:
>> Authors of draft-stewart-tsvwg-sctpstrrst-00.txt should review the
>> inserted text.
>>
>>
>> A new version of the draft has been posted, which addresses this
>> issue. Obviously the authors from
>> draft-stewart-tsvwg-sctpstrrst-00.txt were involved in the process.
>> This draft can now move to the next step towards RFC...
>>
>> Regards, Benoit.
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> IPFIX mailing list
>> IPFIX@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipfix
>>
>
- [IPFIX] draft-ietf-ipfix-export-per-sctp-stream v… Benoit Claise
- Re: [IPFIX] draft-ietf-ipfix-export-per-sctp-stre… Benoit Claise
- Re: [IPFIX] draft-ietf-ipfix-export-per-sctp-stre… Juergen Quittek