Re: [stir] I-D Action: draft-kaplan-stir-ikes-out-00.txt

Torrey Searle <tsearle@sipstacks.com> Wed, 17 July 2013 07:26 UTC

Return-Path: <tsearle@sipstacks.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 84F7A21F8E79 for <stir@ietfa.amsl.com>; Wed, 17 Jul 2013 00:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.176
X-Spam-Level:
X-Spam-Status: No, score=-2.176 tagged_above=-999 required=5 tests=[AWL=-0.800, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_BACKHAIR_34=1, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mN8ijsqi7bFs for <stir@ietfa.amsl.com>; Wed, 17 Jul 2013 00:26:04 -0700 (PDT)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id 478A421F8C7C for <stir@ietf.org>; Wed, 17 Jul 2013 00:26:04 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id a11so3330590iee.20 for <stir@ietf.org>; Wed, 17 Jul 2013 00:26:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=SAW1hvG4PpbGL21gggShohjVW/LZsBR6A2LlaUzO3Xo=; b=YiI6lRwXytmPPR2x0GUfc8neLuZ1o75JDahCQoDa7wyRWvP3+V18h6yowbght2XbAb B7Lor9uBnmGh8XVkgRJgv51sGp5/hh0sGlvhhneaulx27R9YJdlOb+dzErSrVfOyjCpA L6oAi2hlrtFKse/Gq/R39VKUdH0zKxy1q8bbDirlGA/1QIkpehYDRtoOPzB1zLM8L6XQ GrnvvpmnYo8226XiOGrz8vYNyZ2qnGOstmEX/txqOk09KDul62kBQvNQ/DJFfYB+Sqxl TSn7Y5P8l0UqkCW42YUW+XXfKYcLJ/3o7gdxwtXj9maGTGb5cgEPBy9nmFqGCnUH4Rej ftmw==
MIME-Version: 1.0
X-Received: by 10.43.12.198 with SMTP id pj6mr4449989icb.68.1374045962545; Wed, 17 Jul 2013 00:26:02 -0700 (PDT)
Received: by 10.64.68.132 with HTTP; Wed, 17 Jul 2013 00:26:02 -0700 (PDT)
In-Reply-To: <7B23E7E8-2432-48B8-A2BF-75653D89936F@oracle.com>
References: <20130712043221.11767.74779.idtracker@ietfa.amsl.com> <1F4B4D44-BD3E-4995-876A-147832C925F9@oracle.com> <CAMcvRPC6f+0-sx=eGS-1yy=Ubh-WREw-__WZyeNnS1XypY+Xvg@mail.gmail.com> <7B23E7E8-2432-48B8-A2BF-75653D89936F@oracle.com>
Date: Wed, 17 Jul 2013 09:26:02 +0200
Message-ID: <CAMcvRPCN-VnKajt0Mi_MNaj9S0UChHi=iOu_z7-dUA+idZgGvA@mail.gmail.com>
From: Torrey Searle <tsearle@sipstacks.com>
To: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Content-Type: multipart/alternative; boundary="bcaec518701c80c6b504e1b0017b"
X-Gm-Message-State: ALoCoQkAzZuOhlFXwAxw/eATNjXpdIQ/oUPCHJcWr1hajU/TALH61sT+4mKXTwIg5I9ef5esvCA2
Cc: "stir@ietf.org" <stir@ietf.org>
Subject: Re: [stir] I-D Action: draft-kaplan-stir-ikes-out-00.txt
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 17 Jul 2013 07:26:36 -0000

Hello,

Regarding the SIP <->XMPP inter-working of SUBSCRIBE.  Subscriptions in SIP
are time limited, and last forever in XMPP, as a result, sip<->xmpp gateway
may need to generate several SIP subscribes in response to a single XMPP
subscribe.  Perhaps it's worthwhile to  note that only the Dialog Creating
and Dialog Destroying subscriptions will have a signature, and the rest of
the in-dialog requests should be considered trusted as well?


Regards,
Torrey


On Tue, Jul 16, 2013 at 5:19 AM, Hadriel Kaplan
<hadriel.kaplan@oracle.com>wrote:

>
> On Jul 15, 2013, at 4:05 PM, Torrey Searle <tsearle@sipstacks.com> wrote:
>
> > I really like your draft, especially the fact that inter networks with
> ss7.  Just have a initial comment that in the case of the UUI header, the
> spec should probably specify that  the Protocol Discriminator for the UUI
> header should be set to 00 - User Specific Coding.  Though it might me an
> interesting question if it is possible to use a new value for the protocol
> discriminator to easily identify that the value in the UUI header is a
> signature.
>
> Crap, I forgot about the protocol discriminator.  I don't mean I forgot to
> mention it, I mean I forgot about the byte it takes, not to mention the
> type and length bytes.  That means there're only 128 bytes available, which
> for a 1024-bit private key means all of those 128 bytes will be the
> signature.  So I'll have to move the key index and timestamp fields into
> the Call-Reference param instead.  Ugh.
>
> But anyway, yeah good catch, the discriminator should probably be 0x00.
>
>
> > Also how about the case where bob@example.com gets aliased to an e164
> when reaching the pstn gateway?  I assume the pstn gateway would "own" the
> e164 and can re-sign the call before forwarding, but would it be
> interesting to mention this case in the spec?
>
> Does that ever happen in the PSTN gateways?  I know it happens in some
> service providers (like skype for example), but I thought it happened on
> some SIP or H.323 system just before it reached the PSTN GW.  Regardless,
> yes I should mention that in the draft too.
>
> Thanks for the feedback!
>
> -hadriel
>
>