Re: [sacm] Updated IETF 95 Agenda Posted

Adam Montville <adam.w.montville@gmail.com> Fri, 01 April 2016 18:27 UTC

Return-Path: <adam.w.montville@gmail.com>
X-Original-To: sacm@ietfa.amsl.com
Delivered-To: sacm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48BB812D65F for <sacm@ietfa.amsl.com>; Fri, 1 Apr 2016 11:27:31 -0700 (PDT)
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 1aw6j2DQQKWK for <sacm@ietfa.amsl.com>; Fri, 1 Apr 2016 11:27:29 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::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 2F11D12D161 for <sacm@ietf.org>; Fri, 1 Apr 2016 11:27:29 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id o62so116923030oig.1 for <sacm@ietf.org>; Fri, 01 Apr 2016 11:27:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to; bh=W/v4I4g8H6WZ8WH6DVlYiNpBeHxLpXLdbV8wXbykY3I=; b=TwvTvkAPO4u0Nv0aT9cHMb2f5wcgh7lrjynmyyeeQOcBFixzItYvrLW2QEQloZHI2k 9m4LMeIQaesZXYcqCw8jaFG3WhTT6/Db8bF33S+K5UNvyQUOjDRRvxWVpwZ4zhAKeJGL 5No9FBRsihP3aXkmlTWqond6M7AR0kZ6DstovYkAvKltcBC4SvTnVT/Ae47JkPLt9SSW vMmwDOKikGdNjVy8qzo0qg5cOLAHRklD1vdGpwhF9C2X6QlE6JHjdSgbT+Jmt6X+hVZj 0ffnIwA19PG7lgjxCVx3QFuH99GPUS16L1wO8Vmz048bWBtTNYXOsaz1FjEBGwc+IKwc 94pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=W/v4I4g8H6WZ8WH6DVlYiNpBeHxLpXLdbV8wXbykY3I=; b=D6kXu/IbpyZhAuXmPBKGNzLqmeeXc9fc3SJE/CQJDDmqTrZ+wIuItLJMGe28/LpLbl DHZjMYbeEsUaOIoHsxQaz5mESvWLH7JZdwDEdCa/nyQeYXUhM42UAHtkypAleGFDPVaA iZsdRF1RZPnTtwZKg/uZBDygWzTN7VQQ7D/yrrcw6HPJgHUd6+dulw2bX2q3mLQz/VdG 7aT+9pYPgibu3EUE9O20EmTUeFsPjH/cEL477b7WgD5YFUEcUJe6TnnO+hcXkts4+1i4 XX/mOamiPKd9tQynDwM9hPzIaay9fAjc03R0GxslXdwRWL/EFC8g0KqMkjdxaoC3jxuA EjKQ==
X-Gm-Message-State: AD7BkJIEr72E/Die3rafL26oWz5PFLnMVoKh6pPJBj4ircsa8jI5Z+IkOOEEW6XQvSl6wQ==
X-Received: by 10.157.11.130 with SMTP id 2mr4231864oth.41.1459535248587; Fri, 01 Apr 2016 11:27:28 -0700 (PDT)
Received: from adams-mbp.attlocal.net (99-64-100-131.lightspeed.austtx.sbcglobal.net. [99.64.100.131]) by smtp.gmail.com with ESMTPSA id jl6sm4480960oeb.12.2016.04.01.11.27.27 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 01 Apr 2016 11:27:27 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_71697AF9-E954-44C5-B64D-2C16AC7A8BA2"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.6b2
From: Adam Montville <adam.w.montville@gmail.com>
In-Reply-To: <SN2PR0601MB099226A18B2F660403AB4DC8A89A0@SN2PR0601MB0992.namprd06.prod.outlook.com>
Date: Fri, 01 Apr 2016 13:27:08 -0500
Message-Id: <E6535DCE-089D-4EEA-BA8F-AA1F1D5C42A5@gmail.com>
References: <04C2FAE9-476B-489F-81CB-48BCAAFA29D6@gmail.com> <SN2PR0601MB099226A18B2F660403AB4DC8A89A0@SN2PR0601MB0992.namprd06.prod.outlook.com>
To: Lisa Lorenzin <llorenzin@pulsesecure.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/sacm/i-1V3-GnWYm6zTnNO312-ropFt4>
Cc: "<sacm@ietf.org>" <sacm@ietf.org>
Subject: Re: [sacm] Updated IETF 95 Agenda Posted
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SACM WG mail list <sacm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sacm>, <mailto:sacm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sacm/>
List-Post: <mailto:sacm@ietf.org>
List-Help: <mailto:sacm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sacm>, <mailto:sacm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2016 18:27:31 -0000

I have no issue dropping that slot entirely and using that time for ECP.

If no one objects over the next day or so, I’ll gladly update the agenda.  My understanding is that as long as no issues were raised during WGLC we can progress the draft.

Thanks for offering up opinions—agenda as originally posted was just a proposed starting place.

Adam

> On Apr 1, 2016, at 11:04 AM, Lisa Lorenzin <llorenzin@pulsesecure.net> wrote:
> 
> Hi Adam et al.,
> 
> Now that the WGLC last call for the requirements draft has completed with no new issues raised, I have a follow-up request:
> 
> Like Jim, I can only attend on Wednesday; I'd like to be able to participate in the ECP conversation   Can we move it to Wednesday by either dropping the requirements draft entirely, or moving the requirements draft to Friday?
> 
> Regarding the requirements draft - I don't think we need 20 minutes for it in BA:
>  * All four remaining open issues from github were addressed in the latest version, based on the agreements reached either in the issue thread or at the last virtual interim.
>  * The updates to address those issues were all brief - two of them add one sentence each; two of them change one word each.
>  * No new issues were raised in the WGLC.
> 
> So I believe we could drop the requirements draft entirely from the F2F agenda and move directly to a call for consensus to progress the draft, based on the lack of objections in the WGLC.
> 
> If it's mandatory to review the changes at an F2F before doing so, I believe that will only take about 5 minutes.  Either way, I think the remaining 15 or 20 minutes on Friday would be much better spent on the terminology draft!
> 
> Regards,
> Lisa
> 
> 
> -----Original Message-----
> From: sacm [mailto:sacm-bounces@ietf.org] On Behalf Of Adam Montville
> Sent: Tuesday, March 29, 2016 8:03 PM
> To: <sacm@ietf.org> <sacm@ietf.org>
> Subject: [sacm] Updated IETF 95 Agenda Posted
> 
> I’ve updated the agenda based on Jim’s request to move the information model forward (I swapped it with SWID).
> 
> If you are on the agenda as a presenter, please get your slides to the chairs at least the day before our Wednesday session.  Also, please let us know if you need to present remotely so we can loop in the MeetEcho folks as necessary.
> 
> Finally, and as always, we’re going to need a couple of people in the room to take notes and a jabber scribe.  Any early takers?
> 
> Kind regards,
> 
> Adam