[stir] FW: I-D Action: draft-ietf-stir-certificates-13.txt

Michael Hammer <michael.hammer@yaanatech.com> Wed, 29 March 2017 20:24 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 18BC0129493 for <stir@ietfa.amsl.com>; Wed, 29 Mar 2017 13:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 HNFmB4XE4yc4 for <stir@ietfa.amsl.com>; Wed, 29 Mar 2017 13:24:11 -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 600E112994E for <stir@ietf.org>; Wed, 29 Mar 2017 13:24:10 -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; Wed, 29 Mar 2017 13:24:09 -0700
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] I-D Action: draft-ietf-stir-certificates-13.txt
Thread-Index: AQHSqLCzusvW1CSOy06Xl4YfBdWmnaGsmyyA//+h9ZCAAAYH0A==
Date: Wed, 29 Mar 2017 20:24:08 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3BD1032C4@sc9-ex2k10mb1.corp.yaanatech.com>
References: <149065198337.30490.6512482120705975775@ietfa.amsl.com> <635a9167-e6d7-03e5-bc3c-f514d6502bdf@yaanatech.com> <DF9CA449-6415-4C62-97E8-77F9BE8E38B8@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.41]
Content-Type: multipart/alternative; boundary="_000_00C069FD01E0324C9FFCADF539701DB3BD1032C4sc9ex2k10mb1cor_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/rpg6mZGKZqxSOzKmjB1iQPQFsF4>
Subject: [stir] FW: I-D Action: draft-ietf-stir-certificates-13.txt
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: Wed, 29 Mar 2017 20:24:14 -0000

Third try.



Outlook and signed messages doesn't work.



________________________________

Michael Hammer

michael.hammer@yaanatech.com<mailto:michael.hammer@yaanatech.com>

+1 408 202 9291


(c) 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.



From: Michael Hammer
Sent: Wednesday, March 29, 2017 4:21 PM
To: 'housley@vigilsec.com' <housley@vigilsec.com>om>; Tony Rutkowski <tony@yaanatech.com>
Cc: 'stir@ietf.org' <stir@ietf.org>
Subject: RE: [stir] I-D Action: draft-ietf-stir-certificates-13.txt



Russ,



Sorry, not good enough.



First, it is incredibly bad form to redefine a well-known defined parameter from another SDO at a whim.  That just leads to confusion in the industry.  If you want to define something else, call it something else.



Second, to include extra characters with no definition of how they are to be used will lead to interoperability problems.

That is plain bad.

What do I do if I receive a string:  1#201*555*12324 ?



Lastly, this is a draft, so discussion is not over.

If something is broken, would be good idea to fix it.



________________________________

Michael Hammer

michael.hammer@yaanatech.com<mailto:michael.hammer@yaanatech.com>

+1 408 202 9291


(c) 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.



From: stir [mailto:stir-bounces@ietf.org] On Behalf Of Russ Housley
Sent: Wednesday, March 29, 2017 2:38 PM
To: Tony Rutkowski <tony@yaanatech.com<mailto:tony@yaanatech.com>>
Cc: IETF STIR Mail List <stir@ietf.org<mailto:stir@ietf.org>>
Subject: Re: [stir] I-D Action: draft-ietf-stir-certificates-13.txt



Tony:



   TNAuthorizationList ::= SEQUENCE SIZE (1..MAX) OF TNEntry

   TNEntry ::= CHOICE {
               spc [0] ServiceProviderCodeList,
               range [1] TelephoneNumberRange,
               one E164Number
               }

   MH>>> Is this a choice of 2 or 3 items?
                Seems you can't enumerate item number [2]:  one E164Number.



   There are 3 items in the CHOICE (spc, range, and one)  The first two are SEQUENCE, so an explicit tag is needed to aid the decoder. The third item is an IA5String.



   ServiceProviderCodeList ::= SEQUENCE SIZE (1..3) OF IA5String

   TelephoneNumberRange ::= SEQUENCE {
               start E164Number,
               count INTEGER
               }

   MH>>> What is the difference between:
               Range = TelephoneNumber Range, where
                           Start is an E164Number, and
                           Count = 1
        and
               One = E164Number?
        Two alternate codes means more complex coding.



   The IA5String shows the stat of a block of phone numbers, and the count says the number of consecutive telephone numbers. It would be better to require count to be greater than 1.



   I suggest:



      count INTEGER (2..MAX)



   E164Number ::= IA5String (SIZE (1..15)) (FROM ("0123456789#*"))

   MH>>>           E164 numbers can be composed only of "0123456789", no?
               So, the use of # and * are currently undefined in this ID.
               I would assume that:
                           # would be an ending digit indicating the end of a shorter than 15 digit
   number.
                           * would be an ending digit wild-card meaning any phone numbers with
   preceding leading digits.
               However, that would render the meaning of "One" ambiguous, and
                           That would provide another way to do Range, which may complicate code.
               Also, what would it mean if the # or * appeared at the beginning or middle of
   a digit string?



   The WG already had a discussion on the list about whether to include # and *.  I believe this represents the outcome of that discussion.



   Russ