From nobody Wed Jun 22 08:29:57 2022 Return-Path: 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 A2A7BC14CF06 for ; Wed, 22 Jun 2022 08:29:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.108 X-Spam-Level: X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telurix.com Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R3sg8EMlhMOr for ; Wed, 22 Jun 2022 08:29:51 -0700 (PDT) Received: from mail-qv1-xf2c.google.com (mail-qv1-xf2c.google.com [IPv6:2607:f8b0:4864:20::f2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C10D0C157B32 for ; Wed, 22 Jun 2022 08:29:46 -0700 (PDT) Received: by mail-qv1-xf2c.google.com with SMTP id cs6so21140245qvb.6 for ; Wed, 22 Jun 2022 08:29:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=9lQrUYlmRTOZoEDi6fcc1y2lLaDu0X+s8FSva0rlO/Q=; b=tH3OEhfKTFnZwFnOCrc+AVTFY/OveUlxaDktUYYUOpu2GmDVmE7mJBrOxo+40k2wgH 5wpt9h7KEe2uD8PycZfcxlZNZ4qiaCSfnuVWQbzKpSlGHJW0v2K61IK8LRQZLCCkRHe/ l657yr1cWRG7BHgLcB7O39A0Ac7Snp+eRYWIM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=9lQrUYlmRTOZoEDi6fcc1y2lLaDu0X+s8FSva0rlO/Q=; b=mtP7RQz/AIisQx7YnY+11aoxZMtd3MaY8E7hIwKmL9J/50DeYdNcZGyJjp2L4AC7L/ tCob/fXo8W5LjQmZ/YmuAzW2Z9EVPfRSzOicp0hLwYzx/idPNFSFiLId9D7iohvIUG2U ZIlS8lsrAPy6FeC2uvIOp+auh7luzU8hk+UH9grZiM2EFk0KKko+nuqsO3N2hZZ2www7 xqQWWWg9/vjn3nc8LmsC7lwhF9KgjN8ur2JnvP/Gj9Y2a0XhsNklfJD1M7IjyNBhjhnW 1YbXVa5B+7zDrWgmyCpIlpiK7w7ZRFTxDcYd9l9ned7dPHEwh770RuqgbZYBG+qWhx/y gfBQ== X-Gm-Message-State: AJIora+pzQPWBELI6eCroQoBxbwmg3l2HQnrMdvj0pk2M+g1ykpmynp9 hMXZVoesrk+mst600QXQveFMeY4qhkUZWA== X-Google-Smtp-Source: AGRyM1skN5rnaoDYoz3Xns8UjJ/f5/4GRj94qJB1U6aBiSOVgq6/+g0bd4OMXy3lu2SnUHPTjjH9TA== X-Received: by 2002:ac8:7c50:0:b0:305:392:9780 with SMTP id o16-20020ac87c50000000b0030503929780mr3529080qtv.589.1655911784991; Wed, 22 Jun 2022 08:29:44 -0700 (PDT) Received: from mail-yw1-f177.google.com (mail-yw1-f177.google.com. [209.85.128.177]) by smtp.gmail.com with ESMTPSA id x28-20020ac8701c000000b00316022dcc08sm1141203qtm.11.2022.06.22.08.29.44 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Jun 2022 08:29:44 -0700 (PDT) Received: by mail-yw1-f177.google.com with SMTP id 00721157ae682-3176b6ed923so166430937b3.11 for ; Wed, 22 Jun 2022 08:29:44 -0700 (PDT) X-Received: by 2002:a81:6e02:0:b0:317:b68d:3870 with SMTP id j2-20020a816e02000000b00317b68d3870mr4967949ywc.222.1655911783887; Wed, 22 Jun 2022 08:29:43 -0700 (PDT) MIME-Version: 1.0 From: Roman Shpount Date: Wed, 22 Jun 2022 11:29:33 -0400 X-Gmail-Original-Message-ID: Message-ID: To: IETF STIR Mail List Content-Type: multipart/alternative; boundary="000000000000a87b5405e20b01a9" Archived-At: Subject: [stir] Identity and Diversion header X-BeenThere: stir@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Secure Telephone Identity Revisited List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2022 15:29:55 -0000 --000000000000a87b5405e20b01a9 Content-Type: text/plain; charset="UTF-8" Hi All, We had an interesting issue that came up during the identity implementation. When a call is diverted to a different phone number, the Identity header covers the phone number from which the call is diverted. The original from a phone number is present in the Diversion header, but all the identity and potential rich call data information for this phone number is lost. This creates problems for some services, such as external email systems. Have there been any discussions about preserving original Identity information when calls are diverted? Thank You, _____________ Roman Shpount --000000000000a87b5405e20b01a9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

We had an interesting issue tha= t came up during the identity=C2=A0implementation. When a call is diverted = to a different phone number, the=C2=A0Identity header covers the phone numb= er from which the call is diverted. The original from a phone number is pre= sent in the Diversion header, but all the identity and potential rich call = data information for this phone number is lost. This creates problems for s= ome services, such as external email systems.

Have= there been any discussions about preserving original Identity information = when calls are diverted?

Thank You,
_____________
Roman Shpount
--000000000000a87b5405e20b01a9--