
From nobody Thu Feb  1 14:47:55 2018
Return-Path: <thomass.stach@gmail.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 1550912EAF6; Thu,  1 Feb 2018 14:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 dk2HTHLEIWYu; Thu,  1 Feb 2018 14:47:51 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 CADE3126CC7; Thu,  1 Feb 2018 14:47:50 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id t74so9027618wme.3; Thu, 01 Feb 2018 14:47:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=ZxhWguH6PnqN1LPK8a1B5jGzBg57XnczxBRJXf+IsG0=; b=YWWpG3y+IX5uDLlWRy0SXX/eQpQ/OCC8xOQS7FGRD/xCfRFVsCu1ycorJ8SBjwFbbh ViHI54utYWq6DQm7REF5IB8l94B1mIhbP5uvfebMa/+E2Fhh2qDLmp4IokAmq33Sb9GO GcJy3P+fO9uq4swzSNN+Xn0w+y1guEt5fCQvrzOsiN5WWZhP43YAvxIf7cw25lNxWnYa itZKxw8wwQSA51HLEctmFeFVFkryKhJj9pg2vABzBttbLtlOgTbGunBiW1JcylT4RHj6 Kc1VLiuBKEMqa9og5iv9wOGcoX6HVzwrqxMVlVUxYux/wTWCsM+AJoS+yrIY50slsbAQ bX1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ZxhWguH6PnqN1LPK8a1B5jGzBg57XnczxBRJXf+IsG0=; b=DzdRuRMvuQiXgrGYXS4/WS+BqrOozjvZ7YfH5y/kcPLUzBYP4dFhsrRC/cdqAykUcW mDUFr3zjx00eEjfmFQfKoJwKBKkUrWFaiLRQSwpPgOlw5A89iifaY5QI9dsS1pfEGWs8 bHYGQrktLHFCVbIaiiueVMEgeb4bqYBDa47zcs+x2sWi+nYLogw+u1a4/3me9x/N1XUI PxLQptSY8SkU593mZ/TgjoV0cLRnbpq84VOr6DMx1GWUM9uZu7yY1bYyWYc4oAYavuDi xX4AS4suwPkns2gSM+bRV6C7mN3HnluzzTBBEYyG4eyFmLGkbk/4zCrlybVa4Q6Q7PRZ pbsw==
X-Gm-Message-State: AKwxytfDnutWQmrPN9zYnhrN+NkSRw8OzNjJS2rZkDFiwb9sg82ZTUIb XMruOHDtAwfMddzY0Ip/yjjFcXKP
X-Google-Smtp-Source: AH8x224VUsJ2fpm71sNBd+s0cUbJ25LgR2SGvHiiTeiSku2rmsMfEeNl+KwFBxS6ZXr2htDVJzB/kw==
X-Received: by 10.28.106.26 with SMTP id f26mr26609373wmc.36.1517525268701; Thu, 01 Feb 2018 14:47:48 -0800 (PST)
Received: from [192.168.2.110] (dsl-linz7-18-136.utaonline.at. [81.189.18.136]) by smtp.googlemail.com with ESMTPSA id 42sm1094628wrw.15.2018.02.01.14.47.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 14:47:47 -0800 (PST)
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
Cc: draft-ietf-mmusic-trickle-ice-sip.all@ietf.org, mmusic@ietf.org
References: <151676553958.24137.4237678593782258786@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <d8a18070-83c1-e5fa-8b5b-fa47fbed11cc@gmail.com>
Date: Thu, 1 Feb 2018 23:47:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <151676553958.24137.4237678593782258786@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/z3No8P_u__g6xP0EPTtkv9NJiBU>
Subject: Re: [MMUSIC] Genart last call review of draft-ietf-mmusic-trickle-ice-sip-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 01 Feb 2018 22:47:54 -0000

Dale,

first of all apologies for the delay in responding to your thorough review.

Thanks for your effort.

more inline


On 2018-01-24 04:45, Dale Worley wrote:
> Reviewer: Dale Worley
> Review result: Ready with Issues
>
> I am the assigned Gen-ART reviewer for this draft.  The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> Document:  draft-ietf-mmusic-trickle-ice-sip-12
> Reviewer:  Dale R. Worley
> Review Date:  2018-01-23
> IETF LC End Date:  2018-01-26
> IESG Telechat date:  [unknown]
>
> Summary:
>
>         This draft is on the right track but has open issues, described
>         in the review.
>
> This draft is technically quite good, and except for various nits,
> quite well written.  But there are some significant technical issues
> that need to be properly settled before the protocol is well-defined
> with good advice on robust usage.  I don't think settling these issues
> will be difficult.
>
> ** Global/major issues:
>
> * The tokens "end-of-candidate" and "end-of-candidates" seem to be used
> equivalently in this document, with the following number of uses:
>
>       11 end-of-candidate
>       19 end-of-candidates
>
> Which is the correct form?
Hm, as the grammar says "end-of-candidates ", I'll change to the latter.
> * The definition of application/trickle-ice-sdpfrag describes the use of
> "a=charset" as an attribute, but the grammar of sdpfrag in section 9
> does not permit that attribute.
The grammar allows for using extension attributes.
"a=charset" would be one of these, but might only be needed if non-ASCII 
characters are possibly introduced via some potential extension.
>
> * Deployment considerations (section 11)
>
> It might be worth mentioning here what happens if a middlebox deletes
> Trickle ICE INFO requests because it does not understand them, but
> does not delete "Supported: trickle-ice" headers.  It seems to me that
> in order to be robust in this situation, a UA should provide a
> globally routable address in the m= lines of the initial offer or
> answer, or if Trickle ICE INFO requests fail, eventually amend the
> addresses to be globally routable addresses.
There are so many ways how middle boxes can break any mechanism, that we 
can't do much to cover everything.
RFC 5245 has recommendations (e.g. relayed candidates will always work) 
on how to choose the default destination as provided in the m/c-line.
I don't think we need to repeat that reasoning here , and after all the 
user agent might not want to use such a globally routable address.
>
> But the WG may have more knowledge about this situation.
>
> * There are various locations where the language has usages that seem to
> me to be excessively informal or prolix.  Cases I've noticed are:
>
> 2.  Terminology
>
>     It is assumed that the reader will be
>     familiar with the terminology from both documents.
>
> Probably s/will be/is/.
OK
>
> 3.1.  Discovery issues
>
>     Such Offers and Answers can
>     only be handled meaningfully by agents that actually support
>     incremental candidate provisioning, which implies the need to confirm
>     such support before actually using it.
>
> It's probably best to omit "actually" here and elsewhere.  There is
> also a use of "right from the first Offer".  And in some places
> "would" is used where it is not needed or could be replaced by "do";
> "would" should (IMO) be restricted to situations that are
> counter-factual.  There is also a use of "like for example" instead of
> "for example".
I'll have pass through the document and look for these.
>
> I expect the RFC Editor can give guidance on this subject.
>
> ** Detailed/editorial/nits:
>
>         A Session Initiation Protocol (SIP) usage for Trickle ICE
>                    draft-ietf-mmusic-trickle-ice-sip-12
>
> The current practice is to capitalize "usage" in this situation.
> (I expect the RFC Editor can give guidance on the current
> capitalization style for RFCs.)
We switch to capitalized "Usage" as that  seems correct to me.
>
> Abstract
>
>     This document defines usage semantics for Trickle ICE with the
>     Session Initiation Protocol (SIP) and defines a new SIP Info Package.
>
> Perhaps /a new SIP Info Package/a new SIP Info Package to support this
> usage/.
>
> Table of Contents
>
> The capitalization of section titles seems to be inconsistent.
I'll have a pass through the section titles that are taken over into the ToC
>
> 1.  Introduction
>
>     It describes how ICE candidates
>     are to be exchanged incrementally with SIP INFO requests [RFC6086]
>
> Probably s/exchanged incrementally with/exchanged incrementally
> using/, as "with" can be read to mean that the SIP INFO requests are
> one party which is exchanging.
ok
>
> 4.  Incremental Signaling of ICE candidates
>
>     The following sections provide further details on how Trickle ICE
>     Agents perform the initial Offers/Answers exchange (Section 4.1),
>     perform subsequent Offers/Answers exchanges (Section 4.2) and
>     establish the INVITE dialog usage (Section 4.3) such that they can
>     incrementally trickle candidates (Section 4.4).
>
> I think you want to change "Offers/Answers" to "Offer/Answer".
Yes
>
> 4.3.1.  Establishing dialog state through reliable Offer/Answer delivery
>
> It was stated in section 4.1, "Trickle ICE Agents MUST indicate
> support for Trickle ICE by including the SIP option-tag 'trickle-ice'
> in a SIP Supported:  header field within all SIP INVITE requests and
> responses.", but it would be helpful to remind the reader in figure 3
> by showing the Supported: headers:
>
>                     Alice                         Bob
>                       |                            |
>                       |     INVITE (Offer)         |
>                       |     Supported: trickle-ice |
>                       |--------------------------->|
>                       |     183 (Answer)           |
>                       |     Supported: trickle-ice |
>                       |<---------------------------|
>
> and similarly in later figures.
>
> Something similar might be done with the "SRFLX Cand." elements to
> make the figures less cramped.
>
> 4.3.2.  Establishing dialog state through unreliable Offer/Answer
>
>     These retransmissions MUST
>     cease on receipt of an INFO request or on transmission of the Answer
>     in a 2xx response.
>
> Strictly, "a trickle-ice INFO request", as other INFO requests might
> be received as part of other mechanisms.
OK
I'll change to
"These retransmissions MUST cease on receipt of an INFO request
             carrying  a 'trickle-ice' Info Package body  or on ..."
>
> 4.3.4.  Considerations for Third Party Call Control
>
>     The peer
>     Trickle ICE Agent (the UAC) MUST send a Trickle ICE INFO request as
>     soon as they receive an unreliable provisional response (see
>     Figure 8).
>
> s/they receive/it receives/
OK
>
> 4.4.  Delivering candidates in INFO messages
>
>     Agents MUST include a pseudo "m=" line and an identification tag in a
>     "a=mid:" attribute for every "m=" line whose candidate list they
>     intend to update.  Such "a=mid:" attributes MUST immediately precede
>     the list of candidates for that specific "m=" line.  All
>     "a=candidate" or "a=end-of-candidates" attributes following an
>     "a=mid:" attribute, up until (and excluding) the next occurrence of a
>     pseudo "m=" line, pertain to the "m=" line identified by that
>     identification tag.  An "a=end-of-candidates" attribute, preceding
>     any pseudo "m=" line, indicates the end of all trickling from that
>     agent, as opposed to end of trickling for a specific "m=" line, which
>     would be indicated by a media level "a=end-of-candidates" attribute.
>
> This seems to be the first section that involves the detailed
> structure of trickle-ice INFO messages.  It would probably be useful
> here to tell the reader that there is a grammar in section 9.
OK
>
> This paragraph is very dense and you should see if you can split it in
> some way.  In particular, I think it is possible to separate the first
> part, which discusses the structure of the sdpfrag, from the second
> part, which specifies how the pseudo m= lines in the sdpfrag correlate
> with the m= lines in the offer/answer.
I will have a look into this in order to improve
>
> In addition, it seems to me that there is no requirement that the
> sdpfrag contains as many pseudo m= lines as the offer/answer contains
> m= lines, nor that the pseudo m= lines be in the same order as the m=
> lines that they pertain to (the correspondence being made via the mid
> attributes).  Since this is very different from the semantics of SDP
> proper, I think it should be pointed out explicitly.
Makes sense, I'll add a note.
>
> 5.  Initial discovery of Trickle ICE support
>
>     This makes discovery fairly straightforward for Answerers or for
>     cases where Offers need to be generated within existing dialogs
>     (i.e., when sending UPDATE or re-INVITE requests).  In both scenarios
>     prior SDP would have provided the necessary information.
>
> I think you need to expand this to note that INVITE requests are
> required to include "Supported: trickle-ice" if the UA supports
> Trickle-ICE.  This is important because a UA may receive an offerless
> re-INVITE as part of initiating a 3PCC -- the peer UA may be
> attempting to connect media between the UA and a third UA, and the
> third UA may not support Trickle ICE, even though the peer UA does.
> (See, e.g., RFC 3725 section 4.1 and RFC 7088 section 2.3.
> In this situation, the offerless re-INVITE would not contain
> "Supported:  trickle-ice" unless the peer UA knows that the third UA
> supports Trickle-ICE.  The UA, seeing the absence of "Supported:
> trickle-ice", would send a non-Trickle-ICE offer, even if the previous
> SDP had indicated support for Trickle-ICE.
Good point. I'll add an explanation along the lines of your reasoning
>
> 5.1.  Provisioning support for Trickle ICE
>
>     While the exact mechanism for allowing such provisioning is out of
>     scope here, this specification encourages trickle ICE implementations
>     to allow the option in the way they find most appropriate.
>
> What is "the option"?  Perhaps "such provisioning".
Yes. I'll change accordingly
>
> 5.2.  Trickle ICE discovery with Globally Routable User Agent URIs
>
>     This circumvents to use of forking
>     for that request.
>
> I think you want s/circumvents to/prevents the/.
OK
>
> 5.3.  Fall-back to Half Trickle
>
> Figure 11 seems to be incorrect -- since Alice is using Half-Trickle
> ICE, all her candidates are sent in the INVITE, and she shouldn't send
> any INFO requests.  But an INFO request from Alice is shown.
No, that is correct. The INFO from Alice acknowledges the receipt of the 
183 and stop retransmissions (see section 4.3.2)
>
> 6.  Considerations for RTP and RTCP multiplexing
>
>         INFO sip:alice@example.com SIP/2.0
>         ...
>         Info-Package: trickle-ice
>         Content-type: application/sdp
>         Content-Disposition: Info-Package
>         Content-length: 161
>
> Shouldn't this be "Content-type: application/trickle-ice-sdpfrag"?
Yes. Thanks for spotting this.
>
> 7.  Considerations for Media Multiplexing
>
>         INFO sip:alice@example.com SIP/2.0
>         ...
>         Info-Package: trickle-ice
>         Content-type: application/sdp
>         Content-Disposition: Info-Package
>         Content-length: 219
>
> Shouldn't this be "Content-type: application/trickle-ice-sdpfrag"?
ditto
>
> 9.2.  Grammar
>
>     A sender SHOULD stick to lower-
>     case for such grammars, but a receiver MUST treat them case-
>     insensitive.
>
> This is awkward.  Perhaps better is "A sender SHOULD use lower-case
> for attributes from such earlier grammars, but a receiver MUST treat
> them case-insensitively."
OK
>
> I don't know the practice regarding the overall grammar of SDP, but
> the grammar shown here is very rigid regarding the order of fields in
> <session-level-fields> and in <trickle-ice-attribute-fields>.  If this
> rigidity is not intended, there should be some notation on the grammar
> to show this.
I don't see any benefit in making it less rigid and I'm somewhat 
reluctant to change this at this point of the process.
>
> 10.1.  Rationale - Why INFO?
>
>     The decision to use SIP INFO requests as a candidate transport method
>     is based primarily on their lightweight nature.  Once a dialog has
>     been established, INFO requests can be exchanged both ways with no
>     restrictions on timing and frequency and no risk of collision.
>
>     On the other hand, using Offer/Answer and UPDATE requests [RFC3311]
>     would introduce the following complications:
>
> A critical fact is that the sending of Trickle ICE candidates in one
> direction is entirely uncoupled from sending candidates in the other
> direction.  Thus, the sending of candidates in each direction can be
> done by a stream of INFO requests that is not correlated with the
> stream of INFO requests in the other direction.  And since each INFO
> request is cumulatively includes the contents of all previous INFO
> requests in that direction, ordering between INFO requests need not be
> preserved.  All of this permits using largely-independent INFO
> requests.
>
> Contrarily, UPDATE or other offer/answer mechanisms assume that the
> messages in each direction are tightly coupled with messages in the
> other direction.
I like this text and will take it over, unless somebody objects.
>
> 12.2.  application/trickle-ice-sdpfrag Media Type
>
>     This section defines a new Media Type 'application/trickle-ice-
>     sdpfrag' in accordance with [RFC6838].
>
> s/This section/This document/ -- as in section 12.2.
OK
>
> This section should refer to the grammar of section 9 as the
> definition of the media type content.
>
>           SDP files are primarily UTF-8 format text.
>
> The content of application/trickle-ice-sdpfrag is not SDP, strictly
> speaking.  And as noted later in the document, not all of them are
> UTF-8.  I think you want something like this:
>
>     The media contents follow the same rules as SDP, except as noted
>     in this document.  The media contents are text, with the grammar
>     specified in section 9.
>
> Then continue with "Although the initially ...", which describes the
> character set implications of "are text".
OK, will do.
>
>           The "a=charset:"
>           attribute may be used to signal the presence of other character
>           sets in certain parts of a trickle-ice-sdpfrag body (see
>           [RFC4566]).
>
> Except that "a=charset" is not permitted by the grammar of section 9.
As above, it will fall into the extension-attribute bucket if not 
understood.

Thanks again for your thorough review and numerous proposal for improvement.
Regards
Thomas
>
> [END]
>
>
>


From nobody Thu Feb  1 14:49:21 2018
Return-Path: <thomass.stach@gmail.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 3D780126CC7; Thu,  1 Feb 2018 14:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 wfnzFIOtGCgT; Thu,  1 Feb 2018 14:49:18 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (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 5289B12EAF6; Thu,  1 Feb 2018 14:49:10 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id r71so9072921wmd.1; Thu, 01 Feb 2018 14:49:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=1r6GTDNDm2BDy8hRc1onJO6PJmDiRLhcbRoteF8cmYs=; b=bPXPfEwzsZuWMZS/36zVM0DPIc5bF4Xu5SlTfJJEiBJd0WoxWizYe3QffYJKnubDly v8/x5b8rTMgaYT0Z5J8JElv5DuRnoTwgW83jfPkmFBpOWsYfXuqub5C+TAund7E1vCrT 7KS6rxo8/iXaUMYmpJuDyXe2vg7vIWYotyM9l4oHdCWPikZ9jGjk856EFjyq+MrYODNZ V2dbzOeSBUsOvGyB7iRSbECHS1zSJPw8k0/X+eWEjCakdbMf1z/uqB/N5TUTjs3iE0wE rHQeNwijW0I8GvWeBCZkwbjEPiJJfU3YHesU8bygYM9/x5YcIdr1iFVrwV0b2OloV294 i4oA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=1r6GTDNDm2BDy8hRc1onJO6PJmDiRLhcbRoteF8cmYs=; b=eUnmdN1CeKHth/Wm1xDWv90utHjYGwdA11WSr2IGHM5BnrqmqpnbhNN5/SRCx1k3bh sMR6gw58c8GDcGgPKQVM4/GwOWTvsifhMrWtOMHLgTideXGKR5UcyhbLReoIvGQuWYT4 C1f3eDs2W0V3hzne1999C+uumbplXV3J+Rt787GVkAcX+iZa1ng4ZVhlm6ualmUAejhu Cb36oCD9X9HUTXqOWW/Zd7u8VajYn648ty12NwCgf/IlD2BJKbhHrZUtVa6vzhqTjgGF b27gtXhGITh3DPfqobGLNzqi86j8ytnfwSxh7dkMcjepAy4M75yNAhxLOf33lFXBb5rS GY9Q==
X-Gm-Message-State: AKwxytdCEnbBw30NnENmLDxoyRO8D63TRayIM+qFuYx7iRkTUgOcO+sa MQrBaRm71q1QiS6izHuHiXNswdg6mdk=
X-Google-Smtp-Source: AH8x227dtJNnYwutzybb75DfRKY6FJR/mrvqQE4EMOe0FNojmiv4M7WOZYU1uDXtvO5sIdgdDqrfUw==
X-Received: by 10.80.194.194 with SMTP id u2mr11656026edf.84.1517525348589; Thu, 01 Feb 2018 14:49:08 -0800 (PST)
Received: from [192.168.2.110] (dsl-linz7-18-136.utaonline.at. [81.189.18.136]) by smtp.googlemail.com with ESMTPSA id f11sm575661edf.26.2018.02.01.14.49.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 14:49:07 -0800 (PST)
To: Shawn Emery <shawn.emery@gmail.com>, secdir@ietf.org, draft-ietf-mmusic-trickle-ice-sip.all@tools.ietf.org, mmusic@ietf.org
References: <CAChzXmZVt4hH2KCRk-9iMAsiLT5CuncGPuEX8xw0mr=CDFsbOQ@mail.gmail.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <5aba6339-a109-9602-3266-b69aef1d08a0@gmail.com>
Date: Thu, 1 Feb 2018 23:49:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAChzXmZVt4hH2KCRk-9iMAsiLT5CuncGPuEX8xw0mr=CDFsbOQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1AF24D32A8E44FBFF09D06BA"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/9_6orA5Qi3AtwgSovogeABnmwrw>
Subject: Re: [MMUSIC] Review of draft-ietf-mmusic-trickle-ice-sip-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 01 Feb 2018 22:49:20 -0000

This is a multi-part message in MIME format.
--------------1AF24D32A8E44FBFF09D06BA
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Shawn,

first of all apologies for the delay in responding to your review.

Thanks for your effort.

Responses inline


On 2018-01-23 01:56, Shawn Emery wrote:
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the IESG.
> These comments were written primarily for the benefit of the security
> area directors. Document editors and WG chairs should treat these
> comments just like any other last call comments.
>
> This draft specifies how the Session Initiation Protocol (SIP) can use the
> non-blocking version of the Interactive Connectivity Establishment 
> (ICE) protocol,
> Trickle ICE, and defines a new registry for this usage.
>
> The security considerations section does exist and defers security 
> concerns to
> draft-ietf-mmusic-ice-sip-sdp, RFC 6086, and draft-ietf-ice-trickle.
>
> 1. draft-ietf-mmusic-ice-sip-sdp
> This will hopefully be available for a secdir review in the near 
> future, see general
> comments concern below.
> 2. RFC 6086
> 6086 prescribes S/MIME if the environment requires payloads to be 
> private and
> also suggests a digest-challenge in order to provide integrity protection.
> 3. draft-ietf-ice-trickle
> defers to draft-ietf-ice-rfc5245bis.  ice-sip should reference the 
> 5245bis draft
> directly. I won't duplicate Stephen's efforts in reviewing 5245bis.
>
> General comments:
>
> I'm concerned about the normative references to ietf-mmusic-ice-sip-sdp.
> This draft should progress before or along with any dependents.
As far as I can tell both draft will be progresses together in order to 
have the contents in-sync
>
> Editorial comments:
>
> Some of the abbreviations that are not expanded and are not listed as well
> known by the RFC Editor:
>
> SDP
> AOR
> STUN
> TURN
> GRUU (needs to be expanded in Section 3.1)
>
> making it cumbersome to follow the specification.
Sorry for that. I'll provide the necessary expansions.

Thanks again for your review!
Regards
Thomas
>
> Shawn.
> --


--------------1AF24D32A8E44FBFF09D06BA
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><tt>Shawn,</tt></p>
    <p>first of all apologies for the delay in responding to your
      review.</p>
    <p>Thanks for your effort.</p>
    <p><tt>Responses inline</tt></p>
    <br>
    <div class="moz-cite-prefix">On 2018-01-23 01:56, Shawn Emery wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAChzXmZVt4hH2KCRk-9iMAsiLT5CuncGPuEX8xw0mr=CDFsbOQ@mail.gmail.com">
      <div dir="ltr"><span style="font-size:12.8px">I have reviewed this
          document as part of the security directorate's</span><br
          style="font-size:12.8px">
        <span style="font-size:12.8px">ongoing effort to review all <span
class="gmail-m_773398563878481139m_-695948085225974410gmail-m_1623746472089625057gmail-m_-8618428600954061146gmail-m_7708740057377588207m_-5546242983760954135gmail-m_4457086233820409101gmail-m_4728537460569717949m_1367315294398481242gmail-il">IETF</span> documents
          being processed by the IESG.</span><br
          style="font-size:12.8px">
        <span style="font-size:12.8px">These comments were written
          primarily for the benefit of the security</span><br
          style="font-size:12.8px">
        <span style="font-size:12.8px">area directors. Document editors
          and WG chairs should treat these</span><br
          style="font-size:12.8px">
        <span style="font-size:12.8px">comments just like any other last
          call comments.</span><br style="font-size:12.8px">
        <div style="font-size:12.8px"><span style="font-size:12.8px"><br>
          </span></div>
        <div>
          <div style="font-size:12.8px">This draft specifies how the
            Session Initiation Protocol (SIP) can use the</div>
          <div style="font-size:12.8px">non-blocking version of the
            Interactive <span style="font-size:12.8px">Connectivity
              Establishment (ICE) protocol,</span></div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">Trickle
              ICE, and defines a new registry for this usage.</span></div>
          <div style="font-size:12.8px"><br>
          </div>
          <div style="font-size:12.8px">The security considerations
            section does exist and defers security concerns to</div>
          <div style="font-size:12.8px">draft-ietf-mmusic-ice-sip-sdp,
            RFC 6086, and draft-ietf-ice-trickle.</div>
          <div style="font-size:12.8px"><br>
          </div>
          <div style="font-size:12.8px">1. <span
              style="font-size:12.8px">draft-ietf-mmusic-ice-sip-sdp</span></div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">This
              will hopefully be available for a secdir review in the
              near future, see general</span></div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">comments
              concern below.</span></div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">2.
              RFC 6086</span></div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">6086
              prescribes S/MIME if the environment requires payloads to
              be private and</span></div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">also
              suggests a digest-challenge in order to provide integrity
              protection.</span></div>
          <div style="font-size:12.8px">3. draft-ietf-ice-trickle</div>
          <div style="font-size:12.8px">defers to
            draft-ietf-ice-rfc5245bis.  ice-sip should reference the
            5245bis draft</div>
          <div style="font-size:12.8px"><span style="font-size:12.8px">directly. 
              I won't duplicate Stephen's efforts in reviewing 5245bis.</span></div>
          <div style="font-size:12.8px"><br>
          </div>
          <div style="font-size:12.8px">General comments:</div>
          <div style="font-size:12.8px"><br>
          </div>
          <div style="font-size:12.8px">I'm concerned about the
            normative references to ietf-mmusic-ice-sip-sdp.</div>
          <div style="font-size:12.8px">This draft should progress
            before or along with any dependents.</div>
        </div>
      </div>
    </blockquote>
    As far as I can tell both draft will be progresses together in order
    to have the contents in-sync
    <blockquote type="cite"
cite="mid:CAChzXmZVt4hH2KCRk-9iMAsiLT5CuncGPuEX8xw0mr=CDFsbOQ@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div style="font-size:12.8px"><br>
          </div>
          <div style="font-size:12.8px">Editorial comments:</div>
          <div style="font-size:12.8px"><span
              style="color:rgb(0,0,0);font-size:13.3333px"><br>
            </span></div>
          <div><font color="#000000"><span style="font-size:13.3333px">Some
                of the abbreviations that are not expanded and are not
                listed as well</span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">known
                by the RFC Editor:</span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px"><br>
              </span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">SDP</span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">AOR</span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">STUN</span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">TURN<br>
              </span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">GRUU
                (needs to be expanded in Section 3.1)</span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px"><br>
              </span></font></div>
          <div><font color="#000000"><span style="font-size:13.3333px">making
                it cumbersome to follow the specification.</span></font></div>
        </div>
      </div>
    </blockquote>
    Sorry for that. I'll provide the necessary expansions.<br>
    <br>
    Thanks again for your review!<br>
    Regards<br>
    Thomas<br>
    <blockquote type="cite"
cite="mid:CAChzXmZVt4hH2KCRk-9iMAsiLT5CuncGPuEX8xw0mr=CDFsbOQ@mail.gmail.com">
      <div dir="ltr">
        <div>
          <div><font color="#000000"><span style="font-size:13.3333px"><br>
              </span></font></div>
          <div style="font-size:12.8px"><font color="#000000"><span
                style="font-size:13.3333px">Shawn.</span></font></div>
          <div style="font-size:12.8px"><font color="#000000"><span
                style="font-size:13.3333px">--</span></font></div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------1AF24D32A8E44FBFF09D06BA--


From nobody Thu Feb  1 14:49:53 2018
Return-Path: <thomass.stach@gmail.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 D848E126CC7 for <mmusic@ietfa.amsl.com>; Thu,  1 Feb 2018 14:49:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 g9l4pHLyXypb for <mmusic@ietfa.amsl.com>; Thu,  1 Feb 2018 14:49:48 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 D9AA512F28B for <mmusic@ietf.org>; Thu,  1 Feb 2018 14:49:35 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id j21-v6so2142852wmh.1 for <mmusic@ietf.org>; Thu, 01 Feb 2018 14:49:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=7OGT0G7A7yULuXLAId7XJt4dJr6jb2KhczBtka0D9Qg=; b=AUNOckhZXjX38JZfb+EGiGY7PqjeSU8Kdf9KhPkPNkuC2/jcbwZLvnEODQpQVQT302 fEqDph1R3Zo2S5oEdaGMoupBrErfulmPUWR5FfY3OW/hElhnE46boHMB8Bn03Gi+2kkA KnjFni216KL3W4hpUiNB0cY5kZlf/+JgRoBRCwjRUhAi1vTMh0DgsVhYe2K0w5gC4dqv hG2yJrtiuPJkA2xf50nXtx6LaCh7ANo1AEzCg52OR+4/tBUey0su15RnS4vRURdLifGy gxJOmKlzlSXmeEPVXoUF8pMjGG+8CA3YBbXhVNkdcsFpIzEsU4vKW5JmlKODQbJZvIcd LnKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=7OGT0G7A7yULuXLAId7XJt4dJr6jb2KhczBtka0D9Qg=; b=e+fLr+ID1PRPtqLlGG1y+WB2AkjMIqTv88bFBtlXofI2YNeWt7C/g5kkQJAPFkjMaX siYjZ4bCbN4WhkWG7kxEPn/NDgxoEsA7iYWO6ZWJ6dhKRnu0R6lv+t94oP7MqFvbiBj0 gDekOlOy599BHjJamlRHRphAJUZiO4K0mp0mcDYJyaOWWSSf86rPIbmvm+zvcUsaew+h 2IbVoI16xAzowNaiI23lKVmCevwzcVVzbbrY6+BZyoTG+bDmIjV8WfqaXtf+P+DpjZFo spPvBRSYDMZW+xzUUC6doFBx/JHRZ1sdYASFzs6pdS5xHuhfvEFPLS9w31TSfmLLtmtf RXJQ==
X-Gm-Message-State: AKwxytei0QoaZnQR5omIDs+qx6OZ2m55D1s104lzSVW3gdb2x55GmSqt 3nPZ5jAMJDM2pmKYts5tj7G+Ji0I
X-Google-Smtp-Source: AH8x224Ddd8QnnxSMMvEamrY5InjmCfyZIlSYOa3o9DP+vrs/nI44IpYu24ODsA1FbKibHCI9DAIlg==
X-Received: by 10.80.195.75 with SMTP id q11mr64474310edb.254.1517525374200; Thu, 01 Feb 2018 14:49:34 -0800 (PST)
Received: from [192.168.2.110] (dsl-linz7-18-136.utaonline.at. [81.189.18.136]) by smtp.googlemail.com with ESMTPSA id h56sm580191ede.5.2018.02.01.14.49.33 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Feb 2018 14:49:33 -0800 (PST)
References: <c325d057-ada3-e34c-7cab-7a04ccb4e734@gmail.com>
To: mmuSIC <mmusic@ietf.org>
From: Thomas Stach <thomass.stach@gmail.com>
X-Forwarded-Message-Id: <c325d057-ada3-e34c-7cab-7a04ccb4e734@gmail.com>
Message-ID: <c9615510-3e68-7ef7-e509-f0b4f2abdd3b@gmail.com>
Date: Thu, 1 Feb 2018 23:49:32 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <c325d057-ada3-e34c-7cab-7a04ccb4e734@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2Qg2bNovWumMAU0a6exF9qTVAEc>
Subject: [MMUSIC] Fwd: Re: TSV-ART Last Call review for draft-ietf-mmusic-trickle-ice-sip
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 01 Feb 2018 22:49:52 -0000

-------- Forwarded Message --------
Subject: 	Re: TSV-ART Last Call review for 
draft-ietf-mmusic-trickle-ice-sip
Date: 	Thu, 1 Feb 2018 23:47:55 +0100
From: 	Thomas Stach <thomass.stach@gmail.com>
To: 	Joerg Ott <ott@in.tum.de>, 
draft-ietf-mmusic-trickle-ice-sip.all@ietf.org, tsv-art@ietf.org, 
ietf@ietf.org <ietf@ietf.org>



Joerg,

first of all apologies for the delay in responding to your review.

Thanks for your effort.

Responses inline


On 2018-01-26 12:09, Joerg Ott wrote:
> Hi,
>
> Reviewer: Jörg Ott
> Review result: Largely ready with Issues
>
> I've reviewed this document as part of TSV-ART's ongoing effort to 
> review key IETF documents. These comments were written primarily for the
> transport area directors, but are copied to the document's authors for
> their information and to allow them to address any issues raised. When
> done at the time of IETF Last Call, the authors should consider this
> review together with any other last-call comments they receive. Please
> always CC tsv-art@ietf.org if you reply to or forward this review.
>
> The draft defines a how the Session Initiation Protocol (SIP) shall
> make use the incremental discovery and exchange of IP addresses as
> provided by tricke ICE; the main purpose is reducing call setup latency.
>
> The draft defines address the SIP aspects comprehensively with all
> necessary features.  From a transport perspective relevant is primarily
> its use the SIP INFO method for carrying updates to the collected
> addresses to notify the respective peer that further ones can now
> be tried and inform when when the address gathering is complete.
>
> Before proceeding, I note that SIP as defined in RFC 3261 and
> referenced in the draft can use UDP as a transport (which I thought
> was deprecated at some point, but couldn't find evidence to this
> end).
>
> This means that SIP message generation may lead straight to packet
> generation on the network and thus uncontrolled generation of SIP
> INFO frames will lead to uncontrolled, potentially bursty, network
> traffic.
>
> As far as I recall, this has always been an issue with SIP INFO
> for which no pacing or congestion control was defined (this is
> in contrast to SUBCRIBE/NOTIFY, for which packages need to specify
> how to rate control notifications).
>
> The document authors are aware of this but provide, IMHO, insufficient
> guidance when they write in section 10.9:
>
> 10.9.  Rate of INFO Requests
>
>    A Trickle ICE Agent with many network interfaces might create a high
>    rate of INFO requests if every newly detected candidate is trickled
>    individually without aggregation.  Implementors that are concerned
>    about loss of packets in such a case might consider aggregating ICE
>    candidates and sending INFOs only at some configurable intervals.
>
> Given that IP addresses may be gathered rapidly and poor implementations
> may send them one by one, implementers MUST be concerned with this and
> MUST rate limit the transmission of INFO messages.  There are examples
> in other SIP specs (see SUB/NOT, for example) that provide clearer
> guidance from the authors may borrow.  I acknowledge that SIP INFO
> messages are strictly unidirectional and hence one cannot map them
> naturally to determine when one was received.  So the simplest way may
> be a careful pacing.  But the group has probably thought more about
> this.
Ok, we will come up with stricter text and e.g. change to MUST.
With respect to pacing we would stick to our recommendation to send
INFOs only at some configurable intervals without specifying a concrete
value,
since an appropriate value would differ dependent on the specific network.
>
> If SIP runs on top of TCP, which is probably the standard way, this is
> not an issue for the network anymore, but it may remain one for SIP
> proxies and other intermediaries forwarding the SIP INFO messages.
> Also, an endpoint may not be able to tell that it has congestion
> controlled transport all the way.
> Minor notes:
>
> I found two cases, where the correct standards keywords (MUST) may
> be missing:
>
> Section 4.1.3, first paragraph on page 10 reads:
>
>    If the Answerer accepts to use RTCP multiplexing [RFC5761] and/or
>    exclusive RTCP multiplexing [I-D.ietf-mmusic-mux-exclusive], it will
>    include the "a=rtcp-mux" attribute in the initial Answer.
>
> will -> MUST?
We removed normative language at various places where we referred to
other specs based on the review of our AD Ben Campbell.
So, I will stick to "will"
>
> Section 4.4, bottom of page 19:
>
>    When receiving INFO requests carrying any candidates, agents will
>    therefore first identify and discard the attribute lines containing
>    candidates they have already received in previous INFO requests or in
>    the Offer/Answer exchange preceding them.  Two candidates are
>
> Will -> ???
needs to be a MUST.

Thanks again for your review.

>
>
> Best,
> Jörg
>


From nobody Thu Feb  1 19:31:46 2018
Return-Path: <session-request@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 62EE4126D45; Thu,  1 Feb 2018 19:31:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: fandreas@cisco.com, mmusic-chairs@ietf.org, mmusic@ietf.org, ben@nostrum.com
X-Test-IDTracker: no
X-IETF-IDTracker: 6.71.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151754230436.25541.3425462580313370009.idtracker@ietfa.amsl.com>
Date: Thu, 01 Feb 2018 19:31:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/XjCK1I49bXS8Na_QjWCcFaDfck8>
Subject: [MMUSIC] mmusic - New Meeting Session Request for IETF 101
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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 Feb 2018 03:31:44 -0000

A new meeting session request has just been submitted by Flemming Andreasen, a Chair of the mmusic working group.


---------------------------------------------------------
Working Group Name: Multiparty Multimedia Session Control
Area Name: Applications and Real-Time Area
Session Requester: Flemming Andreasen

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 30
Conflicts to Avoid: 
 First Priority: quic perc tls ice httpbis rtcweb avtcore sipcore dispatch payload core dots sipbrandy
 Second Priority: clue xrblock rmcat stir tram sfc regext



People who must be present:
  Ben Campbell
  Flemming Andreasen
  Bo Burman

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Sun Feb  4 13:12:23 2018
Return-Path: <worley@alum.mit.edu>
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 91939127871 for <mmusic@ietfa.amsl.com>; Sun,  4 Feb 2018 13:12:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] 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 78QRjOSWo3GA for <mmusic@ietfa.amsl.com>; Sun,  4 Feb 2018 13:12:16 -0800 (PST)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (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 998EE126DCA for <mmusic@ietf.org>; Sun,  4 Feb 2018 13:12:16 -0800 (PST)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-05v.sys.comcast.net with ESMTP id iRa9eFrcGlyqTiRaBe4PVA; Sun, 04 Feb 2018 21:12:15 +0000
Received: from hobgoblin.ariadne.com ([65.96.206.41]) by resomta-ch2-19v.sys.comcast.net with SMTP id iRa9eK3qYIZBtiRaAeRsVG; Sun, 04 Feb 2018 21:12:15 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w14LCDYK000938; Sun, 4 Feb 2018 16:12:13 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w14LCCxp000935; Sun, 4 Feb 2018 16:12:12 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Thomas Stach <thomass.stach@gmail.com>
Cc: gen-art@ietf.org, draft-ietf-mmusic-trickle-ice-sip.all@ietf.org, mmusic@ietf.org
In-Reply-To: <d8a18070-83c1-e5fa-8b5b-fa47fbed11cc@gmail.com> (thomass.stach@gmail.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 04 Feb 2018 16:12:12 -0500
Message-ID: <87shaga28j.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfGtHio4+szlPjUo9D3ugFZU7YkIjTef+nZgxJgywPT4W7hOvgacEmfmVvWERdeFulochgk81Hb+rUAwsZo0+THSMw0Yu/H42EsoIjfWwX4R4DoVorjVf xKs8PQRZ+Za98QmSzA3tOIMfwqwy+4Ua5pYiOBMZ0kVp/F35VKTtcFk05QqNxVTA/qcmkjum3LG6YGZdveO3A6P5ugD+9EMkZ+i1Psl6TsLGoCIhs/ZP8l3m DnX6V4+xerOCMRVziQGLaFLnmaT5Qz9Gm1MhfAKqbFUeRYxQ/jVoHoZUZh8t1wbT
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/YTPM395GN-uG0SQsUigeZhutV2I>
Subject: Re: [MMUSIC] Genart last call review of draft-ietf-mmusic-trickle-ice-sip-12
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 04 Feb 2018 21:12:18 -0000

Thomas Stach <thomass.stach@gmail.com> writes:
>> * The definition of application/trickle-ice-sdpfrag describes the use of
>> "a=charset" as an attribute, but the grammar of sdpfrag in section 9
>> does not permit that attribute.

> The grammar allows for using extension attributes.

Yes.

>> Figure 11 seems to be incorrect -- since Alice is using Half-Trickle
>> ICE, all her candidates are sent in the INVITE, and she shouldn't send
>> any INFO requests.  But an INFO request from Alice is shown.

> No, that is correct. The INFO from Alice acknowledges the receipt of the 
> 183 and stop retransmissions (see section 4.3.2)

Yes, I was wrong there.

>> I don't know the practice regarding the overall grammar of SDP, but
>> the grammar shown here is very rigid regarding the order of fields in
>> <session-level-fields> and in <trickle-ice-attribute-fields>.  If this
>> rigidity is not intended, there should be some notation on the grammar
>> to show this.

> I don't see any benefit in making it less rigid and I'm somewhat 
> reluctant to change this at this point of the process.

I see no objection to making the field order rigid.  I just wanted to
make sure that the given grammar matched your understanding/intention.

Dale


From nobody Sat Feb 17 16:53:48 2018
Return-Path: <ben@nostrum.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 B858A124B0A; Sat, 17 Feb 2018 16:53:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.01
X-Spam-Level: 
X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[T_RP_MATCHES_RCVD=-0.01, 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 M0HoJMHmrrsr; Sat, 17 Feb 2018 16:53:45 -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 2FCDA124234; Sat, 17 Feb 2018 16:53:42 -0800 (PST)
Received: from [10.0.1.105] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w1I0rcbp099553 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 17 Feb 2018 18:53:41 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.105]
From: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_44B871EC-8D6C-4CD9-B416-45F706EDCBC5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <D1879D95-9844-4B88-80BF-9F94820FC3B5@nostrum.com>
Date: Sat, 17 Feb 2018 18:52:50 -0600
Cc: MMUSIC <mmusic@ietf.org>
To: draft-ietf-mmusic-rid.all@ietf.org
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/2TlR_trQjpoAXPEMY-R6-_z74kI>
Subject: [MMUSIC] AD Evaluation of draft-ietf-mmusic-rid-13
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 18 Feb 2018 00:53:47 -0000

--Apple-Mail=_44B871EC-8D6C-4CD9-B416-45F706EDCBC5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

This is my AD evaluation of draft-ietf-mmusic-rid-13.

Thanks for your work on this document. It=E2=80=99s overall clear and =
readable. I have a few minor comments and nits that I think can be =
handled along with any IETF LC feedback. I will request the IETF Last =
Call shortly.

Thanks!

Ben.

=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94

Minor Comments:

=C2=A711 and subsections: Any chance of at least one example that shows =
both an offer and the resulting answer?

=C2=A76.3:  It seems like step 3 might be better characterized as =
something to the effect of =E2=80=9CThe answerer MUST include the =
=E2=80=9Crid-ID=E2=80=9D field value that was present in the associated =
line in the offer.=E2=80=9D

=C2=A712.2:  Which section(s) of 4566 give registration rules for =
registration of session-level and media-level attribute parameters?  (I =
had assumed that attribute parameter registration rules could vary per =
attribute, but could be mistaken.)  Also, doesn=E2=80=99t =E2=80=9C =
session-level and media-level=E2=80=9D attributes include all =
attributes?

Do we need to perpetuate the questionable practice of requiring a phone =
number?


Editorial/Nits:

=C2=A72:
- Please mention the update to 4855 in the introduction (in addition to =
the mention in the abstract and IANA considerations.)

- I think it would be helpful to a reader new to the subject to add a =
sentence or two around what we mean by =E2=80=9Crestrictions=E2=80=9D in =
context.

- Paragraph 1: Please consider quotes around names of existing =
attributes (e.g. =E2=80=9Crtpmap=E2=80=9D and =E2=80=9Cfmtp=E2=80=9D)

- paragraph 2: Is =E2=80=9CStreams=E2=80=9D in =E2=80=9CRTP Streams=E2=80=9D=
 capitalized on purpose?

- paragraph 3: Please don=E2=80=99t make the reader draw the conclusion =
that 7-bits means 128 distinct values.

=C2=A74:
- 3rd paragraph: =E2=80=9CTo be clear,=E2=80=9D are null words. The =
antecedent for =E2=80=9Cit=E2=80=9D is unclear in =E2=80=9C Such =
implementations MUST send it for all streams=E2=80=A6"

- 4th paragraph: First sentence is convoluted; can it be broken into =
simpler sentences?

- 5th paragraph: =E2=80=9CMAY (but need not)=E2=80=9D: Isn=E2=80=99t =
that always true for a MAY?

- paragraph starting with 'The optional =E2=80=9Cpt=3D<fmt-list> =E2=80=9C=
 =E2=80=A6 =E2=80=98: This paragraph starts a pattern of using a fields =
names as nouns. For example, =E2=80=98 The optional =E2=80=9Cpt=3D<fmt-lis=
t>=E2=80=9D =E2=80=98 rather than =E2=80=98 The optional =
=E2=80=9Cpt-<fmt-list>=E2=80=9D field=E2=80=99. I leave it to the editor =
to decide whether that=E2=80=99s okay, but I personally find it jarring.

=C2=A78.3: Extraneous comma before =E2=80=9C or other mechanisms.=E2=80=9D=


=C2=A712.1: Consider using the IESG as a contact, since WG lists come =
and go.  (I realize MMUSIC may be an exception and lots of registrations =
use it as the contact, but we should probably get away from that.). =
Also, MMUSIC has a phone number?  (I realize the template requires a =
phone number, sigh.)















--Apple-Mail=_44B871EC-8D6C-4CD9-B416-45F706EDCBC5
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

iQIzBAEBCgAdFiEExW9rpd7ez4DexOFOgFZKbJXz1A0FAlqIzmMACgkQgFZKbJXz
1A20ahAAsuSUmluJsGm87LQDC+TvF9SPCdwbTW5Ms2oH8Jmft5JCT7LC1KaeJAKc
F3wXO4/4K3+u/WDAWt3qsid9F0tnWlJSsay0cjV0UN33xuQ6fY0yvqno1kT7hUg/
89WGy1gwFad/DgeHNedvre3NFIF4ydjW1xlYE6hUN099CXEftSNqpTiuBy5LVm+M
QmVfftuzoo1kZ+Pr8FKvJUGvrrHVaW/1WoR+HMPN2T90yvciLc877m7QLpBGlaBN
JHg2ns6eZOO876xNaVleUSwG7KmsVjx5xm90y2iNGWBBpu0P5gX3OU9r51OfXo6C
SGHdUsBvJ85WTeD3DW7G53ibkHf/n11sEUbwayAd5eDxUTXFf/bcHpX0+b4cHMw+
dkdR6u44Ri3fmdmzY62zYCituTGDQ1416pG3j65JDwAQ3XPCr6Q5FvZ+7qa5Wem5
xtLBJ4yg2BXwPnL26TNZ+6Q/vYVnl18iDnlYdj85D7qClo82sut531LOMybxgWkL
26oGc4X9o8MF9GQXaNCPOi/k4AJnxON3PPhgDeJFFxFFkqbLhSi0xPNbaMStc9Ad
MTfh8N7ZCpqBIVxx6nTOYJkUyaZawGnOGPAg7dB6yWkIQJRlc0Wksz5LKjeFpcI+
00B7a4TmcMY5MweSCwEwmixdMBaidb8rIOvUZ3nrh3z7Etg7Lso=
=Zx08
-----END PGP SIGNATURE-----

--Apple-Mail=_44B871EC-8D6C-4CD9-B416-45F706EDCBC5--


From nobody Sun Feb 18 13:12:08 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A6DD5126BF6; Sun, 18 Feb 2018 13:12:00 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151898832066.27848.9749089110020862443@ietfa.amsl.com>
Date: Sun, 18 Feb 2018 13:12:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/g_re4MBlyz7gBx_Xd6Gsppl5EYA>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rfc4566bis-25.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 18 Feb 2018 21:12:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : SDP: Session Description Protocol
        Authors         : Ali Begen
                          Paul Kyzivat
                          Colin Perkins
                          Mark Handley
	Filename        : draft-ietf-mmusic-rfc4566bis-25.txt
	Pages           : 58
	Date            : 2018-02-18

Abstract:
   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 IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc4566bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-25
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rfc4566bis-25

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-25


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Feb 18 13:14:30 2018
Return-Path: <ali.begen@networked.media>
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 ED616126C83 for <mmusic@ietfa.amsl.com>; Sun, 18 Feb 2018 13:14:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 dOV9V61qvK30 for <mmusic@ietfa.amsl.com>; Sun, 18 Feb 2018 13:14:27 -0800 (PST)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 DD4CF126BF6 for <mmusic@ietf.org>; Sun, 18 Feb 2018 13:14:26 -0800 (PST)
Received: by mail-wm0-x236.google.com with SMTP id v71so11728996wmv.2 for <mmusic@ietf.org>; Sun, 18 Feb 2018 13:14:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=vV6VGkD80XZPDbLcExsmtX0/PfZDV2JPdsLS5HlXUDc=; b=bEAqRVtJn3k/BQDVH8l95Wg0H2gialnjy8a1c8tk7HNrlDfYX7fBte/lztTizh5mRp fQtZ7EgKCP8w9UgaL+d+lHAVnZhX1sku1WihcqUjBanMjfxQ27RD+YUpfhdUocBkgTKJ Zss12SfT6q4I52DpjCCsW5w5zyOeQ9QPlcA2kT2+/vZS1ExoI1UsNvnhV+aw/s0EgGNv 2xIx70UY/agrnSkZYPreNU+LAfloDzgEGH8NZ3/zvhGIXdp7Q1pcnZkshr4AmZw81lqQ 0a/68RMPgFDKHAzS7R+/1LFaitvOD5K3+pjFz1K18cCwvjxmKWrdGswpa9eaU59PTE4e DMaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=vV6VGkD80XZPDbLcExsmtX0/PfZDV2JPdsLS5HlXUDc=; b=d6uMRCc7o3g1NUkY2cyWo+QBG8CkRAnVvSXNA9asjvffIPknEXhEZ+ZQdfDCVH7TeR fUyJdAnVZNX6yB4+U05bp8+/oDhDU4LPUUGEtykZbQNMGtde/AI2WjAv4ZXyxLPls9e6 1s2/coLkDtBEyktTdXSJrROLIfcfMbRQEJJ6U6j9ZOy0Baoo/75CHy/2cHlbG9X1jpHu kNy8YNm+wRQJfhZkj8K4FALq2gyfedMC9PwTIPx1gyXSbNVaqo0/BDAIEnjtphIUVdWl bIgHQv3Tj7c6rRGJJg4+WVslvdDyu8oXGqOR8lJuTSZcMQUx62Ym2LL67uFavZGmOUw0 g2gQ==
X-Gm-Message-State: APf1xPDuWKxD1q5q3FRVq1y+IgGVgu39lBn2JodD6bWecCfcmuEyODip cfbwpEYESS4XHsQ1FCYkf5rmZRX70YeiGueWKWEqQMSM
X-Google-Smtp-Source: AH8x227kcVktlKJ9C18kmlzi+HmzHuZEe5xjlVwZz7KnE02O5223OD20rIbFvZYFBk4tBRP2ZktS/B8gATNdy8lMpDo=
X-Received: by 10.28.109.195 with SMTP id b64mr8189032wmi.13.1518988465084; Sun, 18 Feb 2018 13:14:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.153.2 with HTTP; Sun, 18 Feb 2018 13:14:24 -0800 (PST)
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Mon, 19 Feb 2018 00:14:24 +0300
Message-ID: <CAA4MczuBFR0mOF4cXf9+PbqO2Fym-_kKJXHp+Bn1D=YD+ANJ2w@mail.gmail.com>
To: mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11467db6e12dc50565830fcb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/LrJ3vPuPCPD_CoKgXCBU8V4Wids>
Subject: [MMUSIC] 4566bis update
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 18 Feb 2018 21:14:29 -0000

--001a11467db6e12dc50565830fcb
Content-Type: text/plain; charset="UTF-8"

All,

Based on Flemming's review, we made a number of changes. Here is the diff:
https://www.ietf.org/rfcdiff?url1=draft-ietf-mmusic-rfc4566bis-24&url2=draft-ietf-mmusic-rfc4566bis-25

There are still a number of open issues from Flemming's review and I will
post them in the list to get a consensus on those issues. Then, we should
be able to close this.

-acbegen

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

<div dir=3D"ltr">All,<div><br></div><div>Based on Flemming&#39;s review, we=
 made a number of changes. Here is the diff:</div><div><a href=3D"https://w=
ww.ietf.org/rfcdiff?url1=3Ddraft-ietf-mmusic-rfc4566bis-24&amp;url2=3Ddraft=
-ietf-mmusic-rfc4566bis-25">https://www.ietf.org/rfcdiff?url1=3Ddraft-ietf-=
mmusic-rfc4566bis-24&amp;url2=3Ddraft-ietf-mmusic-rfc4566bis-25</a><br></di=
v><div><br></div><div>There are still a number of open issues from Flemming=
&#39;s review and I will post them in the list to get a consensus on those =
issues. Then, we should be able to close this.</div><div><br></div><div>-ac=
begen</div></div>

--001a11467db6e12dc50565830fcb--


From nobody Tue Feb 20 07:25:40 2018
Return-Path: <ali.begen@networked.media>
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 BB68112D879 for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 07:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 4wLEuxdgToPN for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 07:25:07 -0800 (PST)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (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 2569412D883 for <mmusic@ietf.org>; Tue, 20 Feb 2018 07:25:07 -0800 (PST)
Received: by mail-wr0-x22b.google.com with SMTP id l43so15500596wrc.2 for <mmusic@ietf.org>; Tue, 20 Feb 2018 07:25:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=6FX/aGWEzkAd9YcfnUe8f9Ax+p1/c67IKq76uP9cUuo=; b=IqZsJrj0aqRyAuq2vKNV9V1psXCRy2YHUqEnVwAOomrIuCZkAkrmOeeqUAKsXxILZ4 H/dqlLLrWAC5URs1/vckdfkGbGwwm7chVbr5UQjLV6TO5Cuct8mhtOtX4OlFmLf2yjns 0f/lNZi/Qk65sOJmpmcME58PUM1GfYzn77Kbx5qPftAxuRBHvNo6XO6lr1Jev4OgcPSX SUdKZ7P/fNjeDTke9JNmjv7s/MRQRSuWeK3zpNEUW5qaM/Mz4Bj1h3wFRqDWCFXaOv9M kxH8wtX6jmNovENDuRIWQkKEUUKtQq5dMr0ii5aIffzB8W3LQaFrnV8zLWhAMlMG+Bgi RWkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=6FX/aGWEzkAd9YcfnUe8f9Ax+p1/c67IKq76uP9cUuo=; b=XAPnVpd6hY5fgCxN9JPUOKce/i/iSH0JBuK5jpAORh/TXbY7qGscs3nO+x/p2jVigH DcRAMcKXL9l1g16B5CU0KGKKWqrZctE/AnoxeNmlAvXt9nm3ka1lqSOU2ydYZyoQHsm6 a39+6cx7WDm1bqdjeM/uQbi13GL3zpLjMYk3K8bobCnAXurEAzTpwHVInRtSXpGMJQIk JjQ90CH5Enhrz7nGAyh/H52ZvpjnNRiRAVbrZ2NTs3KC29LuOefmj0EhOAoQxoC3EZRs hVNn0krhvWLDceQ06uvUYMctHkYoidwVp07pYae1fn+fQOGcM381yikiExNIWFrUQcIv 02Mg==
X-Gm-Message-State: APf1xPDKFEb9FRHBKvU+p+Bv4r1dHP5mziSV35EssbzmhinSrSwtF8dB D81iDtyNuxIED85wgSdi7PPYpggLGI8=
X-Google-Smtp-Source: AH8x224sR+74kZI+zsVMhX58Iqo+KW18yZPTDhEwwxH/4VE9v0pZcwRGCxbbLKgw9kFOj7ORP52AwQ==
X-Received: by 10.223.177.202 with SMTP id r10mr5642700wra.97.1519140305006; Tue, 20 Feb 2018 07:25:05 -0800 (PST)
Received: from [192.168.1.162] ([85.105.47.236]) by smtp.gmail.com with ESMTPSA id l73sm27067541wma.15.2018.02.20.07.25.03 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Feb 2018 07:25:04 -0800 (PST)
From: "Ali C. Begen" <ali.begen@networked.media>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
Date: Tue, 20 Feb 2018 18:25:01 +0300
To: mmusic@ietf.org
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/nnWEGtFHTYbPMFAH-arogxqMtK0>
Subject: [MMUSIC] 4566bis open issues (from Flemming's review)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Feb 2018 15:25:29 -0000

All,

The latest and greatest 4566bis draft is here:
https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-25

There are some issues raised by Flemming in his chair review, and I =
would like to get the list=E2=80=99s opinion on these.

Thanks.
-acbegen


1) Section 5.7:

   A session description MUST contain either at least one "c=3D" line in
   each media description or a single "c=3D" line at the session level.
   It MAY contain a single session-level "c=3D" line and additional "c=3D"=

   line(s) per media description, in which case the per-media values
   override the session-level settings for the respective media.

Comment: Multiple c=3D lines is only allowed for multicast, right? Can =
we clarify that here?=20

   The slash notation for multiple addresses described above MUST NOT be
   used for IP unicast addresses.

Comment: And hence you also cannot specify more than one c=3D line for a =
unicast stream, right ?

2) Section 5.8:

   The <bandwidth> is interpreted as kilobits per second by default.

Comment: What about lower layer overhead? RFC 3550 Section 6.2 specifies =
that we include UDP and IP overhead, etc. but not link layer. I believe =
this is consistent with (old) discussions on the MMUSIC mailing list as =
well and think it would be useful to clarity that here.

3) Section 5.9:

   The first and second sub-fields give the start and stop times,
   respectively, for the session.  These values are the decimal
   representation of Network Time Protocol (NTP) time values in seconds
   since 1900 [RFC5905].  To convert these values to UNIX time, subtract
   decimal 2208988800.

Comment: What is the time zone ? RFC 5905 suggests it's UTC (which makes =
sense), however the subsequent discussion in the "time zone" adjustment =
field seems to (logically) contradict that, so I'm confused.

4) Section 6.4 and 6.5:

   Syntax:
         ptime-value =3D non-zero-int-or-real
         maxptime-value =3D non-zero-int-or-real

Comment: I always thought they were integeres. The text below doesn't =
make it clear one way or the other, which it needs to.

5) Section 6.15:

   This attribute allows parameters that are specific to a particular
   format to be conveyed in a way that SDP does not have to understand
   them.  The format must be one of the formats specified for the media.
   Format-specific parameters may be any set of parameters required to
   be conveyed by SDP and given unchanged to the media tool that will
   use this format.  At most one instance of this attribute is allowed
   for each format.

Comment: Should we say something about the general convention being a =
semi-colon separate list of format parameters, as shown in the example ?

6) Section 7:

   One transport that can be used to distribute session descriptions is
   the SAP.  SAP provides both encryption and authentication mechanisms,
   but due to the nature of session announcements it is likely that
   there are many occasions where the originator of a session
   announcement cannot be authenticated because the originator is
   previously unknown to the receiver of the announcement and because no
   common public key infrastructure is available.

Comment: Does SAP provide integrity protection as well?

7) Section 8.2.2:

   The "proto" field describes the transport protocol used.  This SHOULD
   reference a standards-track protocol RFC.  This memo registers three
   values: "RTP/AVP" is a reference to [RFC3550] used under the RTP
   Profile for Audio and Video Conferences with Minimal Control
   [RFC3551] running over UDP/IP, "RTP/SAVP" is a reference to the
   Secure Real-time Transport Protocol [RFC3711], and "udp" indicates an
   unspecified protocol over UDP.

Comment: Why is the existing registration to RFC3711 not used (i.e. =
leave out here) ?

   New transport protocols SHOULD be registered with IANA.
   Registrations MUST reference an RFC describing the protocol. Such an
   RFC MAY be Experimental or Informational, although it is preferable
   that it be Standards Track.  Registrations MUST also define the rules
   by which their "fmt" namespace is managed (see below).

Comment: We have an existing registration for udptl which references =
T.38. It should actually reference RFC 7345 (seems like an IANA mistake, =
so maybe make a note of that).

8) Section 8.2.3:

Comment: Where are these registrations to be done? The IANA instructions =
and actual location of the corresponding registries are unclear.

9) Section 8.2.5:

   IANA has registered the bandwidth specifiers "CT" and "AS" with
   definitions as in Section 5.8 of this memo (these definitions update
   those in [RFC4566]).

Comment: The current IANA registration points to RFC4566 and =
mux-attributes, yet here it says the definition in 4566bis is what =
matters. Something needs to change here.


From nobody Tue Feb 20 08:18:25 2018
Return-Path: <pkyzivat@alum.mit.edu>
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 5E70912D93F for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 08:18:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 p_EJ_TOiRvRB for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 08:18:23 -0800 (PST)
Received: from alum-mailsec-scanner-1.mit.edu (alum-mailsec-scanner-1.mit.edu [18.7.68.12]) by ietfa.amsl.com (Postfix) with ESMTP id 106D212D93E for <mmusic@ietf.org>; Tue, 20 Feb 2018 08:18:22 -0800 (PST)
X-AuditID: 1207440c-e4dff70000000ab3-0a-5a8c4a4c431c
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 92.66.02739.C4A4C8A5; Tue, 20 Feb 2018 11:18:21 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w1KGIJUx032595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 20 Feb 2018 11:18:19 -0500
To: mmusic@ietf.org
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <0e0b0574-33df-c21e-0b45-cbce053e2479@alum.mit.edu>
Date: Tue, 20 Feb 2018 11:18:18 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRmVeSWpSXmKPExsUixO6iqOvr1RNl8Oy8lsXU5Y9ZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVcWHnabaCN6wVBxatZm9g3MHSxcjJISFgIrF8+ym2LkYuDiGB HUwS856eZ4FwvjNJ/Hw7EaxKWMBTYsLkxawgtoiAsMSMt3/ZQGwhASeJ5qftjCA2m4CWxJxD /8HqeQXsJS6t+csMYrMIqEp87zsN1isqkCbx6tkOZogaQYmTM5+A1XMKOEt0vH4LFmcWMJOY t/khlC0ucevJfCYIW16ieets5gmM/LOQtM9C0jILScssJC0LGFlWMcol5pTm6uYmZuYUpybr Ficn5uWlFuka6uVmluilppRuYoSEJc8Oxm/rZA4xCnAwKvHwPtDsiRJiTSwrrsw9xCjJwaQk ypui0h0lxJeUn1KZkVicEV9UmpNafIhRgoNZSYT38negHG9KYmVValE+TEqag0VJnFd1ibqf kEB6YklqdmpqQWoRTFaGg0NJgvelB9AewaLU9NSKtMycEoQ0EwcnyHAeoOEenkA1vMUFibnF mekQ+VOMlhxtK5+0MXO0XASRN168bmMWYsnLz0uVEufdBjJUAKQhozQPbiYszbxiFAd6UZj3 FMhYHmCKgpv6CmghE9DC1SKdIAtLEhFSUg2MAS3sIqHPXj37pL7UzGdJ8qdHR+zl3j053qTl xJB0hU//TPfjPR7X/7zc9T/wlqPM1IdqqRvSA+Zm3WuNt7h74mejjk151oTA2OuxhduNzmT5 zXp9RS7b1e6u/1OdyVb6Zzfus/QOyjBrF2d/J2u+9skt5q23XsT+38GhVlf1UV/Gxl3kxmJW JZbijERDLeai4kQAP7XsIQ4DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/_2nnHAutXu8ybK2nCCzY6RtdB0Y>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): ptime
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Feb 2018 16:18:24 -0000

On 2/20/18 10:25 AM, Ali C. Begen wrote:

> 4) Section 6.4 and 6.5:
> 
>     Syntax:
>           ptime-value = non-zero-int-or-real
>           maxptime-value = non-zero-int-or-real
> 
> Comment: I always thought they were integeres. The text below doesn't make it clear one way or the other, which it needs to.

I went back looking for where this came from. It appears that I have 
incomplete history. It came in in late 2015 – early 2016. If you look at 
rfc4566, it doesn’t provide *any* syntax for “packet time”.

My recollection is that somebody felt there was a need for fractional 
ptimes. (And maybe some deployed usage?) Hence we put this in.

Does anyone else have any info or memory of this?

	Thanks,
	Paul


From nobody Tue Feb 20 08:26:05 2018
Return-Path: <pkyzivat@alum.mit.edu>
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 B574912D881 for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 08:26:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 eDRr3f3VLj2P for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 08:26:02 -0800 (PST)
Received: from alum-mailsec-scanner-1.mit.edu (alum-mailsec-scanner-1.mit.edu [18.7.68.12]) by ietfa.amsl.com (Postfix) with ESMTP id CB12312D868 for <mmusic@ietf.org>; Tue, 20 Feb 2018 08:26:01 -0800 (PST)
X-AuditID: 1207440c-e35ff70000000ab3-7f-5a8c4c16cde0
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 9F.A6.02739.71C4C8A5; Tue, 20 Feb 2018 11:25:59 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w1KGPvR8000597 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 20 Feb 2018 11:25:58 -0500
To: mmusic@ietf.org
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu>
Date: Tue, 20 Feb 2018 11:25:57 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFIsWRmVeSWpSXmKPExsUixO6iqCvh0xNlsGWzgMXU5Y9ZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CV8eDcLcaCi+wVV3bVNjB+Z+1i5OSQEDCRWHp1BWMXIxeHkMAO Jol/pz+wQTjfmSRaVn9nAqkSFnCX+P/5FTOILSIgLDHj7V82EFtIwEmi+Wk7I4jNJqAlMefQ fxYQm1fAXuLG2m/sIDaLgKrE+wVrweKiAmkSr57tYIaoEZQ4OfMJWJxTwFmi4/VbsDizgJnE vM0PoWxxiVtP5jNB2PIS29/OYZ7AyD8LSfssJC2zkLTMQtKygJFlFaNcYk5prm5uYmZOcWqy bnFyYl5eapGuoV5uZoleakrpJkZIUPLsYPy2TuYQowAHoxIP7wPNnigh1sSy4srcQ4ySHExK orwpKt1RQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4L38HyvGmJFZWpRblw6SkOViUxHlVl6j7 CQmkJ5akZqemFqQWwWRlODiUJHhPewHtESxKTU+tSMvMKUFIM3FwggznARr+CqSGt7ggMbc4 Mx0if4rRkqNt5ZM2Zo6WiyDyxovXbcxCLHn5ealS4rwKIA0CIA0ZpXlwM2FJ5hWjONCLwrw/ QKp4gAkKbuoroIVMQAtXi3SCLCxJREhJNTBan++TeptifW7BzuS7TgW/kiNLY6a08Uzae0s6 deaaw5JZjoFT5nF/OJw0uzhr2ZQfDPe2n1/gJ2Byx0s7++kaq2mXophtPockhuXo3wpZnd/I GtTv0X2wYPePgEVP7Rm2WZ3tSfvTJnU8pvy++PpD/Gtjw9qWXM2cwv1o8qvfbDtE9835UbxB iaU4I9FQi7moOBEAztsjUg0DAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/qDkSqLP1Ogf-IHWY4liOVr1v-Rg>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Feb 2018 16:26:04 -0000

On 2/20/18 10:25 AM, Ali C. Begen wrote:

> 6) Section 7:
> 
>     One transport that can be used to distribute session descriptions is
>     the SAP.  SAP provides both encryption and authentication mechanisms,
>     but due to the nature of session announcements it is likely that
>     there are many occasions where the originator of a session
>     announcement cannot be authenticated because the originator is
>     previously unknown to the receiver of the announcement and because no
>     common public key infrastructure is available.
> 
> Comment: Does SAP provide integrity protection as well?

It appears that this text is carried over directly from rfc4566. But of 
course the expectations for security considerations are much higher than 
they used to be. So perhaps this should be rewritten.

Is SAP still used? Perhaps it would be better to simply remove it. If it 
is still used then can we get someone who knows it to write something?


From nobody Tue Feb 20 09:08:56 2018
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5248B120454; Tue, 20 Feb 2018 09:08:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
CC: ben@nostrum.com, mmusic@ietf.org, mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, fandreas@cisco.com, draft-ietf-mmusic-rid@ietf.org
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <151914653029.4734.6240401485579716921.idtracker@ietfa.amsl.com>
Date: Tue, 20 Feb 2018 09:08:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/aFEpi-cNzZGjWNjMLaLdQhMde5M>
Subject: [MMUSIC] Last Call: <draft-ietf-mmusic-rid-13.txt> (RTP Payload Format Restrictions) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Feb 2018 17:08:50 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'RTP Payload Format
Restrictions'
  <draft-ietf-mmusic-rid-13.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
ietf@ietf.org mailing lists by 2018-03-06. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   In this specification, we define a framework for specifying
   restrictions on RTP streams in the Session Description Protocol.
   This framework defines a new "rid" SDP attribute to unambiguously
   identify the RTP Streams within a RTP Session and restrict the
   streams' payload format parameters in a codec-agnostic way beyond
   what is provided with the regular Payload Types.

   This specification updates RFC4855 to give additional guidance on
   choice of Format Parameter (fmtp) names, and on their relation to the
   restrictions defined by this document.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rid/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rid/ballot/


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





From nobody Tue Feb 20 09:12:58 2018
Return-Path: <pkyzivat@alum.mit.edu>
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 DC41B12D9FE for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 09:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 D52rdw67_1WO for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 09:12:54 -0800 (PST)
Received: from alum-mailsec-scanner-7.mit.edu (alum-mailsec-scanner-7.mit.edu [18.7.68.19]) by ietfa.amsl.com (Postfix) with ESMTP id A8DC3127978 for <mmusic@ietf.org>; Tue, 20 Feb 2018 09:12:54 -0800 (PST)
X-AuditID: 12074413-d0dff70000000aec-01-5a8c571441f4
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id A5.A4.02796.4175C8A5; Tue, 20 Feb 2018 12:12:52 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w1KHCpXq003294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Tue, 20 Feb 2018 12:12:52 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: IETF MMUSIC WG <mmusic@ietf.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
Message-ID: <cda8eec4-a4e6-81d5-b4de-e01af09f81af@alum.mit.edu>
Date: Tue, 20 Feb 2018 12:12:51 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrNIsWRmVeSWpSXmKPExsUixO6iqCsa3hNlsKWXw2Lq8scsDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKOL/qFXPBQpGK43/usTQwNgh0MXJySAiYSBydeYOti5GLQ0hg B5PEgh372SGc70wS+9acYAKpYhPQkphz6D8LiC0s4Cvx8eIiNhBbREBF4t+7B2C2kICTRPPT dkYQm1fAXuLZtVdg9SwCqhL/L7eB1YgKpEm8eraDGaJGUOLkzCdgNZwCzhIdr9+CxZkFzCTm bX4IZYtL3HoynwnClpdo3jqbeQIj/ywk7bOQtMxC0jILScsCRpZVjHKJOaW5urmJmTnFqcm6 xcmJeXmpRbrmermZJXqpKaWbGCFhKbyDcddJuUOMAhyMSjy8DzR7ooRYE8uKK3MPMUpyMCmJ 8qaodEcJ8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuG9/B0ox5uSWFmVWpQPk5LmYFES51Vbou4n JJCeWJKanZpakFoEk5Xh4FCS4I0OA9ojWJSanlqRlplTgpBm4uAEGc4DNDwXpIa3uCAxtzgz HSJ/itGSo+XikzZmjj8PXwLJGy9etzELseTl56VKifMWgzQIgDRklObBzYSlmVeM4kAvCvNe DgWq4gGmKLipr4AWMgEtXC3SCbKwJBEhJdXAGFiRKfKExdUqevGE5c+ne0W2tGdeCHl/Vkmh Pix82Qkv1p69l98cu7TmpFZ78FSJO9nTZd/suTXRiq84POXSzh6hppD+RekhCpMrvGazaL5a xrqspm49W5lchsq1qYYPi6Zxnj414ZiWoVvkxSLTbV7/HULevyo5eeKXVMy/s/denp1Sfppl uRJLcUaioRZzUXEiAF4Si7cOAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ML1BKCmMSxWdlf7ekpo0-nnae_s>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): proto/fmt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 20 Feb 2018 17:12:56 -0000

On 2/20/18 10:25 AM, Ali C. Begen wrote:

> 7) Section 8.2.2:
> 
>     The "proto" field describes the transport protocol used.  This SHOULD
>     reference a standards-track protocol RFC.  This memo registers three
>     values: "RTP/AVP" is a reference to [RFC3550] used under the RTP
>     Profile for Audio and Video Conferences with Minimal Control
>     [RFC3551] running over UDP/IP, "RTP/SAVP" is a reference to the
>     Secure Real-time Transport Protocol [RFC3711], and "udp" indicates an
>     unspecified protocol over UDP.
> 
> Comment: Why is the existing registration to RFC3711 not used (i.e. leave out here) ?
> 
>     New transport protocols SHOULD be registered with IANA.
>     Registrations MUST reference an RFC describing the protocol. Such an
>     RFC MAY be Experimental or Informational, although it is preferable
>     that it be Standards Track.  Registrations MUST also define the rules
>     by which their "fmt" namespace is managed (see below).
> 
> Comment: We have an existing registration for udptl which references T.38. It should actually reference RFC 7345 (seems like an IANA mistake, so maybe make a note of that).
> 
> 8) Section 8.2.3:
> 
> Comment: Where are these registrations to be done? The IANA instructions and actual location of the corresponding registries are unclear.

This does seem to be a mess. The current text is pretty much the same as 
4566. I went back to rfc2327 for clarification. It said:

‘For non-RTP formats, any unregistered format name may be registered 
through the MIME-type registration process [RFC 2048]. The type given 
here is the MIME subtype only (the top-level MIME content type is 
specified by the media parameter).  The MIME type registration SHOULD 
reference a standards-track RFC which describes the transport protocol 
for this media type.  If there is an existing MIME type for this format, 
the MIME registration should be augmented to reference the transport 
specification for this media type.  If there is not an existing MIME 
type for this format, and there exists no appropriate file format, this 
should be noted in the encoding considerations as "no appropriate file 
format".’

That never seemed like a great idea since it overloaded media type 
definitions.

As best I understand, the intent is simply that “fmt” values and usage 
be defined within the document that is referenced in the IANA “proto” 
registration.

I can see being more normative about this, but then we need to have a 
discussion  about that.

	Thanks,
	Paul


From nobody Tue Feb 20 19:23:11 2018
Return-Path: <worley@alum.mit.edu>
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 7FD14128C0A for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 19:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.685
X-Spam-Level: 
X-Spam-Status: No, score=-1.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] 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 XDQIwvlMi6z3 for <mmusic@ietfa.amsl.com>; Tue, 20 Feb 2018 19:23:08 -0800 (PST)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (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 6A1A31204DA for <mmusic@ietf.org>; Tue, 20 Feb 2018 19:23:08 -0800 (PST)
Received: from resomta-ch2-19v.sys.comcast.net ([69.252.207.115]) by resqmta-ch2-09v.sys.comcast.net with ESMTP id oKzReZa89S9FqoKzreqcJB; Wed, 21 Feb 2018 03:23:07 +0000
Received: from hobgoblin.ariadne.com ([65.96.206.41]) by resomta-ch2-19v.sys.comcast.net with SMTP id oKzpevHOi3V8PoKzqeKRR1; Wed, 21 Feb 2018 03:23:06 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id w1L3N629002375; Tue, 20 Feb 2018 22:23:06 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id w1L3N6Ed002370; Tue, 20 Feb 2018 22:23:06 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "Ali C. Begen" <ali.begen@networked.media>
Cc: mmusic@ietf.org
In-Reply-To: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> (ali.begen@networked.media)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 20 Feb 2018 22:23:06 -0500
Message-ID: <87po4z9gbp.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfBDTNR2QCk/l3TqGynVn4dF5JlVZtUh5b1p9+Nox60IsOAQ5ibg8Vbeml0uKT23HJQAtOqKQsscat3lCWZBeMgIv+OcXRBNiBdNcrUh6q6QLTziJ+jg8 5ZT6FejT5RcWtWYYtrY0tLvpjj3KeNXOLHyCRNPTFgmTsJmP6uR6nGVDJYc3aDrbSzBlZTNmqtCBZDcm2k6PspvBHdx0FnM7Vx8=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/RCmz_M3Qdam-w-LnTel31pnXOH8>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Feb 2018 03:23:09 -0000

"Ali C. Begen" <ali.begen@networked.media> writes:
> 1) Section 5.7:
>
>    A session description MUST contain either at least one "c=" line in
>    each media description or a single "c=" line at the session level.
>    It MAY contain a single session-level "c=" line and additional "c="
>    line(s) per media description, in which case the per-media values
>    override the session-level settings for the respective media.
>
> Comment: Multiple c= lines is only allowed for multicast, right? Can
> we clarify that here? 

The final two paragraphs of the section are:

   Multiple addresses or "c=" lines MAY be specified on a per media
   description basis only if they provide multicast addresses for
   different layers in a hierarchical or layered encoding scheme.  They
   MUST NOT be specified for a session-level "c=" line.

   The slash notation for multiple addresses described above MUST NOT be
   used for IP unicast addresses.

> 3) Section 5.9:
>
>    The first and second sub-fields give the start and stop times,
>    respectively, for the session.  These values are the decimal
>    representation of Network Time Protocol (NTP) time values in seconds
>    since 1900 [RFC5905].  To convert these values to UNIX time, subtract
>    decimal 2208988800.
>
> Comment: What is the time zone ? RFC 5905 suggests it's UTC (which
> makes sense), however the subsequent discussion in the "time zone"
> adjustment field seems to (logically) contradict that, so I'm
> confused.

NTP time values and Unix time values are always time-zone invariant.
NTP counts seconds from 00:00 1 Jan 1900 UTC, whereas Unix counts from
00:00 1 Jan 1970 UTC, so instants designated on those time scales are
independent of any time zone.  (Neither scale counts leap seconds.)
"z=" is only used for repeating events, and specifies corrections for
when the repeats are scheduled according to a civil time system whose
offset from UTC changes.

> 4) Section 6.4 and 6.5:
>
>    Syntax:
>          ptime-value = non-zero-int-or-real
>          maxptime-value = non-zero-int-or-real
>
> Comment: I always thought they were integeres. The text below doesn't
> make it clear one way or the other, which it needs to.

Clearly, the draft intends to allow fractional values.  But why isn't
this "positive-int-or-real"? -- Negative values aren't meaningful.

However, it's not clear to me what the difference between ptime and
maxptime is.

> 5) Section 6.15:
>
>    This attribute allows parameters that are specific to a particular
>    format to be conveyed in a way that SDP does not have to understand
>    them.  The format must be one of the formats specified for the media.
>    Format-specific parameters may be any set of parameters required to
>    be conveyed by SDP and given unchanged to the media tool that will
>    use this format.  At most one instance of this attribute is allowed
>    for each format.
>
> Comment: Should we say something about the general convention being a
> semi-colon separate list of format parameters, as shown in the example?

Given that the specified syntax is "byte-string", it's probably not
worth it.

> 7) Section 8.2.2:
>
>    The "proto" field describes the transport protocol used.  This SHOULD
>    reference a standards-track protocol RFC.  This memo registers three
>    values: "RTP/AVP" is a reference to [RFC3550] used under the RTP
>    Profile for Audio and Video Conferences with Minimal Control
>    [RFC3551] running over UDP/IP, "RTP/SAVP" is a reference to the
>    Secure Real-time Transport Protocol [RFC3711], and "udp" indicates an
>    unspecified protocol over UDP.
>
> Comment: Why is the existing registration to RFC3711 not used
> (i.e. leave out here) ?

Looking at the IANA registry, the reason seems to be that RTP/AVP and
udp are registered by RFC 4566, and so have to be refreshed by the -bis
document, the authors mistakenly assumed that RTP/SAVP was also
registered by RFC 4566 and so also needed to be refreshed.  But
actually, RTP/SAVP was registered by RFC 3711 and so does not have to be
refreshed.

Dale


From nobody Wed Feb 21 12:55:52 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF8BE126C0F; Wed, 21 Feb 2018 12:55:51 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151924655174.22705.8265825268895987307@ietfa.amsl.com>
Date: Wed, 21 Feb 2018 12:55:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ghAPFJ1Vwi7BmRssm4fYpkkJnzs>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-trickle-ice-sip-13.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Feb 2018 20:55:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : A Session Initiation Protocol (SIP) Usage for Trickle ICE
        Authors         : Emil Ivov
                          Thomas Stach
                          Enrico Marocco
                          Christer Holmberg
	Filename        : draft-ietf-mmusic-trickle-ice-sip-13.txt
	Pages           : 46
	Date            : 2018-02-21

Abstract:
   The Interactive Connectivity Establishment (ICE) protocol describes a
   Network Address Translator (NAT) traversal mechanism for UDP-based
   multimedia sessions established with the Offer/Answer model.  The ICE
   extension for Incremental Provisioning of Candidates (Trickle ICE)
   defines a mechanism that allows ICE Agents to shorten session
   establishment delays by making the candidate gathering and
   connectivity checking phases of ICE non-blocking and by executing
   them in parallel.

   This document defines usage semantics for Trickle ICE with the
   Session Initiation Protocol (SIP) and defines a new SIP Info Package
   to support this usage.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-13
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-trickle-ice-sip-13

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-13


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 21 12:59:50 2018
Return-Path: <thomass.stach@gmail.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 B3B7612D95C for <mmusic@ietfa.amsl.com>; Wed, 21 Feb 2018 12:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 H1SMdW1ZVHSL for <mmusic@ietfa.amsl.com>; Wed, 21 Feb 2018 12:59:47 -0800 (PST)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 DBCE9126C0F for <mmusic@ietf.org>; Wed, 21 Feb 2018 12:59:46 -0800 (PST)
Received: by mail-lf0-x236.google.com with SMTP id l191so4331917lfe.1 for <mmusic@ietf.org>; Wed, 21 Feb 2018 12:59:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=IdXNF3eA0GSSVzGtDWwUMTk+e7kV1bIj6h9o+v65jWY=; b=rZ9hQdld+7vJz6lPOFUXvKa8NSmhDAfvk7zlPsfx/dcPvOTOwUYZtPvomSEbuJWnoO I7t2pwZH1Me6qtStq4w0gWAP6p8KCdYl9UKwIIMh/81QOGOgY1/zR1ijYmjlQ4DijZfJ N8NH/fEeVruRspSsZWE594e5RC0RIsJzJtM4veHE6UowreYSjByb3z2tN0wov/sOfUVi OivBud8kPA9UnwqBvuwIqtTkTbUAaPnzUzDdh1Oakbat2LqQheVJvwcJ3iJkB6uSS4Wf FzNsjHmW459cmhi8tstXRs3ah5QmrvgpPJmvEI7YjghbXQ9Y6GSPmprctFk4Pkqw3+K6 Ck+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=IdXNF3eA0GSSVzGtDWwUMTk+e7kV1bIj6h9o+v65jWY=; b=aHVn86fJTkVqCcNa+uk8sl9D2BL9p+Sh1mJjQzN6uAEefOPAzuLNLonMQqN8shncbJ S6zxp2qdG3xnMGdmxXeBSnr7xdAsrIXl1hR0dpRx2S83zvg2mhoeOKVe3NP0YehQKBvw sEggZ16aqXsX8yIU12YBSGMb19PNb7MlGG5gdAuBfK0MAj1+u9MNWZm8+Bh6I9nqI3cK W7OjS0z+MsfErSH1D4vjke4RBMxIg+k25e8WSRPnOmQgXc+0sbV8ALky4twGYfKRDRiC 1ia6xXMOoybgyYLb4jNFXEol7adAOCavTBEnAn2juIQiKcc3nOJ9f4oyIkj8504m3JK3 +zvA==
X-Gm-Message-State: APf1xPAnStaJWOzaqppYKvBDyYxckcYLIpkevB/ugOvgzr2xjhnT59q7 BiQn9ilHOkuEXCJfK40BSJTynWej
X-Google-Smtp-Source: AH8x22734nTPFWW19T2GgYGbAc0AgrDM5o+HZKGMMlnJWT9eOwhYRmTaY+EQe8iRUi6qjFja53tzRg==
X-Received: by 10.46.4.149 with SMTP id a21mr3449628ljf.138.1519246784909; Wed, 21 Feb 2018 12:59:44 -0800 (PST)
Received: from [192.168.2.110] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id l5sm5325212lje.58.2018.02.21.12.59.43 for <mmusic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Feb 2018 12:59:43 -0800 (PST)
To: mmusic@ietf.org
References: <151924655174.22705.8265825268895987307@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <7341d473-dafb-681a-313d-f176929b9f66@gmail.com>
Date: Wed, 21 Feb 2018 21:59:43 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <151924655174.22705.8265825268895987307@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/UPAoetv0my_EYp3ZsGGl4iGEk3A>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-trickle-ice-sip-13.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Feb 2018 20:59:49 -0000

All,


this addresses Changes from draft-ietf-mmusic-trickle-ice-sip-12
- comments from Gen-Art review, TSV-Art review and Security Directorate 
review
- Numerous editorial improvements/corrections/clarifications

Regards
Thomas


On 2018-02-21 21:55, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.
>
>          Title           : A Session Initiation Protocol (SIP) Usage for Trickle ICE
>          Authors         : Emil Ivov
>                            Thomas Stach
>                            Enrico Marocco
>                            Christer Holmberg
> 	Filename        : draft-ietf-mmusic-trickle-ice-sip-13.txt
> 	Pages           : 46
> 	Date            : 2018-02-21
>
> Abstract:
>     The Interactive Connectivity Establishment (ICE) protocol describes a
>     Network Address Translator (NAT) traversal mechanism for UDP-based
>     multimedia sessions established with the Offer/Answer model.  The ICE
>     extension for Incremental Provisioning of Candidates (Trickle ICE)
>     defines a mechanism that allows ICE Agents to shorten session
>     establishment delays by making the candidate gathering and
>     connectivity checking phases of ICE non-blocking and by executing
>     them in parallel.
>
>     This document defines usage semantics for Trickle ICE with the
>     Session Initiation Protocol (SIP) and defines a new SIP Info Package
>     to support this usage.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-13
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-trickle-ice-sip-13
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-13
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Feb 22 15:50:41 2018
Return-Path: <csp@csperkins.org>
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 070011270AC for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 15:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 XiY_21jFHXwr for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 15:50:36 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 AA875126C26 for <mmusic@ietf.org>; Thu, 22 Feb 2018 15:50:36 -0800 (PST)
Received: from [81.187.2.149] (port=34945 helo=[192.168.0.71]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1ep0dH-0004HA-2P; Thu, 22 Feb 2018 23:50:35 +0000
From: Colin Perkins <csp@csperkins.org>
Message-Id: <00A1F596-E6A8-4FA3-8797-DF11D2A73198@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FABA10B2-86CC-4C9A-A10D-A39EE1B0B7ED"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 22 Feb 2018 23:50:31 +0000
In-Reply-To: <0e0b0574-33df-c21e-0b45-cbce053e2479@alum.mit.edu>
Cc: mmusic@ietf.org
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <0e0b0574-33df-c21e-0b45-cbce053e2479@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/S_d7eNpWdp_8hMVor7Q4br0B-M8>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): ptime
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 22 Feb 2018 23:50:39 -0000

--Apple-Mail=_FABA10B2-86CC-4C9A-A10D-A39EE1B0B7ED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 20 Feb 2018, at 16:18, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> On 2/20/18 10:25 AM, Ali C. Begen wrote:
>=20
>> 4) Section 6.4 and 6.5:
>>    Syntax:
>>          ptime-value =3D non-zero-int-or-real
>>          maxptime-value =3D non-zero-int-or-real
>> Comment: I always thought they were integeres. The text below doesn't =
make it clear one way or the other, which it needs to.
>=20
> I went back looking for where this came from. It appears that I have =
incomplete history. It came in in late 2015 =E2=80=93 early 2016. If you =
look at rfc4566, it doesn=E2=80=99t provide *any* syntax for =E2=80=9Cpack=
et time=E2=80=9D.
>=20
> My recollection is that somebody felt there was a need for fractional =
ptimes. (And maybe some deployed usage?) Hence we put this in.
>=20
> Does anyone else have any info or memory of this?


It seems to have been added in 4566bis-15. Ali=E2=80=99s presentation at =
IETF 92 discusses it =
https://www.ietf.org/proceedings/92/slides/slides-92-mmusic-1.pdf =
<https://www.ietf.org/proceedings/92/slides/slides-92-mmusic-1.pdf> and =
the minutes from that meeting say:

a=3Dptime: and a=3Dmaxptime:=20
=20
Are these always integers?
Paul Kyzivat had made a suggestion to allow the use of decimal fractions =
only when the fractional part is non-zero. This definition could also be =
used for framerate; question around whether framerate could be zero.=20
=20
Jonathan Lennox liked Paul's suggestion. Framerate should not be zero.
=20
Roni Even noted that framerate of zero could be a still image.
=20
Conclusion:=20
=E2=97=8F      Nobody objects to Ali=E2=80=99s/Paul's suggestion, so =
move forward with fractional values.


See also https://trac.ietf.org/trac/mmusic/ticket/21 =
<https://trac.ietf.org/trac/mmusic/ticket/21>

(I=E2=80=99m fairly sure there were some earlier comments that triggered =
this discussion, but I can=E2=80=99t find them)

--=20
Colin Perkins
https://csperkins.org/





--Apple-Mail=_FABA10B2-86CC-4C9A-A10D-A39EE1B0B7ED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 20 Feb 2018, at 16:18, Paul Kyzivat &lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" =
class=3D"">pkyzivat@alum.mit.edu</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">On =
2/20/18 10:25 AM, Ali C. Begen wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">4) Section 6.4 and =
6.5:<br class=3D""> &nbsp;&nbsp;&nbsp;Syntax:<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ptime-value =3D =
non-zero-int-or-real<br class=3D""> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;maxptime-value =3D =
non-zero-int-or-real<br class=3D"">Comment: I always thought they were =
integeres. The text below doesn't make it clear one way or the other, =
which it needs to.<br class=3D""></blockquote><br class=3D"">I went back =
looking for where this came from. It appears that I have incomplete =
history. It came in in late 2015 =E2=80=93 early 2016. If you look at =
rfc4566, it doesn=E2=80=99t provide *any* syntax for =E2=80=9Cpacket =
time=E2=80=9D.<br class=3D""><br class=3D"">My recollection is that =
somebody felt there was a need for fractional ptimes. (And maybe some =
deployed usage?) Hence we put this in.<br class=3D""><br class=3D"">Does =
anyone else have any info or memory of this?<br =
class=3D""></div></div></blockquote></div><div class=3D""><br =
class=3D""></div>It seems to have been added in 4566bis-15. Ali=E2=80=99s =
presentation at IETF 92 discusses it&nbsp;<a =
href=3D"https://www.ietf.org/proceedings/92/slides/slides-92-mmusic-1.pdf"=
 =
class=3D"">https://www.ietf.org/proceedings/92/slides/slides-92-mmusic-1.p=
df</a>&nbsp;and the minutes from that meeting say:<div class=3D""><br =
class=3D""></div><div class=3D""><h4 style=3D"margin: 8pt 0cm 0.0001pt; =
line-height: 16.866666793823242px; font-size: 11pt; font-family: =
'Trebuchet MS'; color: rgb(102, 102, 102); font-weight: normal; =
text-decoration: underline;" class=3D"">a=3Dptime: and =
a=3Dmaxptime:&nbsp;</h4><p class=3D"normal" style=3D"margin: 0cm 0cm =
0.0001pt; line-height: 16.866666793823242px; font-size: 11pt; =
font-family: Arial;">&nbsp;</p><div style=3D"margin: 0cm 0cm 0.0001pt; =
line-height: 16.866666793823242px; font-size: 11pt; font-family: Arial;" =
class=3D"">Are these always integers?</div><div style=3D"margin: 0cm 0cm =
0.0001pt; line-height: 16.866666793823242px; font-size: 11pt; =
font-family: Arial;" class=3D"">Paul Kyzivat had made a suggestion to =
allow the use of decimal fractions only when the fractional part is =
non-zero. This definition could also be used for framerate; question =
around whether framerate could be zero.&nbsp;</div><p class=3D"normal" =
style=3D"margin: 0cm 0cm 0.0001pt; line-height: 16.866666793823242px; =
font-size: 11pt; font-family: Arial;">&nbsp;</p><div style=3D"margin: =
0cm 0cm 0.0001pt; line-height: 16.866666793823242px; font-size: 11pt; =
font-family: Arial;" class=3D"">Jonathan Lennox liked Paul's suggestion. =
Framerate should not be zero.</div><p class=3D"normal" style=3D"margin: =
0cm 0cm 0.0001pt; line-height: 16.866666793823242px; font-size: 11pt; =
font-family: Arial;">&nbsp;</p><div style=3D"margin: 0cm 0cm 0.0001pt; =
line-height: 16.866666793823242px; font-size: 11pt; font-family: Arial;" =
class=3D"">Roni Even noted that framerate of zero could be a still =
image.</div><p class=3D"normal" style=3D"margin: 0cm 0cm 0.0001pt; =
line-height: 16.866666793823242px; font-size: 11pt; font-family: =
Arial;">&nbsp;</p><div style=3D"margin: 0cm 0cm 0.0001pt; line-height: =
16.866666793823242px; font-size: 11pt; font-family: Arial;" class=3D""><b =
class=3D"">Conclusion</b>:&nbsp;</div><div style=3D"margin: 0cm 0cm =
0.0001pt 36pt; line-height: 16.866666793823242px; font-size: 11pt; =
font-family: Arial; text-indent: -18pt;" class=3D"">=E2=97=8F<span =
style=3D"font-stretch: normal; font-size: 7pt; line-height: normal; =
font-family: 'Times New Roman';" =
class=3D"">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>Nobody objects to =
Ali=E2=80=99s/Paul's suggestion, so move forward with fractional =
values.</div><div style=3D"margin: 0cm 0cm 0.0001pt 36pt; line-height: =
16.866666793823242px; font-size: 11pt; font-family: Arial; text-indent: =
-18pt;" class=3D""><br class=3D""></div><div style=3D"margin: 0cm 0cm =
0.0001pt 36pt; line-height: 16.866666793823242px; font-size: 11pt; =
font-family: Arial; text-indent: -18pt;" class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">
See also&nbsp;<a href=3D"https://trac.ietf.org/trac/mmusic/ticket/21" =
class=3D"">https://trac.ietf.org/trac/mmusic/ticket/21</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">(I=E2=80=99m fairly sure =
there were some earlier comments that triggered this discussion, but I =
can=E2=80=99t find them)<br class=3D""><br class=3D"">--&nbsp;<br =
class=3D"">Colin Perkins<br class=3D""><a href=3D"https://csperkins.org/" =
class=3D"">https://csperkins.org/</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D"">

</div>
<br class=3D""></div></div></body></html>=

--Apple-Mail=_FABA10B2-86CC-4C9A-A10D-A39EE1B0B7ED--


From nobody Thu Feb 22 15:54:52 2018
Return-Path: <csp@csperkins.org>
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 32746126C26 for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 15:54:51 -0800 (PST)
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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 2AIN_3nY1_Sj for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 15:54:49 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 AF52012422F for <mmusic@ietf.org>; Thu, 22 Feb 2018 15:54:49 -0800 (PST)
Received: from [81.187.2.149] (port=39023 helo=[192.168.0.71]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1ep0hM-00050U-8N; Thu, 22 Feb 2018 23:54:48 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu>
Date: Thu, 22 Feb 2018 23:54:47 +0000
Cc: mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Eap9bYNNrTwZwcQBjyPZ_jHGgSI>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 22 Feb 2018 23:54:51 -0000

> On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> On 2/20/18 10:25 AM, Ali C. Begen wrote:
>> 6) Section 7:
>>    One transport that can be used to distribute session descriptions =
is
>>    the SAP.  SAP provides both encryption and authentication =
mechanisms,
>>    but due to the nature of session announcements it is likely that
>>    there are many occasions where the originator of a session
>>    announcement cannot be authenticated because the originator is
>>    previously unknown to the receiver of the announcement and because =
no
>>    common public key infrastructure is available.
>> Comment: Does SAP provide integrity protection as well?
>=20
> It appears that this text is carried over directly from rfc4566. But =
of course the expectations for security considerations are much higher =
than they used to be. So perhaps this should be rewritten.
>=20
> Is SAP still used? Perhaps it would be better to simply remove it. If =
it is still used then can we get someone who knows it to write =
something?

I=E2=80=99m unconvinced SAP is still used, but in principle it provided =
integrity protection via a PGP signature. This almost certainly =
doesn=E2=80=99t meet current standards.

--=20
Colin Perkins
https://csperkins.org/





From nobody Thu Feb 22 16:03:12 2018
Return-Path: <csp@csperkins.org>
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 EDEB912D873 for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 16:03:09 -0800 (PST)
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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 lzeNuzQafJFb for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 16:03:08 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 60369126C26 for <mmusic@ietf.org>; Thu, 22 Feb 2018 16:03:08 -0800 (PST)
Received: from [81.187.2.149] (port=34398 helo=[192.168.0.71]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1ep0pO-0006Fx-Ua; Fri, 23 Feb 2018 00:03:07 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <cda8eec4-a4e6-81d5-b4de-e01af09f81af@alum.mit.edu>
Date: Fri, 23 Feb 2018 00:03:04 +0000
Cc: IETF MMUSIC WG <mmusic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <636B9089-1AF6-4818-A955-9D3E7B815678@csperkins.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <cda8eec4-a4e6-81d5-b4de-e01af09f81af@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KSv9tCuxucC2OMrJ9pmRfLFCPhE>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): proto/fmt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 23 Feb 2018 00:03:10 -0000

> On 20 Feb 2018, at 17:12, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>=20
> On 2/20/18 10:25 AM, Ali C. Begen wrote:
>=20
>> 7) Section 8.2.2:
>>    The "proto" field describes the transport protocol used.  This =
SHOULD
>>    reference a standards-track protocol RFC.  This memo registers =
three
>>    values: "RTP/AVP" is a reference to [RFC3550] used under the RTP
>>    Profile for Audio and Video Conferences with Minimal Control
>>    [RFC3551] running over UDP/IP, "RTP/SAVP" is a reference to the
>>    Secure Real-time Transport Protocol [RFC3711], and "udp" indicates =
an
>>    unspecified protocol over UDP.
>> Comment: Why is the existing registration to RFC3711 not used (i.e. =
leave out here) ?
>>    New transport protocols SHOULD be registered with IANA.
>>    Registrations MUST reference an RFC describing the protocol. Such =
an
>>    RFC MAY be Experimental or Informational, although it is =
preferable
>>    that it be Standards Track.  Registrations MUST also define the =
rules
>>    by which their "fmt" namespace is managed (see below).
>> Comment: We have an existing registration for udptl which references =
T.38. It should actually reference RFC 7345 (seems like an IANA mistake, =
so maybe make a note of that).
>> 8) Section 8.2.3:
>> Comment: Where are these registrations to be done? The IANA =
instructions and actual location of the corresponding registries are =
unclear.
>=20
> This does seem to be a mess. The current text is pretty much the same =
as 4566. I went back to rfc2327 for clarification. It said:
>=20
> =E2=80=98For non-RTP formats, any unregistered format name may be =
registered through the MIME-type registration process [RFC 2048]. The =
type given here is the MIME subtype only (the top-level MIME content =
type is specified by the media parameter).  The MIME type registration =
SHOULD reference a standards-track RFC which describes the transport =
protocol for this media type.  If there is an existing MIME type for =
this format, the MIME registration should be augmented to reference the =
transport specification for this media type.  If there is not an =
existing MIME type for this format, and there exists no appropriate file =
format, this should be noted in the encoding considerations as "no =
appropriate file format".=E2=80=99
>=20
> That never seemed like a great idea since it overloaded media type =
definitions.
>=20
> As best I understand, the intent is simply that =E2=80=9Cfmt=E2=80=9D =
values and usage be defined within the document that is referenced in =
the IANA =E2=80=9Cproto=E2=80=9D registration.
>=20
> I can see being more normative about this, but then we need to have a =
discussion  about that.


As I recall, the =E2=80=9Cfmt=E2=80=9D namespace was intended to be the =
MIME media types namespace. There was a lot of discussion about this at =
the time, although I think mostly between the AVT chairs (since this =
related to how RTP payload types were registered), the ADs, and the MIME =
people.

--=20
Colin Perkins
https://csperkins.org/





From nobody Thu Feb 22 16:17:17 2018
Return-Path: <csp@csperkins.org>
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 4A30D12D873 for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 16:17:16 -0800 (PST)
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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 ODzKd6R6HJmR for <mmusic@ietfa.amsl.com>; Thu, 22 Feb 2018 16:17:14 -0800 (PST)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 AB8A6124D37 for <mmusic@ietf.org>; Thu, 22 Feb 2018 16:17:14 -0800 (PST)
Received: from [81.187.2.149] (port=39021 helo=[192.168.0.71]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <csp@csperkins.org>) id 1ep133-0008Lo-7P; Fri, 23 Feb 2018 00:17:13 +0000
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
Date: Fri, 23 Feb 2018 00:17:11 +0000
Cc: mmusic@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DB08F76-F13D-4EF4-8D8B-4F4598157265@csperkins.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media>
To: "Ali C. Begen" <ali.begen@networked.media>
X-Mailer: Apple Mail (2.3273)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/fdGkE0pa0wnCFKd7MaAmaVIfmBg>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review)
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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, 23 Feb 2018 00:17:16 -0000

> On 20 Feb 2018, at 15:25, Ali C. Begen <ali.begen@networked.media> =
wrote:
>=20
> All,
>=20
> The latest and greatest 4566bis draft is here:
> https://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-25
>=20
> There are some issues raised by Flemming in his chair review, and I =
would like to get the list=E2=80=99s opinion on these.
>=20
> Thanks.
> -acbegen
>=20
>=20
> 1) Section 5.7:
>=20
>   A session description MUST contain either at least one "c=3D" line =
in
>   each media description or a single "c=3D" line at the session level.
>   It MAY contain a single session-level "c=3D" line and additional =
"c=3D"
>   line(s) per media description, in which case the per-media values
>   override the session-level settings for the respective media.
>=20
> Comment: Multiple c=3D lines is only allowed for multicast, right? Can =
we clarify that here?=20
>=20
>   The slash notation for multiple addresses described above MUST NOT =
be
>   used for IP unicast addresses.
>=20
> Comment: And hence you also cannot specify more than one c=3D line for =
a unicast stream, right ?
>=20
> 2) Section 5.8:
>=20
>   The <bandwidth> is interpreted as kilobits per second by default.
>=20
> Comment: What about lower layer overhead? RFC 3550 Section 6.2 =
specifies that we include UDP and IP overhead, etc. but not link layer. =
I believe this is consistent with (old) discussions on the MMUSIC =
mailing list as well and think it would be useful to clarity that here.

That matches my understanding.

> 3) Section 5.9:
>=20
>   The first and second sub-fields give the start and stop times,
>   respectively, for the session.  These values are the decimal
>   representation of Network Time Protocol (NTP) time values in seconds
>   since 1900 [RFC5905].  To convert these values to UNIX time, =
subtract
>   decimal 2208988800.
>=20
> Comment: What is the time zone ? RFC 5905 suggests it=E2=80=99s UTC =
(which makes sense), however the subsequent discussion in the "time =
zone" adjustment field seems to (logically) contradict that, so I'm =
confused.

They=E2=80=99re NTP timestamps. If I understand correctly, NTP is tied =
to UTC.

> 4) Section 6.4 and 6.5:
>=20
>   Syntax:
>         ptime-value =3D non-zero-int-or-real
>         maxptime-value =3D non-zero-int-or-real
>=20
> Comment: I always thought they were integeres. The text below doesn't =
make it clear one way or the other, which it needs to.
>=20
> 5) Section 6.15:
>=20
>   This attribute allows parameters that are specific to a particular
>   format to be conveyed in a way that SDP does not have to understand
>   them.  The format must be one of the formats specified for the =
media.
>   Format-specific parameters may be any set of parameters required to
>   be conveyed by SDP and given unchanged to the media tool that will
>   use this format.  At most one instance of this attribute is allowed
>   for each format.
>=20
> Comment: Should we say something about the general convention being a =
semi-colon separate list of format parameters, as shown in the example ?

They=E2=80=99re MIME media type parameters, and therefore my definition =
semicolon separated. If that=E2=80=99s not clear, we should specify it.

> 6) Section 7:
>=20
>   One transport that can be used to distribute session descriptions is
>   the SAP.  SAP provides both encryption and authentication =
mechanisms,
>   but due to the nature of session announcements it is likely that
>   there are many occasions where the originator of a session
>   announcement cannot be authenticated because the originator is
>   previously unknown to the receiver of the announcement and because =
no
>   common public key infrastructure is available.
>=20
> Comment: Does SAP provide integrity protection as well?

Yes.

> 7) Section 8.2.2:
>=20
>   The "proto" field describes the transport protocol used.  This =
SHOULD
>   reference a standards-track protocol RFC.  This memo registers three
>   values: "RTP/AVP" is a reference to [RFC3550] used under the RTP
>   Profile for Audio and Video Conferences with Minimal Control
>   [RFC3551] running over UDP/IP, "RTP/SAVP" is a reference to the
>   Secure Real-time Transport Protocol [RFC3711], and "udp" indicates =
an
>   unspecified protocol over UDP.
>=20
> Comment: Why is the existing registration to RFC3711 not used (i.e. =
leave out here) ?
>=20
>   New transport protocols SHOULD be registered with IANA.
>   Registrations MUST reference an RFC describing the protocol. Such an
>   RFC MAY be Experimental or Informational, although it is preferable
>   that it be Standards Track.  Registrations MUST also define the =
rules
>   by which their "fmt" namespace is managed (see below).
>=20
> Comment: We have an existing registration for udptl which references =
T.38. It should actually reference RFC 7345 (seems like an IANA mistake, =
so maybe make a note of that).
>=20
> 8) Section 8.2.3:
>=20
> Comment: Where are these registrations to be done? The IANA =
instructions and actual location of the corresponding registries are =
unclear.

For RTP, they don=E2=80=99t need to be registered since the fmt value is =
the RTP payload type (see also RFC 3555).

For udp, you register the MIME media type following RFC 4288.

For anything else, you do as specified in the RFC that defines that =
=E2=80=9Cproto=E2=80=9D value.=20

This seems clearly specified.

> 9) Section 8.2.5:
>=20
>   IANA has registered the bandwidth specifiers "CT" and "AS" with
>   definitions as in Section 5.8 of this memo (these definitions update
>   those in [RFC4566]).
>=20
> Comment: The current IANA registration points to RFC4566 and =
mux-attributes, yet here it says the definition in 4566bis is what =
matters. Something needs to change here.
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic



--=20
Colin Perkins
https://csperkins.org/





From nobody Sat Feb 24 06:04:14 2018
Return-Path: <magnus.westerlund@ericsson.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 1789F126CBF for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 06:04:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level: 
X-Spam-Status: No, score=-4.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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
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 ebaTCMg6vUNg for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 06:04:10 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 28C3D12D883 for <mmusic@ietf.org>; Sat, 24 Feb 2018 06:04:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1519481048; 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=fJW5KS6bpnfULhb+aJKcui1Ti9Sjq70KN2fK4QOx1lY=; b=gnQUNOqC84zB8Fc0aIaLWjWY4tO1UyJqi+dJwSduyECsZ9w9zj6Fr3HyklJl8h08 AIpOZQB8tK79XHTQ9E6Ip0GFxB/xRIYGRwwk1FXv++ldMVhQXrqaNDk4bFX/35KV PqmRUu0mX9UbANq402/wwhgG3jLuhAOJXVHIvoWqaY0=;
X-AuditID: c1b4fb3a-728f89c0000067b4-8e-5a9170d8b7c1
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.183.60]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id D4.28.26548.8D0719A5; Sat, 24 Feb 2018 15:04:08 +0100 (CET)
Received: from [100.94.46.101] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.60) with Microsoft SMTP Server (TLS) id 14.3.352.0; Sat, 24 Feb 2018 15:04:07 +0100
To: Colin Perkins <csp@csperkins.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
CC: <mmusic@ietf.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <0e0b0574-33df-c21e-0b45-cbce053e2479@alum.mit.edu> <00A1F596-E6A8-4FA3-8797-DF11D2A73198@csperkins.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <522c3733-4b5f-b886-5b98-cd6fb1567a11@ericsson.com>
Date: Sat, 24 Feb 2018 15:04:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <00A1F596-E6A8-4FA3-8797-DF11D2A73198@csperkins.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms020406060605000902020106"
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFIsWRmVeSWpSXmKPExsUyM2K7je6NgolRBiemylgsf3mC0WLq8scs Fis2HGB1YPb4+/4Dk8e0+/fZPJYs+ckUwBzFZZOSmpNZllqkb5fAlTF5XSN7wfU5jBV7Hl1l b2Cc1sjYxcjBISFgInHnrXMXIxeHkMBhRondl1YwQTibGCX615xh7mLk5BAW8JSYMHkxK4gt IuAt0b/hDDuIzSwgKtE+8TUbRMN6oIanC8ESbAIWEjd/NLKB2LwC9hLPdvYygdgsAqoSuzZM A6sRFYiRmPpxIytEjaDEyZlPWEBsTgFHict3WlhBhjILdDNKfD/xCaxISEBboqGpA8yWEFCS uD7vOssERoFZSPpnIeuZBXZhmMTPsxtZIGxxiaYvK6HiZhLzNj9khrC1JZYtfA1kcwDZahLL WpVQhUFsa4kZvw6yQdiKElO6H7JD2KYSr49+ZISwjSTe7WlkX8DIs4pRtDi1uDg33chIL7Uo M7m4OD9PLy+1ZBMjMBYPbvlttYPx4HPHQ4wCHIxKPLzBWROjhFgTy4orcw8xqgDNebRh9QVG KZa8/LxUJRHeh4xAad6UxMqq1KL8+KLSnNTiQ4zSHCxK4rxOaRZRQgLpiSWp2ampBalFMFkm Dk6pBka5lbt4V9xZ/6Cey9Fpd+rZ95uS4m6xa3v+Pm3DdSDfqGPlVJvWeyxB6j61eX4KDzUy 5O8rrH5ZZ++3/d4TjtNaUU+lnmpwWrCrZxzUVivR0G18yii2ft+Lazv9X97exRx23uTunfc3 71j4qbV4PTTZPSMw0GGf/JTJ744VJ266xLh7xeppq3YpsRRnJBpqMRcVJwIAkmc24s0CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/CHIlqDuCeD7fvKK-oIZT1n1TM6Y>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): ptime
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Feb 2018 14:04:13 -0000

--------------ms020406060605000902020106
Content-Type: multipart/alternative;
 boundary="------------25B7F511BE2287F2A168ECCD"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------25B7F511BE2287F2A168ECCD
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,

I very split about this change. From the point of an RTP payload format=20
that defines the packetization time, using fraction would be very nice.=20
And also on that level it is an minor interoperability issue to allow=20
these, the main problem is if the basic SDP parser throws a fit.

However, from my perspective the issue with ptime is that this is an=20
payload format specific parameter that got overloaded onto a single per=20
media stream instance. This becomes problematic as soon as one have=20
multiple codes with none matching values, like if one like single frame=20
audio payloads but have one 20 ms codec and one 30 ms one, what do one=20
use, and how is it interpreted. And what happens if one would state=20
ptime=3D22.5 when one have also a 22.5 frame length codec.

I wished we faced this issue earlier and changed the recommendation to=20
leave the ptime and maxptime values in that a=3Dftmp lines and deprecated=
=20
the use on media stream level.

I think both ptime and maxptime needs text on the fact that the value=20
may not be matching the possible values for all of the payload formats.=20
Especially if the value is a fractional one.

Cheers

Magnus Westerlund


Den 2018-02-23 kl. 00:50, skrev Colin Perkins:
>
>> On 20 Feb 2018, at 16:18, Paul Kyzivat <pkyzivat@alum.mit.edu=20
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>
>> On 2/20/18 10:25 AM, Ali C. Begen wrote:
>>
>>> 4) Section 6.4 and 6.5:
>>> =C2=A0=C2=A0=C2=A0Syntax:
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0ptime-value =3D=
 non-zero-int-or-real
>>> =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0maxptime-value =
=3D non-zero-int-or-real
>>> Comment: I always thought they were integeres. The text below=20
>>> doesn't make it clear one way or the other, which it needs to.
>>
>> I went back looking for where this came from. It appears that I have=20
>> incomplete history. It came in in late 2015 =E2=80=93 early 2016. If y=
ou look=20
>> at rfc4566, it doesn=E2=80=99t provide *any* syntax for =E2=80=9Cpacke=
t time=E2=80=9D.
>>
>> My recollection is that somebody felt there was a need for fractional =

>> ptimes. (And maybe some deployed usage?) Hence we put this in.
>>
>> Does anyone else have any info or memory of this?
>
> It seems to have been added in 4566bis-15. Ali=E2=80=99s presentation a=
t IETF=20
> 92 discusses it=20
> https://www.ietf.org/proceedings/92/slides/slides-92-mmusic-1.pdf=C2=A0=
and=20
> the minutes from that meeting say:
>
>
>         a=3Dptime: and a=3Dmaxptime:
>
> Are these always integers?
> Paul Kyzivat had made a suggestion to allow the use of decimal=20
> fractions only when the fractional part is non-zero. This definition=20
> could also be used for framerate; question around whether framerate=20
> could be zero.
>
> Jonathan Lennox liked Paul's suggestion. Framerate should not be zero.
>
> Roni Even noted that framerate of zero could be a still image.
>
> *Conclusion*:
> =E2=97=8FNobody objects to Ali=E2=80=99s/Paul's suggestion, so move for=
ward with=20
> fractional values.
>
>
> See also https://trac.ietf.org/trac/mmusic/ticket/21
>
> (I=E2=80=99m fairly sure there were some earlier comments that triggere=
d this=20
> discussion, but I can=E2=80=99t find them)
>
> --=20
> Colin Perkins
> https://csperkins.org/
>
>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

--=20

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


--------------25B7F511BE2287F2A168ECCD
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi,</p>
    <p>I very split about this change. From the point of an RTP payload
      format that defines the packetization time, using fraction would
      be very nice. And also on that level it is an minor
      interoperability issue to allow these, the main problem is if the
      basic SDP parser throws a fit.</p>
    <p>However, from my perspective the issue with ptime is that this is
      an payload format specific parameter that got overloaded onto a
      single per media stream instance. This becomes problematic as soon
      as one have multiple codes with none matching values, like if one
      like single frame audio payloads but have one 20 ms codec and one
      30 ms one, what do one use, and how is it interpreted. And what
      happens if one would state ptime=3D22.5 when one have also a 22.5
      frame length codec.=C2=A0</p>
    <p>I wished we faced this issue earlier and changed the
      recommendation to leave the ptime and maxptime values in that
      a=3Dftmp lines and deprecated the use on media stream level. <br>
    </p>
    <p>I think both ptime and maxptime needs text on the fact that the
      value may not be matching the possible values for all of the
      payload formats. Especially if the value is a fractional one. <br>
    </p>
    <p>Cheers</p>
    <p>Magnus Westerlund<br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">Den 2018-02-23 kl. 00:50, skrev Colin
      Perkins:<br>
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:00A1F596-E6A8-4FA3-8797-DF11D2A73198@csperkins.org">
      <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Du=
tf-8">
      <br class=3D"">
      <div>
        <blockquote type=3D"cite" class=3D"">
          <div class=3D"">On 20 Feb 2018, at 16:18, Paul Kyzivat &lt;<a
              href=3D"mailto:pkyzivat@alum.mit.edu" class=3D""
              moz-do-not-send=3D"true">pkyzivat@alum.mit.edu</a>&gt;
            wrote:</div>
          <br class=3D"Apple-interchange-newline">
          <div class=3D"">
            <div class=3D"">On 2/20/18 10:25 AM, Ali C. Begen wrote:<br
                class=3D"">
              <br class=3D"">
              <blockquote type=3D"cite" class=3D"">4) Section 6.4 and 6.5=
:<br
                  class=3D"">
                =C2=A0=C2=A0=C2=A0Syntax:<br class=3D"">
                =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0pti=
me-value =3D non-zero-int-or-real<br class=3D"">
                =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0max=
ptime-value =3D non-zero-int-or-real<br
                  class=3D"">
                Comment: I always thought they were integeres. The text
                below doesn't make it clear one way or the other, which
                it needs to.<br class=3D"">
              </blockquote>
              <br class=3D"">
              I went back looking for where this came from. It appears
              that I have incomplete history. It came in in late 2015 =E2=
=80=93
              early 2016. If you look at rfc4566, it doesn=E2=80=99t prov=
ide
              *any* syntax for =E2=80=9Cpacket time=E2=80=9D.<br class=3D=
"">
              <br class=3D"">
              My recollection is that somebody felt there was a need for
              fractional ptimes. (And maybe some deployed usage?) Hence
              we put this in.<br class=3D"">
              <br class=3D"">
              Does anyone else have any info or memory of this?<br
                class=3D"">
            </div>
          </div>
        </blockquote>
      </div>
      <div class=3D""><br class=3D"">
      </div>
      It seems to have been added in 4566bis-15. Ali=E2=80=99s presentati=
on at
      IETF 92 discusses it=C2=A0<a
        href=3D"https://www.ietf.org/proceedings/92/slides/slides-92-mmus=
ic-1.pdf"
        class=3D"" moz-do-not-send=3D"true">https://www.ietf.org/proceedi=
ngs/92/slides/slides-92-mmusic-1.pdf</a>=C2=A0and
      the minutes from that meeting say:
      <div class=3D""><br class=3D"">
      </div>
      <div class=3D"">
        <h4 style=3D"margin: 8pt 0cm 0.0001pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: 'Trebuchet
          MS'; color: rgb(102, 102, 102); font-weight: normal;
          text-decoration: underline;" class=3D"">a=3Dptime: and
          a=3Dmaxptime:=C2=A0</h4>
        <p class=3D"normal" style=3D"margin: 0cm 0cm 0.0001pt; line-heigh=
t:
          16.866666793823242px; font-size: 11pt; font-family: Arial;">=C2=
=A0</p>
        <div style=3D"margin: 0cm 0cm 0.0001pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;"
          class=3D"">Are these always integers?</div>
        <div style=3D"margin: 0cm 0cm 0.0001pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;"
          class=3D"">Paul Kyzivat had made a suggestion to allow the use
          of decimal fractions only when the fractional part is
          non-zero. This definition could also be used for framerate;
          question around whether framerate could be zero.=C2=A0</div>
        <p class=3D"normal" style=3D"margin: 0cm 0cm 0.0001pt; line-heigh=
t:
          16.866666793823242px; font-size: 11pt; font-family: Arial;">=C2=
=A0</p>
        <div style=3D"margin: 0cm 0cm 0.0001pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;"
          class=3D"">Jonathan Lennox liked Paul's suggestion. Framerate
          should not be zero.</div>
        <p class=3D"normal" style=3D"margin: 0cm 0cm 0.0001pt; line-heigh=
t:
          16.866666793823242px; font-size: 11pt; font-family: Arial;">=C2=
=A0</p>
        <div style=3D"margin: 0cm 0cm 0.0001pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;"
          class=3D"">Roni Even noted that framerate of zero could be a
          still image.</div>
        <p class=3D"normal" style=3D"margin: 0cm 0cm 0.0001pt; line-heigh=
t:
          16.866666793823242px; font-size: 11pt; font-family: Arial;">=C2=
=A0</p>
        <div style=3D"margin: 0cm 0cm 0.0001pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;"
          class=3D""><b class=3D"">Conclusion</b>:=C2=A0</div>
        <div style=3D"margin: 0cm 0cm 0.0001pt 36pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;
          text-indent: -18pt;" class=3D"">=E2=97=8F<span style=3D"font-st=
retch:
            normal; font-size: 7pt; line-height: normal; font-family:
            'Times New Roman';" class=3D"">=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0</span>Nobody objects to
          Ali=E2=80=99s/Paul's suggestion, so move forward with fractiona=
l
          values.</div>
        <div style=3D"margin: 0cm 0cm 0.0001pt 36pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;
          text-indent: -18pt;" class=3D""><br class=3D"">
        </div>
        <div style=3D"margin: 0cm 0cm 0.0001pt 36pt; line-height:
          16.866666793823242px; font-size: 11pt; font-family: Arial;
          text-indent: -18pt;" class=3D""><br class=3D"">
        </div>
        <div class=3D"">
          <div class=3D"">
            See also=C2=A0<a
              href=3D"https://trac.ietf.org/trac/mmusic/ticket/21"
              class=3D"" moz-do-not-send=3D"true">https://trac.ietf.org/t=
rac/mmusic/ticket/21</a></div>
          <div class=3D""><br class=3D"">
          </div>
          <div class=3D"">(I=E2=80=99m fairly sure there were some earlie=
r
            comments that triggered this discussion, but I can=E2=80=99t =
find
            them)<br class=3D"">
            <br class=3D"">
            --=C2=A0<br class=3D"">
            Colin Perkins<br class=3D"">
            <a href=3D"https://csperkins.org/" class=3D""
              moz-do-not-send=3D"true">https://csperkins.org/</a><br
              class=3D"">
            <br class=3D"">
            <br class=3D"">
            <br class=3D"">
          </div>
          <br class=3D"">
        </div>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
mmusic mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:mmusic@ietf.org">mmu=
sic@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20

Magnus Westerlund=20

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"moz-txt-link-abbreviate=
d" href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@erics=
son.com</a>
----------------------------------------------------------------------</p=
re>
  </body>
</html>

--------------25B7F511BE2287F2A168ECCD--

--------------ms020406060605000902020106
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-kryptografisk signatur

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DNEwggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJ
BgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNV
BAoMCEVyaWNzc29uMRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJ
ARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+
laqg5eXTqonqnzT9ykEGL2dx9mBT+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJ
HGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iV
IiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpigGFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36o
gzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkrbdmdnjKGrYSnJigmxw14pJugxL/Vb2Ee
VcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDov
L2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNybDCBggYI
KwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29t
MEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29u
bmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rlcmx1bmRAZXJp
Y3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0
dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3
DQEBCwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4Q
ihhoQR3cvhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXD
yF9mhWYbSAkJyx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6
H3zO3nsq++KBmsOiSKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvE
lup5n7l864FqxnC2friDo4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl
60rmc8SJlt6QXKw0wXEOE1MubauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwD
ig3SZi1qP7D/Ds4V+JLIjjUJc25l9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8K
v7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLCQaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3
UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Zla71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzY
VBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd//n4YbY2QhDCCBsIwggSqoAMCAQICEFO4
foPhnJkok7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUx
MDI3MTIxNjQ2WjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMM
HEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDs8t8AALhQ8qe72FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfS
Tm+7meisbhkqUXkL7fFzoe4iIZCh/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbX
ILlLhRummTdDdxhVW4Leo0awEhfLf98MvWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfp
VdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmdvkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2
PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2
H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP1UrZaEIFu+hO+s0Nm8sOUMa4TlG4
rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0FdQDEzQlnF/h1L4AK1MOkX
1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA+yrrplCh/kYvSBjv
Zibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUrrvijPDaGK5FN
VSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQwgYoGCCsG
AQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEu
Y29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3Js
LTMudHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1Ud
JQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7
GZ6XnHasID3Y3OORauPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0G
CSqGSIb3DQEBCwUAA4ICAQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDU
JQEPRs5QtaZiObNHCZ7mmSNMVek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHG
vw5RY6vRlZrj0uKvdASzYL4KMaB7m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYn
nl2t3D3oBX2NZCQysshUcqRdUbkS13HTCIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwf
ixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNMMbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ8
5AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4Hd
Dc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0RLCi+4d4/47Zs3DC3PUNOxdOE
EHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZfAFM4HoHz8K2BZRaHKWhd
3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqGahxlHYzl/QyEG/du
jp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGCAzswggM3AgEB
MFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMA0GCWCGSAFlAwQCAQUA
oIIBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAyMjQx
NDA0MDdaMC8GCSqGSIb3DQEJBDEiBCCbZpjk/+yIeK4NSwnkelAJe1H4GyCMinHBjzss+pVD
pjBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjEl
MCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBlrrZreXF5
7TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMGwGCyqGSIb3DQEJEAILMV2gWzBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nz
b24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62
a3lxee0wDQYJKoZIhvcNAQEBBQAEggEATl3Ji2Csjd4fBerhrQQkzSkXb+nNYO3M5VS2ZA6a
h90wn6SkrZw8ycnbk/tecoCXUiP4gf8VS1ji2Ww50WiTRdNBPXguJoMBlEW5TB1nOpr5HBSN
Fydpszc5VtZASefibD4SPfzJmu0AzAEXdbHS3+UBnM6+6SjZvCLtGAjoAh/sleiqMyn35Tbk
WPyV5yWchHuUNaAa0ZSHuf+Z+/HIqBEDpHbCQF91NSfgDR3f0/WZbBOe5NYFVD2RPHbfWrLS
LM66EpRPpKJVG921rHiH6x/mnkZiAU1LoKgncknAr8qky4X++jrT8g5noRFRr1nH7znCxnrC
pNz/iOw4GNY/9gAAAAAAAA==
--------------ms020406060605000902020106--


From nobody Sat Feb 24 06:09:26 2018
Return-Path: <magnus.westerlund@ericsson.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 B808312D87F for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 06:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.319
X-Spam-Level: 
X-Spam-Status: No, score=-4.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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
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 miHwgoz-5m2W for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 06:09:21 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 C06E9129C59 for <mmusic@ietf.org>; Sat, 24 Feb 2018 06:09:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1519481359; 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=C3f6vdoQB1UI4gydgexY7CovOq+ZpVD1rg8XID4kUhg=; b=fYYeZt8Sc+fCImo2DQxKUILq67tGsjvb3OQy/JeS2advjPmP67+ImM5YuI4kcJzV 5+5IdhG/8BM05qos0U1xsGnofRQTqldo/GzuKJzTcwvCIceY/GlHkr1EPHvIJqb0 TxBQZyjMzR6hFi6bpvTp49IIknHe89FuJ8lYGWOdrcs=;
X-AuditID: c1b4fb3a-728f89c0000067b4-ee-5a91720e0fd7
Received: from ESESSHC006.ericsson.se (Unknown_Domain [153.88.183.36]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 01.88.26548.E02719A5; Sat, 24 Feb 2018 15:09:19 +0100 (CET)
Received: from [100.94.46.101] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.36) with Microsoft SMTP Server (TLS) id 14.3.352.0; Sat, 24 Feb 2018 15:09:08 +0100
To: Colin Perkins <csp@csperkins.org>, "Ali C. Begen" <ali.begen@networked.media>
CC: <mmusic@ietf.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <9DB08F76-F13D-4EF4-8D8B-4F4598157265@csperkins.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <78aa5f97-bb84-b8c0-79df-b4130532d31c@ericsson.com>
Date: Sat, 24 Feb 2018 15:09:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <9DB08F76-F13D-4EF4-8D8B-4F4598157265@csperkins.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms050500010006080706000601"
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2K7ii5/0cQog4dPWC0OfnvBbLH85QlG i6nLH7M4MHtMu3+fzWPJkp9MHruWXWAPYI7isklJzcksSy3St0vgylj4TK7gXGjF6T0XGRsY r/p0MXJySAiYSCzc/ZSxi5GLQ0jgMKPEpxuv2CGcTYwSCy42MoJUCQuESUzfe4IZxBYRCJZY 0PifBcRmFhCVaJ/4mg3EFhKolOhe9B6shk3AQuLmj0awOK+AvcSBbZfB4iwCqhJznr8Emykq ECMx9eNGVogaQYmTM5+AzeQUcJRYPu0JM8T8bkaJtb8cIeZrSzQ0dbBCXK0kcX3edZYJjAKz kLTPQtICYYdJvDr3ACouLtH0ZSUrhG0mMW/zQ2YIW1ti2cLXQDYHkK0msaxVCVUYxLaWmPHr IBuErSgxpfshO4RtKvH66EdGCNtI4t2eRvYFjDyrGEWLU4uLc9ONjPRSizKTi4vz8/TyUks2 MQIj8OCW31Y7GA8+dzzEKMDBqMTDG5w1MUqINbGsuDL3EKMK0JxHG1ZfYJRiycvPS1US4X3I CJTmTUmsrEotyo8vKs1JLT7EKM3BoiTO65RmESUkkJ5YkpqdmlqQWgSTZeLglGpg5HS7Y29X +Cp+gz9T9T3FuOO+tzJOTdxQIBpl9Fr04nlOhablkVdsO3ZvX3Nj94pV5+fOWbaScQX/ytCJ r1iy9m0vN2nitv3heDnmS9tcjQ/pnuvY7V/NFtBImPXKZEJb1hvBRkPF0hOzlX5Ncfl2yqt9 4651i9e89ptRWT6ZIflgbtrNuqNyLkosxRmJhlrMRcWJAGhIbvfIAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/n0vbiNcXqclKTkOtMNVDuZHBAf4>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): Bandwidth values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Feb 2018 14:09:23 -0000

--------------ms050500010006080706000601
Content-Type: multipart/alternative;
 boundary="------------EBAA99B0C13FE404F4D374C5"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------EBAA99B0C13FE404F4D374C5
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable



Den 2018-02-23 kl. 01:17, skrev Colin Perkins:
>> 2) Section 5.8:
>>
>>    The <bandwidth> is interpreted as kilobits per second by default.
>>
>> Comment: What about lower layer overhead? RFC 3550 Section 6.2 specifi=
es that we include UDP and IP overhead, etc. but not link layer. I believ=
e this is consistent with (old) discussions on the MMUSIC mailing list as=
 well and think it would be useful to clarity that here.
> That matches my understanding.

Yes, I concur with Colin here, the default includes everything to IP=20
level. And clearly one can override that default by being explicit, like =

in the case of TIAS (RFC 3890). That RFC also have guiding=20
interpretation on the default, by actually stating the following on AS:

1.1.2. Application Specific Maximum

    The Application Specific maximum bandwidth is indicated by the
    modifier "AS".  The interpretation of this attribute is dependent on
    the application's notion of maximum bandwidth.  For an RTP
    application, this attribute is the RTP session bandwidth as defined
    in RFC 3550 [4].  The session bandwidth includes the bandwidth that
    the RTP data traffic will consume, including the lower layers, down
    to the IP layer.  Therefore, the bandwidth is in most cases
    calculated over RTP payload, RTP header, UDP, and IP, defined in RFC
    2327 [1].



Cheers

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


--------------EBAA99B0C13FE404F4D374C5
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class=3D"moz-cite-prefix">Den 2018-02-23 kl. 01:17, skrev Colin
      Perkins:
    </div>
    <blockquote type=3D"cite"
      cite=3D"mid:9DB08F76-F13D-4EF4-8D8B-4F4598157265@csperkins.org">
      <blockquote type=3D"cite">
        <pre wrap=3D"">
2) Section 5.8:

  The &lt;bandwidth&gt; is interpreted as kilobits per second by default.=


Comment: What about lower layer overhead? RFC 3550 Section 6.2 specifies =
that we include UDP and IP overhead, etc. but not link layer. I believe t=
his is consistent with (old) discussions on the MMUSIC mailing list as we=
ll and think it would be useful to clarity that here.
</pre>
      </blockquote>
      <pre wrap=3D"">
That matches my understanding.</pre>
    </blockquote>
    <br>
    Yes, I concur with Colin here, the default includes everything to IP
    level. And clearly one can override that default by being explicit,
    like in the case of TIAS (RFC 3890). That RFC also have guiding
    interpretation on the default, by actually stating the following on
    AS:<br>
    <br>
    <pre><span class=3D"m_h">1.1.2.  Application Specific Maximum</span>

   The Application Specific maximum bandwidth is indicated by the
   modifier "AS".  The interpretation of this attribute is dependent on
   the application's notion of maximum bandwidth.  For an RTP
   application, this attribute is the RTP session bandwidth as defined
   in RFC 3550 [4].  The session bandwidth includes the bandwidth that
   the RTP data traffic will consume, including the lower layers, down
   to the IP layer.  Therefore, the bandwidth is in most cases
   calculated over RTP payload, RTP header, UDP, and IP, defined in RFC
   2327 [1].



</pre>
    Cheers<br>
    <pre class=3D"moz-signature" cols=3D"72">
Magnus Westerlund=20

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"moz-txt-link-abbreviate=
d" href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@erics=
son.com</a>
----------------------------------------------------------------------</p=
re>
  </body>
</html>

--------------EBAA99B0C13FE404F4D374C5--

--------------ms050500010006080706000601
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-kryptografisk signatur

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
DNEwggYHMIID76ADAgECAhALRm3NcHtuMGWutmt5cXntMA0GCSqGSIb3DQEBCwUAMEcxCzAJ
BgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MzAeFw0xNzEyMTUwNzIyMjNaFw0yMDEyMTUwNzIyMjJaMHAxETAPBgNV
BAoMCEVyaWNzc29uMRowGAYDVQQDDBFNYWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJ
ARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nzb24uY29tMRAwDgYDVQQFEwdlcmFtc3dkMIIB
IjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsKlHZvB3TsmLEDtPSiFFKAh73S2wApt+
laqg5eXTqonqnzT9ykEGL2dx9mBT+2WZiIKxo4w2sisVl3EEYTqXTkctpur7cN29gLC8F3tJ
HGI2sUVpO9AwpVrN+UuHEVetHt7hdxW9uYd0LJJ8TP6/wGkIfAFaZxlZUn79O2eHElfih1iV
IiTZXLcEe1rBJtzhUNRHWgOm2vQlDJ4sCpigGFq5w+XSRviEQMkQZRvw1CQmb35QS/C/T36o
gzIRHDuAdkoSaiUOY/S2dLp4HkwvOOg+tADpaHkrbdmdnjKGrYSnJigmxw14pJugxL/Vb2Ee
VcgpAfVVst7Lm4POPRI8+wIDAQABo4IBxDCCAcAwSAYDVR0fBEEwPzA9oDugOYY3aHR0cDov
L2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nzb25ubGluZGl2aWR1YWxjYXYzLmNybDCBggYI
KwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3QudGVsaWEuY29t
MEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2VyaWNzc29u
bmxpbmRpdmlkdWFsY2F2My5jZXIwKQYDVR0RBCIwIIEebWFnbnVzLndlc3Rlcmx1bmRAZXJp
Y3Nzb24uY29tMFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0
dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMB0GA1UdJQQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU5ivuhpU51W4UhBDBWwf8XsU837YwHwYD
VR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMwDgYDVR0PAQH/BAQDAgWgMA0GCSqGSIb3
DQEBCwUAA4ICAQBn0FKukg00UN/c/ESpxSIaYTrsd8liHHMu5rLpOBNOacpGNBMGNgUDDt4Q
ihhoQR3cvhYXCrAM59NTvw0HNlgqHZoEeVY7YnJJYnJXDCLUfkK5Dn28E3QrzykkF6giUOXD
yF9mhWYbSAkJyx0Yj0Xc8en3wYNyoFYEqjlKtZrdV0pcgFzEeXVLS8DWrzSy7+KfUtDOEiM6
H3zO3nsq++KBmsOiSKkWn4oYERZg5KElEAHis9av+3KIaEPnOAt8QRWRpFfGZ4d89F16qFvE
lup5n7l864FqxnC2friDo4hLQY6ENaOaYIihXhbl2UYxAGDk89aJm/S5pYyq7wzm+KK3IcUl
60rmc8SJlt6QXKw0wXEOE1MubauYKMsad2s8jD+rEkXp+agTRl+sezWaRxHBpxuUKDd6MhwD
ig3SZi1qP7D/Ds4V+JLIjjUJc25l9tvMGC9+lqI0P+vMI3Zyrou0NNfb55uLQaq18O+7BZ8K
v7jvFdxYyUgbxQ0SPEiyhylcLHAmJeLCQaiZHmCREBkCLKSf0O4lE2TrVzdOD38wjzuQ27U3
UddVCD9EQ3tF7o6EVhpxJJUlB6xe/2UWwy4Zla71dKLUhakdVrN5abzxqFWvzOAT9nBa2HzY
VBtpbcu6KGh72YJ+M79fa9iIkcQCgUnw3gIAeWd//n4YbY2QhDCCBsIwggSqoAMCAQICEFO4
foPhnJkok7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUx
MDI3MTIxNjQ2WjBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMM
HEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAw
ggIKAoICAQDs8t8AALhQ8qe72FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfS
Tm+7meisbhkqUXkL7fFzoe4iIZCh/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbX
ILlLhRummTdDdxhVW4Leo0awEhfLf98MvWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfp
VdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmdvkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2
PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2
H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP1UrZaEIFu+hO+s0Nm8sOUMa4TlG4
rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3sp0FdQDEzQlnF/h1L4AK1MOkX
1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25aEvAA+yrrplCh/kYvSBjv
Zibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUUkBUrrvijPDaGK5FN
VSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCCAbQwgYoGCCsG
AQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFzb25lcmEu
Y29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVyYS5j
b20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3Js
LTMudHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1Ud
JQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7
GZ6XnHasID3Y3OORauPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0G
CSqGSIb3DQEBCwUAA4ICAQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDU
JQEPRs5QtaZiObNHCZ7mmSNMVek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHG
vw5RY6vRlZrj0uKvdASzYL4KMaB7m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYn
nl2t3D3oBX2NZCQysshUcqRdUbkS13HTCIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwf
ixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNMMbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ8
5AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4Hd
Dc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPNmJ0RLCi+4d4/47Zs3DC3PUNOxdOE
EHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKakDZfAFM4HoHz8K2BZRaHKWhd
3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i0bqGahxlHYzl/QyEG/du
jp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+WkDGCAzswggM3AgEB
MFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5cXntMA0GCWCGSAFlAwQCAQUA
oIIBsTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAyMjQx
NDA5MDdaMC8GCSqGSIb3DQEJBDEiBCBc8heIKjZjdtx/teJo5xtYcaax/d/0h1pd13W2255R
VjBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjEl
MCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBlrrZreXF5
7TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMGwGCyqGSIb3DQEJEAILMV2gWzBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nz
b24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMCEAtGbc1we24wZa62
a3lxee0wDQYJKoZIhvcNAQEBBQAEggEAklN478y47JfNXgB/THX17gHcp/nCs9RUqQdcb8Ux
6sG4VX5lYv4+G/TkOVRZm33anLqBxgbdRmur0kYnQHpahM0seb/sUd+FcRa7vuh47qh36RTp
THdd0KVd+CXzuDLR0/92L1amXkb2wWC3G+xPBOHA2fO88xsr3TlN//eMQWJSaaSXxJU3fsUp
BmcZLgfTySqVOdVwScU0BHgansTZciNPpE88rKVtKEUd7ExHQiwcL8WCgzjVYWIx2bGhcT/M
ZxqYIyeLXuAkZnxT+Z4TyvuNkIvfDm4Dt/Ggqye8mKJSLCRl17WgvN80i6DuecS615LgE8k6
PSGxnWxWqG0exwAAAAAAAA==
--------------ms050500010006080706000601--


From nobody Sat Feb 24 10:50:40 2018
Return-Path: <pkyzivat@alum.mit.edu>
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 E0DA0126DFB for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 10:50:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=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 hs7mbEn2zZ4j for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 10:50:37 -0800 (PST)
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id CEDE4126C2F for <mmusic@ietf.org>; Sat, 24 Feb 2018 10:50:36 -0800 (PST)
X-AuditID: 1207440f-ab7ff70000000ab0-44-5a91b3faf061
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id B6.D8.02736.AF3B19A5; Sat, 24 Feb 2018 13:50:35 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w1OIoWGj011183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 24 Feb 2018 13:50:33 -0500
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Colin Perkins <csp@csperkins.org>
Cc: mmusic@ietf.org
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <0e0b0574-33df-c21e-0b45-cbce053e2479@alum.mit.edu> <00A1F596-E6A8-4FA3-8797-DF11D2A73198@csperkins.org> <522c3733-4b5f-b886-5b98-cd6fb1567a11@ericsson.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <e9e95e5b-aa88-9593-8df1-44390af712db@alum.mit.edu>
Date: Sat, 24 Feb 2018 13:50:31 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <522c3733-4b5f-b886-5b98-cd6fb1567a11@ericsson.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprCKsWRmVeSWpSXmKPExsUixO6iqPt788Qog/b/shbLX55gtLi0/h6T xdTlj1kcmD2m3b/P5vHr61U2jyVLfjIFMEdx2aSk5mSWpRbp2yVwZby9/4i1YL1KRc/uC2wN jD2yXYycHBICJhKr3h1k6WLk4hAS2MEk8XPpS2YI5yGTxO6Vl9hAqoQFPCUmTF7M2sXIwSEi kCRx730BSJhZQFjizvL/jCC2kMBTRon93UkgNpuAlsScQ/9ZQGxeAXuJmx+Wg9WwCKhKvFuw ghnEFhVIk3j1bAczRI2gxMmZT8DqOQUcJG7cXMIKMd9MYt7mh8wQtrjErSfzmSBseYnmrbOZ JzAKzELSPgtJyywkLbOQtCxgZFnFKJeYU5qrm5uYmVOcmqxbnJyYl5dapGuil5tZopeaUrqJ ERLU/DsYu9bLHGIU4GBU4uGNEJ8QJcSaWFZcmXuIUZKDSUmUN8oCKMSXlJ9SmZFYnBFfVJqT WnyIUYKDWUmE9yHjxCgh3pTEyqrUonyYlDQHi5I4r/oSdT8hgfTEktTs1NSC1CKYrAwHh5IE 78pNQI2CRanpqRVpmTklCGkmDk6Q4TxAw3eB1PAWFyTmFmemQ+RPMRpztFx80sbMcePF6zZm IZa8/LxUKXHeXyClAiClGaV5cNNgiekVozjQc8K8V0CqeIBJDW7eK6BVTECr3P9PAFlVkoiQ kmpgZDjo3fwt5UKPhkHgrT32P2dXrL+ysMZSnWuroGe37dN1fQdZo+7uTu3rPa8o2lrzmP10 8KSPZ/+9tLY61ly4Z6vdTJ+TRWc/8QifeO9esKnW8vbF9W+Xfb9Y58Qab6Zi4ntex3DdcetK I74WIV6tbbc7V4dPczNVe29QOzVYR8TM3lLhzZw3SizFGYmGWsxFxYkAZYBYoycDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/0MK4XKcfSpbY9iIcLiWdYGg69bU>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): ptime
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Feb 2018 18:50:39 -0000

On 2/24/18 9:04 AM, Magnus Westerlund wrote:
> Hi,
> 
> I very split about this change. From the point of an RTP payload format 
> that defines the packetization time, using fraction would be very nice. 
> And also on that level it is an minor interoperability issue to allow 
> these, the main problem is if the basic SDP parser throws a fit.

Having the general syntax support fractional values is only an enabler. 
Presumably each individual format also needs to specify what range of 
values it supports, and if that includes fractions. Presumably backward 
compatibility will mean that fractions can't be used in all cases. It 
might take more text to clarify this. (It isn't clear to me what that 
text ought to say.)

> However, from my perspective the issue with ptime is that this is an 
> payload format specific parameter that got overloaded onto a single per 
> media stream instance. This becomes problematic as soon as one have 
> multiple codes with none matching values, like if one like single frame 
> audio payloads but have one 20 ms codec and one 30 ms one, what do one 
> use, and how is it interpreted. And what happens if one would state 
> ptime=22.5 when one have also a 22.5 frame length codec.
> 
> I wished we faced this issue earlier and changed the recommendation to 
> leave the ptime and maxptime values in that a=ftmp lines and deprecated 
> the use on media stream level.
> 
> I think both ptime and maxptime needs text on the fact that the value 
> may not be matching the possible values for all of the payload formats. 
> Especially if the value is a fractional one.

I guess what you are saying here is roughly what I was trying to say above?

I guess the existing definitions of formats won't say anything about 
this. Do we need language that says fractional (and zero) values may 
only be used if the format explicitly defines their use?

	Thanks,
	Paul

> Cheers
> 
> Magnus Westerlund
> 
> 
> Den 2018-02-23 kl. 00:50, skrev Colin Perkins:
>>
>>> On 20 Feb 2018, at 16:18, Paul Kyzivat <pkyzivat@alum.mit.edu 
>>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>>
>>> On 2/20/18 10:25 AM, Ali C. Begen wrote:
>>>
>>>> 4) Section 6.4 and 6.5:
>>>>    Syntax:
>>>>          ptime-value = non-zero-int-or-real
>>>>          maxptime-value = non-zero-int-or-real
>>>> Comment: I always thought they were integeres. The text below 
>>>> doesn't make it clear one way or the other, which it needs to.
>>>
>>> I went back looking for where this came from. It appears that I have 
>>> incomplete history. It came in in late 2015 – early 2016. If you look 
>>> at rfc4566, it doesn’t provide *any* syntax for “packet time”.
>>>
>>> My recollection is that somebody felt there was a need for fractional 
>>> ptimes. (And maybe some deployed usage?) Hence we put this in.
>>>
>>> Does anyone else have any info or memory of this?
>>
>> It seems to have been added in 4566bis-15. Ali’s presentation at IETF 
>> 92 discusses it 
>> https://www.ietf.org/proceedings/92/slides/slides-92-mmusic-1.pdf and 
>> the minutes from that meeting say:
>>
>>
>>         a=ptime: and a=maxptime:
>>
>> Are these always integers?
>> Paul Kyzivat had made a suggestion to allow the use of decimal 
>> fractions only when the fractional part is non-zero. This definition 
>> could also be used for framerate; question around whether framerate 
>> could be zero.
>>
>> Jonathan Lennox liked Paul's suggestion. Framerate should not be zero.
>>
>> Roni Even noted that framerate of zero could be a still image.
>>
>> *Conclusion*:
>> ●Nobody objects to Ali’s/Paul's suggestion, so move forward with 
>> fractional values.
>>
>>
>> See also https://trac.ietf.org/trac/mmusic/ticket/21
>>
>> (I’m fairly sure there were some earlier comments that triggered this 
>> discussion, but I can’t find them)
>>
>> -- 
>> Colin Perkins
>> https://csperkins.org/
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
> 
> -- 
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Media Technologies, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Torshamnsgatan 23           | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto:magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 


From nobody Sat Feb 24 11:34:31 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF61127275; Sat, 24 Feb 2018 11:34:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.72.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151950086451.13795.8739583004727843899@ietfa.amsl.com>
Date: Sat, 24 Feb 2018 11:34:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/uK77UuEYnTsUpQQndRf4gWGug3o>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-trickle-ice-sip-14.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Feb 2018 19:34:25 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : A Session Initiation Protocol (SIP) Usage for Trickle ICE
        Authors         : Emil Ivov
                          Thomas Stach
                          Enrico Marocco
                          Christer Holmberg
	Filename        : draft-ietf-mmusic-trickle-ice-sip-14.txt
	Pages           : 46
	Date            : 2018-02-24

Abstract:
   The Interactive Connectivity Establishment (ICE) protocol describes a
   Network Address Translator (NAT) traversal mechanism for UDP-based
   multimedia sessions established with the Offer/Answer model.  The ICE
   extension for Incremental Provisioning of Candidates (Trickle ICE)
   defines a mechanism that allows ICE Agents to shorten session
   establishment delays by making the candidate gathering and
   connectivity checking phases of ICE non-blocking and by executing
   them in parallel.

   This document defines usage semantics for Trickle ICE with the
   Session Initiation Protocol (SIP) and defines a new SIP Info Package
   to support this usage.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-14
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-trickle-ice-sip-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sat Feb 24 11:37:01 2018
Return-Path: <thomass.stach@gmail.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 9384C127275 for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 11:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 0MYxF89D7Mub for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 11:36:58 -0800 (PST)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 53B191200B9 for <mmusic@ietf.org>; Sat, 24 Feb 2018 11:36:58 -0800 (PST)
Received: by mail-lf0-x235.google.com with SMTP id f75so11883515lfg.6 for <mmusic@ietf.org>; Sat, 24 Feb 2018 11:36:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=JctarwDEucXL+ES50NTIriYaCx78iRYm7fG4jePGgL8=; b=Yaj8nJouBPFfEQkGtnZlqTjpaxiMsS+07NZi0+gMwZ5OLsEu3PeLrzPX5OORqswFSd OQZdASDcdaxwLOMHo2gAm9+82T2P71WWA9rE5Ru7gn0F16aSO8aNDhy3UaB+vsPeboz/ kJrDyE/SEVhSM5lCcZ8RxkBGeRYOOVECYxeC5KTa3qGbUYo1Cw+A7LdCqS8uopdonAWy K4u1RtAGnDC1+cAFMIGJuGLpC3e8le16kaI36/B2yrwJjj82VoWl4vE8sJUx5Q3tBaVk Um/lwMZDhdwB+ArDYijNnPhNJ5JgVYMvfpo3/KFgv90wZbFls/cNo4XWmolgYhi86qtP hnDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=JctarwDEucXL+ES50NTIriYaCx78iRYm7fG4jePGgL8=; b=T6iYy1JIX+WdwUZYo7vOdATSM7VVihmNNI3SGSmdKiIDUA2JQDFQh/UnD+gX3p1RCg SOj/opIjh7wQe4iVND43iTwFuRf5xCSfxXBk7Bz5OGb4uBBdx8zSbf6z8UPMJUo2Fn3x bEg8ClaQggEREoe1M0c2JYLGOhgbvvo5AFfX5pLfDMRDxWLAmfJseMjulS6rzn3iqob3 k7aW8bcSVoNzDEAoHHm+HjbIVkMZZKCTGsLYmt6i9+PBTi4hRXmgRlSFThUtDsStpo6S ILqfaLYhL8KX5FC3BHcFCynK1t0GbIwmXIHywQimGa48zrnX6sc9IylJr+U65t4sqAS/ cEhg==
X-Gm-Message-State: APf1xPBKYUQAUdqGRkvxyrn49Tq5tqc/WU9TDYtx8JeVcBG6D6/qod7F itQVC65O9wpeXCRl98p/BkA=
X-Google-Smtp-Source: AG47ELvOlxc+WkAZU0tNcLHFfeoQxhm+Zgkr2fClvuV36EB5LhAPBdu00/sCqG1geFxILxYh8eIn5g==
X-Received: by 10.25.193.78 with SMTP id r75mr4007488lff.124.1519501016612; Sat, 24 Feb 2018 11:36:56 -0800 (PST)
Received: from [192.168.2.111] (d91-130-105-232.cust.tele2.at. [91.130.105.232]) by smtp.googlemail.com with ESMTPSA id z3sm1105482ljb.71.2018.02.24.11.36.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Feb 2018 11:36:55 -0800 (PST)
To: MMUSIC <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>, Enrico Marocco <enrico.marocco@telecomitalia.it>, Emil Ivov <emcho@jitsi.org>
References: <151950086481.13795.9489465247024414537.idtracker@ietfa.amsl.com>
From: Thomas Stach <thomass.stach@gmail.com>
Message-ID: <af510075-a7d5-3059-8ebf-3dc275fd3af5@gmail.com>
Date: Sat, 24 Feb 2018 20:36:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <151950086481.13795.9489465247024414537.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/iXGxRNZdwJjseajQoS4DA-Oneqk>
Subject: Re: [MMUSIC] New Version Notification for draft-ietf-mmusic-trickle-ice-sip-14.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 24 Feb 2018 19:37:01 -0000

All,

this update includes a few editorial things that did not make it into 
-13 like

o  added expansions for SDP,GRUU, AOR, STUN, TURN

o  some editorial corrections


Regards

Thomas




On 2018-02-24 20:34, internet-drafts@ietf.org wrote:
> A new version of I-D, draft-ietf-mmusic-trickle-ice-sip-14.txt
> has been successfully submitted by Thomas Stach and posted to the
> IETF repository.
>
> Name:		draft-ietf-mmusic-trickle-ice-sip
> Revision:	14
> Title:		A Session Initiation Protocol (SIP) Usage for Trickle ICE
> Document date:	2018-02-23
> Group:		mmusic
> Pages:		46
> URL:            https://www.ietf.org/internet-drafts/draft-ietf-mmusic-trickle-ice-sip-14.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-trickle-ice-sip/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-mmusic-trickle-ice-sip-14
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-trickle-ice-sip-14
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-trickle-ice-sip-14
>
> Abstract:
>     The Interactive Connectivity Establishment (ICE) protocol describes a
>     Network Address Translator (NAT) traversal mechanism for UDP-based
>     multimedia sessions established with the Offer/Answer model.  The ICE
>     extension for Incremental Provisioning of Candidates (Trickle ICE)
>     defines a mechanism that allows ICE Agents to shorten session
>     establishment delays by making the candidate gathering and
>     connectivity checking phases of ICE non-blocking and by executing
>     them in parallel.
>
>     This document defines usage semantics for Trickle ICE with the
>     Session Initiation Protocol (SIP) and defines a new SIP Info Package
>     to support this usage.
>
>                                                                                    
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>


From nobody Sat Feb 24 22:50:59 2018
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 BBBCC1267BB for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 22:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_RP_MATCHES_RCVD=-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 ATyehUE92scu for <mmusic@ietfa.amsl.com>; Sat, 24 Feb 2018 22:50:54 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 82EE9124E15 for <mmusic@ietf.org>; Sat, 24 Feb 2018 22:50:54 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B7A9B826F77B9; Sun, 25 Feb 2018 06:50:50 +0000 (GMT)
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.361.1; Sun, 25 Feb 2018 06:50:51 +0000
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0361.001; Sun, 25 Feb 2018 14:50:41 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Colin Perkins <csp@csperkins.org>, "Ali C. Begen" <ali.begen@networked.media>
CC: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] 4566bis open issues (from Flemming's review): Bandwidth values
Thread-Index: AQHTrXkmv0d4uWBgIkSizYD2Zb9vXaO0ruPw
Date: Sun, 25 Feb 2018 06:50:41 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD86625A@DGGEMM506-MBX.china.huawei.com>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <9DB08F76-F13D-4EF4-8D8B-4F4598157265@csperkins.org> <78aa5f97-bb84-b8c0-79df-b4130532d31c@ericsson.com>
In-Reply-To: <78aa5f97-bb84-b8c0-79df-b4130532d31c@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.90]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD86625ADGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/KPPIDKUSjnOCBwPCaeeochUJ2GU>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): Bandwidth values
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 25 Feb 2018 06:50:58 -0000

--_000_6E58094ECC8D8344914996DAD28F1CCD86625ADGGEMM506MBXchina_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

KzENClJvbmkNCg0KRnJvbTogbW11c2ljIFttYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5vcmdd
IE9uIEJlaGFsZiBPZiBNYWdudXMgV2VzdGVybHVuZA0KU2VudDogU2F0dXJkYXksIEZlYnJ1YXJ5
IDI0LCAyMDE4IDQ6MDkgUE0NClRvOiBDb2xpbiBQZXJraW5zOyBBbGkgQy4gQmVnZW4NCkNjOiBt
bXVzaWNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbTU1VU0lDXSA0NTY2YmlzIG9wZW4gaXNzdWVz
IChmcm9tIEZsZW1taW5nJ3MgcmV2aWV3KTogQmFuZHdpZHRoIHZhbHVlcw0KDQoNCg0KDQpEZW4g
MjAxOC0wMi0yMyBrbC4gMDE6MTcsIHNrcmV2IENvbGluIFBlcmtpbnM6DQoNCg0KDQoyKSBTZWN0
aW9uIDUuODoNCg0KDQoNCiAgVGhlIDxiYW5kd2lkdGg+IGlzIGludGVycHJldGVkIGFzIGtpbG9i
aXRzIHBlciBzZWNvbmQgYnkgZGVmYXVsdC4NCg0KDQoNCkNvbW1lbnQ6IFdoYXQgYWJvdXQgbG93
ZXIgbGF5ZXIgb3ZlcmhlYWQ/IFJGQyAzNTUwIFNlY3Rpb24gNi4yIHNwZWNpZmllcyB0aGF0IHdl
IGluY2x1ZGUgVURQIGFuZCBJUCBvdmVyaGVhZCwgZXRjLiBidXQgbm90IGxpbmsgbGF5ZXIuIEkg
YmVsaWV2ZSB0aGlzIGlzIGNvbnNpc3RlbnQgd2l0aCAob2xkKSBkaXNjdXNzaW9ucyBvbiB0aGUg
TU1VU0lDIG1haWxpbmcgbGlzdCBhcyB3ZWxsIGFuZCB0aGluayBpdCB3b3VsZCBiZSB1c2VmdWwg
dG8gY2xhcml0eSB0aGF0IGhlcmUuDQoNCg0KDQpUaGF0IG1hdGNoZXMgbXkgdW5kZXJzdGFuZGlu
Zy4NCg0KWWVzLCBJIGNvbmN1ciB3aXRoIENvbGluIGhlcmUsIHRoZSBkZWZhdWx0IGluY2x1ZGVz
IGV2ZXJ5dGhpbmcgdG8gSVAgbGV2ZWwuIEFuZCBjbGVhcmx5IG9uZSBjYW4gb3ZlcnJpZGUgdGhh
dCBkZWZhdWx0IGJ5IGJlaW5nIGV4cGxpY2l0LCBsaWtlIGluIHRoZSBjYXNlIG9mIFRJQVMgKFJG
QyAzODkwKS4gVGhhdCBSRkMgYWxzbyBoYXZlIGd1aWRpbmcgaW50ZXJwcmV0YXRpb24gb24gdGhl
IGRlZmF1bHQsIGJ5IGFjdHVhbGx5IHN0YXRpbmcgdGhlIGZvbGxvd2luZyBvbiBBUzoNCg0KMS4x
LjIuICBBcHBsaWNhdGlvbiBTcGVjaWZpYyBNYXhpbXVtDQoNCg0KDQogICBUaGUgQXBwbGljYXRp
b24gU3BlY2lmaWMgbWF4aW11bSBiYW5kd2lkdGggaXMgaW5kaWNhdGVkIGJ5IHRoZQ0KDQogICBt
b2RpZmllciAiQVMiLiAgVGhlIGludGVycHJldGF0aW9uIG9mIHRoaXMgYXR0cmlidXRlIGlzIGRl
cGVuZGVudCBvbg0KDQogICB0aGUgYXBwbGljYXRpb24ncyBub3Rpb24gb2YgbWF4aW11bSBiYW5k
d2lkdGguICBGb3IgYW4gUlRQDQoNCiAgIGFwcGxpY2F0aW9uLCB0aGlzIGF0dHJpYnV0ZSBpcyB0
aGUgUlRQIHNlc3Npb24gYmFuZHdpZHRoIGFzIGRlZmluZWQNCg0KICAgaW4gUkZDIDM1NTAgWzRd
LiAgVGhlIHNlc3Npb24gYmFuZHdpZHRoIGluY2x1ZGVzIHRoZSBiYW5kd2lkdGggdGhhdA0KDQog
ICB0aGUgUlRQIGRhdGEgdHJhZmZpYyB3aWxsIGNvbnN1bWUsIGluY2x1ZGluZyB0aGUgbG93ZXIg
bGF5ZXJzLCBkb3duDQoNCiAgIHRvIHRoZSBJUCBsYXllci4gIFRoZXJlZm9yZSwgdGhlIGJhbmR3
aWR0aCBpcyBpbiBtb3N0IGNhc2VzDQoNCiAgIGNhbGN1bGF0ZWQgb3ZlciBSVFAgcGF5bG9hZCwg
UlRQIGhlYWRlciwgVURQLCBhbmQgSVAsIGRlZmluZWQgaW4gUkZDDQoNCiAgIDIzMjcgWzFdLg0K
DQoNCg0KDQoNCg0KQ2hlZXJzDQoNCg0KDQoNCk1hZ251cyBXZXN0ZXJsdW5kDQoNCg0KDQotLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQoNCk1lZGlhIFRlY2hub2xvZ2llcywgRXJpY3Nzb24gUmVzZWFyY2gNCg0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLQ0KDQpFcmljc3NvbiBBQiAgICAgICAgICAgICAgICAgfCBQaG9uZSAgKzQ2IDEw
IDcxNDgyODcNCg0KVG9yc2hhbW5zZ2F0YW4gMjMgICAgICAgICAgIHwgTW9iaWxlICs0NiA3MyAw
OTQ5MDc5DQoNClNFLTE2NCA4MCBTdG9ja2hvbG0sIFN3ZWRlbiB8IG1haWx0bzogbWFnbnVzLndl
c3Rlcmx1bmRAZXJpY3Nzb24uY29tPG1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5j
b20+DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCg==

--_000_6E58094ECC8D8344914996DAD28F1CCD86625ADGGEMM506MBXchina_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQpA
Zm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIg
MiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNv
Tm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAw
MXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
InNlcmlmIjsNCgljb2xvcjpibGFjazt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpwDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1h
cmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBO
ZXcgUm9tYW4iLCJzZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbWFy
Z2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBwdDsNCglm
b250LWZhbWlseToiQ291cmllciBOZXciOw0KCWNvbG9yOmJsYWNrO30NCnNwYW4uSFRNTFByZWZv
cm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0K
CW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0
ZWQiOw0KCWZvbnQtZmFtaWx5OiJDb25zb2xhcyIsInNlcmlmIjsNCgljb2xvcjpibGFjazt9DQpz
cGFuLm1oDQoJe21zby1zdHlsZS1uYW1lOm1faDt9DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXttc28t
c3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRt
YXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4N
CjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRh
PSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJv
ZHkgYmdjb2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxl
Ij4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+JiM0MzsxPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPlJvbmk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGlu
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOndpbmRvd3RleHQiPkZyb206PC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjp3aW5kb3d0ZXh0Ij4gbW11c2ljIFttYWlsdG86bW11c2ljLWJvdW5jZXNAaWV0Zi5v
cmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPk1hZ251cyBXZXN0ZXJsdW5kPGJyPg0KPGI+U2VudDo8
L2I+IFNhdHVyZGF5LCBGZWJydWFyeSAyNCwgMjAxOCA0OjA5IFBNPGJyPg0KPGI+VG86PC9iPiBD
b2xpbiBQZXJraW5zOyBBbGkgQy4gQmVnZW48YnI+DQo8Yj5DYzo8L2I+IG1tdXNpY0BpZXRmLm9y
Zzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW01NVVNJQ10gNDU2NmJpcyBvcGVuIGlzc3VlcyAo
ZnJvbSBGbGVtbWluZydzIHJldmlldyk6IEJhbmR3aWR0aCB2YWx1ZXM8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8cD48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlbiAy
MDE4LTAyLTIzIGtsLiAwMToxNywgc2tyZXYgQ29saW4gUGVya2luczogPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJv
dHRvbTo1LjBwdCI+DQo8cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+DQo8cHJlPjIpIFNlY3Rp
b24gNS44OjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+DQo8
cHJlPiZuYnNwOyBUaGUgJmx0O2JhbmR3aWR0aCZndDsgaXMgaW50ZXJwcmV0ZWQgYXMga2lsb2Jp
dHMgcGVyIHNlY29uZCBieSBkZWZhdWx0LjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wcmU+DQo8cHJlPkNvbW1lbnQ6IFdoYXQgYWJvdXQgbG93ZXIgbGF5ZXIgb3Zl
cmhlYWQ/IFJGQyAzNTUwIFNlY3Rpb24gNi4yIHNwZWNpZmllcyB0aGF0IHdlIGluY2x1ZGUgVURQ
IGFuZCBJUCBvdmVyaGVhZCwgZXRjLiBidXQgbm90IGxpbmsgbGF5ZXIuIEkgYmVsaWV2ZSB0aGlz
IGlzIGNvbnNpc3RlbnQgd2l0aCAob2xkKSBkaXNjdXNzaW9ucyBvbiB0aGUgTU1VU0lDIG1haWxp
bmcgbGlzdCBhcyB3ZWxsIGFuZCB0aGluayBpdCB3b3VsZCBiZSB1c2VmdWwgdG8gY2xhcml0eSB0
aGF0IGhlcmUuPG86cD48L286cD48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjxwcmU+PG86cD4mbmJz
cDs8L286cD48L3ByZT4NCjxwcmU+VGhhdCBtYXRjaGVzIG15IHVuZGVyc3RhbmRpbmcuPG86cD48
L286cD48L3ByZT4NCjwvYmxvY2txdW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW4tYm90dG9tOjEyLjBwdCI+PGJyPg0KWWVzLCBJIGNvbmN1ciB3aXRoIENvbGluIGhlcmUs
IHRoZSBkZWZhdWx0IGluY2x1ZGVzIGV2ZXJ5dGhpbmcgdG8gSVAgbGV2ZWwuIEFuZCBjbGVhcmx5
IG9uZSBjYW4gb3ZlcnJpZGUgdGhhdCBkZWZhdWx0IGJ5IGJlaW5nIGV4cGxpY2l0LCBsaWtlIGlu
IHRoZSBjYXNlIG9mIFRJQVMgKFJGQyAzODkwKS4gVGhhdCBSRkMgYWxzbyBoYXZlIGd1aWRpbmcg
aW50ZXJwcmV0YXRpb24gb24gdGhlIGRlZmF1bHQsIGJ5IGFjdHVhbGx5IHN0YXRpbmcgdGhlIGZv
bGxvd2luZw0KIG9uIEFTOjxvOnA+PC9vOnA+PC9wPg0KPHByZT48c3BhbiBjbGFzcz0ibWgiPjEu
MS4yLiZuYnNwOyBBcHBsaWNhdGlvbiBTcGVjaWZpYyBNYXhpbXVtPC9zcGFuPjxvOnA+PC9vOnA+
PC9wcmU+DQo8cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+DQo8cHJlPiZuYnNwOyZuYnNwOyBU
aGUgQXBwbGljYXRpb24gU3BlY2lmaWMgbWF4aW11bSBiYW5kd2lkdGggaXMgaW5kaWNhdGVkIGJ5
IHRoZTxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPiZuYnNwOyZuYnNwOyBtb2RpZmllciAmcXVvdDtB
UyZxdW90Oy4mbmJzcDsgVGhlIGludGVycHJldGF0aW9uIG9mIHRoaXMgYXR0cmlidXRlIGlzIGRl
cGVuZGVudCBvbjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPiZuYnNwOyZuYnNwOyB0aGUgYXBwbGlj
YXRpb24ncyBub3Rpb24gb2YgbWF4aW11bSBiYW5kd2lkdGguJm5ic3A7IEZvciBhbiBSVFA8bzpw
PjwvbzpwPjwvcHJlPg0KPHByZT4mbmJzcDsmbmJzcDsgYXBwbGljYXRpb24sIHRoaXMgYXR0cmli
dXRlIGlzIHRoZSBSVFAgc2Vzc2lvbiBiYW5kd2lkdGggYXMgZGVmaW5lZDxvOnA+PC9vOnA+PC9w
cmU+DQo8cHJlPiZuYnNwOyZuYnNwOyBpbiBSRkMgMzU1MCBbNF0uJm5ic3A7IFRoZSBzZXNzaW9u
IGJhbmR3aWR0aCBpbmNsdWRlcyB0aGUgYmFuZHdpZHRoIHRoYXQ8bzpwPjwvbzpwPjwvcHJlPg0K
PHByZT4mbmJzcDsmbmJzcDsgdGhlIFJUUCBkYXRhIHRyYWZmaWMgd2lsbCBjb25zdW1lLCBpbmNs
dWRpbmcgdGhlIGxvd2VyIGxheWVycywgZG93bjxvOnA+PC9vOnA+PC9wcmU+DQo8cHJlPiZuYnNw
OyZuYnNwOyB0byB0aGUgSVAgbGF5ZXIuJm5ic3A7IFRoZXJlZm9yZSwgdGhlIGJhbmR3aWR0aCBp
cyBpbiBtb3N0IGNhc2VzPG86cD48L286cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7IGNhbGN1
bGF0ZWQgb3ZlciBSVFAgcGF5bG9hZCwgUlRQIGhlYWRlciwgVURQLCBhbmQgSVAsIGRlZmluZWQg
aW4gUkZDPG86cD48L286cD48L3ByZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7IDIzMjcgWzFdLjxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+DQo8cHJlPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wcmU+DQo8cHJlPjxvOnA+Jm5ic3A7PC9vOnA+PC9wcmU+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5DaGVlcnM8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxwcmU+PG86cD4m
bmJzcDs8L286cD48L3ByZT4NCjxwcmU+TWFnbnVzIFdlc3Rlcmx1bmQgPG86cD48L286cD48L3By
ZT4NCjxwcmU+PG86cD4mbmJzcDs8L286cD48L3ByZT4NCjxwcmU+LS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxvOnA+
PC9vOnA+PC9wcmU+DQo8cHJlPk1lZGlhIFRlY2hub2xvZ2llcywgRXJpY3Nzb24gUmVzZWFyY2g8
bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPG86cD48L286cD48L3ByZT4NCjxw
cmU+RXJpY3Nzb24gQUImbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgfCBQ
aG9uZSZuYnNwOyAmIzQzOzQ2IDEwIDcxNDgyODc8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT5Ub3Jz
aGFtbnNnYXRhbiAyMyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDt8IE1vYmlsZSAmIzQzOzQ2IDczIDA5NDkwNzk8bzpwPjwvbzpwPjwv
cHJlPg0KPHByZT5TRS0xNjQgODAgU3RvY2tob2xtLCBTd2VkZW4gfCBtYWlsdG86IDxhIGhyZWY9
Im1haWx0bzptYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb20iPm1hZ251cy53ZXN0ZXJsdW5k
QGVyaWNzc29uLmNvbTwvYT48bzpwPjwvbzpwPjwvcHJlPg0KPHByZT4tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tPG86
cD48L286cD48L3ByZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_6E58094ECC8D8344914996DAD28F1CCD86625ADGGEMM506MBXchina_--


From nobody Mon Feb 26 15:45:05 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 592E812D952; Mon, 26 Feb 2018 15:44:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151968868731.29322.7194205365214191430@ietfa.amsl.com>
Date: Mon, 26 Feb 2018 15:44:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gq4eqKFbdJnF4JHV5SpZzFLgyio>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rid-14.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 26 Feb 2018 23:44:47 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : RTP Payload Format Restrictions
        Author          : Adam Roach
	Filename        : draft-ietf-mmusic-rid-14.txt
	Pages           : 28
	Date            : 2018-02-26

Abstract:
   In this specification, we define a framework for specifying
   restrictions on RTP streams in the Session Description Protocol.
   This framework defines a new "rid" SDP attribute to unambiguously
   identify the RTP Streams within a RTP Session and restrict the
   streams' payload format parameters in a codec-agnostic way beyond
   what is provided with the regular Payload Types.

   This specification updates RFC4855 to give additional guidance on
   choice of Format Parameter (fmtp) names, and on their relation to the
   restrictions defined by this document.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-rid-14
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-rid-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rid-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 27 01:45:15 2018
Return-Path: <ali.begen@networked.media>
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 9ADAA1274D2 for <mmusic@ietfa.amsl.com>; Tue, 27 Feb 2018 01:45:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 AQ3AzqhA51Im for <mmusic@ietfa.amsl.com>; Tue, 27 Feb 2018 01:45:13 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 D2C5D12702E for <mmusic@ietf.org>; Tue, 27 Feb 2018 01:45:12 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id q83so22832411wme.5 for <mmusic@ietf.org>; Tue, 27 Feb 2018 01:45:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WAO6dEnTTpIgyNQgANf2aBwyOu+KJ8pC3z8DYVgD1N4=; b=L6yToNBtjhF4PEDEJIQp2VA2LC4iBzGc0Az16kb3+JlQItKtCZoiwSBC4MhQAWPhHq 0pW2+fVn+sCslTIEWIcIagZJqPc7yBeDc4KfYcbhdHl5+BNGlDdZoWicH3Fq5N7qJlgO hPPgCBhJl8x9cYwEEvQ36N4FZDTQr+NzH4ykZ8ZZrS9JpPBkonuCnjZfe7NvPhUfi/5s t1V7KIhbKjv0s4nIAcOB15swvXIjD5bR6vRQx4vadbYJfnKqBI+/1k8PSfF34QW2a5iD +fVOoYPVpb9L4dZbzUbUZOy2/sRkzo4Ca0Krt5DkhzvjBETxr2nYE95i1gedrCrmxz1b o05g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WAO6dEnTTpIgyNQgANf2aBwyOu+KJ8pC3z8DYVgD1N4=; b=OlCpTdd8eRxUZzI2/kn3ZGKuTnzpAjc7QE6QaUOpSCWLkahCKSrB6Rg39x9xBfMuNX XuLtq+qbODM6Ieup3EOTnJ3JFDiPujZn8GaGrnFw5aOWVxQBn//sOrPm2p1pzxkohFMy Go3xXHsooUiZDoXpFwj8s+HQeuoOjinPr+cs1Y2oFGHY2apkab41VdaxPnUskVibgKUn MNIuhJXY4wqkBdyY4rTk/EDjpv/rjbmyw2nP0SLRE0PpfUSDAR5YiiNFRYnJ+4To/7Gl el4BICV7D1EWZKIJkm6JwxUy5q8MQvDIr8bFC2wWULt6zme200k99yOXHBQex+INuNmf JLJQ==
X-Gm-Message-State: APf1xPBYQTBp+nqmMTE1RpbBaP1jfw094Rvtl2B9lUCOAOgWqxj+px5t OEOF1lrhqtcGZoBilGo6BO8dD9xoMBkU0y2uvNKAU2AF
X-Google-Smtp-Source: AG47ELu2NPUQpWtrj8sINIqYnrv+iff67OZxxRNOOpSF46Zm2NmgSFKXyGgp9dzF8b85PVbn7qy/5wDQ2nx0i/6f3LY=
X-Received: by 10.28.13.138 with SMTP id 132mr9946017wmn.5.1519724711313; Tue, 27 Feb 2018 01:45:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.153.2 with HTTP; Tue, 27 Feb 2018 01:45:10 -0800 (PST)
In-Reply-To: <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org>
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Tue, 27 Feb 2018 12:45:10 +0300
Message-ID: <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com>
To: Colin Perkins <csp@csperkins.org>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11444c1293176405662e7ba5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/ttZSlc9YNMMsqLXV9R19-o9MvZA>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Feb 2018 09:45:14 -0000

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

On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org> wrote:

> > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> > On 2/20/18 10:25 AM, Ali C. Begen wrote:
> >> 6) Section 7:
> >>    One transport that can be used to distribute session descriptions i=
s
> >>    the SAP.  SAP provides both encryption and authentication mechanism=
s,
> >>    but due to the nature of session announcements it is likely that
> >>    there are many occasions where the originator of a session
> >>    announcement cannot be authenticated because the originator is
> >>    previously unknown to the receiver of the announcement and because =
no
> >>    common public key infrastructure is available.
> >> Comment: Does SAP provide integrity protection as well?
> >
> > It appears that this text is carried over directly from rfc4566. But of
> course the expectations for security considerations are much higher than
> they used to be. So perhaps this should be rewritten.
> >
> > Is SAP still used? Perhaps it would be better to simply remove it. If i=
t
> is still used then can we get someone who knows it to write something?
>
> I=E2=80=99m unconvinced SAP is still used, but in principle it provided i=
ntegrity
> protection via a PGP signature. This almost certainly doesn=E2=80=99t mee=
t current
> standards.
>

Proposed text:

One transport that was used to distribute session descriptions is the SAP,
which is currently not much used any more. SAP provided both encryption and
authentication mechanisms, but due to the nature of session announcements
it is likely that there were many occasions where the originator of a
session announcement could not be authenticated because the originator was
previously unknown to the receiver of the announcement and because no
common public key infrastructure was available. In principle, SAP provided
integrity protection via a PGP signature, however, this almost certainly
does not meet the current standards.

Let me know if this works for you.

-acbegen


>
> --
> Colin Perkins
> https://csperkins.org/
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:csp@csperkins.org" target=3D"_blank">csp@csperkins.org</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><spa=
n class=3D"gmail-">&gt; On 20 Feb 2018, at 16:25, Paul Kyzivat &lt;<a href=
=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.mit.edu</a>&gt; wrote:<br>
&gt; On 2/20/18 10:25 AM, Ali C. Begen wrote:<br>
&gt;&gt; 6) Section 7:<br>
&gt;&gt;=C2=A0 =C2=A0 One transport that can be used to distribute session =
descriptions is<br>
&gt;&gt;=C2=A0 =C2=A0 the SAP.=C2=A0 SAP provides both encryption and authe=
ntication mechanisms,<br>
&gt;&gt;=C2=A0 =C2=A0 but due to the nature of session announcements it is =
likely that<br>
&gt;&gt;=C2=A0 =C2=A0 there are many occasions where the originator of a se=
ssion<br>
&gt;&gt;=C2=A0 =C2=A0 announcement cannot be authenticated because the orig=
inator is<br>
&gt;&gt;=C2=A0 =C2=A0 previously unknown to the receiver of the announcemen=
t and because no<br>
&gt;&gt;=C2=A0 =C2=A0 common public key infrastructure is available.<br>
&gt;&gt; Comment: Does SAP provide integrity protection as well?<br>
&gt;<br>
&gt; It appears that this text is carried over directly from rfc4566. But o=
f course the expectations for security considerations are much higher than =
they used to be. So perhaps this should be rewritten.<br>
&gt;<br>
&gt; Is SAP still used? Perhaps it would be better to simply remove it. If =
it is still used then can we get someone who knows it to write something?<b=
r>
<br>
</span>I=E2=80=99m unconvinced SAP is still used, but in principle it provi=
ded integrity protection via a PGP signature. This almost certainly doesn=
=E2=80=99t meet current standards.<br></blockquote><div><br></div><div>Prop=
osed text:</div><div><br></div><div><div>One transport that was used to dis=
tribute session descriptions is the SAP, which is currently not much used a=
ny more. SAP provided both encryption and authentication mechanisms, but du=
e to the nature of session announcements it is likely that there were many =
occasions where the originator of a session announcement could not be authe=
nticated because the originator was previously unknown to the receiver of t=
he announcement and because no common public key infrastructure was availab=
le. In principle, SAP provided integrity protection via a PGP signature, ho=
wever, this almost certainly does not meet the current standards.</div></di=
v><div><br></div><div>Let me know if this works for you.</div><div><br></di=
v><div>-acbegen</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">
<span class=3D"gmail-HOEnZb"><font color=3D"#888888"><br>
--<br>
Colin Perkins<br>
<a href=3D"https://csperkins.org/" rel=3D"noreferrer" target=3D"_blank">htt=
ps://csperkins.org/</a><br>
</font></span><div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"><br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">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/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div></div>

--001a11444c1293176405662e7ba5--


From nobody Tue Feb 27 06:38:22 2018
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2C9126DC2; Tue, 27 Feb 2018 06:38:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: ben@nostrum.com, mmusic@ietf.org, mmusic-chairs@ietf.org, Flemming Andreasen <fandreas@cisco.com>, fandreas@cisco.com, draft-ietf-mmusic-rid@ietf.org
Reply-To: ietf@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <151974230026.28505.5811234487991578187.idtracker@ietfa.amsl.com>
Date: Tue, 27 Feb 2018 06:38:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/gE_5LJ439wYyY-q1ceRwHGqDUUc>
Subject: [MMUSIC] EXTENDED Last Call: <draft-ietf-mmusic-rid-14.txt> (RTP Payload Format Restrictions) to Proposed Standard
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Feb 2018 14:38:20 -0000

The IESG has received a request from the Multiparty Multimedia Session
Control WG (mmusic) to consider the following document: - 'RTP Payload Format
Restrictions'
  <draft-ietf-mmusic-rid-14.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
ietf@ietf.org mailing lists by 2018-03-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   In this specification, we define a framework for specifying
   restrictions on RTP streams in the Session Description Protocol.
   This framework defines a new "rid" SDP attribute to unambiguously
   identify the RTP Streams within a RTP Session and restrict the
   streams' payload format parameters in a codec-agnostic way beyond
   what is provided with the regular Payload Types.

   This specification updates RFC4855 to give additional guidance on
   choice of Format Parameter (fmtp) names, and on their relation to the
   restrictions defined by this document.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rid/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rid/ballot/


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





From nobody Tue Feb 27 12:54:40 2018
Return-Path: <rjsparks@nostrum.com>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B3712D87F; Tue, 27 Feb 2018 12:54:27 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: ietf@ietf.org, draft-ietf-mmusic-rid.all@ietf.org, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151976486707.28513.8133879591048964555@ietfa.amsl.com>
Date: Tue, 27 Feb 2018 12:54:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/VAEJ2mIMVyz5wdSw_zMiAGJTxS0>
Subject: [MMUSIC] Genart last call review of draft-ietf-mmusic-rid-14
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Feb 2018 20:54:27 -0000

Reviewer: Robert Sparks
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mmusic-rid-14
Reviewer: Robert Sparks
Review Date: 2018-02-27
IETF LC End Date: 2018-03-30
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with nits

Nits:

I could see implementor disagreement around what's allowed when modifying a
session driven by the statement in the introduction that "They do not relax any
existing descriptions." (where "They" here are the restrictions communicated
with this attribute). Please look for a way to make it clear that an updating
offer-answer round _can_ result in fewer restrictions than the original round
did, just not fewer restrictions than the description places on the media if
the "rid" extension is not present.

(Micronit): I don't think the "To be clear" in the first paragraph on page 5
helps. I also worry that "it" may not have a clear meaning in "Such
implementations must send it" later in that paragraph.

At the description of max-bpp on page 7, the last sentence is awkward. Do you
perhaps mean "These values MUST NOT be encoded with more than four digits to
the right of the decimal point."?

In the second paragraph of section 6, "its own unique 5-tuple" is arcane if the
reader hasn't read the rest of the rtcweb work. Could you provide a description
or a pointer to a description here?

At section 6.3, where you say 'For each "a=rid" line:', should you say 'For
each "a=rid" line that has not been discarded by the requirements in section
6.2:'?

I found "a non-empty union" to be a confusing description of the condition you
are trying to convey in section 8. (A union of two sets, at least one of which
is not empty is going to be non-empty). I'm not sure intersection is the right
word here either. Perhaps you could find a different way to characterize the
condition?

The BNF for rid-id allows rid-ids like "This-is_my-favorite" or
"Gm-Cqzkj4VHVD". But all the examples use single digits for rid-ids. I see the
statement that "the actual identifiers used for RIDs are expected to be
opaque". I strongly encourage putting some opaque ones in the examples.

Consider reminding people that ABNF quoted strings are case-insensitive, and
that the grammar as written will allow things like "MaX-WiDtH" and "rECv". If
that's not what you want, consider bringing in RFC7405. 



From nobody Tue Feb 27 15:20:03 2018
Return-Path: <agenda@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C185812EAA4; Tue, 27 Feb 2018 15:11:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <fandreas@cisco.com>, <mmusic-chairs@ietf.org>
Cc: ben@nostrum.com, mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151977308478.5200.908438564180312213.idtracker@ietfa.amsl.com>
Date: Tue, 27 Feb 2018 15:11:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/lavJK84k6HkylfRp3-xF_fBRbic>
Subject: [MMUSIC] mmusic - Requested session has been scheduled for IETF 101
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 27 Feb 2018 23:11:27 -0000

Dear Flemming Andreasen,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 

mmusic Session 1 (1:00:00)
    Friday, Morning Session I 0930-1130
    Room Name: Richmond/Chelsea/Tower size: 75
    ---------------------------------------------
    


Request Information:


---------------------------------------------------------
Working Group Name: Multiparty Multimedia Session Control
Area Name: Applications and Real-Time Area
Session Requester: Flemming Andreasen

Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 30
Conflicts to Avoid: 
 First Priority: quic perc tls ice httpbis rtcweb avtcore sipcore dispatch payload core dots sipbrandy
 Second Priority: clue xrblock rmcat stir tram sfc regext



People who must be present:
  Ben Campbell
  Flemming Andreasen
  Bo Burman

Resources Requested:

Special Requests:
  
---------------------------------------------------------


From nobody Wed Feb 28 00:22:51 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: mmusic@ietf.org
Delivered-To: mmusic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 79BF8124207; Wed, 28 Feb 2018 00:22:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: mmusic@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.73.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151980617046.5200.18272579892578470187@ietfa.amsl.com>
Date: Wed, 28 Feb 2018 00:22:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/eJxzRNaTeKxXhr4hHCSI1PTeHP8>
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-17.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 08:22:50 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiparty Multimedia Session Control WG of the IETF.

        Title           : A Framework for SDP Attributes when Multiplexing
        Author          : Suhas Nandakumar
	Filename        : draft-ietf-mmusic-sdp-mux-attributes-17.txt
	Pages           : 97
	Date            : 2018-02-28

Abstract:
   The purpose of this specification is to provide a framework for
   analyzing the multiplexing characteristics of Session Description
   Protocol (SDP) attributes when SDP is used to negotiate the usage of
   single 5-tuple for sending and receiving media associated with
   multiple media descriptions.

   This specification also categorizes the existing SDP attributes based
   on the framework described herein.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-17
https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-mux-attributes-17

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-17


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Feb 28 01:47:47 2018
Return-Path: <suhasietf@gmail.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 82A4C12EAEC for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 01:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 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, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, 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 eBZreXpdpvbd for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 01:47:43 -0800 (PST)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (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 B97F112EAD8 for <mmusic@ietf.org>; Wed, 28 Feb 2018 01:47:43 -0800 (PST)
Received: by mail-vk0-x22d.google.com with SMTP id q7so1081761vkh.3 for <mmusic@ietf.org>; Wed, 28 Feb 2018 01:47:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=COXqrjhGOvT9U0OHoQEDmO57gu8D8QsU5LS4MI3GHzs=; b=bQJk9QAileeDiO6K8Re4kpDTxWzHJ1fzUjjhzCNOT+iywA+Be5Nm4kkmssyoy7qe4+ k7U25hp7kHR7vtqdDMEsUYAw63OBMii8WjHeyDnvJOn+wCrWLjW0U2JutygO+K/ZeSVj +RC3dpnX/2mQAD7BXIFgSHPok6kvBcvfYtuR1Z1kh4hYC+J9T0jJbR8wIbBfLFctco7H zcpS8vjDmxM6pgIuc0hl+BuaVrdn+VXKeHxmqsxhwVTL/sznhQTu0jWtp8vUBLrDnq2D yzG59+luIQyF79v9G3qcECd5HUEtfbKvJsZOk+JMwKYVTgi4Y5y/NZXExlw5rjVPENua 6cbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=COXqrjhGOvT9U0OHoQEDmO57gu8D8QsU5LS4MI3GHzs=; b=i5y+rpDLUi1ho+TmFuJXKubflFSvq49nbCNhsCltn6GwfzLSpnAMZtJ8XyVVf4wHYl 3TDnH7TOC9fL2Ek7Ic+QtP1Qjf20GVCa6Ui1wxlcZtNd2ADNrlduxKJ6ydguMV0n5tAN qdwP7q96ALm3rhP95cZxzJUa2veW+6oqdR517fDhgXK7z6BkKjhy+LPltY+u8DQ8fBJZ DMD3EZuyQUGVwNpmDeo4n7glnYv4fXVxT/yfYC3JptBB3DmA2tOqkHYm4uD+/lAugmGw ROIhAZAaQgkC93rsLtyg7UnfuWO+tvnh57gXZ4rwagfC+COyouWO5jXfCYp5c4t2XEjm ySiQ==
X-Gm-Message-State: APf1xPD/DHEnfR9IqxsdzRYSkIoJHCr2Q50Qnkjpxvn2XP6kaK+wFdKC ZHRWFR8RX5agoX06GT3YxMpaJa5Nh+hFBnK2rKY=
X-Google-Smtp-Source: AG47ELsCUU20f/XSf+dq8s/OkC+bTGwyErJvgxJdtKDYJLnrxFkP/IMmY3qwyDc0yQggBt2HTfwfYJL+DLZiavoL/h4=
X-Received: by 10.31.227.1 with SMTP id a1mr12654425vkh.195.1519811262607; Wed, 28 Feb 2018 01:47:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.84.146 with HTTP; Wed, 28 Feb 2018 01:47:42 -0800 (PST)
In-Reply-To: <151980617046.5200.18272579892578470187@ietfa.amsl.com>
References: <151980617046.5200.18272579892578470187@ietfa.amsl.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 28 Feb 2018 01:47:42 -0800
Message-ID: <CAMRcRGRd-FuegamSfYdnbZXNQThCeMYckp7xjiO89Xi_Gq1G9A@mail.gmail.com>
To: mmusic WG <mmusic@ietf.org>
Cc: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary="001a114df6226ef83c056642a216"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/bozu2My1oSLFqq-xjhOJShnHin0>
Subject: Re: [MMUSIC] I-D Action: draft-ietf-mmusic-sdp-mux-attributes-17.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 09:47:46 -0000

--001a114df6226ef83c056642a216
Content-Type: text/plain; charset="UTF-8"

This version adds a Note to IDENTICAL category definition to clarify its
usage.

Thanks
Suhas

On Wed, Feb 28, 2018 at 12:22 AM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Multiparty Multimedia Session Control WG
> of the IETF.
>
>         Title           : A Framework for SDP Attributes when Multiplexing
>         Author          : Suhas Nandakumar
>         Filename        : draft-ietf-mmusic-sdp-mux-attributes-17.txt
>         Pages           : 97
>         Date            : 2018-02-28
>
> Abstract:
>    The purpose of this specification is to provide a framework for
>    analyzing the multiplexing characteristics of Session Description
>    Protocol (SDP) attributes when SDP is used to negotiate the usage of
>    single 5-tuple for sending and receiving media associated with
>    multiple media descriptions.
>
>    This specification also categorizes the existing SDP attributes based
>    on the framework described herein.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attributes/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes-17
> https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-
> mux-attributes-17
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-sdp-mux-attributes-17
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr"><div>This version adds a Note to IDENTICAL category defini=
tion to clarify its usage.=C2=A0</div><div><br></div><div>Thanks</div><div>=
Suhas=C2=A0</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Feb 28, 2018 at 12:22 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:=
internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Multiparty Multimedia Session Control WG o=
f the IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 A Framework for SDP Attributes when Multiplexing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Suha=
s Nandakumar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-mmusic-sdp-mux-attr<wbr>ibutes-17.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 97<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2018-02-28<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The purpose of this specification is to provide a framework fo=
r<br>
=C2=A0 =C2=A0analyzing the multiplexing characteristics of Session Descript=
ion<br>
=C2=A0 =C2=A0Protocol (SDP) attributes when SDP is used to negotiate the us=
age of<br>
=C2=A0 =C2=A0single 5-tuple for sending and receiving media associated with=
<br>
=C2=A0 =C2=A0multiple media descriptions.<br>
<br>
=C2=A0 =C2=A0This specification also categorizes the existing SDP attribute=
s based<br>
=C2=A0 =C2=A0on the framework described herein.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-sdp-mux-attri=
butes/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d=
<wbr>oc/draft-ietf-mmusic-sdp-mux-a<wbr>ttributes/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-ietf-mmusic-sdp-mux-attributes=
-17" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dr<wb=
r>aft-ietf-mmusic-sdp-mux-attrib<wbr>utes-17</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-mmusic-sdp-mux-=
attributes-17" rel=3D"noreferrer" target=3D"_blank">https://datatracker.iet=
f.org/d<wbr>oc/html/draft-ietf-mmusic-sdp-<wbr>mux-attributes-17</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-sdp-mux-at=
tributes-17" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcd=
iff?u<wbr>rl2=3Ddraft-ietf-mmusic-sdp-mux-<wbr>attributes-17</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-dr<wbr>afts/</a><br>
<br>
______________________________<wbr>_________________<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/l<wbr>istinfo/mmusic</a><br=
>
</blockquote></div><br></div></div>

--001a114df6226ef83c056642a216--


From nobody Wed Feb 28 06:36:14 2018
Return-Path: <pkyzivat@alum.mit.edu>
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 2B778129C5D for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 06:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 iVbixVxwbw1P for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 06:36:10 -0800 (PST)
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id 80F3C126BF3 for <mmusic@ietf.org>; Wed, 28 Feb 2018 06:36:10 -0800 (PST)
X-AuditID: 1207440f-acfff70000000ab0-de-5a96be57fb5a
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 21.D4.02736.75EB69A5; Wed, 28 Feb 2018 09:36:08 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w1SEa6Yt026291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <mmusic@ietf.org>; Wed, 28 Feb 2018 09:36:06 -0500
To: mmusic@ietf.org
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org> <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu>
Date: Wed, 28 Feb 2018 09:36:06 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKIsWRmVeSWpSXmKPExsUixO6iqBuxb1qUQftPTYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEr4+zKfywFq0Uq/i1exdLA+Iq/i5GTQ0LAROLMomfsXYxcHEIC O5gkfl1/CuV8Z5JoftPJClIlLOAu8f/zK2YQW0RAWGLG279sEEXfGCUO7vzFBpJgE9CSmHPo P0sXIwcHr4C9xKkN2SBhFgFVicfzXzOB2KICaRKvnu0Am8MrIChxcuYTFhCbUyBQomN2D1ic WcBMYt7mh1C2uMStJ/OZIGx5ieats5knMPLPQtI+C0nLLCQts5C0LGBkWcUol5hTmqubm5iZ U5yarFucnJiXl1qka6KXm1mil5pSuokREpb8Oxi71sscYhTgYFTi4T2QOzVKiDWxrLgy9xCj JAeTkiiv+p5pUUJ8SfkplRmJxRnxRaU5qcWHGCU4mJVEeE9vB8rxpiRWVqUW5cOkpDlYlMR5 1Zeo+wkJpCeWpGanphakFsFkZTg4lCR4M/YCNQoWpaanVqRl5pQgpJk4OEGG8wANnwtSw1tc kJhbnJkOkT/FaMzRcvFJGzPHjRev25iFWPLy81KlxHl5QUoFQEozSvPgpsFSyytGcaDnhHkf gFTxANMS3LxXQKuYgFYd+TwFZFVJIkJKqoFxQdDp08u0lvknqJW87yhVfiBUPD9K9nPxplNV H5uWZjQKpV6V5z3e1WmqM3fdzzu6xRk2WpNmseZ9s2St4zFzFu1q1ppzkF18i+4LsV8WQfGl t/mDd8/jVMgye1Iv/GzuxERJfwG3spnFE87m9YZVcb/set5ya58yy5HZmhVm8j5XJ5v0LFFi Kc5INNRiLipOBAAyeW7MCAMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/cBPiEPeOayNS9o81-q2WlKWFLKo>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 14:36:13 -0000

On 2/27/18 4:45 AM, Ali C. Begen wrote:
> 
> 
> On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org 
> <mailto:csp@csperkins.org>> wrote:
> 
>     > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu <mailto:pkyzivat@alum.mit.edu>> wrote:
>     > On 2/20/18 10:25 AM, Ali C. Begen wrote:
>     >> 6) Section 7:
>     >>    One transport that can be used to distribute session descriptions is
>     >>    the SAP.  SAP provides both encryption and authentication mechanisms,
>     >>    but due to the nature of session announcements it is likely that
>     >>    there are many occasions where the originator of a session
>     >>    announcement cannot be authenticated because the originator is
>     >>    previously unknown to the receiver of the announcement and because no
>     >>    common public key infrastructure is available.
>     >> Comment: Does SAP provide integrity protection as well?
>     >
>     > It appears that this text is carried over directly from rfc4566. But of course the expectations for security considerations are much higher than they used to be. So perhaps this should be rewritten.
>     >
>     > Is SAP still used? Perhaps it would be better to simply remove it. If it is still used then can we get someone who knows it to write something?
> 
>     I’m unconvinced SAP is still used, but in principle it provided
>     integrity protection via a PGP signature. This almost certainly
>     doesn’t meet current standards.
> 
> 
> Proposed text:
> 
> One transport that was used to distribute session descriptions is the 
> SAP, which is currently not much used any more. SAP provided both 
> encryption and authentication mechanisms, but due to the nature of 
> session announcements it is likely that there were many occasions where 
> the originator of a session announcement could not be authenticated 
> because the originator was previously unknown to the receiver of the 
> announcement and because no common public key infrastructure was 
> available. In principle, SAP provided integrity protection via a PGP 
> signature, however, this almost certainly does not meet the current 
> standards.
> 
> Let me know if this works for you.

I don't find this helpful. Rather it just seems odd for security 
considerations to be talking about a protocol that isn't used.

I think we could just drop the paragraph in question without losing 
anything.

Or, we could pick another protocol (e.g., SIP) as an example and discuss 
how security works there.

	Thanks,
	Paul


From nobody Wed Feb 28 07:09:18 2018
Return-Path: <ali.begen@networked.media>
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 8E81912EB07 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 07:09:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 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_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 rEOL2iq9CVd6 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 07:09:11 -0800 (PST)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 CD99F126E01 for <mmusic@ietf.org>; Wed, 28 Feb 2018 07:09:10 -0800 (PST)
Received: by mail-wr0-x22e.google.com with SMTP id w77so2773841wrc.6 for <mmusic@ietf.org>; Wed, 28 Feb 2018 07:09:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=sjlWqBrYVDByGRDF5OVQxjxvrwni4KI6ZWoK1gJQ2RI=; b=f6Fu3WRtJe40oyP3U5qHqOvtocF1TjiowgWXTLpAdLF5kGtmUHdlwAgr33sh8PxItA OemRV6Ok7zHXzjcuB3io65EeF+d5Z8OdwcIip2BQ4TJXq+1eUdyPki7+WMlUuBGrrgZ4 99sXBrtBM73O1StOFxTgVPu523gFe2G31F0Tn3HEZZXnDoiXf/n3aTDmo8Clyh8GdWpm rQUIe3+xMh+eZqHeCPi3Gd5Wv/j0VIHVfUhHQ8AswGVTESoHnP2GxOOn1S6eCiU0IWdI LtPc3G+aRgP7Ho4LcvvDJ+zS9ufBMUF6CF5G5KS4XQkriCXJBPJY01ryZrADsLXblb+S 6aIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=sjlWqBrYVDByGRDF5OVQxjxvrwni4KI6ZWoK1gJQ2RI=; b=JaOGqKsD+xItumjzPAsMbNKAVnTw+nO1aeiqmrUwxmKt+8YXQKA3ErsPa6qQd9m9Y/ KEcH4NnVGjuuO1A2mrCZG/g9LDEus2kcFtrLgVJnE13jy7Knm7Uq7FqMVb6zquyncuRt sIj19cIxeNjAmYD7hT453TnA90Lm+3KZoV8F/IwQ5FDJmUMnt6BS9z/aDCDfi30EMiHv c6qaPxBcYklurKXZu5R/1EYc5tLStbcpMFqXunZNMBY+k0JmQN+5kMcuWF0kquKulF9P L/SOUkyf6EBrHjKIdzqfqyQe/EYPZ33ecpPav9e1nXgZkPa+p7+SdGyX+xvCC8zIsVly yJlg==
X-Gm-Message-State: APf1xPDvR0rLA0MSNJihtcYV+patLMdo4Dok1Z6cElj8Y5722KxLYW4s ANAMVi8vX9Plah9lGrmh/+R0guiQA6WFIBpZDH0HZg==
X-Google-Smtp-Source: AH8x226zSYGqAt1w9h9LMVsu74sVOoOwv16EkAcqIvnge1vjQ0/y2hZ4ufHtvxJOtHI2fZayJCBatbwjUSFarTkN/As=
X-Received: by 10.223.151.101 with SMTP id r92mr16515468wrb.120.1519830549237;  Wed, 28 Feb 2018 07:09:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.153.2 with HTTP; Wed, 28 Feb 2018 07:09:08 -0800 (PST)
In-Reply-To: <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org> <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com> <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu>
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Wed, 28 Feb 2018 18:09:08 +0300
Message-ID: <CAA4Mczv24ugVmoF=ssyXdPGf+JZFjSbsLESpN3awRLBVxT5tMg@mail.gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Cc: mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="f403045d5cf201a16505664720e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/Gsm8SY4NMM-Px-iqWMSjitp3mBM>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 15:09:17 -0000

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

On Wed, Feb 28, 2018 at 5:36 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote=
:

> On 2/27/18 4:45 AM, Ali C. Begen wrote:
>
>>
>>
>> On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org
>> <mailto:csp@csperkins.org>> wrote:
>>
>>     > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu
>> <mailto:pkyzivat@alum.mit.edu>> wrote:
>>     > On 2/20/18 10:25 AM, Ali C. Begen wrote:
>>     >> 6) Section 7:
>>     >>    One transport that can be used to distribute session
>> descriptions is
>>     >>    the SAP.  SAP provides both encryption and authentication
>> mechanisms,
>>     >>    but due to the nature of session announcements it is likely th=
at
>>     >>    there are many occasions where the originator of a session
>>     >>    announcement cannot be authenticated because the originator is
>>     >>    previously unknown to the receiver of the announcement and
>> because no
>>     >>    common public key infrastructure is available.
>>     >> Comment: Does SAP provide integrity protection as well?
>>     >
>>     > It appears that this text is carried over directly from rfc4566.
>> But of course the expectations for security considerations are much high=
er
>> than they used to be. So perhaps this should be rewritten.
>>     >
>>     > Is SAP still used? Perhaps it would be better to simply remove it.
>> If it is still used then can we get someone who knows it to write someth=
ing?
>>
>>     I=E2=80=99m unconvinced SAP is still used, but in principle it provi=
ded
>>     integrity protection via a PGP signature. This almost certainly
>>     doesn=E2=80=99t meet current standards.
>>
>>
>> Proposed text:
>>
>> One transport that was used to distribute session descriptions is the
>> SAP, which is currently not much used any more. SAP provided both
>> encryption and authentication mechanisms, but due to the nature of sessi=
on
>> announcements it is likely that there were many occasions where the
>> originator of a session announcement could not be authenticated because =
the
>> originator was previously unknown to the receiver of the announcement an=
d
>> because no common public key infrastructure was available. In principle,
>> SAP provided integrity protection via a PGP signature, however, this alm=
ost
>> certainly does not meet the current standards.
>>
>> Let me know if this works for you.
>>
>
> I don't find this helpful. Rather it just seems odd for security
> considerations to be talking about a protocol that isn't used.
>
> I think we could just drop the paragraph in question without losing
> anything.
>

I am ok with removing the entire paragraph.

-acbegen


>
> Or, we could pick another protocol (e.g., SIP) as an example and discuss
> how security works there.
>
>         Thanks,
>         Paul
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Feb 28, 2018 at 5:36 PM, Paul Kyzivat <span dir=3D"ltr">&lt;<a =
href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.e=
du</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2/27/18 4:45 =
AM, Ali C. Begen wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins &lt;<a href=3D"mailto:csp@cs=
perkins.org" target=3D"_blank">csp@csperkins.org</a> &lt;mailto:<a href=3D"=
mailto:csp@csperkins.org" target=3D"_blank">csp@csperkins.org</a>&gt;&gt; w=
rote:<span class=3D""><br>
<br>
=C2=A0 =C2=A0 &gt; On 20 Feb 2018, at 16:25, Paul Kyzivat &lt;<a href=3D"ma=
ilto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat@alum.mit.edu</a> &lt=
;mailto:<a href=3D"mailto:pkyzivat@alum.mit.edu" target=3D"_blank">pkyzivat=
@alum.mit.edu</a>&gt;<wbr>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; On 2/20/18 10:25 AM, Ali C. Begen wrote:<br>
=C2=A0 =C2=A0 &gt;&gt; 6) Section 7:<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 One transport that can be used to distr=
ibute session descriptions is<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 the SAP.=C2=A0 SAP provides both encryp=
tion and authentication mechanisms,<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 but due to the nature of session announ=
cements it is likely that<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 there are many occasions where the orig=
inator of a session<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 announcement cannot be authenticated be=
cause the originator is<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 previously unknown to the receiver of t=
he announcement and because no<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 common public key infrastructure is ava=
ilable.<br>
=C2=A0 =C2=A0 &gt;&gt; Comment: Does SAP provide integrity protection as we=
ll?<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; It appears that this text is carried over directly from =
rfc4566. But of course the expectations for security considerations are muc=
h higher than they used to be. So perhaps this should be rewritten.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; Is SAP still used? Perhaps it would be better to simply =
remove it. If it is still used then can we get someone who knows it to writ=
e something?<br>
<br>
=C2=A0 =C2=A0 I=E2=80=99m unconvinced SAP is still used, but in principle i=
t provided<br>
=C2=A0 =C2=A0 integrity protection via a PGP signature. This almost certain=
ly<br>
=C2=A0 =C2=A0 doesn=E2=80=99t meet current standards.<br>
<br>
<br>
Proposed text:<br>
<br>
One transport that was used to distribute session descriptions is the SAP, =
which is currently not much used any more. SAP provided both encryption and=
 authentication mechanisms, but due to the nature of session announcements =
it is likely that there were many occasions where the originator of a sessi=
on announcement could not be authenticated because the originator was previ=
ously unknown to the receiver of the announcement and because no common pub=
lic key infrastructure was available. In principle, SAP provided integrity =
protection via a PGP signature, however, this almost certainly does not mee=
t the current standards.<br>
<br>
Let me know if this works for you.<br>
</span></blockquote>
<br>
I don&#39;t find this helpful. Rather it just seems odd for security consid=
erations to be talking about a protocol that isn&#39;t used.<br>
<br>
I think we could just drop the paragraph in question without losing anythin=
g.<br></blockquote><div><br></div><div>I am ok with removing the entire par=
agraph.=C2=A0</div><div><br></div><div>-acbegen</div><div>=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
<br>
Or, we could pick another protocol (e.g., SIP) as an example and discuss ho=
w security works there.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<div class=3D"HOEnZb"><div class=3D"h5"><br=
>
<br>
______________________________<wbr>_________________<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/l<wbr>istinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div></div>

--f403045d5cf201a16505664720e3--


From nobody Wed Feb 28 07:30:45 2018
Return-Path: <Peter.Stevens@bbc.co.uk>
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 B995512DA03 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 07:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 ShZTF5MgfZhu for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 07:30:35 -0800 (PST)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C6A212D940 for <mmusic@ietf.org>; Wed, 28 Feb 2018 07:30:34 -0800 (PST)
Received: from BGB01XI1005.national.core.bbc.co.uk ([10.184.50.55]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w1SFUU42009248; Wed, 28 Feb 2018 15:30:30 GMT
Received: from BGB01XUD1002.national.core.bbc.co.uk ([10.184.52.81]) by BGB01XI1005.national.core.bbc.co.uk ([10.184.50.55]) with mapi id 14.03.0361.001; Wed, 28 Feb 2018 15:30:30 +0000
From: Peter Stevens <Peter.Stevens@bbc.co.uk>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
Thread-Index: AQHTsKYh+UDUFsYJZEOEDcE1LUDspaO57WdC
Date: Wed, 28 Feb 2018 15:30:30 +0000
Message-ID: <2F938AAE444ADB47AFEE6307955A30CE52499A4A@bgb01xud1002>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org> <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com>, <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu>
In-Reply-To: <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23690.007
x-tm-as-result: No--25.462900-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/3gS3WXSHhzqrCoPQOxz2D3tOs_o>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 15:30:42 -0000

I've just seen some of this discussion regarding whether SAP is still being=
 used.

I haven't investigated the details of how it is used within their devices, =
but SAP is used within Dante products, of which there are many from differe=
nt manufacturers.
It might be worth contacting one or more of them for comments.

Peter Stevens

________________________________________
From: Paul Kyzivat [pkyzivat@alum.mit.edu]
Sent: 28 February 2018 14:36
To: mmusic@ietf.org
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP

On 2/27/18 4:45 AM, Ali C. Begen wrote:
>
>
> On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org
> <mailto:csp@csperkins.org>> wrote:
>
>     > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu <mail=
to:pkyzivat@alum.mit.edu>> wrote:
>     > On 2/20/18 10:25 AM, Ali C. Begen wrote:
>     >> 6) Section 7:
>     >>    One transport that can be used to distribute session descriptio=
ns is
>     >>    the SAP.  SAP provides both encryption and authentication mecha=
nisms,
>     >>    but due to the nature of session announcements it is likely tha=
t
>     >>    there are many occasions where the originator of a session
>     >>    announcement cannot be authenticated because the originator is
>     >>    previously unknown to the receiver of the announcement and beca=
use no
>     >>    common public key infrastructure is available.
>     >> Comment: Does SAP provide integrity protection as well?
>     >
>     > It appears that this text is carried over directly from rfc4566. Bu=
t of course the expectations for security considerations are much higher th=
an they used to be. So perhaps this should be rewritten.
>     >
>     > Is SAP still used? Perhaps it would be better to simply remove it. =
If it is still used then can we get someone who knows it to write something=
?
>
>     I=92m unconvinced SAP is still used, but in principle it provided
>     integrity protection via a PGP signature. This almost certainly
>     doesn=92t meet current standards.
>
>
> Proposed text:
>
> One transport that was used to distribute session descriptions is the
> SAP, which is currently not much used any more. SAP provided both
> encryption and authentication mechanisms, but due to the nature of
> session announcements it is likely that there were many occasions where
> the originator of a session announcement could not be authenticated
> because the originator was previously unknown to the receiver of the
> announcement and because no common public key infrastructure was
> available. In principle, SAP provided integrity protection via a PGP
> signature, however, this almost certainly does not meet the current
> standards.
>
> Let me know if this works for you.

I don't find this helpful. Rather it just seems odd for security
considerations to be talking about a protocol that isn't used.

I think we could just drop the paragraph in question without losing
anything.

Or, we could pick another protocol (e.g., SIP) as an example and discuss
how security works there.

        Thanks,
        Paul




-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specif=
ically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------


From nobody Wed Feb 28 09:37:19 2018
Return-Path: <pkyzivat@alum.mit.edu>
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 1B61912AF84 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 09:37:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 Xyg3W03Zv_fe for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 09:37:16 -0800 (PST)
Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id E9E0F124217 for <mmusic@ietf.org>; Wed, 28 Feb 2018 09:37:15 -0800 (PST)
X-AuditID: 1207440d-98bff70000000c05-39-5a96e8c99060
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 06.08.03077.9C8E69A5; Wed, 28 Feb 2018 12:37:14 -0500 (EST)
Received: from PaulKyzivatsMBP.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id w1SHbAgI004416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 28 Feb 2018 12:37:12 -0500
To: Peter Stevens <Peter.Stevens@bbc.co.uk>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org> <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com> <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu> <2F938AAE444ADB47AFEE6307955A30CE52499A4A@bgb01xud1002>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d327461f-a9d7-eb62-ed96-2405dd369cca@alum.mit.edu>
Date: Wed, 28 Feb 2018 12:39:20 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <2F938AAE444ADB47AFEE6307955A30CE52499A4A@bgb01xud1002>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrPIsWRmVeSWpSXmKPExsUixO6iqHvqxbQogwetihZTlz9msTj0ah2j A5PHg80r2DyWLPnJFMAUxWWTkpqTWZZapG+XwJWx5cgq1oLtChXHWxqYGhhnSHYxcnJICJhI PPyznrmLkYtDSGAHk8S05/fYQRJCAg+ZJM7t1QSxhQXcJf5/fsUMYosIREvMevqaHaLhGZNE 9/cNrCAJNgEtiTmH/rOA2LwC9hKvr25mBLFZBFQl7nRtA6sRFUiTePVsBzNEjaDEyZlPwOo5 BVwknryYzARiMwvYStyZu5sZwhaXuPVkPlRcXqJ562zmCYz8s5C0z0LSMgtJyywkLQsYWVYx yiXmlObq5iZm5hSnJusWJyfm5aUW6Rrp5WaW6KWmlG5ihIQq7w7G/+tkDjEKcDAq8fA67J8W JcSaWFZcmXuIUZKDSUmUt+8oUIgvKT+lMiOxOCO+qDQntfgQowQHs5II7+ntQDnelMTKqtSi fJiUNAeLkjiv2hJ1PyGB9MSS1OzU1ILUIpisDAeHkgSvNDAmhQSLUtNTK9Iyc0oQ0kwcnCDD eYCGP3oOMry4IDG3ODMdIn+K0Zij5eKTNmaOGy9etzELseTl56VKifPqg5QKgJRmlObBTYOl m1eM4kDPCfMeBaniAaYquHmvgFYxAa068nkKyKqSRISUVANjobmykdtEAz5us+wv/x2tavtz JRobIpeYKFy4cUe0g/24aEmx0q0NXM99nWvrPhfEnn70YsusThuOJwwHQ+ZP6L//OjrOwrpw numk0gsz3x+bW9i6t/TIqcP/IlYHnK9m2GDXeUzinf4Ph8unj3jxxd2wZzERXGp0NiJwUn/F 61XFhQKzORWVWIozEg21mIuKEwGpdQJYEgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/4HC7gCO6n8uB08m0E_ug8-fBBNg>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 17:37:18 -0000

On 2/28/18 10:30 AM, Peter Stevens wrote:
> I've just seen some of this discussion regarding whether SAP is still being used.
> 
> I haven't investigated the details of how it is used within their devices, but SAP is used within Dante products, of which there are many from different manufacturers.
> It might be worth contacting one or more of them for comments.

In any case, in this context it was only being used as an example. At 
the time it was first written it may well have been the only example. 
But today it is clearly not the the most common, or well known, use. So 
it is kind of a weird thing to include.

	Thanks,
	Paul

> Peter Stevens
> 
> ________________________________________
> From: Paul Kyzivat [pkyzivat@alum.mit.edu]
> Sent: 28 February 2018 14:36
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
> 
> On 2/27/18 4:45 AM, Ali C. Begen wrote:
>>
>>
>> On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org
>> <mailto:csp@csperkins.org>> wrote:
>>
>>      > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu <mailto:pkyzivat@alum.mit.edu>> wrote:
>>      > On 2/20/18 10:25 AM, Ali C. Begen wrote:
>>      >> 6) Section 7:
>>      >>    One transport that can be used to distribute session descriptions is
>>      >>    the SAP.  SAP provides both encryption and authentication mechanisms,
>>      >>    but due to the nature of session announcements it is likely that
>>      >>    there are many occasions where the originator of a session
>>      >>    announcement cannot be authenticated because the originator is
>>      >>    previously unknown to the receiver of the announcement and because no
>>      >>    common public key infrastructure is available.
>>      >> Comment: Does SAP provide integrity protection as well?
>>      >
>>      > It appears that this text is carried over directly from rfc4566. But of course the expectations for security considerations are much higher than they used to be. So perhaps this should be rewritten.
>>      >
>>      > Is SAP still used? Perhaps it would be better to simply remove it. If it is still used then can we get someone who knows it to write something?
>>
>>      I’m unconvinced SAP is still used, but in principle it provided
>>      integrity protection via a PGP signature. This almost certainly
>>      doesn’t meet current standards.
>>
>>
>> Proposed text:
>>
>> One transport that was used to distribute session descriptions is the
>> SAP, which is currently not much used any more. SAP provided both
>> encryption and authentication mechanisms, but due to the nature of
>> session announcements it is likely that there were many occasions where
>> the originator of a session announcement could not be authenticated
>> because the originator was previously unknown to the receiver of the
>> announcement and because no common public key infrastructure was
>> available. In principle, SAP provided integrity protection via a PGP
>> signature, however, this almost certainly does not meet the current
>> standards.
>>
>> Let me know if this works for you.
> 
> I don't find this helpful. Rather it just seems odd for security
> considerations to be talking about a protocol that isn't used.
> 
> I think we could just drop the paragraph in question without losing
> anything.
> 
> Or, we could pick another protocol (e.g., SIP) as an example and discuss
> how security works there.
> 
>          Thanks,
>          Paul
> 
> 
> 
> 
> -----------------------------
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and
> may contain personal views which are not the views of the BBC unless specifically stated.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender
> immediately.
> Please note that the BBC monitors e-mails
> sent or received.
> Further communication will signify your consent to
> this.
> -----------------------------
> 


From nobody Wed Feb 28 09:57:01 2018
Return-Path: <christer.holmberg@ericsson.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 5B6D4124F57 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 09:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 ZKVoSqSBa_j6 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 09:56:57 -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 BC0B812D86C for <mmusic@ietf.org>; Wed, 28 Feb 2018 09:56:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1519840614; 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=W1IbN3NY6f6RF9ttkyOT3BYbkynIOCuGoRz75K8jNWU=; b=Ux2l+GSebD1u63EnnpublPfx7tbnCDuLuarrRA0/NCIcCQsW+4N1ewXYYZP4UGom uaXElanWqRjQvg/AuyZEClRq7EeWhdwDK62UqR1Qn6sPhNN/EOSKsz/djVyrSwFM 5F8ZyBUPieAyD933O1bT32qjDeIJfNgTn99QwGxQW8E=;
X-AuditID: c1b4fb2d-87c029c000005540-d3-5a96ed66d867
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 66.CE.21824.66DE69A5; Wed, 28 Feb 2018 18:56:54 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.82]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0352.000; Wed, 28 Feb 2018 18:56:15 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Peter Stevens <Peter.Stevens@bbc.co.uk>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
Thread-Index: AQHTqmeD5SDU6dt9xkqAaSmXAPdmaKOxC3eAgAbuRgCAAeOeAIAADzMAgAAj/wCAABRcUA==
Date: Wed, 28 Feb 2018 17:56:14 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B6C1B42C2@ESESSMB109.ericsson.se>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org> <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com> <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu> <2F938AAE444ADB47AFEE6307955A30CE52499A4A@bgb01xud1002> <d327461f-a9d7-eb62-ed96-2405dd369cca@alum.mit.edu>
In-Reply-To: <d327461f-a9d7-eb62-ed96-2405dd369cca@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.169]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFLMWRmVeSWpSXmKPExsUyM2K7rm7a22lRBus2WVhMXf6YxeLQq3WM Fis2HGB1YPb4+/4Dk8eDzSvYPJYs+ckUwBzFZZOSmpNZllqkb5fAlfGk/TxLwT71iokT7rM0 MLbJdzFyckgImEhMOL6NvYuRi0NI4DCjxKkXp5kgnMWMEv8vdTB2MXJwsAlYSHT/0wZpEBGo kLi7cCYriC0s4C6xqa2VDaRERMBDYt8PIYiSMInPe9+zgNgsAqoSFy/dZASxeQV8JR6duQs1 fg6zxNdJ/9hBEpwCDhKNv6+BFTEKiEl8P7WGCcRmFhCXuPVkPhPEoQISS/acZ4awRSVePv7H CmErSZzs3swCUa8jsWD3JzYIW1ti2cLXzBCLBSVOznzCMoFRZBaSsbOQtMxC0jILScsCRpZV jKLFqcXFuelGxnqpRZnJxcX5eXp5qSWbGIExcnDLb90djKtfOx5iFOBgVOLhLXs0LUqINbGs uDL3EKMEB7OSCO/p7UAh3pTEyqrUovz4otKc1OJDjNIcLErivCc9eaOEBNITS1KzU1MLUotg skwcnFINjPpCVy95xr274LPRz2Xj38dbBMPrJTfpZcsflLrWdOd55HElN7Xawho/0/6TBhOc DqVyJ6yccfjmG9H++pgD233Tbtw73q9+8qPh9LaSnzIiE0WP8yqJphdvWWz33o/3g878aDex /HhRI71zTL477e/WLFd+X5KgYcnFUbJ5ppH7wSWFp7uOKbEUZyQaajEXFScCAAvZkkmNAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/QOVBUSUwEZDpy6dG4PjhGnRpGrM>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 17:57:00 -0000

Hi,

I agree: there is no need to say anything about SAP in the Security Conside=
rations.=20

I also don't think we need the first sentence in section 4.4, because what =
does it have to do with SDP? If SAP wants to filter, SAP should describe ho=
w to filter.

I'm ok mentioning SAP in Sections 1 and 3.4 - elsewhere I think we should r=
emove it.

Regards,

Christer

-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: 28 February 2018 19:39
To: Peter Stevens <Peter.Stevens@bbc.co.uk>; mmusic@ietf.org
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP

On 2/28/18 10:30 AM, Peter Stevens wrote:
> I've just seen some of this discussion regarding whether SAP is still bei=
ng used.
>=20
> I haven't investigated the details of how it is used within their devices=
, but SAP is used within Dante products, of which there are many from diffe=
rent manufacturers.
> It might be worth contacting one or more of them for comments.

In any case, in this context it was only being used as an example. At the t=
ime it was first written it may well have been the only example.=20
But today it is clearly not the the most common, or well known, use. So it =
is kind of a weird thing to include.

	Thanks,
	Paul

> Peter Stevens
>=20
> ________________________________________
> From: Paul Kyzivat [pkyzivat@alum.mit.edu]
> Sent: 28 February 2018 14:36
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review):=20
> SAP
>=20
> On 2/27/18 4:45 AM, Ali C. Begen wrote:
>>
>>
>> On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org=20
>> <mailto:csp@csperkins.org>> wrote:
>>
>>      > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu <ma=
ilto:pkyzivat@alum.mit.edu>> wrote:
>>      > On 2/20/18 10:25 AM, Ali C. Begen wrote:
>>      >> 6) Section 7:
>>      >>    One transport that can be used to distribute session descript=
ions is
>>      >>    the SAP.  SAP provides both encryption and authentication mec=
hanisms,
>>      >>    but due to the nature of session announcements it is likely t=
hat
>>      >>    there are many occasions where the originator of a session
>>      >>    announcement cannot be authenticated because the originator i=
s
>>      >>    previously unknown to the receiver of the announcement and be=
cause no
>>      >>    common public key infrastructure is available.
>>      >> Comment: Does SAP provide integrity protection as well?
>>      >
>>      > It appears that this text is carried over directly from rfc4566. =
But of course the expectations for security considerations are much higher =
than they used to be. So perhaps this should be rewritten.
>>      >
>>      > Is SAP still used? Perhaps it would be better to simply remove it=
. If it is still used then can we get someone who knows it to write somethi=
ng?
>>
>>      I'm unconvinced SAP is still used, but in principle it provided
>>      integrity protection via a PGP signature. This almost certainly
>>      doesn't meet current standards.
>>
>>
>> Proposed text:
>>
>> One transport that was used to distribute session descriptions is the=20
>> SAP, which is currently not much used any more. SAP provided both=20
>> encryption and authentication mechanisms, but due to the nature of=20
>> session announcements it is likely that there were many occasions=20
>> where the originator of a session announcement could not be=20
>> authenticated because the originator was previously unknown to the=20
>> receiver of the announcement and because no common public key=20
>> infrastructure was available. In principle, SAP provided integrity=20
>> protection via a PGP signature, however, this almost certainly does=20
>> not meet the current standards.
>>
>> Let me know if this works for you.
>=20
> I don't find this helpful. Rather it just seems odd for security=20
> considerations to be talking about a protocol that isn't used.
>=20
> I think we could just drop the paragraph in question without losing=20
> anything.
>=20
> Or, we could pick another protocol (e.g., SIP) as an example and=20
> discuss how security works there.
>=20
>          Thanks,
>          Paul
>=20
>=20
>=20
>=20
> -----------------------------
> http://www.bbc.co.uk
> This e-mail (and any attachments) is confidential and may contain=20
> personal views which are not the views of the BBC unless specifically sta=
ted.
> If you have received it in
> error, please delete it from your system.
> Do not use, copy or disclose the
> information in any way nor act in reliance on it and notify the sender=20
> immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> -----------------------------
>=20

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Wed Feb 28 10:51:16 2018
Return-Path: <ali.begen@networked.media>
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 1ECC9124F57 for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 10:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 oQa20SA8DMSY for <mmusic@ietfa.amsl.com>; Wed, 28 Feb 2018 10:51:08 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 19B501200E5 for <mmusic@ietf.org>; Wed, 28 Feb 2018 10:51:08 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id q83so7004256wme.5 for <mmusic@ietf.org>; Wed, 28 Feb 2018 10:51:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hSYBc5Xh1rR646at9gmAezKMbpNGboEZ5M+NYBnzwqU=; b=tLT5XNH+LxzFZmkOdG9ZPSjq5ys4+jmKcQyt/kUsH7oRF+1PrpE/BvKnTsg8fDCwfP aPpzeKIn/GUzTI2SkTYd1tAZYJXib72XeAiQt5qKNh68z/Fgpjeq6NZB/97Lp56tpy3R Hchq7Ihn6ubdKD88jpWzUcH7djwVXfDKw/uR0AinLpon0lji6REoRCzhoS2ye0kvCXWc mj5+DCc2Jmb5pjEE9ACgqTKc9zZye9Z1a9RGniqFVpA3AyovTQON/IuF+BCgp1KxKcGj vP1MYF4SFcNrEsuFWsCIA1A1fU1+UofaZvxluF2rYrqpL8NR2rGklhT9cLEhai7iDe6v PIFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hSYBc5Xh1rR646at9gmAezKMbpNGboEZ5M+NYBnzwqU=; b=iU1eGphtU2ScVx2s47iAWNdW3F9akhWjGnhJtKYViUM5zxzX/eXreTKGP3WPHlVXla eR5vZrBQHNoPHyS0yymbcilcYN7b69E8SJXGnqs7baRm6yIoW3bXrTZbRMTsvUo1XhKJ 88MpJDeGaAquKCWCLvYtRyo9zDYt7ghZpYmlSv9lRI2sU/D9atd3UIxPa0DFG9a3t85q usjiyKTgFk62sX5U4CUgf5hbWbQF1D89FQJ3H4irhoE/AOgcr1lg9v1bHQkMTjzJANcx Gin+2lHOq3FoYCET8jCqi7fS/9mutoI8k0HmZquKufWNUtB4YqpApFIg2VMGzYr3T7Yp srYg==
X-Gm-Message-State: APf1xPA7TFIHX5s2k+5sltXMXE0mDFnNsDac8ebNxmjZtRRULRhu24Lz 4BRR5z196NQZTrtDlQytFLblY3+NFOUmosHMU4Lv7A==
X-Google-Smtp-Source: AG47ELvCP0k7TqrqRG50qsO/LiTwuBExtpw3tJligJbqlEjAU/iO/BL7v96OF02WYg17xwv0SNmrlF+RxxAdvkypSCA=
X-Received: by 10.28.109.195 with SMTP id b64mr14093560wmi.13.1519843866315; Wed, 28 Feb 2018 10:51:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.153.2 with HTTP; Wed, 28 Feb 2018 10:51:05 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B6C1B42C2@ESESSMB109.ericsson.se>
References: <02C73D37-AA28-4D53-8FD0-9F5F9F261BC2@networked.media> <c6525802-8f77-0ee9-6aae-700c9647b32c@alum.mit.edu> <5D1C540D-86AA-45B9-A503-BB06357972E3@csperkins.org> <CAA4MczvWMMdjtH_K90GfjTnKrx6FNztcDiFmqfs4PgD2yodm_w@mail.gmail.com> <2477cec7-dd04-b391-5731-37ed3d34fbf6@alum.mit.edu> <2F938AAE444ADB47AFEE6307955A30CE52499A4A@bgb01xud1002> <d327461f-a9d7-eb62-ed96-2405dd369cca@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B6C1B42C2@ESESSMB109.ericsson.se>
From: "Ali C. Begen" <ali.begen@networked.media>
Date: Wed, 28 Feb 2018 21:51:05 +0300
Message-ID: <CAA4MczuDP1KvnQf_bJ23ghRBS6_hnykQdaScrcQEwc5SLqcV0A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Cc: Paul Kyzivat <pkyzivat@alum.mit.edu>, Peter Stevens <Peter.Stevens@bbc.co.uk>,  "mmusic@ietf.org" <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="001a11467db6c42bdd05664a393d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mmusic/P2xawCi3kSVRdDkECw7GiC-CQB0>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 28 Feb 2018 18:51:15 -0000

--001a11467db6c42bdd05664a393d
Content-Type: text/plain; charset="UTF-8"

Works for me. I implemented the changes.

-acbegen

On Wed, Feb 28, 2018 at 8:56 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi,
>
> I agree: there is no need to say anything about SAP in the Security
> Considerations.
>
> I also don't think we need the first sentence in section 4.4, because what
> does it have to do with SDP? If SAP wants to filter, SAP should describe
> how to filter.
>
> I'm ok mentioning SAP in Sections 1 and 3.4 - elsewhere I think we should
> remove it.
>
> Regards,
>
> Christer
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: 28 February 2018 19:39
> To: Peter Stevens <Peter.Stevens@bbc.co.uk>; mmusic@ietf.org
> Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review): SAP
>
> On 2/28/18 10:30 AM, Peter Stevens wrote:
> > I've just seen some of this discussion regarding whether SAP is still
> being used.
> >
> > I haven't investigated the details of how it is used within their
> devices, but SAP is used within Dante products, of which there are many
> from different manufacturers.
> > It might be worth contacting one or more of them for comments.
>
> In any case, in this context it was only being used as an example. At the
> time it was first written it may well have been the only example.
> But today it is clearly not the the most common, or well known, use. So it
> is kind of a weird thing to include.
>
>         Thanks,
>         Paul
>
> > Peter Stevens
> >
> > ________________________________________
> > From: Paul Kyzivat [pkyzivat@alum.mit.edu]
> > Sent: 28 February 2018 14:36
> > To: mmusic@ietf.org
> > Subject: Re: [MMUSIC] 4566bis open issues (from Flemming's review):
> > SAP
> >
> > On 2/27/18 4:45 AM, Ali C. Begen wrote:
> >>
> >>
> >> On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins <csp@csperkins.org
> >> <mailto:csp@csperkins.org>> wrote:
> >>
> >>      > On 20 Feb 2018, at 16:25, Paul Kyzivat <pkyzivat@alum.mit.edu
> <mailto:pkyzivat@alum.mit.edu>> wrote:
> >>      > On 2/20/18 10:25 AM, Ali C. Begen wrote:
> >>      >> 6) Section 7:
> >>      >>    One transport that can be used to distribute session
> descriptions is
> >>      >>    the SAP.  SAP provides both encryption and authentication
> mechanisms,
> >>      >>    but due to the nature of session announcements it is likely
> that
> >>      >>    there are many occasions where the originator of a session
> >>      >>    announcement cannot be authenticated because the originator
> is
> >>      >>    previously unknown to the receiver of the announcement and
> because no
> >>      >>    common public key infrastructure is available.
> >>      >> Comment: Does SAP provide integrity protection as well?
> >>      >
> >>      > It appears that this text is carried over directly from rfc4566.
> But of course the expectations for security considerations are much higher
> than they used to be. So perhaps this should be rewritten.
> >>      >
> >>      > Is SAP still used? Perhaps it would be better to simply remove
> it. If it is still used then can we get someone who knows it to write
> something?
> >>
> >>      I'm unconvinced SAP is still used, but in principle it provided
> >>      integrity protection via a PGP signature. This almost certainly
> >>      doesn't meet current standards.
> >>
> >>
> >> Proposed text:
> >>
> >> One transport that was used to distribute session descriptions is the
> >> SAP, which is currently not much used any more. SAP provided both
> >> encryption and authentication mechanisms, but due to the nature of
> >> session announcements it is likely that there were many occasions
> >> where the originator of a session announcement could not be
> >> authenticated because the originator was previously unknown to the
> >> receiver of the announcement and because no common public key
> >> infrastructure was available. In principle, SAP provided integrity
> >> protection via a PGP signature, however, this almost certainly does
> >> not meet the current standards.
> >>
> >> Let me know if this works for you.
> >
> > I don't find this helpful. Rather it just seems odd for security
> > considerations to be talking about a protocol that isn't used.
> >
> > I think we could just drop the paragraph in question without losing
> > anything.
> >
> > Or, we could pick another protocol (e.g., SIP) as an example and
> > discuss how security works there.
> >
> >          Thanks,
> >          Paul
> >
> >
> >
> >
> > -----------------------------
> > http://www.bbc.co.uk
> > This e-mail (and any attachments) is confidential and may contain
> > personal views which are not the views of the BBC unless specifically
> stated.
> > If you have received it in
> > error, please delete it from your system.
> > Do not use, copy or disclose the
> > information in any way nor act in reliance on it and notify the sender
> > immediately.
> > Please note that the BBC monitors e-mails sent or received.
> > Further communication will signify your consent to this.
> > -----------------------------
> >
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

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

<div dir=3D"ltr">Works for me. I implemented the changes.<div><br></div><di=
v>-acbegen</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Wed, Feb 28, 2018 at 8:56 PM, Christer Holmberg <span dir=3D"ltr">&=
lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">chri=
ster.holmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">Hi,<br>
<br>
I agree: there is no need to say anything about SAP in the Security Conside=
rations.<br>
<br>
I also don&#39;t think we need the first sentence in section 4.4, because w=
hat does it have to do with SDP? If SAP wants to filter, SAP should describ=
e how to filter.<br>
<br>
I&#39;m ok mentioning SAP in Sections 1 and 3.4 - elsewhere I think we shou=
ld remove it.<br>
<br>
Regards,<br>
<br>
Christer<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-boun=
ces@ietf.<wbr>org</a>] On Behalf Of Paul Kyzivat<br>
Sent: 28 February 2018 19:39<br>
To: Peter Stevens &lt;<a href=3D"mailto:Peter.Stevens@bbc.co.uk">Peter.Stev=
ens@bbc.co.uk</a>&gt;; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</=
a><br>
Subject: Re: [MMUSIC] 4566bis open issues (from Flemming&#39;s review): SAP=
<br>
<br>
On 2/28/18 10:30 AM, Peter Stevens wrote:<br>
&gt; I&#39;ve just seen some of this discussion regarding whether SAP is st=
ill being used.<br>
&gt;<br>
&gt; I haven&#39;t investigated the details of how it is used within their =
devices, but SAP is used within Dante products, of which there are many fro=
m different manufacturers.<br>
&gt; It might be worth contacting one or more of them for comments.<br>
<br>
In any case, in this context it was only being used as an example. At the t=
ime it was first written it may well have been the only example.<br>
But today it is clearly not the the most common, or well known, use. So it =
is kind of a weird thing to include.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
<br>
&gt; Peter Stevens<br>
&gt;<br>
&gt; ______________________________<wbr>__________<br>
&gt; From: Paul Kyzivat [<a href=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@=
alum.mit.edu</a>]<br>
&gt; Sent: 28 February 2018 14:36<br>
&gt; To: <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; Subject: Re: [MMUSIC] 4566bis open issues (from Flemming&#39;s review)=
:<br>
&gt; SAP<br>
&gt;<br>
&gt; On 2/27/18 4:45 AM, Ali C. Begen wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Fri, Feb 23, 2018 at 2:54 AM, Colin Perkins &lt;<a href=3D"mail=
to:csp@csperkins.org">csp@csperkins.org</a><br>
&gt;&gt; &lt;mailto:<a href=3D"mailto:csp@csperkins.org">csp@csperkins.org<=
/a>&gt;&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt; On 20 Feb 2018, at 16:25, Paul Kyzivat &l=
t;<a href=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.mit.edu</a> &lt;ma=
ilto:<a href=3D"mailto:pkyzivat@alum.mit.edu">pkyzivat@alum.mit.edu</a>&gt;=
<wbr>&gt; wrote:<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt; On 2/20/18 10:25 AM, Ali C. Begen wrote:<=
br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt; 6) Section 7:<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 One transport that can b=
e used to distribute session descriptions is<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 the SAP.=C2=A0 SAP provi=
des both encryption and authentication mechanisms,<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 but due to the nature of=
 session announcements it is likely that<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 there are many occasions=
 where the originator of a session<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 announcement cannot be a=
uthenticated because the originator is<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 previously unknown to th=
e receiver of the announcement and because no<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 common public key infras=
tructure is available.<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;&gt; Comment: Does SAP provide integrity p=
rotection as well?<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt; It appears that this text is carried over=
 directly from rfc4566. But of course the expectations for security conside=
rations are much higher than they used to be. So perhaps this should be rew=
ritten.<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 &gt; Is SAP still used? Perhaps it would be be=
tter to simply remove it. If it is still used then can we get someone who k=
nows it to write something?<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 I&#39;m unconvinced SAP is still used, but in =
principle it provided<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 integrity protection via a PGP signature. This=
 almost certainly<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 doesn&#39;t meet current standards.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Proposed text:<br>
&gt;&gt;<br>
&gt;&gt; One transport that was used to distribute session descriptions is =
the<br>
&gt;&gt; SAP, which is currently not much used any more. SAP provided both<=
br>
&gt;&gt; encryption and authentication mechanisms, but due to the nature of=
<br>
&gt;&gt; session announcements it is likely that there were many occasions<=
br>
&gt;&gt; where the originator of a session announcement could not be<br>
&gt;&gt; authenticated because the originator was previously unknown to the=
<br>
&gt;&gt; receiver of the announcement and because no common public key<br>
&gt;&gt; infrastructure was available. In principle, SAP provided integrity=
<br>
&gt;&gt; protection via a PGP signature, however, this almost certainly doe=
s<br>
&gt;&gt; not meet the current standards.<br>
&gt;&gt;<br>
&gt;&gt; Let me know if this works for you.<br>
&gt;<br>
&gt; I don&#39;t find this helpful. Rather it just seems odd for security<b=
r>
&gt; considerations to be talking about a protocol that isn&#39;t used.<br>
&gt;<br>
&gt; I think we could just drop the paragraph in question without losing<br=
>
&gt; anything.<br>
&gt;<br>
&gt; Or, we could pick another protocol (e.g., SIP) as an example and<br>
&gt; discuss how security works there.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Thanks,<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Paul<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; -----------------------------<br>
&gt; <a href=3D"http://www.bbc.co.uk" rel=3D"noreferrer" target=3D"_blank">=
http://www.bbc.co.uk</a><br>
&gt; This e-mail (and any attachments) is confidential and may contain<br>
&gt; personal views which are not the views of the BBC unless specifically =
stated.<br>
&gt; If you have received it in<br>
&gt; error, please delete it from your system.<br>
&gt; Do not use, copy or disclose the<br>
&gt; information in any way nor act in reliance on it and notify the sender=
<br>
&gt; immediately.<br>
&gt; Please note that the BBC monitors e-mails sent or received.<br>
&gt; Further communication will signify your consent to this.<br>
&gt; -----------------------------<br>
&gt;<br>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">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/<wbr>listinfo/mmusic</a><br=
>
<br>
______________________________<wbr>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">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/<wbr>listinfo/mmusic</a><br=
>
</div></div></blockquote></div><br></div>

--001a11467db6c42bdd05664a393d--

