IETF Logo Mail Archive

Re: [MMUSIC] ICE SDP extension-att-name in ICE candidate

Jonathan Lennox <jonathan@vidyo.com> Fri, 02 December 2016 16:19 UTC

Return-Path: <prvs=614405f391=jonathan@vidyo.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC2B412951C for <mmusic@ietfa.amsl.com>; Fri, 2 Dec 2016 08:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.995
X-Spam-Level:
X-Spam-Status: No, score=0.995 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=3.595, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNBPp_R11rjC for <mmusic@ietfa.amsl.com>; Fri, 2 Dec 2016 08:19:41 -0800 (PST)
Received: from mx0b-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59009129636 for <mmusic@ietf.org>; Fri, 2 Dec 2016 08:19:41 -0800 (PST)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id uB2GJFw9010467; Fri, 2 Dec 2016 11:19:37 -0500
Received: from mail.vidyo.com ([162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 26y4cpeyhb-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Fri, 02 Dec 2016 11:19:37 -0500
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Fri, 2 Dec 2016 10:19:35 -0600
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [MMUSIC] ICE SDP extension-att-name in ICE candidate
Thread-Index: AQHSTLbOWPqAH1jMTkO6OYGLldQJ96D01KE8gABmRIA=
Date: Fri, 02 Dec 2016 16:19:35 +0000
Message-ID: <7CD3C8C3-BD3E-490D-ADFD-537D0E2EC109@vidyo.com>
References: <CAD5OKxs=RbCvafdm2v4hRjfcQQyBPSdzOpnVAs8=9HshuJ1Odg@mail.gmail.com> <87fum7vzok.fsf@hobgoblin.ariadne.com> <CAD5OKxtGnyNonm3wH7eM_j4SLabmMGhZ1x+UzrfexzFEpsTDaQ@mail.gmail.com>
In-Reply-To: <CAD5OKxtGnyNonm3wH7eM_j4SLabmMGhZ1x+UzrfexzFEpsTDaQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [160.79.219.114]
Content-Type: multipart/alternative; boundary="_000_7CD3C8C3BD3E490DADFD537D0E2EC109vidyocom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-12-02_12:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1609300000 definitions=main-1612020253
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/vgTyBSYEexdEPPQzUnKzXN4pKh4>
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE SDP extension-att-name in ICE candidate
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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 Dec 2016 16:19:43 -0000

On Dec 1, 2016, at 11:44 PM, Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> wrote:


Should we add the registry for these values? Also, should some language be added on how unsupported ice candidate attributes are handled?

5245, and ice-sip-sdp, already says

   The candidate attribute can itself be extended.  The grammar allows
   for new name/value pairs to be added at the end of the attribute.  An
   implementation MUST ignore any name/value pairs it doesn't
   understand.

which I think is fine.

But I agree that an IANA registry for these is probably a good idea.

Note that in addition to the attributes you listed, I also see Chrome sending “network-cost” in its JSEP.  This is presumably draft-thatcher-ice-network-cost.

Roman Shpount

On Dec 1, 2016 9:21 PM, "Dale R. Worley" <worley@ariadne.com<mailto:worley@ariadne.com>> wrote:
Roman Shpount <roman@telurix.com<mailto:roman@telurix.com>> writes:
> Is there a registry for ICE extension-att-name? How does one looks up
> where extension-att-name
> is defined, what it means, and how it is used? Are there any rules
> associated with ICE candidate extensions?
>
> As far as I know there are two extension attributes that are commonly used:
> "generation" and "network" but I am not sure where these values and their
> usage are defined.

There is no registry for this extension, as there is none listed under
"Interactive Connectivity Establishment (ICE)" in the IANA protocol
registry.

"extension-att-name" itself is mentioned only in RFC 5245 (ICE) and RFC
6544 (ICE over TCP).

Dale
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic

v2.23.0 | Report a Bug | By Email