From Felix.Wyss@inin.com Sat Apr 16 22:09:18 2011 Return-Path: X-Original-To: speechsc@ietfc.amsl.com Delivered-To: speechsc@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id C1D99E06D3 for ; Sat, 16 Apr 2011 22:09:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.198 X-Spam-Level: X-Spam-Status: No, score=-0.198 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2IyKn9Z+nj+V for ; Sat, 16 Apr 2011 22:09:17 -0700 (PDT) Received: from inin.com (smtpgw.inin.com [209.43.1.24]) by ietfc.amsl.com (Postfix) with ESMTP id 9154CE0655 for ; Sat, 16 Apr 2011 22:09:17 -0700 (PDT) Received: from ININHUB1 [172.16.1.156] by smtpgw.inin.com - Websense Email Security (6.1.1); Sun, 17 Apr 2011 01:09:16 -0400 Received: from ININMAIL.i3domain.inin.com ([172.16.1.186]) by ininhub1.i3domain.inin.com ([172.16.1.156]) with mapi; Sun, 17 Apr 2011 01:09:16 -0400 From: "Wyss, Felix" To: "speechsc@ietf.org" Date: Sun, 17 Apr 2011 01:09:15 -0400 Thread-Topic: MRCP and mixed IPv4/IPv6 environments Thread-Index: Acv8vZaKv27BjMKEQtecUzJUelnP8A== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_B043FD61A001424599674F50FC89C2D7B3DFF766D5ININMAILi3dom_" MIME-Version: 1.0 X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1 X-SEF-ZeroHour-RefID: fgs=355854944 X-SEF-Processed: 6_1_1_105__2011_04_17_01_09_16 Subject: [Speechsc] MRCP and mixed IPv4/IPv6 environments X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2011 05:09:18 -0000 --_000_B043FD61A001424599674F50FC89C2D7B3DFF766D5ININMAILi3dom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The examples in the most recent draft (draft-ietf-speechsc-mrcpv2-24.txt) u= se only IPv4 address types. There is no mention of IPv6, let alone how MRC= P should be used in mixed IPv4/IPv6 environments. I think that should be a= ddressed in the RFC, at a minimum with some examples and/or discussion to p= rovide guidance to implementers. This seems especially important as the in= troduction of the "a=3Dcmid" co-media attribute adds another dimension to t= he media negotiation. As an example, I took a synthesizer sample from the current draft and tried= to come up with an offer/answer exchange in a mixed environment with alter= nate address type semantics (RFC#4091). I am assuming here that the offere= r allows the answerer to accept a different address type for MRCP and RTP b= y listing both stream identifiers of the IP4 and IP6 RTP streams as two sep= arate "a=3Dcmid" attributes. Thus, the answerer could elect to use IPv6 fo= r MRCP and IPv4 for RTP: Offer: v=3D0 o=3Dsarvi 2890844526 2890844526 IN IP6 2001:DB8::4 s=3D- a=3Dgroup:ANAT 1 2 a=3Dgroup:ANAT 3 4 m=3Dapplication 9 TCP/MRCPv2 1 c=3DIN IP4 192.0.2.12 a=3Dsetup:active a=3Dconnection:new a=3Dresource:speechsynth a=3Dcmid:3 a=3Dcmid:4 a=3Dmid:1 m=3Dapplication 9 TCP/MRCPv2 1 c=3DIN IP6 2001:DB8::1 a=3Dsetup:active a=3Dconnection:new a=3Dresource:speechsynth a=3Dcmid:3 a=3Dcmid:4 a=3Dmid:2 m=3Daudio 49170 RTP/AVP 0 c=3DIN IP4 192.0.2.12 a=3Drtpmap:0 pcmu/8000 a=3Drecvonly a=3Dmid:3 m=3Daudio 49170 RTP/AVP 0 c=3DIN IP6 2001:DB8::1 a=3Drtpmap:0 pcmu/8000 a=3Drecvonly a=3Dmid:4 Example Answer 1 (IPv6 for MRCP, IPv6 for RTP): v=3D0 o=3D 2890842808 2890842808 IN IP6 2001:DB8::5 s=3D- m=3Dapplication 0 TCP/MRCPv2 1 c=3DIN IP4 0.0.0.0 a=3Dmid:1 m=3Dapplication 32416 TCP/MRCPv2 1 c=3DIN IP6 2001:DB8::2 a=3Dsetup:passive a=3Dconnection:new a=3Dchannel:32AECB234338@speechsynth a=3Dcmid:4 a=3Dmid:2 m=3Daudio 0 RTP/AVP 0 c=3DIN IP4 0.0.0.0 a=3Dmid:3 m=3Daudio 48260 RTP/AVP 0 c=3DIN IP6 IN IP6 2001:DB8::2 a=3Drtpmap:0 pcmu/8000 a=3Dsendonly a=3Dmid:4 Example Answer 2 (IPv6 for MRCP, IPv4 for RTP): v=3D0 o=3D 2890842808 2890842808 IN IP6 2001:DB8::5 s=3D- m=3Dapplication 0 TCP/MRCPv2 1 c=3DIN IP4 0.0.0.0 a=3Dmid:1 m=3Dapplication 32416 TCP/MRCPv2 1 c=3DIN IP6 2001:DB8::2 a=3Dsetup:passive a=3Dconnection:new a=3Dchannel:32AECB234338@speechsynth a=3Dcmid:3 a=3Dmid:2 m=3Daudio 48260 RTP/AVP 0 c=3DIN IP4 192.0.2.11 a=3Drtpmap:0 pcmu/8000 a=3Dsendonly a=3Dmid:3 m=3Daudio 0 RTP/AVP 0 c=3DIN IP6 :: a=3Dmid:4 Does that seem like an appropriate interpretation? Thanks, Felix Wyss Interactive Intelligence, Inc. --_000_B043FD61A001424599674F50FC89C2D7B3DFF766D5ININMAILi3dom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The examples in the most = recent draft (draft-ietf-speechsc-mrcpv2-24.txt) use only IPv4 address type= s.  There is no mention of IPv6, let alone how MRCP should be used in = mixed IPv4/IPv6 environments.  I think that should be addressed in the= RFC, at a minimum with some examples and/or discussion to provide guidance= to implementers.  This seems especially important as the introduction= of the "a=3Dcmid" co-media attribute adds another dimension to t= he media negotiation. 

 

As an example, I took a synthesizer sample from = the current draft and tried to come up with an offer/answer exchange in a m= ixed environment with alternate address type semantics (RFC#4091).  I = am assuming here that the offerer allows the answerer to accept a different= address type for MRCP and RTP by listing both stream identifiers of the IP= 4 and IP6 RTP streams as two separate "a=3Dcmid" attributes. = ; Thus, the answerer could elect to use IPv6 for MRCP and IPv4 for RTP:&nbs= p;

 

 

Offer:=

 

v=3D0

o=3Dsarvi 2890844526 2890844526 IN IP6 2001:DB8::4

s=3D-

a=3Dgroup:ANAT 1 2=

a=3Dgroup:ANAT 3 4

m=3Dapplica= tion 9 TCP/MRCPv2 1

c=3DIN IP4 192.0.2.12

a=3Dsetup:active

a=3Dconnection:new

a=3Dresource:speechsynth

a=3Dcmid:3<= /span>

a=3Dcmid:4=

a=3Dmid:1=

m=3Dapplication 9 TC= P/MRCPv2 1

c=3DIN IP6 2001:DB8::1

a=3Dsetup:active

a=3Dconnection:new

a=3Dresource:speechsynth

a=3Dcmid:3

a=3Dcmid:4<= /p>

a=3Dmid:2<= /p>

m=3Daudio 49170 RTP/AVP 0

c=3DIN IP4 1= 92.0.2.12

= a=3Drtpmap:0 pcmu/8000

a=3Drecvonly

a=3Dmid:3

m=3Daudio 49170 RTP/AVP 0

c=3DIN IP6 2001:DB8::1

a=3Drtpmap:0 pcmu/8000

a=3Drecvonly<= o:p>

a=3Dmid:4<= o:p>

 = ;

 

Example Answer 1 (IPv6 for MRCP, IPv6 for RTP):

 

v=3D0

o=
=3D 2890842808 2890842808 IN IP6 2001:DB=
8::5

s= =3D-

<= span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>m=3Da= pplication 0 TCP/MRCPv2 1

c=3DIN IP4 0.0.0.0

a=3Dmid:1

m=3Dapplicat= ion 32416 TCP/MRCPv2 1

c=3DIN IP6 2001:DB8::2

a=3Dsetup:pas= sive

a=3Dconnection:new

a=3Dchannel:32AECB234338@speechsynth

a=3Dcmid:4<= o:p>

a=3Dmid:2<= o:p>

m=3Daudio = 0 RTP/AVP 0

c=3DIN IP=
4 0.0.0.0

a=3Dmid:3

m=3Daudio 48260 RTP/AVP 0
=

c=3DIN IP6 IN IP6 2001:DB8::2

a=3Drtpmap:= 0 pcmu/8000

a=3Dmid:4

 

Example Answer 2 (IPv6 for MRC= P, IPv4 for RTP):

 

v=3D0= 

o=3D 2890842808 2890842808 IN IP6 2001:DB8::5

s=3D-

m=3Dapplication 0 TCP/MRCPv2 1

c=3DIN IP4 0.0.0.0

a=3Dmid:1

m=3Dapplication 32416 TCP/MRCPv2 1=

c=3DIN IP6 2001:DB8::2=

a=3Dsetup:passive

a=3Dconne= ction:new

a=3Dchannel:32AECB234338@speechsynth

a=3Dcmid:3

a=3Dmid:2

m=3Daudio 48260 RTP/AVP 0

c=3DIN IP4 192.0.2.11

a=3Drtpmap:0 pcmu/8000

a=3Dsendonly

a=3Dmid:3

m=3Daudio 0 RTP/AVP 0

c=3DIN IP6 ::

a=3Dmid:4

 =

 

Does that seem like an appropriate interpretation= ?  

 

Thanks,

Felix Wyss

Interactive Intelligence, Inc.

 

= --_000_B043FD61A001424599674F50FC89C2D7B3DFF766D5ININMAILi3dom_-- From slawomir.testowy@gmail.com Sun Apr 17 23:32:06 2011 Return-Path: X-Original-To: speechsc@ietfc.amsl.com Delivered-To: speechsc@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id DD482E0758; Sun, 17 Apr 2011 23:32:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2rqNUcX6xbH9; Sun, 17 Apr 2011 23:32:02 -0700 (PDT) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by ietfc.amsl.com (Postfix) with ESMTP id 9C6FEE05F5; Sun, 17 Apr 2011 23:32:02 -0700 (PDT) Received: by pxi20 with SMTP id 20so3037819pxi.27 for ; Sun, 17 Apr 2011 23:32:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yVFcRCtHvoCUG8ZATAM+kedCXD0+MVBd9Sa7t+QAEZ4=; b=pTTF+Jv0Jp3A1KzTRGLHkStR/cDqddTW+iESVIs87TFrXby6ImL6kSf9EtGQ4uJDVa jkSXFAphR5yXwdIvSXKKWIBKPc8wpusgvbVRA4XvCOKItTpvrDwEKkn+FDYduC0/tb2o HoLFXgQ+PlNY10XAP4HZX2bn+HoS4rgACX/6o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ELergUC2CwNhn0v6NT9N6IEYohQWBR4jyZ80uOB6Yjdwwg4xDj23KUaeNmfikbqmB1 l25DdpCz2MHFZLnsp8t1hZi8cTLTsz+Lo2e25124dZAMOfw9iQRY+IarnG+jZ9kJxxfq WJwkLp4luNjgn8EVm4ITHJrnJxIcGktEvPpHw= MIME-Version: 1.0 Received: by 10.142.214.16 with SMTP id m16mr2501139wfg.218.1303108320014; Sun, 17 Apr 2011 23:32:00 -0700 (PDT) Received: by 10.142.217.5 with HTTP; Sun, 17 Apr 2011 23:31:59 -0700 (PDT) In-Reply-To: <20110316191330.15705.6182.idtracker@localhost> References: <20110316191330.15705.6182.idtracker@localhost> Date: Mon, 18 Apr 2011 08:31:59 +0200 Message-ID: From: Slawomir Testowy To: ietf@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: speechsc@ietf.org Subject: Re: [Speechsc] Last Call: (Media Resource Control Protocol Version 2 (MRCPv2)) to Proposed Standard X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 06:32:07 -0000 Hello, my small comment: The BARGE-IN-OCCURRED method is in few places wrote as BARGE-IN-OCCURED (note missing "R"). I wonder how this could go through all 24 MRCPv2 revisions.... Regards, Slawek Testowy 2011/3/16 The IESG : > > The IESG has received a request from the Speech Services Control WG > (speechsc) to consider the following document: > - 'Media Resource Control Protocol Version 2 (MRCPv2)' > =A0 as a Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2011-04-13. (This allows an additional two > weeks for review since the document is large and the review period overla= ps > the Prague IETF meeting). Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/ > > > > No IPR declarations have been submitted directly on this I-D. > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www.ietf.org/mailman/listinfo/speechsc > Supplemental web site: > <http://www.standardstrack.com/ietf/speechsc> > From slawomir.testowy@gmail.com Mon Apr 18 00:11:00 2011 Return-Path: X-Original-To: speechsc@ietfc.amsl.com Delivered-To: speechsc@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8C9BFE0769; Mon, 18 Apr 2011 00:11:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IwIvlp++rqT7; Mon, 18 Apr 2011 00:10:55 -0700 (PDT) Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by ietfc.amsl.com (Postfix) with ESMTP id 967B6E06C1; Mon, 18 Apr 2011 00:10:55 -0700 (PDT) Received: by pvh1 with SMTP id 1so2688381pvh.31 for ; Mon, 18 Apr 2011 00:10:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xEm/aP+Q4OH4TvbG39/wYEN18UjHhJ6rtbtHyB8eqco=; b=i24bf+oCz4tvU6HZRukvHG2PIpFhSmbRk3NcACZgQOO46f7BMY3Uh235k3gk9gkOm6 AsVu50z7bSZMEkhDRo3Dxp/H2REkJiVMld9MDcmC4D7wyMR7lB6c/WQ5AldU9TSvl5Xr tG33uHbJnr7V/syoy1kGRaEMwxWEBWCXs1ICk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=kr2KqKI58F1i/gMEl0LVvjPENtTcZ0Xho75XJ/knvZUHJKAxgZAROaRfrEm00u+mYC uBwHMV1aoBvwOK+LO6CODJbgqgkNYJ6bMD9u87nb6srT9hInibolJHSFy0LSroz69y50 aMCRAvzHBuRGIWaK8cippwfY6NxGGrbInBi1w= MIME-Version: 1.0 Received: by 10.142.234.18 with SMTP id g18mr2520404wfh.104.1303110653268; Mon, 18 Apr 2011 00:10:53 -0700 (PDT) Received: by 10.142.217.5 with HTTP; Mon, 18 Apr 2011 00:10:53 -0700 (PDT) In-Reply-To: <20110316191330.15705.6182.idtracker@localhost> References: <20110316191330.15705.6182.idtracker@localhost> Date: Mon, 18 Apr 2011 09:10:53 +0200 Message-ID: From: Slawomir Testowy To: ietf@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: speechsc@ietf.org Subject: Re: [Speechsc] Last Call: (Media Resource Control Protocol Version 2 (MRCPv2)) to Proposed Standard X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 07:11:00 -0000 Hi! Some other comments: > 4.2. Managing Resource Control Channels > When the client wants to add a media processing resource to the > session, it issues a SIP re-INVITE transaction. Is it possible to allocate more than one resource of the same type during one SIP dialog? Example in 4.2 shows how to allocate synthesizer and recognizer, but does not specify if there may be e.g. more than one synthesizer. >6.2.9. Content-Encoding > > > The content-encoding entity-header is used as a modifier to the > media-type. When present, its value indicates what additional > content encoding has been applied to the entity-body, and thus what > decoding mechanisms must be applied in order to obtain the media-type > referenced by the content-type header field. Content-encoding is > primarily used to allow a document to be compressed without losing > the identity of its underlying media type. Note that the SDP session > can be used to determine accepted encodings (see Section 7). This > header field MAY occur on all messages. Section 7 describes usage of OPTIONS method of SIP and Accept-Encoding header is returned by SIP response, not SDP answer, so I guess "Note that the SDP session can be used" should be changed to "Note that the SIP session can be used". > When a CONTROL request to jump backward is issued to a currently > speaking synthesizer resource, and the target jump point is before > the start of the current "SPEAK" request, the current "SPEAK" request > MUST restart from the beginning of its speech data and the response > to the CONTROL request MUST contain this header field with a value of > "true" indicating a restart. Why sometimes requests are surrounded by quotation marks (like "SPEAK") and sometimes not (like CONTROL request)? This happens through all the specification. This may be a minor nit, but makes the whole paper look like= a "draft" :) > 8.4.7. Prosody-Parameters > The prosody parameter headers in the "SET-PARAMS" or "SPEAK" request > only apply if the speech data is of type text/plain and does not use > a speech markup format. Why is it so? Why it is not true for Voice-Parameters? Is it true for CONTROL (i.e. current SPEAK must be text/plain)? Specification does not say anything about it. > 8.4.16. Load-Lexicon > > > This header field is used to indicate whether a lexicon has to be > loaded or unloaded. The default value for this header field is > "true". This header field MAY be specified in a DEFINE-LEXICON > method. I propose rewording this paragraph to explicilty state that "true" means "load lexicon" and "false" means "unload lexicon". Thanks. Slawek Testowy 2011/3/16 The IESG : > > The IESG has received a request from the Speech Services Control WG > (speechsc) to consider the following document: > - 'Media Resource Control Protocol Version 2 (MRCPv2)' > =A0 as a Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2011-04-13. (This allows an additional two > weeks for review since the document is large and the review period overla= ps > the Prague IETF meeting). Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-speechsc-mrcpv2/ > > > > No IPR declarations have been submitted directly on this I-D. > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www.ietf.org/mailman/listinfo/speechsc > Supplemental web site: > <http://www.standardstrack.com/ietf/speechsc> > From eburger@standardstrack.com Mon Apr 18 07:59:48 2011 Return-Path: X-Original-To: speechsc@ietfc.amsl.com Delivered-To: speechsc@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 86B87E068E for ; Mon, 18 Apr 2011 07:59:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.398 X-Spam-Level: X-Spam-Status: No, score=-101.398 tagged_above=-999 required=5 tests=[AWL=-1.199, BAYES_00=-2.599, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7p4Ij8W0COBv for ; Mon, 18 Apr 2011 07:59:47 -0700 (PDT) Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [66.117.3.189]) by ietfc.amsl.com (Postfix) with ESMTP id 72205E0712 for ; Mon, 18 Apr 2011 07:59:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=standardstrack.com; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Message-Id:References:To:X-Mailer; b=Xa8KG6Y+FyppI5t2ao20Z05xWSY7zUr5d11zfi7OoXPA2DfZFR7r6r0us8RcfVF/G6RBhWjvKqPNTopxFfTIoZhA6FsIcNdc7pSNxuZtxfe7vIKo58Eb7eqAgJYDJ+V/; Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.171]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1QBpuJ-0007P6-5i; Mon, 18 Apr 2011 07:58:32 -0700 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/signed; boundary=Apple-Mail-37-561550427; protocol="application/pkcs7-signature"; micalg=sha1 From: Eric Burger In-Reply-To: Date: Mon, 18 Apr 2011 10:59:41 -0400 Message-Id: <313BB3E0-0BC7-464A-BDE9-EE7F5CA24F35@standardstrack.com> References: To: "Wyss, Felix" X-Mailer: Apple Mail (2.1084) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - standardstrack.com Cc: "speechsc@ietf.org" Subject: Re: [Speechsc] MRCP and mixed IPv4/IPv6 environments X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2011 14:59:48 -0000 --Apple-Mail-37-561550427 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This is a really good point. Especially in light of IPv4 exhaustion, = IPv6 should be on everybody's mind. That said, while it would be extremely helpful to have IPv6 examples in = the published RFC, I am not sure the MRCPv2 document under-specifies = IPv6 use. Moreover, the speechsc work group will not be the place to = work out SDP IPv6 issues. The good news is according to the SIPit 24 = report, almost 70% of implementations came with IPv6 SIP stacks, so we = are well on our way to proving interoperability. Especially since IETF Last Call completed last week, I would offer that = IPv6 examples could be a great follow-on Informational draft, if people = would like to work on it. On Apr 17, 2011, at 1:09 AM, Wyss, Felix wrote: > The examples in the most recent draft = (draft-ietf-speechsc-mrcpv2-24.txt) use only IPv4 address types. There = is no mention of IPv6, let alone how MRCP should be used in mixed = IPv4/IPv6 environments. I think that should be addressed in the RFC, at = a minimum with some examples and/or discussion to provide guidance to = implementers. This seems especially important as the introduction of = the "a=3Dcmid" co-media attribute adds another dimension to the media = negotiation.=20 > =20 > As an example, I took a synthesizer sample from the current draft and = tried to come up with an offer/answer exchange in a mixed environment = with alternate address type semantics (RFC#4091). I am assuming here = that the offerer allows the answerer to accept a different address type = for MRCP and RTP by listing both stream identifiers of the IP4 and IP6 = RTP streams as two separate "a=3Dcmid" attributes. Thus, the answerer = could elect to use IPv6 for MRCP and IPv4 for RTP:=20 > =20 > =20 > Offer: > =20 > v=3D0 > o=3Dsarvi 2890844526 2890844526 IN IP6 2001:DB8::4 > s=3D- > a=3Dgroup:ANAT 1 2 > a=3Dgroup:ANAT 3 4 > m=3Dapplication 9 TCP/MRCPv2 1 > c=3DIN IP4 192.0.2.12 > a=3Dsetup:active > a=3Dconnection:new > a=3Dresource:speechsynth > a=3Dcmid:3 > a=3Dcmid:4 > a=3Dmid:1 > m=3Dapplication 9 TCP/MRCPv2 1 > c=3DIN IP6 2001:DB8::1 > a=3Dsetup:active > a=3Dconnection:new > a=3Dresource:speechsynth > a=3Dcmid:3 > a=3Dcmid:4 > a=3Dmid:2 > m=3Daudio 49170 RTP/AVP 0 > c=3DIN IP4 192.0.2.12 > a=3Drtpmap:0 pcmu/8000 > a=3Drecvonly > a=3Dmid:3 > m=3Daudio 49170 RTP/AVP 0 > c=3DIN IP6 2001:DB8::1 > a=3Drtpmap:0 pcmu/8000 > a=3Drecvonly > a=3Dmid:4 > =20 > =20 > Example Answer 1 (IPv6 for MRCP, IPv6 for RTP): > =20 > v=3D0 > o=3D 2890842808 2890842808 IN IP6 2001:DB8::5 > s=3D- > m=3Dapplication 0 TCP/MRCPv2 1 > c=3DIN IP4 0.0.0.0 > a=3Dmid:1 > m=3Dapplication 32416 TCP/MRCPv2 1 > c=3DIN IP6 2001:DB8::2 > a=3Dsetup:passive > a=3Dconnection:new > a=3Dchannel:32AECB234338@speechsynth > a=3Dcmid:4 > a=3Dmid:2 > m=3Daudio 0 RTP/AVP 0 > c=3DIN IP4 0.0.0.0 > a=3Dmid:3 > m=3Daudio 48260 RTP/AVP 0 > c=3DIN IP6 IN IP6 2001:DB8::2 > a=3Drtpmap:0 pcmu/8000 > a=3Dsendonly > a=3Dmid:4 > =20 > =20 > Example Answer 2 (IPv6 for MRCP, IPv4 for RTP): > =20 > v=3D0 > o=3D 2890842808 2890842808 IN IP6 2001:DB8::5 > s=3D- > m=3Dapplication 0 TCP/MRCPv2 1 > c=3DIN IP4 0.0.0.0 > a=3Dmid:1 > m=3Dapplication 32416 TCP/MRCPv2 1 > c=3DIN IP6 2001:DB8::2 > a=3Dsetup:passive > a=3Dconnection:new > a=3Dchannel:32AECB234338@speechsynth > a=3Dcmid:3 > a=3Dmid:2 > m=3Daudio 48260 RTP/AVP 0 > c=3DIN IP4 192.0.2.11 > a=3Drtpmap:0 pcmu/8000 > a=3Dsendonly > a=3Dmid:3 > m=3Daudio 0 RTP/AVP 0 > c=3DIN IP6 :: > a=3Dmid:4 > =20 > =20 > Does that seem like an appropriate interpretation? =20 > =20 > Thanks, > Felix Wyss > Interactive Intelligence, Inc. > =20 > _______________________________________________ > Speechsc mailing list > Speechsc@ietf.org > https://www.ietf.org/mailman/listinfo/speechsc > Supplemental web site: > <http://www.standardstrack.com/ietf/speechsc> --Apple-Mail-37-561550427 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILHzCCBN0w ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8 om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59 MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8 NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggY6MIIFIqAD AgECAhEAxcM7lN0zgrA71mfq+sG6xjANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVU Ti1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMDA5MDgwMDAw MDBaFw0xMTA5MDgyMzU5NTlaMIHhMTUwMwYDVQQLEyxDb21vZG8gVHJ1c3QgTmV0d29yayAtIFBF UlNPTkEgTk9UIFZBTElEQVRFRDFGMEQGA1UECxM9VGVybXMgYW5kIENvbmRpdGlvbnMgb2YgdXNl OiBodHRwOi8vd3d3LmNvbW9kby5uZXQvcmVwb3NpdG9yeTEfMB0GA1UECxMWKGMpMjAwMyBDb21v ZG8gTGltaXRlZDEUMBIGA1UEAxMLRXJpYyBCdXJnZXIxKTAnBgkqhkiG9w0BCQEWGmVidXJnZXJA c3RhbmRhcmRzdHJhY2suY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqeauFkEq 5Pj7AIAaDRbUWIpoblTKyrjcSfXRaHvjk0jWBTsBPe6oOZjudMK0Vo9A1Sl52BixDgf1/qb2Z+PT 7M0mqSOOsSucEBid48IMvGi79xmKKAVf5jiyFNNAaTZWn76dwNLMkKd/+Ki0fn8kEbb2zG+gGKyZ MNHiNX+GQfPpHyzo2MTwnb16lXMfGJrGv4uLZS/pY9PENdFQnwV0ASZoqX+ArtLY2xeuC+rYG9xQ Cz7qiLbJhCJzWsEGETyHLDjE5bN4HB9DsJKtGFLQuOdTanwGigNz9cVH9pLFNQxiotavAouXgqS4 wGvcq4mGP9w9zTychoUqIKsEg9OD1wIDAQABo4ICHDCCAhgwHwYDVR0jBBgwFoAUiYJnfcSdJnAA S7RQSHzePa4Ebn0wHQYDVR0OBBYEFAlgEOVj6Hl0La8sPRP388HEMiWvMA4GA1UdDwEB/wQEAwIF oDAMBgNVHRMBAf8EAjAAMCAGA1UdJQQZMBcGCCsGAQUFBwMEBgsrBgEEAbIxAQMFAjARBglghkgB hvhCAQEEBAMCBSAwRgYDVR0gBD8wPTA7BgwrBgEEAbIxAQIBAQEwKzApBggrBgEFBQcCARYdaHR0 cHM6Ly9zZWN1cmUuY29tb2RvLm5ldC9DUFMwgaUGA1UdHwSBnTCBmjBMoEqgSIZGaHR0cDovL2Ny bC5jb21vZG9jYS5jb20vVVROLVVTRVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWls LmNybDBKoEigRoZEaHR0cDovL2NybC5jb21vZG8ubmV0L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0 aGVudGljYXRpb25hbmRFbWFpbC5jcmwwbAYIKwYBBQUHAQEEYDBeMDYGCCsGAQUFBzAChipodHRw Oi8vY3J0LmNvbW9kb2NhLmNvbS9VVE5BQUFDbGllbnRDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6 Ly9vY3NwLmNvbW9kb2NhLmNvbTAlBgNVHREEHjAcgRplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNv bTANBgkqhkiG9w0BAQUFAAOCAQEACRTppSEc5DMYn8YXcbfX36iTaNBGw1gUvTNam0U8pXH0E7H3 2d4cTq6DEMu5ifEvxMGBqhUyv0sKxQ7+UvtDwrk7Kiy2L6TUC4zNEklZbtDqY7+Wd7EQZkN4k/zx kMLlz2VIIRL/Cg48NrBKP5bo1la78NTJx8m4+VForLseEBabxMQoWB/GOVC7WpO/+RCgd93gz6H/ RzW1hnK0Uvu5H3Kz7HEC3R1Qk/sE9nXVzTfoJOMJRnyMS5Ut61mgoWSm/kUtczAlRRYh6IBOhzAl awoXz+yk9hMCheYRAWx0EamBBpSzvqXj0N2vXYc62v3e3ddcLZncjiB0pYIfCE3s4DGCA/8wggP7 AgEBMIHEMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBD aXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cu dXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRp b24gYW5kIEVtYWlsAhEAxcM7lN0zgrA71mfq+sG6xjAJBgUrDgMCGgUAoIICDzAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMTA0MTgxNDU5NDFaMCMGCSqGSIb3DQEJ BDEWBBSaFKwqKit+r02sE/gwUoVxPI8lqjCB1QYJKwYBBAGCNxAEMYHHMIHEMIGuMQswCQYDVQQG EwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUg VVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQG A1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsAhEAxcM7 lN0zgrA71mfq+sG6xjCB1wYLKoZIhvcNAQkQAgsxgceggcQwga4xCzAJBgNVBAYTAlVTMQswCQYD VQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRoZSBVU0VSVFJVU1Qg TmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4t VVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1haWwCEQDFwzuU3TOCsDvWZ+r6 wbrGMA0GCSqGSIb3DQEBAQUABIIBAArqFqsnzhmHJ7hs8wnf/F5JB5kq2wKismSfXxuWoFSjbE7O gNqqPtKMJBmy0eniaSh8EUFKG7AtIOS+N50aWFlZO36x4DKk/4cy7QgQOKZ3to5WVGwCUGhnHVWp ngGjNXehHoz2QC5zk8TwE6g5IBf4jQdfBtf3SbbhKrJcy/bxC8Vd6vgAt9Y2D6F5HNQTRgbfV6fi 6hpO8S/EVp0oWJOnofZQE7gsCBbzv7Q5cwRhSTmzjG7gV7/32/XEKl1kWhArM7TAzAp89r+X+a5Z yxjM1GaM8rYcAEkPs0Rhov6SCFf7j+MXdeBaFJ3/7M5HM2eLhQa7iTP/jluKb3oG3zoAAAAAAAA= --Apple-Mail-37-561550427-- From Felix.Wyss@inin.com Tue Apr 19 22:24:43 2011 Return-Path: X-Original-To: speechsc@ietfc.amsl.com Delivered-To: speechsc@ietfc.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 4A167E0690 for ; Tue, 19 Apr 2011 22:24:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, J_CHICKENPOX_111=0.6, J_CHICKENPOX_12=0.6, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6] Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bOvMkofkf9bA for ; Tue, 19 Apr 2011 22:24:42 -0700 (PDT) Received: from inin.com (smtpgw.inin.com [209.43.1.24]) by ietfc.amsl.com (Postfix) with ESMTP id 3E98AE0670 for ; Tue, 19 Apr 2011 22:24:42 -0700 (PDT) Received: from ININHUB2 [172.16.1.157] by smtpgw.inin.com - Websense Email Security (6.1.1); Wed, 20 Apr 2011 01:24:41 -0400 Received: from ININMAIL.i3domain.inin.com ([172.16.1.186]) by ininhub2.i3domain.inin.com ([172.16.1.157]) with mapi; Wed, 20 Apr 2011 01:24:40 -0400 From: "Wyss, Felix" To: 'Eric Burger' Date: Wed, 20 Apr 2011 01:24:39 -0400 Thread-Topic: [Speechsc] MRCP and mixed IPv4/IPv6 environments Thread-Index: Acv92UNj5W7SJea4TTOMSEAkjodbWAA9dlbg Message-ID: References: <313BB3E0-0BC7-464A-BDE9-EE7F5CA24F35@standardstrack.com> In-Reply-To: <313BB3E0-0BC7-464A-BDE9-EE7F5CA24F35@standardstrack.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1 X-SEF-ZeroHour-RefID: fgs=354985904 X-SEF-Processed: 6_1_1_105__2011_04_20_01_24_41 Cc: "speechsc@ietf.org" Subject: Re: [Speechsc] MRCP and mixed IPv4/IPv6 environments X-BeenThere: speechsc@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Speech Services Control Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2011 05:24:43 -0000 Hi Eric, It may be true that the IPv6 dependent parts of MRCP depend on other RFCs, = but I fear there will invariably be ambiguities that implementers will have= to make judgment calls on. Every time this happens, the likelihood of int= eroperability issues increases. As this RFC introduces new SDP attributes,= I think it makes sense to proactively identify cases where there may be a = particular risk for impedance mismatches and addressing them with examples = and/or some prose -- even if non-normative. =20 I feel the "a=3Dcmid" attribute in particular has potential for such ambigu= ities and think mixed IPv4/IPv6 environments are an area that could benefit= from guidance. At a minimum this will ensure implementers are aware that = there may be additional aspects to consider.=20 Thanks, --Felix > -----Original Message----- > From: Eric Burger [mailto:eburger@standardstrack.com] > Sent: Monday, April 18, 2011 11:00 > To: Wyss, Felix > Cc: speechsc@ietf.org > Subject: Re: [Speechsc] MRCP and mixed IPv4/IPv6 environments >=20 > This is a really good point. Especially in light of IPv4 exhaustion, IPv= 6 > should be on everybody's mind. >=20 > That said, while it would be extremely helpful to have IPv6 examples in > the published RFC, I am not sure the MRCPv2 document under-specifies IPv6 > use. Moreover, the speechsc work group will not be the place to work out > SDP IPv6 issues. The good news is according to the SIPit 24 report, > almost 70% of implementations came with IPv6 SIP stacks, so we are well o= n > our way to proving interoperability. >=20 > Especially since IETF Last Call completed last week, I would offer that > IPv6 examples could be a great follow-on Informational draft, if people > would like to work on it. >=20 >=20 > On Apr 17, 2011, at 1:09 AM, Wyss, Felix wrote: >=20 > > The examples in the most recent draft (draft-ietf-speechsc-mrcpv2- > 24.txt) use only IPv4 address types. There is no mention of IPv6, let > alone how MRCP should be used in mixed IPv4/IPv6 environments. I think > that should be addressed in the RFC, at a minimum with some examples > and/or discussion to provide guidance to implementers. This seems > especially important as the introduction of the "a=3Dcmid" co-media > attribute adds another dimension to the media negotiation. > > > > As an example, I took a synthesizer sample from the current draft and > tried to come up with an offer/answer exchange in a mixed environment wit= h > alternate address type semantics (RFC#4091). I am assuming here that the > offerer allows the answerer to accept a different address type for MRCP > and RTP by listing both stream identifiers of the IP4 and IP6 RTP streams > as two separate "a=3Dcmid" attributes. Thus, the answerer could elect to > use IPv6 for MRCP and IPv4 for RTP: > > > > > > Offer: > > > > v=3D0 > > o=3Dsarvi 2890844526 2890844526 IN IP6 2001:DB8::4 > > s=3D- > > a=3Dgroup:ANAT 1 2 > > a=3Dgroup:ANAT 3 4 > > m=3Dapplication 9 TCP/MRCPv2 1 > > c=3DIN IP4 192.0.2.12 > > a=3Dsetup:active > > a=3Dconnection:new > > a=3Dresource:speechsynth > > a=3Dcmid:3 > > a=3Dcmid:4 > > a=3Dmid:1 > > m=3Dapplication 9 TCP/MRCPv2 1 > > c=3DIN IP6 2001:DB8::1 > > a=3Dsetup:active > > a=3Dconnection:new > > a=3Dresource:speechsynth > > a=3Dcmid:3 > > a=3Dcmid:4 > > a=3Dmid:2 > > m=3Daudio 49170 RTP/AVP 0 > > c=3DIN IP4 192.0.2.12 > > a=3Drtpmap:0 pcmu/8000 > > a=3Drecvonly > > a=3Dmid:3 > > m=3Daudio 49170 RTP/AVP 0 > > c=3DIN IP6 2001:DB8::1 > > a=3Drtpmap:0 pcmu/8000 > > a=3Drecvonly > > a=3Dmid:4 > > > > > > Example Answer 1 (IPv6 for MRCP, IPv6 for RTP): > > > > v=3D0 > > o=3D 2890842808 2890842808 IN IP6 2001:DB8::5 > > s=3D- > > m=3Dapplication 0 TCP/MRCPv2 1 > > c=3DIN IP4 0.0.0.0 > > a=3Dmid:1 > > m=3Dapplication 32416 TCP/MRCPv2 1 > > c=3DIN IP6 2001:DB8::2 > > a=3Dsetup:passive > > a=3Dconnection:new > > a=3Dchannel:32AECB234338@speechsynth > > a=3Dcmid:4 > > a=3Dmid:2 > > m=3Daudio 0 RTP/AVP 0 > > c=3DIN IP4 0.0.0.0 > > a=3Dmid:3 > > m=3Daudio 48260 RTP/AVP 0 > > c=3DIN IP6 IN IP6 2001:DB8::2 > > a=3Drtpmap:0 pcmu/8000 > > a=3Dsendonly > > a=3Dmid:4 > > > > > > Example Answer 2 (IPv6 for MRCP, IPv4 for RTP): > > > > v=3D0 > > o=3D 2890842808 2890842808 IN IP6 2001:DB8::5 > > s=3D- > > m=3Dapplication 0 TCP/MRCPv2 1 > > c=3DIN IP4 0.0.0.0 > > a=3Dmid:1 > > m=3Dapplication 32416 TCP/MRCPv2 1 > > c=3DIN IP6 2001:DB8::2 > > a=3Dsetup:passive > > a=3Dconnection:new > > a=3Dchannel:32AECB234338@speechsynth > > a=3Dcmid:3 > > a=3Dmid:2 > > m=3Daudio 48260 RTP/AVP 0 > > c=3DIN IP4 192.0.2.11 > > a=3Drtpmap:0 pcmu/8000 > > a=3Dsendonly > > a=3Dmid:3 > > m=3Daudio 0 RTP/AVP 0 > > c=3DIN IP6 :: > > a=3Dmid:4 > > > > > > Does that seem like an appropriate interpretation? > > > > Thanks, > > Felix Wyss > > Interactive Intelligence, Inc. > > > > _______________________________________________ > > Speechsc mailing list > > Speechsc@ietf.org > > https://www.ietf.org/mailman/listinfo/speechsc > > Supplemental web site: > > <http://www.standardstrack.com/ietf/speechsc>