Re: [cnit] CNIT Charter bashing..

Henning Schulzrinne <Henning.Schulzrinne@fcc.gov> Fri, 12 June 2015 14:07 UTC

Return-Path: <Henning.Schulzrinne@fcc.gov>
X-Original-To: cnit@ietfa.amsl.com
Delivered-To: cnit@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49D981AC42B for <cnit@ietfa.amsl.com>; Fri, 12 Jun 2015 07:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.811
X-Spam-Level:
X-Spam-Status: No, score=-2.811 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 HwImSJBguKGT for <cnit@ietfa.amsl.com>; Fri, 12 Jun 2015 07:07:42 -0700 (PDT)
Received: from DC-IP-1.fcc.gov (dc-ip-1.fcc.gov [192.104.54.97]) by ietfa.amsl.com (Postfix) with ESMTP id 256531AC423 for <cnit@ietf.org>; Fri, 12 Jun 2015 07:07:41 -0700 (PDT)
Message-ID: <E6A16181E5FD2F46B962315BB05962D07D3554F9@fcc.gov>
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: Richard Shockey <richard@shockey.us>, "philippe.fouquart@orange.com" <philippe.fouquart@orange.com>, "cnit@ietf.org" <cnit@ietf.org>
Thread-Topic: [cnit] CNIT Charter bashing..
Thread-Index: AQHQpF27t1IjTQnD9Ee6If5FuC7/752nvtOAgAAcbYD//73Z54ABUaEA///tFM2AAEwjgP//wzVI
Date: Fri, 12 Jun 2015 14:07:19 +0000
References: <D19F23AD.26CEA%richard@shockey.us> <E42CCDDA6722744CB241677169E8365603614617@MISOUT7MSGUSRDB.ITServices.sbc.com> <9588_1434045613_5579CCAD_9588_574_1_fki5dyxdmgyv92b6hugpfuoy.1434045608655@email.android.com> <E6A16181E5FD2F46B962315BB05962D07D354C94@fcc.gov> <9384_1434103912_557AB068_9384_7221_1_B5939C6860701C49AA39C5DA5189448B14C216E0@OPEXCLILM42.corporate.adroot.infra.ftgroup> <E6A16181E5FD2F46B962315BB05962D07D355444@fcc.gov>, <D1A055CF.26E60%richard@shockey.us>
In-Reply-To: <D1A055CF.26E60%richard@shockey.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/cnit/ruBxqRcUfxBdkycHuHCXpZyTQ30>
Subject: Re: [cnit] CNIT Charter bashing..
X-BeenThere: cnit@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Calling Name Identity Trust discussion list <cnit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cnit>, <mailto:cnit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cnit/>
List-Post: <mailto:cnit@ietf.org>
List-Help: <mailto:cnit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cnit>, <mailto:cnit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Jun 2015 14:07:44 -0000

There seem to be three levels:

(1) Make existing SIP display name information survive NNI and VoIP-to-TDM translation. The ATIS-SIPForum effort seems to be an appropriate venue for that as it involves no new SIP headers or SIP behavior.

(2) Allow for (but not mandate) signing the display name. We need to determine whether this is just another STIR special case or not. This applies to the (common) case where the signer of the SIP request is also in a position to validate the caller name, using whatever internal policies they may have. (In some cases, this is simply whatever the subscriber typed into a web form, so this isn't perfect, but since the number signing will provide traceability, the FBI and IRS along with HSBC and Microsoft know whom to talk to if a customer of Joe's VoIP Service & Salvage asserts those identities. Trademark law and civil fraud statutes seem to cover that case; the main practical difficulty today is that finding the source of the information is impossible.)

(3) Better caller name information that allows parties other than the carrier to assert additional information.

Does that cover the options?

Henning


________________________________________
From: Richard Shockey [richard@shockey.us]
Sent: Friday, June 12, 2015 9:36 AM
To: Henning Schulzrinne; philippe.fouquart@orange.com; cnit@ietf.org
Subject: Re: [cnit] CNIT Charter bashing..



RS> Well intra enterprise certainly.  There it tends to get pulled from
Active Directory but until we can get the NNI interface deployed its not
working at all for inter enterprise.  We are certainly looking at that for
Phase 2 of the NNI TF.

My goal is some what more modest for a first phase.  Certainly you want
signed extended versions of the display name but one should not create
artificial barriers to non signed data exchanges between service providers
where the security comes from the big yellow wire at Layer 1.  Plus I
still want a straight answer if this proposal is going to have a
requirement for a new SIP header and all the IETF ART pain and suffering
that goes with that. I want the AD¹s to make that demand ( if it is to be
imposed) explicit now.