IETF Logo Mail Archive

Re: [Arcing] arcing - New Meeting Session Request for IETF 95

Edward Lewis <edward.lewis@icann.org> Thu, 03 March 2016 17:06 UTC

Return-Path: <edward.lewis@icann.org>
X-Original-To: arcing@ietfa.amsl.com
Delivered-To: arcing@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDFCD1A88DC; Thu, 3 Mar 2016 09:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level:
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] autolearn=ham
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 6lDJsF3kyJ_f; Thu, 3 Mar 2016 09:06:36 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC6401B29B8; Thu, 3 Mar 2016 09:04:34 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Thu, 3 Mar 2016 09:04:32 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Thu, 3 Mar 2016 09:04:32 -0800
From: Edward Lewis <edward.lewis@icann.org>
To: "arcing-chairs@ietf.org" <arcing-chairs@ietf.org>
Thread-Topic: [Arcing] arcing - New Meeting Session Request for IETF 95
Thread-Index: AQHRcNG/gerIqTBN0kC0zakX9nQarJ9ILiOA
Date: Thu, 03 Mar 2016 17:04:32 +0000
Message-ID: <D2FDD769.1422C%edward.lewis@icann.org>
References: <20160226194955.23064.53842.idtracker@ietfa.amsl.com>
In-Reply-To: <20160226194955.23064.53842.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.1.160122
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3539851467_18937105"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/arcing/5RiCpXLIzzA1iWpfUkWSPw3qpM0>
Cc: "arcing@ietf.org" <arcing@ietf.org>
Subject: Re: [Arcing] arcing - New Meeting Session Request for IETF 95
X-BeenThere: arcing@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: This list will discuss different architectural approaches to signalling alternative resolution contexts for Internet names <arcing.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/arcing>, <mailto:arcing-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/arcing/>
List-Post: <mailto:arcing@ietf.org>
List-Help: <mailto:arcing-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/arcing>, <mailto:arcing-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2016 17:06:37 -0000

Is ARCING a formal working group?  I don't see it listed on
https://datatracker.ietf.org/wg/.

On 2/26/16, 11:49, "Arcing on behalf of "IETF Meeting Session Request
Tool"" <arcing-bounces@ietf.org on behalf of
session_request_developers@ietf.org> wrote:

>---------------------------------------------------------
>Working Group Name: Alternative Resolution Contexts for Internet Naming

Perhaps the same tool is used for WGs and BoFs, hence the use of "Working
Group" here.  On the other hand, maybe ARCING has been made a WG.  Can't
tell.

This says it isn't chartered (found this using a web search engine, not
from the IETF web site), state is BoF:

https://datatracker.ietf.org/wg/arcing/charter/


If this is a BoF, what's the plan for an agenda?  I ask because I have a
draft already but I also feel the need to document why this is a problem
based on hallway conversations and observations about the state of play.

v2.23.0 | Report a Bug | By Email