IETF Logo Mail Archive

Re: [Rmt] Mail regarding draft-ietf-rmt-flute-revised

"Luby, Michael" <luby@qualcomm.com> Sat, 30 October 2010 00:07 UTC

Return-Path: <luby@qualcomm.com>
X-Original-To: rmt@core3.amsl.com
Delivered-To: rmt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F08A43A68BB; Fri, 29 Oct 2010 17:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 lnHqdmiLO7Hk; Fri, 29 Oct 2010 17:07:39 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id BC41D3A63D2; Fri, 29 Oct 2010 17:07:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=luby@qualcomm.com; q=dns/txt; s=qcdkim; t=1288397375; x=1319933375; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:user-agent: acceptlanguage:content-type:content-transfer-encoding: mime-version; z=From:=20"Luby,=20Michael"=20<luby@qualcomm.com>|To:=20Da vid=20Harrington=20<ietfdbh@comcast.net>,=0D=0A=09"draft- ietf-rmt-flute-revised@tools.ietf.org"=0D=0A=09<draft-iet f-rmt-flute-revised@tools.ietf.org>|CC:=20"rmt-chairs@iet f.org"=20<rmt-chairs@ietf.org>,=20"rmt@ietf.org"=20<rmt@i etf.org>|Date:=20Fri,=2029=20Oct=202010=2017:09:25=20-070 0|Subject:=20Re:=20Mail=20regarding=20draft-ietf-rmt-flut e-revised|Thread-Topic:=20Mail=20regarding=20draft-ietf-r mt-flute-revised|Thread-Index:=20ActTlmyw+TM6/ERiSImH60Xo 0dHE0AkMElDB|Message-ID:=20<C8F0B045.6045%luby@qualcomm.c om>|In-Reply-To:=20<2FE1F2A66E7B4B28BDFC601B9352C244@23FX 1C1>|Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|user-agent:=20Mic rosoft-Entourage/13.7.0.100913|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0; bh=A9QgeGR0Z6x3Vz2A1/2XuO2cRsB/G/bfP54K2vmrzDc=; b=ARrSQu1mkJTXAQQjSoBjjNAhpYk3Del1apoSp39d+rbPPi5sPYk0LDxI kKJ3LM2LcM56qLrclqve5OWlPdzZ3PqXUyTbIP/sx1OsyrvsnDbkebPhF q25n5Lk3aVrCf98n4DfLhbeRjdY31a3TRMzgUwpJTqN01X9o1Xh2CNfhZ g=;
X-IronPort-AV: E=McAfee;i="5400,1158,6151"; a="59861531"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 29 Oct 2010 17:09:28 -0700
X-IronPort-AV: E=Sophos;i="4.58,260,1286175600"; d="scan'208";a="24372674"
Received: from nasanexhub05.na.qualcomm.com ([129.46.134.219]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-MD5; 29 Oct 2010 17:09:27 -0700
Received: from nasclexhc02.na.qualcomm.com (10.227.147.13) by nasanexhub05.na.qualcomm.com (129.46.134.219) with Microsoft SMTP Server (TLS) id 8.3.83.0; Fri, 29 Oct 2010 17:09:27 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc02.na.qualcomm.com ([10.227.147.13]) with mapi; Fri, 29 Oct 2010 17:09:19 -0700
From: "Luby, Michael" <luby@qualcomm.com>
To: David Harrington <ietfdbh@comcast.net>, "draft-ietf-rmt-flute-revised@tools.ietf.org" <draft-ietf-rmt-flute-revised@tools.ietf.org>
Date: Fri, 29 Oct 2010 17:09:25 -0700
Thread-Topic: Mail regarding draft-ietf-rmt-flute-revised
Thread-Index: ActTlmyw+TM6/ERiSImH60Xo0dHE0AkMElDB
Message-ID: <C8F0B045.6045%luby@qualcomm.com>
In-Reply-To: <2FE1F2A66E7B4B28BDFC601B9352C244@23FX1C1>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.7.0.100913
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rmt-chairs@ietf.org" <rmt-chairs@ietf.org>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [Rmt] Mail regarding draft-ietf-rmt-flute-revised
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2010 00:07:41 -0000

Hi David, 
Yes, you are correct, this should be pushed forward.  I think the only
remaining issue is whether the FLUTE version number should be incremented
due to backwards compatibility issues, or some argumentation saying that a
version increment is not necessary because the backwards compatibility
issues are not there or not significant enough to justify.  Is there any
consensus on this final issue at this time?  Anybody want to provide
argumentation that we can justifiably keep this as version 1 (same as the
deprecated RFC3926), or should we just go along with the IESG request to
make this Version 2?   We need to push this forward and complete the work.
Mike




On 9/13/10 3:53 PM, "David Harrington" <ietfdbh@comcast.net> wrote:

> Hi,
> 
> Where are we with this document?
> I asked for an updated version number back in July.
> I'm not seeing much discussion on the ML.
> When can I expect a new revision that addresses the backwards
> compatibility issue?
> 
> David Harrington
> Director, IETF Transport Area
> ietfdbh@comcast.net (preferred for ietf)
> dbharrington@huaweisymantec.com
> +1 603 828 1401 (cell)
>

v2.23.0 | Report a Bug | By Email