IETF Logo Mail Archive

Re: [stir] URN SOS

Paul Kyzivat <pkyzivat@alum.mit.edu> Mon, 23 December 2019 15:09 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 1BD8612008D for <stir@ietfa.amsl.com>; Mon, 23 Dec 2019 07:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 GFYCRaFzbWCb for <stir@ietfa.amsl.com>; Mon, 23 Dec 2019 07:09:27 -0800 (PST)
Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11on2061.outbound.protection.outlook.com [40.107.236.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA661120026 for <stir@ietf.org>; Mon, 23 Dec 2019 07:09:26 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=N7Cq/EdtPi34HAEIt60NZ/ezPAvjYURi3FtxyYR2c3g+zixA5N7f4xtb8MzBIuaTnMUznnMwV8LN1W40neeIO9GIvLCxnsR5jxCUfCCOaP0ngqi/Sfw1OXhD+ehDbBv0HfBJRQYR419BotIeh2ddyvYWKyaXfFevL1WIOfZtUN20yBsNk3elT+KgJAdF7X2w5IR9A/cH1lDtRHniszazR+7al1aLwZM8xOjft2hApm2vHsZ3EdJfk31o4uTH0QZeQ+WQSHPDITYrvMSAFkYKa74BdLMXVSaSgIyEuv58ELO5XhN8dLbQcdU5uFswfeJJ6PU8WDmbPP97zM4Jro/YiQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dNuQf5HRom15iJsMMYLznsMRmtwItZrMkG4EIy53qwY=; b=GbRAV/6l9iTpu/DfAqDalvWZPQdXfqqt5wnpJm/dPMU0x4a0BJqonhPUPr+P5ssnqA0xTSAal1mvzcMUh73fNheh8rUGwHCCIYNnuhJK+BbbuMkoKfns2MqU4qS2nl+yXEVxxHq4UZwvDXxXE/ySOr9kxQP0vbvMp1dKNDR4AoXxE4Q29qPuVMozFBTxbeVn6+ce4EKzeuzz2zDk5zgy9ncPh6SOs4diBnKS/pjpRVepZ+oWc2NiS+pNcyztBJWBu4UYo1WtVlfzChcSjqzsXhC9fnwU7b8nllt3iDy16Dya0QbbFsBi/DBixG1orTOxCqPdWwytqLaRqfbvkCoTPA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=ietf.org smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dNuQf5HRom15iJsMMYLznsMRmtwItZrMkG4EIy53qwY=; b=eOjpGudNgqawtiSrUk1Tg+khRC1ixPFZXhRCFwk8SwdVVx+BRPrQPsVBvGtoilCOabnPhceW0rFj3RZqlE1oGQMTJi/6QGsAmfywleUz8oNahq0rxNzY/iAbE7aEU5kcuWzZRh2uZU6R/vTgUwXGOo/VtreBay32jVVVYXUgTic=
Received: from DM5PR12CA0070.namprd12.prod.outlook.com (2603:10b6:3:103::32) by BN7PR12MB2803.namprd12.prod.outlook.com (2603:10b6:408:32::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.16; Mon, 23 Dec 2019 15:09:25 +0000
Received: from SN1NAM02FT009.eop-nam02.prod.protection.outlook.com (2a01:111:f400:7e44::208) by DM5PR12CA0070.outlook.office365.com (2603:10b6:3:103::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.14 via Frontend Transport; Mon, 23 Dec 2019 15:09:24 +0000
Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT009.mail.protection.outlook.com (10.152.73.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.14 via Frontend Transport; Mon, 23 Dec 2019 15:09:24 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id xBNF9M76010420 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <stir@ietf.org>; Mon, 23 Dec 2019 10:09:23 -0500
To: stir@ietf.org
References: <EF51940D-F3B7-4F4E-9AA4-CFE76B75194D@vigilsec.com> <CAL02cgQdow3HsWe-EH-UQU-5bwegyjxsEA+DLRp6TcyrZtLLLg@mail.gmail.com> <00593B03-11CE-4364-97AF-79B53881FCF6@vigilsec.com> <CACG=0wRwcf543PSJqoMRZVx29w3XwXT2_vzTsbKjFb3vxVL_bg@mail.gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <13e7729e-38e4-9e6e-5c66-1c8b680ee7d0@alum.mit.edu>
Date: Mon, 23 Dec 2019 10:09:22 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <CACG=0wRwcf543PSJqoMRZVx29w3XwXT2_vzTsbKjFb3vxVL_bg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:18.7.68.33; IPV:CAL; SCL:-1; CTRY:US; EFV:NLI; SFV:NSPM; SFS:(10009020)(376002)(396003)(346002)(39860400002)(136003)(189003)(199004)(76130400001)(2906002)(246002)(70206006)(8936002)(786003)(53546011)(336012)(31686004)(316002)(31696002)(956004)(75432002)(2616005)(26005)(6916009)(186003)(86362001)(8676002)(478600001)(966005)(70586007)(36906005)(26826003)(5660300002)(7596002)(356004); DIR:OUT; SFP:1101; SCL:1; SRVR:BN7PR12MB2803; H:outgoing-alum.mit.edu; FPR:; SPF:Pass; LANG:en; PTR:outgoing-alum.mit.edu; MX:1; A:1;
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: fe4a8fdb-b639-47b3-43dc-08d787ba18c8
X-MS-TrafficTypeDiagnostic: BN7PR12MB2803:
X-Microsoft-Antispam-PRVS: <BN7PR12MB2803528EF530957E4BE0F261F92E0@BN7PR12MB2803.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:9508;
X-Forefront-PRVS: 0260457E99
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 6y7tJhpUxYATwSi9zcvPib4AnZ8Y9cL2pJfWpr1Gzt7u2uA80iLNRF6lY8a+TCKe0nWTyVrj170KK2R2UevRJTRML+fioY5Cw5OnnTK/lJ7xUS59H8XYy/tri04eSD1tIb34dezDFaUSGrLI4VIQVT8WZADDdAcGy5CPnVJ3IggWQ7tk+KDrLQ/2K5bL8O70f9og4IaYuYjI2B2LZxzfcGzpWAZl1ieVcQLbpOwfXVsc+/dJ+3p/q9b7r+hek51uW6ycCa1Lie+fDNPr+mLVGuGck9nWx9ywLpNsX28zkxYFBoMAU6wZmoMAKhSWdegELHOuU8EZOS6FT1f/9Fq4o6BAnhcqNYKEmG3f+1nYnxEFw75SF2ITNTI/awxUKz6vSKMRWiEjhN4Gn8u/tIg5AmxDI3r/l+AEK9pN9sPg0bG3dvJAAWXl3woEY5265FR70DxuQHltDNozypiIchgaLNGZpp7Oz+A3pmyCOS4emtM=
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Dec 2019 15:09:24.4227 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: fe4a8fdb-b639-47b3-43dc-08d787ba18c8
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN7PR12MB2803
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/06zhc0xgVsUa719_-njfwxYq_ps>
Subject: Re: [stir] URN SOS
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 23 Dec 2019 15:09:29 -0000

On 12/23/19 9:02 AM, Anders Kristensen wrote:
> May have to do with the fact that RFC 8224 does not cover URNs:

If the problem is that URNs aren't covered, then how would replacing 
urn:service:sos with urn:sos solve the problem???

The use of urn:service:sos is institutionalized now in a lot of 
documents. Changing that seems like a hard problem. How about fixing RFC 
8224?

	Thanks,
	Paul

>     1 <https://tools.ietf..org/html/rfc8224#section-1>. Introduction
> 
> 
> 
>     This document provides enhancements to the existing mechanisms for
>     authenticated identity management in the Session Initiation Protocol
>     (SIP) [RFC3261  <https://tools.ietf.org/html/rfc3261>].  An identity, for the purposes of this document, is
>     defined as either
> 
>     o  a canonical address-of-record (AoR) SIP URI employed to reach a
>        user (such as "sip:alice@atlanta.example.com  <mailto:sip%3Aalice@atlanta.example.com>") or
> 
>     o  a telephone number, which commonly appears either in a tel URI
>        [RFC3966  <https://tools.ietf.org/html/rfc3966>] or as the user portion of a SIP URI.
> 
> 
> On Sun, Dec 22, 2019 at 1:14 PM Russ Housley <housley@vigilsec.com 
> <mailto:housley@vigilsec.com>> wrote:
> 
>     Richard:
> 
>     It seems to meet the need that was raised in the discussion.  Others
>     can comment if I missed some important context.
> 
>     Russ
> 
> 
>>     On Dec 22, 2019, at 3:38 PM, Richard Barnes <rlb@ipv.sx
>>     <mailto:rlb@ipv.sx>> wrote:
>>
>>     Not sure if this is what you’re thinking of, or if this has
>>     already been mentioned, but: urn:service:sos exists.
>>
>>     https://tools.ietf.org/html/rfc5031
>>
>>
>>     On Sat, Dec 21, 2019 at 17:26 Russ Housley <housley@vigilsec.com
>>     <mailto:housley@vigilsec.com>> wrote:
>>
>>         At the session at IETF 106, there was a suggestion that a URN
>>         SOS be defined.  I am sending this note to start a discussion
>>         on that topic.
>>
>>         Russ
>>         _______________________________________________
>>         stir mailing list
>>         stir@ietf.org <mailto:stir@ietf.org>
>>         https://www.ietf.org/mailman/listinfo/stir
>>
>>     _______________________________________________
>>     stir mailing list
>>     stir@ietf.org <mailto:stir@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/stir
> 
>     _______________________________________________
>     stir mailing list
>     stir@ietf.org <mailto:stir@ietf.org>
>     https://www.ietf.org/mailman/listinfo/stir
> 
> 
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir
>

v2.23.0 | Report a Bug | By Email