IETF Logo Mail Archive

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

Adam Roach <adam@nostrum.com> Thu, 23 August 2018 05:27 UTC

Return-Path: <adam@nostrum.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 4D442129619; Wed, 22 Aug 2018 22:27:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 1JqBkr3hJoko; Wed, 22 Aug 2018 22:27:50 -0700 (PDT)
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 711CE124C04; Wed, 22 Aug 2018 22:27:50 -0700 (PDT)
Received: from Svantevit.roach.at (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w7N5RUqE090037 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 23 Aug 2018 00:27:40 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Svantevit.roach.at
To: "Roni Even (A)" <roni.even@huawei.com>
Cc: "clue@ietf.org" <clue@ietf.org>, Applications and Real-Time Area Discussion <art@ietf.org>
References: <15d3b114-5c04-61c4-8a62-61d8a414143d@nostrum.com> <6E58094ECC8D8344914996DAD28F1CCD8C3550@DGGEMM506-MBX.china.huawei.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <e1a5af02-7a1e-106c-0da9-fa50c3f13554@nostrum.com>
Date: Thu, 23 Aug 2018 00:27:25 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD8C3550@DGGEMM506-MBX.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------846DC007A6FF4C78B938C64B"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/afX5gexfC9YdQcG7oReRKVJNW0c>
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:27:52 -0000

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