
From magnus.westerlund@ericsson.com  Wed Apr  1 05:31:48 2009
Return-Path: <magnus.westerlund@ericsson.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 87BD828C2D4 for <rmt@core3.amsl.com>; Wed,  1 Apr 2009 05:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.172
X-Spam-Level: 
X-Spam-Status: No, score=-6.172 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 5jVBNRxeUF6F for <rmt@core3.amsl.com>; Wed,  1 Apr 2009 05:31:47 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 92CC128C2B2 for <rmt@ietf.org>; Wed,  1 Apr 2009 05:13:47 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 18010220F9; Wed,  1 Apr 2009 14:14:00 +0200 (CEST)
X-AuditID: c1b4fb3e-aafb3bb000006d6d-3a-49d35a4f256f
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 97CB1221FC; Wed,  1 Apr 2009 14:13:03 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 1 Apr 2009 14:09:19 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 1 Apr 2009 14:09:18 +0200
Message-ID: <49D3596E.1060008@ericsson.com>
Date: Wed, 01 Apr 2009 14:09:18 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: draft-ietf-rmt-bb-lct-revised@tools.ietf.org
References: <20090328004502.0844C3A68CE@core3.amsl.com> <49D294F0.5000008@roundbox.com>
In-Reply-To: <49D294F0.5000008@roundbox.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 01 Apr 2009 12:09:18.0454 (UTC) FILETIME=[AEE6F160:01C9B2C2]
X-Brightmail-Tracker: AAAAAA==
Cc: rmt@ietf.org
Subject: Re: [Rmt] I-D Action:draft-ietf-rmt-bb-lct-revised-09.txt
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: Wed, 01 Apr 2009 12:31:48 -0000

Authors,

take this as comment as an IETF last call comment. I have just initiated
the last call process so don't submit a new version until after the ietf
last call has ended.

Best Regards

Magnus

Igor Slepchin skrev:
> In section 5.2.1 the last sentence in the last paragraph before the
> header extension format diagram says:
> 
> "The second format is used for fixed length (one 32-bit word)
> extensions, using HET values from 127 to 255."
> 
> It should say "using HET values from 128 to 255."
> 
> Thank you,
> Igor Slepchin
> 
> Internet-Drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the Reliable Multicast Transport Working
>> Group of the IETF.
>>
>>
>>     Title           : Layered Coding Transport (LCT) Building Block
>>     Author(s)       : M. Luby, et al.
>>     Filename        : draft-ietf-rmt-bb-lct-revised-09.txt
>>     Pages           : 40
>>     Date            : 2009-03-27
>>
>> Layered Coding Transport (LCT) provides transport level support for
>> reliable content delivery and stream delivery protocols.  LCT is
>> specifically designed to support protocols using IP multicast, but
>> also provides support to protocols that use unicast.  LCT is
>> compatible with congestion control that provides multiple rate
>> delivery to receivers and is also compatible with coding techniques
>> that provide reliable delivery of content.  This document obsoletes
>> RFC3451
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-lct-revised-09.txt
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> Below is the data which will enable a MIME compliant mail reader
>> implementation to automatically retrieve the ASCII version of the
>> Internet-Draft.
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Rmt mailing list
>> Rmt@ietf.org
>> https://www.ietf.org/mailman/listinfo/rmt
> 
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www.ietf.org/mailman/listinfo/rmt
> 


-- 

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From wwwrun@core3.amsl.com  Wed Apr  1 07:26:35 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: rmt@ietf.org
Delivered-To: rmt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 2196C3A6A1C; Wed,  1 Apr 2009 07:26:35 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090401142635.2196C3A6A1C@core3.amsl.com>
Date: Wed,  1 Apr 2009 07:26:35 -0700 (PDT)
Cc: rmt@ietf.org
Subject: [Rmt] Last Call: draft-ietf-rmt-bb-lct-revised (Layered Coding Transport (LCT) Building Block) to Proposed Standard
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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: Wed, 01 Apr 2009 14:26:35 -0000

The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:

- 'Layered Coding Transport (LCT) Building Block '
   <draft-ietf-rmt-bb-lct-revised-09.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-04-15. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rmt-bb-lct-revised-09.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13401&rfc_flag=0

The following IPR Declarations may be related to this I-D:




From magnus.westerlund@ericsson.com  Thu Apr  2 00:37:13 2009
Return-Path: <magnus.westerlund@ericsson.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 5BA8F3A6C8F for <rmt@core3.amsl.com>; Thu,  2 Apr 2009 00:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.527
X-Spam-Level: 
X-Spam-Status: No, score=-5.527 tagged_above=-999 required=5 tests=[AWL=-0.570, BAYES_00=-2.599, HELO_EQ_SE=0.35, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
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 ZcYOAfbuPl2x for <rmt@core3.amsl.com>; Thu,  2 Apr 2009 00:37:12 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id E07763A6A35 for <rmt@ietf.org>; Thu,  2 Apr 2009 00:37:11 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 71AFA20E54; Thu,  2 Apr 2009 09:37:59 +0200 (CEST)
X-AuditID: c1b4fb3c-ac794bb0000004b9-74-49d46b4c0c05
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 35208205C1; Thu,  2 Apr 2009 09:37:48 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 2 Apr 2009 09:36:06 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 2 Apr 2009 09:36:06 +0200
Message-ID: <49D46AE6.7020500@ericsson.com>
Date: Thu, 02 Apr 2009 09:36:06 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
References: <RT-Ticket-228671@icann.org>	<20090310144451.206183A6B26@core3.amsl.com> <rt-3.8.3pre1-466-1238524452-1151.228671-7-0@icann.org>
In-Reply-To: <rt-3.8.3pre1-466-1238524452-1151.228671-7-0@icann.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 02 Apr 2009 07:36:06.0521 (UTC) FILETIME=[AEF63690:01C9B365]
X-Brightmail-Tracker: AAAAAA==
Cc: rmt-chairs@tools.ietf.org, adamson@itd.nrl.navy.mil, M.Handley@cs.ucl.ac.uk, "rmt@ietf.org" <rmt@ietf.org>, cabo@tzi.org, macker@itd.nrl.navy.mil
Subject: Re: [Rmt] [IANA #228671] Last Call: draft-ietf-rmt-pi-norm-revised	(NACK-Oriented Reliable Multicast Protocol) to Proposed Standard
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: Thu, 02 Apr 2009 07:37:13 -0000

Hi,

For information, the only IETF last call comment on the NORM PI that I
have seen was these IANA questions. I expect the authors to respond to
these before progressing to IESG evaluation.

Magnus

Amanda Baber via RT skrev:
> IESG:
> 
> IANA has the following questions and comments regarding 
> draft-ietf-rmt-pi-norm-revised-09.txt: 
> 
> - Where is the registry where we need to define "ietf:rmt:norm"?
> 
> - Can you verify that value 0 is available for assignment?
> 
> - For extensibility purposes do you want to create registries for
> your various NORM Commands and Command Messages?
> 
> - The EXT_AUTH extention is not mentioned until the Security
> Considerations in Section 6 and never fully defined. Even though
> that section says it's out of scope, it's probably not appropriate
> to define it there.
> 
> Upon approval of this document, IANA will create the following registry at
> http://www.iana.org/assignments/rmt-fec-parameters
> 
> Registry Name: NORM Header Extension Types
> ietf:rmt:norm:extensions
> Registration Procedures: Specification Required
> 
> Initial contents of this sub-registry will be:
> 
> +-------+------------+-----------------------------+
> | Value | Name | Reference |
> +-------+------------+-----------------------------+
> | 0 | Available | [RFC-rmt-pi-norm-revised-09 |
> | 1 | "EXT_AUTH" | [RFC-rmt-pi-norm-revised-09 |
> | 2 | Available | [RFC-rmt-pi-norm-revised-09 |
> | 3 | "EXT_CC" | [RFC-rmt-pi-norm-revised-09 |
> | 4-63 | Available | [RFC-rmt-pi-norm-revised-09 |
> | 64 | "EXT_FTI" | [RFC-rmt-pi-norm-revised-09 |
> | 65-127| Available | [RFC-rmt-pi-norm-revised-09 |
> | 128 | "EXT_RATE" | [RFC-rmt-pi-norm-revised-09 |
> |129-255| Available | [RFC-rmt-pi-norm-revised-09 |
> +-------+------------+-----------------------------+
> 
> We understand the above to be the only IANA Action for this document.
> 
> Thank you.
> 
> Amanda Baber
> (on behalf of IANA)
> 
>> The IESG has received a request from the Reliable Multicast Transport
>> WG
>> (rmt) to consider the following document:
>>
>> - 'NACK-Oriented Reliable Multicast Protocol '
>>    <draft-ietf-rmt-pi-norm-revised-09.txt> as a Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action.  Please send substantive comments to
>> the
>> ietf@ietf.org mailing lists by 2009-03-31. Exceptionally,
>> comments may be sent to iesg@ietf.org instead. In either case, please
>> retain the beginning of the Subject line to allow automated sorting.
>>
>> The file can be obtained via
>> http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-revised-
>> 09.txt
>>
>>
>> IESG discussion can be tracked via
>>
> https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13806&rfc_flag=0
>> The following IPR Declarations may be related to this I-D:
>>
>>
> 
> 
> 
> 


-- 

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From watson@qualcomm.com  Thu Apr  9 11:31:57 2009
Return-Path: <watson@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 F36973A6C03 for <rmt@core3.amsl.com>; Thu,  9 Apr 2009 11:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.382
X-Spam-Level: 
X-Spam-Status: No, score=-105.382 tagged_above=-999 required=5 tests=[AWL=1.216, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 dyjJd53joUO9 for <rmt@core3.amsl.com>; Thu,  9 Apr 2009 11:31:52 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id B97723A6C63 for <rmt@ietf.org>; Thu,  9 Apr 2009 11:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=watson@qualcomm.com; q=dns/txt; s=qcdkim; t=1239301910; x=1270837910; h=from:to:date:subject:thread-topic:thread-index: message-id:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Watson,=20Mark"=20<watson@qualcomm.com>|To:=20" rmt@ietf.org"=20<rmt@ietf.org>|Date:=20Thu,=209=20Apr=202 009=2011:31:30=20-0700|Subject:=20Comment=20on=20LCT=20dr aft|Thread-Topic:=20Comment=20on=20LCT=20draft |Thread-Index:=20Acm5QWZ5JZlBmyO5CUmq5fohqap5/A=3D=3D |Message-ID:=20<C6038D12.2C65F%watson@qualcomm.com> |Accept-Language:=20en-US|Content-Language:=20en |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C6038D122C65Fwatsonqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5579"=3B=20a=3D"17024052"; bh=1gp+chEJ999Tu+UEc+6Y4mEQ6x4VEJmiDkfcdweqd8Y=; b=ToF59LzcAomjWGmadAO4wmJvdHWpoaeHIBzyEyAlJXC5+BgFxZwUalgB j2UxBqC9cH0E6RuZl6wxvDj2mI2rvX3NCWtPYzFA17f72I6hL6Ly2+FXd Z7E/z0GCXWcRUA3zkLSHk1OGf3CctgSCc6Je2aXnAZbgzLPWhkDvc9Epw 0=;
X-IronPort-AV: E=McAfee;i="5300,2777,5579"; a="17024052"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Apr 2009 11:31:34 -0700
Received: from msgtransport01.qualcomm.com (msgtransport01.qualcomm.com [129.46.61.148]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n39IVYTM004725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rmt@ietf.org>; Thu, 9 Apr 2009 11:31:34 -0700
Received: from nasanexhub03.na.qualcomm.com (nasanexhub03.na.qualcomm.com [10.46.93.98]) by msgtransport01.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n39IVXB9025283 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rmt@ietf.org>; Thu, 9 Apr 2009 11:31:34 -0700
Received: from nasclexhc01.na.qualcomm.com (10.227.147.14) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.1.340.0; Thu, 9 Apr 2009 11:31:33 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Thu, 9 Apr 2009 11:31:32 -0700
From: "Watson, Mark" <watson@qualcomm.com>
To: "rmt@ietf.org" <rmt@ietf.org>
Date: Thu, 9 Apr 2009 11:31:30 -0700
Thread-Topic: Comment on LCT draft
Thread-Index: Acm5QWZ5JZlBmyO5CUmq5fohqap5/A==
Message-ID: <C6038D12.2C65F%watson@qualcomm.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C6038D122C65Fwatsonqualcommcom_"
MIME-Version: 1.0
Subject: [Rmt] Comment on LCT draft
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: Thu, 09 Apr 2009 18:31:57 -0000

--_000_C6038D122C65Fwatsonqualcommcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

All,

I received the following comment in the IESG Last Call for LCT:

"Section 5.2.2 specifies an overloading of the ERT flag and ERT field:

|  Expected Residual Time (ERT): ERT flag, corresponding 32 bit time
|  value
|
|     This timing information represents the sender expected residual
|     transmission time for the current session or for the transmission
|     of the current object.  If the packet containing the ERT timing
|     information also contains the TOI field, then ERT refers to the
|     object corresponding to the TOI field, otherwise it refers to the
|     session.

This overloading seems to be potentially dangerous; it prematurely
excludes the possibility to specify a session ERT value whenever
a session carries multiple objects and hence needs to make use of
TOI in every packet.
Wouldn't it be a more clean solution to spent another bit and
optional field, to achieve a clean separation of both Object ERT
and Session ERT ?"

This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional "Expected Session Residual Time" field. However I was not invol=
ved in any of the original discussions on the EXT_TIME header, so I would l=
ike to know if there are any comments on this from those that were (or inde=
ed anyone else).

...Mark



--_000_C6038D122C65Fwatsonqualcommcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Comment on LCT draft</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>All,<BR>
<BR>
I received the following comment in the IESG Last Call for LCT:<BR>
<BR>
&#8220;Section 5.2.2 specifies an overloading of the ERT flag and ERT field=
:<BR>
<BR>
| &nbsp;Expected Residual Time (ERT): ERT flag, corresponding 32 bit time<B=
R>
| &nbsp;value<BR>
|<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;This timing information represents the sender exp=
ected residual<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;transmission time for the current session or for =
the transmission<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;of the current object. &nbsp;If the packet contai=
ning the ERT timing<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;information also contains the TOI field, then ERT=
 refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;object corresponding to the TOI field, otherwise =
it refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;session.<BR>
<BR>
This overloading seems to be potentially dangerous; it prematurely<BR>
excludes the possibility to specify a session ERT value whenever<BR>
a session carries multiple objects and hence needs to make use of<BR>
TOI in every packet.<BR>
Wouldn't it be a more clean solution to spent another bit and<BR>
optional field, to achieve a clean separation of both Object ERT<BR>
and Session ERT ?&#8221;<BR>
<BR>
This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional &#8220;Expected Session Residual Time&#8221; field. However I w=
as not involved in any of the original discussions on the EXT_TIME header, =
so I would like to know if there are any comments on this from those that w=
ere (or indeed anyone else).<BR>
<BR>
...Mark <BR>
<BR>
<BR>
</SPAN></FONT>
</BODY>
</HTML>


--_000_C6038D122C65Fwatsonqualcommcom_--

From luby@qualcomm.com  Fri Apr 10 10:20:34 2009
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 B9CCE3A6928 for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:20:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.851
X-Spam-Level: 
X-Spam-Status: No, score=-105.851 tagged_above=-999 required=5 tests=[AWL=0.747, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 r0WSVbZ1M5Cd for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:20:27 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id F2DAB3A63EB for <rmt@ietf.org>; Fri, 10 Apr 2009 10:20:26 -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=1239384096; x=1270920096; 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:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Luby,=20Michael"=20<luby@qualcomm.com>|To:=20"W atson,=20Mark"=20<watson@qualcomm.com>,=20"rmt@ietf.org" =20<rmt@ietf.org>|CC:=20"Luby,=20Michael"=20<luby@qualcom m.com>|Date:=20Fri,=2010=20Apr=202009=2010:21:14=20-0700 |Subject:=20Re:=20[Rmt]=20Comment=20on=20LCT=20draft |Thread-Topic:=20[Rmt]=20Comment=20on=20LCT=20draft |Thread-Index:=20Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5o |Message-ID:=20<C604CE1A.21C2%luby@qualcomm.com> |In-Reply-To:=20<C6038D12.2C65F%watson@qualcomm.com> |Accept-Language:=20en-US|Content-Language:=20en |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C604CE1A21C2lubyqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5579"=3B=20a=3D"17052615"; bh=Xt3i9f2CUfzKxKft8YXuP7QTNe+2zWnOittQP1E3BjI=; b=SJkorNEMPEM5bv7P1iacSjefjBbwKcubYT0pJJtH5YooxOATUt+U7FJZ gt/vaPycytzYF+FaoNlZhr3BXGVWCkmYBV65FUFQBgV63903Psrwh+4sy OtLCg+kMye8u+m3aohBJcfBJcWz6cJO6Ro4C7jf8IWgFn74puArGY/dHb w=;
X-IronPort-AV: E=McAfee;i="5300,2777,5579"; a="17052615"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2009 10:21:20 -0700
Received: from totoro.qualcomm.com (totoro.qualcomm.com [129.46.61.158]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHLKkR029371 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:21:20 -0700
Received: from nasanexhub06.na.qualcomm.com (nasanexhub06.na.qualcomm.com [129.46.134.254]) by totoro.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHLJZh029415 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:21:20 -0700 (PDT)
Received: from nasclexhc01.na.qualcomm.com (10.227.147.14) by nasanexhub06.na.qualcomm.com (129.46.134.254) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 10 Apr 2009 10:21:19 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Fri, 10 Apr 2009 10:21:18 -0700
From: "Luby, Michael" <luby@qualcomm.com>
To: "Watson, Mark" <watson@qualcomm.com>, "rmt@ietf.org" <rmt@ietf.org>
Date: Fri, 10 Apr 2009 10:21:14 -0700
Thread-Topic: [Rmt] Comment on LCT draft
Thread-Index: Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5o
Message-ID: <C604CE1A.21C2%luby@qualcomm.com>
In-Reply-To: <C6038D12.2C65F%watson@qualcomm.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C604CE1A21C2lubyqualcommcom_"
MIME-Version: 1.0
Cc: "Luby, Michael" <luby@qualcomm.com>
Subject: Re: [Rmt] Comment on LCT draft
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: Fri, 10 Apr 2009 17:20:34 -0000

--_000_C604CE1A21C2lubyqualcommcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

There is less ambiguity than one might think with this (perhaps no ambiguit=
y).  If you read the section about the TOI you will see that the TOI field =
MUST be used in all packets if more than one object is to be transmitted in=
 the session, i.e., the TOI field is either present in all the packets of a=
 session or is never present.  Given this, the ERT within a session is esse=
ntially always the end of the transmission of the current object:

(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.
(2) if there is only one object in the session
    (a) if the TOI is used for the object then the ERT is the end time of t=
ransmission of that object.
    (b) if the TOI is not used then the ERT is the end time of transmission=
 of the session, which presumably is the end time of transmission of that o=
bject.

It seems that  the only ambiguity is if there is one object in the session =
and some of the packets for that object carry the TOI and others don't (thi=
s does not seem disallowed by the MUST, despite the "i.e. ..." statement wh=
ich says it is not allowed).  In this case, it still seems that the ERT wil=
l always refer to the end time of the transmission of that object/session (=
they should be the same).  But, perhaps this could be clarified by includin=
g language that says that for a particular object the TOI must be in all pa=
ckets pertaining to that object or the TOI must not be in all packets perta=
ining to that object (this seems like a good restriction for other reasons =
as well, i.e., it is the natural way to do this and to do something differe=
nt in the case of transmission of one object seems pretty nonsensical, and =
the "i.e. ... " statement says this is true as well, even if it doesn't log=
ically follow from the MUST).

Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.

So, a concrete suggestion:

Change: The
         TOI field MUST be used in all packets if more than one object
         is to be transmitted in a session, i.e. the TOI field is either
         present in all the packets of a session or is never present.

To: The
         TOI field MUST be used in all packets in a session or none of the =
packets in a session.
         The TOI field MUST be used in all packets in a session if more tha=
n one object
         is to be transmitted in a session.

Change:  Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the current session or for the transmission of the
         current object, measured in units of 1ms.  If the packet
         containing the ERT field also contains the TOI field, then ERT
         refers to the object corresponding to the TOI field, otherwise
         it refers to the session.

To: Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the transmission of the current object, measured in units=
 of 1ms.

Mike


On 4/9/09 11:31 AM, "Watson, Mark" <watson@qualcomm.com> wrote:

All,

I received the following comment in the IESG Last Call for LCT:

"Section 5.2.2 specifies an overloading of the ERT flag and ERT field:

|  Expected Residual Time (ERT): ERT flag, corresponding 32 bit time
|  value
|
|     This timing information represents the sender expected residual
|     transmission time for the current session or for the transmission
|     of the current object.  If the packet containing the ERT timing
|     information also contains the TOI field, then ERT refers to the
|     object corresponding to the TOI field, otherwise it refers to the
|     session.

This overloading seems to be potentially dangerous; it prematurely
excludes the possibility to specify a session ERT value whenever
a session carries multiple objects and hence needs to make use of
TOI in every packet.
Wouldn't it be a more clean solution to spent another bit and
optional field, to achieve a clean separation of both Object ERT
and Session ERT ?"

This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional "Expected Session Residual Time" field. However I was not invol=
ved in any of the original discussions on the EXT_TIME header, so I would l=
ike to know if there are any comments on this from those that were (or inde=
ed anyone else).

...Mark




--_000_C604CE1A21C2lubyqualcommcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Rmt] Comment on LCT draft</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>There is less ambiguity than one might think with this (perhaps no am=
biguity). &nbsp;If you read the section about the TOI you will see that the=
 TOI field MUST be used in all packets if more than one object is to be tra=
nsmitted in the session, i.e., the TOI field is either present in all the p=
ackets of a session or is never present. &nbsp;Given this, the ERT within a=
 session is essentially always the end of the transmission of the current o=
bject:<BR>
<BR>
(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.<BR=
>
(2) if there is only one object in the session<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(a) if the TOI is used for the object then the ERT =
is the end time of transmission of that object.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(b) if the TOI is not used then the ERT is the end =
time of transmission of the session, which presumably is the end time of tr=
ansmission of that object.<BR>
<BR>
It seems that &nbsp;the only ambiguity is if there is one object in the ses=
sion and some of the packets for that object carry the TOI and others don&#=
8217;t (this does not seem disallowed by the MUST, despite the &#8220;i.e. =
...&#8221; statement which says it is not allowed). &nbsp;In this case, it =
still seems that the ERT will always refer to the end time of the transmiss=
ion of that object/session (they should be the same). &nbsp;But, perhaps th=
is could be clarified by including language that says that for a particular=
 object the TOI must be in all packets pertaining to that object or the TOI=
 must not be in all packets pertaining to that object (this seems like a go=
od restriction for other reasons as well, i.e., it is the natural way to do=
 this and to do something different in the case of transmission of one obje=
ct seems pretty nonsensical, and the &#8220;i.e. ... &#8220; statement says=
 this is true as well, even if it doesn&#8217;t logically follow from the M=
UST).<BR>
<BR>
Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.<BR>
<BR>
So, a concrete suggestion:<BR>
<BR>
Change: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session, i.e. the TOI field is either<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;present in all the pa=
ckets of a session or is never present.<BR>
<BR>
To: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets in a session or none of the packets in a session.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The TOI field MUST be=
 used in all packets in a session if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session.<BR>
<BR>
Change: &nbsp;Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the current =
session or for the transmission of the<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;current object, measu=
red in units of 1ms. &nbsp;If the packet<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;containing the ERT fi=
eld also contains the TOI field, then ERT<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;refers to the object =
corresponding to the TOI field, otherwise<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;it refers to the sess=
ion.<BR>
<BR>
To: Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the transmis=
sion of the current object, measured in units of 1ms.<BR>
<BR>
Mike<BR>
<BR>
<BR>
On 4/9/09 11:31 AM, &quot;Watson, Mark&quot; &lt;<a href=3D"watson@qualcomm=
.com">watson@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>All,<BR>
<BR>
I received the following comment in the IESG Last Call for LCT:<BR>
<BR>
&#8220;Section 5.2.2 specifies an overloading of the ERT flag and ERT field=
:<BR>
<BR>
| &nbsp;Expected Residual Time (ERT): ERT flag, corresponding 32 bit time<B=
R>
| &nbsp;value<BR>
|<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;This timing information represents the sender exp=
ected residual<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;transmission time for the current session or for =
the transmission<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;of the current object. &nbsp;If the packet contai=
ning the ERT timing<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;information also contains the TOI field, then ERT=
 refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;object corresponding to the TOI field, otherwise =
it refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;session.<BR>
<BR>
This overloading seems to be potentially dangerous; it prematurely<BR>
excludes the possibility to specify a session ERT value whenever<BR>
a session carries multiple objects and hence needs to make use of<BR>
TOI in every packet.<BR>
Wouldn't it be a more clean solution to spent another bit and<BR>
optional field, to achieve a clean separation of both Object ERT<BR>
and Session ERT ?&#8221;<BR>
<BR>
This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional &#8220;Expected Session Residual Time&#8221; field. However I w=
as not involved in any of the original discussions on the EXT_TIME header, =
so I would like to know if there are any comments on this from those that w=
ere (or indeed anyone else).<BR>
<BR>
...Mark <BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C604CE1A21C2lubyqualcommcom_--

From watson@qualcomm.com  Fri Apr 10 10:28:07 2009
Return-Path: <watson@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 6A40A3A6A5D for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.454
X-Spam-Level: 
X-Spam-Status: No, score=-105.454 tagged_above=-999 required=5 tests=[AWL=1.144, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 V4UMeEr-28nq for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:27:59 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 535B53A63EB for <rmt@ietf.org>; Fri, 10 Apr 2009 10:27:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=watson@qualcomm.com; q=dns/txt; s=qcdkim; t=1239384548; x=1270920548; h=from:to:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Watson,=20Mark"=20<watson@qualcomm.com>|To:=20" Luby,=20Michael"=20<luby@qualcomm.com>,=20"rmt@ietf.org" =20<rmt@ietf.org>|Date:=20Fri,=2010=20Apr=202009=2010:29: 03=20-0700|Subject:=20Re:=20[Rmt]=20Comment=20on=20LCT=20 draft|Thread-Topic:=20[Rmt]=20Comment=20on=20LCT=20draft |Thread-Index:=20Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5oAABF 4x8=3D|Message-ID:=20<C604CFEF.2C6C1%watson@qualcomm.com> |In-Reply-To:=20<C604CE1A.21C2%luby@qualcomm.com> |Accept-Language:=20en-US|Content-Language:=20en |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C604CFEF2C6C1watsonqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5579"=3B=20a=3D"17052853"; bh=o196s90c53APwGOGy8/lGtVuWegUazS4xecuSabHpTA=; b=x0Qh7SC+Be7MARkaAUUZY+Z8DeFkpBMPlus/1z/UDEF6kfuzmN/3I/D1 xz0cfzwUR0bUMlc9lIhmbS4x2nFfOqnczx3jCCP84lI+f5vzdsVNfybKp y6fT7Sphqb7h1bPb8PfOUfaILia6bpnQpbA8KS8gIUWHB9Rbveeoz4O2T 0=;
X-IronPort-AV: E=McAfee;i="5300,2777,5579"; a="17052853"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2009 10:29:08 -0700
Received: from msgtransport02.qualcomm.com (msgtransport02.qualcomm.com [129.46.61.151]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHT7oA030380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:29:08 -0700
Received: from nasanexhub03.na.qualcomm.com (nasanexhub03.na.qualcomm.com [10.46.93.98]) by msgtransport02.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHT7i8004384 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:29:07 -0700
Received: from nasclexhc01.na.qualcomm.com (10.227.147.14) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 10 Apr 2009 10:29:07 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Fri, 10 Apr 2009 10:29:03 -0700
From: "Watson, Mark" <watson@qualcomm.com>
To: "Luby, Michael" <luby@qualcomm.com>, "rmt@ietf.org" <rmt@ietf.org>
Date: Fri, 10 Apr 2009 10:29:03 -0700
Thread-Topic: [Rmt] Comment on LCT draft
Thread-Index: Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5oAABF4x8=
Message-ID: <C604CFEF.2C6C1%watson@qualcomm.com>
In-Reply-To: <C604CE1A.21C2%luby@qualcomm.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C604CFEF2C6C1watsonqualcommcom_"
MIME-Version: 1.0
Subject: Re: [Rmt] Comment on LCT draft
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: Fri, 10 Apr 2009 17:28:07 -0000

--_000_C604CFEF2C6C1watsonqualcommcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Mike,

I agree with your proposals.

The original comment argued for the possibility to specify an expected end =
time for the session when more than one object is present, which is not cur=
rently possible (with or without the changes below). Is such a capability u=
seful ?

...Mark


On 4/10/09 10:21 AM, "Luby, Michael" <luby@qualcomm.com> wrote:

There is less ambiguity than one might think with this (perhaps no ambiguit=
y).  If you read the section about the TOI you will see that the TOI field =
MUST be used in all packets if more than one object is to be transmitted in=
 the session, i.e., the TOI field is either present in all the packets of a=
 session or is never present.  Given this, the ERT within a session is esse=
ntially always the end of the transmission of the current object:

(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.
(2) if there is only one object in the session
    (a) if the TOI is used for the object then the ERT is the end time of t=
ransmission of that object.
    (b) if the TOI is not used then the ERT is the end time of transmission=
 of the session, which presumably is the end time of transmission of that o=
bject.

It seems that  the only ambiguity is if there is one object in the session =
and some of the packets for that object carry the TOI and others don't (thi=
s does not seem disallowed by the MUST, despite the "i.e. ..." statement wh=
ich says it is not allowed).  In this case, it still seems that the ERT wil=
l always refer to the end time of the transmission of that object/session (=
they should be the same).  But, perhaps this could be clarified by includin=
g language that says that for a particular object the TOI must be in all pa=
ckets pertaining to that object or the TOI must not be in all packets perta=
ining to that object (this seems like a good restriction for other reasons =
as well, i.e., it is the natural way to do this and to do something differe=
nt in the case of transmission of one object seems pretty nonsensical, and =
the "i.e. ... " statement says this is true as well, even if it doesn't log=
ically follow from the MUST).

Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.

So, a concrete suggestion:

Change: The
         TOI field MUST be used in all packets if more than one object
         is to be transmitted in a session, i.e. the TOI field is either
         present in all the packets of a session or is never present.

To: The
         TOI field MUST be used in all packets in a session or none of the =
packets in a session.
         The TOI field MUST be used in all packets in a session if more tha=
n one object
         is to be transmitted in a session.

Change:  Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the current session or for the transmission of the
         current object, measured in units of 1ms.  If the packet
         containing the ERT field also contains the TOI field, then ERT
         refers to the object corresponding to the TOI field, otherwise
         it refers to the session.

To: Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the transmission of the current object, measured in units=
 of 1ms.

Mike


On 4/9/09 11:31 AM, "Watson, Mark" <watson@qualcomm.com> wrote:

All,

I received the following comment in the IESG Last Call for LCT:

"Section 5.2.2 specifies an overloading of the ERT flag and ERT field:

|  Expected Residual Time (ERT): ERT flag, corresponding 32 bit time
|  value
|
|     This timing information represents the sender expected residual
|     transmission time for the current session or for the transmission
|     of the current object.  If the packet containing the ERT timing
|     information also contains the TOI field, then ERT refers to the
|     object corresponding to the TOI field, otherwise it refers to the
|     session.

This overloading seems to be potentially dangerous; it prematurely
excludes the possibility to specify a session ERT value whenever
a session carries multiple objects and hence needs to make use of
TOI in every packet.
Wouldn't it be a more clean solution to spent another bit and
optional field, to achieve a clean separation of both Object ERT
and Session ERT ?"

This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional "Expected Session Residual Time" field. However I was not invol=
ved in any of the original discussions on the EXT_TIME header, so I would l=
ike to know if there are any comments on this from those that were (or inde=
ed anyone else).

...Mark





--_000_C604CFEF2C6C1watsonqualcommcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Rmt] Comment on LCT draft</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Mike,<BR>
<BR>
I agree with your proposals.<BR>
<BR>
The original comment argued for the possibility to specify an expected end =
time for the session when more than one object is present, which is not cur=
rently possible (with or without the changes below). Is such a capability u=
seful ?<BR>
<BR>
...Mark<BR>
<BR>
<BR>
On 4/10/09 10:21 AM, &quot;Luby, Michael&quot; &lt;<a href=3D"luby@qualcomm=
.com">luby@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>There is less ambiguity than one might thin=
k with this (perhaps no ambiguity). &nbsp;If you read the section about the=
 TOI you will see that the TOI field MUST be used in all packets if more th=
an one object is to be transmitted in the session, i.e., the TOI field is e=
ither present in all the packets of a session or is never present. &nbsp;Gi=
ven this, the ERT within a session is essentially always the end of the tra=
nsmission of the current object:<BR>
<BR>
(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.<BR=
>
(2) if there is only one object in the session<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(a) if the TOI is used for the object then the ERT =
is the end time of transmission of that object.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(b) if the TOI is not used then the ERT is the end =
time of transmission of the session, which presumably is the end time of tr=
ansmission of that object.<BR>
<BR>
It seems that &nbsp;the only ambiguity is if there is one object in the ses=
sion and some of the packets for that object carry the TOI and others don&#=
8217;t (this does not seem disallowed by the MUST, despite the &#8220;i.e. =
...&#8221; statement which says it is not allowed). &nbsp;In this case, it =
still seems that the ERT will always refer to the end time of the transmiss=
ion of that object/session (they should be the same). &nbsp;But, perhaps th=
is could be clarified by including language that says that for a particular=
 object the TOI must be in all packets pertaining to that object or the TOI=
 must not be in all packets pertaining to that object (this seems like a go=
od restriction for other reasons as well, i.e., it is the natural way to do=
 this and to do something different in the case of transmission of one obje=
ct seems pretty nonsensical, and the &#8220;i.e. ... &#8220; statement says=
 this is true as well, even if it doesn&#8217;t logically follow from the M=
UST).<BR>
<BR>
Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.<BR>
<BR>
So, a concrete suggestion:<BR>
<BR>
Change: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session, i.e. the TOI field is either<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;present in all the pa=
ckets of a session or is never present.<BR>
<BR>
To: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets in a session or none of the packets in a session.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The TOI field MUST be=
 used in all packets in a session if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session.<BR>
<BR>
Change: &nbsp;Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the current =
session or for the transmission of the<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;current object, measu=
red in units of 1ms. &nbsp;If the packet<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;containing the ERT fi=
eld also contains the TOI field, then ERT<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;refers to the object =
corresponding to the TOI field, otherwise<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;it refers to the sess=
ion.<BR>
<BR>
To: Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the transmis=
sion of the current object, measured in units of 1ms.<BR>
<BR>
Mike<BR>
<BR>
<BR>
On 4/9/09 11:31 AM, &quot;Watson, Mark&quot; &lt;<a href=3D"watson@qualcomm=
.com">watson@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>All,<BR>
<BR>
I received the following comment in the IESG Last Call for LCT:<BR>
<BR>
&#8220;Section 5.2.2 specifies an overloading of the ERT flag and ERT field=
:<BR>
<BR>
| &nbsp;Expected Residual Time (ERT): ERT flag, corresponding 32 bit time<B=
R>
| &nbsp;value<BR>
|<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;This timing information represents the sender exp=
ected residual<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;transmission time for the current session or for =
the transmission<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;of the current object. &nbsp;If the packet contai=
ning the ERT timing<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;information also contains the TOI field, then ERT=
 refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;object corresponding to the TOI field, otherwise =
it refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;session.<BR>
<BR>
This overloading seems to be potentially dangerous; it prematurely<BR>
excludes the possibility to specify a session ERT value whenever<BR>
a session carries multiple objects and hence needs to make use of<BR>
TOI in every packet.<BR>
Wouldn't it be a more clean solution to spent another bit and<BR>
optional field, to achieve a clean separation of both Object ERT<BR>
and Session ERT ?&#8221;<BR>
<BR>
This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional &#8220;Expected Session Residual Time&#8221; field. However I w=
as not involved in any of the original discussions on the EXT_TIME header, =
so I would like to know if there are any comments on this from those that w=
ere (or indeed anyone else).<BR>
<BR>
...Mark <BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C604CFEF2C6C1watsonqualcommcom_--

From luby@qualcomm.com  Fri Apr 10 10:43:36 2009
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 6EDE13A6A86 for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.037
X-Spam-Level: 
X-Spam-Status: No, score=-104.037 tagged_above=-999 required=5 tests=[AWL=-1.440, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 MK1T+zUcdyq0 for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:43:27 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 0FEB63A6A39 for <rmt@ietf.org>; Fri, 10 Apr 2009 10:43:27 -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=1239385476; x=1270921476; 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:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Luby,=20Michael"=20<luby@qualcomm.com>|To:=20"W atson,=20Mark"=20<watson@qualcomm.com>,=20"rmt@ietf.org" =20<rmt@ietf.org>|CC:=20"Luby,=20Michael"=20<luby@qualcom m.com>|Date:=20Fri,=2010=20Apr=202009=2010:44:27=20-0700 |Subject:=20Re:=20[Rmt]=20Comment=20on=20LCT=20draft |Thread-Topic:=20[Rmt]=20Comment=20on=20LCT=20draft |Thread-Index:=20Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5oAABF 4x8AAImwyQ=3D=3D|Message-ID:=20<C604D38B.21C9%luby@qualco mm.com>|In-Reply-To:=20<C604CFEF.2C6C1%watson@qualcomm.co m>|Accept-Language:=20en-US|Content-Language:=20en |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C604D38B21C9lubyqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5579"=3B=20a=3D"17040078"; bh=/uK1Bt1jXyyLmCo5qDRITSCTFeGb1a14yFQ+jwkE0Xg=; b=fhva9MiqRH6f/DeSR/5lUZpCql868+3rDld0P5VBEfyzIRjQnKwlxuyF QjWZTp3ORdXXL3s2ErUrYdajR5WNZ77Uq35jSSO3ItBB5ZsL7pyQBH+JD BAneEpEysCf7bFIsD+Hocjb3IrYN6oVAmR4FOdll0osvD+3FeKik9DSn5 M=;
X-IronPort-AV: E=McAfee;i="5300,2777,5579"; a="17040078"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2009 10:44:35 -0700
Received: from msgtransport01.qualcomm.com (msgtransport01.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHiZvS032611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:44:35 -0700
Received: from nasanexhub03.na.qualcomm.com (nasanexhub03.na.qualcomm.com [10.46.93.98]) by msgtransport01.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHiZeJ028446 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:44:35 -0700
Received: from nasclexhc01.na.qualcomm.com (10.227.147.14) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 10 Apr 2009 10:44:34 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Fri, 10 Apr 2009 10:44:33 -0700
From: "Luby, Michael" <luby@qualcomm.com>
To: "Watson, Mark" <watson@qualcomm.com>, "rmt@ietf.org" <rmt@ietf.org>
Date: Fri, 10 Apr 2009 10:44:27 -0700
Thread-Topic: [Rmt] Comment on LCT draft
Thread-Index: Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5oAABF4x8AAImwyQ==
Message-ID: <C604D38B.21C9%luby@qualcomm.com>
In-Reply-To: <C604CFEF.2C6C1%watson@qualcomm.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C604D38B21C9lubyqualcommcom_"
MIME-Version: 1.0
Cc: "Luby, Michael" <luby@qualcomm.com>
Subject: Re: [Rmt] Comment on LCT draft
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: Fri, 10 Apr 2009 17:43:36 -0000

--_000_C604D38B21C9lubyqualcommcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Mark,
I think the original comment was more focused on the ambiguity/overloading =
of the ERT rather than on arguing that there should be the possibility to s=
pecify an expected end time for the session.  I would argue that if someone=
 really wanted this capability then they would have already lobbied for it =
within the RMT, and it is a bit late to make these kinds of changes now wit=
hout a good reason, and likely to cause additional work with no clear gain =
unless someone really sees a reason for doing this.  That said, if people t=
hink that it is a good idea to be able to signal the expected end of the se=
ssion in-band then we could go forward with the work to specify this (there=
 are some reserved bits in the LCT header that could be used to signal this=
).  I think actually we might have had a way to signal the end of session t=
ime in an earlier draft but we took it out (but I might be wrong on this).
Mike


On 4/10/09 10:29 AM, "Watson, Mark" <watson@qualcomm.com> wrote:

Mike,

I agree with your proposals.

The original comment argued for the possibility to specify an expected end =
time for the session when more than one object is present, which is not cur=
rently possible (with or without the changes below). Is such a capability u=
seful ?

...Mark


On 4/10/09 10:21 AM, "Luby, Michael" <luby@qualcomm.com> wrote:

There is less ambiguity than one might think with this (perhaps no ambiguit=
y).  If you read the section about the TOI you will see that the TOI field =
MUST be used in all packets if more than one object is to be transmitted in=
 the session, i.e., the TOI field is either present in all the packets of a=
 session or is never present.  Given this, the ERT within a session is esse=
ntially always the end of the transmission of the current object:

(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.
(2) if there is only one object in the session
    (a) if the TOI is used for the object then the ERT is the end time of t=
ransmission of that object.
    (b) if the TOI is not used then the ERT is the end time of transmission=
 of the session, which presumably is the end time of transmission of that o=
bject.

It seems that  the only ambiguity is if there is one object in the session =
and some of the packets for that object carry the TOI and others don't (thi=
s does not seem disallowed by the MUST, despite the "i.e. ..." statement wh=
ich says it is not allowed).  In this case, it still seems that the ERT wil=
l always refer to the end time of the transmission of that object/session (=
they should be the same).  But, perhaps this could be clarified by includin=
g language that says that for a particular object the TOI must be in all pa=
ckets pertaining to that object or the TOI must not be in all packets perta=
ining to that object (this seems like a good restriction for other reasons =
as well, i.e., it is the natural way to do this and to do something differe=
nt in the case of transmission of one object seems pretty nonsensical, and =
the "i.e. ... " statement says this is true as well, even if it doesn't log=
ically follow from the MUST).

Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.

So, a concrete suggestion:

Change: The
         TOI field MUST be used in all packets if more than one object
         is to be transmitted in a session, i.e. the TOI field is either
         present in all the packets of a session or is never present.

To: The
         TOI field MUST be used in all packets in a session or none of the =
packets in a session.
         The TOI field MUST be used in all packets in a session if more tha=
n one object
         is to be transmitted in a session.

Change:  Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the current session or for the transmission of the
         current object, measured in units of 1ms.  If the packet
         containing the ERT field also contains the TOI field, then ERT
         refers to the object corresponding to the TOI field, otherwise
         it refers to the session.

To: Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the transmission of the current object, measured in units=
 of 1ms.

Mike


On 4/9/09 11:31 AM, "Watson, Mark" <watson@qualcomm.com> wrote:

All,

I received the following comment in the IESG Last Call for LCT:

"Section 5.2.2 specifies an overloading of the ERT flag and ERT field:

|  Expected Residual Time (ERT): ERT flag, corresponding 32 bit time
|  value
|
|     This timing information represents the sender expected residual
|     transmission time for the current session or for the transmission
|     of the current object.  If the packet containing the ERT timing
|     information also contains the TOI field, then ERT refers to the
|     object corresponding to the TOI field, otherwise it refers to the
|     session.

This overloading seems to be potentially dangerous; it prematurely
excludes the possibility to specify a session ERT value whenever
a session carries multiple objects and hence needs to make use of
TOI in every packet.
Wouldn't it be a more clean solution to spent another bit and
optional field, to achieve a clean separation of both Object ERT
and Session ERT ?"

This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional "Expected Session Residual Time" field. However I was not invol=
ved in any of the original discussions on the EXT_TIME header, so I would l=
ike to know if there are any comments on this from those that were (or inde=
ed anyone else).

...Mark






--_000_C604D38B21C9lubyqualcommcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Rmt] Comment on LCT draft</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Mark,<BR>
I think the original comment was more focused on the ambiguity/overloading =
of the ERT rather than on arguing that there should be the possibility to s=
pecify an expected end time for the session. &nbsp;I would argue that if so=
meone really wanted this capability then they would have already lobbied fo=
r it within the RMT, and it is a bit late to make these kinds of changes no=
w without a good reason, and likely to cause additional work with no clear =
gain unless someone really sees a reason for doing this. &nbsp;That said, i=
f people think that it is a good idea to be able to signal the expected end=
 of the session in-band then we could go forward with the work to specify t=
his (there are some reserved bits in the LCT header that could be used to s=
ignal this). &nbsp;I think actually we might have had a way to signal the e=
nd of session time in an earlier draft but we took it out (but I might be w=
rong on this).<BR>
Mike<BR>
<BR>
<BR>
On 4/10/09 10:29 AM, &quot;Watson, Mark&quot; &lt;<a href=3D"watson@qualcom=
m.com">watson@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Mike,<BR>
<BR>
I agree with your proposals.<BR>
<BR>
The original comment argued for the possibility to specify an expected end =
time for the session when more than one object is present, which is not cur=
rently possible (with or without the changes below). Is such a capability u=
seful ?<BR>
<BR>
...Mark<BR>
<BR>
<BR>
On 4/10/09 10:21 AM, &quot;Luby, Michael&quot; &lt;<a href=3D"luby@qualcomm=
.com">luby@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>There is less ambiguity than one might thin=
k with this (perhaps no ambiguity). &nbsp;If you read the section about the=
 TOI you will see that the TOI field MUST be used in all packets if more th=
an one object is to be transmitted in the session, i.e., the TOI field is e=
ither present in all the packets of a session or is never present. &nbsp;Gi=
ven this, the ERT within a session is essentially always the end of the tra=
nsmission of the current object:<BR>
<BR>
(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.<BR=
>
(2) if there is only one object in the session<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(a) if the TOI is used for the object then the ERT =
is the end time of transmission of that object.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(b) if the TOI is not used then the ERT is the end =
time of transmission of the session, which presumably is the end time of tr=
ansmission of that object.<BR>
<BR>
It seems that &nbsp;the only ambiguity is if there is one object in the ses=
sion and some of the packets for that object carry the TOI and others don&#=
8217;t (this does not seem disallowed by the MUST, despite the &#8220;i.e. =
...&#8221; statement which says it is not allowed). &nbsp;In this case, it =
still seems that the ERT will always refer to the end time of the transmiss=
ion of that object/session (they should be the same). &nbsp;But, perhaps th=
is could be clarified by including language that says that for a particular=
 object the TOI must be in all packets pertaining to that object or the TOI=
 must not be in all packets pertaining to that object (this seems like a go=
od restriction for other reasons as well, i.e., it is the natural way to do=
 this and to do something different in the case of transmission of one obje=
ct seems pretty nonsensical, and the &#8220;i.e. ... &#8220; statement says=
 this is true as well, even if it doesn&#8217;t logically follow from the M=
UST).<BR>
<BR>
Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.<BR>
<BR>
So, a concrete suggestion:<BR>
<BR>
Change: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session, i.e. the TOI field is either<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;present in all the pa=
ckets of a session or is never present.<BR>
<BR>
To: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets in a session or none of the packets in a session.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The TOI field MUST be=
 used in all packets in a session if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session.<BR>
<BR>
Change: &nbsp;Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the current =
session or for the transmission of the<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;current object, measu=
red in units of 1ms. &nbsp;If the packet<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;containing the ERT fi=
eld also contains the TOI field, then ERT<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;refers to the object =
corresponding to the TOI field, otherwise<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;it refers to the sess=
ion.<BR>
<BR>
To: Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the transmis=
sion of the current object, measured in units of 1ms.<BR>
<BR>
Mike<BR>
<BR>
<BR>
On 4/9/09 11:31 AM, &quot;Watson, Mark&quot; &lt;<a href=3D"watson@qualcomm=
.com">watson@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>All,<BR>
<BR>
I received the following comment in the IESG Last Call for LCT:<BR>
<BR>
&#8220;Section 5.2.2 specifies an overloading of the ERT flag and ERT field=
:<BR>
<BR>
| &nbsp;Expected Residual Time (ERT): ERT flag, corresponding 32 bit time<B=
R>
| &nbsp;value<BR>
|<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;This timing information represents the sender exp=
ected residual<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;transmission time for the current session or for =
the transmission<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;of the current object. &nbsp;If the packet contai=
ning the ERT timing<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;information also contains the TOI field, then ERT=
 refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;object corresponding to the TOI field, otherwise =
it refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;session.<BR>
<BR>
This overloading seems to be potentially dangerous; it prematurely<BR>
excludes the possibility to specify a session ERT value whenever<BR>
a session carries multiple objects and hence needs to make use of<BR>
TOI in every packet.<BR>
Wouldn't it be a more clean solution to spent another bit and<BR>
optional field, to achieve a clean separation of both Object ERT<BR>
and Session ERT ?&#8221;<BR>
<BR>
This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional &#8220;Expected Session Residual Time&#8221; field. However I w=
as not involved in any of the original discussions on the EXT_TIME header, =
so I would like to know if there are any comments on this from those that w=
ere (or indeed anyone else).<BR>
<BR>
...Mark <BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C604D38B21C9lubyqualcommcom_--

From watson@qualcomm.com  Fri Apr 10 10:47:39 2009
Return-Path: <watson@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 DE5283A6947 for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.617
X-Spam-Level: 
X-Spam-Status: No, score=-105.617 tagged_above=-999 required=5 tests=[AWL=0.981, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 4FbLR1e98rd4 for <rmt@core3.amsl.com>; Fri, 10 Apr 2009 10:47:30 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 598BF3A68D1 for <rmt@ietf.org>; Fri, 10 Apr 2009 10:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=watson@qualcomm.com; q=dns/txt; s=qcdkim; t=1239385719; x=1270921719; h=from:to:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Watson,=20Mark"=20<watson@qualcomm.com>|To:=20" Luby,=20Michael"=20<luby@qualcomm.com>,=20"rmt@ietf.org" =20<rmt@ietf.org>|Date:=20Fri,=2010=20Apr=202009=2010:48: 28=20-0700|Subject:=20Re:=20[Rmt]=20Comment=20on=20LCT=20 draft|Thread-Topic:=20[Rmt]=20Comment=20on=20LCT=20draft |Thread-Index:=20Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5oAABF 4x8AAImwyQAAI+lU|Message-ID:=20<C604D47C.2C6C8%watson@qua lcomm.com>|In-Reply-To:=20<C604D38B.21C9%luby@qualcomm.co m>|Accept-Language:=20en-US|Content-Language:=20en |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C604D47C2C6C8watsonqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5579"=3B=20a=3D"17053496"; bh=dgcGJUgmlxRSLN0UlLClSY07OMghCBAqyVoJX1DbM+Q=; b=x8zePZldZqufHwy8urdimE+Z1yHK0JsaaLvsT9emwb3MmrMFpL+1Jsr+ K1JrK+fIjMHeTJl5HRvSiTXtMylZj1DJzwfoJ7eTaIEGdUv3y9qYeIsL7 D1awRjrVGrwy81cQftHpDz5dxG+LBtMKv87PEkkHQANKFTboT91lZLkph k=;
X-IronPort-AV: E=McAfee;i="5300,2777,5579"; a="17053496"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2009 10:48:33 -0700
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com [129.46.61.156]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHmXap000683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:48:33 -0700
Received: from nasanexhub03.na.qualcomm.com (nasanexhub03.na.qualcomm.com [10.46.93.98]) by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n3AHmWsH021158 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rmt@ietf.org>; Fri, 10 Apr 2009 10:48:32 -0700
Received: from nasclexhc02.na.qualcomm.com (10.227.147.13) by nasanexhub03.na.qualcomm.com (10.46.93.98) with Microsoft SMTP Server (TLS) id 8.1.340.0; Fri, 10 Apr 2009 10:48:32 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc02.na.qualcomm.com ([10.227.147.13]) with mapi; Fri, 10 Apr 2009 10:48:31 -0700
From: "Watson, Mark" <watson@qualcomm.com>
To: "Luby, Michael" <luby@qualcomm.com>, "rmt@ietf.org" <rmt@ietf.org>
Date: Fri, 10 Apr 2009 10:48:28 -0700
Thread-Topic: [Rmt] Comment on LCT draft
Thread-Index: Acm5QWZ5JZlBmyO5CUmq5fohqap5/AAv1l5oAABF4x8AAImwyQAAI+lU
Message-ID: <C604D47C.2C6C8%watson@qualcomm.com>
In-Reply-To: <C604D38B.21C9%luby@qualcomm.com>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C604D47C2C6C8watsonqualcommcom_"
MIME-Version: 1.0
Subject: Re: [Rmt] Comment on LCT draft
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: Fri, 10 Apr 2009 17:47:40 -0000

--_000_C604D47C2C6C8watsonqualcommcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Mike,

Ok, so my proposed disposition of this comment is to say that we will clari=
fy the ERT to always be the end time of the current object and that the pos=
sibility to separately specify the end time of the current session is not b=
elieved to be useful, but could anyway be added in another document if need=
ed (with an LCT header extension).

Any other comments ?

...Mark


On 4/10/09 10:44 AM, "Luby, Michael" <luby@qualcomm.com> wrote:

Mark,
I think the original comment was more focused on the ambiguity/overloading =
of the ERT rather than on arguing that there should be the possibility to s=
pecify an expected end time for the session.  I would argue that if someone=
 really wanted this capability then they would have already lobbied for it =
within the RMT, and it is a bit late to make these kinds of changes now wit=
hout a good reason, and likely to cause additional work with no clear gain =
unless someone really sees a reason for doing this.  That said, if people t=
hink that it is a good idea to be able to signal the expected end of the se=
ssion in-band then we could go forward with the work to specify this (there=
 are some reserved bits in the LCT header that could be used to signal this=
).  I think actually we might have had a way to signal the end of session t=
ime in an earlier draft but we took it out (but I might be wrong on this).
Mike


On 4/10/09 10:29 AM, "Watson, Mark" <watson@qualcomm.com> wrote:

Mike,

I agree with your proposals.

The original comment argued for the possibility to specify an expected end =
time for the session when more than one object is present, which is not cur=
rently possible (with or without the changes below). Is such a capability u=
seful ?

...Mark


On 4/10/09 10:21 AM, "Luby, Michael" <luby@qualcomm.com> wrote:

There is less ambiguity than one might think with this (perhaps no ambiguit=
y).  If you read the section about the TOI you will see that the TOI field =
MUST be used in all packets if more than one object is to be transmitted in=
 the session, i.e., the TOI field is either present in all the packets of a=
 session or is never present.  Given this, the ERT within a session is esse=
ntially always the end of the transmission of the current object:

(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.
(2) if there is only one object in the session
    (a) if the TOI is used for the object then the ERT is the end time of t=
ransmission of that object.
    (b) if the TOI is not used then the ERT is the end time of transmission=
 of the session, which presumably is the end time of transmission of that o=
bject.

It seems that  the only ambiguity is if there is one object in the session =
and some of the packets for that object carry the TOI and others don't (thi=
s does not seem disallowed by the MUST, despite the "i.e. ..." statement wh=
ich says it is not allowed).  In this case, it still seems that the ERT wil=
l always refer to the end time of the transmission of that object/session (=
they should be the same).  But, perhaps this could be clarified by includin=
g language that says that for a particular object the TOI must be in all pa=
ckets pertaining to that object or the TOI must not be in all packets perta=
ining to that object (this seems like a good restriction for other reasons =
as well, i.e., it is the natural way to do this and to do something differe=
nt in the case of transmission of one object seems pretty nonsensical, and =
the "i.e. ... " statement says this is true as well, even if it doesn't log=
ically follow from the MUST).

Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.

So, a concrete suggestion:

Change: The
         TOI field MUST be used in all packets if more than one object
         is to be transmitted in a session, i.e. the TOI field is either
         present in all the packets of a session or is never present.

To: The
         TOI field MUST be used in all packets in a session or none of the =
packets in a session.
         The TOI field MUST be used in all packets in a session if more tha=
n one object
         is to be transmitted in a session.

Change:  Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the current session or for the transmission of the
         current object, measured in units of 1ms.  If the packet
         containing the ERT field also contains the TOI field, then ERT
         refers to the object corresponding to the TOI field, otherwise
         it refers to the session.

To: Expected Residual Time (ERT): 0 or 32 bits

         This field represents the sender expected residual transmission
         time for the transmission of the current object, measured in units=
 of 1ms.

Mike


On 4/9/09 11:31 AM, "Watson, Mark" <watson@qualcomm.com> wrote:

All,

I received the following comment in the IESG Last Call for LCT:

"Section 5.2.2 specifies an overloading of the ERT flag and ERT field:

|  Expected Residual Time (ERT): ERT flag, corresponding 32 bit time
|  value
|
|     This timing information represents the sender expected residual
|     transmission time for the current session or for the transmission
|     of the current object.  If the packet containing the ERT timing
|     information also contains the TOI field, then ERT refers to the
|     object corresponding to the TOI field, otherwise it refers to the
|     session.

This overloading seems to be potentially dangerous; it prematurely
excludes the possibility to specify a session ERT value whenever
a session carries multiple objects and hence needs to make use of
TOI in every packet.
Wouldn't it be a more clean solution to spent another bit and
optional field, to achieve a clean separation of both Object ERT
and Session ERT ?"

This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional "Expected Session Residual Time" field. However I was not invol=
ved in any of the original discussions on the EXT_TIME header, so I would l=
ike to know if there are any comments on this from those that were (or inde=
ed anyone else).

...Mark







--_000_C604D47C2C6C8watsonqualcommcom_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [Rmt] Comment on LCT draft</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Mike,<BR>
<BR>
Ok, so my proposed disposition of this comment is to say that we will clari=
fy the ERT to always be the end time of the current <B>object</B> and that =
the possibility to separately specify the end time of the current <B>sessio=
n</B> is not believed to be useful, but could anyway be added in another do=
cument if needed (with an LCT header extension).<BR>
<BR>
Any other comments ?<BR>
<BR>
...Mark<BR>
<BR>
<BR>
On 4/10/09 10:44 AM, &quot;Luby, Michael&quot; &lt;<a href=3D"luby@qualcomm=
.com">luby@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Mark,<BR>
I think the original comment was more focused on the ambiguity/overloading =
of the ERT rather than on arguing that there should be the possibility to s=
pecify an expected end time for the session. &nbsp;I would argue that if so=
meone really wanted this capability then they would have already lobbied fo=
r it within the RMT, and it is a bit late to make these kinds of changes no=
w without a good reason, and likely to cause additional work with no clear =
gain unless someone really sees a reason for doing this. &nbsp;That said, i=
f people think that it is a good idea to be able to signal the expected end=
 of the session in-band then we could go forward with the work to specify t=
his (there are some reserved bits in the LCT header that could be used to s=
ignal this). &nbsp;I think actually we might have had a way to signal the e=
nd of session time in an earlier draft but we took it out (but I might be w=
rong on this).<BR>
Mike<BR>
<BR>
<BR>
On 4/10/09 10:29 AM, &quot;Watson, Mark&quot; &lt;<a href=3D"watson@qualcom=
m.com">watson@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Mike,<BR>
<BR>
I agree with your proposals.<BR>
<BR>
The original comment argued for the possibility to specify an expected end =
time for the session when more than one object is present, which is not cur=
rently possible (with or without the changes below). Is such a capability u=
seful ?<BR>
<BR>
...Mark<BR>
<BR>
<BR>
On 4/10/09 10:21 AM, &quot;Luby, Michael&quot; &lt;<a href=3D"luby@qualcomm=
.com">luby@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>There is less ambiguity than one might thin=
k with this (perhaps no ambiguity). &nbsp;If you read the section about the=
 TOI you will see that the TOI field MUST be used in all packets if more th=
an one object is to be transmitted in the session, i.e., the TOI field is e=
ither present in all the packets of a session or is never present. &nbsp;Gi=
ven this, the ERT within a session is essentially always the end of the tra=
nsmission of the current object:<BR>
<BR>
(1) If there is more than one object in the session the TOI MUST be in all =
packets and thus the ERT is the end time of transmission of each object.<BR=
>
(2) if there is only one object in the session<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(a) if the TOI is used for the object then the ERT =
is the end time of transmission of that object.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;(b) if the TOI is not used then the ERT is the end =
time of transmission of the session, which presumably is the end time of tr=
ansmission of that object.<BR>
<BR>
It seems that &nbsp;the only ambiguity is if there is one object in the ses=
sion and some of the packets for that object carry the TOI and others don&#=
8217;t (this does not seem disallowed by the MUST, despite the &#8220;i.e. =
...&#8221; statement which says it is not allowed). &nbsp;In this case, it =
still seems that the ERT will always refer to the end time of the transmiss=
ion of that object/session (they should be the same). &nbsp;But, perhaps th=
is could be clarified by including language that says that for a particular=
 object the TOI must be in all packets pertaining to that object or the TOI=
 must not be in all packets pertaining to that object (this seems like a go=
od restriction for other reasons as well, i.e., it is the natural way to do=
 this and to do something different in the case of transmission of one obje=
ct seems pretty nonsensical, and the &#8220;i.e. ... &#8220; statement says=
 this is true as well, even if it doesn&#8217;t logically follow from the M=
UST).<BR>
<BR>
Perhaps even easier is to just change the definition of ERT to say that it =
is the end transmission of the object, since practically this is what it is=
 defined to be right now, although in a convoluted way.<BR>
<BR>
So, a concrete suggestion:<BR>
<BR>
Change: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session, i.e. the TOI field is either<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;present in all the pa=
ckets of a session or is never present.<BR>
<BR>
To: The<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;TOI field MUST be use=
d in all packets in a session or none of the packets in a session.<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The TOI field MUST be=
 used in all packets in a session if more than one object<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;is to be transmitted =
in a session.<BR>
<BR>
Change: &nbsp;Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the current =
session or for the transmission of the<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;current object, measu=
red in units of 1ms. &nbsp;If the packet<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;containing the ERT fi=
eld also contains the TOI field, then ERT<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;refers to the object =
corresponding to the TOI field, otherwise<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;it refers to the sess=
ion.<BR>
<BR>
To: Expected Residual Time (ERT): 0 or 32 bits<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;This field represents=
 the sender expected residual transmission<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;time for the transmis=
sion of the current object, measured in units of 1ms.<BR>
<BR>
Mike<BR>
<BR>
<BR>
On 4/9/09 11:31 AM, &quot;Watson, Mark&quot; &lt;<a href=3D"watson@qualcomm=
.com">watson@qualcomm.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>All,<BR>
<BR>
I received the following comment in the IESG Last Call for LCT:<BR>
<BR>
&#8220;Section 5.2.2 specifies an overloading of the ERT flag and ERT field=
:<BR>
<BR>
| &nbsp;Expected Residual Time (ERT): ERT flag, corresponding 32 bit time<B=
R>
| &nbsp;value<BR>
|<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;This timing information represents the sender exp=
ected residual<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;transmission time for the current session or for =
the transmission<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;of the current object. &nbsp;If the packet contai=
ning the ERT timing<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;information also contains the TOI field, then ERT=
 refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;object corresponding to the TOI field, otherwise =
it refers to the<BR>
| &nbsp;&nbsp;&nbsp;&nbsp;session.<BR>
<BR>
This overloading seems to be potentially dangerous; it prematurely<BR>
excludes the possibility to specify a session ERT value whenever<BR>
a session carries multiple objects and hence needs to make use of<BR>
TOI in every packet.<BR>
Wouldn't it be a more clean solution to spent another bit and<BR>
optional field, to achieve a clean separation of both Object ERT<BR>
and Session ERT ?&#8221;<BR>
<BR>
This seems reasonable to me, except that I would not change the semantics o=
f the existing bit (for backwards compatibility reasons), but rather add an=
 additional &#8220;Expected Session Residual Time&#8221; field. However I w=
as not involved in any of the original discussions on the EXT_TIME header, =
so I would like to know if there are any comments on this from those that w=
ere (or indeed anyone else).<BR>
<BR>
...Mark <BR>
<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial=
"><SPAN STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C604D47C2C6C8watsonqualcommcom_--

From adamson@itd.nrl.navy.mil  Thu Apr 16 08:11:05 2009
Return-Path: <adamson@itd.nrl.navy.mil>
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 6AA8E3A6B74 for <rmt@core3.amsl.com>; Thu, 16 Apr 2009 08:11:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.456
X-Spam-Level: 
X-Spam-Status: No, score=-6.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 hD7yCsXlQmaY for <rmt@core3.amsl.com>; Thu, 16 Apr 2009 08:11:04 -0700 (PDT)
Received: from s2.itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3]) by core3.amsl.com (Postfix) with ESMTP id 5F53528C0EF for <rmt@ietf.org>; Thu, 16 Apr 2009 08:10:53 -0700 (PDT)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.8/8.13.8) with SMTP id n3GFC5OY007319; Thu, 16 Apr 2009 11:12:05 -0400
Received: from macsimus.itd.nrl.navy.mil ([132.250.92.151]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.16.48) with SMTP id M2009041611120515187 ; Thu, 16 Apr 2009 11:12:05 -0400
Message-Id: <249E4CD8-3D2D-4EBC-B745-C664B3BDF0AF@itd.nrl.navy.mil>
From: Brian Adamson <adamson@itd.nrl.navy.mil>
To: rmt@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 16 Apr 2009 11:12:05 -0400
X-Mailer: Apple Mail (2.930.3)
Cc: Brian Adamson <adamson@itd.nrl.navy.mil>
Subject: [Rmt] IETF74 FCAST Action Item
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: Thu, 16 Apr 2009 15:11:05 -0000

Hello,

During discussions at the IETF74 RMT meeting, we concluded that we  
should poll the mailing list to determine if there is sufficient  
interest in adding the new FCAST document and pursuing it as an RMT  
working group item.  There was some interest expressed during the  
working group meeting and a number of folks raised their hands  
indicating they would review the document (i.e. we need broader  
participation than just the document authors!)

This message requests interested parties to respond on the mailing  
list to indicate their opinion on this:

1) Do you think there is merit in the FCAST specification as an RMT WG  
item (or not)?

2) Will you review the document so that we can rapidly finish it if it  
is accepted as a working group item?


Thank you in advance for your responses to this query.

best regards,




Brian Adamson
adamson@itd.nrl.navy.mil





From asaeda@sfc.wide.ad.jp  Fri Apr 17 05:19:10 2009
Return-Path: <asaeda@sfc.wide.ad.jp>
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 7E2363A6F7D for <rmt@core3.amsl.com>; Fri, 17 Apr 2009 05:19:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.038
X-Spam-Level: ***
X-Spam-Status: No, score=3.038 tagged_above=-999 required=5 tests=[AWL=0.275,  BAYES_20=-0.74, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
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 PVa7xus7hn4D for <rmt@core3.amsl.com>; Fri, 17 Apr 2009 05:19:09 -0700 (PDT)
Received: from pione.sfc.wide.ad.jp (pione.sfc.wide.ad.jp [203.178.143.172]) by core3.amsl.com (Postfix) with ESMTP id C52DC28C132 for <rmt@ietf.org>; Fri, 17 Apr 2009 05:19:09 -0700 (PDT)
Received: from localhost (dhcp-143-225.sfc.wide.ad.jp [203.178.143.225]) by pione.sfc.wide.ad.jp (Postfix) with ESMTP id 3B38B13D06C4; Fri, 17 Apr 2009 21:20:21 +0900 (JST)
Date: Fri, 17 Apr 2009 21:20:21 +0900 (JST)
Message-Id: <20090417.212021.62361778.asaeda@sfc.wide.ad.jp>
To: adamson@itd.nrl.navy.mil
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <249E4CD8-3D2D-4EBC-B745-C664B3BDF0AF@itd.nrl.navy.mil>
References: <249E4CD8-3D2D-4EBC-B745-C664B3BDF0AF@itd.nrl.navy.mil>
X-Mailer: Mew version 6.1 on Emacs 22.2.50 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: rmt@ietf.org
Subject: Re: [Rmt] IETF74 FCAST Action Item
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: Fri, 17 Apr 2009 12:19:10 -0000

Hi Brian,

> 1) Do you think there is merit in the FCAST specification as an RMT
> WG item (or not)?

I support it.
Supporting both ALC and NORM would be highly beneficial for various
use-cases. And no IPR issue will be good for potential developers.

> 2) Will you review the document so that we can rapidly finish it if
> it is accepted as a working group item?

Yes, I'd be happy to review the document.

Regards,
--
Hitoshi Asaeda

From magnus.westerlund@ericsson.com  Fri Apr 17 08:34:37 2009
Return-Path: <magnus.westerlund@ericsson.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 64B353A6E98 for <rmt@core3.amsl.com>; Fri, 17 Apr 2009 08:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 AenGlaucxobz for <rmt@core3.amsl.com>; Fri, 17 Apr 2009 08:34:36 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 29C1B3A6DFB for <rmt@ietf.org>; Fri, 17 Apr 2009 08:34:36 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 16C6620586; Fri, 17 Apr 2009 17:35:44 +0200 (CEST)
X-AuditID: c1b4fb3c-abfcdbb00000238f-99-49e8a1cf6f20
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 9308D20774; Fri, 17 Apr 2009 17:35:43 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 17 Apr 2009 17:34:40 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 17 Apr 2009 17:34:39 +0200
Message-ID: <49E8A18F.9050803@ericsson.com>
Date: Fri, 17 Apr 2009 17:34:39 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: draft-ietf-rmt-flute-revised@tools.ietf.org, "rmt@ietf.org" <rmt@ietf.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 17 Apr 2009 15:34:39.0949 (UTC) FILETIME=[05B1DFD0:01C9BF72]
X-Brightmail-Tracker: AAAAAA==
Subject: [Rmt] AD evaluation comments on draft-ietf-rmt-flute-revised-06
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: Fri, 17 Apr 2009 15:34:37 -0000

Hi,

I have reviewed the Flute spec and have some comments:

1. There are ID nits on the doc:
  == Outdated reference: A later version (-06) exists of
     draft-ietf-rmt-pi-alc-revised-03

  == Outdated reference: A later version (-09) exists of
     draft-ietf-rmt-bb-lct-revised-04

  == Outdated reference: draft-ietf-rmt-fec-bb-revised has been published as
     RFC 5052

  -- Possible downref: Non-RFC (?) normative reference: ref. '7'

  -- Possible downref: Non-RFC (?) normative reference: ref. '8'

  ** Obsolete normative reference: RFC 2279 (ref. '10') (Obsoleted by RFC
     3629)

  ** Obsolete normative reference: RFC 2434 (ref. '11') (Obsoleted by RFC
     5226)

  -- Obsolete informational reference (is this intentional?): RFC 2327 (ref.
     '14') (Obsoleted by RFC 4566)

  -- Obsolete informational reference (is this intentional?): RFC 2633 (ref.
     '19') (Obsoleted by RFC 3851)

  -- Obsolete informational reference (is this intentional?): RFC 2048 (ref.
     '21') (Obsoleted by RFC 4288, RFC 4289)


Use the check on the tools page to verify before submission that there
are no ones. The submission check covers only parts of all the nits.

2. I have basically the same comment on this document as on ALC PI about
mandatory to implement security solutions.

3. The document header, the abstract and the introduction needs to say
that this document will obsolete RFC 3926.

4. Section 1. As the ALC PI isn't suitable for general deployment using
unicast, flute can't really either. The congestion control is the issue.

5. Section 3.3, there is a reference to the NTP time format. NTP v4 has
been to IESG but are not approved yet. Are there a point of actually
referencing the clarified formats in that doc? That also have a
clarified discussion about epochs that helps handling the wrap around.

6. Section 3.4.1:
   Mandatory receiver behavior for handling FDT Instance
   ID wraparound and other special situations (for example, missing FDT
   Instance IDs resulting in larger increments than one) is outside the
   scope of this specification and left to individual implementations of
   FLUTE.

Why isn't this specified. Seem to be important for interoperable usage.
Seems to be a fine thing to gloss over in an experimental, but not in a
proposed standard.

7. Section 3.4.2:

Why is only HTTP URLs valid in the location header? In addition why was
HTTP URLs used? There is after all an explicit transport mechanism
implied by that. Some clarification on that relation would be good.

8. section 3.4.3:

Shouldn't the reserve bits be ignore on reception also?

9. Section 4, page 20, bullet 2:

Missing reference  to FEC encoding id 0.

10. Section 6:

Shouldn't this text discuss the need for configuring the congestion
control mechanism also? The security parameters needs discussion also.

11. Section 8.2: Chairs, have the update of the media type registrations
been reviewed on the ietf-types list?

12. Section 8.2: The template hasn't been updated. The change controller
is a split item and should be saying "IETF".

13. Section 8.3.1: It seems to be some confusion about the usage of URN
for purpose of describing where the name spaces are. I think this needs
to be clarified. Can the authors and the chairs please try to resolve
this with the IANA?

14. Section 12.2:

Are really reference 17 and 18 informative. You are binding them for a
particular usage.


Conclusion: A number of issues needs resolving. I am expecting a revised ID.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From magnus.westerlund@ericsson.com  Fri Apr 17 09:12:03 2009
Return-Path: <magnus.westerlund@ericsson.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 165C528C0D8 for <rmt@core3.amsl.com>; Fri, 17 Apr 2009 09:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level: 
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 E6EwB2qEStT6 for <rmt@core3.amsl.com>; Fri, 17 Apr 2009 09:12:02 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id A77473A69FF for <rmt@ietf.org>; Fri, 17 Apr 2009 09:12:01 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 0A868220B2; Fri, 17 Apr 2009 18:13:14 +0200 (CEST)
X-AuditID: c1b4fb3e-ad822bb0000024d5-c8-49e88e235432
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 287022767B; Fri, 17 Apr 2009 16:11:48 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 17 Apr 2009 16:08:29 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 17 Apr 2009 16:08:28 +0200
Message-ID: <49E88D5C.4000607@ericsson.com>
Date: Fri, 17 Apr 2009 16:08:28 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: draft-ietf-rmt-pi-alc-revised@tools.ietf.org,  "rmt@ietf.org" <rmt@ietf.org>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 17 Apr 2009 14:08:28.0520 (UTC) FILETIME=[FB486E80:01C9BF65]
X-Brightmail-Tracker: AAAAAA==
Subject: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06
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: Fri, 17 Apr 2009 16:12:03 -0000

Hi,

I have reviewed the ALC PI and have some comments.

1. If one compare this one with the experimental one they are very
similar. At least my expectation would be that a bit more details are
actually nailed down on how one should do them to achieve interoperable
implementations. For example the choice of congestion control algorithm.
I think we only have one that we can really use to satisfy the intended
usage of large scale sessions. Why isn't this a required to implement
feature?

The same thing can be said about normative to implement security
features. Yes, here there are choices, but still specify one required to
implement should be possible. If you have observant the NORM PI got this
comment from the SECdir reviewer. And I think he was right, we should be
clear on these.

A question is if we need to specify one mandatory to implement FEC
encoding?

In general I am not against the flexibility the protocol allows for.
However, it should be clear what you do need to implement for a
base-line implementation.

2. Section 2, third paragraph:
"This
   specification defines ALC as payload of the UDP transport protocol
   [RFC0768] that supports IP multicast delivery of packets.  Future
   versions of this specification, or companion documents may extend ALC
   to use the IP network layer service directly.  ALC could be used as
   the basis for designing a protocol that uses a different underlying
   network service such as unicast UDP, but the design of such a
   protocol is outside the scope of this document."

This type of text seems out of place. You are not any longer describing
a experimental protocol. State what is, not what could have been. Also
the ALC PI would not work from a congestion control side over unicast IP.

3. I am also disappointed that the ID nits hasn't been taking care of:

  Miscellaneous warnings:

----------------------------------------------------------------------------

  == The copyright year in the IETF Trust Copyright Line does not match the
     current year

  -- The exact meaning of the all-uppercase expression 'MAY NOT' is not
     defined in RFC 2119.  If it is intended as a requirements
expression, it
     should be rewritten using one of the combinations defined in RFC 2119;
     otherwise it should not be all-uppercase.

  == The expression 'MAY NOT', while looking like RFC 2119 requirements
text,
     is not defined in RFC 2119, and should not be used.  Consider using
'MUST
     NOT' instead (if that is what you mean).

     Found 'MAY NOT' in this paragraph:

     All senders and receivers implementing ALC MUST support the EXT_NOP
     Header Extension and MUST recognize EXT_AUTH, but MAY NOT be able to
     parse its content.  The EXT_NOP and EXT_AUTH LCT Header Extensions are
     defined in [I-D.ietf-rmt-bb-lct-revised]

  == The expression 'MAY NOT', while looking like RFC 2119 requirements
text,
     is not defined in RFC 2119, and should not be used.  Consider using
'MUST
     NOT' instead (if that is what you mean).

     Found 'MAY NOT' in this paragraph:

     If more than one object is to be carried within a session then the
     Transmission Object Identifier (TOI) MUST be used in the LCT header to
     identify which packets are to be associated with which objects. In this
     case the receiver MUST use the TOI to associate received packets with
     objects.  The TOI is scoped by the IP address of the sender and the
TSI,
     i.e., the TOI is scoped by the session.  The TOI for each object is
     REQUIRED to be unique within a session, but MAY NOT be unique across
     sessions.  Furthermore, the same object MAY have a different TOI in
     different sessions.  The mapping between TOIs and objects carried in a
     session is outside the scope of this document.

  == The document seems to lack a disclaimer for pre-RFC5378 work, but was
     first submitted before 10 November 2008.  Should you add the
disclaimer?
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.).


  Checking references for intended status: Proposed Standard

----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  == Outdated reference: A later version (-09) exists of
     draft-ietf-rmt-bb-lct-revised-07

  ** Obsolete normative reference: RFC 2327 (Obsoleted by RFC 4566)

  ** Downref: Normative reference to an Informational RFC: RFC 2357

  ** Downref: Normative reference to an Experimental RFC: RFC 2974

  -- Obsolete informational reference (is this intentional?): RFC 1889
     (Obsoleted by RFC 3550)

Yes, there is a difference between the draft submission check and the
full checks that the tools page provide. At publication request time I
do expect the draft be without real nits.

4. There are more references that are not updated. Cases where mechanism
are available in IETF draft, like the TESLA solution. Which would impact
the reference for example in Section 5, third paragraph.

5. Section 4.4:

"If immediate checking is possible and if the packet
   fails the check then the receiver MUST discard the packet and reduce
   its reception rate to a minimum before continuing to regulate its
   reception rate using the multiple rate congestion control."

Isn't the above instruction about reducing the rate based on packets
that fails authentication checks resulting in another DoS vector on the
receiver. If the only thing I need to do to keep the receiver at minimum
reception rate is to send the occasional packet that fails the checks
that seems extremely cheap. Can you please elaborate what the thoughts
where on this?

So in conclusion I think this document needs a work over and some
nailing down on what is mandatory to implement. I am expecting a revised ID.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From root@core3.amsl.com  Mon Apr 20 14:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: rmt@ietf.org
Delivered-To: rmt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 5EEF33A6ECA; Mon, 20 Apr 2009 14:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090420214501.5EEF33A6ECA@core3.amsl.com>
Date: Mon, 20 Apr 2009 14:45:01 -0700 (PDT)
Cc: rmt@ietf.org
Subject: [Rmt] I-D Action:draft-ietf-rmt-pi-norm-revised-10.txt
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: Mon, 20 Apr 2009 21:45:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Reliable Multicast Transport Working Group of the IETF.


	Title           : NACK-Oriented Reliable Multicast Protocol
	Author(s)       : B. Adamson, et al.
	Filename        : draft-ietf-rmt-pi-norm-revised-10.txt
	Pages           : 90
	Date            : 2009-04-20

This document describes the messages and procedures of the Negative-
ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) Protocol.
This protocol is designed to provide end-to-end reliable transport of
bulk data objects or streams over generic IP multicast routing and
forwarding services.  NORM uses a selective, negative acknowledgment
mechanism for transport reliability and offers additional protocol
mechanisms to allow for operation with minimal a priori coordination
among senders and receivers.  A congestion control scheme is
specified to allow the NORM protocol to fairly share available
network bandwidth with other transport protocols such as Transmission
Control Protocol (TCP).  It is capable of operating with both
reciprocal multicast routing among senders and receivers and with
asymmetric connectivity (possibly a unicast return path) between the
senders and receivers.  The protocol offers a number of features to
allow different types of applications or possibly other higher level
transport protocols to utilize its service in different ways.  The
protocol leverages the use of FEC-based repair and other IETF
reliable multicast transport (RMT) building blocks in its design.
This document obsoletes RFC 3940.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-revised-10.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-rmt-pi-norm-revised-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-04-20144426.I-D@ietf.org>


--NextPart--

From magnus.westerlund@ericsson.com  Tue Apr 21 05:41:29 2009
Return-Path: <magnus.westerlund@ericsson.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 AC3C33A6BB4 for <rmt@core3.amsl.com>; Tue, 21 Apr 2009 05:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.174
X-Spam-Level: 
X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 HDffoUuEvzc9 for <rmt@core3.amsl.com>; Tue, 21 Apr 2009 05:41:28 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 798093A6BAE for <rmt@ietf.org>; Tue, 21 Apr 2009 05:41:28 -0700 (PDT)
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id BDF4D20435; Tue, 21 Apr 2009 14:42:43 +0200 (CEST)
X-AuditID: c1b4fb3e-ad788bb000005486-6f-49edbf4393e0
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 8DD00203D7; Tue, 21 Apr 2009 14:42:43 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 21 Apr 2009 14:42:43 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 21 Apr 2009 14:42:43 +0200
Message-ID: <49EDBF43.5070408@ericsson.com>
Date: Tue, 21 Apr 2009 14:42:43 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: draft-ietf-rmt-pi-norm-revised@tools.ietf.org
References: <20090420214501.5EEF33A6ECA@core3.amsl.com>
In-Reply-To: <20090420214501.5EEF33A6ECA@core3.amsl.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 21 Apr 2009 12:42:43.0185 (UTC) FILETIME=[AA139E10:01C9C27E]
X-Brightmail-Tracker: AAAAAA==
Cc: rmt@ietf.org
Subject: Re: [Rmt] I-D Action:draft-ietf-rmt-pi-norm-revised-10.txt
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: Tue, 21 Apr 2009 12:41:29 -0000

Hi,


I hope that the WG has noticed the new IANA rules. These needs to be
reviewed.


What are the rules for addition to this registry?

7.1.3.  NORM_CMD Message Sub-types

   This document defines a namespace for "NORM_CMD" Message Sub-types
   named:

   "ietf:rmt:norm:command"

   It is possible that specifications extending NORM may wish to define
   additional "NORM_CMD" messages to enhance protocol functionality.
   The "NORM_CMD" sub-type field is an 8-bit value.  Note that the
   specification already provides for an "application-defined"
   "NORM_CMD" message sub-type that may be used at the discretion of
   individual applications using NORM for transport.  These
   "application-defined" commands may be suitable for many application-
   specific purposes and do not require standards action.  In any case,
   such additional messages SHALL be subject to the same congestion
   control constraints as the existing NORM sender message set.

   The current specification defines a number of "NORM_CMD" message sub-
   types that senders can use to signal the receivers in various aspects
   of NORM protocol operation.  This specification registers the
   following "NORM_CMD" Message Sub-types:

         +-------+-------------------------+--------------------+
         | Value | Name                    | Reference          |
         +-------+-------------------------+--------------------+
         | 1     | "NORM_CMD(FLUSH)"       | This specification |
         | 2     | "NORM_CMD(EOT)"         | This specification |
         | 3     | "NORM_CMD(SQUELCH)"     | This specification |
         | 4     | "NORM_CMD(CC)"          | This specification |
         | 5     | "NORM_CMD(REPAIR_ADV)"  | This specification |
         | 6     | "NORM_CMD(ACK_REQ)"     | This specification |
         | 7     | "NORM_CMD(APPLICATION)" | This specification |
         +-------+-------------------------+--------------------+




Then there is the ID nits that should be looked into. Please use the
tools webpage nits so you get all the nits. The submission tool does
only do a limited set of the checks.



  Miscellaneous warnings:

----------------------------------------------------------------------------

  == The document seems to lack the recommended RFC 2119 boilerplate,
even if
     it appears to use RFC 2119 keywords -- however, there's a paragraph
with
     a matching beginning. Boilerplate error?

     (The document does seem to have the reference to RFC 2119 which the
     ID-Checklist requires).

  Checking references for intended status: Proposed Standard

----------------------------------------------------------------------------

     (See RFCs 3967 and 4897 for information about using normative
references
     to lower-maturity documents in RFCs)

  == Unused Reference: 'RFC1112' is defined on line 4013, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC2119' is defined on line 4016, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC5226' is defined on line 4035, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC2357' is defined on line 4071, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC3048' is defined on line 4078, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC3269' is defined on line 4083, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC3940' is defined on line 4106, but no explicit
     reference was found in the text


3. Then there is a downref to the congestion control. Personally I am
fine with that, but I do have to do a new IETF last call with it being
explicitly mentioned.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From magnus.westerlund@ericsson.com  Thu Apr 23 04:31:27 2009
Return-Path: <magnus.westerlund@ericsson.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 5868A3A715B for <rmt@core3.amsl.com>; Thu, 23 Apr 2009 04:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.178
X-Spam-Level: 
X-Spam-Status: No, score=-6.178 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 CtN74SyjNmu5 for <rmt@core3.amsl.com>; Thu, 23 Apr 2009 04:31:26 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 3F31D3A6AED for <rmt@ietf.org>; Thu, 23 Apr 2009 04:31:26 -0700 (PDT)
Received: from mailgw3.ericsson.se (unknown [127.0.0.1]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id ADBBE222E3; Thu, 23 Apr 2009 13:32:09 +0200 (CEST)
X-AuditID: c1b4fb3c-ab7ccbb00000238f-14-49f047c3276a
Received: from esealmw126.eemea.ericsson.se (unknown [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id C86D223C20; Thu, 23 Apr 2009 12:49:39 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 23 Apr 2009 12:49:34 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 23 Apr 2009 12:49:34 +0200
Message-ID: <49F047BE.8060002@ericsson.com>
Date: Thu, 23 Apr 2009 12:49:34 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Brian Adamson <adamson@itd.nrl.navy.mil>
References: <249E4CD8-3D2D-4EBC-B745-C664B3BDF0AF@itd.nrl.navy.mil>
In-Reply-To: <249E4CD8-3D2D-4EBC-B745-C664B3BDF0AF@itd.nrl.navy.mil>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 23 Apr 2009 10:49:34.0657 (UTC) FILETIME=[309FF310:01C9C401]
X-Brightmail-Tracker: AAAAAA==
Cc: rmt@ietf.org
Subject: Re: [Rmt] IETF74 FCAST Action Item
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: Thu, 23 Apr 2009 11:31:27 -0000

Hi,

If the interest for this item is this low, I am very hesitant to approve
taking it on as WG item.

Cheers

Magnus

Brian Adamson skrev:
> Hello,
> 
> During discussions at the IETF74 RMT meeting, we concluded that we
> should poll the mailing list to determine if there is sufficient
> interest in adding the new FCAST document and pursuing it as an RMT
> working group item.  There was some interest expressed during the
> working group meeting and a number of folks raised their hands
> indicating they would review the document (i.e. we need broader
> participation than just the document authors!)
> 
> This message requests interested parties to respond on the mailing list
> to indicate their opinion on this:
> 
> 1) Do you think there is merit in the FCAST specification as an RMT WG
> item (or not)?
> 
> 2) Will you review the document so that we can rapidly finish it if it
> is accepted as a working group item?
> 
> 
> Thank you in advance for your responses to this query.
> 
> best regards,
> 
> 
> 
> 
> Brian Adamson
> adamson@itd.nrl.navy.mil
> 
> 
> 
> 
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www.ietf.org/mailman/listinfo/rmt
> 


-- 

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From root@core3.amsl.com  Fri Apr 24 11:15:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: rmt@ietf.org
Delivered-To: rmt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 0BC963A6C94; Fri, 24 Apr 2009 11:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090424181502.0BC963A6C94@core3.amsl.com>
Date: Fri, 24 Apr 2009 11:15:02 -0700 (PDT)
Cc: rmt@ietf.org
Subject: [Rmt] I-D Action:draft-ietf-rmt-pi-norm-revised-11.txt
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: Fri, 24 Apr 2009 18:15:02 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Reliable Multicast Transport Working Group of the IETF.


	Title           : NACK-Oriented Reliable Multicast Protocol
	Author(s)       : B. Adamson, et al.
	Filename        : draft-ietf-rmt-pi-norm-revised-11.txt
	Pages           : 91
	Date            : 2009-04-24

This document describes the messages and procedures of the Negative-
ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) Protocol.
This protocol is designed to provide end-to-end reliable transport of
bulk data objects or streams over generic IP multicast routing and
forwarding services.  NORM uses a selective, negative acknowledgment
mechanism for transport reliability and offers additional protocol
mechanisms to allow for operation with minimal a priori coordination
among senders and receivers.  A congestion control scheme is
specified to allow the NORM protocol to fairly share available
network bandwidth with other transport protocols such as Transmission
Control Protocol (TCP).  It is capable of operating with both
reciprocal multicast routing among senders and receivers and with
asymmetric connectivity (possibly a unicast return path) between the
senders and receivers.  The protocol offers a number of features to
allow different types of applications or possibly other higher level
transport protocols to utilize its service in different ways.  The
protocol leverages the use of FEC-based repair and other IETF
Reliable Multicast Transport (RMT) building blocks in its design.
This document obsoletes RFC 3940.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-revised-11.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-rmt-pi-norm-revised-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-04-24111451.I-D@ietf.org>


--NextPart--

From adamson@itd.nrl.navy.mil  Fri Apr 24 11:23:16 2009
Return-Path: <adamson@itd.nrl.navy.mil>
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 D2CD53A6BAE for <rmt@core3.amsl.com>; Fri, 24 Apr 2009 11:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 dki3SyzfdPSa for <rmt@core3.amsl.com>; Fri, 24 Apr 2009 11:23:11 -0700 (PDT)
Received: from s2.itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3]) by core3.amsl.com (Postfix) with ESMTP id 6F20328C22F for <rmt@ietf.org>; Fri, 24 Apr 2009 11:23:11 -0700 (PDT)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.8/8.13.8) with SMTP id n3OIOFYY017020; Fri, 24 Apr 2009 14:24:15 -0400
Received: from [192.168.1.202] ([132.250.218.64]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.16.48) with SMTP id M2009042414241523750 ; Fri, 24 Apr 2009 14:24:15 -0400
Message-Id: <FF836B55-D5AB-4F69-B358-43DFA2DC400E@itd.nrl.navy.mil>
From: Brian Adamson <adamson@itd.nrl.navy.mil>
To: rmt@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Fri, 24 Apr 2009 14:24:15 -0400
X-Mailer: Apple Mail (2.930.3)
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: [Rmt] NORM IANA Consideration update
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: Fri, 24 Apr 2009 18:23:16 -0000

RMT participants,

At the suggestion of IANA, the updated NORM draft includes language  
and registry information for additional IETF specifications to extend  
the NORM_CMD sub-type set.  Similarly the NORM Stream Control Code is  
discussed/registered in the IANA considerations as well.  Standards  
action is required to register these.

These registries will allow extension specifications to enhance NORM  
behavior (e.g., additional session control messaging, etc) in a more  
standardized manner than the built-in "application-defined  
commands" (which are still included and available for specific apps  
without standards action wr2 NORM required).

Since this is a notable addition, we felt it important to bring it to  
the working group's attention for any comments, objections, etc.   
There was no change to the protocol spec, just that these field values  
assignments were raised to IANA visibility.

Since the NORM document is in IESG review, a timely response is  
requested.

best regards,


Brian Adamson
adamson@itd.nrl.navy.mil





From wwwrun@core3.amsl.com  Mon Apr 27 06:56:43 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: rmt@ietf.org
Delivered-To: rmt@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 4EB8B3A6A22; Mon, 27 Apr 2009 06:56:43 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090427135643.4EB8B3A6A22@core3.amsl.com>
Date: Mon, 27 Apr 2009 06:56:43 -0700 (PDT)
Cc: rmt@ietf.org
Subject: [Rmt] Last Call: draft-ietf-rmt-pi-norm-revised (NACK-Oriented Reliable Multicast Protocol) to Proposed Standard
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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: Mon, 27 Apr 2009 13:56:43 -0000

The IESG has received a request from the Reliable Multicast Transport WG
(rmt) to consider the following document:

- 'NACK-Oriented Reliable Multicast Protocol '
   <draft-ietf-rmt-pi-norm-revised-11.txt> as a Proposed Standard

This document has a normative reference to RFC 4654, "TCP-Friendly
Multicast Congestion Control (TFMCC): Protocol Specification" an
Experimental RFC. Please consider the appropriateness of this downward
reference. See RFC 3967 for additional information about this. 

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-05-11. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-rmt-pi-norm-revised-11.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=13806&rfc_flag=0


From bushsf@research.ge.com  Mon Apr 27 12:59:29 2009
Return-Path: <bushsf@research.ge.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 ECF6028C17A for <rmt@core3.amsl.com>; Mon, 27 Apr 2009 12:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.07
X-Spam-Level: 
X-Spam-Status: No, score=-6.07 tagged_above=-999 required=5 tests=[AWL=0.528,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 x5spWAlrsrrW for <rmt@core3.amsl.com>; Mon, 27 Apr 2009 12:59:23 -0700 (PDT)
Received: from exprod5og108.obsmtp.com (exprod5og108.obsmtp.com [64.18.0.186]) by core3.amsl.com (Postfix) with ESMTP id 4ABC228C171 for <rmt@ietf.org>; Mon, 27 Apr 2009 12:59:23 -0700 (PDT)
Received: from source ([12.71.149.1]) (using TLSv1) by exprod5ob108.postini.com ([64.18.4.12]) with SMTP ID DSNKSfYO7ARot2IWeVSvLgHHaapwl8SfJapk@postini.com; Mon, 27 Apr 2009 13:00:45 PDT
Received: from unknown (HELO cinmlef06.e2k.ad.ge.com) ([3.159.213.37]) by Cinmlip06.e2k.ad.ge.com with ESMTP; 27 Apr 2009 15:58:39 -0400
Received: from CINMLVEM12.e2k.ad.ge.com ([3.159.214.57]) by cinmlef06.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 27 Apr 2009 15:58:39 -0400
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_01C9C772.8E8C9AA2"
Date: Mon, 27 Apr 2009 15:58:37 -0400
Message-ID: <328DC56CE839BA49BC31BEE66564C1EF0756899F@CINMLVEM12.e2k.ad.ge.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP: Nanoscale Networking Special Issue of AD HOC NETWORKS (ELSEVIER) JOURNAL
Thread-Index: AcnHco2eHGry2a/dTvGez6kXfrh/Fg==
From: "Bush, Stephen F (GE, Research)" <bushsf@research.ge.com>
To: "RMT" <rmt@ietf.org>
X-OriginalArrivalTime: 27 Apr 2009 19:58:39.0102 (UTC) FILETIME=[8EB251E0:01C9C772]
Subject: [Rmt] CFP: Nanoscale Networking Special Issue of AD HOC NETWORKS (ELSEVIER) JOURNAL
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: Mon, 27 Apr 2009 19:59:30 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9C772.8E8C9AA2
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


AD HOC NETWORKS (ELSEVIER) JOURNAL


=20

A Special Issue on=20

=20

"Nanoscale Networking"

=20

"There is plenty of room at the bottom" as Feynman presciently stated
about the atomic scale, and communication is needed down there. There is
a growing trend of results from diverse approaches that both leverages
and overcomes the environment at the nanoscale. These include molecular
motors, random carbon nanotube networks, calcium signaling, and quantum
networking to name a few. The goal of this issue is to focus upon ad hoc
networking at the nanoscale and thus is not seeking static
system-on-chip results unless they are in support of ad hoc nanoscale
network approaches. The following list provides example topics (in no
particular order):

*	Molecular Communication: Sparse-molecule communication,
molecular motors, calcium signaling, communication via diffusive
processes, single-nanotube radios, pheromones and stigmergic
communication, etc...=20
*	Quantum Communication Networks: Hybrid classical quantum
communication networks, repeaters, teleportation, entanglement swapping,
nanoscale photon detectors, quantum dot networks, networks and quantum
robotics, etc...=20
*	Applications for Nano-Networks: Wireless nanoscale transmitters
and receivers, nano-sensors and actuators, nanorobotics, medical and
in-vivo imaging and sensing, lab-on-a-chip, swarm micro- and
nano-inspection, embedding sensing, etc...=20
*	Modeling, Simulation, Standards and Architectural Aspects of
Nano-Networks: Physical characterization/modeling of nano-scale
interconnects and devices, fault-tolerant and reliability of
nano-devices, self-healing properties of nano-networks, energy
efficiency, bio-inspired aspects, etc...=20
*	Novel Information and Graph Theory Aspects of Nano-Networks:
Network architectures and topologies, statistical mechanics approach to
nano-communications, routing/addressing issues in nano-networks,
nano-coding, applications of complex network theory, self-organization
in nano-scale systems, modeling of nano/bio communication channels,
etc...=20
*	Device Physics and Interconnects: Nano-technologies and devices
for nanoscale biological and ad hoc network on-chip interconnects
(calcium signaling, molecular motors, CNTs, graphene nano-ribbons,
semic., metallic and DNA-templated nanowires), optical and wireless
interconnects, etc...=20
*	Nano-Robotics: Communication systems and networking protocols
for sub-inch robotic systems, including low-bandwidth coordination
schemes for nano-robot teams and range and bearing devices for
inter-robot relative positioning, etc...=20
*	Bio-nano Applications: Bio-micro/nanoelectronics, molecular
scale chemical and biosensors, bio-MEMS technology, data and power
management, nano-scale and molecular communications and information
processing, Information theory analysis of biological communications,
molecular computation using molecular cells, chemical computing, etc...

The list is not restrictive - authors are encouraged to contact the
editors before submitting a paper to determine whether the proposed
submission is within the scope of this Special Issue.

=20

Prospective authors should prepare their manuscripts according to the
guidelines in the Guide for Authors, found at
http://ees.elsevier.com/adhoc <http://www.elsevier.com/locate/comnet> ,
and submit them to the online submission and reviewing tool, at
http://www.editorialmanager.com/comnet
<http://www.editorialmanager.com/comnet> , choosing the Article Type:
SI-Nanoscale Networking.

=20

Important Dates

Paper Submission Deadline:       Sep 4, 2009

Notification:                              Feb 12, 2009=20

Revisions due:                           May 7, 2010

Final version due:                      Jul 9, 2010

Publication Date:                       2nd half 2010

=20

Guest Editor

Stephen F Bush, IEEE Nano-Scale, Molecular, and Quantum Networking
Committee Chair, (bushsf@research.ge.com)


------_=_NextPart_001_01C9C772.8E8C9AA2
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3527" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>
<H1 style=3D"MARGIN: 12pt 0in 3pt; TEXT-ALIGN: center" =
align=3Dcenter><FONT=20
size=3D5><SPAN style=3D"mso-ansi-language: EN-US; mso-fareast-language: =
EN-US">AD=20
HOC NETWORKS (ELSEVIER) JOURNAL</SPAN><SPAN=20
style=3D"FONT-WEIGHT: normal; mso-ansi-language: EN-US"><?xml:namespace =
prefix =3D o=20
ns =3D "urn:schemas-microsoft-com:office:office" =
/><o:p></o:p></SPAN></FONT></H1>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: center; mso-layout-grid-align: =
none"=20
align=3Dcenter><SPAN style=3D"FONT-SIZE: 16pt; mso-ansi-language: =
EN-US"><FONT=20
face=3D"Times New Roman">A Special Issue on =
<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: center; mso-layout-grid-align: =
none"=20
align=3Dcenter><SPAN style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: center; mso-layout-grid-align: =
none"=20
align=3Dcenter><SPAN style=3D"FONT-SIZE: 22pt; mso-ansi-language: =
EN-US"><FONT=20
face=3D"Times New Roman">&#8220;<B>Nanoscale=20
Networking&#8221;<o:p></o:p></B></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoBodyText style=3D"MARGIN: 0in 0in 0pt"><FONT face=3D"Times =
New Roman"=20
size=3D3>&#8220;There is plenty of room at the bottom&#8221; as Feynman =
presciently stated=20
about the atomic scale, and communication is needed down there. There is =
a=20
growing trend of results from diverse approaches that both leverages and =

overcomes the environment at the nanoscale. These include molecular =
motors,=20
random carbon nanotube networks, calcium signaling, and quantum =
networking to=20
name a few. The goal of this issue is to focus upon ad hoc networking at =
the=20
nanoscale and thus is <B>not</B> seeking static system-on-chip results =
unless=20
they are in support of ad hoc nanoscale network approaches. The =
following list=20
provides example topics (in no particular order):</FONT></P>
<UL type=3Ddisc>
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US">Molecular=20
  Communication</SPAN></B><B><SPAN lang=3DEL=20
  style=3D"FONT-SIZE: 11pt">:</SPAN></B><SPAN lang=3DEL =
style=3D"FONT-SIZE: 11pt">=20
  </SPAN><SPAN style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US">Sparse-molecule=20
  communication, molecular motors, calcium signaling, communication via=20
  diffusive processes</SPAN><SPAN lang=3DEL style=3D"FONT-SIZE: 11pt">, =
</SPAN><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US">single-nanotube =
radios,=20
  pheromones and </SPAN><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US">stigmergic=20
  communication, </SPAN><SPAN lang=3DEL style=3D"FONT-SIZE: 11pt">etc... =

  <o:p></o:p></SPAN></FONT>
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">Quantum=20
  Communication Networks:</SPAN></B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">=20
  Hybrid classical quantum communication networks, repeaters, =
teleportation,=20
  entanglement swapping, nanoscale photon detectors, quantum dot =
networks,=20
  networks&nbsp;and quantum robotics, etc... <o:p></o:p></SPAN></FONT>
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">Applications=20
  for Nano-Networks:</SPAN></B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt"> Wireless=20
  nanoscale transmitters and receivers, nano-sensors and actuators,=20
  nanorobotics, medical and in-vivo imaging and sensing, lab-on-a-chip, =
swarm=20
  micro</SPAN><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US">-</SPAN><SPAN =
lang=3DEL=20
  style=3D"FONT-SIZE: 11pt"> and nano-inspection, embedding sensing, =
etc...=20
  <o:p></o:p></SPAN></FONT>
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">Modeling,=20
  Simulation, Standards and Architectural Aspects of=20
  Nano-Networks:</SPAN></B><SPAN lang=3DEL style=3D"FONT-SIZE: 11pt"> =
Physical=20
  characterization/modeling of nano-scale interconnects and devices,=20
  fault-tolerant and reliability of nano-devices, self-healing =
properties of=20
  nano-networks, energy efficiency, bio-inspired aspects,=20
  etc...<o:p></o:p></SPAN></FONT>=20
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">Novel=20
  Information and Graph Theory Aspects of Nano-Networks:</SPAN></B><SPAN =
lang=3DEL=20
  style=3D"FONT-SIZE: 11pt"> Network architectures and topologies, =
statistical=20
  mechanics approach to nano-communications, routing/addressing issues =
in=20
  nano-networks, nano-coding, applications of complex network theory,=20
  self-organization in nano-scale systems, modeling of nano/bio =
communication=20
  channels, etc...<o:p></o:p></SPAN></FONT>=20
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">Device Physics=20
  and Interconnects:</SPAN></B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">=20
  Nano-technologies and devices for </SPAN><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US">nanoscale =
biological and ad=20
  hoc network </SPAN><SPAN lang=3DEL style=3D"FONT-SIZE: 11pt">on-chip =
interconnects=20
  (</SPAN><SPAN style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US">calcium=20
  signaling, molecular motors, </SPAN><SPAN lang=3DEL=20
  style=3D"FONT-SIZE: 11pt">CNTs, graphene nano-ribbons, semic., =
metallic and=20
  DNA-templated nanowires), optical and wireless interconnects, =
</SPAN><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US">etc&#8230;</SPAN><SPAN lang=3DEL=20
  style=3D"FONT-SIZE: 11pt"><o:p></o:p></SPAN></FONT>=20
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL=20
  style=3D"FONT-SIZE: 11pt">Nano-Robotics:</SPAN></B><SPAN lang=3DEL=20
  style=3D"FONT-SIZE: 11pt"> Communication systems and networking =
protocols for=20
  sub-inch robotic systems, including low-bandwidth coordination schemes =
for=20
  nano-robot teams and range and bearing devices for inter-robot =
relative=20
  positioning, etc...<o:p></o:p></SPAN></FONT>=20
  <LI class=3DMsoNormal=20
  style=3D"MARGIN: 0in 0in 0pt; tab-stops: list .5in; =
mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l2 =
level1 lfo5"><FONT=20
  face=3D"Times New Roman"><B><SPAN lang=3DEL style=3D"FONT-SIZE: =
11pt">Bio-nano=20
  Applications:</SPAN></B><SPAN lang=3DEL style=3D"FONT-SIZE: 11pt">=20
  Bio-micro/nanoelectronics, molecular scale chemical and biosensors, =
bio-MEMS=20
  technology, data and power management, nano-scale and molecular =
communications=20
  and information processing, Information theory analysis of biological=20
  communications, molecular computation using molecular cells, chemical=20
  computing, etc...</SPAN><SPAN=20
  style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US"><o:p></o:p></SPAN></FONT></LI></UL>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">The list is not restrictive - authors are =
encouraged to=20
contact the editors before submitting a paper to determine whether the =
proposed=20
submission is within the scope of this Special=20
Issue.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Prospective authors should prepare their =
manuscripts=20
according to the guidelines in the Guide for Authors, found at=20
</FONT></SPAN><SPAN lang=3DEL><A =
title=3Dhttp://www.elsevier.com/locate/comnet=20
href=3D"http://www.elsevier.com/locate/comnet"><SPAN=20
title=3Dhttp://www.elsevier.com/locate/comnet=20
style=3D"mso-field-code: 'HYPERLINK =
'http://ees.elsevier.com/adhoc''"><SPAN=20
lang=3DEN-US title=3Dhttp://www.elsevier.com/locate/comnet=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'; mso-ansi-language: =
EN-US; mso-fareast-language: =
EN-US">http://ees.elsevier.com/adhoc</SPAN></SPAN></A></SPAN><FONT=20
face=3D"Times New Roman"><SPAN style=3D"FONT-SIZE: 11pt; =
mso-ansi-language: EN-US">,=20
and submit them to the online submission and reviewing tool, at =
</SPAN><SPAN=20
lang=3DEL><A title=3Dhttp://www.editorialmanager.com/comnet=20
href=3D"http://www.editorialmanager.com/comnet"><SPAN lang=3DEN-US=20
title=3Dhttp://www.editorialmanager.com/comnet=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US">http://www.editorialmanager.com/comnet</SPAN></A></SPAN><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US">, choosing the =
Article Type:=20
</SPAN><B><SPAN style=3D"mso-ansi-language: EN-US"><FONT =
size=3D3>SI-Nanoscale=20
Networking</FONT></SPAN></B><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US">.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><B><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Important =
Dates<o:p></o:p></FONT></SPAN></B></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Paper Submission Deadline:<SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN>Sep 4,=20
2009<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Notification:<SPAN=20
style=3D"mso-spacerun: =
yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;</SPAN><SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SP=
AN>Feb=20
12, 2009 <o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Revisions due:<SPAN=20
style=3D"mso-spacerun: yes">&nbsp;&nbsp; </SPAN><SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN><SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN>May 7, 2010<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Final version due:<SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;<SPAN=20
class=3D296224019-27042009>&nbsp;&nbsp;&nbsp; </SPAN></SPAN>Jul 9,=20
2010<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">Publication Date:<SPAN=20
style=3D"mso-tab-count: 1">&nbsp;&nbsp;&nbsp;&nbsp;</SPAN><SPAN=20
style=3D"mso-tab-count: =
1">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;<SPAN=20
class=3D296224019-27042009>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</SP=
AN></SPAN>2<SUP>nd</SUP>=20
half 2010<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"><FONT=20
face=3D"Times New Roman">&nbsp;<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; TEXT-ALIGN: justify; =
mso-layout-grid-align: none"><FONT=20
face=3D"Times New Roman"><B><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US">Guest =
Editor</SPAN></B><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US"><o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal=20
style=3D"MARGIN: 0in 0in 0pt; mso-layout-grid-align: none"><FONT=20
face=3D"Times New Roman"><SPAN lang=3DNL=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: NL">Stephen F Bush, IEEE =
</SPAN><SPAN=20
class=3Dstyle81><SPAN lang=3DEL style=3D"FONT-SIZE: 11pt">Nano-Scale, =
Molecular, and=20
Quantum Networking</SPAN></SPAN><SPAN class=3Dstyle81><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: EN-US"> Committee=20
Chair</SPAN></SPAN><SPAN lang=3DNL=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: NL">,=20
(bushsf@research.ge.com)</SPAN></FONT><SPAN=20
style=3D"FONT-SIZE: 11pt; mso-ansi-language: =
EN-US"><o:p></o:p></SPAN></P></FONT></DIV></FONT></DIV></BODY></HTML>

------_=_NextPart_001_01C9C772.8E8C9AA2--

From adamson@itd.nrl.navy.mil  Tue Apr 28 07:04:58 2009
Return-Path: <adamson@itd.nrl.navy.mil>
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 7BA2228C24A for <rmt@core3.amsl.com>; Tue, 28 Apr 2009 07:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5mAvnsyT4kSf for <rmt@core3.amsl.com>; Tue, 28 Apr 2009 07:04:57 -0700 (PDT)
Received: from s2.itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3]) by core3.amsl.com (Postfix) with ESMTP id 97B4A28C10C for <rmt@ietf.org>; Tue, 28 Apr 2009 07:04:57 -0700 (PDT)
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.8/8.13.8) with SMTP id n3SE5llF020992; Tue, 28 Apr 2009 10:06:06 -0400
Received: from macsimus.itd.nrl.navy.mil ([132.250.92.151]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.16.48) with SMTP id M2009042810055403114 ; Tue, 28 Apr 2009 10:05:54 -0400
Message-Id: <BDFF86A4-AD92-4964-A0B1-886E73AD6B16@itd.nrl.navy.mil>
From: Brian Adamson <adamson@itd.nrl.navy.mil>
To: rmt@ietf.org, Magnus Westerlund <magnus.westerlund@ericsson.com>, Lorenzo Vicisano <lorenzo@vicisano.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Tue, 28 Apr 2009 10:05:54 -0400
X-Mailer: Apple Mail (2.930.3)
Subject: [Rmt] FLUTE errata check
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: Tue, 28 Apr 2009 14:04:58 -0000

As we discussed at the RMT working group meeting, I checked that the  
revised FLUTE spec addressed the errata reported for RFC 3926.  The  
appropriate sections seem to have been updated and edited and the  
various references updated and/or removed accordingly.  So, it appears  
to me that this issue has been addressed in the revised FLUTE draft.


Brian Adamson
adamson@itd.nrl.navy.mil





From rfc-editor@rfc-editor.org  Tue Apr 28 16:56:10 2009
Return-Path: <rfc-editor@rfc-editor.org>
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 DCEAC3A6BA6; Tue, 28 Apr 2009 16:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.923
X-Spam-Level: 
X-Spam-Status: No, score=-16.923 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 0KaBUGd5ax6e; Tue, 28 Apr 2009 16:56:10 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 82E2B3A6C7F; Tue, 28 Apr 2009 16:56:03 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id CEB7A293E4C; Tue, 28 Apr 2009 16:54:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090428235439.CEB7A293E4C@bosco.isi.edu>
Date: Tue, 28 Apr 2009 16:54:39 -0700 (PDT)
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 5510 on Reed-Solomon Forward Error Correction (FEC) Schemes
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: Tue, 28 Apr 2009 23:56:10 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5510

        Title:      Reed-Solomon Forward Error Correction (FEC) 
                    Schemes 
        Author:     J. Lacan, V. Roca,
                    J. Peltotalo, S. Peltotalo
        Status:     Standards Track
        Date:       April 2009
        Mailbox:    jerome.lacan@isae.fr, 
                    vincent.roca@inria.fr, 
                    jani.peltotalo@tut.fi,  sami.peltotalo@tut.fi
        Pages:      28
        Characters: 57493
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-bb-fec-rs-05.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5510.txt

This document describes a Fully-Specified Forward Error Correction
(FEC) Scheme for the Reed-Solomon FEC codes over GF(2^^m), where m is
in {2..16}, and its application to the reliable delivery of data
objects on the packet erasure channel (i.e., a communication path
where packets are either received without any corruption or discarded
during transmission).  This document also describes a Fully-Specified
FEC Scheme for the special case of Reed-Solomon codes over GF(2^^8)
when there is no encoding symbol group.  Finally, in the context of
the Under-Specified Small Block Systematic FEC Scheme (FEC Encoding
ID 129), this document assigns an FEC Instance ID to the special case
of Reed-Solomon codes over GF(2^^8).

Reed-Solomon codes belong to the class of Maximum Distance Separable
(MDS) codes, i.e., they enable a receiver to recover the k source
symbols from any set of k received symbols.  The schemes described
here are compatible with the implementation from Luigi Rizzo.  
[STANDARDS TRACK]

This document is a product of the Reliable Multicast Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From gf@erg.abdn.ac.uk  Wed Apr 29 00:36:39 2009
Return-Path: <gf@erg.abdn.ac.uk>
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 C9F363A6E6F for <rmt@core3.amsl.com>; Wed, 29 Apr 2009 00:36:39 -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 WcAG-Btkuu1j for <rmt@core3.amsl.com>; Wed, 29 Apr 2009 00:36:39 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 3F8383A6C2E for <rmt@ietf.org>; Wed, 29 Apr 2009 00:36:04 -0700 (PDT)
Received: from Gorry-Fairhursts-Laptop-6.local (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n3T7bMVn001578 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Apr 2009 08:37:23 +0100 (BST)
Message-ID: <49F803B2.5040503@erg.abdn.ac.uk>
Date: Wed, 29 Apr 2009 08:37:22 +0100
From: Gorry Fairhurst <gf@erg.abdn.ac.uk>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: rmt@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gf@erg.abdn.ac.uk
Subject: [Rmt]  IETF74 FCAST Action Item
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: Wed, 29 Apr 2009 07:36:39 -0000

I've been on vacation and then catching-up, forgive the delay - this is 
anyway a repeat of what I said earlier.

 > 1) Do you think there is merit in the FCAST specification as an RMT
 > WG item (or not)?

As I said in the working group meeting, I would support this.

To me FLUTE is a useful spec that has been deployed, but when we 
scheduled RMT as a work item we envisaged a building block approach. I 
guess we are also wiser now, and we can provide a leaner more targeted 
specification?

I think having more than one spec would be good, especially if this 
stimulated some IPR-free development work, but do not myself currently 
plan an implementation.

 > 2) Will you review the document so that we can rapidly finish it if
 > it is accepted as a working group item?

Yes, I have reviewed the current draft, and I found it reasonably mature 
- it seems time to take on wider inputs from others in the WG.

I'd be happy to review further revisions of this document.

Gorry

From magnus.westerlund@ericsson.com  Wed Apr 29 05:46:58 2009
Return-Path: <magnus.westerlund@ericsson.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 2CCFD3A6940 for <rmt@core3.amsl.com>; Wed, 29 Apr 2009 05:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.181
X-Spam-Level: 
X-Spam-Status: No, score=-6.181 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
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 E8aSz9gG9LRH for <rmt@core3.amsl.com>; Wed, 29 Apr 2009 05:46:50 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id C7C893A688C for <rmt@ietf.org>; Wed, 29 Apr 2009 05:46:49 -0700 (PDT)
X-AuditID: c1b4fb3e-b7bb8ae000006a07-f9-49f84c8ad5c3
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 70.82.27143.A8C48F94; Wed, 29 Apr 2009 14:48:10 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 29 Apr 2009 14:47:09 +0200
Received: from [147.214.183.173] ([147.214.183.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 29 Apr 2009 14:47:09 +0200
Message-ID: <49F84C4D.1070206@ericsson.com>
Date: Wed, 29 Apr 2009 14:47:09 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "rmt@ietf.org" <rmt@ietf.org>
X-Enigmail-Version: 0.95.7
Content-Type: multipart/mixed; boundary="------------050900080004050508030309"
X-OriginalArrivalTime: 29 Apr 2009 12:47:09.0816 (UTC) FILETIME=[9C4E4780:01C9C8C8]
X-Brightmail-Tracker: AAAAAA==
Subject: [Rmt] [Fwd: Gen-ART review of draft-ietf-rmt-bb-lct-revised-09]
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: Wed, 29 Apr 2009 12:46:58 -0000

This is a multi-part message in MIME format.
--------------050900080004050508030309
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

For your information.

I do expect the authors to take also these comments into account and
respond to the reviewer.

Cheers

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

--------------050900080004050508030309
Content-Type: message/rfc822;
 name="Gen-ART review of draft-ietf-rmt-bb-lct-revised-09.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="Gen-ART review of draft-ietf-rmt-bb-lct-revised-09.eml"

Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by esealmw103.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 27 Apr 2009 22:47:19 +0200
Received: from mailgw1.ericsson.se ([193.180.251.45]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);
	 Mon, 27 Apr 2009 22:47:19 +0200
X-AuditID: c1b4fb2d-b7bfcae00000634c-47-49f619d65f0a
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194])
	by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 0D.98.25420.6D916F94; Mon, 27 Apr 2009 22:47:19 +0200 (CEST)
Received: from S73602b (w173.z064002096.dfw-tx.dsl.cnc.net [64.2.96.173])
	by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis)
	id 0MKpCa-1LyXin2PET-000ckc; Mon, 27 Apr 2009 16:46:45 -0400
Message-ID: <8A564F7D29F542F29B9C9DA00D55614B@china.huawei.com>
From: "Spencer Dawkins" <spencer@wonderhamster.org>
To: "Michael Luby" <luby@qualcomm.com>,
	"Mark Watson" <watson@qualcomm.com>,
	"Lorenzo Vicisano" <vicisano@qualcomm.com>
Cc: <ietf@ietf.org>,
	"General Area Review Team" <gen-art@ietf.org>,
	"Magnus Westerlund" <magnus.westerlund@ericsson.com>,
	"Brian Adamson" <adamson@itd.nrl.navy.mil>
Subject: Gen-ART review of draft-ietf-rmt-bb-lct-revised-09
Date: Mon, 27 Apr 2009 15:46:16 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Provags-ID: V01U2FsdGVkX1/iu3rQ84oNPKg5iZFu35LfIf0plt59zTkl6Ts
 OhZ4oPWgldvDNBFkflBna+8vILZ/E7hhKvkyX8nNhf0HtcPjaR
 ANc1D0YWKZ1vHcDtgf2A21oHVX77+Qe2NUi/6Kl2DY=
X-Brightmail-Tracker: AAAAAg1fNrUOgkFm
Return-Path: spencer@wonderhamster.org
X-OriginalArrivalTime: 27 Apr 2009 20:47:19.0166 (UTC) FILETIME=[5B30B9E0:01C9C779]

I have been selected as the General Area Review Team (Gen-ART)
reviewer for this draft (for background on Gen-ART, please see
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-rmt-bb-lct-revised-09
Reviewer: Spencer Dawkins
Review Date: 2009-04-27
IETF LC End Date: 2009-04-15 (sorry! "along with any other LATE Last Call 
comments...")
IESG Telechat date: (not known)

Summary: This specification is almost ready for publication as a Proposed 
Standard. I have a couple of minor questions (below). I've also included a 
small number of nits, but this draft is very clean on that score.

Comments:

Abstract

   Layered Coding Transport (LCT) provides transport level support for
   reliable content delivery and stream delivery protocols.  LCT is
   specifically designed to support protocols using IP multicast, but
   also provides support to protocols that use unicast.  LCT is
   compatible with congestion control that provides multiple rate
   delivery to receivers and is also compatible with coding techniques
   that provide reliable delivery of content.  This document obsoletes
   RFC3451

Spencer (nit): it would be great if the abstract used the word "building 
block"... OBTW, there's a missing period after "RFC3451".

1.  Introduction

   Layered Coding Transport provides transport level support for

Spencer (nit): it would be good to provide "Layered Coding Transport (LCT)" 
somewhere around here - the next section of the document just starts using 
the abbreviation with no expansion...

   reliable content delivery and stream delivery protocols.  Layered
   Coding Transport is specifically designed to support protocols using
   IP multicast, but also provides support to protocols that use
   unicast.  Layered Coding Transport is compatible with congestion
   control that provides multiple rate delivery to receivers and is also
   compatible with coding techniques that provide reliable delivery of
   content.

   RFC3451 [RFC3451], which is obsoleted by this document, contained a
   previous versions of the protocol.  RFC3451 was published in the

Spencer (nit): s/versions/version/? but this section of the document wobbles 
back and forth between singular ("this document") and plural ("these 
specifications") - maybe clear to someone who's followed the working group 
for a while, but less clear to me...

   "Experimental" category.  It was the stated intent of the RMT working
   group to re-submit these specifications as an IETF Proposed Standard
   in due course.

4.  Applicability

   Before joining a session, the receivers MUST obtain enough of the
   session description to start the session.  This MUST include the

Spencer (minor): I don't think this two are 2119 MUSTs ... based on the 
previous sentence, I'd just s/MUST// the first one completely, but they 
should be at least lower-cased...

   relevant session parameters needed by a receiver to participate in
   the session, including all information relevant to congestion
   control.  The session description is determined by the sender, and is
   typically communicated to the receivers out-of-band.  In some cases,
   as described later, parts of the session description that are not
   required to initiate a session MAY be included in the LCT header or
   communicated to a receiver out-of-band after the receiver has joined
   the session.

4.1.  Environmental Requirements and Considerations

   LCT channels and SSM channels coincide, and thus the receiver will
   only receive packets sent to the requested LCT channel.  With ASM,
   the receiver joins an LCT channel by joining a multicast group G, and
   all packets sent to G, regardless of the sender, may be received by
   the receiver.  Thus, SSM has compelling security advantages over ASM
   for prevention of denial of service attacks.  In either case,
   receivers SHOULD use mechanisms to filter out packets from unwanted
   sources.

Spencer (minor): I'm confused by this. I would have thought that ASM wasn't 
so easily filtered in many cases (SSM, sure) - based on the source address, 
which could be coming from anywhere? Is this a membership check?

8.3.  Congestion control issues

   A receiver with an incorrect implementation of a multiple rate
   congestion control building block may affect health of the network in
   the path between the sender and the receiver, and may also affect the
   reception rates of other receivers joined to the session.

   Protocol Instantiations could address this issue by requiring
   receivers to identify themselves as legitimate before they receive
   the Session Description needed to join the session.

Spencer (minor): I'm sorry, but I don't understand what's being suggested 
here. Could you provide any guidance about how a sender could "identify a 
receiver as legitimate"? Is this authentication? If so, what's being 
authenticated - an implementation? I may not understand how this would 
address the issue of incorrect implementations, either, but let's start with 
the first question ;-) 




--------------050900080004050508030309--

From budden@nps.edu  Wed Apr 29 12:46:54 2009
Return-Path: <budden@nps.edu>
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 07B2A3A7188 for <rmt@core3.amsl.com>; Wed, 29 Apr 2009 12:46:54 -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=[AWL=0.000,  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 nWv+X-bJM4lX for <rmt@core3.amsl.com>; Wed, 29 Apr 2009 12:46:53 -0700 (PDT)
Received: from virginia.nps.edu (virginia.nps.edu [205.155.65.15]) by core3.amsl.com (Postfix) with ESMTP id 6A77B3A6F24 for <rmt@ietf.org>; Wed, 29 Apr 2009 12:46:20 -0700 (PDT)
Received: from localhost.localdomain ([172.20.57.107]) by virginia.nps.edu with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 Apr 2009 12:47:42 -0700
Message-ID: <49F8AF10.2070903@nps.navy.mil>
Date: Wed, 29 Apr 2009 12:48:32 -0700
From: Rex Buddenberg <budden@nps.navy.mil>
User-Agent: Thunderbird 2.0.0.21 (X11/20090320)
MIME-Version: 1.0
To: rmt@ietf.org
References: <249E4CD8-3D2D-4EBC-B745-C664B3BDF0AF@itd.nrl.navy.mil> <49F047BE.8060002@ericsson.com>
In-Reply-To: <49F047BE.8060002@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Apr 2009 19:47:42.0510 (UTC) FILETIME=[5C29D4E0:01C9C903]
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Re: [Rmt] IETF74 FCAST Action Item
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: Wed, 29 Apr 2009 19:46:54 -0000

Poll response: I think there is indeed merit.  Worthwhile WG item.


At the risk of overkill, here are some of my reasons and rationale:

My comments have to do with the utility of FCAST (and NORM) in military 
and emergency services environments.  If I get this right, it will be a 
translation from operational needs into protocol requirements.


Traffic observation.  A much higher percentage of traffic  in the 
military/EMS world is multicast  than in the civilian world.  We have 
acronyms like BFT (blue force track, asset tracking), COP (common 
operational picture), chat, APB (all points bulletin, from the TV 
shows), and CAP -- common alerting protocol -- which should give you an 
idea of how ubiquitous multicast data is.
Conversely, all of this entails extension of the internet to mobile 
platforms so we suffer a 10*4 decrease in bandwidth at the radio-WAN.  
The only offset to that bandwidth constriction is the fact that the 
media is a shared one -- the ether.

That much rationale should convince that multicast is a good idea -- the 
demand side and supply side arguments intersect.  Further, we have to 
cover multicast at all layers of the ISO reference model (application 
layer included) in order to get the benefit.  Multicast at layers 1-4 
provides no relief if the applications don't use it.


One of the banes of military 'data links' is that they do not include 
meta data in the data stream.  Compounded by the fact that the data 
dictionary (format) is usually in the same spec as the communications 
specification.   This, coupled with the fact that the data dictionaries 
between any two information systems don't coincide yields all kinds of 
interoperability difficulties.  This leads to phenomena where a single 
physical object (a ship) is reported by several different sensor/comms 
lashups to a common operational plot where it shows up as several 
objects (one appearance per sensor/comms instantiation).   Is it any 
wonder that the users don't trust it?  Modularizing communications and 
data away from each other is a core interoperability problem.  Including 
the meta data in the data stream is one very good means of accomplishing 
that end.

Therefore, the basic ideas in FCAST are good and necessary.


But there's more.  Look at the problem from the data point of view 
rather than the comms (internet) one for a moment.  There is 
considerable work in object-orienting data.  I know of three initiatives 
out there worth mentioning:

XMPP.  Chat implementations have flowered like the proverbial Czech 
springtime.  Many were not interoperable with each other and none 
carried object security (vital).  DISA has latched onto XMPP as the 
common denominator.  We shouldn't have too much trouble figuring out 
that a multicast-based chat implementation has many benefits over the 
current server-centric model, both in terms of robustness and bandwidth 
conservation.

Cursor on Target.  Object oriented data format that uses XML as the 
tagging means (small step from the MIME typing mentioned in FCAST).  
There are several things wrong with Cursor on Target, lack of 
authenticity being one of them.  But for this discussion, the most 
egregious one is that there's no 'envelope' specified for Cursor o 
meritn Target messages (e.g.e-mail). I can't read the Cursor on Target 
specification and point to any layer 6/7 protocols.

Common Alerting Protocol.  Over the years, several means of warning the 
public, and alerting emergency services, have evolved.  Many are 
stovepipes (remember the TV warnings about nuclear attack?).  CAP is 
designed to get past the stovepipes by specifying an XML-based schema 
that modularizes both the message and the meta-data away from the 
communications means of delivery.  Many of the FCAST I-D para 4.1 items 
also appear (object time validity, for example)  in the CAP schema.  CAP 
also eschews  specifying a 'wrapper' or 'envelope' -- considered outside 
scope.


Somewhere between a layer 6/7 protocol and MIME/XML-based data formats 
we will need a careful modularization boundary ... don't have a complete 
interoperability solution without it.






Magnus Westerlund wrote:
> Hi,
>
> If the interest for this item is this low, I am very hesitant to approve
> taking it on as WG item.
>
> Cheers
>
> Magnus
>
> Brian Adamson skrev:
>   
>> Hello,
>>
>> During discussions at the IETF74 RMT meeting, we concluded that we
>> should poll the mailing list to determine if there is sufficient
>> interest in adding the new FCAST document and pursuing it as an RMT
>> working group item.  There was some interest expressed during the
>> working group meeting and a number of folks raised their hands
>> indicating they would review the document (i.e. we need broader
>> participation than just the document authors!)
>>
>> This message requests interested parties to respond on the mailing list
>> to indicate their opinion on this:
>>
>> 1) Do you think there is merit in the FCAST specification as an RMT WG
>> item (or not)?
>>
>> 2) Will you review the document so that we can rapidly finish it if it
>> is accepted as a working group item?
>>
>>
>> Thank you in advance for your responses to this query.
>>
>> best regards,
>>
>>
>>
>>
>> Brian Adamson
>> adamson@itd.nrl.navy.mil
>>
>>
>>
>>
>> _______________________________________________
>> Rmt mailing list
>> Rmt@ietf.org
>> https://www.ietf.org/mailman/listinfo/rmt
>>
>>     
>
>
>   

-- 
Rex Buddenberg
Senior Lecturer
Naval Postgraduate School
Monterey, Ca 93943
831/656-3576

