Re: [MMUSIC] Last Call: <draft-ietf-mmusic-rfc4566bis-34.txt> (SDP: Session Description Protocol) to Proposed Standard

"Roni Even (A)" <> Thu, 11 April 2019 10:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 039251202B9; Thu, 11 Apr 2019 03:05:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id yOrEit117gDo; Thu, 11 Apr 2019 03:05:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 625651200F1; Thu, 11 Apr 2019 03:05:04 -0700 (PDT)
Received: from (unknown []) by Forcepoint Email with ESMTP id 8DC0A5AEF1168462050B; Thu, 11 Apr 2019 11:05:02 +0100 (IST)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 11 Apr 2019 11:05:02 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Thu, 11 Apr 2019 11:05:02 +0100
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Thu, 11 Apr 2019 11:05:01 +0100
Received: from ([]) by ([]) with mapi id 14.03.0415.000; Thu, 11 Apr 2019 18:04:41 +0800
From: "Roni Even (A)" <>
To: Magnus Westerlund <>, "" <>
CC: "" <>, "" <>, "" <>
Thread-Topic: [MMUSIC] Last Call: <draft-ietf-mmusic-rfc4566bis-34.txt> (SDP: Session Description Protocol) to Proposed Standard
Thread-Index: AQHU4L35G0bkeH37hEyuzO/M/jMwpKY22TWQ
Date: Thu, 11 Apr 2019 10:04:41 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD18CDB636dggemm526mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <>
Subject: Re: [MMUSIC] Last Call: <draft-ietf-mmusic-rfc4566bis-34.txt> (SDP: Session Description Protocol) to Proposed Standard
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Apr 2019 10:05:07 -0000

Hi Magnus,
I think it will affect the IANA registries where values may be shared with non SDP attribute. For example the sub-protocol in the IANA WebSocket Subprotocol name registry

Roni Even

From: mmusic [] On Behalf Of Magnus Westerlund
Sent: Thursday, April 11, 2019 11:14 AM
Subject: Re: [MMUSIC] Last Call: <draft-ietf-mmusic-rfc4566bis-34.txt> (SDP: Session Description Protocol) to Proposed Standard

MMUSIC WG, Document Editors

In the processing of draft-ietf-mmusic-data-channel-sdpneg-25 an interesting question arose regarding text strings in SDP attribute values.

Currently the document says:

4.5.  Internationalization

   The SDP specification recommends the use of the ISO 10646 character

   set in the UTF-8 encoding [RFC3629] to allow many different languages

   to be represented.  However, to assist in compact representations,

   SDP also allows other character sets such as ISO 8859-1 to be used

   when desired.  Internationalization only applies to free-text sub-

   fields (session name and background information), and not to SDP as a


If one like to include UTF-8 field for attributes it would be good if

the requirement would be clear going forward that there is an expectancy

that at least parser can process any UTF-8 strings that may occur in any


That would allow future SDP field values to use UTF-8 strings without risks

and simplify processing. Like in the case of the data channel SDP mapping

where the extra step of encoding lable characters not visually safe as escaped

characters could be avoided.

Does anyone have input if making such a change would have significant impact on

the interoperability?



On 2019-03-22 15:46, The IESG wrote:

The IESG has received a request from the Multiparty Multimedia Session

Control WG (mmusic) to consider the following document: - 'SDP: Session

Description Protocol'

  <draft-ietf-mmusic-rfc4566bis-34.txt> as 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<> mailing lists by 2019-04-12. Exceptionally, comments may be

sent to<> instead. In either case, please retain the beginning of

the Subject line to allow automated sorting.


   This memo defines the Session Description Protocol (SDP).  SDP is

   intended for describing multimedia sessions for the purposes of

   session announcement, session invitation, and other forms of

   multimedia session initiation.  This document obsoletes RFC 4566.

The file can be obtained via

IESG discussion can be tracked via

No IPR declarations have been submitted directly on this I-D.


mmusic mailing list<>


Magnus Westerlund


Network Architecture & Protocols, Ericsson Research


Ericsson AB                 | Phone  +46 10 7148287

Torshamnsgatan 23           | Mobile +46 73 0949079

SE-164 80 Stockholm, Sweden | mailto:<>