[sacm] AD Review of draft-ietf-sacm-vuln-scenario

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 09 December 2016 19:08 UTC

Return-Path: <kathleen.moriarty.ietf@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 67C6A127A90 for <sacm@ietfa.amsl.com>; Fri, 9 Dec 2016 11:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, 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 JU3e5nMLFNdi for <sacm@ietfa.amsl.com>; Fri, 9 Dec 2016 11:08:04 -0800 (PST)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (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 CE33D126BF7 for <sacm@ietf.org>; Fri, 9 Dec 2016 11:08:03 -0800 (PST)
Received: by mail-ua0-x229.google.com with SMTP id 20so26607314uak.0 for <sacm@ietf.org>; Fri, 09 Dec 2016 11:08:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=TZ/A+ALFo8GHSqLSUgtaVO2wcDqyh8Kb0s1zSND1Rqk=; b=YKGiJUHCVimyH3oO2xNRanywdjoy8wA1mtiSPDwuN/oAYQVl9h4leTcq31sYcS5NgO k1pQL9MeKMaiG5sS432E0FG0KFUU79vdR6dR9rZLsuZRg++rDd1Y22/hjJ8DAfIUinga tdtkKZl7cGfVsjJRULOeixpncUUZP8bnPP8YvWWGcCeDvjWMb52cPSSkuxBSOZjYEx/A FNsHhKedNB1q2yNY46jpdaORRdkx/bGY++rluYsYGgqEf/dz40XijfwUvGcoco2fs968 0GUBXa/iLqeGOImWwWLCKW4MqcWP8kTFjMkSLno0i6cH0qFnIZh6ljAO1y3cybF4zk6+ I5yA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TZ/A+ALFo8GHSqLSUgtaVO2wcDqyh8Kb0s1zSND1Rqk=; b=TDQkkMbeNiDaswpfpwnOw+ktbNzphkRndPJ9BEP1h/zFiG/Yj9jm/n0AshRdSdXPhZ inLSe4VsCGY/piWKq3ux5TXtmz/0QHrbCBBKphdqCf1gTRI2dkWExsUBg7c8jJeixKtn t0KsYso+Muhhv1WowVkBTZX3WfIrp6GvyepvJJzXcchYiG8xiHEm8rHW6gbXZI/A5plz HjxquxEDKqAN3i6PFRslLJK7UxYIA5hQaOa56s2VYl8ZH/QSY44u5IJD0LJ4BnZGBAHm 21d2mYwaNc4z/suz+WotgikhtS403HLrF/2MRuAshkytjMisTqQ0i8sSjAjh8hekYU7q 8POw==
X-Gm-Message-State: AKaTC01/GUiMDcfXY/SswGB8LC04crx9zXhHd+6JbljPIoahMRBF3grsLq0oWjymHL2Qmtp4oOysmhtp4LP1FQ==
X-Received: by 10.176.85.24 with SMTP id t24mr66238585uaa.21.1481310482899; Fri, 09 Dec 2016 11:08:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.82.232 with HTTP; Fri, 9 Dec 2016 11:08:02 -0800 (PST)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Fri, 09 Dec 2016 14:08:02 -0500
Message-ID: <CAHbuEH4CY6-DJsPSzF4HS=3dTy0bfdu9WG6uQB6N4=5vBuLbEw@mail.gmail.com>
To: "sacm@ietf.org" <sacm@ietf.org>
Content-Type: multipart/alternative; boundary="f403045dd96022c81605433e79cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/qel4UHHVPMplLwAuRJ_U0IohNbk>
Subject: [sacm] AD Review of draft-ietf-sacm-vuln-scenario
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, 09 Dec 2016 19:08:05 -0000

Hello,

I just reviewed draft-ietf-sacm-vuln-scenario and think it is better suited
as a link off of the SACM wiki in the datatracker and can live on as an
expired draft.  I don't see the value in continuing the publication process
since a use case document has already been published.  If the WG really
wants this published, I'll proceed, but would like to be convinced in how
that will be useful.

Thank you.

-- 

Best regards,
Kathleen