IETF Logo Mail Archive

Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "attribute" to "SACM attribute"? (#62)

Henk Birkholz <notifications@github.com> Fri, 08 June 2018 12:55 UTC

Return-Path: <noreply@github.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 56725130EA5 for <sacm@ietfa.amsl.com>; Fri, 8 Jun 2018 05:55:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 yrSAe7DPKW4m for <sacm@ietfa.amsl.com>; Fri, 8 Jun 2018 05:55:53 -0700 (PDT)
Received: from out-12.smtp.github.com (out-12.smtp.github.com [192.30.254.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E827B124C04 for <sacm@ietf.org>; Fri, 8 Jun 2018 05:55:52 -0700 (PDT)
Date: Fri, 08 Jun 2018 05:55:52 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528462552; bh=eQt85NAaH30qT+lxnYpLZW4C9v/x7tyJFVF0bY7z2bk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u1lGu7Cmi585fYagxqNX6YOZ0hqSrS91tQCDB5rs7Qb+Fi1lkR1p6P5+QMQEuDlpf fZfZt6EkP4Sr1OW0mFBeAXTBQyD78GbCrVly6it+fWILuSDjUrDFpSAlT0ZN0ayH0j 11F7/yFKTabtFqV0rM0wrTyuaDyJqcsFsnITFZhw=
From: Henk Birkholz <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-terminology <reply+00a6c4d11a04af061ddddc468be9061e01c36f8be4a0b32692cf0000000117323ed892a169ce10bce885@reply.github.com>
To: sacmwg/draft-ietf-sacm-terminology <draft-ietf-sacm-terminology@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <sacmwg/draft-ietf-sacm-terminology/issues/62/395752294@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-terminology/issues/62@github.com>
References: <sacmwg/draft-ietf-sacm-terminology/issues/62@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a7cd869ca1_414f2ad09f764f542116f3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: henkbirkholz
X-GitHub-Recipient: sacm
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: sacm@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/sacm/aESinejY0G_t2mbvPuNFz9LuglM>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Should we change "attribute" to "SACM attribute"? (#62)
X-BeenThere: sacm@ietf.org
X-Mailman-Version: 2.1.26
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, 08 Jun 2018 12:55:55 -0000

This issue depends on resolving issue https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/85 first.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/sacmwg/draft-ietf-sacm-terminology/issues/62#issuecomment-395752294

v2.23.0 | Report a Bug | By Email