IETF Logo Mail Archive

Re: [clue] ICE, ICE-bis, and Cluster 238

"Roni Even (A)" <roni.even@huawei.com> Thu, 23 August 2018 05:45 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65451130D7A; Wed, 22 Aug 2018 22:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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 T5K9oGy5JV-f; Wed, 22 Aug 2018 22:45:26 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4980912F1A6; Wed, 22 Aug 2018 22:45:26 -0700 (PDT)
Received: from LHREML712-CAH.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id F02DF211E8DBD; Thu, 23 Aug 2018 06:45:19 +0100 (IST)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.399.0; Thu, 23 Aug 2018 06:45:20 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.48]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0399.000; Thu, 23 Aug 2018 13:45:14 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Adam Roach <adam@nostrum.com>
CC: "clue@ietf.org" <clue@ietf.org>, Applications and Real-Time Area Discussion <art@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [clue] ICE, ICE-bis, and Cluster 238
Thread-Index: AQHUOkHiKLXkliQTg0+3hQ2q8EkTBKTMyZyw//9/toCAAIff8A==
Date: Thu, 23 Aug 2018 05:45:14 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD8C357F@DGGEMM506-MBX.china.huawei.com>
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <6E58094ECC8D8344914996DAD28F1CCD8C3550@DGGEMM506-MBX.china.huawei.com> <e1a5af02-7a1e-106c-0da9-fa50c3f13554@nostrum.com>
In-Reply-To: <e1a5af02-7a1e-106c-0da9-fa50c3f13554@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.143]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD8C357FDGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/KPOlfOotphN6-JnzSxHFsPs3f8k>
Subject: Re: [clue] ICE, ICE-bis, and Cluster 238
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2018 05:45:29 -0000

Hi Adam,

Adding Christer here since he is the editor of the datachannel draft

The datachannel document went through IETF last call in July 2016 on the -13 version and -14 version is the update based on comments from the different reviews.
The document was parked since it was waiting for normative referenced documents that were in progress I think that the last one is draft-ietf-mmusic-data-channel-sdpneg that went to publication now (BTW I volunteered to be the editor of this document to help conclude the CLUE work)
So if it is really important to change the reference this can be for the RFC editor in my view

Roni Even


From: Adam Roach [mailto:adam@nostrum.com]
Sent: Thursday, August 23, 2018 8:27 AM
To: Roni Even (A)
Cc: clue@ietf.org; Applications and Real-Time Area Discussion
Subject: Re: [clue] ICE, ICE-bis, and Cluster 238

On 8/23/18 12:14 AM, Roni Even (A) wrote:


As for the CLUE documents I see no problem with changing the reference. As can be seen bellow the references are informative and in my personal view it does not matter if the documents will reference RFC5245 since RFC8445 obsolete RFC5245 anyhow.
How do you see the change to reference RFC8445 happening. Is it a note to the RFC editor?



For both CLUE documents, this plan involves asking the authors to make the update, along with any other IETF last-call comments they receive, prior to placing them on an IESG telechat.

/a

v2.23.0 | Report a Bug | By Email