Re: [MMUSIC] JSEP Issue #394: What appears in m= lines.

Roman Shpount <> Tue, 10 January 2017 18:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 944C1129D6B for <>; Tue, 10 Jan 2017 10:08:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id aafj5Dyha5zS for <>; Tue, 10 Jan 2017 10:08:10 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 52365129D65 for <>; Tue, 10 Jan 2017 10:08:10 -0800 (PST)
Received: by with SMTP id x49so107023391qtc.2 for <>; Tue, 10 Jan 2017 10:08:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GQXpkeSzjdZhAHHpGb8L0Wpv208N7sQwY1AKLQwa4Vg=; b=gObhM05ZQ/HhxTaYbCpx0AfsSmzzeepXtUUkUrkHgl62t0yRI9AV6szuVhLVgTWEG9 RssZ4NQsqUKu3saOoBgXu9By5muFbRl3gAH6MZU4z/BCjLGB9viwerEtJJF59J2gO3n9 UNjVV0l3cS6jl68cNPgIHj43O712mAZIwudMjYgl9sSdrbKEUicC4nm+qgCPUMoRp/Uy wZzZVFMWeQT/rzOWU9ScfwdS/C3SimzBNV/epL7SsPpoxaBqeyUq9ES1tgJ5B7c6qqyQ aVZKz3ji6vQayORtPXHVcufGt30GG2kRXrQqY8QyR0I7OdwoiOQBncCJH1B6glJgnYfO dtfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GQXpkeSzjdZhAHHpGb8L0Wpv208N7sQwY1AKLQwa4Vg=; b=LPFnFGgYH21KSBjuvA2ODGtuOfWgQuQ4MRnVUyZszzsznSs7YtyuGt5BaTSifgcKft 8zl5Xlq9Vvc0vJCcN6UBldrqzAETfhyYXdARSHIF9svM8FhH+/7Qb9hfjQDrQzVoyHjE V1KPezL5lWk/JUvSEZPfFfexzuaJpqPdpf4qleypyv7Zs+sMY2+AdcAmJRp2pye8ibTt oWa+z/4lpmf+/wRaFRlv6+acQhisPl8Lhxwd9J3Q2DGW8vSSMv7VWB80f2CWyKRd/68D W4ttem073vOxbAg7z9RhOgmiapai3h6HMmYEXrOxZBM23I4CYuV6ky2j06EDaKFAafKn RA6Q==
X-Gm-Message-State: AIkVDXKM/KL89LKZcZtYSirWxw9nDZP4Ml4ANwOtr/Ske9wNF3K91mEZTfvsXn5E88OifA==
X-Received: by with SMTP id v47mr3802298qtc.126.1484071689266; Tue, 10 Jan 2017 10:08:09 -0800 (PST)
Received: from ( []) by with ESMTPSA id r15sm1987906qte.9.2017. for <> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Jan 2017 10:08:09 -0800 (PST)
Received: by with SMTP id 11so84493648qkl.3 for <>; Tue, 10 Jan 2017 10:08:08 -0800 (PST)
X-Received: by with SMTP id k20mr3963099qkl.34.1484071688427; Tue, 10 Jan 2017 10:08:08 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Tue, 10 Jan 2017 10:08:07 -0800 (PST)
In-Reply-To: <>
References: <> <> <> <> <>
From: Roman Shpount <>
Date: Tue, 10 Jan 2017 13:08:07 -0500
X-Gmail-Original-Message-ID: <>
Message-ID: <>
To: Paul Kyzivat <>
Content-Type: multipart/alternative; boundary=001a1149e640cf636b0545c15db7
Archived-At: <>
Cc: "" <>
Subject: Re: [MMUSIC] JSEP Issue #394: What appears in m= lines.
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 10 Jan 2017 18:08:11 -0000

We can do the registration for ICE transport tag in ICE-SIP-SDP. ICE tag
will indicate that ICE is required for this offer/answer exchange to
succeed. When ICE transport tag is used, c= and m= SDP line would carry no
address information and will contain "c=IN IP4" and port 9 in the
m= line. Also, if ICE/ transport tag is used, we should remove the
requirement for a re-INVITE after ICE nomination process is complete, since
it serves no purpose when no address is specified in c= and m= lines.

If we are not going to define ICE/ transport, then I propose the following:

1. When c= line is set to "IN IP4" and m= line is set to port 9, so
that these lines carry no valid address information as it is specified in
JSEP, protocol should be UDP/DTLS/SAVPF for RTP or UDP/DTLS/SCTP for data

2. When c= line and m= line carry valid address information, protocol
should match the candidate specified in c= and m= lines.

3. In cases when c= line and m= line carry valid address information, when
initial offer and answer are generated, they must include UDP candidates
and UDP candidates must be used as defaults. Once ICE nomination process is
complete, only the active candidate pair MUST be included in SDP, and the
transport for the active pair must be used.

I am not sure about the proper procedure for c= and m= lines during the ICE
nomination process, since active candidate can change during the
offer/answer exchange which can cause protocol line mismatch. One option is
to continue re-sending the initial offer and answer.

P.S. In the quoted text someone mentioned "UDP/TLS/RTP/SAVPF", should it be

Roman Shpount