[Speechsc] MRCP and mixed IPv4/IPv6 environments
"Wyss, Felix" <Felix.Wyss@inin.com> Sun, 17 April 2011 05:09 UTC
Return-Path: <Felix.Wyss@inin.com>
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 <speechsc@ietfc.amsl.com>; 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 <speechsc@ietfc.amsl.com>; 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 <speechsc@ietf.org>; 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" <Felix.Wyss@inin.com>
To: "speechsc@ietf.org" <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: <B043FD61A001424599674F50FC89C2D7B3DFF766D5@ININMAIL.i3domain.inin.com>
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 <speechsc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/speechsc>, <mailto:speechsc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/speechsc>
List-Post: <mailto:speechsc@ietf.org>
List-Help: <mailto:speechsc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/speechsc>, <mailto:speechsc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Apr 2011 05:09:18 -0000
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=cmid" 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 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=cmid" attributes. Thus, the answerer could elect to use IPv6 for MRCP and IPv4 for RTP: Offer: v=0 o=sarvi 2890844526 2890844526 IN IP6 2001:DB8::4 s=- a=group:ANAT 1 2 a=group:ANAT 3 4 m=application 9 TCP/MRCPv2 1 c=IN IP4 192.0.2.12 a=setup:active a=connection:new a=resource:speechsynth a=cmid:3 a=cmid:4 a=mid:1 m=application 9 TCP/MRCPv2 1 c=IN IP6 2001:DB8::1 a=setup:active a=connection:new a=resource:speechsynth a=cmid:3 a=cmid:4 a=mid:2 m=audio 49170 RTP/AVP 0 c=IN IP4 192.0.2.12 a=rtpmap:0 pcmu/8000 a=recvonly a=mid:3 m=audio 49170 RTP/AVP 0 c=IN IP6 2001:DB8::1 a=rtpmap:0 pcmu/8000 a=recvonly a=mid:4 Example Answer 1 (IPv6 for MRCP, IPv6 for RTP): v=0 o= 2890842808 2890842808 IN IP6 2001:DB8::5 s=- m=application 0 TCP/MRCPv2 1 c=IN IP4 0.0.0.0 a=mid:1 m=application 32416 TCP/MRCPv2 1 c=IN IP6 2001:DB8::2 a=setup:passive a=connection:new a=channel:32AECB234338@speechsynth a=cmid:4 a=mid:2 m=audio 0 RTP/AVP 0 c=IN IP4 0.0.0.0 a=mid:3 m=audio 48260 RTP/AVP 0 c=IN IP6 IN IP6 2001:DB8::2 a=rtpmap:0 pcmu/8000 a=sendonly a=mid:4 Example Answer 2 (IPv6 for MRCP, IPv4 for RTP): v=0 o= 2890842808 2890842808 IN IP6 2001:DB8::5 s=- m=application 0 TCP/MRCPv2 1 c=IN IP4 0.0.0.0 a=mid:1 m=application 32416 TCP/MRCPv2 1 c=IN IP6 2001:DB8::2 a=setup:passive a=connection:new a=channel:32AECB234338@speechsynth a=cmid:3 a=mid:2 m=audio 48260 RTP/AVP 0 c=IN IP4 192.0.2.11 a=rtpmap:0 pcmu/8000 a=sendonly a=mid:3 m=audio 0 RTP/AVP 0 c=IN IP6 :: a=mid:4 Does that seem like an appropriate interpretation? Thanks, Felix Wyss Interactive Intelligence, Inc.
- [Speechsc] MRCP and mixed IPv4/IPv6 environments Wyss, Felix
- Re: [Speechsc] MRCP and mixed IPv4/IPv6 environme… Eric Burger
- Re: [Speechsc] MRCP and mixed IPv4/IPv6 environme… Wyss, Felix
- Re: [Speechsc] MRCP and mixed IPv4/IPv6 environme… Dan Burnett