
From ingemar.s.johansson@ericsson.com  Fri Oct  2 10:50:03 2009
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE50F3A687A for <mmusic@core3.amsl.com>; Fri,  2 Oct 2009 10:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.4
X-Spam-Level: 
X-Spam-Status: No, score=-3.4 tagged_above=-999 required=5 tests=[AWL=-1.410,  BAYES_20=-0.74, HELO_EQ_SE=0.35, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_16=0.6, J_CHICKENPOX_17=0.6, 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 uJ8DumlaN9nU for <mmusic@core3.amsl.com>; Fri,  2 Oct 2009 10:50:02 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 1AE283A67B0 for <mmusic@ietf.org>; Fri,  2 Oct 2009 10:50:01 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b6eae000003d08-51-4ac63da01e6a
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id 55.CE.15624.0AD36CA4; Fri,  2 Oct 2009 19:51:28 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 2 Oct 2009 19:51:25 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 2 Oct 2009 19:51:24 +0200
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C01F2FE62@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Image attribute and layered coding
Thread-Index: AcpDiPWqHwV6oqnPTW6wbNZb/zH50g==
From: "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 02 Oct 2009 17:51:25.0478 (UTC) FILETIME=[F5F83C60:01CA4388]
X-Brightmail-Tracker: AAAAAA==
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
Subject: [MMUSIC] Image attribute and layered coding
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2009 17:50:03 -0000

Hi

After a period of silence I am in the process of updating the image =
attrubute draft.=20
I have an issue with the image attribute and how it can be used with =
layered codecs.

>From RFC5583 one can take the following example=20
         v=3D0
         o=3Dsvcsrv 289083124 289083124 IN IP4 host.example.com
         s=3DLAYERED VIDEO SIGNALING Seminar
         t=3D0 0
         c=3DIN IP4 192.0.2.1/127
         a=3Dgroup:DDP L1 L2 L3
         m=3Dvideo 40000 RTP/AVP 96 97
         b=3DAS:90
         a=3Dframerate:15
         a=3Drtpmap:96 H264/90000
         a=3Drtpmap:97 H264/90000
         a=3Dmid:L1
         m=3Dvideo 40002 RTP/AVP 98 99
         b=3DAS:64
         a=3Dframerate:15
         a=3Drtpmap:98 H264-SVC/90000
         a=3Drtpmap:99 H264-SVC/90000
         a=3Dmid:L2
         a=3Ddepend:98 lay L1:96,97; 99 lay L1:97
         m=3Dvideo 40004 RTP/AVP 100 101
         b=3DAS:128
         a=3Dframerate:30
         a=3Drtpmap:100 H264-SVC/90000
         a=3Drtpmap:101 H264-SVC/90000
         a=3Dmid:L3
         a=3Ddepend:100 lay L1:96,97; 101 lay L1:97 L2:99

My headache is where the imageattr fits best (if possible). I guess the =
obvious is to put the same attribute in every media description. This is =
of course a lot of repetitions of likely the same attribute (after all =
the display is the same)

One alternative is make it possible to use the image attribute as a =
session attribute, it is not forbidden in the current draft version but =
I have up until now assumed that the attribute is limited to the media =
description..

Comments ?

/Ingemar



=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
INGEMAR JOHANSSON  M.Sc.=20
Senior Research Engineer=20

Ericsson AB
Multimedia Technologies
Labratoriegr=E4nd 11
971 28, Lule=E5, Sweden
Phone +46-1071 43042
SMS/MMS +46-73 078 3289
ingemar.s.johansson@ericsson.com
www.ericsson.com=20
Visit http://labs.ericsson.com !
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

From Christian.Haas@frequentis.com  Sat Oct  3 02:32:44 2009
Return-Path: <Christian.Haas@frequentis.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C78093A682C for <mmusic@core3.amsl.com>; Sat,  3 Oct 2009 02:32:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.462
X-Spam-Level: 
X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[AWL=0.277,  BAYES_20=-0.74, HTML_MESSAGE=0.001]
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 N4dMURmqdRrE for <mmusic@core3.amsl.com>; Sat,  3 Oct 2009 02:32:43 -0700 (PDT)
Received: from mail1.frequentis.com (mail1.frequentis.com [212.186.194.131]) by core3.amsl.com (Postfix) with ESMTP id 3DBE03A659A for <mmusic@ietf.org>; Sat,  3 Oct 2009 02:32:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.44,499,1249250400"; d="scan'208,217";a="664627"
Received: from unknown (HELO webmail.frequentis.com) ([192.168.254.147]) by mail1.frequentis.com with ESMTP; 03 Oct 2009 11:34:09 +0200
Received: from VIECLEX01.frequentis.frq ([172.16.1.55]) by webmail.frequentis.com with Microsoft SMTPSVC(6.0.3790.3959);  Sat, 3 Oct 2009 11:34:09 +0200
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_01CA440C.A7FA7ADB"
Date: Sat, 3 Oct 2009 11:34:08 +0200
Message-ID: <70FB7A734037F44399441D45A72DE90D12CA81@VIECLEX01.frequentis.frq>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22
Thread-Index: Aco6DnDOJU+iBP/DQhGHuV19VgdmvQDkPE6wAZrYV6o=
References: <4AB65606.4040905@netlab.tkk.fi> <70FB7A734037F44399441D45A72DE90D04B8298B@VIECLEX01.frequentis.frq>
From: "HAAS Christian" <Christian.Haas@frequentis.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 03 Oct 2009 09:34:09.0200 (UTC) FILETIME=[A8934300:01CA440C]
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Oct 2009 09:32:44 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA440C.A7FA7ADB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello again!

In here I list my findings of my first pass of the syntax review. As =
always,
I'm optimistic to find extra time for another pass.

I) Syntax modifications

1. accept-param:
The syntax does not enforce using the q parameter as 'delimeter' between
media-type-range and accept-range parameters; HTTP does this more =
explicitly
in 14.1
Suggestion:

accept-range      =3D  media-type-range [ SEMI accept-params ]
accept-params     =3D  "q" EQUAL qvalue *( SEMI generic-param )

this then also affects other definitions that rely on current =
accept-param:

encoding          =3D  codings [ SEMI accept-params ]
language          =3D  language-range [ SEMI accept-params ]

...although this then requires the q parameter to be first for the =
encoding
and language definitions as well. Bad / Not Bad?


2. language-range (for Accept-Ranges):
It could reference the language-tag definition (one page below), =
suggestion:

language-range    =3D  language-tag / "*"


3. Proxy-Require and Proxy-Supported:
They can both reference the feature-tag-list below, suggestion:

Proxy-Require        =3D  "Proxy-Require" HCOLON feature-tag-list
Proxy-Supported      =3D  "Proxy-Supported" HCOLON feature-tag-list


4. Retry-After:
a) 16.40 allows this header to specify seconds or a date, the syntax =
only
allows delta-seconds.
b) What is the comment for? Maintenance description?
c) Usage of duration retry-param is not described in 16.40 nor anywhere =
else

Suggestion (assuming no further description text is added):

Retry-After          =3D "Retry-After" HCOLON ( RTSP-date / =
delta-seconds )


5. channel (for transport parameter)
I suggest a comment like at ttl:

channel              =3D 1*3DIGIT ; 0 to 255


6. User-Agent
I guess the syntax should be identical to the one of Server; the extra =
'0'
for the * list is unnecessary.


II) Things I might have not properly understood:

1. Accept-Language:
The header allows to be empty. If this is the case, does this mean all
languages have a q value of 1 or does the last sentence in 16.4 imply NO
language is acceptable: "If an Accept-Language header is present, then =
all
languages which are assigned a quality factor greater than 0 are =
acceptable."
I guess it of course means all languages are equally acceptable, =
especially
with the default q value of 1 -- yet, does this mean for all explicitly =
given
languages or all the server knows of which are not explicitly given?


2. Allow:
This header may also be empty. How can I reach a valid resource that =
does not
produce 404, but 405 and allows no request to be performed?


3. Content-Type:
May be given in SIP-like short form "c" -- This is the only header to =
allow
this according to the syntax.
Why?


Regards,
ch


-----Original Message-----
From: mmusic-bounces@ietf.org on behalf of HAAS Christian
Sent: Fri 9/25/2009 7:23 AM
To: mmusic@ietf.org
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22
=20
Hello all!

I've read through the draft (skipping the syntax definitions) and found =
only
minor issues regarding wording, typos and consistency so far, which I =
already
sent to Magnus directly.

I will try to find some time during the upcoming days for a dedicated =
check
of the syntax.

Regards,
ch
____________________________________________________
Christian Haas
Team DIVOS, Software Engineer
FREQUENTIS AG

Innovationsstra=DFe 1, 1100 Vienna, Austria
Phone   +43-1-811 50 - 8353
Mobile   +43-664-60 850 - 8353
Fax       +43-1-811 50 - 77 8353
Web      www.frequentis.com
E-Mail    christian.haas@frequentis.com
=20
Handelsgericht Wien (Vienna Commercial Court): FN 72115 b
DVR 0364797, ATU 14715600
____________________________________________________
Diese E-Mail k=F6nnte vertrauliche und/oder rechtlich gesch=FCtzte =
Informationen
enthalten. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrt=FCmlich erhalten haben, informieren Sie bitte sofort den Absender =
und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser E-Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If =
you
are not the intended recipient (or have received this e-mail in error) =
please
notify the sender immediately and destroy this e-mail. Any unauthorised
copying, disclosure or distribution of the material in this e-mail is
strictly forbidden.=20



-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf =
Of
Joerg Ott
Sent: Sonntag, 20. September 2009 18:19
To: mmusic@ietf.org
Cc: Magnus Westerlund; Jean-Francois Mule; Martin Stiemerling
Subject: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22

Folks,

as agreed in Stockholm, we are issuing working group last call on the =
revised
RTSP spec, draft-ietf-mmusic-rfc2326bis-22 heading for Proposed =
Standard.
(http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22)

The WGLC will expire in four weeks, on 19 Oct 2009.

We know that this is a long spec, the more important is it to receive
thorough review by the community.  While we have three volunteer =
reviewers
(thanks again!), we urge everyone who cares to provide detailed =
feedback.

Please review the document and post your comments to the MMUSIC list =
and/or
the authors.

Thanks,
Joerg

MMUSIC co-chair

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


------_=_NextPart_001_01CA440C.A7FA7ADB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>Re: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hello again!<BR>
<BR>
In here I list my findings of my first pass of the syntax review. As =
always, I'm optimistic to find extra time for another pass.<BR>
<BR>
I) Syntax modifications<BR>
<BR>
1. accept-param:<BR>
The syntax does not enforce using the q parameter as 'delimeter' between =
media-type-range and accept-range parameters; HTTP does this more =
explicitly in 14.1<BR>
Suggestion:<BR>
<BR>
accept-range&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; media-type-range [ =
SEMI accept-params ]<BR>
accept-params&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; &quot;q&quot; EQUAL =
qvalue *( SEMI generic-param )<BR>
<BR>
this then also affects other definitions that rely on current =
accept-param:<BR>
<BR>
encoding&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; =
codings [ SEMI accept-params ]<BR>
language&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; =
language-range [ SEMI accept-params ]<BR>
<BR>
...although this then requires the q parameter to be first for the =
encoding and language definitions as well. Bad / Not Bad?<BR>
<BR>
<BR>
2. language-range (for Accept-Ranges):<BR>
It could reference the language-tag definition (one page below), =
suggestion:<BR>
<BR>
language-range&nbsp;&nbsp;&nbsp; =3D&nbsp; language-tag / =
&quot;*&quot;<BR>
<BR>
<BR>
3. Proxy-Require and Proxy-Supported:<BR>
They can both reference the feature-tag-list below, suggestion:<BR>
<BR>
Proxy-Require&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; =
&quot;Proxy-Require&quot; HCOLON feature-tag-list<BR>
Proxy-Supported&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D&nbsp; =
&quot;Proxy-Supported&quot; HCOLON feature-tag-list<BR>
<BR>
<BR>
4. Retry-After:<BR>
a) 16.40 allows this header to specify seconds or a date, the syntax =
only allows delta-seconds.<BR>
b) What is the comment for? Maintenance description?<BR>
c) Usage of duration retry-param is not described in 16.40 nor anywhere =
else<BR>
<BR>
Suggestion (assuming no further description text is added):<BR>
<BR>
Retry-After&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =3D =
&quot;Retry-After&quot; HCOLON ( RTSP-date / delta-seconds )<BR>
<BR>
<BR>
5. channel (for transport parameter)<BR>
I suggest a comment like at ttl:<BR>
<BR>
channel&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; =3D 1*3DIGIT ; 0 to 255<BR>
<BR>
<BR>
6. User-Agent<BR>
I guess the syntax should be identical to the one of Server; the extra =
'0' for the * list is unnecessary.<BR>
<BR>
<BR>
II) Things I might have not properly understood:<BR>
<BR>
1. Accept-Language:<BR>
The header allows to be empty. If this is the case, does this mean all =
languages have a q value of 1 or does the last sentence in 16.4 imply NO =
language is acceptable: &quot;If an Accept-Language header is present, =
then all languages which are assigned a quality factor greater than 0 =
are acceptable.&quot;<BR>
I guess it of course means all languages are equally acceptable, =
especially with the default q value of 1 -- yet, does this mean for all =
explicitly given languages or all the server knows of which are not =
explicitly given?<BR>
<BR>
<BR>
2. Allow:<BR>
This header may also be empty. How can I reach a valid resource that =
does not produce 404, but 405 and allows no request to be performed?<BR>
<BR>
<BR>
3. Content-Type:<BR>
May be given in SIP-like short form &quot;c&quot; -- This is the only =
header to allow this according to the syntax.<BR>
Why?<BR>
<BR>
<BR>
Regards,<BR>
ch<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: mmusic-bounces@ietf.org on behalf of HAAS Christian<BR>
Sent: Fri 9/25/2009 7:23 AM<BR>
To: mmusic@ietf.org<BR>
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22<BR>
<BR>
Hello all!<BR>
<BR>
I've read through the draft (skipping the syntax definitions) and found =
only<BR>
minor issues regarding wording, typos and consistency so far, which I =
already<BR>
sent to Magnus directly.<BR>
<BR>
I will try to find some time during the upcoming days for a dedicated =
check<BR>
of the syntax.<BR>
<BR>
Regards,<BR>
ch<BR>
____________________________________________________<BR>
Christian Haas<BR>
Team DIVOS, Software Engineer<BR>
FREQUENTIS AG<BR>
<BR>
Innovationsstra=DFe 1, 1100 Vienna, Austria<BR>
Phone&nbsp;&nbsp; +43-1-811 50 - 8353<BR>
Mobile&nbsp;&nbsp; +43-664-60 850 - 8353<BR>
Fax&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +43-1-811 50 - 77 8353<BR>
Web&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; www.frequentis.com<BR>
E-Mail&nbsp;&nbsp;&nbsp; christian.haas@frequentis.com<BR>
<BR>
Handelsgericht Wien (Vienna Commercial Court): FN 72115 b<BR>
DVR 0364797, ATU 14715600<BR>
____________________________________________________<BR>
Diese E-Mail k=F6nnte vertrauliche und/oder rechtlich gesch=FCtzte =
Informationen<BR>
enthalten. Wenn Sie nicht der richtige Adressat sind oder diese =
E-Mail<BR>
irrt=FCmlich erhalten haben, informieren Sie bitte sofort den Absender =
und<BR>
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die =
unbefugte<BR>
Weitergabe dieser E-Mail sind nicht gestattet.<BR>
This e-mail may contain confidential and/or privileged information. If =
you<BR>
are not the intended recipient (or have received this e-mail in error) =
please<BR>
notify the sender immediately and destroy this e-mail. Any =
unauthorised<BR>
copying, disclosure or distribution of the material in this e-mail =
is<BR>
strictly forbidden.<BR>
<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: mmusic-bounces@ietf.org [<A =
HREF=3D"mailto:mmusic-bounces@ietf.org">mailto:mmusic-bounces@ietf.org</A=
>] On Behalf Of<BR>
Joerg Ott<BR>
Sent: Sonntag, 20. September 2009 18:19<BR>
To: mmusic@ietf.org<BR>
Cc: Magnus Westerlund; Jean-Francois Mule; Martin Stiemerling<BR>
Subject: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22<BR>
<BR>
Folks,<BR>
<BR>
as agreed in Stockholm, we are issuing working group last call on the =
revised<BR>
RTSP spec, draft-ietf-mmusic-rfc2326bis-22 heading for Proposed =
Standard.<BR>
(<A =
HREF=3D"http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22">http:=
//tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22</A>)<BR>
<BR>
The WGLC will expire in four weeks, on 19 Oct 2009.<BR>
<BR>
We know that this is a long spec, the more important is it to =
receive<BR>
thorough review by the community.&nbsp; While we have three volunteer =
reviewers<BR>
(thanks again!), we urge everyone who cares to provide detailed =
feedback.<BR>
<BR>
Please review the document and post your comments to the MMUSIC list =
and/or<BR>
the authors.<BR>
<BR>
Thanks,<BR>
Joerg<BR>
<BR>
MMUSIC co-chair<BR>
<BR>
_______________________________________________<BR>
mmusic mailing list<BR>
mmusic@ietf.org<BR>
<A =
HREF=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.or=
g/mailman/listinfo/mmusic</A><BR>
_______________________________________________<BR>
mmusic mailing list<BR>
mmusic@ietf.org<BR>
<A =
HREF=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.or=
g/mailman/listinfo/mmusic</A><BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01CA440C.A7FA7ADB--

From root@core3.amsl.com  Thu Oct  8 14:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 7C0723A68C7; Thu,  8 Oct 2009 14: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: <20091008213001.7C0723A68C7@core3.amsl.com>
Date: Thu,  8 Oct 2009 14:30:01 -0700 (PDT)
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-11.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Oct 2009 21: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 Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: An Extension to the Session Description Protocol (SDP) for Media Loopback
	Author(s)	: C. Sivachelvan, N. Venna, P. Jones, N. Stratton, A. Roychowdhury, K. Hedayat
	Filename	: draft-ietf-mmusic-media-loopback-11.txt
	Pages		: 33
	Date		: 2009-10-7
	
The wide deployment of Voice over IP (VoIP), Real-time Text and 
    Video over IP services has introduced new challenges in managing 
    and maintaining voice/real-time Text/video quality, reliability, 
    and overall performance.  In particular, media delivery is an area 
    that needs attention.  One method of meeting these challenges is 
    monitoring the media delivery performance by looping media back to 
    the transmitter.  This is typically referred to as "active 
    monitoring" of services.   Media loopback is especially popular in 
    ensuring the quality of transport to the edge of a given VoIP, 
    Real-time Text or Video over IP service.  Today in networks that 
    deliver real-time media, short of running 'ping' and 'traceroute' 
    to the edge, service providers are left without the necessary tools 
    to actively monitor, manage, and diagnose quality issues with their 
    service.  The extension defined herein adds new SDP media 
    attributes which enables establishment of media sessions where the 
    media is looped back to the transmitter. Such media sessions will 
    serve as monitoring and troubleshooting tools by providing the 
    means for measurement of more advanced VoIP, Real-time Text and 
    Video Over IP performance metrics.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-media-loopback-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-mmusic-media-loopback-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--


From jf.mule@cablelabs.com  Fri Oct  9 01:32:59 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 129C828C1C0 for <mmusic@core3.amsl.com>; Fri,  9 Oct 2009 01:32:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.243
X-Spam-Level: 
X-Spam-Status: No, score=-0.243 tagged_above=-999 required=5 tests=[AWL=0.220,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 lDbf3kKV6dGx for <mmusic@core3.amsl.com>; Fri,  9 Oct 2009 01:32:58 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 3733128C108 for <mmusic@ietf.org>; Fri,  9 Oct 2009 01:32:58 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n998YcQm009527; Fri, 9 Oct 2009 02:34:39 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Fri, 9 Oct 2009 02:34:39 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 9 Oct 2009 02:34:24 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C6024FE9D9@srvxchg3.cablelabs.com>
In-Reply-To: <20091008213001.7C0723A68C7@core3.amsl.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Update of draft-ietf-mmusic-media-loopback-11.txt
Thread-Index: AcpIXsDxgrCJqE1PTvezk1pCbWtiSQAWsILQ
References: <20091008213001.7C0723A68C7@core3.amsl.com>
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <draft-ietf-mmusic-media-loopback@tools.ietf.org>
X-Approved: ondar
Cc: mmusic@ietf.org
Subject: [MMUSIC] Update of draft-ietf-mmusic-media-loopback-11.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2009 08:32:59 -0000

   At the last IETF meeting in July, we discussed the status of your
draft.
See the WG meeting notes in the proceedings.
Hadriel mentioned that there were a few comments that had not been
addressed and the action was for Hadriel to sync up with you and work on
the changes to get the draft ready for publication request.

  I just looked at the ID update you submitted this week using the diff
on tools.ietf.org.
All I can see in draft-11 is:
	- the I-D date and company refresh for two of the authors
	- the addition of some text in the Copyright Notice:
"Code Components extracted from this
document must include Simplified BSD License text as described in=09
Section 4.e of the Trust Legal Provisions and are provided without=09
warranty as described in the BSD License."


   Can the authors go through the list of open comments and close them
by sending a summary to the mmusic list?
In particular, those comments referred by  Hadriel at the mike in
Stockholm?
 =20
A draft update with draft-12 addressing the last comments received would
be appreciated.

Thank you,
Jean-Francois
MMUSIC co-chair.


> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
> Behalf Of Internet-Drafts@ietf.org
> Sent: Thursday, October 08, 2009 3:30 PM
> To: i-d-announce@ietf.org
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-
> 11.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session
> Control Working Group of the IETF.
>=20
> 	Title		: An Extension to the Session Description
> Protocol (SDP) for Media Loopback
> 	Author(s)	: C. Sivachelvan, N. Venna, P. Jones, N.
> Stratton, A. Roychowdhury, K. Hedayat
> 	Filename	: draft-ietf-mmusic-media-loopback-11.txt
> 	Pages		: 33
> 	Date		: 2009-10-7
>=20
> The wide deployment of Voice over IP (VoIP), Real-time Text and
>     Video over IP services has introduced new challenges in
> managing
>     and maintaining voice/real-time Text/video quality,
> reliability,
>     and overall performance.  In particular, media delivery is an
> area
>     that needs attention.  One method of meeting these challenges
> is
>     monitoring the media delivery performance by looping media back
> to
>     the transmitter.  This is typically referred to as "active
>     monitoring" of services.   Media loopback is especially popular
> in
>     ensuring the quality of transport to the edge of a given VoIP,
>     Real-time Text or Video over IP service.  Today in networks
> that
>     deliver real-time media, short of running 'ping' and
> 'traceroute'
>     to the edge, service providers are left without the necessary
> tools
>     to actively monitor, manage, and diagnose quality issues with
> their
>     service.  The extension defined herein adds new SDP media
>     attributes which enables establishment of media sessions where
> the
>     media is looped back to the transmitter. Such media sessions
> will
>     serve as monitoring and troubleshooting tools by providing the
>     means for measurement of more advanced VoIP, Real-time Text and
>     Video Over IP performance metrics.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-media-
> loopback-11.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

From jf.mule@cablelabs.com  Fri Oct  9 07:24:55 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7BA33A69C2 for <mmusic@core3.amsl.com>; Fri,  9 Oct 2009 07:24:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.283
X-Spam-Level: 
X-Spam-Status: No, score=-0.283 tagged_above=-999 required=5 tests=[AWL=0.179,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001]
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 36vT3pqFGiCE for <mmusic@core3.amsl.com>; Fri,  9 Oct 2009 07:24:45 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 40D3C28C11A for <mmusic@ietf.org>; Fri,  9 Oct 2009 07:24:45 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n99EQ0CB030415; Fri, 9 Oct 2009 08:26:00 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Fri, 9 Oct 2009 08:26:00 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
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_01CA48EC.6C9DF95B"
Date: Fri, 9 Oct 2009 08:25:43 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C6024FE9E9@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of IKE/IPsec media description in SDP, draft-saito-mmusic-sdp-ike-05
Thread-Index: AcpI7GJvWu3gvbdQS4OoW1GPugdlJg==
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: "Makoto Saito" <ma.saito@nttv6.jp>, <dwing@cisco.com>, "Shintaro Mizuno" <sk1002@fancy.ocn.ne.jp>
X-Approved: ondar
Cc: mmusic@ietf.org
Subject: [MMUSIC] Review of IKE/IPsec media description in SDP, draft-saito-mmusic-sdp-ike-05
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2009 14:24:55 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA48EC.6C9DF95B
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

This is a partial review of an individual draft, Media Description for
IKE in the Session Description Protocol,
http://tools.ietf.org/html/draft-saito-mmusic-sdp-ike-05. Note that a
Security Directorate review has been requested via Tim Polk.

=20

It is my understanding that this draft has been around for almost 3
years. Some operators have deployed applications based on the mechanism
described in the document. =20

=20

This review is done at the request of the authors who intend to request
publication as an informational RFC.  Additional reviews and comments
are welcome.

=20

=20

--- http://tools.ietf.org/html/draft-saito-mmusic-sdp-ike-05

--- Technical comments and questions

=20

*         General questions

I'm not sure if all the points below need to be addressed in the
document but there are questions that popped up reviewing the draft:

=20

o    Handling of provisional SIP responses:

Is there a need to mandate that the first response from the answering
entity should be a final response, and not a provisional response? =20

If a provisional response is allowed, does it need to be sent reliably?

If the SIP UA sending the INVITE receives an unreliable provisional
response containing SDP, what does it do?

=20

o    Handling of multiple SDP media lines

The draft should cover the cases where a Remote Client offers multiple
media lines, for example one with media format of "ike-esp" and another
with media format for an audio codec.

=20

o    Forking

Can the INVITE be forked to multiple registered instances? Probably
doesn't make sense for this application -- so should you add text that
says there is only one registered instance?

If multiple registered instances are allowed, how is forking handled?

=20

o    SIP session and VPN state sync?

There is little bit of text on page-8, para-2 on this but it prompts
more questions.

How does either the Remote Client or Home Router detect when an
established VPN fail? Is there a native "keep-alive" supported by VPN.=20

Should the RFC 4028 "SIP session timer" extension be supported?

Is there any need to re-authenticate an established VPN, say if some
security association times out (i.e., can the Remote Client re-INVITE
the session)?

Basically, how are the SIP dialog and VPN states maintained
(independently, does a state change to a SIP termination state implies
the VPN is terminated, vice-versa).

=20

*         Security comments and questions

The mechanism is based on the assumption that the SDP media description
is protected using encryption. =20

You have text on page-5 section 1.2 as part of the "background" but it
would be good to call this out in the document, and create a specific
section on it.  It could take the form of an Applicability Statement
(see http://tools.ietf.org/html/rfc3325#section-1) to reinforce the
requirements that must be met in order for the solution to be of any
meaningful use.

=20

On a different note, if the remote client and home router are
pre-configured with a shared secret or a certificate issued by a trusted
CA, is there a need to have a hash fingerprint in the SDP to identify
which certificate or secret to use?

=20

=20

*         Security - authorization and user authentication model

This is related to Page-5, para-2, Page-19 in Security Consideration and
other places in the document.

It is mentioned that SIP is used for name resolution and authorization.
It is unclear to me where it is described who is responsible for
ensuring that only authorized clients can use this mechanism to gain
access the Home Router.

Say there are three Remote Clients; RC-1, RC-2, RC-3, and three Home
Routers (in different homes); HR-a, HR-b, HR-c. And say that only the
following combinations are allowed for IKE:=20

 RC-1 to HR-a

 RC-2 to HR-b

 RC-3 to HR-c

If RC-1 attempts to establish an IKE session with HR-2, who blocks it?
Based on what information in the SIP signaling or IKE exchange?

Basically, the model for service authorization needs to be explained in
more details.

In the scenario where service authorization is done by the "SIP cloud",
could the user behind the Remote Client be authorized to initiate an IKE
session independent of the terminating Home Router user? And could the
Home Router user authorize the IKE session independent of the initiating
RC user? =20

Some text on this would help.

=20

*         Page-5, para-6:

Do any of the RFC 4474 deficiencies discussed in DISPATCH affect this
document (e.g., issues related to B2BUA traversal)? For more info, see
http://tools.ietf.org/html/draft-rosenberg-sip-rfc4474-concerns-00.

=20

*         Page-7 Section-2 Protocol Overview:

Comments on Figure-1, step 3:

This 3rd step says...

    "After SDP exchange, Remote Client (SDP offerer)

     initiates IKE with the SDP answerer to establish

     IPsec SA."=20

This is not accurate, since the offer/answer negotiation can result in
either end initiating the IKE session.  Indicate the active role to
address this comment.=20

=20

=20

*         Page-9, section-3 Protocol Identifier:

Given you are re-using the values of the "setup" attribute from RFC
4145, suggest being specific in the sentence below.

=20

Change...

<  The semantics of "active", "passive", and "actpass" in the offer/

<  answer exchange is the same as the definition described in 4.1 of RFC

<  4145.=20

=20

To...

>   The semantics for the "udp-setup" attribute values of "active",

>   "passive", and "actpass" in the offer/answer exchange are the same
as=20

>   that described for the "setup" attribute in 4.1 of RFC 4145, except
that

>   it applies to an IKE session instead of a TCP connection.=20

=20

*         Page-9, section-3 Protocol Identifier:

This section would benefit some rewrite to normatively define what each
new SDP parameter defines.

For example, paragraph 1 could define the new SDP attributes more
clearly:

=20
This document defines two SDP media formats for the "udp" protocol under
the "application" media type, "ike-esp" and "ike-esp-udpencap":
        + "ike-esp" indicates that the media described is IKE for the
establishment of an IPsec security association as described in IPsec ESP
as specified in []...=20
        + "ike-esp-udpencap" indicates that the media described is IKE
for the establishment of UDP encapsulation of IPsec packets through NAT
boxes as specified in []...

=20

=20

*         Page-12, section 5.2 Offer and Answer Exchange with ICE:

a) It would be good to add a few sentences to explain that the mechanism
that ICE specifies for keeping NAT bindings open for RTP & RTCP traffic
does work for UDP encapsulated IKE exchanges.

b) The use of "UDP session" in sections 5.2, 5.3 and other parts of the
document is improper.  There are UDP-based media sessions but there is
no such thing as a UDP session.  Consider rewording the sentences that
explain the needs to multiplex several types of UDP packets over the
same UDP ports, something like that.

=20

*         Page 20, section 9 IANA Considerations

 This section must be written to ask IANA to register the attributes.

See the requirements in http://tools.ietf.org/html/rfc4566#section-8.2.8
and a good example in
http://tools.ietf.org/html/draft-ietf-mmusic-sdp-capability-negotiation-
10#page-72=20

=20

=20

--- Editorial and other comments

The document needs to be scrubbed for grammar errors, conversational
phrasing (e.g., "by the way..."), run-on sentences, etc.  I will send a
list of nits directly to the authors.

=20

idnits 2.11.14 reports 4 warnings and 1 comment; check the results at
http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft-saito-m=
m
usic-sdp-ike-05.txt

=20

Acknowledgment: David Hancock and Stuart Hoggan provided input into the
above review - many thanks to them.

=20

Regards,

Jean-Francois as an individual contributor.

=20


------_=_NextPart_001_01CA48EC.6C9DF95B
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Courier;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:99;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, =
div.MsoListParagraphCxSpFirst
	{mso-style-priority:99;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, =
div.MsoListParagraphCxSpMiddle
	{mso-style-priority:99;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, =
div.MsoListParagraphCxSpLast
	{mso-style-priority:99;
	mso-style-type:export-only;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Courier;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:595.0pt 842.0pt;
	margin:1.0in 45.45pt 1.0in 45.45pt;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1521966053;
	mso-list-type:hybrid;
	mso-list-template-ids:1780001880 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>This
is a partial review of an individual draft, Media Description for IKE in =
the
Session Description Protocol, <a
href=3D"http://tools.ietf.org/html/draft-saito-mmusic-sdp-ike-05">http://=
tools.ietf.org/html/draft-saito-mmusic-sdp-ike-05</a>.
Note that a Security Directorate review has been requested via Tim =
Polk.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>It
is my understanding that this draft has been around for almost 3 years. =
Some
operators have deployed applications based on the mechanism described in =
the
document.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>This
review is done at the request of the authors who intend to request =
publication
as an informational RFC.&nbsp; Additional reviews and comments are =
welcome.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:green'>--- =
http://tools.ietf.org/html/draft-saito-mmusic-sdp-ike-05<o:p></o:p></span=
></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:green'>--- Technical comments and questions<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>General questions<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>I&#8217;m
not sure if all the points below need to be addressed in the document =
but there
are questions that popped up reviewing the draft:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Handling of =
provisional SIP
responses:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Is
there a need to mandate that the first response from the answering =
entity
should be a final response, and not a provisional response?&nbsp; =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>If
a provisional response is allowed, does it need to be sent =
reliably?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>If
the SIP UA sending the INVITE receives an unreliable provisional =
response
containing SDP, what does it do?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>Handling of =
multiple SDP
media lines<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>The
draft should cover the cases where a Remote Client offers multiple media =
lines,
for example one with media format of &quot;ike-esp&quot; and another =
with media
format for an audio codec.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Forking<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Can
the INVITE be forked to multiple registered instances? Probably doesn't =
make
sense for this application -- so should you add text that says there is =
only
one registered instance?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>If
multiple registered instances are allowed, how is forking =
handled?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;
mso-list:l0 level2 lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><span style=3D'mso-list:Ignore'>o<span
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span
style=3D'font-size:10.0pt;font-family:"Courier New"'>SIP session and VPN =
state
sync?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>There
is little bit of text on page-8, para-2 on this but it prompts more =
questions.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>How
does either the Remote Client or Home Router detect when an established =
VPN
fail? Is there a native &quot;keep-alive&quot; supported by VPN. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Should
the RFC 4028 &quot;SIP session timer&quot; extension be =
supported?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Is
there any need to re-authenticate an established VPN, say if some =
security
association times out (i.e., can the Remote Client re-INVITE the =
session)?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Basically,
how are the SIP dialog and VPN states maintained (independently, does a =
state
change to a SIP termination state implies the VPN is terminated, =
vice-versa).<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Security comments and questions<o:p></o:p></span></b></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>The
mechanism is based on the assumption that the SDP media description is
protected using encryption.&nbsp; <o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>You
have text on page-5 section 1.2 as part of the &#8220;background&#8221; =
but it
would be good to call this out in the document, and create a specific =
section
on it.&nbsp; It could take the form of an Applicability Statement (see =
<a
href=3D"http://tools.ietf.org/html/rfc3325#section-1">http://tools.ietf.o=
rg/html/rfc3325#section-1</a>)
to reinforce the requirements that must be met in order for the solution =
to be
of any meaningful use.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>On
a different note, if the remote client and home router are =
pre-configured with
a shared secret or a certificate issued by a trusted CA, is there a need =
to
have a hash fingerprint in the SDP to identify which certificate or =
secret to
use?<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Security - authorization and user authentication =
model<o:p></o:p></span></b></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>This
is related to Page-5, para-2, Page-19 in Security Consideration and =
other
places in the document.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>It
is mentioned that SIP is used for name resolution and =
authorization.&nbsp; It is
unclear to me where it is described who is responsible for ensuring that =
only
authorized clients can use this mechanism to gain access the Home =
Router.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Say
there are three Remote Clients; RC-1, RC-2, RC-3, and three Home Routers =
(in
different homes); HR-a, HR-b, HR-c. And say that only the following
combinations are allowed for IKE: <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;RC-1
to HR-a<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;RC-2
to HR-b<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;RC-3
to HR-c<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>If
RC-1 attempts to establish an IKE session with HR-2, who blocks it? =
Based on
what information in the SIP signaling or IKE =
exchange?<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Basically,
the model for service authorization needs to be explained in more =
details.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>In
the scenario where service authorization is done by the &#8220;SIP =
cloud&#8221;,
could the user behind the Remote Client be authorized to initiate an IKE
session independent of the terminating Home Router user? And could the =
Home
Router user authorize the IKE session independent of the initiating RC =
user?&nbsp; <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Some
text on this would help.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Page-5, para-6:<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Do
any of the RFC 4474 deficiencies discussed in DISPATCH affect this =
document
(e.g., issues related to B2BUA traversal)? For more info, see <a
href=3D"http://tools.ietf.org/html/draft-rosenberg-sip-rfc4474-concerns-0=
0">http://tools.ietf.org/html/draft-rosenberg-sip-rfc4474-concerns-00</a>=
.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Page-7 Section-2 Protocol =
Overview:<o:p></o:p></span></b></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Comments
on Figure-1, step 3:<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>This
3rd step says...<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp;&nbsp;
&quot;After SDP exchange, Remote Client (SDP =
offerer)<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;
initiates IKE with the SDP answerer to establish<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;
IPsec SA.&quot; <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>This
is not accurate, since the offer/answer negotiation can result in either =
end
initiating the IKE session.&nbsp; Indicate the active role to address =
this comment. <o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Page-9, section-3 Protocol =
Identifier:<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Given
you are re-using the values of the &#8220;setup&#8221; attribute from =
RFC 4145,
suggest being specific in the sentence below.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Change...<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&lt;&nbsp;
The semantics of &quot;active&quot;, &quot;passive&quot;, and
&quot;actpass&quot; in the offer/<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&lt;&nbsp;
answer exchange is the same as the definition described in 4.1 of =
RFC<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&lt;&nbsp;
4145. <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>To...<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&gt;&nbsp;&nbsp;
The semantics for the &quot;udp-setup&quot; attribute values of
&quot;active&quot;,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&gt;&nbsp;&nbsp;
&quot;passive&quot;, and &quot;actpass&quot; in the offer/answer =
exchange are
the same as <o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&gt;&nbsp;&nbsp;
that described for the &quot;setup&quot; attribute in 4.1 of RFC 4145, =
except
that<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&gt;&nbsp;&nbsp;
it applies to an IKE session instead of a TCP connection. =
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Page-9, section-3 Protocol =
Identifier:<o:p></o:p></span></b></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>This
section would benefit some rewrite to normatively define what each new =
SDP
parameter defines.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>For
example, paragraph 1 could define the new SDP attributes more =
clearly:<o:p></o:p></span></p>

<pre><span style=3D'font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></pre><pre><span
style=3D'font-family:"Courier New"'>This document defines two SDP media =
formats for the &#8220;udp&#8221; protocol under the =
&#8220;application&#8221; media type, &quot;ike-esp&quot; and =
&quot;ike-esp-udpencap&quot;:<o:p></o:p></span></pre><pre><span
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + &quot;ike-esp&quot; =
indicates that the media described is IKE for the establishment of an =
IPsec security association as described in IPsec ESP as specified in =
[]... <o:p></o:p></span></pre><pre><span
style=3D'font-family:"Courier =
New"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; + =
&quot;ike-esp-udpencap&quot; indicates that the media described is IKE =
for the establishment of UDP encapsulation of IPsec packets through NAT =
boxes as specified in []...<o:p></o:p></span></pre>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-size:10.0pt;font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Page-12, section 5.2 Offer and Answer Exchange with =
ICE:<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>a)
It would be good to add a few sentences to explain that the mechanism =
that ICE
specifies for keeping NAT bindings open for RTP &amp; RTCP traffic does =
work
for UDP encapsulated IKE exchanges.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>b)
The use of &#8220;UDP session&#8221; in sections 5.2, 5.3 and other =
parts of
the document is improper.&nbsp; There are UDP-based media sessions but =
there is no
such thing as a UDP session.&nbsp; Consider rewording the sentences that =
explain the
needs to multiplex several types of UDP packets over the same UDP ports,
something like that.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><a
name=3Dsection-9></a><![if !supportLists]><span =
style=3D'font-size:10.0pt;
font-family:Symbol'><span style=3D'mso-list:Ignore'>&middot;<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><b><span =
style=3D'font-size:10.0pt;font-family:
"Courier New"'>Page 20, section 9 IANA =
Considerations<o:p></o:p></span></b></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;This
section must be written to ask IANA to register the =
attributes.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>See
the requirements in <a =
href=3D"http://tools.ietf.org/html/rfc4566#section-8.2.8">http://tools.ie=
tf.org/html/rfc4566#section-8.2.8</a>
and a good example in <a
href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-sdp-capability-negot=
iation-10#page-72">http://tools.ietf.org/html/draft-ietf-mmusic-sdp-capab=
ility-negotiation-10#page-72</a>
<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New";
color:green'>--- Editorial and other comments<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>The
document needs to be scrubbed for grammar errors, conversational =
phrasing
(e.g., &quot;by the way...&quot;), run-on sentences, etc.&nbsp; I will =
send a list
of nits directly to the authors.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>idnits
2.11.14 reports 4 warnings and 1 comment; check the results at <a
href=3D"http://tools.ietf.org/idnits?url=3Dhttp://tools.ietf.org/id/draft=
-saito-mmusic-sdp-ike-05.txt">http://tools.ietf.org/idnits?url=3Dhttp://t=
ools.ietf.org/id/draft-saito-mmusic-sdp-ike-05.txt</a><o:p></o:p></span><=
/p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Acknowledgment:
David Hancock and Stuart Hoggan provided input into the above review =
&#8211;
many thanks to them.<o:p></o:p></span></p>

<p class=3DMsoPlainText><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoPlainText><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'>Regards,<o:p></o:p></span></p>

<p class=3DMsoPlainText><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Jean-Francois
as an individual contributor.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01CA48EC.6C9DF95B--

From kaynam.hedayat@exfo.com  Mon Oct 12 06:42:11 2009
Return-Path: <kaynam.hedayat@exfo.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 744E63A687D for <mmusic@core3.amsl.com>; Mon, 12 Oct 2009 06:42:11 -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 ZMPY8TaY-e25 for <mmusic@core3.amsl.com>; Mon, 12 Oct 2009 06:42:09 -0700 (PDT)
Received: from smtpinqc.exfo.com (smtpinqc.exfo.com [206.162.164.97]) by core3.amsl.com (Postfix) with ESMTP id AE7AC3A6870 for <mmusic@ietf.org>; Mon, 12 Oct 2009 06:42:09 -0700 (PDT)
Received: from spqcexc04.exfo.com ([172.16.48.171]) by smtpinqc.exfo.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Oct 2009 09:42:09 -0400
Received: from spboexc01.exfo.com ([10.10.10.16]) by spqcexc04.exfo.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 12 Oct 2009 09:42:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 12 Oct 2009 09:42:06 -0400
Message-ID: <86F9069E07A5EC4E890AF73FD8E85E172ACB77@spboexc01.exfo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Update of draft-ietf-mmusic-media-loopback-11.txt
Thread-Index: AcpIXsDxgrCJqE1PTvezk1pCbWtiSQAWsILQAKICd+A=
References: <20091008213001.7C0723A68C7@core3.amsl.com> <9AAEDF491EF7CA48AB587781B8F5D7C6024FE9D9@srvxchg3.cablelabs.com>
From: "Kaynam Hedayat" <kaynam.hedayat@exfo.com>
To: "Jean-Francois Mule" <jf.mule@cablelabs.com>, <draft-ietf-mmusic-media-loopback@tools.ietf.org>
X-OriginalArrivalTime: 12 Oct 2009 13:42:08.0979 (UTC) FILETIME=[CB551A30:01CA4B41]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-5.600.1016-16942.007
X-TM-AS-Result: No--15.574100-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
X-Mailman-Approved-At: Mon, 12 Oct 2009 08:05:38 -0700
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Update of draft-ietf-mmusic-media-loopback-11.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2009 13:42:11 -0000

Jean-Francois,

We will follow-up with Hadriel and others to close the remaining items
raised and will provide a summary to the mailing list.


Regards,
Kaynam

-----Original Message-----
From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On Behalf
Of Jean-Francois Mule
Sent: Friday, October 09, 2009 4:34 AM
To: draft-ietf-mmusic-media-loopback@tools.ietf.org
Cc: mmusic@ietf.org
Subject: [MMUSIC] Update of draft-ietf-mmusic-media-loopback-11.txt


   At the last IETF meeting in July, we discussed the status of your
draft.
See the WG meeting notes in the proceedings.
Hadriel mentioned that there were a few comments that had not been
addressed and the action was for Hadriel to sync up with you and work on
the changes to get the draft ready for publication request.

  I just looked at the ID update you submitted this week using the diff
on tools.ietf.org.
All I can see in draft-11 is:
	- the I-D date and company refresh for two of the authors
	- the addition of some text in the Copyright Notice:
"Code Components extracted from this
document must include Simplified BSD License text as described in=09
Section 4.e of the Trust Legal Provisions and are provided without=09
warranty as described in the BSD License."


   Can the authors go through the list of open comments and close them
by sending a summary to the mmusic list?
In particular, those comments referred by  Hadriel at the mike in
Stockholm?
 =20
A draft update with draft-12 addressing the last comments received would
be appreciated.

Thank you,
Jean-Francois
MMUSIC co-chair.


> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
> Behalf Of Internet-Drafts@ietf.org
> Sent: Thursday, October 08, 2009 3:30 PM
> To: i-d-announce@ietf.org
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-media-loopback-
> 11.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session
> Control Working Group of the IETF.
>=20
> 	Title		: An Extension to the Session Description
> Protocol (SDP) for Media Loopback
> 	Author(s)	: C. Sivachelvan, N. Venna, P. Jones, N.
> Stratton, A. Roychowdhury, K. Hedayat
> 	Filename	: draft-ietf-mmusic-media-loopback-11.txt
> 	Pages		: 33
> 	Date		: 2009-10-7
>=20
> The wide deployment of Voice over IP (VoIP), Real-time Text and
>     Video over IP services has introduced new challenges in
> managing
>     and maintaining voice/real-time Text/video quality,
> reliability,
>     and overall performance.  In particular, media delivery is an
> area
>     that needs attention.  One method of meeting these challenges
> is
>     monitoring the media delivery performance by looping media back
> to
>     the transmitter.  This is typically referred to as "active
>     monitoring" of services.   Media loopback is especially popular
> in
>     ensuring the quality of transport to the edge of a given VoIP,
>     Real-time Text or Video over IP service.  Today in networks
> that
>     deliver real-time media, short of running 'ping' and
> 'traceroute'
>     to the edge, service providers are left without the necessary
> tools
>     to actively monitor, manage, and diagnose quality issues with
> their
>     service.  The extension defined herein adds new SDP media
>     attributes which enables establishment of media sessions where
> the
>     media is looped back to the transmitter. Such media sessions
> will
>     serve as monitoring and troubleshooting tools by providing the
>     means for measurement of more advanced VoIP, Real-time Text and
>     Video Over IP performance metrics.
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mmusic-media-
> loopback-11.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic

From root@core3.amsl.com  Tue Oct 13 17:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 654213A685D; Tue, 13 Oct 2009 17: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: <20091014004501.654213A685D@core3.amsl.com>
Date: Tue, 13 Oct 2009 17:45:01 -0700 (PDT)
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-ice-tcp-08.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2009 00: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 Multiparty Multimedia Session Control Working Group of the IETF.


	Title           : TCP Candidates with Interactive Connectivity Establishment (ICE)
	Author(s)       : S. Perreault, J. Rosenberg
	Filename        : draft-ietf-mmusic-ice-tcp-08.txt
	Pages           : 19
	Date            : 2009-10-13

Interactive Connectivity Establishment (ICE) defines a mechanism for
NAT traversal for multimedia communication protocols based on the
offer/answer model of session negotiation.  ICE works by providing a
set of candidate transport addresses for each media stream, which are
then validated with peer-to-peer connectivity checks based on Session
Traversal Utilities for NAT (STUN).  ICE provides a general framework
for describing candidates, but only defines UDP-based transport
protocols.  This specification extends ICE to TCP-based media,
including the ability to offer a mix of TCP and UDP-based candidates
for a single stream.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-ice-tcp-08.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-mmusic-ice-tcp-08.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From simon.perreault@viagenie.ca  Tue Oct 13 17:58:49 2009
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A75F3A690B for <mmusic@core3.amsl.com>; Tue, 13 Oct 2009 17:58:49 -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 qWV+zWddLiRZ for <mmusic@core3.amsl.com>; Tue, 13 Oct 2009 17:58:48 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 48B3A3A68A8 for <mmusic@ietf.org>; Tue, 13 Oct 2009 17:58:48 -0700 (PDT)
Received: from balaise.lan (modemcable245.152-21-96.mc.videotron.ca [96.21.152.245]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C5D7220E2F for <mmusic@ietf.org>; Tue, 13 Oct 2009 20:58:49 -0400 (EDT)
From: Simon Perreault <simon.perreault@viagenie.ca>
To: mmusic@ietf.org
Date: Tue, 13 Oct 2009 20:58:48 -0400
User-Agent: KMail/1.12.0 (Linux/2.6.30.5-43.fc11.x86_64; KDE/4.3.1; x86_64; ; )
References: <20091014004501.654213A685D@core3.amsl.com>
In-Reply-To: <20091014004501.654213A685D@core3.amsl.com>
Organization: =?iso-8859-15?q?Viag=E9nie?=
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <200910132058.48985.simon.perreault@viagenie.ca>
Subject: Re: [MMUSIC] I-D Action:draft-ietf-mmusic-ice-tcp-08.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2009 00:58:49 -0000

On Tuesday 13 October 2009 20:45:01 Internet-Drafts@ietf.org wrote:
> 	Title           : TCP Candidates with Interactive Connectivity
> Establishment (ICE) Author(s)       : S. Perreault, J. Rosenberg
> 	Filename        : draft-ietf-mmusic-ice-tcp-08.txt
> 	Pages           : 19
> 	Date            : 2009-10-13

This new revision is an effort to gauge what is the interest in ICE-TCP and 
where it should go. There is only one change, the addition of this paragraph:

      Note: It has been reported that the simultaneous-open technique
      has a low success rate (~40%) with the population of NAT devices
      in use as of this writing.  Therefore, it is RECOMMENDED that
      implementations of this specification acquire and use IPv6 host
      candidates.  Means of doing so across NATs include Tunnel Setup
      Protocol [I-D.blanchet-v6ops-tunnelbroker-tsp], Teredo [RFC4380],
      IPSec NAT-T [RFC3947], and others.


Two questions for this WG:

- Should this effort be dropped or continue?

- What is needed for this draft to get WG consensus?

Thanks, and sorry for not posting this sooner,
Simon
-- 
DNS64 open-source   --> http://ecdysis.viagenie.ca
STUN/TURN server    --> http://numb.viagenie.ca
vCard 4.0           --> http://www.vcarddav.org

From jf.mule@cablelabs.com  Wed Oct 14 09:10:20 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ADDF3A6929 for <mmusic@core3.amsl.com>; Wed, 14 Oct 2009 09:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 qo2SxGsnOgLK for <mmusic@core3.amsl.com>; Wed, 14 Oct 2009 09:10:19 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 9C6AD3A6864 for <mmusic@ietf.org>; Wed, 14 Oct 2009 09:10:19 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n9EGAKHm030404; Wed, 14 Oct 2009 10:10:20 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Wed, 14 Oct 2009 10:10:20 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
x-cr-hashedpuzzle: Ah0z E/V/ FQo1 FdPd GHK/ HPGd H/gv J19h RFy1 RhJ8 Wwi1 XGx3 X5TT Y0YR c4rW fVXi; 3; ZAByAGEAZgB0AC0AaQBlAHQAZgAtAG0AbQB1AHMAaQBjAC0AcgBmAGMANAA3ADUANgBiAGkAcwBAAHQAbwBvAGwAcwAuAGkAZQB0AGYALgBvAHIAZwA7AGoAbwBAAG4AZQB0AGwAYQBiAC4AdABrAGsALgBmAGkAOwBtAG0AdQBzAGkAYwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {608733BD-D964-41CC-9BED-4010B7A58282}; agBmAC4AbQB1AGwAZQBAAGMAYQBiAGwAZQBsAGEAYgBzAC4AYwBvAG0A; Wed, 14 Oct 2009 16:10:10 GMT; VwBHAEwAQwAgAG8AbgAgAGQAcgBhAGYAdAAtAGkAZQB0AGYALQBtAG0AdQBzAGkAYwAtAHIAZgBjADQANwA1ADYAYgBpAHMALQAwADMA
x-cr-puzzleid: {608733BD-D964-41CC-9BED-4010B7A58282}
Content-class: urn:content-classes:message
Date: Wed, 14 Oct 2009 10:10:10 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WGLC on draft-ietf-mmusic-rfc4756bis-03
Thread-Index: AcpM6M4YlHJPdxh7ScGv3yGY13jt2w==
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <mmusic@ietf.org>
X-Approved: ondar
Cc: Joerg Ott <jo@netlab.tkk.fi>, draft-ietf-mmusic-rfc4756bis@tools.ietf.org
Subject: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2009 16:10:20 -0000

This is to start a 2-week working group last call on draft
draft-ietf-mmusic-rfc4756bis-03,
http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-03.  The comment
period will end on Wednesday October 28.

Please send your comments to the mmusic list and the authors.

Thank you,
Jean-Francois.



From jf.mule@cablelabs.com  Wed Oct 14 15:31:44 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C28213A69C4 for <mmusic@core3.amsl.com>; Wed, 14 Oct 2009 15:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 ZS0N+T6pFC0x for <mmusic@core3.amsl.com>; Wed, 14 Oct 2009 15:31:43 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 9A4DB3A67AE for <mmusic@ietf.org>; Wed, 14 Oct 2009 15:31:43 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n9EMVitX031797; Wed, 14 Oct 2009 16:31:45 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Wed, 14 Oct 2009 16:31:45 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 14 Oct 2009 16:31:28 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC96@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on draft-ietf-mmusic-rfc4756bis-03
Thread-Index: AcpM6M4YlHJPdxh7ScGv3yGY13jt2wABIsPQ
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <draft-ietf-mmusic-rfc4756bis@tools.ietf.org>
X-Approved: ondar
Cc: mmusic@ietf.org
Subject: [MMUSIC] Comments on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2009 22:31:44 -0000

Ali,

   The draft is well written and provides clear justifications for the
updates to RFC 4756.

   Below are a few comments for your consideration.

Regards,
Jean-Francois.

- Document frontpage:
Given this draft extends the group and ssrc-group attributes with new
semantics (a=3Dgroup:FEC-XR, a=3Dssrc-group:FEC-XR), the boiler plate =
should
indicate that this document does update RFC 3388bis and RFC 5576, I
think.=20

- page 4, para 4: typo
s/the grouping semantics defined in this document offers flexibility
about which source streams can be grouped together prior to FEC
protection/ the grouping semantics defined in this document offer the
flexibility to determine how source streams are grouped together prior
to applying FEC protection

- page 5, numbered bullets=20
(see next comment)
a) You summarize a few FEC framework requirements. =20
I suppose they are contained in the document, if so put the document
reference [].
b) I'm not sure about this comment but I wonder whether these
requirements should be included with the capital verbs here. I would
turns those MAY into may, as they are duplicate requirements in the FEC
framework and implementations compliant with this draft would not need
to meet those as stated (see the comment below).  You only drive the one
SDP grouping semantics requirement you have below them (as a MUST).

- page 5, last sentence of section 1
Change the requirement to be more explicit on what the SDP semantics
must be able to express (and I would split bullet 3 into two bullets).
As written, the reader has to translate what the FEC requirements mean
for the SDP semantics (in reference to "these features").
Old text:
---
To summarize, the FEC Framework supports the following:
   1.  A source flow MAY be protected by multiple different FEC schemes.
   2.  An FEC scheme MAY generate multiple repair flows.
   3.  Source flows MAY be grouped prior to FEC protection.  That is,
       one or more repair flows MAY protect a group of source flows.

   To fully benefit from the flexibility provided by the FEC Framework,
   the grouping semantics for FEC MUST support these features.
---

New text:
In summary, based on the FEC Framework [], the SDP grouping semantics
for FEC MUST support the ability to indicate that:
   1.  a given source flow is protected by multiple different FEC
schemes.
   2.  multiple repair flows are associated with a given source flow
   3.  multiple source flows are grouped prior to applying FEC
protection
   4.  one or more repair flows protect a group of source flows.
--- or something like that.

- page 5, section 3
The text in section 3 should be written as if it is the new
to-be-published RFC. You should assume the draft is the RFC that
obsoletes RFC 4756 and explain what motivated some changes and
extensions. =20
This leads to a few editorial changes, some of which are suggested
below.

s/issues with RFC 4756/changes from RFC 4756 (in the section 3 heading)

- page 5, section 3.1
Consider presenting what this document defines first, and finish with
the changes from previous RFCs. =20

Example:
--- old text
   Currently, the 'group' attribute and the FEC grouping semantics
   defined in [RFC3388] and [RFC4756], respectively, are used to
   associate source and repair flows together.

   The 'group' attribute is used to group multiple repair flows with one
   or more source flows.  However, [RFC3388] prohibits an "m" line
   identified by its 'mid' attribute from appearing in more than one
   "a=3Dgroup" line using the same semantics.  This limitation prevents =
us
   from indicating specific associations between the source and repair
   flows by using an "a=3Dgroup:FEC" line per FEC Framework instance.  =
For
   example, for the scenario sketched in Figure 1, [RFC3388] mandates us
   to write

        a=3Dgroup:FEC S1 S2 R1 R2

   Clearly, this "a=3Dgroup:FEC" line does not say anything specific =
about
   which repair flows are protecting which source flows.

   A new work ([I-D.ietf-mmusic-rfc3388bis]) is currently in progress in
   the MMUSIC WG to remove this limitation in [RFC3388].  However,
   [RFC4756] also needs to be updated according to the FEC Framework
   requirements.

--- new text
   The FEC grouping semantics and 'group' attribute
   defined in this document and [RFC3388bis], respectively, are used to
   associate source and repair flows together.

   This document specifies how the SDP 'group' attribute is used to=20
   group multiple repair flows with one or more source flows. =20
   [I-D.ietf-mmusic-rfc3388bis] updates [RFC3388]
   to allow an "m" line identified by its 'mid' attribute to appear in
   more than one "a=3Dgroup" line using the same semantics. This change
   allows us a sender to indicate the specific associations between the
   source and repair flows by using an "a=3Dgroup:FEC" line per FEC
   Framework instance.=20
  =20
// change the example to show the above and how the 3388bis helps

   This document updates [RFC4756] to allow the source and repair flows
   to be associated in SDP.

--- hope this helps convey what the text should look like expressing the
same things.

- section 4.1, bottom of page 6, first 2 paragraphs of page 7
This is where having some formal MUST requirements for compliant
implementations would be beneficial.

Change:
   If there are more than one
   repair flows included in an FEC group, they are considered to be
   additive.  Repair flows that are in different FEC groups are non-
   additive.

Into something like:
   Repair flows included in the same FEC Group MUST be additive. And
   repair flows that are not additive MUST be indicated in separate
   SDP FEC group lines.

- page 8, section 4.2
s/MUST/must in "we MUST write"=20
(you have now a formal requirement in section 4.1)

- page 8, section 4.3
Change:
< Instead, the 'ssrc-group' attribute MUST be used.
With
> This document extends [RFC 5576] in two ways.  First we define how FEC
is applied to source and repair flows for SSRC multiplexed streams using
the 'ssrc-group' attribute.  We then specify how additivity of the
repair flows are expressed for SSRC multiplexed streams.

- page 8, last paragraph of section 4.3
Same comment as above for the "a=3Dgroup" lines: it would be good to =
have
2 MUST requirements to indicate that additive repairs flows MUST be on
the same a=3Dssrc-group lines while non-additive ones MUST be on =
separate
lines.

- page 9, section 4.4., last paragraph at the bottom of page 9
I would not point to RFC4756 but instead point to this draft (from my
perspective, it does not make much sense to ask implementers to first
check that there is no ambiguity with the previous RFC.

- page 10, para 3:
Same comment as above.
=20
- section 4.4 and backward compatibility
Given the new tokens you define (FEC-XR), there is no backward
compatibility issues. Section 4.4 explains how to cope with situations
when the remote party only understands RFC 4756.
Should this section be called "SDP Offer/Answer and backward
compatibility considerations"?

- aBNF?
Would it be beneficial to have a new BNF for the SDP attributes you
extend?
e..g
        =20
       group-attribute    =3D "a=3Dgroup:" semantics  ; from =
[RFC3388bis]
                             *(space identification-tag)
        semantics          =3D "LS" / "FID" /=20
                             "FEC" /               ; from RFC 4756 for
backward compatibility
                             "FEC-XR"               ; this RFC


> -----Original Message-----
> From: Jean-Francois Mule
> Sent: Wednesday, October 14, 2009 10:10 AM
> To: mmusic@ietf.org
> Cc: 'draft-ietf-mmusic-rfc4756bis@tools.ietf.org'; Joerg Ott
> Subject: WGLC on draft-ietf-mmusic-rfc4756bis-03
>=20
> This is to start a 2-week working group last call on draft draft-
> ietf-mmusic-rfc4756bis-03, http://tools.ietf.org/html/draft-ietf-
> mmusic-rfc4756bis-03.  The comment period will end on Wednesday
> October 28.
>=20
> Please send your comments to the mmusic list and the authors.
>=20
> Thank you,
> Jean-Francois.
>=20


From abegen@cisco.com  Thu Oct 15 14:12:36 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 929383A68C0 for <mmusic@core3.amsl.com>; Thu, 15 Oct 2009 14:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  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 7DjFiioCBfGu for <mmusic@core3.amsl.com>; Thu, 15 Oct 2009 14:12:35 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 569553A687C for <mmusic@ietf.org>; Thu, 15 Oct 2009 14:12:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=9454; q=dns/txt; s=sjiport06001; t=1255641159; x=1256850759; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Ali=20C.=20Begen=20(abegen)"=20<abegen@cisco.co m>|Subject:=20RE:=20[MMUSIC]=20Comments=20on=20draft-ietf -mmusic-rfc4756bis-03|Date:=20Thu,=2015=20Oct=202009=2014 :11:44=20-0700|Message-ID:=20<04CAD96D4C5A3D48B1919248A8F E0D540A6E7297@xmb-sjc-215.amer.cisco.com>|To:=20"Jean-Fra ncois=20Mule"=20<jf.mule@cablelabs.com>,=0D=0A=20=20=20 =20=20=20=20=20<draft-ietf-mmusic-rfc4756bis@tools.ietf.o rg>|Cc:=20<mmusic@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |In-Reply-To:=20<9AAEDF491EF7CA48AB587781B8F5D7C6024FEC96 @srvxchg3.cablelabs.com>|References:=20<9AAEDF491EF7CA48A B587781B8F5D7C6024FEC96@srvxchg3.cablelabs.com>; bh=867s1nRs2vIDkBMatf3zTVuc2LCgh7W87ZiwqjEvLxU=; b=mNliA/sAwtYrKeA2rLMogRmo/gSRo2r04NnsNU64o4lkduF4FpG5SLEd qAOthzn762nTG5ZHqxjZ9WkkyWctDdDFAwIhmCAFzfWq4G8I0pHi0WOdx ckbJvwtKy8jRBhO7dcqSAvN2hWYGw8c0q0Yubo2AZS2DJ1J3x9HMy78M/ 8=;
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAP8s10qrR7Ht/2dsb2JhbADBO5g2hDAE
X-IronPort-AV: E=Sophos;i="4.44,568,1249257600"; d="scan'208";a="410293180"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 15 Oct 2009 21:12:38 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9FLCbXF017638; Thu, 15 Oct 2009 21:12:38 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 15 Oct 2009 14:12:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Oct 2009 14:11:44 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A6E7297@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC96@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Comments on draft-ietf-mmusic-rfc4756bis-03
Thread-Index: AcpM6M4YlHJPdxh7ScGv3yGY13jt2wABIsPQADudUlA=
References: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC96@srvxchg3.cablelabs.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Jean-Francois Mule" <jf.mule@cablelabs.com>, <draft-ietf-mmusic-rfc4756bis@tools.ietf.org>
X-OriginalArrivalTime: 15 Oct 2009 21:12:37.0475 (UTC) FILETIME=[38CF8B30:01CA4DDC]
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2009 21:12:36 -0000

Hi JF,

Thanks for the quick review. I addressed all of your comments and =
submitted a new version.
http://www.ietf.org/id/draft-ietf-mmusic-rfc4756bis-04.txt

Let me know if you have further comments. The diff should be available =
shortly.

-acbegen

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On =
Behalf Of Jean-Francois
> Mule
> Sent: Wednesday, October 14, 2009 6:31 PM
> To: draft-ietf-mmusic-rfc4756bis@tools.ietf.org
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] Comments on draft-ietf-mmusic-rfc4756bis-03
>=20
> Ali,
>=20
>    The draft is well written and provides clear justifications for the
> updates to RFC 4756.
>=20
>    Below are a few comments for your consideration.
>=20
> Regards,
> Jean-Francois.
>=20
> - Document frontpage:
> Given this draft extends the group and ssrc-group attributes with new
> semantics (a=3Dgroup:FEC-XR, a=3Dssrc-group:FEC-XR), the boiler plate =
should
> indicate that this document does update RFC 3388bis and RFC 5576, I
> think.
>=20
> - page 4, para 4: typo
> s/the grouping semantics defined in this document offers flexibility
> about which source streams can be grouped together prior to FEC
> protection/ the grouping semantics defined in this document offer the
> flexibility to determine how source streams are grouped together prior
> to applying FEC protection
>=20
> - page 5, numbered bullets
> (see next comment)
> a) You summarize a few FEC framework requirements.
> I suppose they are contained in the document, if so put the document
> reference [].
> b) I'm not sure about this comment but I wonder whether these
> requirements should be included with the capital verbs here. I would
> turns those MAY into may, as they are duplicate requirements in the =
FEC
> framework and implementations compliant with this draft would not need
> to meet those as stated (see the comment below).  You only drive the =
one
> SDP grouping semantics requirement you have below them (as a MUST).
>=20
> - page 5, last sentence of section 1
> Change the requirement to be more explicit on what the SDP semantics
> must be able to express (and I would split bullet 3 into two bullets).
> As written, the reader has to translate what the FEC requirements mean
> for the SDP semantics (in reference to "these features").
> Old text:
> ---
> To summarize, the FEC Framework supports the following:
>    1.  A source flow MAY be protected by multiple different FEC =
schemes.
>    2.  An FEC scheme MAY generate multiple repair flows.
>    3.  Source flows MAY be grouped prior to FEC protection.  That is,
>        one or more repair flows MAY protect a group of source flows.
>=20
>    To fully benefit from the flexibility provided by the FEC =
Framework,
>    the grouping semantics for FEC MUST support these features.
> ---
>=20
> New text:
> In summary, based on the FEC Framework [], the SDP grouping semantics
> for FEC MUST support the ability to indicate that:
>    1.  a given source flow is protected by multiple different FEC
> schemes.
>    2.  multiple repair flows are associated with a given source flow
>    3.  multiple source flows are grouped prior to applying FEC
> protection
>    4.  one or more repair flows protect a group of source flows.
> --- or something like that.
>=20
> - page 5, section 3
> The text in section 3 should be written as if it is the new
> to-be-published RFC. You should assume the draft is the RFC that
> obsoletes RFC 4756 and explain what motivated some changes and
> extensions.
> This leads to a few editorial changes, some of which are suggested
> below.
>=20
> s/issues with RFC 4756/changes from RFC 4756 (in the section 3 =
heading)
>=20
> - page 5, section 3.1
> Consider presenting what this document defines first, and finish with
> the changes from previous RFCs.
>=20
> Example:
> --- old text
>    Currently, the 'group' attribute and the FEC grouping semantics
>    defined in [RFC3388] and [RFC4756], respectively, are used to
>    associate source and repair flows together.
>=20
>    The 'group' attribute is used to group multiple repair flows with =
one
>    or more source flows.  However, [RFC3388] prohibits an "m" line
>    identified by its 'mid' attribute from appearing in more than one
>    "a=3Dgroup" line using the same semantics.  This limitation =
prevents us
>    from indicating specific associations between the source and repair
>    flows by using an "a=3Dgroup:FEC" line per FEC Framework instance.  =
For
>    example, for the scenario sketched in Figure 1, [RFC3388] mandates =
us
>    to write
>=20
>         a=3Dgroup:FEC S1 S2 R1 R2
>=20
>    Clearly, this "a=3Dgroup:FEC" line does not say anything specific =
about
>    which repair flows are protecting which source flows.
>=20
>    A new work ([I-D.ietf-mmusic-rfc3388bis]) is currently in progress =
in
>    the MMUSIC WG to remove this limitation in [RFC3388].  However,
>    [RFC4756] also needs to be updated according to the FEC Framework
>    requirements.
>=20
> --- new text
>    The FEC grouping semantics and 'group' attribute
>    defined in this document and [RFC3388bis], respectively, are used =
to
>    associate source and repair flows together.
>=20
>    This document specifies how the SDP 'group' attribute is used to
>    group multiple repair flows with one or more source flows.
>    [I-D.ietf-mmusic-rfc3388bis] updates [RFC3388]
>    to allow an "m" line identified by its 'mid' attribute to appear in
>    more than one "a=3Dgroup" line using the same semantics. This =
change
>    allows us a sender to indicate the specific associations between =
the
>    source and repair flows by using an "a=3Dgroup:FEC" line per FEC
>    Framework instance.
>=20
> // change the example to show the above and how the 3388bis helps
>=20
>    This document updates [RFC4756] to allow the source and repair =
flows
>    to be associated in SDP.
>=20
> --- hope this helps convey what the text should look like expressing =
the
> same things.
>=20
> - section 4.1, bottom of page 6, first 2 paragraphs of page 7
> This is where having some formal MUST requirements for compliant
> implementations would be beneficial.
>=20
> Change:
>    If there are more than one
>    repair flows included in an FEC group, they are considered to be
>    additive.  Repair flows that are in different FEC groups are non-
>    additive.
>=20
> Into something like:
>    Repair flows included in the same FEC Group MUST be additive. And
>    repair flows that are not additive MUST be indicated in separate
>    SDP FEC group lines.
>=20
> - page 8, section 4.2
> s/MUST/must in "we MUST write"
> (you have now a formal requirement in section 4.1)
>=20
> - page 8, section 4.3
> Change:
> < Instead, the 'ssrc-group' attribute MUST be used.
> With
> > This document extends [RFC 5576] in two ways.  First we define how =
FEC
> is applied to source and repair flows for SSRC multiplexed streams =
using
> the 'ssrc-group' attribute.  We then specify how additivity of the
> repair flows are expressed for SSRC multiplexed streams.
>=20
> - page 8, last paragraph of section 4.3
> Same comment as above for the "a=3Dgroup" lines: it would be good to =
have
> 2 MUST requirements to indicate that additive repairs flows MUST be on
> the same a=3Dssrc-group lines while non-additive ones MUST be on =
separate
> lines.
>=20
> - page 9, section 4.4., last paragraph at the bottom of page 9
> I would not point to RFC4756 but instead point to this draft (from my
> perspective, it does not make much sense to ask implementers to first
> check that there is no ambiguity with the previous RFC.
>=20
> - page 10, para 3:
> Same comment as above.
>=20
> - section 4.4 and backward compatibility
> Given the new tokens you define (FEC-XR), there is no backward
> compatibility issues. Section 4.4 explains how to cope with situations
> when the remote party only understands RFC 4756.
> Should this section be called "SDP Offer/Answer and backward
> compatibility considerations"?
>=20
> - aBNF?
> Would it be beneficial to have a new BNF for the SDP attributes you
> extend?
> e..g
>=20
>        group-attribute    =3D "a=3Dgroup:" semantics  ; from =
[RFC3388bis]
>                              *(space identification-tag)
>         semantics          =3D "LS" / "FID" /
>                              "FEC" /               ; from RFC 4756 for
> backward compatibility
>                              "FEC-XR"               ; this RFC
>=20
>=20
> > -----Original Message-----
> > From: Jean-Francois Mule
> > Sent: Wednesday, October 14, 2009 10:10 AM
> > To: mmusic@ietf.org
> > Cc: 'draft-ietf-mmusic-rfc4756bis@tools.ietf.org'; Joerg Ott
> > Subject: WGLC on draft-ietf-mmusic-rfc4756bis-03
> >
> > This is to start a 2-week working group last call on draft draft-
> > ietf-mmusic-rfc4756bis-03, http://tools.ietf.org/html/draft-ietf-
> > mmusic-rfc4756bis-03.  The comment period will end on Wednesday
> > October 28.
> >
> > Please send your comments to the mmusic list and the authors.
> >
> > Thank you,
> > Jean-Francois.
> >
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

From root@core3.amsl.com  Thu Oct 15 14:15:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 0A75128C16C; Thu, 15 Oct 2009 14: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: <20091015211502.0A75128C16C@core3.amsl.com>
Date: Thu, 15 Oct 2009 14:15:02 -0700 (PDT)
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-rfc4756bis-04.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2009 21: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 Multiparty Multimedia Session Control Working Group of the IETF.


	Title           : Forward Error Correction Grouping Semantics in Session Description Protocol
	Author(s)       : A. Begen
	Filename        : draft-ietf-mmusic-rfc4756bis-04.txt
	Pages           : 13
	Date            : 2009-10-15

The Session Description Protocol (SDP) supports grouping media lines.
SDP also has semantics defined for grouping the associated source and
Forward Error Correction (FEC)-based repair flows.  However, the
semantics that was defined in RFC 4756 generally fail to provide the
specific grouping relationships between the source and repair flows
when there are more than one source and/or repair flows in the same
group.  Furthermore, the existing semantics does not support
describing additive repair flows.  This document addresses these
issues by introducing new FEC grouping semantics.  SSRC-level
grouping semantics is also introduced in this document for Real-time
Transport Protocol (RTP) streams using SSRC multiplexing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc4756bis-04.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-mmusic-rfc4756bis-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From abegen@cisco.com  Fri Oct 16 16:44:41 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B3EC3A6947; Fri, 16 Oct 2009 16:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.112
X-Spam-Level: 
X-Spam-Status: No, score=-6.112 tagged_above=-999 required=5 tests=[AWL=-0.413, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, MIME_8BIT_HEADER=0.3, 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 9K5LmgUq8YI5; Fri, 16 Oct 2009 16:44:40 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 085CF3A6808; Fri, 16 Oct 2009 16:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=4722; q=dns/txt; s=sjiport05001; t=1255736684; x=1256946284; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Ali=20C.=20Begen=20(abegen)"=20<abegen@cisco.co m>|Subject:=20RE:=20[Fecframe]=20FW:=20[MMUSIC]=20WGLC=20 on=20draft-ietf-mmusic-rfc4756bis-03|Date:=20Fri,=2016=20 Oct=202009=2016:44:42=20-0700|Message-ID:=20<04CAD96D4C5A 3D48B1919248A8FE0D540A6E765F@xmb-sjc-215.amer.cisco.com> |To:=20=3D?UTF-8?B?VWxhxZ8gQy4gS296YXQ=3D?=3D=20<ulas.koz at@gmail.com>|Cc:=20<fecframe@ietf.org>,=20<mmusic@ietf.o rg>|MIME-Version:=201.0|Content-Transfer-Encoding:=20base 64|In-Reply-To:=20<241bc2150910161609u5fb572asfbe4e4ad943 57fad@mail.gmail.com>|References:=20<04CAD96D4C5A3D48B191 9248A8FE0D540A636394@xmb-sjc-215.amer.cisco.com>=20<04CAD 96D4C5A3D48B1919248A8FE0D540A6E7326@xmb-sjc-215.amer.cisc o.com>=20<241bc2150910161609u5fb572asfbe4e4ad94357fad@mai l.gmail.com>; bh=xqFveWIoRacO9fTbqzjrqmk6VMkpHzn+A+tbaoE8eZM=; b=iKVGkCticE+GtWVf+OIG7AeuQ25/DBkc2Xvm5qUPX5B9syXJId164QPL AmKgH7/Hhd4ZVFPzvsaZvA2jG1dszVgQirO4uEm7LoaExcUqRYkjk5YQk dUCGd8pTzJiP+6kVeWeK/1cOXZ7Am/gRUx2qksXd0pNFYo6AS5AqoFcBV g=;
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAJei2EqrRN+J/2dsb2JhbACZZKZumAyEMQQ
X-IronPort-AV: E=Sophos;i="4.44,576,1249257600"; d="scan'208";a="99257945"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-5.cisco.com with ESMTP; 16 Oct 2009 23:44:44 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id n9GNiiB5019378; Fri, 16 Oct 2009 23:44:44 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 16 Oct 2009 16:44:44 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Fri, 16 Oct 2009 16:44:42 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A6E765F@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <241bc2150910161609u5fb572asfbe4e4ad94357fad@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fecframe] FW: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
Thread-Index: AcpOta5M4YqNpOznSkijjk6DShIr9wABLNTg
References: <04CAD96D4C5A3D48B1919248A8FE0D540A636394@xmb-sjc-215.amer.cisco.com> <04CAD96D4C5A3D48B1919248A8FE0D540A6E7326@xmb-sjc-215.amer.cisco.com> <241bc2150910161609u5fb572asfbe4e4ad94357fad@mail.gmail.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: =?UTF-8?B?VWxhxZ8gQy4gS296YXQ=?= <ulas.kozat@gmail.com>
X-OriginalArrivalTime: 16 Oct 2009 23:44:44.0637 (UTC) FILETIME=[A36FB0D0:01CA4EBA]
Cc: mmusic@ietf.org, fecframe@ietf.org
Subject: Re: [MMUSIC] [Fecframe] FW: WGLC on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2009 23:44:41 -0000

VGhhbmtzIGZvciB0aGUgcmV2aWV3LiBJJ2xsIGFkZHJlc3MgdGhlc2UgZWRpdG9yaWFsIGZpeGVz
IGluIHRoZSBuZXh0IHJldmlzaW9uIHdpdGggYWxsIG90aGVyIGNvbW1lbnRzIHRoYXQgbWF5IGJl
IHJlY2VpdmVkLiBDQydpbmcgbW11c2ljLg0KDQotYWNiZWdlbg0KDQo+IC0tLS0tT3JpZ2luYWwg
TWVzc2FnZS0tLS0tDQo+IEZyb206IFVsYcWfIEMuIEtvemF0IFttYWlsdG86dWxhcy5rb3phdEBn
bWFpbC5jb21dDQo+IFNlbnQ6IEZyaWRheSwgT2N0b2JlciAxNiwgMjAwOSA3OjA5IFBNDQo+IFRv
OiBBbGkgQy4gQmVnZW4gKGFiZWdlbikNCj4gQ2M6IGZlY2ZyYW1lQGlldGYub3JnDQo+IFN1Ympl
Y3Q6IFJlOiBbRmVjZnJhbWVdIEZXOiBbTU1VU0lDXSBXR0xDIG9uIGRyYWZ0LWlldGYtbW11c2lj
LXJmYzQ3NTZiaXMtMDMNCj4gDQo+IEFsaSwNCj4gDQo+IEkgcmVhZCB0aGUgZHJhZnQuIEFzc3Vt
aW5nIHRoZSB1c2FnZSBvZiBvdGhlciBTRFAgbGluZXMgYXJlIGNvcnJlY3QsIEkNCj4gdGhpbmsg
dGhlIGRyYWZ0IGlzIGNsZWFyIGVub3VnaC4gSSBoYXZlIHR3byBtaW5vciBjb21tZW50cyB0aGF0
IG1pZ2h0DQo+IGFkZCBmdXJ0aGVyIGNsYXJpdHkgdG8gdGhlIGRvY3VtZW50Og0KPiANCj4gMS4g
SW4gU2VjdGlvbiAxLCB0aGUgc2VudGVuY2UgIkhvd2V2ZXIsIG5vdCBhbGwgRkVDIHNjaGVtZXMg
c3VwcG9ydA0KPiB0aGUgZnVsbCByYW5nZSBvZiBwb3NzaWJsZSBzY2VuYXJpb3MgKGUuZy4sIHdo
ZW4gdGhlIHNvdXJjZSBzdHJlYW1zDQo+IGNhcnJ5IGRpZmZlcmVudCB0b3AtbGV2ZWwgbWVkaWEg
dHlwZXMgc3VjaCBhcyBhdWRpbyBhbmQgdmlkZW8pLiIgaXMNCj4gdmFndWUuIE1heWJlIHJlbW92
aW5nIHRoaXMgc2VudGVuY2UgYW5kIGNvbWJpbmluZyB3aXRoIHRoZSBmb2xsb3dpbmcNCj4gcGFy
YWdyYXBoIGNhbiBtYWtlIGEgYmV0dGVyIHRyYW5zaXRpb24uDQo+IA0KPiAyLiBJbiBTZWN0aW9u
IDQuNC4sIHlvdSByZWZlciB0byBTZWN0aW9uIDMuMSBpbiB0d28gcGxhY2VzIHNheWluZyB0aGF0
DQo+IGxpbWl0YXRpb25zIGluIHRoYXQgc2VjdGlvbiBzaG91bGQgYmUga2VwdCBpbiBtaW5kLiBX
aGVuIEkgbG9vayBhdA0KPiBTZWN0aW9uIDMuMSwgaXQgbWFpbmx5IGRlc2NyaWJlcyB0aGUgY2hh
bmdlcyBmcm9tIG90aGVyIFJGQ3MgcmF0aGVyDQo+IHRoYW4gbGlzdGluZyBzcGVjaWZpYyBsaW1p
dGF0aW9ucy4NCj4gDQo+IFVsYXMNCj4gDQo+IE9uIFRodSwgT2N0IDE1LCAyMDA5IGF0IDM6NTAg
UE0sIEFsaSBDLiBCZWdlbiAoYWJlZ2VuKSA8YWJlZ2VuQGNpc2NvLmNvbT4gd3JvdGU6DQo+ID4g
SGVyZSBpcyBhIHF1aWNrIHVwZGF0ZSBvbiB0aGUgZHJhZnQgYmFzZWQgb24gc29tZSBjb21tZW50
cyBmcm9tIE1NVVNJQy4NCj4gPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRm
LW1tdXNpYy1yZmM0NzU2YmlzLTA0DQo+ID4NCj4gPiBQbGVhc2UgcmV2aWV3IHRoaXMgb25lLCBp
ZiB5b3UgYXJlIHBsYW5uaW5nIHRvIGRvIGEgcmV2aWV3Lg0KPiA+DQo+ID4gLWFjYmVnZW4NCj4g
Pg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiBmZWNmcmFtZS1i
b3VuY2VzQGlldGYub3JnIFttYWlsdG86ZmVjZnJhbWUtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVo
YWxmIE9mIEFsaSBDLg0KPiA+PiBCZWdlbiAoYWJlZ2VuKQ0KPiA+PiBTZW50OiBXZWRuZXNkYXks
IE9jdG9iZXIgMTQsIDIwMDkgMTI6MTkgUE0NCj4gPj4gVG86IGZlY2ZyYW1lQGlldGYub3JnDQo+
ID4+IFN1YmplY3Q6IFtGZWNmcmFtZV0gRlc6IFtNTVVTSUNdIFdHTEMgb24gZHJhZnQtaWV0Zi1t
bXVzaWMtcmZjNDc1NmJpcy0wMw0KPiA+Pg0KPiA+PiBUaGlzIGlzIHRoZSBXR0xDIGZvciB0aGUg
NDc1NmJpcyBkcmFmdC4NCj4gPj4NCj4gPj4gUmVjYWxsIHRoYXQgdGhpcyBpcyBhbiBlc3NlbnRp
YWwgdXBkYXRlIGZvciB0aGUgZnJhbWV3b3JrIGFuZCBuZWVkcyB0byBiZSBhcHByb3ZlZA0KPiBi
ZWZvcmUNCj4gPj4gd2UgY2FuIGZpbmFsaXplIHRoZSBTRFAgZHJhZnQuIFNvLCBwbGVhc2UgcmV2
aWV3IGl0IGFuZCBzZW5kIHlvdXIgeWVhaC9uYWggdG8NCj4gPj4gbW11c2ljQGlldGcub3JnLg0K
PiA+Pg0KPiA+PiBJdCBpcyBhIHNob3J0IHNwZWMsIHdvbid0IHRha2UgbXVjaCB0aW1lLg0KPiA+
PiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW1tdXNpYy1yZmM0NzU2Ymlz
LTAzDQo+ID4+DQo+ID4+IFRoYW5rcywgYWNiZWdlbi4NCj4gPj4NCj4gPj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogbW11c2ljLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0
bzptbXVzaWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEplYW4tDQo+IEZyYW5jb2lz
DQo+ID4+IE11bGUNCj4gPj4gU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDE0LCAyMDA5IDEyOjEw
IFBNDQo+ID4+IFRvOiBtbXVzaWNAaWV0Zi5vcmcNCj4gPj4gQ2M6IEpvZXJnIE90dDsgZHJhZnQt
aWV0Zi1tbXVzaWMtcmZjNDc1NmJpc0B0b29scy5pZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBbTU1V
U0lDXSBXR0xDIG9uIGRyYWZ0LWlldGYtbW11c2ljLXJmYzQ3NTZiaXMtMDMNCj4gPj4NCj4gPj4g
VGhpcyBpcyB0byBzdGFydCBhIDItd2VlayB3b3JraW5nIGdyb3VwIGxhc3QgY2FsbCBvbiBkcmFm
dA0KPiA+PiBkcmFmdC1pZXRmLW1tdXNpYy1yZmM0NzU2YmlzLTAzLA0KPiA+PiBodHRwOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLW1tdXNpYy1yZmM0NzU2YmlzLTAzLiDCoFRoZSBj
b21tZW50DQo+ID4+IHBlcmlvZCB3aWxsIGVuZCBvbiBXZWRuZXNkYXkgT2N0b2JlciAyOC4NCj4g
Pj4NCj4gPj4gUGxlYXNlIHNlbmQgeW91ciBjb21tZW50cyB0byB0aGUgbW11c2ljIGxpc3QgYW5k
IHRoZSBhdXRob3JzLg0KPiA+Pg0KPiA+PiBUaGFuayB5b3UsDQo+ID4+IEplYW4tRnJhbmNvaXMu
DQo+ID4+DQo+ID4+DQo+ID4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fDQo+ID4+IG1tdXNpYyBtYWlsaW5nIGxpc3QNCj4gPj4gbW11c2ljQGlldGYub3Jn
DQo+ID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbW11c2ljDQo+ID4+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+IEZl
Y2ZyYW1lIG1haWxpbmcgbGlzdA0KPiA+PiBGZWNmcmFtZUBpZXRmLm9yZw0KPiA+PiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZlY2ZyYW1lDQo+ID4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBGZWNmcmFtZSBtYWlsaW5n
IGxpc3QNCj4gPiBGZWNmcmFtZUBpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vZmVjZnJhbWUNCj4gPg0K

From root@core3.amsl.com  Sun Oct 18 01:15:02 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id F377F3A6841; Sun, 18 Oct 2009 01: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: <20091018081501.F377F3A6841@core3.amsl.com>
Date: Sun, 18 Oct 2009 01:15:01 -0700 (PDT)
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-image-attributes-03.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2009 08: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 Multiparty Multimedia Session Control Working Group of the IETF.


	Title           : Negotiation of Generic Image Attributes in SDP
	Author(s)       : I. Johansson, K. Jung
	Filename        : draft-ietf-mmusic-image-attributes-03.txt
	Pages           : 21
	Date            : 2009-10-18

This document proposes a new generic session setup attribute to make
it possible to negotiate different image attributes such as image
size.  A possible use case is to make it possible for a low-end hand-
held terminal to display video without the need to rescale the image,
something that may consume large amounts of memory and processing
power.  The draft also helps to maintain an optimal bitrate for video
as only the image size that is desired by the receiver is
transmitted.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-image-attributes-03.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-mmusic-image-attributes-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From abegen@cisco.com  Sun Oct 18 12:30:46 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5042F3A6864 for <mmusic@core3.amsl.com>; Sun, 18 Oct 2009 12:30:46 -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 x5+I75D6K1IJ for <mmusic@core3.amsl.com>; Sun, 18 Oct 2009 12:30:45 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 956CF3A67D8 for <mmusic@ietf.org>; Sun, 18 Oct 2009 12:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=842; q=dns/txt; s=sjiport06001; t=1255894252; x=1257103852; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Ali=20C.=20Begen=20(abegen)"=20<abegen@cisco.co m>|Subject:=20ABNF=20syntax=20in=203388bis|Date:=20Sun, =2018=20Oct=202009=2012:30:25=20-0700|Message-ID:=20<04CA D96D4C5A3D48B1919248A8FE0D540A6E76F6@xmb-sjc-215.amer.cis co.com>|To:=20<mmusic@ietf.org>|Cc:=20<Gonzalo.Camarillo@ ericsson.com>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable; bh=KFKoiCzHOtu5kzOZ4wi3c2rg8RjwFvx6nI0V3juy+N4=; b=S+GelKwi4FLYUrB3WbXCYnTs+r7esrBuXBEfeJOtZ0NONg1kew4miavF lE0MPuymSn11bgVpMlUJlV2rp1AGyGmaXcE2C8p42r9hxat+P7mi87gUR 9APvGLHCjoUkO+xXkJcNtDJ46qMzQlnTh8KD2DJQUQ/PZHf+oSAVFliTX 8=;
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAA8K20qrRN+K/2dsb2JhbADBWZY5hDEE
X-IronPort-AV: E=Sophos;i="4.44,581,1249257600"; d="scan'208";a="412117720"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-6.cisco.com with ESMTP; 18 Oct 2009 19:30:51 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id n9IJUqhM011079; Sun, 18 Oct 2009 19:30:52 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 18 Oct 2009 12:30:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 18 Oct 2009 12:30:25 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A6E76F6@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ABNF syntax in 3388bis
Thread-Index: AcpQKXDV7VotPl9SQC2favlobH5jMQ==
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 18 Oct 2009 19:30:51.0844 (UTC) FILETIME=[80CF7040:01CA5029]
Cc: Gonzalo.Camarillo@ericsson.com
Subject: [MMUSIC] ABNF syntax in 3388bis
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Oct 2009 19:30:46 -0000

I have a question about =
http://www.ietf.org/id/draft-ietf-mmusic-rfc3388bis-03.txt

Section 5 of -03 version says:

           group-attribute     =3D "a=3Dgroup:" semantics
                                 *(space identification-tag)
           semantics           =3D "LS" / "FID" / semantics-extension
           semantics-extension =3D token

I don't know every detail of the ABNF syntax, but here the =
identification tags seem to be totally optional, whereas we at least =
need two of them to be able to use the 'group' attribute, right?

So, should not we rather have:

           group-attribute     =3D "a=3Dgroup:" semantics
                                 2*(space identification-tag)
           semantics           =3D "LS" / "FID" / semantics-extension
           semantics-extension =3D token

-acbegen

From ingemar.s.johansson@ericsson.com  Sun Oct 18 22:25:10 2009
Return-Path: <ingemar.s.johansson@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 035353A672E for <mmusic@core3.amsl.com>; Sun, 18 Oct 2009 22:25:10 -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 94IsWJAVRino for <mmusic@core3.amsl.com>; Sun, 18 Oct 2009 22:25:09 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id B445D3A67F8 for <mmusic@ietf.org>; Sun, 18 Oct 2009 22:25:08 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b3fae00000105f-1c-4adbf839a44c
Received: from esealmw126.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id C3.BB.04191.938FBDA4; Mon, 19 Oct 2009 07:25:13 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 19 Oct 2009 07:25:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Oct 2009 07:25:12 +0200
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C020A350A@esealmw109.eemea.ericsson.se>
In-Reply-To: <mailman.45.1255892408.7808.mmusic@ietf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: draft-ietf-mmusic-image-attributes-03.txt
Thread-Index: AcpQJU3CMJ75nOGPSOKj08lViHuMZQAVvQtA
References: <mailman.45.1255892408.7808.mmusic@ietf.org>
From: "Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>
To: <mmusic@ietf.org>
X-OriginalArrivalTime: 19 Oct 2009 05:25:13.0468 (UTC) FILETIME=[88CB6BC0:01CA507C]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [MMUSIC] draft-ietf-mmusic-image-attributes-03.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 05:25:10 -0000

Hi

I uploaded a new version of the image attribute draft. The update is not
complete but I wanted to upload at least a partial update before the
expriration date.=20
Will submit the complete update as soon as possible.

/Ingemar



> -----Original Message-----
> From: mmusic-bounces@ietf.org=20
> [mailto:mmusic-bounces@ietf.org] On Behalf Of mmusic-request@ietf.org
> Sent: den 18 oktober 2009 21:00
> To: mmusic@ietf.org
> Subject: mmusic Digest, Vol 66, Issue 9
>=20
> If you have received this digest without all the individual=20
> message attachments you will need to update your digest=20
> options in your list subscription.  To do so, go to=20
>=20
> https://www.ietf.org/mailman/listinfo/mmusic
>=20
> Click the 'Unsubscribe or edit options' button, log in, and=20
> set "Get MIME or Plain Text Digests?" to MIME.  You can set=20
> this option globally for all the list digests you receive at=20
> this point.
>=20
>=20
>=20
> Send mmusic mailing list submissions to
> 	mmusic@ietf.org
>=20
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.ietf.org/mailman/listinfo/mmusic
> or, via email, send a message with subject or body 'help' to
> 	mmusic-request@ietf.org
>=20
> You can reach the person managing the list at
> 	mmusic-owner@ietf.org
>=20
> When replying, please edit your Subject line so it is more=20
> specific than "Re: Contents of mmusic digest..."
>=20
>=20
> Today's Topics:
>=20
>    1. I-D Action:draft-ietf-mmusic-image-attributes-03.txt
>       (Internet-Drafts@ietf.org)
>=20
>=20
> ----------------------------------------------------------------------
>=20
> Message: 1
> Date: Sun, 18 Oct 2009 01:15:01 -0700 (PDT)
> From: Internet-Drafts@ietf.org
> Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-image-attributes-03.txt
> To: i-d-announce@ietf.org
> Cc: mmusic@ietf.org
> Message-ID: <20091018081501.F377F3A6841@core3.amsl.com>
> Content-Type: text/plain; charset=3D"us-ascii"
>=20
>=20
>=20
> ------------------------------
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>=20
>=20
> End of mmusic Digest, Vol 66, Issue 9
> *************************************
>=20

From schierl@hhi.fhg.de  Mon Oct 19 04:49:36 2009
Return-Path: <schierl@hhi.fhg.de>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B7B73A6958 for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 04:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.343
X-Spam-Level: 
X-Spam-Status: No, score=-3.343 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, 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 HkRpHjf4DB1q for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 04:49:35 -0700 (PDT)
Received: from mail.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id 32D733A67D7 for <mmusic@ietf.org>; Mon, 19 Oct 2009 04:49:35 -0700 (PDT)
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534) id 316F71D89039; Mon, 19 Oct 2009 13:49:40 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 13ACD15004E; Mon, 19 Oct 2009 13:49:39 +0200 (CEST)
Received: from [130.149.228.125] (unknown [130.149.228.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Thomas Schierl", Issuer "Fraunhofer-Gesellschaft Root-CA v2" (not verified)) by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 5AF1E1D88FCD; Mon, 19 Oct 2009 13:49:39 +0200 (CEST)
Message-ID: <4ADC5251.2010304@hhi.fhg.de>
Date: Mon, 19 Oct 2009 13:49:37 +0200
From: Thomas Schierl <schierl@hhi.fhg.de>
Organization: Fraunhofer HHI
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Joerg Ott <jo@netlab.tkk.fi>
References: <4AB65606.4040905@netlab.tkk.fi>
In-Reply-To: <4AB65606.4040905@netlab.tkk.fi>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-alterMIME: Yes
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Jean-Francois Mule <jf.mule@cablelabs.com>, mmusic@ietf.org, Martin Stiemerling <Stiemerling@nw.neclab.eu>
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 11:49:36 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Dear authors,<br>
<br>
I have one question, which came into my mind reading Appendix D.<br>
<br>
In section D.1.2, I read "
<pre class="newpage">Usage of grouping of media lines [<a
 href="http://tools.ietf.org/html/rfc3388"
 title="&quot;Grouping of Media Lines in the Session Description Protocol (SDP)&quot;">RFC3388</a>] to determine which media
   lines should or should not be included in a RTSP session is
   unspecified.
</pre>
"<br>
<br>
Earlier in the Appendix, I read "
<pre class="newpage"> However
   ,the SDP extension "Grouping of Media Lines in the Session
   Description Protocol (SDP)" [<a
 href="http://tools.ietf.org/html/rfc3388"
 title="&quot;Grouping of Media Lines in the Session Description Protocol (SDP)&quot;">RFC3388</a>] may provide such functionality
   depending on need.  Also future grouping semantics may in the future
   be developed.
</pre>
"<br>
<br>
<br>
What does it mean?&nbsp; Is SDP grouping allowed to be used with this spec?
If not, then there might
be an issue with respect of using the RFC 5583 decoding dependency
signaling required for multi flow
transmission of layered codecs such as SVC.<br>
<br>
<br>
Thanks,<br>
Thomas<br>
<br>
<pre class="moz-signature" cols="72">-- 
Thomas Schierl
--------------
Fraunhofer HHI

</pre>
<br>
<br>
Joerg Ott wrote:
<blockquote cite="mid:4AB65606.4040905@netlab.tkk.fi" type="cite">Folks,
  <br>
  <br>
as agreed in Stockholm, we are issuing working group last
  <br>
call on the revised RTSP spec, draft-ietf-mmusic-rfc2326bis-22
  <br>
heading for Proposed Standard.
  <br>
(<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22">http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22</a>)
  <br>
  <br>
The WGLC will expire in four weeks, on 19 Oct 2009.
  <br>
  <br>
We know that this is a long spec, the more important is it
  <br>
to receive thorough review by the community.&nbsp; While we have
  <br>
three volunteer reviewers (thanks again!), we urge everyone
  <br>
who cares to provide detailed feedback.
  <br>
  <br>
Please review the document and post your comments to the
  <br>
MMUSIC list and/or the authors.
  <br>
  <br>
Thanks,
  <br>
Joerg
  <br>
  <br>
MMUSIC co-chair
  <br>
  <br>
_______________________________________________
  <br>
mmusic mailing list
  <br>
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
  <br>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
  <br>
  <br>
  <br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">

</pre>
<BR>
<BR>
</body>
</html>


From schierl@hhi.fhg.de  Mon Oct 19 05:16:28 2009
Return-Path: <schierl@hhi.fhg.de>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 29C753A68BB for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 05:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.637
X-Spam-Level: 
X-Spam-Status: No, score=-4.637 tagged_above=-999 required=5 tests=[AWL=-0.436, BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, J_CHICKENPOX_21=0.6, 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 2KIDIVdgDjaN for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 05:16:26 -0700 (PDT)
Received: from mail.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id 3FE5B3A69CD for <mmusic@ietf.org>; Mon, 19 Oct 2009 05:16:26 -0700 (PDT)
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534) id 2FF1F1D89026; Mon, 19 Oct 2009 14:16:30 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 751F4150041; Mon, 19 Oct 2009 14:16:30 +0200 (CEST)
Received: from [130.149.228.125] (unknown [130.149.228.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Thomas Schierl", Issuer "Fraunhofer-Gesellschaft Root-CA v2" (not verified)) by mail.hhi.fraunhofer.de (Postfix) with ESMTP id 962E21D88F51; Mon, 19 Oct 2009 14:16:29 +0200 (CEST)
Message-ID: <4ADC589D.8000306@hhi.fhg.de>
Date: Mon, 19 Oct 2009 14:16:29 +0200
From: Thomas Schierl <schierl@hhi.fhg.de>
Organization: Fraunhofer HHI
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Jean-Francois Mule <jf.mule@cablelabs.com>
References: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cablelabs.com>
In-Reply-To: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cablelabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-alterMIME: Yes
Cc: mmusic@ietf.org, Joerg Ott <jo@netlab.tkk.fi>, draft-ietf-mmusic-rfc4756bis@tools.ietf.org
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 12:16:28 -0000

Dear Ali,

I am not sure if the SDP signaling is covering all cases. What is about 
the case of having a SVC or any other layered media, where one session 
SB contains the base layer and another session SE contains the 
enhancement layer. Let us assume session SB is protected by  repair flow 
RB. Furthermore, session SB and SE are jointly protected by repair flow 
RB+E. Additionally, RB+E is additive to RB. The only way expressing this 
with the current draft seems to be:

        a=group:FEC-XR SB RB
        a=group:FEC-XR SB SE RB RB+E

I would expect that the grouping can signal that RB can be used 
separately for SB, but RB and RB+E can be also jointly used for the 
combination of SB and SE. Would the above grouping be in line with the 
current draft? I wonder if this may be somehow contrary to definition in 
section 4.1:

"Repair flows that are in different FEC groups are non-
   additive.".

If the signaling in the example above is in line with the intention of 
the draft, I would make the following modifications:

- You may add an "...exclusively in different FEC groups..." to the 
sentence of section 4.1 above.
- Further, I would add the following text to section 4.1 to make it clearer:

"In order to express multiple relations between source and repair flows, 
source and repair flows may appear in more than one FEC group."

I think the same should be valid for the FEC-SSRC grouping.

Best regards,
Thomas


-- 
Thomas Schierl
--------------
Fraunhofer HHI



Jean-Francois Mule wrote:
> This is to start a 2-week working group last call on draft
> draft-ietf-mmusic-rfc4756bis-03,
> http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-03.  The comment
> period will end on Wednesday October 28.
>
> Please send your comments to the mmusic list and the authors.
>
> Thank you,
> Jean-Francois.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>   





From abegen@cisco.com  Mon Oct 19 07:20:31 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FA983A680D for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 07:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.924
X-Spam-Level: 
X-Spam-Status: No, score=-5.924 tagged_above=-999 required=5 tests=[AWL=-0.525, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_22=0.6, 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 j27lFrEaGfTc for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 07:20:30 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 75D1F3A6778 for <mmusic@ietf.org>; Mon, 19 Oct 2009 07:20:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=3858; q=dns/txt; s=sjiport01001; t=1255962037; x=1257171637; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Ali=20C.=20Begen=20(abegen)"=20<abegen@cisco.co m>|Subject:=20RE:=20[MMUSIC]=20WGLC=20on=20draft-ietf-mmu sic-rfc4756bis-03|Date:=20Mon,=2019=20Oct=202009=2007:20: 31=20-0700|Message-ID:=20<04CAD96D4C5A3D48B1919248A8FE0D5 40A6E779B@xmb-sjc-215.amer.cisco.com>|To:=20"Thomas=20Sch ierl"=20<schierl@hhi.fhg.de>,=0D=0A=20=20=20=20=20=20=20 =20"Jean-Francois=20Mule"=20<jf.mule@cablelabs.com>|Cc: =20<mmusic@ietf.org>,=20"Joerg=20Ott"=20<jo@netlab.tkk.fi >,=0D=0A=20=20=20=20=20=20=20=20<draft-ietf-mmusic-rfc475 6bis@tools.ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |In-Reply-To:=20<4ADC589D.8000306@hhi.fhg.de>|References: =20<9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cab lelabs.com>=20<4ADC589D.8000306@hhi.fhg.de>; bh=IT1M8SZnZpmH3VSeQGSUEeG0sUutGbJ8SuVDpQX9zrM=; b=nNjM51B+7lXHczO9kxEVaOqrWAzyw6NxNHYNI0PZiUGCkV4EZ1d5d6Bp IA6xXlNjewh1eZXybxTVjZECwNyVf2kwQR5awV4OU7Hu+fGJXDT1f3KrZ yivbqcZglZfahjcelQ3trv5iO+bAH+PujW2LXivBz73USR/i+zZbfPPjP 4=;
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAKsS3EqrRN+J/2dsb2JhbADEQ5ZohDEE
X-IronPort-AV: E=Sophos;i="4.44,585,1249257600"; d="scan'208";a="257991376"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-1.cisco.com with ESMTP; 19 Oct 2009 14:20:37 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id n9JEKb7m025929; Mon, 19 Oct 2009 14:20:37 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 19 Oct 2009 07:20:37 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Oct 2009 07:20:31 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <4ADC589D.8000306@hhi.fhg.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
Thread-Index: AcpQtgaWzENnEJrKS6GpZBJZrNtOgwADPPjQ
References: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cablelabs.com> <4ADC589D.8000306@hhi.fhg.de>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Thomas Schierl" <schierl@hhi.fhg.de>, "Jean-Francois Mule" <jf.mule@cablelabs.com>
X-OriginalArrivalTime: 19 Oct 2009 14:20:37.0440 (UTC) FILETIME=[542C8C00:01CA50C7]
Cc: mmusic@ietf.org, Joerg Ott <jo@netlab.tkk.fi>, draft-ietf-mmusic-rfc4756bis@tools.ietf.org
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 14:20:31 -0000

Hi Thomas,

> -----Original Message-----
> From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
> Sent: Monday, October 19, 2009 8:16 AM
> To: Jean-Francois Mule
> Cc: mmusic@ietf.org; Joerg Ott; =
draft-ietf-mmusic-rfc4756bis@tools.ietf.org
> Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
>=20
> Dear Ali,
>=20
> I am not sure if the SDP signaling is covering all cases. What is =
about
> the case of having a SVC or any other layered media, where one session
> SB contains the base layer and another session SE contains the
> enhancement layer. Let us assume session SB is protected by  repair =
flow
> RB. Furthermore, session SB and SE are jointly protected by repair =
flow
> RB+E. Additionally, RB+E is additive to RB. The only way expressing =
this
> with the current draft seems to be:
>=20
>         a=3Dgroup:FEC-XR SB RB
>         a=3Dgroup:FEC-XR SB SE RB RB+E

If RB+E and RB were not additive, we would have:

a=3Dgroup:FEC-XR SB RB
a=3Dgroup:FEC-XR SB SE RB+E

But, now you are saying that they are additive, I believe we should =
have:
=20
a=3Dgroup:FEC-XR SB RB RB+E
a=3Dgroup:FEC-XR SB SE RB+E

Because RB+E is additive to RB, that means it is protecting SB as well. =
Here I assumed RB exclusively protected SB. If this assumption does not =
hold, see below.

> I would expect that the grouping can signal that RB can be used
> separately for SB, but RB and RB+E can be also jointly used for the
> combination of SB and SE. Would the above grouping be in line with the
> current draft? I wonder if this may be somehow contrary to definition =
in

Now, this sounds different than the first scenario you described above, =
IMO. And, this leads to the original SDP you gave:

a=3Dgroup:FEC-XR SB RB
a=3Dgroup:FEC-XR SB SE RB RB+E

> section 4.1:
>=20
> "Repair flows that are in different FEC groups are non-
>    additive.".

Why would it be contrary? Here, RB and RB+E are in the same line and =
that is enough to state their additivity. But, in this scenario, their =
joint decoding helps the group of SB+SE. The above SDP says if the =
source consists of SB only, then just use RB only since RB+E would not =
help with decoding.
=20
> If the signaling in the example above is in line with the intention of
> the draft, I would make the following modifications:
>=20
> - You may add an "...exclusively in different FEC groups..." to the
> sentence of section 4.1 above.

We can add this to make it stronger. But, I believe if two repair flows =
are additive in a group, it does not mean that they will also be =
additive in any other group where one of the source flows they protect =
is listed.

Agree?

> - Further, I would add the following text to section 4.1 to make it =
clearer:
>=20
> "In order to express multiple relations between source and repair =
flows,
> source and repair flows may appear in more than one FEC group."

I believe this was clear, but it is a good suggestion.
=20
> I think the same should be valid for the FEC-SSRC grouping.

Sure.

Thanks for the review. Let me know if you agree with the above.

Cheers, acbegen.

=20
> Best regards,
> Thomas
>=20
>=20
> --
> Thomas Schierl
> --------------
> Fraunhofer HHI
>=20
>=20
>=20
> Jean-Francois Mule wrote:
> > This is to start a 2-week working group last call on draft
> > draft-ietf-mmusic-rfc4756bis-03,
> > http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-03.  The =
comment
> > period will end on Wednesday October 28.
> >
> > Please send your comments to the mmusic list and the authors.
> >
> > Thank you,
> > Jean-Francois.
> >
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
> >
> >
> >
>=20
>=20
>=20


From schierl@hhi.fhg.de  Mon Oct 19 08:33:41 2009
Return-Path: <schierl@hhi.fhg.de>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9CDE3A68C0 for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 08:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.143
X-Spam-Level: 
X-Spam-Status: No, score=-2.143 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HTML_MESSAGE=0.001, J_CHICKENPOX_21=0.6, J_CHICKENPOX_22=0.6, MIME_HTML_ONLY=1.457, 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 S2DP6WACiETh for <mmusic@core3.amsl.com>; Mon, 19 Oct 2009 08:33:40 -0700 (PDT)
Received: from mail.hhi.fraunhofer.de (mail.HHI.FRAUNHOFER.DE [193.174.67.45]) by core3.amsl.com (Postfix) with ESMTP id 609A53A6778 for <mmusic@ietf.org>; Mon, 19 Oct 2009 08:33:40 -0700 (PDT)
Received: by mail.hhi.fraunhofer.de (Postfix, from userid 65534) id 7094A1D8903E; Mon, 19 Oct 2009 17:33:45 +0200 (CEST)
Received: from imsva.hhi.de (unknown [127.0.0.1]) by IMSA (Postfix) with ESMTP id 2CAD9150036; Mon, 19 Oct 2009 17:33:45 +0200 (CEST)
Received: from [10.8.0.10] (unknown [10.8.0.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Thomas Schierl", Issuer "Fraunhofer-Gesellschaft Root-CA v2" (not verified)) by mail.hhi.fraunhofer.de (Postfix) with ESMTP id ED9D31D88F51; Mon, 19 Oct 2009 17:33:44 +0200 (CEST)
Message-ID: <4ADC86D7.9030307@hhi.fhg.de>
Date: Mon, 19 Oct 2009 17:33:43 +0200
From: Thomas Schierl <schierl@hhi.fhg.de>
Organization: Fraunhofer HHI
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: "Ali C. Begen (abegen)" <abegen@cisco.com>
References: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cablelabs.com> <4ADC589D.8000306@hhi.fhg.de> <04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com>
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-alterMIME: Yes
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>, mmusic@ietf.org, Joerg Ott <jo@netlab.tkk.fi>, draft-ietf-mmusic-rfc4756bis@tools.ietf.org
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 15:33:41 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=windows-1252"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi  Ali,<br>
<br>
Ali C. Begen (abegen) wrote:
<blockquote
 cite="mid:04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com"
 type="cite">
  <pre wrap="">Now, this sounds different than the first scenario you described above, IMO. And, this leads to the original SDP you gave:

a=group:FEC-XR SB RB
a=group:FEC-XR SB SE RB RB+E

  </pre>
</blockquote>
<br>
You are right, RB and RB+E are meant to be additive with respect to
SB+SE.<br>
<br>
<blockquote
 cite="mid:04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com"
 type="cite">
  <pre wrap=""></pre>
  <blockquote type="cite">
    <pre wrap="">section 4.1:

"Repair flows that are in different FEC groups are non-
   additive.".
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Why would it be contrary? Here, RB and RB+E are in the same line and that is enough to state their additivity. But, in this scenario, their joint decoding helps the group of SB+SE. The above SDP says if the source consists of SB only, then just use RB only since RB+E would not help with decoding.
 
  </pre>
  <blockquote type="cite">
    <pre wrap="">If the signaling in the example above is in line with the intention of
the draft, I would make the following modifications:

- You may add an "...exclusively in different FEC groups..." to the
sentence of section 4.1 above.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
We can add this to make it stronger. But, I believe if two repair flows are additive in a group, it does not mean that they will also be additive in any other group where one of the source flows they protect is listed.
  </pre>
</blockquote>
<br>
I think this makes the text clearer, at least to me.<br>
<br>
<blockquote
 cite="mid:04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com"
 type="cite">
  <pre wrap="">
Agree?

  </pre>
  <blockquote type="cite">
    <pre wrap="">- Further, I would add the following text to section 4.1 to make it clearer:

"In order to express multiple relations between source and repair flows,
source and repair flows may appear in more than one FEC group."
    </pre>
  </blockquote>
  <pre wrap=""><!---->
I believe this was clear, but it is a good suggestion.
  </pre>
</blockquote>
<br>
Good<br>
<br>
<blockquote
 cite="mid:04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com"
 type="cite">
  <pre wrap=""> 
  </pre>
  <blockquote type="cite">
    <pre wrap="">I think the same should be valid for the FEC-SSRC grouping.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Sure.

Thanks for the review. Let me know if you agree with the above.
  </pre>
</blockquote>
<br>
Thanks for the clarifications. I am ok with the changes and the
resulting draft.<br>
<br>
Thomas<br>
<br>
<blockquote
 cite="mid:04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com"
 type="cite">
  <pre wrap="">
Cheers, acbegen.

 
  </pre>
  <blockquote type="cite">
    <pre wrap="">Best regards,
Thomas


--
Thomas Schierl
--------------
Fraunhofer HHI



Jean-Francois Mule wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">This is to start a 2-week working group last call on draft
draft-ietf-mmusic-rfc4756bis-03,
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-03">http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-03</a>.  The comment
period will end on Wednesday October 28.

Please send your comments to the mmusic list and the authors.

Thank you,
Jean-Francois.


_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>



      </pre>
    </blockquote>
    <pre wrap="">

    </pre>
  </blockquote>
  <pre wrap=""><!---->

  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Thomas Schierl
--------------
Fraunhofer HHI



</pre>
<BR>
<BR>
</body>
</html>


From root@core3.amsl.com  Mon Oct 19 09:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id CF63828C0FA; Mon, 19 Oct 2009 09: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: <20091019161501.CF63828C0FA@core3.amsl.com>
Date: Mon, 19 Oct 2009 09:15:01 -0700 (PDT)
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action:draft-ietf-mmusic-rfc4756bis-05.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 16: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 Multiparty Multimedia Session Control Working Group of the IETF.


	Title           : Forward Error Correction Grouping Semantics in Session Description Protocol
	Author(s)       : A. Begen
	Filename        : draft-ietf-mmusic-rfc4756bis-05.txt
	Pages           : 13
	Date            : 2009-10-19

The Session Description Protocol (SDP) supports grouping media lines.
SDP also has semantics defined for grouping the associated source and
Forward Error Correction (FEC)-based repair flows.  However, the
semantics that was defined in RFC 4756 generally fail to provide the
specific grouping relationships between the source and repair flows
when there are more than one source and/or repair flows in the same
group.  Furthermore, the existing semantics does not support
describing additive repair flows.  This document addresses these
issues by introducing new FEC grouping semantics.  SSRC-level
grouping semantics is also introduced in this document for Real-time
Transport Protocol (RTP) streams using SSRC multiplexing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc4756bis-05.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-mmusic-rfc4756bis-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--

From abegen@cisco.com  Mon Oct 19 09:15:47 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B338828C1DE; Mon, 19 Oct 2009 09:15:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.876
X-Spam-Level: 
X-Spam-Status: No, score=-5.876 tagged_above=-999 required=5 tests=[AWL=-0.477, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, J_CHICKENPOX_22=0.6, 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 iXOJ8aSQOsiz; Mon, 19 Oct 2009 09:15:46 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id AB3F628C1D6; Mon, 19 Oct 2009 09:15:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=3574; q=dns/txt; s=sjiport04001; t=1255968953; x=1257178553; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Ali=20C.=20Begen=20(abegen)"=20<abegen@cisco.co m>|Subject:=20RE:=20[MMUSIC]=20WGLC=20on=20draft-ietf-mmu sic-rfc4756bis-03|Date:=20Mon,=2019=20Oct=202009=2009:15: 50=20-0700|Message-ID:=20<04CAD96D4C5A3D48B1919248A8FE0D5 40A6E7817@xmb-sjc-215.amer.cisco.com>|To:=20"Thomas=20Sch ierl"=20<schierl@hhi.fhg.de>|Cc:=20"Jean-Francois=20Mule" =20<jf.mule@cablelabs.com>,=20<mmusic@ietf.org>,=0D=0A=20 =20=20=20=20=20=20=20"Joerg=20Ott"=20<jo@netlab.tkk.fi>, =20<fecframe@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |In-Reply-To:=20<4ADC86D7.9030307@hhi.fhg.de>|References: =20<9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cab lelabs.com>=20<4ADC589D.8000306@hhi.fhg.de>=20<04CAD96D4C 5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com >=20<4ADC86D7.9030307@hhi.fhg.de>; bh=UjXcWGvqn5vkvf4C7a1PC9d9f90qXgdiBQhYsTY4rUE=; b=NwGNE0+2wx8PZOgeAcYs4JUx9b3oaBBMHCGkf5pVJ9JneckUyyWyDPjU L2nHpn4WK30hWKROv2m2He74dm20D0Rd+xAH1QAAAA82GT8SXbEfHXlc4 P8DPnYjr+si41VPgmsoCp1h0kumL1sCNcDK3AJoOZrmtBV/82UnaDc0Ab A=;
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAHMt3EqrR7Ht/2dsb2JhbADEMpZ3hDEE
X-IronPort-AV: E=Sophos;i="4.44,586,1249257600"; d="scan'208";a="45816066"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 19 Oct 2009 16:15:53 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9JGFrrI011848; Mon, 19 Oct 2009 16:15:53 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 19 Oct 2009 09:15:53 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Oct 2009 09:15:50 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A6E7817@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <4ADC86D7.9030307@hhi.fhg.de>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
Thread-Index: AcpQ0ZUtBfUYh5EZQmafLgecsm2eSwABbIqA
References: <9AAEDF491EF7CA48AB587781B8F5D7C6024FEC0C@srvxchg3.cablelabs.com> <4ADC589D.8000306@hhi.fhg.de> <04CAD96D4C5A3D48B1919248A8FE0D540A6E779B@xmb-sjc-215.amer.cisco.com> <4ADC86D7.9030307@hhi.fhg.de>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "Thomas Schierl" <schierl@hhi.fhg.de>
X-OriginalArrivalTime: 19 Oct 2009 16:15:53.0695 (UTC) FILETIME=[6E954EF0:01CA50D7]
Cc: Jean-Francois Mule <jf.mule@cablelabs.com>, fecframe@ietf.org, mmusic@ietf.org, Joerg Ott <jo@netlab.tkk.fi>
Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Oct 2009 16:15:47 -0000

Cool, here is the new version addressing all remaining comments received =
so far.
http://www.ietf.org/id/draft-ietf-mmusic-rfc4756bis-05.txt

Cheers,
-acbegen

> -----Original Message-----
> From: Thomas Schierl [mailto:schierl@hhi.fhg.de]
> Sent: Monday, October 19, 2009 11:34 AM
> To: Ali C. Begen (abegen)
> Cc: Jean-Francois Mule; mmusic@ietf.org; Joerg Ott; draft-ietf-mmusic-
> rfc4756bis@tools.ietf.org
> Subject: Re: [MMUSIC] WGLC on draft-ietf-mmusic-rfc4756bis-03
>=20
> Hi  Ali,
>=20
> Ali C. Begen (abegen) wrote:
>=20
> 	Now, this sounds different than the first scenario you described =
above, IMO. And,
> this leads to the original SDP you gave:
>=20
> 	a=3Dgroup:FEC-XR SB RB
> 	a=3Dgroup:FEC-XR SB SE RB RB+E
>=20
>=20
>=20
>=20
> You are right, RB and RB+E are meant to be additive with respect to =
SB+SE.
>=20
>=20
>=20
>=20
>=20
> 		section 4.1:
>=20
> 		"Repair flows that are in different FEC groups are non-
> 		   additive.".
>=20
>=20
>=20
> 	Why would it be contrary? Here, RB and RB+E are in the same line and =
that is enough
> to state their additivity. But, in this scenario, their joint decoding =
helps the group of
> SB+SE. The above SDP says if the source consists of SB only, then just =
use RB only since
> RB+E would not help with decoding.
>=20
>=20
>=20
> 		If the signaling in the example above is in line with the intention =
of
> 		the draft, I would make the following modifications:
>=20
> 		- You may add an "...exclusively in different FEC groups..." to the
> 		sentence of section 4.1 above.
>=20
>=20
>=20
> 	We can add this to make it stronger. But, I believe if two repair =
flows are additive
> in a group, it does not mean that they will also be additive in any =
other group where one
> of the source flows they protect is listed.
>=20
>=20
>=20
> I think this makes the text clearer, at least to me.
>=20
>=20
>=20
>=20
> 	Agree?
>=20
>=20
>=20
> 		- Further, I would add the following text to section 4.1 to make it =
clearer:
>=20
> 		"In order to express multiple relations between source and repair =
flows,
> 		source and repair flows may appear in more than one FEC group."
>=20
>=20
>=20
> 	I believe this was clear, but it is a good suggestion.
>=20
>=20
>=20
> Good
>=20
>=20
>=20
>=20
>=20
>=20
> 		I think the same should be valid for the FEC-SSRC grouping.
>=20
>=20
>=20
> 	Sure.
>=20
> 	Thanks for the review. Let me know if you agree with the above.
>=20
>=20
>=20
> Thanks for the clarifications. I am ok with the changes and the =
resulting draft.
>=20
> Thomas
>=20
>=20
>=20
>=20
> 	Cheers, acbegen.
>=20
>=20
>=20
>=20
> 		Best regards,
> 		Thomas
>=20
>=20
> 		--
> 		Thomas Schierl
> 		--------------
> 		Fraunhofer HHI
>=20
>=20
>=20
> 		Jean-Francois Mule wrote:
>=20
>=20
> 			This is to start a 2-week working group last call on draft
> 			draft-ietf-mmusic-rfc4756bis-03,
> 			http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-03.  The =
comment
> 			period will end on Wednesday October 28.
>=20
> 			Please send your comments to the mmusic list and the authors.
>=20
> 			Thank you,
> 			Jean-Francois.
>=20
>=20
> 			_______________________________________________
> 			mmusic mailing list
> 			mmusic@ietf.org
> 			https://www.ietf.org/mailman/listinfo/mmusic
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> --
> Thomas Schierl
> --------------
> Fraunhofer HHI
>=20
>=20
>=20
>=20


From magnus.westerlund@ericsson.com  Fri Oct 23 07:18:37 2009
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 94DA63A6890 for <mmusic@core3.amsl.com>; Fri, 23 Oct 2009 07:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.233
X-Spam-Level: 
X-Spam-Status: No, score=-6.233 tagged_above=-999 required=5 tests=[AWL=0.016,  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 kN7T9CeyKjWn for <mmusic@core3.amsl.com>; Fri, 23 Oct 2009 07:18:36 -0700 (PDT)
Received: from mailgw3.ericsson.se (mailgw3.ericsson.se [193.180.251.60]) by core3.amsl.com (Postfix) with ESMTP id 5FB403A67D9 for <mmusic@ietf.org>; Fri, 23 Oct 2009 07:18:36 -0700 (PDT)
X-AuditID: c1b4fb3c-b7b3fae00000105f-18-4ae1bb454363
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw3.ericsson.se (Symantec Mail Security) with SMTP id F7.A6.04191.54BB1EA4; Fri, 23 Oct 2009 16:18:45 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 23 Oct 2009 16:18:45 +0200
Received: from [147.214.183.250] ([147.214.183.250]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 23 Oct 2009 16:18:43 +0200
Message-ID: <4AE1BB44.7010008@ericsson.com>
Date: Fri, 23 Oct 2009 16:18:44 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Joerg Ott <jo@netlab.tkk.fi>
References: <4AB65606.4040905@netlab.tkk.fi>
In-Reply-To: <4AB65606.4040905@netlab.tkk.fi>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 23 Oct 2009 14:18:43.0483 (UTC) FILETIME=[B9E716B0:01CA53EB]
X-Brightmail-Tracker: AAAAAA==
Cc: Martin Stiemerling <Stiemerling@nw.neclab.eu>, Jean-Francois Mule <jf.mule@cablelabs.com>, mmusic@ietf.org
Subject: Re: [MMUSIC] WGLC: draft-ietf-mmusic-rfc2326bis-22
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2009 14:18:37 -0000

Thanks to everyone that has provided comments. In additions to the one
on the mailing list I have received some private ones. Unfortunately I
don't have time to resolve these and provide an updated draft by Monday.
I will do my best to go through your comments next week and provide
proposals for resolutions and bring up where I think additional
discussion are needed.

Best Regards

Magnus

Joerg Ott skrev:
> Folks,
> 
> as agreed in Stockholm, we are issuing working group last
> call on the revised RTSP spec, draft-ietf-mmusic-rfc2326bis-22
> heading for Proposed Standard.
> (http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22)
> 
> The WGLC will expire in four weeks, on 19 Oct 2009.
> 
> We know that this is a long spec, the more important is it
> to receive thorough review by the community.  While we have
> three volunteer reviewers (thanks again!), we urge everyone
> who cares to provide detailed feedback.
> 
> Please review the document and post your comments to the
> MMUSIC list and/or the authors.
> 
> Thanks,
> Joerg
> 
> MMUSIC co-chair
> 
> 


-- 

Magnus Westerlund

IETF Transport Area Director
----------------------------------------------------------------------
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 Oct 23 15:15:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 87FDD3A67FA; Fri, 23 Oct 2009 15: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: <20091023221501.87FDD3A67FA@core3.amsl.com>
Date: Fri, 23 Oct 2009 15:15:01 -0700 (PDT)
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-cs-02.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2009 22:15:01 -0000

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

	Title		: Session Description Protocol (SDP) Extension For Setting Up Audio and Video Media Streams Over Circuit-Switched Bearers In  The Public Switched Telephone Network (PSTN)
	Author(s)	: M. Garcia-Martin, S. Veikkolainen
	Filename	: draft-ietf-mmusic-sdp-cs-02.txt
	Pages		: 25
	Date		: 2009-10-23
	
This memo describes use cases, requirements, and protocol extensions
   for using the Session Description Protocol (SDP) Offer/Answer model
   for establishing audio and video media streams over circuit-switched
   bearers in the Public Switched Telephone Network (PSTN).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-cs-02.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-mmusic-sdp-cs-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart--


From jf.mule@cablelabs.com  Tue Oct 27 10:03:26 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D52BB3A6A5B for <mmusic@core3.amsl.com>; Tue, 27 Oct 2009 10:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 pvqbg1V1IPnP for <mmusic@core3.amsl.com>; Tue, 27 Oct 2009 10:03:26 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 107B03A6A48 for <mmusic@ietf.org>; Tue, 27 Oct 2009 10:03:26 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n9RH3dAn000303; Tue, 27 Oct 2009 11:03:40 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Tue, 27 Oct 2009 11:03:40 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Oct 2009 11:03:34 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C6024FF2D0@srvxchg3.cablelabs.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New WGLC on draft-ietf-mmusic-rfc4756bis-05, comment period ends 11/11/2009
Thread-Index: AcpM6M4YlHJPdxh7ScGv3yGY13jt2wKO+mcA
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <mmusic@ietf.org>
X-Approved: ondar
Cc: Joerg Ott <jo@netlab.tkk.fi>, draft-ietf-mmusic-rfc4756bis@tools.ietf.org
Subject: [MMUSIC] New WGLC on draft-ietf-mmusic-rfc4756bis-05, comment period ends 11/11/2009
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2009 17:03:26 -0000

We received a valid comment on the WGLC issued on 10/14 below. =20
Some folks asked whether the current WGLC is on draft-03, or draft-04
and draft-05, the two updates made during the WLGC period.  To clear any
confusions, Joerg and I would like to re-issue the WGLC on draft-05.

This note is to start a WGLC on draft-ietf-mmusic-rfc4756bis-05, a draft
heading to Proposed Standard
(http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-05). =20
The comment period will end on Wednesday November 11. =20
All comments received since 10/14 will be considered to be part of the
WGLC comments.


Hope this clears any confusion. Please send your comments to the mmusic
list and the authors.

Thank you,
Joerg and Jean-Francois.
MMUSIC co-chairs
=09
> -----Original Message-----
> From: Jean-Francois Mule
> Sent: Wednesday, October 14, 2009 10:10 AM
> To: mmusic@ietf.org
> Cc: 'draft-ietf-mmusic-rfc4756bis@tools.ietf.org'; Joerg Ott
> Subject: WGLC on draft-ietf-mmusic-rfc4756bis-03
>=20
> This is to start a 2-week working group last call on draft draft-
> ietf-mmusic-rfc4756bis-03, http://tools.ietf.org/html/draft-ietf-
> mmusic-rfc4756bis-03.  The comment period will end on Wednesday
> October 28.
>=20
> Please send your comments to the mmusic list and the authors.=09
>=20
> Thank you,
> Jean-Francois.
>=20


From lucas@gonze.com  Tue Oct 27 18:49:30 2009
Return-Path: <lucas@gonze.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A10C928C185 for <mmusic@core3.amsl.com>; Tue, 27 Oct 2009 18:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 Hl0yikTrD8oY for <mmusic@core3.amsl.com>; Tue, 27 Oct 2009 18:49:29 -0700 (PDT)
Received: from mail-ew0-f208.google.com (mail-ew0-f208.google.com [209.85.219.208]) by core3.amsl.com (Postfix) with ESMTP id 6F6473A69D3 for <mmusic@ietf.org>; Tue, 27 Oct 2009 18:49:29 -0700 (PDT)
Received: by ewy4 with SMTP id 4so339261ewy.37 for <mmusic@ietf.org>; Tue, 27 Oct 2009 18:49:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.87.83 with SMTP id x61mr5946338wee.7.1256694580676; Tue,  27 Oct 2009 18:49:40 -0700 (PDT)
Date: Tue, 27 Oct 2009 18:49:40 -0700
Message-ID: <81ef3ab00910271849k2194808pbf6e58a745f1381c@mail.gmail.com>
From: Lucas Gonze <lucas@gonze.com>
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [MMUSIC] draft-pantos-http-live-streaming
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2009 01:49:30 -0000

This is with regard to the draft at
http://tools.ietf.org/html/draft-pantos-http-live-streaming-02 and
discussed on this list
(http://www.ietf.org/mail-archive/web/mmusic/current/maillist.html)
under the subject "Comments on draft-pantos-http-live-streaming."

I agree with this comment by R=E9mi Denis-Courmont of VideoLan:
=3D=3D=3D
* I don't understand how the receiver (the client) of the playlist can
_reliably_ distinguish a plain old playlist file from a live streaming file=
.
M3U URLs are already in common use to deliver "real" playlist, and the
semantics are significantly different from what your draft does. If none of=
the
new parameters you introduce are mandatory, this protocol is basically
impossible to implement in a way that does not break existing functionality=
 in
many media players.
=3D=3D=3D

David Singer replied that "Players can use the presence of the
EXT-X-TARGETDURATION tag to determine whether the playlist file
follows the rules of the draft."

However, that is only true for players that are retrofitted to use
this tag as a magic number. This approach does no good for the
installed base of software.  The result will be that a large amount of
software which is working will acquire a bug.

In addition, there is no way for a pre-existing M3U handler invoked as
a helper app for the browser to pass control along to other apps that
may be able to handle this new protocol.

In addition, Apple's iTunes client does not correctly render ordinary
M3U files.  If the M3U contains more than one reference, the iTunes
client will only render the first one.  Therefore users should not
associate the iTunes client with M3U files.  If the iTunes client is
needed to handle this new protocol, and only software aside from the
iTunes client can handle the existing M3U protocol, then there will be
two broken protocols rather than two working -- but distinct -- ones.

Also, a nit about this section: "M3U Playlist files whose names end in
.m3u8 and/or have the HTTP Content-Type
"application/vnd.apple.mpegurl" are encoded in UTF-8 [RFC3629].  Files
whose names end with .m3u and/or have the HTTP Content-Type [RFC2616]
"audio/mpegurl" are encoded in US-ASCII."  This document is not the
place to specify the media type of existing protocols like the .m3u8
and .m3u extensions.  If it were, the common media type identifier for
M3U is audio/x-mpegurl.  audio/mpegurl is not widely used for M3U and
is not listed by IANA at
http://www.iana.org/assignments/media-types/audio/.

David, I don't intend to flame.  I wouldn't be surprised if what was
happening here was that you were taking the initiative within Apple to
document the protocol for the benefit of the internet community, and I
absolutely do believe that this informational note is a contribution
to the community.

Best,
Lucas Gonze

From jf.mule@cablelabs.com  Thu Oct 29 08:36:16 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9552628C0E4 for <mmusic@core3.amsl.com>; Thu, 29 Oct 2009 08:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 7EJ4hdLPwXnE for <mmusic@core3.amsl.com>; Thu, 29 Oct 2009 08:36:15 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id DC02528C0D7 for <mmusic@ietf.org>; Thu, 29 Oct 2009 08:36:15 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n9TFaVQU017585 for <mmusic@ietf.org>; Thu, 29 Oct 2009 09:36:31 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Thu, 29 Oct 2009 09:36:31 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 29 Oct 2009 09:36:18 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C6024FF443@srvxchg3.cablelabs.com>
In-Reply-To: <4AC0B88F.9000609@netlab.tkk.fi>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Draft MMUSIC Agenda posted for Hiroshima
Thread-Index: AcpAPtokcAZ+zoALS+2UI8O8JJsDCwYbfjVw
References: <4AC0B88F.9000609@netlab.tkk.fi>
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <mmusic@ietf.org>
X-Approved: ondar
Subject: [MMUSIC] Draft MMUSIC Agenda posted for Hiroshima
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2009 15:36:16 -0000

A draft agenda for the MMUSIC WG meeting at IETF 76 is posted at =
http://www.ietf.org/proceedings/09nov/agenda/mmusic.html

We only received 2 agenda items so far:

1) RTSP 2.0                             (Magnus Westerlund, 30)
   http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-22

2) FEC Grouping Semantics in SDP        (Ali Begen, 10)
   http://tools.ietf.org/html/draft-ietf-mmusic-rfc4756bis-05


We know some of you won't be in Hiroshima but let us know if you have =
additional agenda items or if we missed any requests.

Jean-Fran=E7ois.

> -----Original Message-----
> From: Joerg Ott [mailto:jo@netlab.tkk.fi]
> Sent: Monday, September 28, 2009 7:22 AM
> To: mmusic@ietf.org
> Cc: Jean-Francois Mule
> Subject: Agenda items for Hiroshima
>=20
> Folks,
>=20
> we should have one meeting slot for MMUSIC to meet in
> Hiroshima.  We'd like to poll you for agenda items.
>=20
> Please indicate in your agenda item request
>=20
> -- about which published Internet draft (and version)
>     it is
> -- which specific issues you would like to talk about
>=20
> (and, of course, please note the 'note well' statement
>   before sending in requests)
>=20
> WG items will have priority over individual drafts.
>=20
> Please send requests just to Jean-Fran=E7ois and myself.
>=20
> Thanks,
> Joerg

From Simo.Veikkolainen@nokia.com  Fri Oct 30 04:16:03 2009
Return-Path: <Simo.Veikkolainen@nokia.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F19A03A69FC for <mmusic@core3.amsl.com>; Fri, 30 Oct 2009 04:16:02 -0700 (PDT)
X-Quarantine-ID: <9RSAOkJtTpzo>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, MIME error: error: illegal encoding [base64] for MIME type message/external-body
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 9RSAOkJtTpzo for <mmusic@core3.amsl.com>; Fri, 30 Oct 2009 04:16:01 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 677243A6A84 for <mmusic@ietf.org>; Fri, 30 Oct 2009 04:16:01 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-mx03.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n9UBG5UZ002101 for <mmusic@ietf.org>; Fri, 30 Oct 2009 13:16:15 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Oct 2009 13:16:05 +0200
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Oct 2009 13:16:04 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Oct 2009 13:16:00 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Fri, 30 Oct 2009 12:15:57 +0100
From: <Simo.Veikkolainen@nokia.com>
To: <mmusic@ietf.org>
Date: Fri, 30 Oct 2009 12:15:55 +0100
Thread-Topic: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-cs-02.txt
Thread-Index: AcpULo/WhEUVlYSaS1eOa87i29BQWAFIp9fg
Message-ID: <B23B311878A0B4438F5F09F47E01AAE04D8EADA27C@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_003_B23B311878A0B4438F5F09F47E01AAE04D8EADA27CNOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 30 Oct 2009 11:16:00.0392 (UTC) FILETIME=[5C486880:01CA5952]
X-Nokia-AV: Clean
Subject: [MMUSIC] FW:  I-D ACTION:draft-ietf-mmusic-sdp-cs-02.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2009 11:16:03 -0000

--_003_B23B311878A0B4438F5F09F47E01AAE04D8EADA27CNOKEUMSG01mgd_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,
We submitted a new version of the SDP-CS draft. The changes include:
- added possibility of using video streams in addition to audio streams
- changed the name of the "correlation" attribute to "cs-correlation"
- modified the example in Section 6.2. to include also video streams=20
- added a note in Security Considerations that SRTP cannot be used to secur=
e the media in CS domain.

We also noticed that the advanced example in Section 6.2 uses "-" as the po=
rt number, which should be "9". We will need to fix this in the next versio=
n. Also, there has been some off-list discussion on aligning draft-garcia-m=
music-sdp-misc-cap and draft-boucadair-mmusic-ccap which may have some effe=
cts to this draft as well.

Regards,
Simo


>-----Original Message-----
>From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org]=20
>On Behalf Of ext Internet-Drafts@ietf.org
>Sent: 24 October, 2009 01:15
>To: i-d-announce@ietf.org
>Cc: mmusic@ietf.org
>Subject: [MMUSIC] I-D ACTION:draft-ietf-mmusic-sdp-cs-02.txt
>
>A New Internet-Draft is available from the on-line=20
>Internet-Drafts directories.
>This draft is a work item of the Multiparty Multimedia Session=20
>Control Working Group of the IETF.
>
>	Title		: Session Description Protocol (SDP)=20
>Extension For Setting Up Audio and Video Media Streams Over=20
>Circuit-Switched Bearers In  The Public Switched Telephone=20
>Network (PSTN)
>	Author(s)	: M. Garcia-Martin, S. Veikkolainen
>	Filename	: draft-ietf-mmusic-sdp-cs-02.txt
>	Pages		: 25
>	Date		: 2009-10-23
>=09
>This memo describes use cases, requirements, and protocol extensions
>   for using the Session Description Protocol (SDP) Offer/Answer model
>   for establishing audio and video media streams over circuit-switched
>   bearers in the Public Switched Telephone Network (PSTN).
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdp-cs-02.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=20
>reader implementation to automatically retrieve the ASCII=20
>version of the Internet-Draft.
>=

--_003_B23B311878A0B4438F5F09F47E01AAE04D8EADA27CNOKEUMSG01mgd_
Content-Type: message/external-body; name="draft-ietf-mmusic-sdp-cs-02.url"
Content-Description: draft-ietf-mmusic-sdp-cs-02.url
Content-Disposition: attachment; filename="draft-ietf-mmusic-sdp-cs-02.url";
	size=92; creation-date="Sat, 24 Oct 2009 00:17:09 GMT";
	modification-date="Sat, 24 Oct 2009 00:17:09 GMT"
Content-Transfer-Encoding: base64


W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1pZXRmLW1tdXNpYy1zZHAtY3MtMDIudHh0DQo=

--_003_B23B311878A0B4438F5F09F47E01AAE04D8EADA27CNOKEUMSG01mgd_
Content-Type: text/plain; name="ATT00001..txt"
Content-Description: ATT00001..txt
Content-Disposition: attachment; filename="ATT00001..txt"; size=133;
	creation-date="Sat, 24 Oct 2009 00:17:09 GMT";
	modification-date="Sat, 24 Oct 2009 00:17:09 GMT"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBt
YWlsaW5nIGxpc3QNCm1tdXNpY0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9tbXVzaWMNCg==

--_003_B23B311878A0B4438F5F09F47E01AAE04D8EADA27CNOKEUMSG01mgd_--

From abegen@cisco.com  Fri Oct 30 08:48:29 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E74AC3A69AF; Fri, 30 Oct 2009 08:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.488
X-Spam-Level: 
X-Spam-Status: No, score=-6.488 tagged_above=-999 required=5 tests=[AWL=0.111,  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 nTRbL3PiwCcd; Fri, 30 Oct 2009 08:48:28 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id BD9423A6969; Fri, 30 Oct 2009 08:48:28 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAM+n6kqrRN+J/2dsb2JhbADJZ4kfCI8Ggk0IgWgE
X-IronPort-AV: E=Sophos;i="4.44,654,1249257600"; d="scan'208";a="421173915"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-6.cisco.com with ESMTP; 30 Oct 2009 15:48:46 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id n9UFmkw0003685; Fri, 30 Oct 2009 15:48:46 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Oct 2009 08:48:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 30 Oct 2009 08:48:26 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A8438CC@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04CA3F09@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on http://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01
Thread-Index: AcpZc9a8faHDQsSKTQ2uUezfE/+AGgAAjMUQ
References: <238382595265324EA50F6134BB42DCAF04CA3F09@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.com>, <avt@ietf.org>
X-OriginalArrivalTime: 30 Oct 2009 15:48:45.0646 (UTC) FILETIME=[76BBFEE0:01CA5978]
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on http://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2009 15:48:30 -0000

Hi Tom,

Thanks for reading the revised draft.

> Hi Ali,
>=20
> When reading through the draft =
http://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-
> mcast-rtp-01 =
<http://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01>=
  ,
> including your editor comments, I understand that despite the cookie =
exchange solution, it
> does not allow to have a "stateless" server (that is, the server needs =
to remember the
> ports). You indeed correctly pointed out that RTCP SR messages are =
unsollicited, so they
> cannot be linked to a received cookie. I do not think it makes sense =
to "forbid" the
> server (RS in the considered use cases) to send RTCP SR at any moment =
in time. Hence, as

Yes, sender reports pose a problem at this time (the server needs to =
remember the port). There may be a nice solution to it, but we don't =
have any for now.

> the RS needs to remember anyhow the ports and thus must keep state, =
the cookie would no
> longer be needed from that perspective. Is that an appropriate =
conclusion? Port mapping

That is where we are now. But I am not sure whether the WG will make =
that conclusion.=20

> response message (exchange) is then no longer needed anymore, although =
I understand this
> message is also a kind of confirmation of reception of the port =
mapping request message.

Yes, response serves as a confirmation of the request.
=20
> You also mention that NAT tolerance is a design criterium. How was =
that taken into account
> in the proposed messaging flow?

We have not gotten into its details yet. But, yes, nat friendliness is =
desired/required.
=20
> The NAT friendly solution IMO is that the port mapping request =
messages for RTP and RTCP
> is sent along with a RAMS-R FB by the RR to the RS whereas a port =
mapping request for RTP

But this message (since it includes RAMS-R) needs to go to port P2 on RS =
(rtcp port for the primary mcast session) instead of port P3.

> is sent along with a NACK FB by the RR to the RS. This is not to =
inform the RS of the
> ports it should use each time -as it needs to remember that anyhow and =
keep state based on
> the 1st received port maping request by the RR- but to open the NAPT =
in between. The
> disadvantage is of course the higher messaging load for the RS (and =
RR).
>=20
> I realise the draft wants to provide an answer on how an RR can =
indicate the UDP ports it
> wishes to use for RTP unicast sessions without any session-signaling =
protocol involved,
> but I do not think all design criteria can be met. I think we can drop =
the cookie, and
> just keep the port mapping response/request message (without cookie), =
meaning the RS needs
> to keep state of the port allocated to each RR  based on acknowledged =
port mapping request
> messages, and when receiving RTCP Byes in the retransmission session, =
it can drop the
> "state".

This is an interesting proposal but we are giving up from the stateless =
server idea. Are we willing to do that? In order to keep the server =
stateless, we might break another rule, if we have to, and re-consider =
our earlier proposal - PubPorts (where port numbers are directly =
transmitted in the RTCP message). That will satisfy our requirements =
except that it introduces layer violation.
=20
> In my opinion, the ideal solution is still that we can make the P2 and =
P3 ports on the RS
> equal, where a single message (RAMS-R or NACK) by an RR will allow the =
response (RTP burst
> or RTP retransmission packet) to pass through NAT, provided the RR =
supports the RTP/RTCP

Yes, your proposal above requires this.

> port muxing.  I realise this would require the RS to use an SSRC in =
the unicast
> retransmission session that is different from the one used in the =
primary SSM session-
> allowing the RS to distinguish RTCP messages based on the media SSRC =
in the RTCP messages.
> However, using a different SSRC when retransmission session muxing is =
used, is forbidden

Correct.

> by RFC 4588. But there is no justification in RFC 4588 why this was =
disallowed, and
> further inquiries have made me believe that there is really no hard =
reason why this
> constraint was imposed.

I believe the reason is to allow for easier monitoring and processing of =
RTCP reports. If a session and its retransmission session use different =
SSRCs, how do we correlate them at the monitoring (RTCP processing) =
agent? There can be multiple primary sessions and their retransmission =
sessions running on the same client at the same time.
=20
> As you know, in the DVB retransmission solution for linear TV (hence =
SSM sessions), it is
> allowed to use a different SSRC even though session muxing is used (as =
the UNICAST
> retransmission session is associated with a SSM session), "overruling" =
RFC 4588 on that
> aspect. This then allows making P2=3DP3, with no ambiguities for the =
RS in resolving which
> incoming RTCP message belongs to which session (either the unicast =
retransmission session
> or the unicast feedback channel of the SSM session).  This solution =
requires no port
> signaling at all and is NAT friendly.

Yes, I am aware of that. I will try to get an answer from MMUSIC folks, =
too. In fact, I cc'ed mmsuic hoping that someone will clarify this =
requirement in RFC 4588.

Thanks again,
-acbegen
=20
> Regards
> Tom
>=20
>=20
>=20
>=20
>=20


From jf.mule@cablelabs.com  Fri Oct 30 09:08:40 2009
Return-Path: <jf.mule@cablelabs.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB8C028C0E5 for <mmusic@core3.amsl.com>; Fri, 30 Oct 2009 09:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.463
X-Spam-Level: 
X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
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 nwivSYcUg8gc for <mmusic@core3.amsl.com>; Fri, 30 Oct 2009 09:08:39 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 976E428C0E0 for <mmusic@ietf.org>; Fri, 30 Oct 2009 09:08:39 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.3/8.14.3) with SMTP id n9UG8tAK020067; Fri, 30 Oct 2009 10:08:55 -0600
Received: from srvxchg3.cablelabs.com (10.5.0.25) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com); Fri, 30 Oct 2009 10:08:54 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/511/kyzyl.cablelabs.com)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 30 Oct 2009 10:08:50 -0600
Message-ID: <9AAEDF491EF7CA48AB587781B8F5D7C602644EC7@srvxchg3.cablelabs.com>
In-Reply-To: <04CAD96D4C5A3D48B1919248A8FE0D540A8438CC@xmb-sjc-215.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [MMUSIC] Comments onhttp://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01
Thread-Index: AcpZc9a8faHDQsSKTQ2uUezfE/+AGgAAjMUQAAFAFbA=
References: <238382595265324EA50F6134BB42DCAF04CA3F09@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D540A8438CC@xmb-sjc-215.amer.cisco.com>
From: "Jean-Francois Mule" <jf.mule@cablelabs.com>
To: <mmusic@ietf.org>
X-Approved: ondar
Cc: VAN CAENEGEM Tom <Tom.Van_Caenegem@alcatel-lucent.com>
Subject: Re: [MMUSIC] Comments onhttp://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2009 16:08:40 -0000

As an FYI, and thanks to Ali who suggested it, we have also added this =
draft on the agenda for the MMUSIC WG session in Hiroshima.

Jean-Fran=E7ois

> -----Original Message-----
> From: mmusic-bounces@ietf.org [mailto:mmusic-bounces@ietf.org] On
> Behalf Of Ali C. Begen (abegen)
> Sent: Friday, October 30, 2009 9:48 AM
> To: VAN CAENEGEM Tom; avt@ietf.org
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] Comments onhttp://tools.ietf.org/html/draft-
> begen-avt-ports-for-ucast-mcast-rtp-01
>=20
> Hi Tom,
>=20
> Thanks for reading the revised draft.
>=20
> > Hi Ali,
> >
> > When reading through the draft http://tools.ietf.org/html/draft-
> begen-avt-ports-for-ucast-
> > mcast-rtp-01 <http://tools.ietf.org/html/draft-begen-avt-ports-
> for-ucast-mcast-rtp-01>  ,
> > including your editor comments, I understand that despite the
> cookie exchange solution, it
> > does not allow to have a "stateless" server (that is, the server
> needs to remember the
> > ports). You indeed correctly pointed out that RTCP SR messages
> are unsollicited, so they
> > cannot be linked to a received cookie. I do not think it makes
> sense to "forbid" the
> > server (RS in the considered use cases) to send RTCP SR at any
> moment in time. Hence, as
>=20
> Yes, sender reports pose a problem at this time (the server needs
> to remember the port). There may be a nice solution to it, but we
> don't have any for now.
>=20
> > the RS needs to remember anyhow the ports and thus must keep
> state, the cookie would no
> > longer be needed from that perspective. Is that an appropriate
> conclusion? Port mapping
>=20
> That is where we are now. But I am not sure whether the WG will
> make that conclusion.
>=20
> > response message (exchange) is then no longer needed anymore,
> although I understand this
> > message is also a kind of confirmation of reception of the port
> mapping request message.
>=20
> Yes, response serves as a confirmation of the request.
>=20
> > You also mention that NAT tolerance is a design criterium. How
> was that taken into account
> > in the proposed messaging flow?
>=20
> We have not gotten into its details yet. But, yes, nat friendliness
> is desired/required.
>=20
> > The NAT friendly solution IMO is that the port mapping request
> messages for RTP and RTCP
> > is sent along with a RAMS-R FB by the RR to the RS whereas a port
> mapping request for RTP
>=20
> But this message (since it includes RAMS-R) needs to go to port P2
> on RS (rtcp port for the primary mcast session) instead of port P3.
>=20
> > is sent along with a NACK FB by the RR to the RS. This is not to
> inform the RS of the
> > ports it should use each time -as it needs to remember that
> anyhow and keep state based on
> > the 1st received port maping request by the RR- but to open the
> NAPT in between. The
> > disadvantage is of course the higher messaging load for the RS
> (and RR).
> >
> > I realise the draft wants to provide an answer on how an RR can
> indicate the UDP ports it
> > wishes to use for RTP unicast sessions without any session-
> signaling protocol involved,
> > but I do not think all design criteria can be met. I think we can
> drop the cookie, and
> > just keep the port mapping response/request message (without
> cookie), meaning the RS needs
> > to keep state of the port allocated to each RR  based on
> acknowledged port mapping request
> > messages, and when receiving RTCP Byes in the retransmission
> session, it can drop the
> > "state".
>=20
> This is an interesting proposal but we are giving up from the
> stateless server idea. Are we willing to do that? In order to keep
> the server stateless, we might break another rule, if we have to,
> and re-consider our earlier proposal - PubPorts (where port numbers
> are directly transmitted in the RTCP message). That will satisfy
> our requirements except that it introduces layer violation.
>=20
> > In my opinion, the ideal solution is still that we can make the
> P2 and P3 ports on the RS
> > equal, where a single message (RAMS-R or NACK) by an RR will
> allow the response (RTP burst
> > or RTP retransmission packet) to pass through NAT, provided the
> RR supports the RTP/RTCP
>=20
> Yes, your proposal above requires this.
>=20
> > port muxing.  I realise this would require the RS to use an SSRC
> in the unicast
> > retransmission session that is different from the one used in the
> primary SSM session-
> > allowing the RS to distinguish RTCP messages based on the media
> SSRC in the RTCP messages.
> > However, using a different SSRC when retransmission session
> muxing is used, is forbidden
>=20
> Correct.
>=20
> > by RFC 4588. But there is no justification in RFC 4588 why this
> was disallowed, and
> > further inquiries have made me believe that there is really no
> hard reason why this
> > constraint was imposed.
>=20
> I believe the reason is to allow for easier monitoring and
> processing of RTCP reports. If a session and its retransmission
> session use different SSRCs, how do we correlate them at the
> monitoring (RTCP processing) agent? There can be multiple primary
> sessions and their retransmission sessions running on the same
> client at the same time.
>=20
> > As you know, in the DVB retransmission solution for linear TV
> (hence SSM sessions), it is
> > allowed to use a different SSRC even though session muxing is
> used (as the UNICAST
> > retransmission session is associated with a SSM session),
> "overruling" RFC 4588 on that
> > aspect. This then allows making P2=3DP3, with no ambiguities for
> the RS in resolving which
> > incoming RTCP message belongs to which session (either the
> unicast retransmission session
> > or the unicast feedback channel of the SSM session).  This
> solution requires no port
> > signaling at all and is NAT friendly.
>=20
> Yes, I am aware of that. I will try to get an answer from MMUSIC
> folks, too. In fact, I cc'ed mmsuic hoping that someone will
> clarify this requirement in RFC 4588.
>=20
> Thanks again,
> -acbegen
>=20
> > Regards
> > Tom
> >
> >
> >
> >
> >
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

From lucas@gonze.com  Fri Oct 30 10:07:05 2009
Return-Path: <lucas@gonze.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 550423A6A83 for <mmusic@core3.amsl.com>; Fri, 30 Oct 2009 10:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.047
X-Spam-Level: 
X-Spam-Status: No, score=-1.047 tagged_above=-999 required=5 tests=[AWL=-0.929, BAYES_20=-0.74, FM_FORGED_GMAIL=0.622]
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 ofqCtBMV+fYz for <mmusic@core3.amsl.com>; Fri, 30 Oct 2009 10:07:04 -0700 (PDT)
Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by core3.amsl.com (Postfix) with ESMTP id 4E1D53A6A5C for <mmusic@ietf.org>; Fri, 30 Oct 2009 10:07:04 -0700 (PDT)
Received: by ewy18 with SMTP id 18so2928272ewy.43 for <mmusic@ietf.org>; Fri, 30 Oct 2009 10:07:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.86.72 with SMTP id v50mr682519wee.184.1256922440446; Fri,  30 Oct 2009 10:07:20 -0700 (PDT)
In-Reply-To: <81ef3ab00910271849k2194808pbf6e58a745f1381c@mail.gmail.com>
References: <81ef3ab00910271849k2194808pbf6e58a745f1381c@mail.gmail.com>
Date: Fri, 30 Oct 2009 10:07:20 -0700
Message-ID: <81ef3ab00910301007u12c504deq28670cc1d84cf75@mail.gmail.com>
From: Lucas Gonze <lucas@gonze.com>
To: mmusic@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [MMUSIC] draft-pantos-http-live-streaming
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2009 17:07:05 -0000

I realize that I am intruding on the normal business of this list with
this topic.  I apologize in advance.

There haven't been responses from Apple to comments here on
draft-pantos-live-streaming, so I wonder whether that business may
have moved elsewhere.  If anyone is aware of a change of venue for
that work, could you give me a ping?

Thanks in advance.

On Tue, Oct 27, 2009 at 6:49 PM, Lucas Gonze <lucas@gonze.com> wrote:
> This is with regard to the draft at
> http://tools.ietf.org/html/draft-pantos-http-live-streaming-02 and

From abegen@cisco.com  Fri Oct 30 14:16:47 2009
Return-Path: <abegen@cisco.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C854E3A6916; Fri, 30 Oct 2009 14:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.491
X-Spam-Level: 
X-Spam-Status: No, score=-6.491 tagged_above=-999 required=5 tests=[AWL=0.108,  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 SR70yYFPVZD4; Fri, 30 Oct 2009 14:16:46 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id A86033A63EC; Fri, 30 Oct 2009 14:16:46 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEACj16kqrR7H+/2dsb2JhbADIMZg4hD0E
X-IronPort-AV: E=Sophos;i="4.44,656,1249257600"; d="scan'208";a="421351772"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 30 Oct 2009 21:17:04 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n9ULH4vc020877; Fri, 30 Oct 2009 21:17:04 GMT
Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 30 Oct 2009 14:17:03 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 30 Oct 2009 14:15:59 -0700
Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A843A83@xmb-sjc-215.amer.cisco.com>
In-Reply-To: <238382595265324EA50F6134BB42DCAF04CA4002@FRVELSMBS22.ad2.ad.alcatel.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Comments on http://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01
Thread-Index: AcpZc9a8faHDQsSKTQ2uUezfE/+AGgAAjMUQAAKD1SAACObOEA==
References: <238382595265324EA50F6134BB42DCAF04CA3F09@FRVELSMBS22.ad2.ad.alcatel.com> <04CAD96D4C5A3D48B1919248A8FE0D540A8438CC@xmb-sjc-215.amer.cisco.com> <238382595265324EA50F6134BB42DCAF04CA4002@FRVELSMBS22.ad2.ad.alcatel.com>
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "VAN CAENEGEM Tom" <Tom.Van_Caenegem@alcatel-lucent.com>, <avt@ietf.org>
X-OriginalArrivalTime: 30 Oct 2009 21:17:03.0997 (UTC) FILETIME=[53DDD2D0:01CA59A6]
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comments on http://tools.ietf.org/html/draft-begen-avt-ports-for-ucast-mcast-rtp-01
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2009 21:16:47 -0000

> > The NAT friendly solution IMO is that the port mapping request
> > messages for RTP and RTCP is sent along with a RAMS-R FB by the RR =
to
> > the RS whereas a port mapping request for RTP
>=20
> But this message (since it includes RAMS-R) needs to go to port P2 on =
RS
> (rtcp port for the primary mcast session) instead of port P3.
>=20
> TOM: I meant two separate RTCP messages, the RAMS-R sent to port P2, =
and
> the port mapping request is sent to port P3. Not a neat solution =
either,
> I agree.

I see.
=20
> > is sent along with a NACK FB by the RR to the RS. This is not to
> > inform the RS of the ports it should use each time -as it needs to
> > remember that anyhow and keep state based on the 1st received port
> > maping request by the RR- but to open the NAPT in between. The
> disadvantage is of course the higher messaging load for the RS (and =
RR).
> >
> > I realise the draft wants to provide an answer on how an RR can
> > indicate the UDP ports it wishes to use for RTP unicast sessions
> > without any session-signaling protocol involved, but I do not think
> > all design criteria can be met. I think we can drop the cookie, and
> > just keep the port mapping response/request message (without =
cookie),
> > meaning the RS needs to keep state of the port allocated to each RR
> > based on acknowledged port mapping request messages, and when
> receiving RTCP Byes in the retransmission session, it can drop the
> "state".
>=20
> This is an interesting proposal but we are giving up from the =
stateless
> server idea. Are we willing to do that? In order to keep the server
> stateless, we might break another rule, if we have to, and re-consider
> our earlier proposal - PubPorts (where port numbers are directly
> transmitted in the RTCP message). That will satisfy our requirements
> except that it introduces layer violation.
>=20
> TOM: don't you still face the same issue, that RTCP SR get sent by the
> RS unsollicited, so the RS needs to remember from previous received
> pubport message, which port to use for the RTCP SR?

Yes, sender reports seem to require state on the server.

> > In my opinion, the ideal solution is still that we can make the P2 =
and
>=20
> > P3 ports on the RS equal, where a single message (RAMS-R or NACK) by
> > an RR will allow the response (RTP burst or RTP retransmission =
packet)
>=20
> > to pass through NAT, provided the RR supports the RTP/RTCP
>=20
> Yes, your proposal above requires this.
>=20
> TOM: not really, but making P2=3DP3 on top of that definitely takes =
away
> many complexities and "overhead".

Sure, it does but also brings up other issues mentioned below.
 =20
> > port muxing.  I realise this would require the RS to use an SSRC in
> > the unicast retransmission session that is different from the one =
used
>=20
> > in the primary SSM session- allowing the RS to distinguish RTCP
> messages based on the media SSRC in the RTCP messages.
> > However, using a different SSRC when retransmission session muxing =
is
> > used, is forbidden
>=20
> Correct.
>=20
> > by RFC 4588. But there is no justification in RFC 4588 why this was
> > disallowed, and further inquiries have made me believe that there is
> > really no hard reason why this constraint was imposed.
>=20
> I believe the reason is to allow for easier monitoring and processing =
of
> RTCP reports. If a session and its retransmission session use =
different
> SSRCs, how do we correlate them at the monitoring (RTCP processing)
> agent? There can be multiple primary sessions and their retransmission
> sessions running on the same client at the same time.
>=20
> TOM: the agent needs the SDP  -or any other signaling info- to start =
the
> monitoring process. This may include SSRC information. If not, the RFC
> 4588  indicates how association can be done for ssrc-multiplexed =
scheme,
> and I cannot see why  the described approach cannot be mapped to the
> session-multiplexed scheme where the original and the retransmission
> stream have a different SSRC.

Correlating SSRC-muxed streams is a lot more complicated than =
correlating session-muxed streams. Section 5.3 of 4588 provides some =
guidelines on how to do it and also mentions an ambiguity, which could =
be addressed by taking some precautions at the receiver in unicast =
retransmissions, but the same is not necessarily true for multicast =
retransmissions (something DVB-IPI supports).=20

If we can figure out a nice and solid solution to this, I'll take it. =
But this seems questionable (at least to me).

Cheers, acbegen

