IETF Logo Mail Archive

Re: [straw] RTCP document: Proposed Standard or Best Current Practice?

Christer Holmberg <christer.holmberg@ericsson.com> Fri, 10 June 2016 10:50 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: straw@ietfa.amsl.com
Delivered-To: straw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA5B412D1E4 for <straw@ietfa.amsl.com>; Fri, 10 Jun 2016 03:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 LQnSsHWM4Wys for <straw@ietfa.amsl.com>; Fri, 10 Jun 2016 03:50:45 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DDEA12D1C2 for <straw@ietf.org>; Fri, 10 Jun 2016 03:50:45 -0700 (PDT)
X-AuditID: c1b4fb30-f79486d0000069d0-b8-575a9b82d359
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.183.45]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 69.51.27088.28B9A575; Fri, 10 Jun 2016 12:50:42 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.154]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.03.0294.000; Fri, 10 Jun 2016 12:50:42 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Lorenzo Miniero <lorenzo@meetecho.com>, "straw@ietf.org" <straw@ietf.org>
Thread-Topic: [straw] RTCP document: Proposed Standard or Best Current Practice?
Thread-Index: AQHRwwVgA8PWBuH6+Uy0vUXIY9jwzp/il4IA
Date: Fri, 10 Jun 2016 10:50:41 +0000
Message-ID: <D380768D.A8C5%christer.holmberg@ericsson.com>
References: <20160610124634.028fd73e@lminiero>
In-Reply-To: <20160610124634.028fd73e@lminiero>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.4.160422
x-originating-ip: [153.88.183.19]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5DDEF16A581D944EB6B1B40EFE8DCE65@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyM2K7rm7T7Khwg+fXNSy2b1nAZHGr+TGr A5PHkiU/mTw6Ht5nD2CK4rJJSc3JLEst0rdL4MrY3uVVsFmg4k/zLdYGxt28XYycHBICJhJn Ts1kg7DFJC7cWw9mCwkcYZSYvTS8i5ELyF7CKPHx5n+WLkYODjYBC4nuf9ogNSICvhJf3h5l AbGFBQIl3hzoZoSIB0ksWfOPGcI2kti+cRdYDYuAqsT+aR1MIGN4BawkGp/pQKzSk7jbchOs lVNAX+Jfw2QwmxHonO+n1jCB2MwC4hK3nsxngjhTQGLJnvPMELaoxMvH/1hBbFGgOV/uzWOE iCtKtD9tYITo1ZO4MXUKG4RtLbH3zGRWCFtbYtnC12BzeAUEJU7OfMIygVF8FpJ1s5C0z0LS PgtJ+ywk7QsYWVcxihanFiflphsZ6aUWZSYXF+fn6eWllmxiBEbawS2/DXYwvnzueIhRgINR iYf3wbPIcCHWxLLiytxDjBIczEoivH3To8KFeFMSK6tSi/Lji0pzUosPMUpzsCiJ8/q/VAwX EkhPLEnNTk0tSC2CyTJxcEo1MO7w2asxP+9xZ5t93P+XAjlMPb2/up984Dz2L9+w++jG1sXm M2dLnpw5M0837eaizuybzOw3cl64uG2XE3iwISomJyjsldm+rM0uljs/i1f1v0yqN32xTzCY veHX3EzO1JMzNrYf/6sZF8HyvKDoZr/i0n8m0yYtar5x9sKpV8qa3Q5OHafudSixFGckGmox FxUnAgCTjG08sAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/straw/IStMjbbYgJqS6uzpWSXk9mtkxKw>
Subject: Re: [straw] RTCP document: Proposed Standard or Best Current Practice?
X-BeenThere: straw@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Sip Traversal Required for Applications to Work \(STRAW\) working group discussion list" <straw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/straw>, <mailto:straw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/straw/>
List-Post: <mailto:straw@ietf.org>
List-Help: <mailto:straw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/straw>, <mailto:straw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2016 10:50:48 -0000

(As co-chair)

Hi,

Just to point out that, apart from the taxonomy document, all STRAW
deliverables so far haven been ³Standards Track².

Regards,

Christer


On 10/06/16 13:46, "straw on behalf of Lorenzo Miniero"
<straw-bounces@ietf.org on behalf of lorenzo@meetecho.com> wrote:

>Hi all,
>
>I just published a new version of the RTCP document, that hopefully
>now addresses all the very useful comments Ben provided in his
>latest detailed review:
>
>https://tools.ietf.org/html/draft-ietf-straw-b2bua-rtcp-12
>
>One last notable point remains to be clarified, that is related to the
>intended scope of the document. The draft is currently "Standards
>Track", something Ben is not sure about, considering this might mean
>expecting B2BUA developers to implement this. Besides, the document is
>more trying to discipline the behaviour of components that, for one
>reason or another, are not always adhering to specifications that
>should already prevent the broken behaviours the draft tries to
>address. In order to make sure the WG would be aware of this discussion
>and not have it buried under the other discussions we had around the
>document itself, Ben suggested to open a new post to discuss
>specifically about this and get the WG's feeling on the matter.
>
>As I said a few posts ago, I'd rather keep the document "Proposed
>Standard" than changing it to a "Best Current Practice", mainly because
>we want it to have an actual impact and stress the importance of doing
>things right in that context. Besides, the DTLS-SRTP document was
>published as "Standards Track" too, and I believe the aim of the two
>documents was similar. Anyway, I obviously wouldn't fight changing it to
>"Best Current Practice", as we are talking about guidelines on the
>behaviour to follow.
>
>What is your opinion on this? Any reason to change the scope of the
>document, or any reason not to?
>
>Thanks!
>Lorenzo
>
>_______________________________________________
>straw mailing list
>straw@ietf.org
>https://www.ietf.org/mailman/listinfo/straw

v2.23.0 | Report a Bug | By Email