Re: [stir] Eric Rescorla's Discuss on draft-ietf-stir-certificates-16: (with DISCUSS)
Eric Rescorla <ekr@rtfm.com> Wed, 13 December 2017 17:06 UTC
Return-Path: <ekr@rtfm.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 90A7F12895E for <stir@ietfa.amsl.com>; Wed, 13 Dec 2017 09:06:43 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 CxFk9r4AAE_q for <stir@ietfa.amsl.com>; Wed, 13 Dec 2017 09:06:16 -0800 (PST)
Received: from mail-yb0-x22b.google.com (mail-yb0-x22b.google.com [IPv6:2607:f8b0:4002:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CC84128D2E for <stir@ietf.org>; Wed, 13 Dec 2017 09:06:12 -0800 (PST)
Received: by mail-yb0-x22b.google.com with SMTP id t127so1301416ybf.9 for <stir@ietf.org>; Wed, 13 Dec 2017 09:06:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0mc/L98NkCEdS2gIyq3eBJJePs80Jl2s9fp9q1CQEDM=; b=fDFVdlH/IhTOkhTRJhigI5EZdDYGbwatSCqCWl+ummBCP9bYvOdzzbj5zQrMcm37PC w9jp1A2/llI/h6Q/cSMAqcFglThkS+tdnvAsHJYvF1CmVsqzpcF3cJe1i8gWZUDR6I95 3kRNm8FuMbK4+zyv1VxTrbeOubrGPWSIEi7sdCWqV0CrUn1bWetngAHDnYOR2iRV2WwA mimXtD7VrKm53Yh0jr8l9qXGI2EqZP/zEGKZ+BwaMvglBgPdra87t+aVTPLEEo997cPe a9kYicGlaOGvydiea4F7GlzgpxmK3VGl17WnbdTZNgLzob0SnsSYcsT5uoQQfcV8JZHP NeZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0mc/L98NkCEdS2gIyq3eBJJePs80Jl2s9fp9q1CQEDM=; b=MYWcnnadTCRP2bZbB/hsBDAicXUDzbUSIYSNUW2gNEzzbAJixsOFicXrCyIrfDrKH/ HSudDahZV0YjG1CxDA3x5CXrH/ssdOUwUKCJCygVDRUuUCesnPo6Gnm3Y9lVTn27ssc4 7qK90hulKKgC11NhC1aqAfUrkw1Q8Kq8acuh2COpFY2R5YrYl0C1hpi7/umETQ1jC++9 Yk4UpDXTP/5NVkbXHG5BmGeO5s65ydE7GatcpqmY3t6PZEcnfIwLt/reus+KiolGY9Rt A51ddx0oFwU2Muv9qdoMQp1SmFCOS9WwUqhqT/PhDY2pzc6uuPiYXJrjhhEG23/bF/My oZhw==
X-Gm-Message-State: AKGB3mLORCTltjIhaD+3QQkvRGP6RSEf8gtHrJfSjxj9tVZICDANjTRI u8bE+eAm6L9L2bNzMVKoIVtjuQa1Cp/u/z8hkSjEbw==
X-Google-Smtp-Source: ACJfBosOSm8Bzps2rCgjxjLj4Gn2/3t9VRsenDfLq2zvHjrpKhkszRBVfn0I/FfpZe3IHcFArAguWQctamUzrcocVJM=
X-Received: by 10.129.222.9 with SMTP id k9mr2259997ywj.47.1513184771593; Wed, 13 Dec 2017 09:06:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.123.132 with HTTP; Wed, 13 Dec 2017 09:05:30 -0800 (PST)
In-Reply-To: <DB52F922-FAEF-4DBE-8A8B-F0F6EB009CB1@sn3rd.com>
References: <151312309254.29995.11111198641956884169.idtracker@ietfa.amsl.com> <1e300ca0-f9fd-0079-ea1f-851fe30283cd@nostrum.com> <DB52F922-FAEF-4DBE-8A8B-F0F6EB009CB1@sn3rd.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 13 Dec 2017 09:05:30 -0800
Message-ID: <CABcZeBNM_rQpRJEPC_LNai2FoC13k8a1VHNk8KKpc5gV_riWug@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>, draft-ietf-stir-certificates@ietf.org, stir-chairs@ietf.org, IETF STIR Mail List <stir@ietf.org>, Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary="f403043d0488ca759105603bc874"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/UmxLXZEmuNm8jocf7-erzMRnNWY>
Subject: Re: [stir] Eric Rescorla's Discuss on draft-ietf-stir-certificates-16: (with DISCUSS)
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, 13 Dec 2017 17:06:43 -0000
On Wed, Dec 13, 2017 at 8:36 AM, Sean Turner <sean@sn3rd.com> wrote: > > > > On Dec 13, 2017, at 11:24, Adam Roach <adam@nostrum.com> wrote: > > > > On 12/12/17 17:58, Eric Rescorla wrote: > >> > >> national policies. The count field is only applicable to start > >> fields' whose values do not include "*" or "#" (i.e., a > >> TelephoneNumber that does not include "*" or "#"). count never > >> overflows a TelephoneNumber digit boundary (i.e., a > >> TelephoneNumberRange with TelephoneNumber=10 with a count=91 will > >> address numbers 10-99). > >> > >> This text doesn't seem very clear. When you say "never overflows a digit > >> boundary" do you mean "doesn't extend the integer to the left"? Because > >> you sure seem to be overflowing the 1s place here. > > > > Based on the in-room conversation in Singapore, the notion here seems to > be that the number does not increase in length. > > Yep. > > >> Is the algorithm that you are given the input TN, Count, and TN > >> consists D digits that the range is: > >> > >> MIN(TN + Count, 10^D - 1) > >> > >> That would be consistent with your example here, but I don't think > consistent > >> with your text. Or do you mean something else? > >> > > > > Your formula above matches my understanding, and I think including it in > the document as the formal definition of how 'count' behaves would be the > best way to address the lack of clarity you cite. > > Agreed. How about this change: > > OLD: > > count never overflows a TelephoneNumber digit > boundary (i.e., a TelephoneNumberRange with > TelephoneNumber=10 with a count=91 will address > numbers 10-99). > > NEW: > > count never makes the number increase in length > (i.e., a TelephoneNumberRange with TelephoneNumber=10 > with a count=91 will address numbers 10-99); formally, > given the inputs count and TelephoneNumber of length D > the end of the TelephoneNumberRange is: > MIN(TelephoneNumber + count, 10^D - 1) > This seems fine. -Ekr
- [stir] Eric Rescorla's Discuss on draft-ietf-stir… Eric Rescorla
- Re: [stir] Eric Rescorla's Discuss on draft-ietf-… Adam Roach
- Re: [stir] Eric Rescorla's Discuss on draft-ietf-… Eric Rescorla
- Re: [stir] Eric Rescorla's Discuss on draft-ietf-… Sean Turner
- Re: [stir] Eric Rescorla's Discuss on draft-ietf-… Eric Rescorla