Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Keep in mind that we may need to change the "SACM" prefix (#85)
Henk Birkholz <notifications@github.com> Fri, 08 June 2018 12:49 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 805C6130E9F for <sacm@ietfa.amsl.com>; Fri, 8 Jun 2018 05:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.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, RCVD_IN_DNSWL_HI=-5, 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 sWec6uCnuKPZ for <sacm@ietfa.amsl.com>; Fri, 8 Jun 2018 05:49:08 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A62FA130E94 for <sacm@ietf.org>; Fri, 8 Jun 2018 05:49:08 -0700 (PDT)
Date: Fri, 08 Jun 2018 05:49:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1528462147; bh=LJXFbZo5AFEThiJa9p7vtVXSN3Q0SqZkY6gQzUJBsRM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=Szy0B5pzytTsoTef7Nb45OdhierEAF4wo+1V1leYlElVkpO/l8IU9EPdyj40Y9ig+ L39SQ6enGLugSFhMP1Iad+k9fd74SXsGxShU2RKWp29jtEiM271Guj+AXyAQx9tfWq 1n812xGNpsufe7/ZxkaZZXlhf9y8Iu2Hkjm+Yl0I=
From: Henk Birkholz <notifications@github.com>
Reply-To: sacmwg/draft-ietf-sacm-terminology <reply+00a6c4d1b3232810e1a1cc1d6579df142dc33eefd15a173192cf0000000117323d4392a169ce11581e19@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/85/395750675@github.com>
In-Reply-To: <sacmwg/draft-ietf-sacm-terminology/issues/85@github.com>
References: <sacmwg/draft-ietf-sacm-terminology/issues/85@github.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b1a7b438b82_4e162afb1914ef581031a3"; 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/EkM5zk7DMYz0x7JZ3Ij2HzCxDo4>
Subject: Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] Keep in mind that we may need to change the "SACM" prefix (#85)
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:49:11 -0000
Yes. I would urge to put this topic on the agenda for the next meeting, please. -- 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/85#issuecomment-395750675
- Re: [sacm] [sacmwg/draft-ietf-sacm-terminology] K… Henk Birkholz
- [sacm] [sacmwg/draft-ietf-sacm-terminology] Keep … adammontville