
From nobody Wed Nov 21 14:33:41 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: bfcpbis@ietf.org
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AE7128BCC; Wed, 21 Nov 2018 14:33:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Eric Rescorla <ekr@rtfm.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-bfcpbis-rfc4583bis@ietf.org, bfcpbis-chairs@ietf.org, mary.ietf.barnes@gmail.com, bfcpbis@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154283961859.5506.3702552585345849896.idtracker@ietfa.amsl.com>
Date: Wed, 21 Nov 2018 14:33:38 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/hvkp3n7G5tNU-dBChaK49k3YdqE>
Subject: [bfcpbis] Eric Rescorla's No Objection on draft-ietf-bfcpbis-rfc4583bis-26: (with COMMENT)
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2018 22:33:39 -0000

Eric Rescorla has entered the following ballot position for
draft-ietf-bfcpbis-rfc4583bis-26: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-rfc4583bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Based on Adam's comments, I am changing my DISCUSS to No Objection



From nobody Tue Nov 27 14:46:56 2018
Return-Path: <ben@nostrum.com>
X-Original-To: bfcpbis@ietf.org
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CDF5130E2B; Tue, 27 Nov 2018 14:46:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Ben Campbell <ben@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-bfcpbis-rfc4583bis@ietf.org, bfcpbis-chairs@ietf.org, mary.ietf.barnes@gmail.com, bfcpbis@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.89.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154335879450.11879.649292566270100300.idtracker@ietfa.amsl.com>
Date: Tue, 27 Nov 2018 14:46:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/FtDS95laRmmUBlW_XUmjJPlySW8>
Subject: [bfcpbis] Ben Campbell's Discuss on draft-ietf-bfcpbis-rfc4583bis-26: (with DISCUSS and COMMENT)
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2018 22:46:45 -0000

Ben Campbell has entered the following ballot position for
draft-ietf-bfcpbis-rfc4583bis-26: Discuss

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bfcpbis-rfc4583bis/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------


The category assignments in this draft do not match the existing assignments in
mux-attributes, which marks "floorctrl" as "TBD", and the others as "NORMAL".
This draft marks all attributes as "TBD".


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

The following point was part of my DISCUSS position. Since the problem seems
broader than for just this draft,  I won't hold the draft hostage to it's
solution. But I hope we can find a cleaner approach in general:

<old-discuss-point>

This document lists all the SDP attributes as having an a Mux Category of
"TBD". draft-ietf-mmusic-sdp-mux-attributes did indeed assign a category of
"TBD" to all the attributes, save for bfcpver, which didn't exist at the time.
But the point of "TBD" was to say that draft-ietf-mmusic-sdp-mux-attributes did
not actually analyze the attributes to determine a "real" mux category. It's
not intended as free pass to let other attribute definitions skip that analysis.

Ideally, I think that this draft should assign a "real" mux category for each
attribute in it. Failing that, it at least needs to do so for "bfcpver". I'm
guessing that should be "caution" or "special". (Perhaps unfortunately,
draft-ietf-mmusic-sdp-mux-attributes did not define a category of "nope" :-) )

Update: After a bit of discussion and a re-read of
draft-ietf-mmusic-sdp-mux-attributes, I see that, while the use of "TBD" does
not seem consistent with the definition of TBD, it does seem consistent with
the practice in mux-attributes of assigning a category of TBD to attributes
associated with non-muxable protocols. I've sent an email to the MMUSIC WG for
guidance on the intended use.

</old-discuss-point>

*** Substantive Comments ***

§4: "The fmt (format) list is not applicable to BFCP. The fmt list of ’m’
lines in the case of any proto field value related to BFCP MUST
contain a single "*" character. If the the fmt list contains any
other value it is ignored."

It seems like the last sentence should use a MUST to match the one in the
previous sentence.

*** Editorial Comments ***

§3: "Typically, a client that establishes a BFCP
stream with a conference server will act as a floor control client,
while the conference server will act as a floor control server."

The use of "typically" seems odd without a discussion of when it might not.
Perhaps a forward reference to section 7 would help?

§6: "[I-D.ietf-mmusic-sdp-mux-attributes] defines the mux categories for
the SDP attributes defined in this specification. Table 2 defines
the mux category for the ’bfcpver’ attribute:"

I assume the first sentence should say "... except for bfcpver."?

§10, 3rd paragraph: Incorrect comma use in "... SDP), in ..."
§10.1, last paragraph: "... value, in the offer, ...": The first comma is
incorrect. §10.3: First paragraph: "When the offerer receives an answer, which
contains an ’m’ line..." s/ ", which" / "that"

§16.2: It seems like [I-D.ietf-mmusic-sdp-mux-attributes] should be a normative
reference.



From nobody Tue Nov 27 14:48:27 2018
Return-Path: <ben@nostrum.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95C47130DD2; Tue, 27 Nov 2018 14:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 8P5J-PZ9ct9J; Tue, 27 Nov 2018 14:48:06 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98DD9130E81; Tue, 27 Nov 2018 14:48:03 -0800 (PST)
Received: from [10.0.1.24] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wARMlvAP009171 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 27 Nov 2018 16:47:58 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.24]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <F4DA2D8D-B840-4638-AFFE-FEA3C5CF52F4@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A55AED46-3F02-4194-A50E-A3C4375D0816"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Tue, 27 Nov 2018 16:47:57 -0600
In-Reply-To: <95321542-CA94-4345-AD2D-44FFDF43456E@nostrum.com>
Cc: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "draft-ietf-bfcpbis-rfc4583bis.all@ietf.org" <draft-ietf-bfcpbis-rfc4583bis.all@ietf.org>,  "draft-ietf-mmusic-sdp-mux-attributes@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes@ietf.org>,  The IESG <iesg@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
To: "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
References: <6EA38BB6-27E3-44B0-8F04-7EF8C5857BF5@nostrum.com> <B99C9CC6-89F5-4896-90C2-2AA2B8C28A56@cisco.com> <95321542-CA94-4345-AD2D-44FFDF43456E@nostrum.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/0t_rnbb7P1OGsVXob8C5OaVGr0k>
Subject: Re: [bfcpbis] [MMUSIC] Use of the "TBD" Mux Category in bfcpbis.
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Nov 2018 22:48:09 -0000

--Apple-Mail=_A55AED46-3F02-4194-A50E-A3C4375D0816
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Does anyone have further thoughts on this?

> On Oct 24, 2018, at 1:22 PM, Ben Campbell <ben@nostrum.com> wrote:
>=20
> Signed PGP part
> Hi Suhas,
>=20
> As I mentioned, I am not suggesting we add this to the mux-attributes =
draft. My question was, what is the correct category to use for a new =
attribute associated with a non-muxable protocol?
>=20
> Ben.
>=20
>> On Oct 24, 2018, at 1:08 PM, Suhas Nandakumar (snandaku) =
<snandaku@cisco.com> wrote:
>>=20
>> Hi Ben
>>=20
>> The mmusic WG agreed  to freeze further categorizations inside mux =
draft and that any new draft has to define the categories for the =
attributes they define. In this case the bis draft needs to define the =
needed categories and update IANA.
>> The procedures for the same as defined in Mux draft as well
>>=20
>> Thanks
>> Suhas
>> Sent from my iPhone
>>=20
>>> On Oct 24, 2018, at 9:37 AM, Ben Campbell <ben@nostrum.com> wrote:
>>>=20
>>> Hi,
>>>=20
>>> I=E2=80=99d like to get the opinions of MMUSIC participants on the =
use of the =E2=80=9CTBD=E2=80=9D mux category.
>>>=20
>>> draft-ietf-bfcpbis-rfc4583bis ( in IESG evaluation) defines a new =
SDP attribute =E2=80=9Cbfcpver=E2=80=9D. Since it=E2=80=99s associated =
with bfcp, which does not specify mux/demux procedures, the draft gives =
it a mux-category of =E2=80=9CTBD=E2=80=9D. Is that the right choice? If =
not, what is?
>>>=20
>>> draft-ietf-mmusic-sdp-mux-attributes describes TBD as follows:
>>>=20
>>>> The attributes in the TBD category have not been analyzed under the
>>>> proposed multiplexing framework and SHOULD NOT be multiplexed.
>>>=20
>>> However, mux-attributes goes on to use TBD for several attributes, =
including one for bfcp, with notes to the effect of the following:
>>>=20
>>>> NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation
>>>> ],
>>>> there exists no publicly available specification that defines
>>>> procedures for multiplexing/demultiplexing BFCP streams over a =
single
>>>> 5-tuple.  Once such a specification is available, the multiplexing
>>>> categories assignments for the attributes in this section could be
>>>> revisited.
>>>=20
>>> That doesn=E2=80=99t really fit the definition. It seems more like =
the attributes _have_ been analyzed, and the note states the conclusion.
>>>=20
>>> This is further complicated by the fact that  the only change =
4566bis allows to an existing mux-category registration is to move from =
=E2=80=9CTBD=E2=80=9D to something else. Any other choice will make life =
harder if we later update bfcp with mux/demux procedures.
>>>=20
>>> I am not (yet) suggesting a change to mux-attributes or 4566bis; =
I=E2=80=99m just trying to figure out the right way to specify =
mux-categories for new attributes.
>>>=20
>>> Thanks!
>>>=20
>>> Ben.
>>>=20
>>>=20
>>>=20
>>>=20
>=20
>=20


--Apple-Mail=_A55AED46-3F02-4194-A50E-A3C4375D0816
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlv9yZ0ACgkQgFZKbJXz
1A0BSBAAjtRUliOeoeLFM6bt3DNSLmG2ceDY25PBaxwy/z+dfLcmRBtm2ZoXsoj5
SJ2s7X7WsP8MGaqYf0e3hEj4yt1kZAIyVoByCkq91USSTJd/GyGgKaTB2jJhRd2g
skGOKNuh1Gw7V3pVJxlsmkrL43TYifjCUW9aJbQt0/OsO7MCQ1bwsdH7MAdjZkoG
KKJjz79fY5BfMv+dotpjS41Qs2vzNeBn8iyfNak+QlDKCmz4EHJAW2XbEK8Ls0Ws
hM0iWWvR8AwcJhumYBKSkgIA4HVLXrAPMkM8BuCJfUmlnC3Qvop54WYJzMOeM6XD
jmuzBJHwcDqwtcfbgs0BtqQuPGFJtUJIq6Bb9Ml4LWAJ13RLQ9zWN5bL2U5iUCZt
mAlWDv7BYZsAIb3VavvrKUfv5+PNdPOo+WRphs6r2oGlXs53M6xFEnmUEJs7203d
4+/CUHmsAx25hFTCPdZz8n80JQQAkw6nuFcz5cU3D5zOcMVgWagYa7yP5iNQ/csV
OL1HGtDsQ9sHbJNO5PPwPIwu1AbfzXZhDoBCcq5xIQ6e9pitjM4GU7VWWGhy5jEE
bTv1OxTHBZ212VuniLmmpGYO8m7aNdF4jmWWNOyW/IbdzKlhjt460eXoU5WuVlhX
aEgQvt7IZ/YuxHfRseniTGJfhDn7GtsdJ2yuJJVeBj9NL41TW0M=
=cCVd
-----END PGP SIGNATURE-----

--Apple-Mail=_A55AED46-3F02-4194-A50E-A3C4375D0816--


From nobody Wed Nov 28 00:45:10 2018
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF47130E4D for <bfcpbis@ietfa.amsl.com>; Wed, 28 Nov 2018 00:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.76
X-Spam-Level: 
X-Spam-Status: No, score=-5.76 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com header.b=GEBmujcG; dkim=pass (1024-bit key) header.d=ericsson.com header.b=Q+KFO5Xn
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 TZfE4P6yWv5C for <bfcpbis@ietfa.amsl.com>; Wed, 28 Nov 2018 00:45:02 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 9E039130E4A for <bfcpbis@ietf.org>; Wed, 28 Nov 2018 00:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple;  q=dns/txt; i=@ericsson.com; t=1543393799; x=1545985799; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=WIXqJPAP04T27+uHTXsGLlaAT1THocvqP3dJJn1QoyQ=; b=GEBmujcG1TJ081UkRYQdpBlP3IbFIkEwGchu3PuJvkLyB0rUdg1UmRg3j4I3NKE8 IdWHI9XEoUqYiIp5h6bBvQzHUrgpRX8KeEwnEngk9FApeFGaGuFLXgT7zPXVUA95 S7MapP0j0ihS4xTjAYo6XubuhMQ+mrbNuoAilBD2arc=;
X-AuditID: c1b4fb2d-f61ff70000007af1-fe-5bfe520792b9
Received: from ESESBMB501.ericsson.se (Unknown_Domain [153.88.183.114]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id AA.70.31473.7025EFB5; Wed, 28 Nov 2018 09:29:59 +0100 (CET)
Received: from ESESSMB502.ericsson.se (153.88.183.163) by ESESBMB501.ericsson.se (153.88.183.168) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Wed, 28 Nov 2018 09:29:58 +0100
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (153.88.183.157) by ESESSMB502.ericsson.se (153.88.183.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3 via Frontend Transport; Wed, 28 Nov 2018 09:29:58 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WIXqJPAP04T27+uHTXsGLlaAT1THocvqP3dJJn1QoyQ=; b=Q+KFO5XnJwDQrRFW++PRK5ZQ61zqvb23fVbFB5l/a92uZDDGlcSc3f7LFX+vgeNAf+RbU7ZlF90GpKLk0MqU3+ejyN+xp2b7HELLtPq4GaFmR7HEUiOGjx6k0uic239cIMKXaqw4yDsDen8kNj3xId2ZTIaw5XERtwgSTLqFUBY=
Received: from AM6PR07MB5621.eurprd07.prod.outlook.com (20.178.91.14) by AM6PR07MB5382.eurprd07.prod.outlook.com (20.177.199.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1382.6; Wed, 28 Nov 2018 08:29:57 +0000
Received: from AM6PR07MB5621.eurprd07.prod.outlook.com ([fe80::a5dd:4302:feec:e113]) by AM6PR07MB5621.eurprd07.prod.outlook.com ([fe80::a5dd:4302:feec:e113%3]) with mapi id 15.20.1382.017; Wed, 28 Nov 2018 08:29:57 +0000
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>
CC: "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "draft-ietf-bfcpbis-rfc4583bis.all@ietf.org" <draft-ietf-bfcpbis-rfc4583bis.all@ietf.org>, "draft-ietf-mmusic-sdp-mux-attributes@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes@ietf.org>, The IESG <iesg@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Use of the "TBD" Mux Category in bfcpbis.
Thread-Index: AQHUa7fLUzTJtaj4Lke/k5MIV+CmzqUusaGAgAAD+oCANblwgIAAxCOA
Date: Wed, 28 Nov 2018 08:29:57 +0000
Message-ID: <80B8CB97-B78A-48F5-BFE2-E8C91232CACB@ericsson.com>
References: <6EA38BB6-27E3-44B0-8F04-7EF8C5857BF5@nostrum.com> <B99C9CC6-89F5-4896-90C2-2AA2B8C28A56@cisco.com> <95321542-CA94-4345-AD2D-44FFDF43456E@nostrum.com> <F4DA2D8D-B840-4638-AFFE-FEA3C5CF52F4@nostrum.com>
In-Reply-To: <F4DA2D8D-B840-4638-AFFE-FEA3C5CF52F4@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.13.0.181109
authentication-results: spf=none (sender IP is ) smtp.mailfrom=christer.holmberg@ericsson.com; 
x-originating-ip: [89.166.49.243]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM6PR07MB5382; 6:LIeZ6Ww3LXW1gtVNzkcmUZKQIJQZMNLzmZmMRiF8WqDhawjsvwWP/eFD3UHH2lRXbV4TjGHr9RX4qiSHwwPHxRRrRue6hmDbIWet+F4wDP91rk9lEHLaftxaEI0O1AWjbDhG2kz7oMeSENVVcOb+zU6I/C9tUMoRN9eYiS7+DODcgqTddahkN8mOCGmyLuFS/sHjbUm6Sb78pcHsSMkbZWnnJfl9nr/YoMlTJXzinST0nBVjxWCOUeBZ2K/JwrvKuPgO20u5FQhix1kCz+VdepL/gjmaYlcs+yHXK3imrJ3cqB3E7srwg3CWaTT4vDjy7SnVQJQ7L1tYCbnfRJxzR8o6sTM6Z/Vcf6YKnSsHsYWDAVN1jfbA/Ku8Pj5yE8/Sv83i9PXjA0t9+ZnZ/N5kc0rVdu1Ng7QTxfTNYu9rq8SBBgroHiCeZ9wjq1aX6xWPCtUrxSia9w7wS7Q2sMS4nw==; 5:dtoN0ZehiyzYUEy5V+kX9hTGV1e17MYTSx56/qzLc8Ty+CFJB+y7gJFY1nFS+bDYl6tM/dU7F95ZBUYanr8gP2SE+kc3RXF6sA4RS0k6kdOB1b36y6rrKJ4ER+rRJ0q/+bBYstQBC3pSU/n3+IfeRRE/AStRQ/jHeh0UGnnZ2oc=; 7:gYWBc7+pGpbRmvgm+yUKyyaesMgeYr1UAhxqwW4KmaLxpYCuiFnvsUlPVwEsNcmR/15Muqwtcfx5WyLB7XU/ZuzQRBGKJRqn8DzdY28qXj6f0bi8rE4q0Lq9Um75vbxbD2zhMzcZBwZJ8Hg8nS/f7Q==
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 950ca365-dc46-4f66-6fc2-08d6550bae42
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:AM6PR07MB5382; 
x-ms-traffictypediagnostic: AM6PR07MB5382:
x-microsoft-antispam-prvs: <AM6PR07MB5382427C867D621CD3F6D16493D10@AM6PR07MB5382.eurprd07.prod.outlook.com>
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231443)(999002)(944501410)(52105112)(10201501046)(3002001)(148016)(149066)(150057)(6041310)(20161123562045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:AM6PR07MB5382; BCL:0; PCL:0; RULEID:; SRVR:AM6PR07MB5382; 
x-forefront-prvs: 0870212862
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(136003)(396003)(366004)(39860400002)(199004)(189003)(36756003)(6246003)(6512007)(7736002)(76176011)(4326008)(25786009)(305945005)(2906002)(102836004)(486006)(2616005)(446003)(6436002)(83716004)(11346002)(71200400001)(71190400001)(53936002)(81166006)(86362001)(82746002)(81156014)(476003)(5660300001)(44832011)(8936002)(8676002)(6116002)(6486002)(316002)(97736004)(14454004)(14444005)(229853002)(93886005)(3846002)(26005)(186003)(256004)(66066001)(106356001)(105586002)(110136005)(68736007)(6506007)(54906003)(53546011)(478600001)(33656002)(99286004)(58126008); DIR:OUT; SFP:1101; SCL:1; SRVR:AM6PR07MB5382; H:AM6PR07MB5621.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: pQeR6Mdg6ZpUT9rgUlMKzrG1KKSc3QHSAhDbOJtipYt51328cZGgeHaSPzK9QUKgQE5T6hwYgyQkX+IPHMqkqySwkBaBg86U1GTEj0G3z7ceIuk8mM97gySeR70iRuj8BHEsRP/9l52q69tswWKxEnPiCtpVDUPSztq7yx9NqkdcwxtHNtbXSqJ+BAc3mhlUffBO/65ek+tBnK1Z6K3ZvQjuS2qh70JpHv3sIAJr/Wi0drN7kfkuBz3/vcfDAp5XNpgM1/WwQiHKyQ+Ac0ZFB6I4wD3EoonrUUJvgC8maOcOgy7GgBkXiVPJdvk0fGTWeFJqEhkvU1YNElStPYjW1zA/Fxyex016A1ys8d6hTds=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <050AE1973D098B46A9045A6037C92BDF@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 950ca365-dc46-4f66-6fc2-08d6550bae42
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2018 08:29:57.5224 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB5382
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SaUhUURTHuW+ZeTP04DajeVCsHErIUHOBHi1qH4wp0sIITD/olA8V1+ap ZAtYWOmYuDSKSqTVpDVuZJYLbqOGuFQaJLhhpkgmmKhlogzNzJugb/9z/r//PfdcLkMqGmln Jj45jdcmaxJVEjlVHt6i9ZSGmSOPDE8qucrcYSlnbnhPcG/LTBKuVj9GcGU7RSRXUjNPcc97 ZukgqVq//ZpWGwxbhLqibYG6QEbIT8TwifEZvNY7IFoeV788IEn9rro+2tVCZ6ENNx2SMYD9 IedZuUSH5IwC9yPYMNVQYvEbQVV9iVQsDASsjf0hrAWFC0nQVQ8Q1rwCFxNQ2ndOpL4heDlg tkQYRoI5yDMftjIOOBwejjUiK0PiBgKMXU8IK6PEgTCvyxCZINhYuU+I+jS0/+xCVk3hg5Bd XEpbNWvB82f0tDhrCoF+8QdlNWQWo2n6sQ1CeA9sDtXZDiKxE0wuVBLiohgMHZ9IUTvC0rzZ xjtib7g3VCAVsxroNn61M27wYWXOnnWFz5V5tgUAj0tgcKiVEg1PWC0psQdCwNg2KxGhUQQ9 76rtkAesFb6RijoBtndy7IG9YMyfowqRb8V/l62wPAyJD0Fju7fYVkN794xU1G6gz5uzaRbv hsHyBaoK0UbkKPCCkBTr6+fFa+OvCkJKslcyn9aELN/I1Lzt2Ypql0/1Iswg1S5WEWSOVNCa DCEzqRcBQ6oc2PQAS4uN0WTe4LUpUdr0RF7oRS4MpXJivYwdEQocq0njE3g+ldf+cwlG5pyF /FmpblpmmqmjcosfdOqcjl02bR3t70bKAwUvJgrCvPZdWLp7c12elEGfdRMqJiqv/Poo6G67 dE+HXfwSXKSUq+PY6PMd9PG4WyHuq9z6Frt5zY/OzLy0mVuwf7Zv/OSZ5kWfUlnqIxiJvZPd EhylHHENnXrKJQUG+sR0ur8KVVFCnMbHg9QKmr97e2GaQgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/oRP6djfasZpnbsA2oE2F7HEIarM>
Subject: Re: [bfcpbis] [MMUSIC] Use of the "TBD" Mux Category in bfcpbis.
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2018 08:45:09 -0000

SGksDQoNCldoaWxlIHdlIG1heSBub3QgYWRkIG5ldyBhdHRyaWJ1dGVzIHRvIHRoZSBtdXgtY2F0
ZWdvcnkgZHJhZnQsIGRvbid0IHdlIGhhdmUgdG8gQ0hBTkdFIHRoZSBjYXRlZ29yeSBvZiBzb21l
IEJGQ1AgcmVsYXRlZCBhdHRyaWJ1dGVzIGFscmVhZHkgaW4gdGhlIGRyYWZ0LCBpbiBvcmRlciB0
byBhbGlnbiB3aXRoIEJGQ1BiaXM/DQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCu+7v09uIDI4
LzExLzIwMTgsIDAuNDgsICJCZW4gQ2FtcGJlbGwiIDxiZW5Abm9zdHJ1bS5jb20+IHdyb3RlOg0K
DQogICAgRG9lcyBhbnlvbmUgaGF2ZSBmdXJ0aGVyIHRob3VnaHRzIG9uIHRoaXM/DQogICAgDQog
ICAgPiBPbiBPY3QgMjQsIDIwMTgsIGF0IDE6MjIgUE0sIEJlbiBDYW1wYmVsbCA8YmVuQG5vc3Ry
dW0uY29tPiB3cm90ZToNCiAgICA+IA0KICAgID4gU2lnbmVkIFBHUCBwYXJ0DQogICAgPiBIaSBT
dWhhcywNCiAgICA+IA0KICAgID4gQXMgSSBtZW50aW9uZWQsIEkgYW0gbm90IHN1Z2dlc3Rpbmcg
d2UgYWRkIHRoaXMgdG8gdGhlIG11eC1hdHRyaWJ1dGVzIGRyYWZ0LiBNeSBxdWVzdGlvbiB3YXMs
IHdoYXQgaXMgdGhlIGNvcnJlY3QgY2F0ZWdvcnkgdG8gdXNlIGZvciBhIG5ldyBhdHRyaWJ1dGUg
YXNzb2NpYXRlZCB3aXRoIGEgbm9uLW11eGFibGUgcHJvdG9jb2w/DQogICAgPiANCiAgICA+IEJl
bi4NCiAgICA+IA0KICAgID4+IE9uIE9jdCAyNCwgMjAxOCwgYXQgMTowOCBQTSwgU3VoYXMgTmFu
ZGFrdW1hciAoc25hbmRha3UpIDxzbmFuZGFrdUBjaXNjby5jb20+IHdyb3RlOg0KICAgID4+IA0K
ICAgID4+IEhpIEJlbg0KICAgID4+IA0KICAgID4+IFRoZSBtbXVzaWMgV0cgYWdyZWVkICB0byBm
cmVlemUgZnVydGhlciBjYXRlZ29yaXphdGlvbnMgaW5zaWRlIG11eCBkcmFmdCBhbmQgdGhhdCBh
bnkgbmV3IGRyYWZ0IGhhcyB0byBkZWZpbmUgdGhlIGNhdGVnb3JpZXMgZm9yIHRoZSBhdHRyaWJ1
dGVzIHRoZXkgZGVmaW5lLiBJbiB0aGlzIGNhc2UgdGhlIGJpcyBkcmFmdCBuZWVkcyB0byBkZWZp
bmUgdGhlIG5lZWRlZCBjYXRlZ29yaWVzIGFuZCB1cGRhdGUgSUFOQS4NCiAgICA+PiBUaGUgcHJv
Y2VkdXJlcyBmb3IgdGhlIHNhbWUgYXMgZGVmaW5lZCBpbiBNdXggZHJhZnQgYXMgd2VsbA0KICAg
ID4+IA0KICAgID4+IFRoYW5rcw0KICAgID4+IFN1aGFzDQogICAgPj4gU2VudCBmcm9tIG15IGlQ
aG9uZQ0KICAgID4+IA0KICAgID4+PiBPbiBPY3QgMjQsIDIwMTgsIGF0IDk6MzcgQU0sIEJlbiBD
YW1wYmVsbCA8YmVuQG5vc3RydW0uY29tPiB3cm90ZToNCiAgICA+Pj4gDQogICAgPj4+IEhpLA0K
ICAgID4+PiANCiAgICA+Pj4gSeKAmWQgbGlrZSB0byBnZXQgdGhlIG9waW5pb25zIG9mIE1NVVNJ
QyBwYXJ0aWNpcGFudHMgb24gdGhlIHVzZSBvZiB0aGUg4oCcVEJE4oCdIG11eCBjYXRlZ29yeS4N
CiAgICA+Pj4gDQogICAgPj4+IGRyYWZ0LWlldGYtYmZjcGJpcy1yZmM0NTgzYmlzICggaW4gSUVT
RyBldmFsdWF0aW9uKSBkZWZpbmVzIGEgbmV3IFNEUCBhdHRyaWJ1dGUg4oCcYmZjcHZlcuKAnS4g
U2luY2UgaXTigJlzIGFzc29jaWF0ZWQgd2l0aCBiZmNwLCB3aGljaCBkb2VzIG5vdCBzcGVjaWZ5
IG11eC9kZW11eCBwcm9jZWR1cmVzLCB0aGUgZHJhZnQgZ2l2ZXMgaXQgYSBtdXgtY2F0ZWdvcnkg
b2Yg4oCcVEJE4oCdLiBJcyB0aGF0IHRoZSByaWdodCBjaG9pY2U/IElmIG5vdCwgd2hhdCBpcz8N
CiAgICA+Pj4gDQogICAgPj4+IGRyYWZ0LWlldGYtbW11c2ljLXNkcC1tdXgtYXR0cmlidXRlcyBk
ZXNjcmliZXMgVEJEIGFzIGZvbGxvd3M6DQogICAgPj4+IA0KICAgID4+Pj4gVGhlIGF0dHJpYnV0
ZXMgaW4gdGhlIFRCRCBjYXRlZ29yeSBoYXZlIG5vdCBiZWVuIGFuYWx5emVkIHVuZGVyIHRoZQ0K
ICAgID4+Pj4gcHJvcG9zZWQgbXVsdGlwbGV4aW5nIGZyYW1ld29yayBhbmQgU0hPVUxEIE5PVCBi
ZSBtdWx0aXBsZXhlZC4NCiAgICA+Pj4gDQogICAgPj4+IEhvd2V2ZXIsIG11eC1hdHRyaWJ1dGVz
IGdvZXMgb24gdG8gdXNlIFRCRCBmb3Igc2V2ZXJhbCBhdHRyaWJ1dGVzLCBpbmNsdWRpbmcgb25l
IGZvciBiZmNwLCB3aXRoIG5vdGVzIHRvIHRoZSBlZmZlY3Qgb2YgdGhlIGZvbGxvd2luZzoNCiAg
ICA+Pj4gDQogICAgPj4+PiBOT1RFOiBBcyBwZXIgc2VjdGlvbiA5IG9mIFtJLUQuaWV0Zi1tbXVz
aWMtc2RwLWJ1bmRsZS1uZWdvdGlhdGlvbg0KICAgID4+Pj4gXSwNCiAgICA+Pj4+IHRoZXJlIGV4
aXN0cyBubyBwdWJsaWNseSBhdmFpbGFibGUgc3BlY2lmaWNhdGlvbiB0aGF0IGRlZmluZXMNCiAg
ICA+Pj4+IHByb2NlZHVyZXMgZm9yIG11bHRpcGxleGluZy9kZW11bHRpcGxleGluZyBCRkNQIHN0
cmVhbXMgb3ZlciBhIHNpbmdsZQ0KICAgID4+Pj4gNS10dXBsZS4gIE9uY2Ugc3VjaCBhIHNwZWNp
ZmljYXRpb24gaXMgYXZhaWxhYmxlLCB0aGUgbXVsdGlwbGV4aW5nDQogICAgPj4+PiBjYXRlZ29y
aWVzIGFzc2lnbm1lbnRzIGZvciB0aGUgYXR0cmlidXRlcyBpbiB0aGlzIHNlY3Rpb24gY291bGQg
YmUNCiAgICA+Pj4+IHJldmlzaXRlZC4NCiAgICA+Pj4gDQogICAgPj4+IFRoYXQgZG9lc27igJl0
IHJlYWxseSBmaXQgdGhlIGRlZmluaXRpb24uIEl0IHNlZW1zIG1vcmUgbGlrZSB0aGUgYXR0cmli
dXRlcyBfaGF2ZV8gYmVlbiBhbmFseXplZCwgYW5kIHRoZSBub3RlIHN0YXRlcyB0aGUgY29uY2x1
c2lvbi4NCiAgICA+Pj4gDQogICAgPj4+IFRoaXMgaXMgZnVydGhlciBjb21wbGljYXRlZCBieSB0
aGUgZmFjdCB0aGF0ICB0aGUgb25seSBjaGFuZ2UgNDU2NmJpcyBhbGxvd3MgdG8gYW4gZXhpc3Rp
bmcgbXV4LWNhdGVnb3J5IHJlZ2lzdHJhdGlvbiBpcyB0byBtb3ZlIGZyb20g4oCcVEJE4oCdIHRv
IHNvbWV0aGluZyBlbHNlLiBBbnkgb3RoZXIgY2hvaWNlIHdpbGwgbWFrZSBsaWZlIGhhcmRlciBp
ZiB3ZSBsYXRlciB1cGRhdGUgYmZjcCB3aXRoIG11eC9kZW11eCBwcm9jZWR1cmVzLg0KICAgID4+
PiANCiAgICA+Pj4gSSBhbSBub3QgKHlldCkgc3VnZ2VzdGluZyBhIGNoYW5nZSB0byBtdXgtYXR0
cmlidXRlcyBvciA0NTY2YmlzOyBJ4oCZbSBqdXN0IHRyeWluZyB0byBmaWd1cmUgb3V0IHRoZSBy
aWdodCB3YXkgdG8gc3BlY2lmeSBtdXgtY2F0ZWdvcmllcyBmb3IgbmV3IGF0dHJpYnV0ZXMuDQog
ICAgPj4+IA0KICAgID4+PiBUaGFua3MhDQogICAgPj4+IA0KICAgID4+PiBCZW4uDQogICAgPj4+
IA0KICAgID4+PiANCiAgICA+Pj4gDQogICAgPj4+IA0KICAgID4gDQogICAgPiANCiAgICANCiAg
ICANCg0K


From nobody Wed Nov 28 08:13:33 2018
Return-Path: <ben@nostrum.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC21130E94 for <bfcpbis@ietfa.amsl.com>; Wed, 28 Nov 2018 08:13:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level: 
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 pEmtQL9Kvnn0 for <bfcpbis@ietfa.amsl.com>; Wed, 28 Nov 2018 08:13:29 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD129130E96 for <bfcpbis@ietf.org>; Wed, 28 Nov 2018 08:13:29 -0800 (PST)
Received: from [10.0.1.24] (cpe-70-122-203-106.tx.res.rr.com [70.122.203.106]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id wASGDO4J083892 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 28 Nov 2018 10:13:25 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-70-122-203-106.tx.res.rr.com [70.122.203.106] claimed to be [10.0.1.24]
From: Ben Campbell <ben@nostrum.com>
Message-Id: <A6CBBA11-5CA3-4ECA-93C2-7C1A31C35EED@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E5EE79F2-6013-44DF-9687-D0C19F9CD3BC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 12.1 \(3445.101.1\))
Date: Wed, 28 Nov 2018 10:13:23 -0600
In-Reply-To: <80B8CB97-B78A-48F5-BFE2-E8C91232CACB@ericsson.com>
Cc: "Suhas Nandakumar (snandaku)" <snandaku@cisco.com>, "bfcpbis@ietf.org" <bfcpbis@ietf.org>, "draft-ietf-bfcpbis-rfc4583bis.all@ietf.org" <draft-ietf-bfcpbis-rfc4583bis.all@ietf.org>,  "draft-ietf-mmusic-sdp-mux-attributes@ietf.org" <draft-ietf-mmusic-sdp-mux-attributes@ietf.org>,  The IESG <iesg@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
To: Christer Holmberg <christer.holmberg@ericsson.com>
References: <6EA38BB6-27E3-44B0-8F04-7EF8C5857BF5@nostrum.com> <B99C9CC6-89F5-4896-90C2-2AA2B8C28A56@cisco.com> <95321542-CA94-4345-AD2D-44FFDF43456E@nostrum.com> <F4DA2D8D-B840-4638-AFFE-FEA3C5CF52F4@nostrum.com> <80B8CB97-B78A-48F5-BFE2-E8C91232CACB@ericsson.com>
X-Mailer: Apple Mail (2.3445.101.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/jOvUE0fm3FFvb6jw_8jOzb4B5iM>
Subject: [bfcpbis] Mux category for non-muxable protocols (was Re: [MMUSIC] Use of the "TBD" Mux Category in bfcpbis.)
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Nov 2018 16:13:32 -0000

--Apple-Mail=_E5EE79F2-6013-44DF-9687-D0C19F9CD3BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

There are some misalignments between BFCPbis and mux-category that we =
need to deal with, yes.

But my question was more general: What is the correct category to use =
for a new attribute associated with a known-to-be-non-muxable protocol? =
TBD doesn=E2=80=99t seem right, but that=E2=80=99s what we=E2=80=99ve =
used so far.

(I changed the email subject to match)

Ben.

> On Nov 28, 2018, at 2:29 AM, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
>=20
> Hi,
>=20
> While we may not add new attributes to the mux-category draft, don't =
we have to CHANGE the category of some BFCP related attributes already =
in the draft, in order to align with BFCPbis?
>=20
> Regards,
>=20
> Christer
>=20
> =EF=BB=BFOn 28/11/2018, 0.48, "Ben Campbell" <ben@nostrum.com> wrote:
>=20
>    Does anyone have further thoughts on this?
>=20
>> On Oct 24, 2018, at 1:22 PM, Ben Campbell <ben@nostrum.com> wrote:
>>=20
>> Signed PGP part
>> Hi Suhas,
>>=20
>> As I mentioned, I am not suggesting we add this to the mux-attributes =
draft. My question was, what is the correct category to use for a new =
attribute associated with a non-muxable protocol?
>>=20
>> Ben.
>>=20
>>> On Oct 24, 2018, at 1:08 PM, Suhas Nandakumar (snandaku) =
<snandaku@cisco.com> wrote:
>>>=20
>>> Hi Ben
>>>=20
>>> The mmusic WG agreed  to freeze further categorizations inside mux =
draft and that any new draft has to define the categories for the =
attributes they define. In this case the bis draft needs to define the =
needed categories and update IANA.
>>> The procedures for the same as defined in Mux draft as well
>>>=20
>>> Thanks
>>> Suhas
>>> Sent from my iPhone
>>>=20
>>>> On Oct 24, 2018, at 9:37 AM, Ben Campbell <ben@nostrum.com> wrote:
>>>>=20
>>>> Hi,
>>>>=20
>>>> I=E2=80=99d like to get the opinions of MMUSIC participants on the =
use of the =E2=80=9CTBD=E2=80=9D mux category.
>>>>=20
>>>> draft-ietf-bfcpbis-rfc4583bis ( in IESG evaluation) defines a new =
SDP attribute =E2=80=9Cbfcpver=E2=80=9D. Since it=E2=80=99s associated =
with bfcp, which does not specify mux/demux procedures, the draft gives =
it a mux-category of =E2=80=9CTBD=E2=80=9D. Is that the right choice? If =
not, what is?
>>>>=20
>>>> draft-ietf-mmusic-sdp-mux-attributes describes TBD as follows:
>>>>=20
>>>>> The attributes in the TBD category have not been analyzed under =
the
>>>>> proposed multiplexing framework and SHOULD NOT be multiplexed.
>>>>=20
>>>> However, mux-attributes goes on to use TBD for several attributes, =
including one for bfcp, with notes to the effect of the following:
>>>>=20
>>>>> NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation
>>>>> ],
>>>>> there exists no publicly available specification that defines
>>>>> procedures for multiplexing/demultiplexing BFCP streams over a =
single
>>>>> 5-tuple.  Once such a specification is available, the multiplexing
>>>>> categories assignments for the attributes in this section could be
>>>>> revisited.
>>>>=20
>>>> That doesn=E2=80=99t really fit the definition. It seems more like =
the attributes _have_ been analyzed, and the note states the conclusion.
>>>>=20
>>>> This is further complicated by the fact that  the only change =
4566bis allows to an existing mux-category registration is to move from =
=E2=80=9CTBD=E2=80=9D to something else. Any other choice will make life =
harder if we later update bfcp with mux/demux procedures.
>>>>=20
>>>> I am not (yet) suggesting a change to mux-attributes or 4566bis; =
I=E2=80=99m just trying to figure out the right way to specify =
mux-categories for new attributes.
>>>>=20
>>>> Thanks!
>>>>=20
>>>> Ben.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>=20
>>=20
>=20
>=20
>=20


--Apple-Mail=_E5EE79F2-6013-44DF-9687-D0C19F9CD3BC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlv+vqMACgkQgFZKbJXz
1A3rRhAAnRSUl/Nv8h65hLqM2oirRvtcl7+BFTbQhoMDUc5YdpZpJPY8lhbVVlbn
GG7FwjUDEpcuhGmQWuFKABPyvpVSD5H4ya1JMFdz6UPFrre47rxwLgbAH6Ie80Ke
tO55uVsQma+dsRd8zJefL0vzQ9hz5kP5j7iZI/4ObQrmWkCoS99aDty1jHO/zaDP
npqLy0DKiM17zM8TZsq/XWNw9oHcxPs/bBCHhUKyjyyBQj79dLhEQ8vsBtQHmSdL
ZK2r3vN8F039A5sRVQI6ecVV5F2M9ROEr69RH7C/j9ZqlrYA9nt4nQJZT+IZ7nBz
NuCw4eOl5rlpUleYBIP8TuqTHABx2SbPwN61l9YqLlrFS8yI7kkNqOUCxV4I9cp7
5xtfftMRlxJxmv4L1En3js4h63g6fBx+GrfzFNgiojvLOFOO95oFwkEyLrIwQtuG
o7J3O0hMwHKh0kcy5SqT5bmYFWiaTTMkvsEtg5kTAxhGk7zcbiWbr0NvCOXfcMHi
N81pnHEd0ZQWxnGRLmRJEUEpK77EzHckM3nYN5kw0H9Wiw5u+CtIfLhIrZoQdkQO
OiSki347QxDXuAA9QOBV/q/EZrR+1ZzqON4Nw4KYDHWcbmkz3u3a20plTowom9EZ
7M83hxi0s6Rnfw8f0HKFsdfwQQqAvjCCNVKK8fzFarsVAu3Z7QU=
=gvlQ
-----END PGP SIGNATURE-----

--Apple-Mail=_E5EE79F2-6013-44DF-9687-D0C19F9CD3BC--


From nobody Thu Nov 29 00:47:42 2018
Return-Path: <suhasietf@gmail.com>
X-Original-To: bfcpbis@ietfa.amsl.com
Delivered-To: bfcpbis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A165130DC3; Thu, 29 Nov 2018 00:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 4QLNloBJ-CQB; Thu, 29 Nov 2018 00:47:37 -0800 (PST)
Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97B91130DD1; Thu, 29 Nov 2018 00:47:37 -0800 (PST)
Received: by mail-vs1-xe34.google.com with SMTP id x64so663414vsa.5; Thu, 29 Nov 2018 00:47:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n1O7P6OoDZ0wI/i2Z4EPFABjME1zxKuiWXTgSB2TkQM=; b=OwMZI2ukB9eS96rOegYymh3baJzuE2ozbQlVBWDt0o5O0AILUMbYFTXEHKU5q1E75G OMz3nlqZUevZ8dChWplkEFkEYI1F7XrI7t2UozKdXeIk1/rJ9k0peUwMWGcrqkg1+4Bx 9AZcZkQvtR+IiTBDIj9CTvMlCR6CSDyOCHQPojOPRy8z/lqqwNFlJt608NslOw0nfAu1 kmu8RV8w1NRZOuzLjy2LLQ7cq0Ss8BV4n19KBB4BC5po2tPGn75QxN18OdooEEhnDFh6 /ffUF1OanHmiZBtpyQvbaH2ilntBU8ldHLRTVwr9WcPgPI5fyuPXgJH0pEas+of0Bpap 88Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=n1O7P6OoDZ0wI/i2Z4EPFABjME1zxKuiWXTgSB2TkQM=; b=ojhb3RLkvuREeZ3cJwvs3BgiC3ZbT4JVWgMDCmt/GlZwplHRq2blBPHY2S8wM5lGwi jmXeZDJ39/PWNCD2MKIjYKfZJ1URNxzTY5pzA3m8Yuph2bRQPE51ubCdBmtrUG1xncDV iyrACsHkLoxOJTQrslJIQ3UgyDKQiF0PiDPCMrvUUu0wPozMU2zmq0RqvxNzjBGiH2zM kKd7Rqz0vTtzlGV8BTaLriqCP7SaoipaljBya4WsvR2XQPbzJ7k0NwbNG99nRTeEobfF Cyu2/vP7O1JTG7ouSELRuhanKbK88S0TumKXF2TAx+XgdPvHGU2epVZsXcjR0G3xJgpz Jo3w==
X-Gm-Message-State: AA+aEWZjbadZyisPsssvI+PaUfG0iwnYudxu290/knt7cOsyQW8ISute f29LvyXdijMVsjuXrqDwoeKvrkA/TPA1bbFcbWc=
X-Google-Smtp-Source: AFSGD/X4dn0HM+C1X5fNiQQkM5YngmK1XjT94S6tm0J7lT7vt4Qn7iGUymRENktydZIoSB1H8cUOT7EFBATm4UpVmE0=
X-Received: by 2002:a67:d913:: with SMTP id t19mr231758vsj.26.1543481256549; Thu, 29 Nov 2018 00:47:36 -0800 (PST)
MIME-Version: 1.0
References: <6EA38BB6-27E3-44B0-8F04-7EF8C5857BF5@nostrum.com> <B99C9CC6-89F5-4896-90C2-2AA2B8C28A56@cisco.com> <95321542-CA94-4345-AD2D-44FFDF43456E@nostrum.com> <F4DA2D8D-B840-4638-AFFE-FEA3C5CF52F4@nostrum.com> <80B8CB97-B78A-48F5-BFE2-E8C91232CACB@ericsson.com> <A6CBBA11-5CA3-4ECA-93C2-7C1A31C35EED@nostrum.com>
In-Reply-To: <A6CBBA11-5CA3-4ECA-93C2-7C1A31C35EED@nostrum.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Thu, 29 Nov 2018 00:47:24 -0800
Message-ID: <CAMRcRGRhNXSFPgbCMvbX+YMYyW9ZxyeyAtDFB-GUs0ncP6YXdA@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, bfcpbis@ietf.org,  mmusic WG <mmusic@ietf.org>, draft-ietf-mmusic-sdp-mux-attributes@ietf.org,  draft-ietf-bfcpbis-rfc4583bis.all@ietf.org, The IESG <iesg@ietf.org>,  snandaku@cisco.com
Content-Type: multipart/alternative; boundary="00000000000003a3b3057bc9bce5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bfcpbis/h_a3LMIdyWGJ-ogbUOT-AOP0Mlw>
Subject: Re: [bfcpbis] [MMUSIC] Mux category for non-muxable protocols (was Re: Use of the "TBD" Mux Category in bfcpbis.)
X-BeenThere: bfcpbis@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BFCPBIS working group discussion list <bfcpbis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bfcpbis/>
List-Post: <mailto:bfcpbis@ietf.org>
List-Help: <mailto:bfcpbis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bfcpbis>, <mailto:bfcpbis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2018 08:47:40 -0000

--00000000000003a3b3057bc9bce5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello Ben

Please see inline

On Wed, Nov 28, 2018 at 8:14 AM Ben Campbell <ben@nostrum.com> wrote:

> There are some misalignments between BFCPbis and mux-category that we nee=
d
> to deal with, yes.
>
> But my question was more general: What is the correct category to use for
> a new attribute associated with a known-to-be-non-muxable protocol? TBD
> doesn=E2=80=99t seem right, but that=E2=80=99s what we=E2=80=99ve used so=
 far.
>
>
[Suhas]  The only 2 options i see with the categorization is either
"CAUTION" or "SPECIAL". Former implies multiplex at your own risk and later
requires specification that defines such a attribute to further clarify on
the behavior under multiplexing, if allowed.


(I changed the email subject to match)
>
> Ben.
>
> > On Nov 28, 2018, at 2:29 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
> >
> > Hi,
> >
> > While we may not add new attributes to the mux-category draft, don't we
> have to CHANGE the category of some BFCP related attributes already in th=
e
> draft, in order to align with BFCPbis?
> >
> > Regards,
> >
> > Christer
> >
> > =EF=BB=BFOn 28/11/2018, 0.48, "Ben Campbell" <ben@nostrum.com> wrote:
> >
> >    Does anyone have further thoughts on this?
> >
> >> On Oct 24, 2018, at 1:22 PM, Ben Campbell <ben@nostrum.com> wrote:
> >>
> >> Signed PGP part
> >> Hi Suhas,
> >>
> >> As I mentioned, I am not suggesting we add this to the mux-attributes
> draft. My question was, what is the correct category to use for a new
> attribute associated with a non-muxable protocol?
> >>
> >> Ben.
> >>
> >>> On Oct 24, 2018, at 1:08 PM, Suhas Nandakumar (snandaku) <
> snandaku@cisco.com> wrote:
> >>>
> >>> Hi Ben
> >>>
> >>> The mmusic WG agreed  to freeze further categorizations inside mux
> draft and that any new draft has to define the categories for the
> attributes they define. In this case the bis draft needs to define the
> needed categories and update IANA.
> >>> The procedures for the same as defined in Mux draft as well
> >>>
> >>> Thanks
> >>> Suhas
> >>> Sent from my iPhone
> >>>
> >>>> On Oct 24, 2018, at 9:37 AM, Ben Campbell <ben@nostrum.com> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I=E2=80=99d like to get the opinions of MMUSIC participants on the u=
se of the
> =E2=80=9CTBD=E2=80=9D mux category.
> >>>>
> >>>> draft-ietf-bfcpbis-rfc4583bis ( in IESG evaluation) defines a new SD=
P
> attribute =E2=80=9Cbfcpver=E2=80=9D. Since it=E2=80=99s associated with b=
fcp, which does not
> specify mux/demux procedures, the draft gives it a mux-category of =E2=80=
=9CTBD=E2=80=9D.
> Is that the right choice? If not, what is?
> >>>>
> >>>> draft-ietf-mmusic-sdp-mux-attributes describes TBD as follows:
> >>>>
> >>>>> The attributes in the TBD category have not been analyzed under the
> >>>>> proposed multiplexing framework and SHOULD NOT be multiplexed.
> >>>>
> >>>> However, mux-attributes goes on to use TBD for several attributes,
> including one for bfcp, with notes to the effect of the following:
> >>>>
> >>>>> NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-negotiation
> >>>>> ],
> >>>>> there exists no publicly available specification that defines
> >>>>> procedures for multiplexing/demultiplexing BFCP streams over a sing=
le
> >>>>> 5-tuple.  Once such a specification is available, the multiplexing
> >>>>> categories assignments for the attributes in this section could be
> >>>>> revisited.
> >>>>
> >>>> That doesn=E2=80=99t really fit the definition. It seems more like t=
he
> attributes _have_ been analyzed, and the note states the conclusion.
> >>>>
> >>>> This is further complicated by the fact that  the only change 4566bi=
s
> allows to an existing mux-category registration is to move from =E2=80=9C=
TBD=E2=80=9D to
> something else. Any other choice will make life harder if we later update
> bfcp with mux/demux procedures.
> >>>>
> >>>> I am not (yet) suggesting a change to mux-attributes or 4566bis; I=
=E2=80=99m
> just trying to figure out the right way to specify mux-categories for new
> attributes.
> >>>>
> >>>> Thanks!
> >>>>
> >>>> Ben.
> >>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
> >
> >
> >
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--00000000000003a3b3057bc9bce5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br>Hello Ben<div><br></div><div>Please see inline</div><d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, Nov 28, 2018 at =
8:14 AM Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There are some misa=
lignments between BFCPbis and mux-category that we need to deal with, yes.<=
br>
<br>
But my question was more general: What is the correct category to use for a=
 new attribute associated with a known-to-be-non-muxable protocol? TBD does=
n=E2=80=99t seem right, but that=E2=80=99s what we=E2=80=99ve used so far.<=
br>
<br></blockquote><div><br></div><div>[Suhas]=C2=A0 The only 2 options i see=
 with the categorization is either &quot;CAUTION&quot; or &quot;SPECIAL&quo=
t;. Former implies multiplex at your own risk and later requires specificat=
ion that defines such a attribute to further clarify on the behavior under =
multiplexing, if allowed.=C2=A0</div><div><br></div><div><br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
(I changed the email subject to match)<br>
<br>
Ben.<br>
<br>
&gt; On Nov 28, 2018, at 2:29 AM, Christer Holmberg &lt;<a href=3D"mailto:c=
hrister.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson=
.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Hi,<br>
&gt; <br>
&gt; While we may not add new attributes to the mux-category draft, don&#39=
;t we have to CHANGE the category of some BFCP related attributes already i=
n the draft, in order to align with BFCPbis?<br>
&gt; <br>
&gt; Regards,<br>
&gt; <br>
&gt; Christer<br>
&gt; <br>
&gt; =EF=BB=BFOn 28/11/2018, 0.48, &quot;Ben Campbell&quot; &lt;<a href=3D"=
mailto:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br=
>
&gt; <br>
&gt;=C2=A0 =C2=A0 Does anyone have further thoughts on this?<br>
&gt; <br>
&gt;&gt; On Oct 24, 2018, at 1:22 PM, Ben Campbell &lt;<a href=3D"mailto:be=
n@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Signed PGP part<br>
&gt;&gt; Hi Suhas,<br>
&gt;&gt; <br>
&gt;&gt; As I mentioned, I am not suggesting we add this to the mux-attribu=
tes draft. My question was, what is the correct category to use for a new a=
ttribute associated with a non-muxable protocol?<br>
&gt;&gt; <br>
&gt;&gt; Ben.<br>
&gt;&gt; <br>
&gt;&gt;&gt; On Oct 24, 2018, at 1:08 PM, Suhas Nandakumar (snandaku) &lt;<=
a href=3D"mailto:snandaku@cisco.com" target=3D"_blank">snandaku@cisco.com</=
a>&gt; wrote:<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Hi Ben<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; The mmusic WG agreed=C2=A0 to freeze further categorizations i=
nside mux draft and that any new draft has to define the categories for the=
 attributes they define. In this case the bis draft needs to define the nee=
ded categories and update IANA.<br>
&gt;&gt;&gt; The procedures for the same as defined in Mux draft as well<br=
>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; Thanks<br>
&gt;&gt;&gt; Suhas<br>
&gt;&gt;&gt; Sent from my iPhone<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; On Oct 24, 2018, at 9:37 AM, Ben Campbell &lt;<a href=3D"m=
ailto:ben@nostrum.com" target=3D"_blank">ben@nostrum.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Hi,<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; I=E2=80=99d like to get the opinions of MMUSIC participant=
s on the use of the =E2=80=9CTBD=E2=80=9D mux category.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; draft-ietf-bfcpbis-rfc4583bis ( in IESG evaluation) define=
s a new SDP attribute =E2=80=9Cbfcpver=E2=80=9D. Since it=E2=80=99s associa=
ted with bfcp, which does not specify mux/demux procedures, the draft gives=
 it a mux-category of =E2=80=9CTBD=E2=80=9D. Is that the right choice? If n=
ot, what is?<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; draft-ietf-mmusic-sdp-mux-attributes describes TBD as foll=
ows:<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; The attributes in the TBD category have not been analy=
zed under the<br>
&gt;&gt;&gt;&gt;&gt; proposed multiplexing framework and SHOULD NOT be mult=
iplexed.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; However, mux-attributes goes on to use TBD for several att=
ributes, including one for bfcp, with notes to the effect of the following:=
<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt;&gt; NOTE: As per section 9 of [I-D.ietf-mmusic-sdp-bundle-=
negotiation<br>
&gt;&gt;&gt;&gt;&gt; ],<br>
&gt;&gt;&gt;&gt;&gt; there exists no publicly available specification that =
defines<br>
&gt;&gt;&gt;&gt;&gt; procedures for multiplexing/demultiplexing BFCP stream=
s over a single<br>
&gt;&gt;&gt;&gt;&gt; 5-tuple.=C2=A0 Once such a specification is available,=
 the multiplexing<br>
&gt;&gt;&gt;&gt;&gt; categories assignments for the attributes in this sect=
ion could be<br>
&gt;&gt;&gt;&gt;&gt; revisited.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; That doesn=E2=80=99t really fit the definition. It seems m=
ore like the attributes _have_ been analyzed, and the note states the concl=
usion.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; This is further complicated by the fact that=C2=A0 the onl=
y change 4566bis allows to an existing mux-category registration is to move=
 from =E2=80=9CTBD=E2=80=9D to something else. Any other choice will make l=
ife harder if we later update bfcp with mux/demux procedures.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; I am not (yet) suggesting a change to mux-attributes or 45=
66bis; I=E2=80=99m just trying to figure out the right way to specify mux-c=
ategories for new attributes.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Thanks!<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; Ben.<br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt;&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div></div></div>

--00000000000003a3b3057bc9bce5--

