Re: [sacm] SACM - consensus on defining SACM terminology in a separate document

David Harrington <ietfdbh@comcast.net> Tue, 06 August 2013 21:24 UTC

Return-Path: <ietfdbh@comcast.net>
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 D251E21F9DFB for <sacm@ietfa.amsl.com>; Tue, 6 Aug 2013 14:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level:
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZS-35p57yHRN for <sacm@ietfa.amsl.com>; Tue, 6 Aug 2013 14:24:07 -0700 (PDT)
Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:211]) by ietfa.amsl.com (Postfix) with ESMTP id DF5EB21F9EB0 for <sacm@ietf.org>; Tue, 6 Aug 2013 14:24:01 -0700 (PDT)
Received: from omta19.emeryville.ca.mail.comcast.net ([76.96.30.76]) by qmta11.emeryville.ca.mail.comcast.net with comcast id 9RLp1m00A1eYJf8ABZQ1Fi; Tue, 06 Aug 2013 21:24:01 +0000
Received: from [192.168.1.181] ([176.96.153.9]) by omta19.emeryville.ca.mail.comcast.net with comcast id 9ZPj1m00N0CRbBk01ZPndn; Tue, 06 Aug 2013 21:23:59 +0000
User-Agent: Microsoft-MacOutlook/14.3.6.130613
Date: Tue, 06 Aug 2013 23:23:42 +0200
From: David Harrington <ietfdbh@comcast.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, "sacm@ietf.org" <sacm@ietf.org>
Message-ID: <CE2735F9.2F64D%ietfdbh@comcast.net>
Thread-Topic: [sacm] SACM - consensus on defining SACM terminology in a separate document
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA128A4DFA@AZ-FFEXMB04.global.avaya.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1375824241; bh=wPaTL6GrFHFF6JzzZ7pb68QPvdzFafY5tCtORYGRcuM=; h=Received:Received:Date:Subject:From:To:Message-ID:Mime-version: Content-type; b=ocStl+WBVTAMAqX9T1u6kOG97tm1gbJ7tCFa6pyR034GHmTDlo+1oXFj47Tft+kFg OkxgEsj5JkEoYOtOEC495+FnMyuV84VUMF9C8cw1ag8f9AYFyTJ6/sD8by/womwXTx G09lGHBD/GL8qv7VgdRpkzNJphJuVtc8bf4dRjpeAkQxn8mswaHZrAQ34Z1ilNZDog 3pVqiwGyFgjqOaXuF4GmfZhkAwIhRpo8rz4ukZydTrqXr+Z76zSgn2rLl6ofv86qmx iR1QnJDOPUIO5XpBXmQMPmvjsE3NHkGIkEFMEiJRdy39Z1vOpAQkqzE03CcmWTx3QH zf34FoNO/eWjg==
Subject: Re: [sacm] SACM - consensus on defining SACM terminology in a separate document
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 06 Aug 2013 21:24:16 -0000

+1
--
David Harrington
Ietfdbh@comcast.net
+1-603-828-1401





On 8/6/13 2:57 PM, "Romascanu, Dan (Dan)" <dromasca@avaya.com> wrote:

>At the SACM WG meeting at IETF-87 the participants in the room did not
>raise any objection to the proposal to separate the terminology section
>from draft-waltermire-sacm-use-cases and make of it a separate document
>that defines the SACM terms in one place and can be referred by all other
>SACM documents. We are asking the WG to confirm this consensus on the
>mail list. Please send all comments, questions and concerns to the SACM
>WG mail list before 8/15.
>
>Thanks and Regards,
>
>Adam and Dan
>
>
>
>
>_______________________________________________
>sacm mailing list
>sacm@ietf.org
>https://www.ietf.org/mailman/listinfo/sacm