Re: [stir] Minutes for session at IETF 98

Michael Hammer <michael.hammer@yaanatech.com> Thu, 06 April 2017 13:47 UTC

Return-Path: <michael.hammer@yaanatech.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED411294FC for <stir@ietfa.amsl.com>; Thu, 6 Apr 2017 06:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 BoXvL8QGb2ep for <stir@ietfa.amsl.com>; Thu, 6 Apr 2017 06:47:19 -0700 (PDT)
Received: from email1.corp.yaanatech.com (12-12-158-69-static.dzbja.com [12.12.158.69]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C69D1294F6 for <stir@ietf.org>; Thu, 6 Apr 2017 06:47:19 -0700 (PDT)
Received: from SC9-EX2K10MB1.corp.yaanatech.com ([fe80::149d:c2e1:8065:2a47]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.03.0123.003; Thu, 6 Apr 2017 06:47:19 -0700
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "housley@vigilsec.com" <housley@vigilsec.com>
CC: "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] Minutes for session at IETF 98
Thread-Index: AQHSriioiUl0d/YwuU6AQ5QrJtxBMKG3MGZYgAEq5RA=
Date: Thu, 6 Apr 2017 13:47:18 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3BD104F12@sc9-ex2k10mb1.corp.yaanatech.com>
References: <B61D0639-58D2-44F8-9445-FB37E2837B99@vigilsec.com> <00C069FD01E0324C9FFCADF539701DB3BD104BE1@sc9-ex2k10mb1.corp.yaanatech.com> <48958C16-E34E-4D0B-AA10-6B353749433B@vigilsec.com>
In-Reply-To: <48958C16-E34E-4D0B-AA10-6B353749433B@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/0QVl_Ix3u87DVlabqc4Ql7dw7yk>
Subject: Re: [stir] Minutes for session at IETF 98
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 13:47:21 -0000

Usually, when a decision is needed the notes say something about sending to the list.
So, I accept that was the original intent.

While changing to DTMF would remove my objection,
I am confused about the idea of having certs for what appears to be dial-strings.

Is that the real intent?

________________________________
Michael Hammer
michael.hammer@yaanatech.com
+1 408 202 9291

© 2016 Yaana Technologies, LLC. All Rights Reserved. Email confidentiality notice. This message is private and confidential. If you have received this message in error, please notify us and remove it from your system.

-----Original Message-----
From: Russ Housley [mailto:housley@vigilsec.com]
Sent: Wednesday, April 05, 2017 3:54 PM
To: Michael Hammer <michael.hammer@yaanatech.com>
Cc: IETF STIR Mail List <stir@ietf.org>
Subject: Re: [stir] Minutes for session at IETF 98


> On Apr 5, 2017, at 1:24 PM, Michael Hammer <michael.hammer@yaanatech.com> wrote:
>
> It used to be that decisions were made on the IETF mail lists.
> Has that changed?

The minute report what happened in the room.  The point of getting the minutes posted promptly is so that people on the mail list can offer an opposing opinion if they have one.

> I want to register my objection to the following:
> - Calling character strings that include # or * an E.164 number.
>
> Suggested fix:
> - Add "Pseudo" to the name of the element to distinguish it from ITU-T
> E.164 standard definition,
> - Define where in the string a # or * may appear (syntax),
> - Define the meaning of a # or * embedded in the character string (semantics).

Perhaps the string that includes # and * should be a DTMFNumber.

Russ