
From Rod.Walsh@nokia.com  Mon Jun  1 02:47:36 2009
Return-Path: <Rod.Walsh@nokia.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 8E6D828C10C for <rmt@core3.amsl.com>; Mon,  1 Jun 2009 02:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.109
X-Spam-Level: 
X-Spam-Status: No, score=-5.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 DZgNmq6PyaBR for <rmt@core3.amsl.com>; Mon,  1 Jun 2009 02:47:30 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 18F4628C0F0 for <rmt@ietf.org>; Mon,  1 Jun 2009 02:47:29 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n519l885013952; Mon, 1 Jun 2009 12:47:21 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 1 Jun 2009 12:47:05 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 1 Jun 2009 12:47:05 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Mon, 1 Jun 2009 11:47:05 +0200
From: <Rod.Walsh@nokia.com>
To: <watson@qualcomm.com>, <magnus.westerlund@ericsson.com>, <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, <rmt@ietf.org>
Date: Mon, 1 Jun 2009 11:47:02 +0200
Thread-Topic: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06
Thread-Index: Acm/d3BeHeVlJKLRTXm6l2idwHzzSAT6Qn/iA89b6EY=
Message-ID: <C6497E46.83BB%rod.walsh@nokia.com>
In-Reply-To: <C62F6020.2D01A%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_C6497E4683BBrodwalshnokiacom_"
MIME-Version: 1.0
X-OriginalArrivalTime: 01 Jun 2009 09:47:05.0632 (UTC) FILETIME=[EC246200:01C9E29D]
X-Nokia-AV: Clean
Subject: Re: [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: Mon, 01 Jun 2009 09:47:36 -0000

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

Hi All

Perhaps the WEBRC mandating suggestion is not the right response on CC...
>> "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 sca=
le sessions. Why isn't this a required to implement feature?"
> "If I understand the WG discussion correctly, we should mandate the suppo=
rt of WEBRC for Congestion Control."

I feel that this (paraphrased) answer is not ideal "Oh, we didn't see that =
mass of RFC text about CC needs for multicast from around the time RMT was =
first chartered, how foolish, let's mandate WEBRCC now." (Mark, I hope you'=
ve still got the sense of humor to take this poke with a smile from fortres=
s QC? :)

So I humbly suggest some assimilated form of this as the answer..
"Most of the practitioners of ALC protocols have found the greatest use of =
ALC in unidirectional fully provisioned (as a lower layer) channels such as=
 3GPP-MBMS and DVB-H. In these fully provisioned cases where the ALC packet=
s are not subsequently forwarded, unmodified, from receivers to the open in=
ternet, a layer 3 or 4 CC mechanism is both redundant and potentially expen=
sive. It is highly unlikely that a mandated one would be adopted in DVB and=
 3GPP for these kinds of applications, so mandating that in the ALC RFC may=
 well lead to the SDO fragmentation that was previously diligently avoided =
through the hard work of RMT contributors. To provide for this 'practical a=
pplication to broadcast' and 'flexible use on the open internet' dual natur=
e of ALC CC, FLUTE originally had text that explicatively stated that no CC=
 block was required in the case described above, but a CC block was require=
d otherwise - but didn't mandate any CC instance - at that time WEBRC was t=
he only IETF published candidate. At that time, the lack of wide scale impl=
ementation, interoperability maturing and performance validation led us to =
actively choose not to mandate WEBRC, though we did originally reference it=
. Several years have passed since those decisions and the MBMS and DVB-H ap=
plications characteristics remain the same, in the mean time the validity o=
f WEBRC has not been disproven. So perhaps spec text along the lines of the=
 original FLUTE text would be ideal."

The only caveat I have on this is the state of WEBRC. When proposed is was =
a brilliant contribution, in the time since how many distinct works have va=
lidated implementability or other performance metrics? If there is a high l=
evel of WG confidence, making it mandatory in the "forward to open internet=
" case sounds sensible, otherwise not.

(And apologies if I just arrived at the conversation midway through and tot=
ally misjudged the context - my 6 monthly RMT email review just came up, so=
 my flow with RMT is not ideal either :)

Cheers, Rod.


On 13/05/2009 03:19, "ext Watson, Mark" <watson@qualcomm.com> wrote:

> 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.
>

If I understand the WG discussion correctly, we should mandate the support
of WEBRC for Congestion Control. I propose to replace the first sentence of
section 2.2 (Multiple Rate Congestion Control Building Block) with

"At a minimum, implementations of ALC MUST support [RFC3738]."

And reword the following paragraphs appropriately.

For security, as with NORM, we have text defining 'Baseline secure ALC
operation'. Do you think we should mandate support for this ?

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

<HTML>
<HEAD>
<TITLE>Re: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Hi All<BR>
<BR>
Perhaps the WEBRC mandating suggestion is not the right response on CC...<B=
R>
&gt;&gt; &#8220;For example the choice of congestion control algorithm. I t=
hink 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?&#8=
221;<BR>
&gt; &#8220;If I understand the WG discussion correctly, we should mandate =
the support of WEBRC for Congestion Control.&#8221;<BR>
<BR>
I feel that this (paraphrased) answer is not ideal &#8220;Oh, we didn&#8217=
;t see that mass of RFC text about CC needs for multicast from around the t=
ime RMT was first chartered, how foolish, let&#8217;s mandate WEBRCC now.&#=
8221; (Mark, I hope you&#8217;ve still got the sense of humor to take this =
poke with a smile from fortress QC? :)<BR>
<BR>
So I humbly suggest some assimilated form of this as the answer..<BR>
&#8220;Most of the practitioners of ALC protocols have found the greatest u=
se of ALC in unidirectional fully provisioned (as a lower layer) channels s=
uch as 3GPP-MBMS and DVB-H. In these fully provisioned cases where the ALC =
packets are not subsequently forwarded, unmodified, from receivers to the o=
pen internet, a layer 3 or 4 CC mechanism is both redundant and potentially=
 expensive. It is highly unlikely that a mandated one would be adopted in D=
VB and 3GPP for these kinds of applications, so mandating that in the ALC R=
FC may well lead to the SDO fragmentation that was previously diligently av=
oided through the hard work of RMT contributors. To provide for this &#8216=
;practical application to broadcast&#8217; and &#8216;flexible use on the o=
pen internet&#8217; dual nature of ALC CC, FLUTE originally had text that e=
xplicatively stated that no CC block was required in the case described abo=
ve, but a CC block was required otherwise &#8211; but didn&#8217;t mandate =
any CC instance &#8211; at that time WEBRC was the only IETF published cand=
idate. At that time, the lack of wide scale implementation, interoperabilit=
y maturing and performance validation led us to actively choose not to mand=
ate WEBRC, though we did originally reference it. Several years have passed=
 since those decisions and the MBMS and DVB-H applications characteristics =
remain the same, in the mean time the validity of WEBRC has not been dispro=
ven. So perhaps spec text along the lines of the original FLUTE text would =
be ideal.&#8221;<BR>
<BR>
The only caveat I have on this is the state of WEBRC. When proposed is was =
a brilliant contribution, in the time since how many distinct works have va=
lidated implementability or other performance metrics? If there is a high l=
evel of WG confidence, making it mandatory in the &#8220;forward to open in=
ternet&#8221; case sounds sensible, otherwise not.<BR>
<BR>
(And apologies if I just arrived at the conversation midway through and tot=
ally misjudged the context &#8211; my 6 monthly RMT email review just came =
up, so my flow with RMT is not ideal either :)<BR>
<BR>
Cheers, Rod.<BR>
<BR>
<BR>
On 13/05/2009 03:19, &quot;ext Watson, Mark&quot; &lt;<a href=3D"watson@qua=
lcomm.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'>&gt; Hi,<BR>
&gt;<BR>
&gt; I have reviewed the ALC PI and have some comments.<BR>
&gt;<BR>
&gt; 1. If one compare this one with the experimental one they are very<BR>
&gt; similar. At least my expectation would be that a bit more details are<=
BR>
&gt; actually nailed down on how one should do them to achieve interoperabl=
e<BR>
&gt; implementations. For example the choice of congestion control algorith=
m.<BR>
&gt; I think we only have one that we can really use to satisfy the intende=
d<BR>
&gt; usage of large scale sessions. Why isn't this a required to implement<=
BR>
&gt; feature?<BR>
&gt;<BR>
&gt; The same thing can be said about normative to implement security<BR>
&gt; features. Yes, here there are choices, but still specify one required =
to<BR>
&gt; implement should be possible. If you have observant the NORM PI got th=
is<BR>
&gt; comment from the SECdir reviewer. And I think he was right, we should =
be<BR>
&gt; clear on these.<BR>
&gt;<BR>
&gt; A question is if we need to specify one mandatory to implement FEC<BR>
&gt; encoding?<BR>
&gt;<BR>
&gt; In general I am not against the flexibility the protocol allows for.<B=
R>
&gt; However, it should be clear what you do need to implement for a<BR>
&gt; base-line implementation.<BR>
&gt;<BR>
<BR>
If I understand the WG discussion correctly, we should mandate the support<=
BR>
of WEBRC for Congestion Control. I propose to replace the first sentence of=
<BR>
section 2.2 (Multiple Rate Congestion Control Building Block) with<BR>
<BR>
&quot;At a minimum, implementations of ALC MUST support [RFC3738].&quot;<BR=
>
<BR>
And reword the following paragraphs appropriately.<BR>
<BR>
For security, as with NORM, we have text defining 'Baseline secure ALC<BR>
operation'. Do you think we should mandate support for this ?<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C6497E4683BBrodwalshnokiacom_--

From magnus.westerlund@ericsson.com  Mon Jun  1 03:02:22 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 87BE93A6F12 for <rmt@core3.amsl.com>; Mon,  1 Jun 2009 03:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[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 u--jDHiGnzwD for <rmt@core3.amsl.com>; Mon,  1 Jun 2009 03:02:18 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 1826C3A6EE2 for <rmt@ietf.org>; Mon,  1 Jun 2009 03:02:17 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b78ae000007894-c5-4a23a7289fce
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 30.F5.30868.827A32A4; Mon,  1 Jun 2009 12:02:16 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 1 Jun 2009 12:00:51 +0200
Received: from [147.214.183.61] ([147.214.183.61]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 1 Jun 2009 12:00:51 +0200
Message-ID: <4A23A6D3.9040508@ericsson.com>
Date: Mon, 01 Jun 2009 12:00:51 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Rod.Walsh@nokia.com
References: <C6497E46.83BB%rod.walsh@nokia.com>
In-Reply-To: <C6497E46.83BB%rod.walsh@nokia.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 01 Jun 2009 10:00:51.0399 (UTC) FILETIME=[D8566D70:01C9E29F]
X-Brightmail-Tracker: AAAAAA==
Cc: draft-ietf-rmt-pi-alc-revised@tools.ietf.org, watson@qualcomm.com, rmt@ietf.org
Subject: Re: [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: Mon, 01 Jun 2009 10:02:22 -0000

Rod.Walsh@nokia.com skrev:
> Hi All
> 
> Perhaps the WEBRC mandating suggestion is not the right response on CC...
>>> “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?”
>> “If I understand the WG discussion correctly, we should mandate the
> support of WEBRC for Congestion Control.”
> 
> I feel that this (paraphrased) answer is not ideal “Oh, we didn’t see
> that mass of RFC text about CC needs for multicast from around the time
> RMT was first chartered, how foolish, let’s mandate WEBRCC now.” (Mark,
> I hope you’ve still got the sense of humor to take this poke with a
> smile from fortress QC? :)
> 
> So I humbly suggest some assimilated form of this as the answer..
> “Most of the practitioners of ALC protocols have found the greatest use
> of ALC in unidirectional fully provisioned (as a lower layer) channels
> such as 3GPP-MBMS and DVB-H. In these fully provisioned cases where the
> ALC packets are not subsequently forwarded, unmodified, from receivers
> to the open internet, a layer 3 or 4 CC mechanism is both redundant and
> potentially expensive. It is highly unlikely that a mandated one would
> be adopted in DVB and 3GPP for these kinds of applications, so mandating
> that in the ALC RFC may well lead to the SDO fragmentation that was
> previously diligently avoided through the hard work of RMT contributors.
> To provide for this ‘practical application to broadcast’ and ‘flexible
> use on the open internet’ dual nature of ALC CC, FLUTE originally had
> text that explicatively stated that no CC block was required in the case
> described above, but a CC block was required otherwise – but didn’t
> mandate any CC instance – at that time WEBRC was the only IETF published
> candidate. At that time, the lack of wide scale implementation,
> interoperability maturing and performance validation led us to actively
> choose not to mandate WEBRC, though we did originally reference it.
> Several years have passed since those decisions and the MBMS and DVB-H
> applications characteristics remain the same, in the mean time the
> validity of WEBRC has not been disproven. So perhaps spec text along the
> lines of the original FLUTE text would be ideal.”
> 
> The only caveat I have on this is the state of WEBRC. When proposed is
> was a brilliant contribution, in the time since how many distinct works
> have validated implementability or other performance metrics? If there
> is a high level of WG confidence, making it mandatory in the “forward to
> open internet” case sounds sensible, otherwise not.
> 
> (And apologies if I just arrived at the conversation midway through and
> totally misjudged the context – my 6 monthly RMT email review just came
> up, so my flow with RMT is not ideal either :)
> 

Rod, I am fully aware that many of the usages of ALC are in environments
that has dedicated resources, like DVB and 3GPP MBMS. But for general
usage where you don't have dedicated and controlled resources I see
congestion control being a requirement you can't skip.

So is WEBRC broken, so far I haven't seen anything indicating that.
However, we clearly don't have the data to show that it is mature and
interoperable and everything to bring it to proposed standard. This is
an issue. Something for everyone in this WG to think about. Are you
confident that WEBRC works well enough to both prevent a congestion
collapse and provide reasonable service behavior?

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 watson@qualcomm.com  Mon Jun  1 09:06:06 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 18E793A6B45 for <rmt@core3.amsl.com>; Mon,  1 Jun 2009 09:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[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 DL6x+6J4tMXG for <rmt@core3.amsl.com>; Mon,  1 Jun 2009 09:05:58 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id 0B02D3A6CB5 for <rmt@ietf.org>; Mon,  1 Jun 2009 09:04:13 -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=1243872253; x=1275408253; 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"Watson,=20Mark"=20<watson@qualcomm.com>|To:=20M agnus=20Westerlund=20<magnus.westerlund@ericsson.com>,=0D =0A=20=20=20=20=20=20=20=20"Rod.Walsh@nokia.com"=0D=0A=09 <Rod.Walsh@nokia.com>|CC:=20"draft-ietf-rmt-pi-alc-revise d@tools.ietf.org"=0D=0A=09<draft-ietf-rmt-pi-alc-revised@ tools.ietf.org>,=0D=0A=20=20=20=20=20=20=20=20"rmt@ietf.o rg"=20<rmt@ietf.org>|Date:=20Mon,=201=20Jun=202009=2009:0 4:07=20-0700|Subject:=20Re:=20[Rmt]=20AD=20comments=20on =20draft-ietf-rmt-pi-alc-revised-06|Thread-Topic:=20[Rmt] =20AD=20comments=20on=20draft-ietf-rmt-pi-alc-revised-06 |Thread-Index:=20AcnioA8ITIcKf7BNSo2nZIcAWJid7wAMoh9q |Message-ID:=20<C6494A07.2E03F%watson@qualcomm.com> |In-Reply-To:=20<4A23A6D3.9040508@ericsson.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_C6494A072E03Fwatsonqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5633"=3B=20a=3D"18831905"; bh=WWxZNlx+67VG1o74O+YOMS4s9wEzqbcsfBIeHrhF/zw=; b=MbUTQJ5WmFtTlYj+RCWMl4Xi7OlYy8JJeeA9YG+8ulC4UGrmEr45sjxk K7WCVVDp8h5cRyoy3C/MmmdoicYjIl0qQppDcwXzhpC04aPpRyY1DeIa8 cnemhm3clGMhguEkLBmf/zjAhsxMRcmvx1aMN8IpQsxZA48+bFT02hx9r I=;
X-IronPort-AV: E=McAfee;i="5300,2777,5633"; a="18831905"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 01 Jun 2009 09:04:13 -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 n51G4CXJ032342 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 1 Jun 2009 09:04:13 -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 n51G4C9f001563 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 1 Jun 2009 09:04:12 -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.358.0; Mon, 1 Jun 2009 09:04:09 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Mon, 1 Jun 2009 09:04:09 -0700
From: "Watson, Mark" <watson@qualcomm.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>
Date: Mon, 1 Jun 2009 09:04:07 -0700
Thread-Topic: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06
Thread-Index: AcnioA8ITIcKf7BNSo2nZIcAWJid7wAMoh9q
Message-ID: <C6494A07.2E03F%watson@qualcomm.com>
In-Reply-To: <4A23A6D3.9040508@ericsson.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_C6494A072E03Fwatsonqualcommcom_"
MIME-Version: 1.0
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Mon, 01 Jun 2009 16:06:06 -0000

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

Magnus,

We seem to repeat a variant of this discussion quite often. I wonder if the=
 IESG could recommend a standard pattern for addressing 'non-Internet domai=
ns of application' ?. For example there could be a standard RFC section "Ot=
her domains of application" in which you can specify deltas to the requirem=
ents of the rest of the RFC for specific non-Internet application domains o=
r domains with specific properties. This would make it possible for the bod=
y of the RFC to be clear about the requirements for the Internet, without n=
eeding different smallprint for every case.

It is not clear to me why the domain-specific standards bodies can't specif=
y the deltas themselves, but generally they do prefer to be able to use a s=
traightforward reference (i.e. For the IETF to have done their domain-speci=
fic thinking for them).

...Mark

On 6/1/09 3:00 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com> wro=
te:

Rod.Walsh@nokia.com skrev:
> Hi All
>
> Perhaps the WEBRC mandating suggestion is not the right response on CC...
>>> "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?"
>> "If I understand the WG discussion correctly, we should mandate the
> support of WEBRC for Congestion Control."
>
> I feel that this (paraphrased) answer is not ideal "Oh, we didn't see
> that mass of RFC text about CC needs for multicast from around the time
> RMT was first chartered, how foolish, let's mandate WEBRCC now." (Mark,
> I hope you've still got the sense of humor to take this poke with a
> smile from fortress QC? :)
>
> So I humbly suggest some assimilated form of this as the answer..
> "Most of the practitioners of ALC protocols have found the greatest use
> of ALC in unidirectional fully provisioned (as a lower layer) channels
> such as 3GPP-MBMS and DVB-H. In these fully provisioned cases where the
> ALC packets are not subsequently forwarded, unmodified, from receivers
> to the open internet, a layer 3 or 4 CC mechanism is both redundant and
> potentially expensive. It is highly unlikely that a mandated one would
> be adopted in DVB and 3GPP for these kinds of applications, so mandating
> that in the ALC RFC may well lead to the SDO fragmentation that was
> previously diligently avoided through the hard work of RMT contributors.
> To provide for this 'practical application to broadcast' and 'flexible
> use on the open internet' dual nature of ALC CC, FLUTE originally had
> text that explicatively stated that no CC block was required in the case
> described above, but a CC block was required otherwise - but didn't
> mandate any CC instance - at that time WEBRC was the only IETF published
> candidate. At that time, the lack of wide scale implementation,
> interoperability maturing and performance validation led us to actively
> choose not to mandate WEBRC, though we did originally reference it.
> Several years have passed since those decisions and the MBMS and DVB-H
> applications characteristics remain the same, in the mean time the
> validity of WEBRC has not been disproven. So perhaps spec text along the
> lines of the original FLUTE text would be ideal."
>
> The only caveat I have on this is the state of WEBRC. When proposed is
> was a brilliant contribution, in the time since how many distinct works
> have validated implementability or other performance metrics? If there
> is a high level of WG confidence, making it mandatory in the "forward to
> open internet" case sounds sensible, otherwise not.
>
> (And apologies if I just arrived at the conversation midway through and
> totally misjudged the context - my 6 monthly RMT email review just came
> up, so my flow with RMT is not ideal either :)
>

Rod, I am fully aware that many of the usages of ALC are in environments
that has dedicated resources, like DVB and 3GPP MBMS. But for general
usage where you don't have dedicated and controlled resources I see
congestion control being a requirement you can't skip.

So is WEBRC broken, so far I haven't seen anything indicating that.
However, we clearly don't have the data to show that it is mature and
interoperable and everything to bring it to proposed standard. This is
an issue. Something for everyone in this WG to think about. Are you
confident that WEBRC works well enough to both prevent a congestion
collapse and provide reasonable service behavior?

Cheers

Magnus Westerlund

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


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

<HTML>
<HEAD>
<TITLE>Re: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Magnus,<BR>
<BR>
We seem to repeat a variant of this discussion quite often. I wonder if the=
 IESG could recommend a standard pattern for addressing &#8216;non-Internet=
 domains of application&#8217; ?. For example there could be a standard RFC=
 section &#8220;Other domains of application&#8221; in which you can specif=
y deltas to the requirements of the rest of the RFC for specific non-Intern=
et application domains or domains with specific properties. This would make=
 it possible for the body of the RFC to be clear about the requirements for=
 the Internet, without needing different smallprint for every case. <BR>
<BR>
It is not clear to me why the domain-specific standards bodies can&#8217;t =
specify the deltas themselves, but generally they do prefer to be able to u=
se a straightforward reference (i.e. For the IETF to have done their domain=
-specific thinking for them).<BR>
<BR>
...Mark<BR>
<BR>
On 6/1/09 3:00 AM, &quot;Magnus Westerlund&quot; &lt;<a href=3D"magnus.west=
erlund@ericsson.com">magnus.westerlund@ericsson.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'><a href=3D"Rod.Walsh@nokia.com">Rod.Walsh@n=
okia.com</a> skrev:<BR>
&gt; Hi All<BR>
&gt;<BR>
&gt; Perhaps the WEBRC mandating suggestion is not the right response on CC=
...<BR>
&gt;&gt;&gt; &#8220;For example the choice of congestion control algorithm.=
 I think we<BR>
&gt; only have one that we can really use to satisfy the intended usage of<=
BR>
&gt; large scale sessions. Why isn't this a required to implement feature?&=
#8221;<BR>
&gt;&gt; &#8220;If I understand the WG discussion correctly, we should mand=
ate the<BR>
&gt; support of WEBRC for Congestion Control.&#8221;<BR>
&gt;<BR>
&gt; I feel that this (paraphrased) answer is not ideal &#8220;Oh, we didn&=
#8217;t see<BR>
&gt; that mass of RFC text about CC needs for multicast from around the tim=
e<BR>
&gt; RMT was first chartered, how foolish, let&#8217;s mandate WEBRCC now.&=
#8221; (Mark,<BR>
&gt; I hope you&#8217;ve still got the sense of humor to take this poke wit=
h a<BR>
&gt; smile from fortress QC? :)<BR>
&gt;<BR>
&gt; So I humbly suggest some assimilated form of this as the answer..<BR>
&gt; &#8220;Most of the practitioners of ALC protocols have found the great=
est use<BR>
&gt; of ALC in unidirectional fully provisioned (as a lower layer) channels=
<BR>
&gt; such as 3GPP-MBMS and DVB-H. In these fully provisioned cases where th=
e<BR>
&gt; ALC packets are not subsequently forwarded, unmodified, from receivers=
<BR>
&gt; to the open internet, a layer 3 or 4 CC mechanism is both redundant an=
d<BR>
&gt; potentially expensive. It is highly unlikely that a mandated one would=
<BR>
&gt; be adopted in DVB and 3GPP for these kinds of applications, so mandati=
ng<BR>
&gt; that in the ALC RFC may well lead to the SDO fragmentation that was<BR=
>
&gt; previously diligently avoided through the hard work of RMT contributor=
s.<BR>
&gt; To provide for this &#8216;practical application to broadcast&#8217; a=
nd &#8216;flexible<BR>
&gt; use on the open internet&#8217; dual nature of ALC CC, FLUTE originall=
y had<BR>
&gt; text that explicatively stated that no CC block was required in the ca=
se<BR>
&gt; described above, but a CC block was required otherwise &#8211; but did=
n&#8217;t<BR>
&gt; mandate any CC instance &#8211; at that time WEBRC was the only IETF p=
ublished<BR>
&gt; candidate. At that time, the lack of wide scale implementation,<BR>
&gt; interoperability maturing and performance validation led us to activel=
y<BR>
&gt; choose not to mandate WEBRC, though we did originally reference it.<BR=
>
&gt; Several years have passed since those decisions and the MBMS and DVB-H=
<BR>
&gt; applications characteristics remain the same, in the mean time the<BR>
&gt; validity of WEBRC has not been disproven. So perhaps spec text along t=
he<BR>
&gt; lines of the original FLUTE text would be ideal.&#8221;<BR>
&gt;<BR>
&gt; The only caveat I have on this is the state of WEBRC. When proposed is=
<BR>
&gt; was a brilliant contribution, in the time since how many distinct work=
s<BR>
&gt; have validated implementability or other performance metrics? If there=
<BR>
&gt; is a high level of WG confidence, making it mandatory in the &#8220;fo=
rward to<BR>
&gt; open internet&#8221; case sounds sensible, otherwise not.<BR>
&gt;<BR>
&gt; (And apologies if I just arrived at the conversation midway through an=
d<BR>
&gt; totally misjudged the context &#8211; my 6 monthly RMT email review ju=
st came<BR>
&gt; up, so my flow with RMT is not ideal either :)<BR>
&gt;<BR>
<BR>
Rod, I am fully aware that many of the usages of ALC are in environments<BR=
>
that has dedicated resources, like DVB and 3GPP MBMS. But for general<BR>
usage where you don't have dedicated and controlled resources I see<BR>
congestion control being a requirement you can't skip.<BR>
<BR>
So is WEBRC broken, so far I haven't seen anything indicating that.<BR>
However, we clearly don't have the data to show that it is mature and<BR>
interoperable and everything to bring it to proposed standard. This is<BR>
an issue. Something for everyone in this WG to think about. Are you<BR>
confident that WEBRC works well enough to both prevent a congestion<BR>
collapse and provide reasonable service behavior?<BR>
<BR>
Cheers<BR>
<BR>
Magnus Westerlund<BR>
<BR>
IETF Transport Area Director &amp; TSVWG Chair<BR>
----------------------------------------------------------------------<BR>
Multimedia Technologies, Ericsson Research EAB/TVM<BR>
----------------------------------------------------------------------<BR>
Ericsson AB &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;| Phone &nbsp;+46 10 7148287<BR>
F&auml;r&ouml;gatan 6 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| Mobile +46 73 0949079<BR>
SE-164 80 Stockholm, Sweden| mailto: <a href=3D"magnus.westerlund@ericsson.=
com">magnus.westerlund@ericsson.com</a><BR>
----------------------------------------------------------------------<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C6494A072E03Fwatsonqualcommcom_--

From magnus.westerlund@ericsson.com  Tue Jun  2 05:57: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 1147E3A6878 for <rmt@core3.amsl.com>; Tue,  2 Jun 2009 05:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[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 bS5pC1yhY+Cl for <rmt@core3.amsl.com>; Tue,  2 Jun 2009 05:57:57 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id BDC6D3A6F2E for <rmt@ietf.org>; Tue,  2 Jun 2009 05:57:56 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b14ae0000039d7-b7-4a252166e75a
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id AB.13.14807.661252A4; Tue,  2 Jun 2009 14:56:07 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 2 Jun 2009 13:16:36 +0200
Received: from [147.214.183.61] ([147.214.183.61]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 2 Jun 2009 13:16:36 +0200
Message-ID: <4A250A14.7060107@ericsson.com>
Date: Tue, 02 Jun 2009 13:16:36 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Watson, Mark" <watson@qualcomm.com>
References: <C6494A07.2E03F%watson@qualcomm.com>
In-Reply-To: <C6494A07.2E03F%watson@qualcomm.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 02 Jun 2009 11:16:36.0005 (UTC) FILETIME=[978C0550:01C9E373]
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Tue, 02 Jun 2009 12:57:58 -0000

Watson, Mark skrev:
> Magnus,
> 
> We seem to repeat a variant of this discussion quite often. I wonder if
> the IESG could recommend a standard pattern for addressing ‘non-Internet
> domains of application’ ?. For example there could be a standard RFC
> section “Other domains of application” in which you can specify deltas
> to the requirements of the rest of the RFC for specific non-Internet
> application domains or domains with specific properties. This would make
> it possible for the body of the RFC to be clear about the requirements
> for the Internet, without needing different smallprint for every case.

No, I don't think so. Because the variations are different for different
protocols. Sure, congestion control comes up pretty often. However, it
is generaly need also for none Internet usage. It is only when you both
reserve resources and ensure that the traffic provided over that
resource matches the reservation that you can be pretty certain that you
don't need congestion control. Even in these cases you commonly need to
deal with failure modes.

So, no even if reoccurring what goes into this often has variations and
special considerations.

> 
> It is not clear to me why the domain-specific standards bodies can’t
> specify the deltas themselves, but generally they do prefer to be able
> to use a straightforward reference (i.e. For the IETF to have done their
> domain-specific thinking for them).
> 

Yes, for an SDO like DVB can clearly specify that you don't need to
implement congestion control because the traffic will always be ingress
filtered and shaped before being broadcasted. Thus congestion isn't a
real issue. However, I know that some IETFers do not like when other
SDOs profile our standards. There is a risk in profiling both from
interoperability and correct function.

Cheers


Magnus

From watson@qualcomm.com  Tue Jun  2 09:46:41 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 36FFE3A7034 for <rmt@core3.amsl.com>; Tue,  2 Jun 2009 09:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.598
X-Spam-Level: 
X-Spam-Status: No, score=-104.598 tagged_above=-999 required=5 tests=[AWL=2.000, 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 ULRMv44efvne for <rmt@core3.amsl.com>; Tue,  2 Jun 2009 09:46:34 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 72CEF3A7033 for <rmt@ietf.org>; Tue,  2 Jun 2009 09:45:57 -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=1243961158; x=1275497158; 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"Watson,=20Mark"=20<watson@qualcomm.com>|To:=20M agnus=20Westerlund=20<magnus.westerlund@ericsson.com>|CC: =20"draft-ietf-rmt-pi-alc-revised@tools.ietf.org"=0D=0A =09<draft-ietf-rmt-pi-alc-revised@tools.ietf.org>,=0D=0A =20=20=20=20=20=20=20=20"Rod.Walsh@nokia.com"=0D=0A=09<Ro d.Walsh@nokia.com>,=0D=0A=20=20=20=20=20=20=20=20"rmt@iet f.org"=20<rmt@ietf.org>|Date:=20Tue,=202=20Jun=202009=200 9:45:49=20-0700|Subject:=20Re:=20[Rmt]=20AD=20comments=20 on=20draft-ietf-rmt-pi-alc-revised-06|Thread-Topic:=20[Rm t]=20AD=20comments=20on=20draft-ietf-rmt-pi-alc-revised-0 6|Thread-Index:=20AcnjgcPqyyvffeWBRwWXIE7lISPY8AAH9FVl |Message-ID:=20<C64AA54D.2E0BF%watson@qualcomm.com> |In-Reply-To:=20<4A250A14.7060107@ericsson.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_C64AA54D2E0BFwatsonqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5634"=3B=20a=3D"18878287"; bh=vwRewIt5z1A7ejwIClccJdrjTWFEx4U45xbenmHGG90=; b=rjmtyTXkje78PhlCkCPoWFjBgggBrpQZHV6g/YpgiK2OSdRvZPHvClDn RbJgEwxSOLobkdU6fYRhifXfVq3k91pA8bZVxHQvvg2Svc0mLFkJqTquK yPtWJ7mto084vugSuHOKMGpuPDdKcTEGmcmUvVxcph+p2I2nEXK/RQsrl w=;
X-IronPort-AV: E=McAfee;i="5300,2777,5634"; a="18878287"
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; 02 Jun 2009 09:45:58 -0700
Received: from msgtransport05.qualcomm.com (msgtransport05.qualcomm.com [129.46.61.150]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n52GjvnR011944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 2 Jun 2009 09:45:58 -0700
Received: from nasanexhub06.na.qualcomm.com (nasanexhub06.na.qualcomm.com [129.46.134.254]) by msgtransport05.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n52GjvJE018311 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 2 Jun 2009 09:45:57 -0700
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.358.0; Tue, 2 Jun 2009 09:45:56 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Tue, 2 Jun 2009 09:45:56 -0700
From: "Watson, Mark" <watson@qualcomm.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Date: Tue, 2 Jun 2009 09:45:49 -0700
Thread-Topic: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06
Thread-Index: AcnjgcPqyyvffeWBRwWXIE7lISPY8AAH9FVl
Message-ID: <C64AA54D.2E0BF%watson@qualcomm.com>
In-Reply-To: <4A250A14.7060107@ericsson.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_C64AA54D2E0BFwatsonqualcommcom_"
MIME-Version: 1.0
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Tue, 02 Jun 2009 16:46:41 -0000

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

Magnus,

What I was suggesting as a standard RFC section a bit like "Security Consid=
erations" in which the "Other domains" requirements should be collected, wi=
th guidelines as to what kind of thing should go in there. Then the rest of=
 the document is unambiguously applicable to the Internet domain. Obviously=
 the content of this section would be very dependent on the protocol being =
defined.

In a sense, this section would be the IETF doing the necessarily profiling =
for other standards groups itself (hopefully avoiding the risks you cite be=
low). This happens anyway, but I'm suggesting we make it more explicit so t=
hat we do not keep repeating the argument about whether Internet domain req=
uirements are MUST or SHOULD for protocols which have other domains of appl=
ications.

...Mark


On 6/2/09 4:16 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com> wro=
te:

Watson, Mark skrev:
> Magnus,
>
> We seem to repeat a variant of this discussion quite often. I wonder if
> the IESG could recommend a standard pattern for addressing 'non-Internet
> domains of application' ?. For example there could be a standard RFC
> section "Other domains of application" in which you can specify deltas
> to the requirements of the rest of the RFC for specific non-Internet
> application domains or domains with specific properties. This would make
> it possible for the body of the RFC to be clear about the requirements
> for the Internet, without needing different smallprint for every case.

No, I don't think so. Because the variations are different for different
protocols. Sure, congestion control comes up pretty often. However, it
is generaly need also for none Internet usage. It is only when you both
reserve resources and ensure that the traffic provided over that
resource matches the reservation that you can be pretty certain that you
don't need congestion control. Even in these cases you commonly need to
deal with failure modes.

So, no even if reoccurring what goes into this often has variations and
special considerations.

>
> It is not clear to me why the domain-specific standards bodies can't
> specify the deltas themselves, but generally they do prefer to be able
> to use a straightforward reference (i.e. For the IETF to have done their
> domain-specific thinking for them).
>

Yes, for an SDO like DVB can clearly specify that you don't need to
implement congestion control because the traffic will always be ingress
filtered and shaped before being broadcasted. Thus congestion isn't a
real issue. However, I know that some IETFers do not like when other
SDOs profile our standards. There is a risk in profiling both from
interoperability and correct function.

Cheers


Magnus
_______________________________________________
Rmt mailing list
Rmt@ietf.org
https://www.ietf.org/mailman/listinfo/rmt


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

<HTML>
<HEAD>
<TITLE>Re: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Magnus,<BR>
<BR>
What I was suggesting as a standard RFC section a bit like &#8220;Security =
Considerations&#8221; in which the &#8220;Other domains&#8221; requirements=
 should be collected, with guidelines as to what kind of thing should go in=
 there. Then the rest of the document is unambiguously applicable to the In=
ternet domain. Obviously the content of this section would be very dependen=
t on the protocol being defined.<BR>
<BR>
In a sense, this section would be the IETF doing the necessarily profiling =
for other standards groups itself (hopefully avoiding the risks you cite be=
low). This happens anyway, but I&#8217;m suggesting we make it more explici=
t so that we do not keep repeating the argument about whether Internet doma=
in requirements are MUST or SHOULD for protocols which have other domains o=
f applications.<BR>
<BR>
...Mark<BR>
<BR>
<BR>
On 6/2/09 4:16 AM, &quot;Magnus Westerlund&quot; &lt;<a href=3D"magnus.west=
erlund@ericsson.com">magnus.westerlund@ericsson.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Watson, Mark skrev:<BR>
&gt; Magnus,<BR>
&gt;<BR>
&gt; We seem to repeat a variant of this discussion quite often. I wonder i=
f<BR>
&gt; the IESG could recommend a standard pattern for addressing &#8216;non-=
Internet<BR>
&gt; domains of application&#8217; ?. For example there could be a standard=
 RFC<BR>
&gt; section &#8220;Other domains of application&#8221; in which you can sp=
ecify deltas<BR>
&gt; to the requirements of the rest of the RFC for specific non-Internet<B=
R>
&gt; application domains or domains with specific properties. This would ma=
ke<BR>
&gt; it possible for the body of the RFC to be clear about the requirements=
<BR>
&gt; for the Internet, without needing different smallprint for every case.=
<BR>
<BR>
No, I don't think so. Because the variations are different for different<BR=
>
protocols. Sure, congestion control comes up pretty often. However, it<BR>
is generaly need also for none Internet usage. It is only when you both<BR>
reserve resources and ensure that the traffic provided over that<BR>
resource matches the reservation that you can be pretty certain that you<BR=
>
don't need congestion control. Even in these cases you commonly need to<BR>
deal with failure modes.<BR>
<BR>
So, no even if reoccurring what goes into this often has variations and<BR>
special considerations.<BR>
<BR>
&gt;<BR>
&gt; It is not clear to me why the domain-specific standards bodies can&#82=
17;t<BR>
&gt; specify the deltas themselves, but generally they do prefer to be able=
<BR>
&gt; to use a straightforward reference (i.e. For the IETF to have done the=
ir<BR>
&gt; domain-specific thinking for them).<BR>
&gt;<BR>
<BR>
Yes, for an SDO like DVB can clearly specify that you don't need to<BR>
implement congestion control because the traffic will always be ingress<BR>
filtered and shaped before being broadcasted. Thus congestion isn't a<BR>
real issue. However, I know that some IETFers do not like when other<BR>
SDOs profile our standards. There is a risk in profiling both from<BR>
interoperability and correct function.<BR>
<BR>
Cheers<BR>
<BR>
<BR>
Magnus<BR>
_______________________________________________<BR>
Rmt mailing list<BR>
<a href=3D"Rmt@ietf.org">Rmt@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/rmt">https://www.ietf.org/=
mailman/listinfo/rmt</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C64AA54D2E0BFwatsonqualcommcom_--

From magnus.westerlund@ericsson.com  Wed Jun  3 01:58: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 A0EB63A6A6F for <rmt@core3.amsl.com>; Wed,  3 Jun 2009 01:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level: 
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[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 YFNC45WZDa7j for <rmt@core3.amsl.com>; Wed,  3 Jun 2009 01:58:12 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 6112E3A6781 for <rmt@ietf.org>; Wed,  3 Jun 2009 01:58:12 -0700 (PDT)
X-AuditID: c1b4fb3e-b7b4bae00000395e-f9-4a263b246d02
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id DD.D5.14686.42B362A4; Wed,  3 Jun 2009 10:58:12 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.174]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 10:50:42 +0200
Received: from [147.214.183.61] ([147.214.183.61]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 3 Jun 2009 10:50:30 +0200
Message-ID: <4A263956.5080400@ericsson.com>
Date: Wed, 03 Jun 2009 10:50:30 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Watson, Mark" <watson@qualcomm.com>
References: <C64AA54D.2E0BF%watson@qualcomm.com>
In-Reply-To: <C64AA54D.2E0BF%watson@qualcomm.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 03 Jun 2009 08:50:30.0784 (UTC) FILETIME=[597B3000:01C9E428]
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Wed, 03 Jun 2009 08:58:13 -0000

Watson, Mark skrev:
> Magnus,
> 
> What I was suggesting as a standard RFC section a bit like “Security
> Considerations” in which the “Other domains” requirements should be
> collected, with guidelines as to what kind of thing should go in there.
> Then the rest of the document is unambiguously applicable to the
> Internet domain. Obviously the content of this section would be very
> dependent on the protocol being defined.
> 
> In a sense, this section would be the IETF doing the necessarily
> profiling for other standards groups itself (hopefully avoiding the
> risks you cite below). This happens anyway, but I’m suggesting we make
> it more explicit so that we do not keep repeating the argument about
> whether Internet domain requirements are MUST or SHOULD for protocols
> which have other domains of applications.

Sorry Mark, I don't understand how I am going to be able to write such a
section without knowing which domain it is for. Only when you know your
domain and what features it has can you determine what you may not
require in terms of security protocol or congestion control, or
configuration support.

Maybe, I am misunderstanding you?

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 adamson@itd.nrl.navy.mil  Wed Jun  3 06:01:29 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 9A17C3A6F08 for <rmt@core3.amsl.com>; Wed,  3 Jun 2009 06:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  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 CpF0SZJb-n-p for <rmt@core3.amsl.com>; Wed,  3 Jun 2009 06:01:28 -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 957293A6AC3 for <rmt@ietf.org>; Wed,  3 Jun 2009 06:01:28 -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 n53D0Vnb025607; Wed, 3 Jun 2009 09:00:44 -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 M2009060309003316156 ; Wed, 03 Jun 2009 09:00:33 -0400
Message-Id: <BC5CE2F6-4281-40CC-A1AF-827E7DA8119F@itd.nrl.navy.mil>
From: Brian Adamson <adamson@itd.nrl.navy.mil>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
In-Reply-To: <4A263956.5080400@ericsson.com>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 3 Jun 2009 09:00:33 -0400
References: <C64AA54D.2E0BF%watson@qualcomm.com> <4A263956.5080400@ericsson.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "Watson, Mark" <watson@qualcomm.com>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Wed, 03 Jun 2009 13:01:29 -0000

As Magnus says, I don't think you could write the section ahead of =20
time without knowing the domain.

But, perhaps something that could be done in such a similar section =20
would be to identify the specific aspects / requirements on the =20
protocol that are due to "Internet Considerations" as opposed to the =20
aspects/requirements of the protocol for its general operation.  Then, =20=

this section would provide a focal point for profiling for other (non-=20=

Internet) domains ... i.e, the profiling could address any deviations =20=

from the "Internet Considerations".  For example, mandated congestion =20=

control would be identified in that "Internet Considerations" section =20=

and other profiles could then specify their own qualifications and/or =20=

deviations from considerations such as congestion control, security, =20
etc that might not be germain to the protocol's operation in those =20
other domains ...

Just some thoughts on what Mark suggested.  Probably some IESG thought =20=

would be in order here?


Brian Adamson
adamson@itd.nrl.navy.mil




On Jun 3, 2009, at 4:50 AM, Magnus Westerlund wrote:

> Watson, Mark skrev:
>> Magnus,
>>
>> What I was suggesting as a standard RFC section a bit like =93Security
>> Considerations=94 in which the =93Other domains=94 requirements =
should be
>> collected, with guidelines as to what kind of thing should go in =20
>> there.
>> Then the rest of the document is unambiguously applicable to the
>> Internet domain. Obviously the content of this section would be very
>> dependent on the protocol being defined.
>>
>> In a sense, this section would be the IETF doing the necessarily
>> profiling for other standards groups itself (hopefully avoiding the
>> risks you cite below). This happens anyway, but I=92m suggesting we =20=

>> make
>> it more explicit so that we do not keep repeating the argument about
>> whether Internet domain requirements are MUST or SHOULD for protocols
>> which have other domains of applications.
>
> Sorry Mark, I don't understand how I am going to be able to write =20
> such a
> section without knowing which domain it is for. Only when you know =20
> your
> domain and what features it has can you determine what you may not
> require in terms of security protocol or congestion control, or
> configuration support.
>
> Maybe, I am misunderstanding you?
>
> Cheers
>
> Magnus Westerlund
>
> IETF Transport Area Director & TSVWG Chair
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> _______________________________________________
> Rmt mailing list
> Rmt@ietf.org
> https://www.ietf.org/mailman/listinfo/rmt
>


From watson@qualcomm.com  Wed Jun  3 10:19:52 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 EEAC83A6DA6 for <rmt@core3.amsl.com>; Wed,  3 Jun 2009 10:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Level: 
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[AWL=1.000, 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 wPG6LcZcAQ5X for <rmt@core3.amsl.com>; Wed,  3 Jun 2009 10:19:48 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id 7B5053A67DF for <rmt@ietf.org>; Wed,  3 Jun 2009 10:19:48 -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=1244049590; x=1275585590; 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"Watson,=20Mark"=20<watson@qualcomm.com>|To:=20M agnus=20Westerlund=20<magnus.westerlund@ericsson.com>|CC: =20"draft-ietf-rmt-pi-alc-revised@tools.ietf.org"=0D=0A =09<draft-ietf-rmt-pi-alc-revised@tools.ietf.org>,=0D=0A =20=20=20=20=20=20=20=20"Rod.Walsh@nokia.com"=0D=0A=09<Ro d.Walsh@nokia.com>,=0D=0A=20=20=20=20=20=20=20=20"rmt@iet f.org"=20<rmt@ietf.org>|Date:=20Wed,=203=20Jun=202009=201 0:19:14=20-0700|Subject:=20Re:=20[Rmt]=20AD=20comments=20 on=20draft-ietf-rmt-pi-alc-revised-06|Thread-Topic:=20[Rm t]=20AD=20comments=20on=20draft-ietf-rmt-pi-alc-revised-0 6|Thread-Index:=20AcnkKW9jCHiimJCSRZC0PY0N5tbYCAAO50kx |Message-ID:=20<C64BED3D.2E17B%watson@qualcomm.com> |In-Reply-To:=20<4A263956.5080400@ericsson.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_C64BED3D2E17Bwatsonqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5635"=3B=20a=3D"18935521"; bh=o2yIn3L7iaXP5+gJ4aXqOijbypX9iiISYIl8sdrYN7M=; b=Te6G+lS8ZUPTN06O1czY8kBupNnt8V7q98sqo9iARj2+rJNC8TIaNGmg KFUaHG8oRpos3eHTfeT9YOXO6MiN//VdB8ySmN7cu4QXTh2uxhK3M4c67 IiRtbAzZeLWEyOHFBIWC77qfYr/lrDsMGCgrtXVR/sPHoB+Xlf6fSugTw g=;
X-IronPort-AV: E=McAfee;i="5300,2777,5635"; a="18935521"
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; 03 Jun 2009 10:19:23 -0700
Received: from msgtransport03.qualcomm.com (msgtransport03.qualcomm.com [129.46.61.154]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n53HJMli015351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 3 Jun 2009 10:19:23 -0700
Received: from nasanexhub04.na.qualcomm.com (nasanexhub04.qualcomm.com [129.46.134.222]) by msgtransport03.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n53HJDbg007043 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 3 Jun 2009 10:19:20 -0700
Received: from nasclexhc02.na.qualcomm.com (10.227.147.13) by nasanexhub04.na.qualcomm.com (129.46.134.222) with Microsoft SMTP Server (TLS) id 8.1.358.0; Wed, 3 Jun 2009 10:19:16 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc02.na.qualcomm.com ([10.227.147.13]) with mapi; Wed, 3 Jun 2009 10:19:15 -0700
From: "Watson, Mark" <watson@qualcomm.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Date: Wed, 3 Jun 2009 10:19:14 -0700
Thread-Topic: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06
Thread-Index: AcnkKW9jCHiimJCSRZC0PY0N5tbYCAAO50kx
Message-ID: <C64BED3D.2E17B%watson@qualcomm.com>
In-Reply-To: <4A263956.5080400@ericsson.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_C64BED3D2E17Bwatsonqualcommcom_"
MIME-Version: 1.0
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Wed, 03 Jun 2009 17:19:53 -0000

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

Hi Magnus,

I think you have overestimated the scope of my proposal (or I have overstat=
ed it). I am thinking something almost editorial in nature. I'm not suggest=
ing that anyone try to write text which is generic across multiple protocol=
s or multiple arbitrary domains.

What I'm suggesting is that if you have requirements for a specific protoco=
l which are applicable to a *specific non-Internet domain*, then these shou=
ld be collected into a "Requirements for non-Internet domains" section, rat=
her than spread throughout the rest of the document. (Equally there could b=
e requirements for non-Internet domains with specific well-defined properti=
es - such as the text suggested by Rod for ALC which refers to "unidirectio=
nal fully provisioned (at a lower layer) channels".)

The advantages are

 *   if this section is deleted, you then have a complete protocol specific=
ation that meets the requirements for Internet usage and this would be a ve=
ry clear and unambiguous policy.
 *   other SDOs have an clear place into which to propose their domain-spec=
ific requirements, without the usual confusion about whether those requirem=
ents mess things up for Internet usage.

It just seems to me that there is a process discussion about non-Internet r=
equirements which we repeat every time, and perhaps with guidance from the =
IESG that repetition could be avoided.

...Mark

On 6/3/09 1:50 AM, "Magnus Westerlund" <magnus.westerlund@ericsson.com> wro=
te:

Watson, Mark skrev:
> Magnus,
>
> What I was suggesting as a standard RFC section a bit like "Security
> Considerations" in which the "Other domains" requirements should be
> collected, with guidelines as to what kind of thing should go in there.
> Then the rest of the document is unambiguously applicable to the
> Internet domain. Obviously the content of this section would be very
> dependent on the protocol being defined.
>
> In a sense, this section would be the IETF doing the necessarily
> profiling for other standards groups itself (hopefully avoiding the
> risks you cite below). This happens anyway, but I'm suggesting we make
> it more explicit so that we do not keep repeating the argument about
> whether Internet domain requirements are MUST or SHOULD for protocols
> which have other domains of applications.

Sorry Mark, I don't understand how I am going to be able to write such a
section without knowing which domain it is for. Only when you know your
domain and what features it has can you determine what you may not
require in terms of security protocol or congestion control, or
configuration support.

Maybe, I am misunderstanding you?

Cheers

Magnus Westerlund

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


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

<HTML>
<HEAD>
<TITLE>Re: [Rmt] AD comments on draft-ietf-rmt-pi-alc-revised-06</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'>Hi Magnus,<BR>
<BR>
I think you have overestimated the scope of my proposal (or I have overstat=
ed it). I am thinking something almost editorial in nature. I&#8217;m not s=
uggesting that anyone try to write text which is generic across multiple pr=
otocols or multiple arbitrary domains.<BR>
<BR>
What I&#8217;m suggesting is that if you have requirements for a <B>specifi=
c protocol</B> which are applicable to a *specific non-Internet domain*, th=
en these should be collected into a &#8220;Requirements for non-Internet do=
mains&#8221; section, rather than spread throughout the rest of the documen=
t. (Equally there could be requirements for non-Internet domains with speci=
fic well-defined properties &#8211; such as the text suggested by Rod for A=
LC which refers to &#8220;unidirectional fully provisioned (at a lower laye=
r) channels&#8221;.)<BR>
<BR>
The advantages are <BR>
</SPAN></FONT><UL><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SP=
AN STYLE=3D'font-size:11pt'>if this section is deleted, you then have a com=
plete protocol specification that meets the requirements for Internet usage=
 and this would be a very clear and unambiguous policy.
</SPAN></FONT><LI><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN S=
TYLE=3D'font-size:11pt'>other SDOs have an clear place into which to propos=
e their domain-specific requirements, without the usual confusion about whe=
ther those requirements mess things up for Internet usage.<BR>
</SPAN></FONT></UL><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
It just seems to me that there is a process discussion about non-Internet r=
equirements which we repeat every time, and perhaps with guidance from the =
IESG that repetition could be avoided.<BR>
<BR>
...Mark<BR>
<BR>
On 6/3/09 1:50 AM, &quot;Magnus Westerlund&quot; &lt;<a href=3D"magnus.west=
erlund@ericsson.com">magnus.westerlund@ericsson.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Watson, Mark skrev:<BR>
&gt; Magnus,<BR>
&gt;<BR>
&gt; What I was suggesting as a standard RFC section a bit like &#8220;Secu=
rity<BR>
&gt; Considerations&#8221; in which the &#8220;Other domains&#8221; require=
ments should be<BR>
&gt; collected, with guidelines as to what kind of thing should go in there=
.<BR>
&gt; Then the rest of the document is unambiguously applicable to the<BR>
&gt; Internet domain. Obviously the content of this section would be very<B=
R>
&gt; dependent on the protocol being defined.<BR>
&gt;<BR>
&gt; In a sense, this section would be the IETF doing the necessarily<BR>
&gt; profiling for other standards groups itself (hopefully avoiding the<BR=
>
&gt; risks you cite below). This happens anyway, but I&#8217;m suggesting w=
e make<BR>
&gt; it more explicit so that we do not keep repeating the argument about<B=
R>
&gt; whether Internet domain requirements are MUST or SHOULD for protocols<=
BR>
&gt; which have other domains of applications.<BR>
<BR>
Sorry Mark, I don't understand how I am going to be able to write such a<BR=
>
section without knowing which domain it is for. Only when you know your<BR>
domain and what features it has can you determine what you may not<BR>
require in terms of security protocol or congestion control, or<BR>
configuration support.<BR>
<BR>
Maybe, I am misunderstanding you?<BR>
<BR>
Cheers<BR>
<BR>
Magnus Westerlund<BR>
<BR>
IETF Transport Area Director &amp; TSVWG Chair<BR>
----------------------------------------------------------------------<BR>
Multimedia Technologies, Ericsson Research EAB/TVM<BR>
----------------------------------------------------------------------<BR>
Ericsson AB &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;| Phone &nbsp;+46 10 7148287<BR>
F&auml;r&ouml;gatan 6 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;| Mobile +46 73 0949079<BR>
SE-164 80 Stockholm, Sweden| mailto: <a href=3D"magnus.westerlund@ericsson.=
com">magnus.westerlund@ericsson.com</a><BR>
----------------------------------------------------------------------<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C64BED3D2E17Bwatsonqualcommcom_--

From root@core3.amsl.com  Wed Jun  3 12:30: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 6028F3A6D7E; Wed,  3 Jun 2009 12:30: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: <20090603193001.6028F3A6D7E@core3.amsl.com>
Date: Wed,  3 Jun 2009 12:30:01 -0700 (PDT)
Cc: rmt@ietf.org
Subject: [Rmt] I-D Action:draft-ietf-rmt-pi-norm-revised-13.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, 03 Jun 2009 19:30: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 Transport Protocol
	Author(s)       : B. Adamson, et al.
	Filename        : draft-ietf-rmt-pi-norm-revised-13.txt
	Pages           : 94
	Date            : 2009-06-03

This document describes the messages and procedures of the Negative-
ACKnowledgment (NACK) Oriented Reliable Multicast (NORM) Protocol.
This protocol can 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-13.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-13.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From magnus.westerlund@ericsson.com  Wed Jun 24 08:48: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 6CB6F3A6CCE for <rmt@core3.amsl.com>; Wed, 24 Jun 2009 08:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.247
X-Spam-Level: 
X-Spam-Status: No, score=-6.247 tagged_above=-999 required=5 tests=[AWL=0.002,  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 XTExZE-kO7nc for <rmt@core3.amsl.com>; Wed, 24 Jun 2009 08:48:26 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 200433A6C5B for <rmt@ietf.org>; Wed, 24 Jun 2009 08:48:25 -0700 (PDT)
X-AuditID: c1b4fb3e-b7be1ae000004757-ec-4a42471f4594
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 31.78.18263.F17424A4; Wed, 24 Jun 2009 17:32:47 +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, 24 Jun 2009 17:32:47 +0200
Received: from [147.214.183.61] ([147.214.183.61]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830);  Wed, 24 Jun 2009 17:32:46 +0200
Message-ID: <4A42471E.7040902@ericsson.com>
Date: Wed, 24 Jun 2009 17:32:46 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: "Watson, Mark" <watson@qualcomm.com>
References: <C64BED3D.2E17B%watson@qualcomm.com>
In-Reply-To: <C64BED3D.2E17B%watson@qualcomm.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 24 Jun 2009 15:32:46.0874 (UTC) FILETIME=[0662FFA0:01C9F4E1]
X-Brightmail-Tracker: AAAAAA==
Cc: "draft-ietf-rmt-pi-alc-revised@tools.ietf.org" <draft-ietf-rmt-pi-alc-revised@tools.ietf.org>, "Rod.Walsh@nokia.com" <Rod.Walsh@nokia.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [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: Wed, 24 Jun 2009 15:48:27 -0000

Watson, Mark skrev:
> Hi Magnus,
> 
> I think you have overestimated the scope of my proposal (or I have
> overstated it). I am thinking something almost editorial in nature. I’m
> not suggesting that anyone try to write text which is generic across
> multiple protocols or multiple arbitrary domains.
> 
> What I’m suggesting is that if you have requirements for a *specific
> protocol* which are applicable to a *specific non-Internet domain*, then
> these should be collected into a “Requirements for non-Internet domains”
> section, rather than spread throughout the rest of the document.
> (Equally there could be requirements for non-Internet domains with
> specific well-defined properties – such as the text suggested by Rod for
> ALC which refers to “unidirectional fully provisioned (at a lower layer)
> channels”.)
> 
> The advantages are
> 
>     * if this section is deleted, you then have a complete protocol
>       specification that meets the requirements for Internet usage and
>       this would be a very clear and unambiguous policy.
>     * other SDOs have an clear place into which to propose their
>       domain-specific requirements, without the usual confusion about
>       whether those requirements mess things up for Internet usage.
> 
> 
> It just seems to me that there is a process discussion about
> non-Internet requirements which we repeat every time, and perhaps with
> guidance from the IESG that repetition could be avoided.
> 

Mark,

Okay, I understand your proposal better.

I think this is hard to do in a generic fashion as each specific domain
requires its considerations both technical and politically. In cases it
makes sense I can see writing up such recommendations for a specific
other domain.

However, what are you suggesting in regards to this document?

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
----------------------------------------------------------------------
