IETF Logo Mail Archive

Re: [Insipid] Reviews for INSIPID Session-ID solution draft

Arun Arunachalam <carunach@cisco.com> Mon, 04 August 2014 22:58 UTC

Return-Path: <carunach@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DE81A03EA for <insipid@ietfa.amsl.com>; Mon, 4 Aug 2014 15:58:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 eMyBls4AGq-u for <insipid@ietfa.amsl.com>; Mon, 4 Aug 2014 15:58:01 -0700 (PDT)
Received: from av-tac-jap.cisco.com (skinny-sumo.cisco.com [64.104.15.102]) by ietfa.amsl.com (Postfix) with ESMTP id BA0FF1A03DE for <insipid@ietf.org>; Mon, 4 Aug 2014 15:58:00 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from fire.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-jap.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id s74Mvuww002376; Tue, 5 Aug 2014 07:57:57 +0900 (JST)
Received: from dhcp-10-150-54-58.cisco.com (dhcp-10-150-54-58.cisco.com [10.150.54.58]) by fire.cisco.com (8.14.5+Sun/8.13.8) with ESMTP id s74MvqHf023631; Mon, 4 Aug 2014 15:57:52 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Arun Arunachalam <carunach@cisco.com>
In-Reply-To: <8b639cc7c90f95a505b7ed66a9af5cce@mail.gmail.com>
Date: Mon, 04 Aug 2014 18:57:52 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <80C0F26B-EE04-4528-9353-073FBE85C760@cisco.com>
References: <4DB16225-A09D-4B9A-ADAB-9C2B23FE3D57@cisco.com> <49405AE0-0C44-4260-849B-22621387581A@cisco.com> <999A3253-0F6E-4172-BC5B-8B851BC60019@cisco.com> <0663B39E-2E3F-4B03-AC7C-BC5C83324DD7@cisco.com> <8b639cc7c90f95a505b7ed66a9af5cce@mail.gmail.com>
To: Brett Tate <brett@broadsoft.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/insipid/JXdjs6eu0aIpJgP3J-0CsXWjI-M
Cc: "Arun Arunachalam (carunach)" <carunach@cisco.com>, insipid@ietf.org
Subject: Re: [Insipid] Reviews for INSIPID Session-ID solution draft
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Aug 2014 22:58:02 -0000

Thanks Brett.

Yes, I was looking for examples where this statement could be applicable.

Arun

On Aug 4, 2014, at 6:24 AM, Brett Tate <brett@broadsoft.com> wrote:

>> Section 4.1 (page 4)
>> Intermediaries that insert a Session-ID header into a SIP message on
>>    behalf of a sending User Agent MUST utilize version 5 UUIDs to ensure
>>    that UUIDs for the communication session are consistently generated.
>>   If an intermediary does not know the tag value for an endpoint, the
>>    intermediary MUST NOT attempt to generate a UUID for that endpoint.
>> 
>>   Typically, an INVITE from an endpoint will have a From tag. Can you
> give
>> an example where the intermediary doesn't know the tag value?
> 
> If you are seeking an answer instead of requesting that the example be
> included within draft...
> 
> The text indicates how to behave when interacting with devices
> non-compliant to RFC 3261.  For instance, tag usage was not always
> mandatory within RFC 2543.

v2.23.0 | Report a Bug | By Email