Re: [MMUSIC] Data channel dcsa attribute usage and IANA

"Roni Even (A)" <roni.even@huawei.com> Thu, 29 August 2019 09:50 UTC

Return-Path: <roni.even@huawei.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 EE807120273; Thu, 29 Aug 2019 02:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 38tBGHabbhEG; Thu, 29 Aug 2019 02:50:05 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 9E958120145; Thu, 29 Aug 2019 02:50:05 -0700 (PDT)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5C5D8C0F4ABFC99EBC58; Thu, 29 Aug 2019 10:50:03 +0100 (IST)
Received: from lhreml729-chm.china.huawei.com (10.201.108.80) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 29 Aug 2019 10:50:02 +0100
Received: from lhreml729-chm.china.huawei.com (10.201.108.80) by lhreml729-chm.china.huawei.com (10.201.108.80) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Thu, 29 Aug 2019 10:50:02 +0100
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml729-chm.china.huawei.com (10.201.108.80) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Thu, 29 Aug 2019 10:50:02 +0100
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.195]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0439.000; Thu, 29 Aug 2019 17:49:59 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>
CC: "mmusic-chairs@ietf.org" <mmusic-chairs@ietf.org>
Thread-Topic: [MMUSIC] Data channel dcsa attribute usage and IANA
Thread-Index: AQHVXkujg9M91RaR+EiTe/MX9Cr3VacR4OVQ
Date: Thu, 29 Aug 2019 09:49:59 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD23D439E1@dggemm526-mbx.china.huawei.com>
References: <FA58AC4B-B7CF-488A-A287-ACB14C9D9056@ericsson.com>
In-Reply-To: <FA58AC4B-B7CF-488A-A287-ACB14C9D9056@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.60]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD23D439E1dggemm526mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/v8w-ib_lr2GpP6QFkfRRTl0yb1M>
Subject: Re: [MMUSIC] Data channel dcsa attribute usage and IANA
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 29 Aug 2019 09:50:09 -0000

Hi,
I think that dcsa(subprotocol) would have been enough, at least based on channel-sdpneg document, maybe Paul can help

Roni

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Thursday, August 29, 2019 12:25 PM
To: Roni Even (A); mmusic@ietf.org; pkyzivat@alum.mit.edu
Cc: mmusic-chairs@ietf.org
Subject: Re: [MMUSIC] Data channel dcsa attribute usage and IANA

Hi,

One question for clarification:

Section 8.2.4.1 of RFC4566bis says:

      “Usage Level: Usage level(s) of the attribute.  This MUST be one or
      more of the following: session, media, source, dcsa and
      dcsa(subprotocol).”

…and in the Table in Section 8.2.4 it says:

“dcsa,dcsa(msrp)”


Q1: Why does it need to say both ‘dcsa’ and ‘dcsa(subprotocol)’? Isn’t it enough with ‘dcsa(subprotocol)’?

Regards,

Christer



From: mmusic <mmusic-bounces@ietf.org<mailto:mmusic-bounces@ietf.org>> on behalf of Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>
Date: Thursday, 29 August 2019 at 11.27
To: "Roni Even (A)" <roni.even@huawei.com<mailto:roni.even@huawei.com>>, "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Cc: "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>
Subject: Re: [MMUSIC] Data channel dcsa attribute usage and IANA

Hi,

Thanks for the information! The last paragraph clarifies it.

So, draft-t140-usage-data-channel will update the IANA registry for the SDP attributes used inside the SDP dcsa attribute.

Regards,

Christer


From: "Roni Even (A)" <roni.even@huawei.com<mailto:roni.even@huawei.com>>
Date: Thursday, 29 August 2019 at 11.08
To: Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>>, "mmusic@ietf.org<mailto:mmusic@ietf.org>" <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Cc: "mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>" <mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>>
Subject: RE: Data channel dcsa attribute usage and IANA

Hi Christer,
To add to Paul’s response
Look at the last 2 paragraphs of section 5.2.1   https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-28#section-5.2.1

Roni

From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: Wednesday, August 28, 2019 1:33 PM
To: mmusic@ietf.org<mailto:mmusic@ietf.org>
Cc: mmusic-chairs@ietf.org<mailto:mmusic-chairs@ietf.org>
Subject: [MMUSIC] Data channel dcsa attribute usage and IANA

Hi,

Section 7.2 of draft-ietf-mmusic-msrp-usage-data-channel updates the IANA registry for the SDP ‘setup’ attribute, by indicating that it can be used inside an SDP ‘dcsa’ attribute.

Do we really need to update the IANA registry for all SDP attributes that can be included in an ‘dcsa’ attribute???

There is no text in draft-mmusic-data-channel-neg about having to modify the IANA registry for such attributes.

Regards,

Christer